EVerest API definition for display messages 1.0.0

API for EVerest api clients implementing display message.

  • #EVerest
  • #display_message

Servers

  • mqtt://localhost:1883/everest_api/1/display_message/{module_id}mqttdefault

    default local MQTT

    object
    module_id
    required
    string

    The ID of the module as defined in the EVerest config file.

Operations

  • REPLY e2m/set_display_message

    Direction: EVerest to Module

    Operation IDreceive_request_set_display_message

    Available only on servers:

    Accepts the following message:

    Request set display messagereceive_request_set_display_message

    Request to set a display message

    Message IDreceive_request_set_display_message
    object

    Examples

    REPLY INFORMATION

    REPLY CHANNEL INFORMATION

    Reply will be directed to the address specified at this location: $message.header#/replyTo

    REPLY address information

    REPLY will be sent to the address provided in:$message.header#/replyTo
  • SEND

    Operation IDsend_reply_set_display_message

    Available only on servers:

    Accepts the following message:

    Reply set display messagesend_reply_set_display_message

    Reply to a request to set adisplay message

    Message IDsend_reply_set_display_message
    object

    Response to the set display message request.

    Examples

  • REPLY e2m/get_display_message

    Direction: EVerest to Module

    Operation IDreceive_request_get_display_message

    Available only on servers:

    Accepts the following message:

    Request get display messagereceive_request_get_display_message

    Request to get a display message

    Message IDreceive_request_get_display_message
    object

    Examples

    REPLY INFORMATION

    REPLY CHANNEL INFORMATION

    Reply will be directed to the address specified at this location: $message.header#/replyTo

    REPLY address information

    REPLY will be sent to the address provided in:$message.header#/replyTo
  • SEND

    Operation IDsend_reply_get_display_message

    Available only on servers:

    Accepts the following message:

    Reply get display messagesend_reply_get_display_message

    Reply to a request to get adisplay message

    Message IDsend_reply_get_display_message
    object

    Reponse on the 'get display message' request. Will return the requested display messages.

    Examples

  • REPLY e2m/clear_display_message

    Direction: EVerest to Module

    Operation IDreceive_request_clear_display_message

    Available only on servers:

    Accepts the following message:

    Request clear display messagereceive_request_clear_display_message

    Request to clear a display message

    Message IDreceive_request_clear_display_message
    object

    Examples

    REPLY INFORMATION

    REPLY CHANNEL INFORMATION

    Reply will be directed to the address specified at this location: $message.header#/replyTo

    REPLY address information

    REPLY will be sent to the address provided in:$message.header#/replyTo
  • SEND

    Operation IDsend_reply_clear_display_message

    Available only on servers:

    Accepts the following message:

    Reply clear display messagesend_reply_clear_display_message

    Reply to a request to clear adisplay message

    Message IDsend_reply_clear_display_message
    object

    Response on the clear display message request.

    Examples

  • RECEIVE e2m/heartbeat

    Operation IDreceive_heartbeat

    Available only on servers:

    Accepts the following message:

    Receive heartbeatreceive_heartbeat

    Heartbeat produced by EVerest as configured via cfg_heartbeat_interval_ms in the EVerest configuration

    Message IDreceive_heartbeat
    Payload
    integer

    64bit unsigned integer. The id of every heartbeat increases by 1 and overflows when the maximum representable value is reached

    Examples

  • SEND m2e/communication_check

    Operation IDsend_communication_check

    Available only on servers:

    Accepts the following message:

    Send communication checksend_communication_check

    Signal to EVerest that communication is good or check shall be stopped

    Message IDsend_communication_check
    Payload
    boolean

    Send 'true' at least every 'cfg_communication_check_to_s' seconds to signal module is alive. Send 'false' to stop communication check'

    Examples

Messages

  • #1Request set display messagereceive_request_set_display_message

    Request to set a display message

    Message IDreceive_request_set_display_message
    object
  • #2Reply set display messagesend_reply_set_display_message

    Reply to a request to set adisplay message

    Message IDsend_reply_set_display_message
    object

    Response to the set display message request.

  • #3Request get display messagereceive_request_get_display_message

    Request to get a display message

    Message IDreceive_request_get_display_message
    object
  • #4Reply get display messagesend_reply_get_display_message

    Reply to a request to get adisplay message

    Message IDsend_reply_get_display_message
    object

    Reponse on the 'get display message' request. Will return the requested display messages.

  • #5Request clear display messagereceive_request_clear_display_message

    Request to clear a display message

    Message IDreceive_request_clear_display_message
    object
  • #6Reply clear display messagesend_reply_clear_display_message

    Reply to a request to clear adisplay message

    Message IDsend_reply_clear_display_message
    object

    Response on the clear display message request.

  • #7Receive heartbeatreceive_heartbeat

    Heartbeat produced by EVerest as configured via cfg_heartbeat_interval_ms in the EVerest configuration

    Message IDreceive_heartbeat
    Payload
    integer

    64bit unsigned integer. The id of every heartbeat increases by 1 and overflows when the maximum representable value is reached

  • #8Send communication checksend_communication_check

    Signal to EVerest that communication is good or check shall be stopped

    Message IDsend_communication_check
    Payload
    boolean

    Send 'true' at least every 'cfg_communication_check_to_s' seconds to signal module is alive. Send 'false' to stop communication check'

Schemas

  • object

    Request to remove a specific display message.

  • object

    Response on the clear display message request.

  • ClearMessageResponseEnum
    string

    Response on a clear display message request

      Allowed values:
    • "Accepted"
    • "Unknown"
  • object

    Message to show on a display

  • DisplayMessageStatusEnum
    string

    Response on a display message request

      Allowed values:
    • "Accepted"
    • "NotSupportedMessageFormat"
    • "Rejected"
    • "NotSupportedPriority"
    • "NotSupportedState"
    • "UnknownTransaction"
  • IdentifierType
    string

    The identifier type

      Allowed values:
    • "IdToken"
    • "SessionId"
    • "TransactionId"
  • object

    Contains message details

  • MessageFormat
    string

    Format of the message to be displayed

      Allowed values:
    • "ASCII"
    • "HTML"
    • "URI"
    • "UTF8"
    • "QRCODE"
  • MessagePriorityEnum
    string

    Priority of the message. AlwaysFront is the highest priority: The Charging Station SHALL show this message at the configured moment, regardless of other installed messages. Hence, it shall not cycle it with other messages and the Charging Station’s own message shall not override this message. When a newer message with this MessagePriority is received, this message is replaced. InFront: The Charging Station SHALL show this message at the configured moment, regardless of the normal cycle of messages. If there are multiple InFront message that must be shown at the same time, they must be cycled. NormalCycle: Show this message in the cycle of messages.

      Allowed values:
    • "AlwaysFront"
    • "InFront"
    • "NormalCycle"
  • MessageStateEnum
    string

    During what state the message should be shown

      Allowed values:
    • "Charging"
    • "Faulted"
    • "Idle"
    • "Unavailable"
    • "Suspending"
    • "Discharging"
  • object

    Request display messages. The properties are filtered. If the properties are omitted, there will be no filter applied (if all properties are omitted, all stored display messages will be returned).

  • object

    Reponse on the 'get display message' request. Will return the requested display messages.

  • array<object>

    Request to set a list of display messages.

  • object

    Response to the set display message request.

  • CommunicationCheck
    boolean

    Send 'true' at least every 'cfg_communication_check_to_s' seconds to signal module is alive. Send 'false' to stop communication check'

  • HeartBeatId
    integer

    64bit unsigned integer. The id of every heartbeat increases by 1 and overflows when the maximum representable value is reached