EVerest API definition for the use of the EVSE manager 1.0.0

API to allow EVerest API clients to use the EvseManager module.

  • #EVerest
  • #EVSE manager

Servers

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

    default local MQTT

    object
    module_id
    required
    string

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

Operations

  • REQUEST m2e/get_evse

    Direction: Module to EVerest

    Operation IDsend_request_get_evse

    Available only on servers:

    Accepts the following message:

    Request to get EVSEsend_request_get_evse

    Request to get EVSE.

    Message IDsend_request_get_evse
    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

  • RECEIVE

    Operation IDreceive_reply_get_evse

    Available only on servers:

    Accepts the following message:

    Reply to request to get EVSEreceive_reply_get_evse

    Reply to the request to get the EVSE.

    Message IDreceive_reply_get_evse
    object

    Type that defines properties of an EVSE including its connectors

    Examples

  • REQUEST m2e/enable_disable

    Direction: Module to EVerest

    Operation IDsend_request_enable_disable

    Available only on servers:

    Accepts the following message:

    Request to enable or disable the EVSEsend_request_enable_disable

    Enables or disables the evse. Turns off PWM with error F. Charging is only possible if an EVSE is enabled.

    Message IDsend_request_enable_disable
    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

  • RECEIVE

    Operation IDreceive_reply_enable_disable

    Available only on servers:

    Accepts the following message:

    Reply to request to enable or disable the EVSEreceive_reply_enable_disable

    Reply to the request to enable or disable the EVSE.

    Message IDreceive_reply_enable_disable
    Payload
    boolean

    Returns true if evse is enabled after the command, false if it is disabled. This may not be the same value as the request, since there may be a higher priority request from another source that is actually deciding whether it is enabled or disabled.

    Examples

  • REQUEST m2e/pause_charging

    Direction: Module to EVerest

    Operation IDsend_request_pause_charging

    Available only on servers:

    Accepts the following message:

    Request pause chargingsend_request_pause_charging

    Request to pause charging.

    Message IDsend_request_pause_charging
    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

  • RECEIVE

    Operation IDreceive_reply_pause_charging

    Available only on servers:

    Accepts the following message:

    Reply to pause charging requestreceive_reply_pause_charging

    Reply to the request to pause charging.

    Message IDreceive_reply_pause_charging
    Payload
    boolean

    Reply to pause charging request. 'true' on success

    Examples

  • REQUEST m2e/resume_charging

    Direction: Module to EVerest

    Operation IDsend_request_resume_charging

    Available only on servers:

    Accepts the following message:

    Request resume chargingsend_request_resume_charging

    Request to resume charging.

    Message IDsend_request_resume_charging
    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

  • RECEIVE

    Operation IDreceive_reply_resume_charging

    Available only on servers:

    Accepts the following message:

    Reply to resume charging requestreceive_reply_resume_charging

    Reply to the request to resume charging.

    Message IDreceive_reply_resume_charging
    Payload
    boolean

    Reply to resume charging request. 'true' on success, false otherwise (e.g. resuming a car pause won't work)

    Examples

  • REQUEST m2e/stop_transaction

    Direction: Module to EVerest

    Operation IDsend_request_stop_transaction

    Available only on servers:

    Accepts the following message:

    Request stop transactionsend_request_stop_transaction

    Request to stop the current transaction.

    Message IDsend_request_stop_transaction
    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

  • RECEIVE

    Operation IDreceive_reply_stop_transaction

    Available only on servers:

    Accepts the following message:

    Reply to stop transaction requestreceive_reply_stop_transaction

    Reply to the request to stop the current transaction.

    Message IDreceive_reply_stop_transaction
    Payload
    boolean

    Reply to stop transaction request. 'true' on success

    Examples

  • REQUEST m2e/force_unlock

    Direction: Module to EVerest

    Operation IDsend_request_force_unlock

    Available only on servers:

    Accepts the following message:

    Request force unlocksend_request_force_unlock

    Request to force unlock.

    Message IDsend_request_force_unlock
    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

  • RECEIVE

    Operation IDreceive_reply_force_unlock

    Available only on servers:

    Accepts the following message:

    Reply to force unlock requestreceive_reply_force_unlock

    Forces connector to unlock connector now. During normal operation, connector will be locked/unlocked in the correct sequence.Do not use this function except if explicitly requested by e.g. management cloud.

    Message IDreceive_reply_force_unlock
    Payload
    boolean

    Returns true if unlocking sequence was successfully executed

    Examples

  • RECEIVE e2m/session_event

    Operation IDreceive_session_event

    Available only on servers:

    Accepts the following message:

    Receive session eventreceive_session_event

    Emits all events related to sessions

    Message IDreceive_session_event
    object

    Emits all events related to sessions

    Examples

  • REQUEST m2e/session_event/get

    Request the most recently published (latched) session event. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_session_event

    Available only on servers:

    Accepts the following message:

    Request current session eventsend_request_get_session_event

    Request the most recently published (latched) session event.

    Message IDsend_request_get_session_event
    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

  • RECEIVE

    Operation IDreceive_reply_get_session_event

    Available only on servers:

    Accepts the following message:

    Reply to get session event requestreceive_reply_get_session_event

    The most recently published session event.

    Message IDreceive_reply_get_session_event
    oneOf

    Examples

  • RECEIVE e2m/hlc_session_failed

    Operation IDreceive_hlc_session_failed

    Available only on servers:

    Accepts the following message:

    Receive HLC session failed eventreceive_hlc_session_failed

    Emits if a HLC session failed

    Message IDreceive_hlc_session_failed
    object

    Published on the hlc_session_failed variable whenever an HLC session failure occurs. Can fire multiple times per EVerest session (e.g. on retries). Use uuid to correlate with session_event.

    Examples

  • REQUEST m2e/hlc_session_failed/get

    Request the most recently published (latched) hlc session failed. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_hlc_session_failed

    Available only on servers:

    Accepts the following message:

    Request current hlc session failedsend_request_get_hlc_session_failed

    Request the most recently published (latched) hlc session failed.

    Message IDsend_request_get_hlc_session_failed
    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

  • RECEIVE

    Operation IDreceive_reply_get_hlc_session_failed

    Available only on servers:

    Accepts the following message:

    Reply to get hlc session failed requestreceive_reply_get_hlc_session_failed

    The most recently published hlc session failed.

    Message IDreceive_reply_get_hlc_session_failed
    oneOf

    Examples

  • RECEIVE e2m/ev_info

    Operation IDreceive_ev_info

    Available only on servers:

    Accepts the following message:

    Receive details about EVreceive_ev_info

    More details about the EV if available.

    Message IDreceive_ev_info
    object

    Information about the connected EV if available

    Examples

  • REQUEST m2e/ev_info/get

    Request the most recently published (latched) ev info. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_ev_info

    Available only on servers:

    Accepts the following message:

    Request current ev infosend_request_get_ev_info

    Request the most recently published (latched) ev info.

    Message IDsend_request_get_ev_info
    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

  • RECEIVE

    Operation IDreceive_reply_get_ev_info

    Available only on servers:

    Accepts the following message:

    Reply to get ev info requestreceive_reply_get_ev_info

    The most recently published ev info.

    Message IDreceive_reply_get_ev_info
    oneOf

    Examples

  • RECEIVE e2m/session_info

    Operation IDreceive_session_info

    Available only on servers:

    Accepts the following message:

    Receive session and transaction informationreceive_session_info

    Information about the current session and transaction. During a session, data is published with a frequency of ~1Hz. If no session is active, data is published on change. A session starts when the first user interaction occurs, e.g. plug in of an EV or authorization was provided. A session ends when the EV is unplugged or the authorization has timed out. A transaction starts if an EV is plugged in and the user is authorized. A transaction ends when the EV is unplugged or the user is not authorized anymore.

    Message IDreceive_session_info
    object

    Context for Session information

    Examples

  • REQUEST m2e/session_info/get

    Request the most recently published (latched) session info. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_session_info

    Available only on servers:

    Accepts the following message:

    Request current session infosend_request_get_session_info

    Request the most recently published (latched) session info.

    Message IDsend_request_get_session_info
    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

  • RECEIVE

    Operation IDreceive_reply_get_session_info

    Available only on servers:

    Accepts the following message:

    Reply to get session info requestreceive_reply_get_session_info

    The most recently published session info.

    Message IDreceive_reply_get_session_info
    oneOf

    Examples

  • RECEIVE e2m/powermeter

    Operation IDreceive_powermeter

    Available only on servers:

    Accepts the following message:

    Receive powermeterreceive_powermeter

    Powermeter measured dataset

    Message IDreceive_powermeter
    object

    Measured dataset (AC or DC)

    Examples

  • REQUEST m2e/powermeter/get

    Request the most recently published (latched) powermeter. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_powermeter

    Available only on servers:

    Accepts the following message:

    Request current powermetersend_request_get_powermeter

    Request the most recently published (latched) powermeter.

    Message IDsend_request_get_powermeter
    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

  • RECEIVE

    Operation IDreceive_reply_get_powermeter

    Available only on servers:

    Accepts the following message:

    Reply to get powermeter requestreceive_reply_get_powermeter

    The most recently published powermeter.

    Message IDreceive_reply_get_powermeter
    oneOf

    Examples

  • RECEIVE e2m/powermeter_public_key_ocmf

    Operation IDreceive_powermeter_public_key_ocmf

    Available only on servers:

    Accepts the following message:

    Receive powermeter public key OCMFreceive_powermeter_public_key_ocmf

    Powermeter public key OCMF

    Message IDreceive_powermeter_public_key_ocmf
    Payload
    string

    The public key as string used to sign the OCMF data

    Examples

  • REQUEST m2e/powermeter_public_key_ocmf/get

    Request the most recently published (latched) powermeter public key ocmf. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_powermeter_public_key_ocmf

    Available only on servers:

    Accepts the following message:

    Request current powermeter public key ocmfsend_request_get_powermeter_public_key_ocmf

    Request the most recently published (latched) powermeter public key ocmf.

    Message IDsend_request_get_powermeter_public_key_ocmf
    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

  • RECEIVE

    Operation IDreceive_reply_get_powermeter_public_key_ocmf

    Available only on servers:

    Accepts the following message:

    Reply to get powermeter public key ocmf requestreceive_reply_get_powermeter_public_key_ocmf

    The most recently published powermeter public key ocmf.

    Message IDreceive_reply_get_powermeter_public_key_ocmf
    oneOf

    Examples

  • RECEIVE e2m/evse_id

    Operation IDreceive_evse_id

    Available only on servers:

    Accepts the following message:

    Receive EVSE IDreceive_evse_id

    EVSE ID

    Message IDreceive_evse_id
    Payload
    string

    EVSE ID including the connector number, e.g. DEPNXE123456*1

    Examples

  • REQUEST m2e/evse_id/get

    Request the most recently published (latched) EVSE ID. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_evse_id

    Available only on servers:

    Accepts the following message:

    Request current EVSE IDsend_request_get_evse_id

    Request the most recently published (latched) EVSE ID.

    Message IDsend_request_get_evse_id
    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

  • RECEIVE

    Operation IDreceive_reply_get_evse_id

    Available only on servers:

    Accepts the following message:

    Reply to get EVSE ID requestreceive_reply_get_evse_id

    The most recently published EVSE ID.

    Message IDreceive_reply_get_evse_id
    oneOf

    Examples

  • RECEIVE e2m/hw_capabilities

    Operation IDreceive_hw_capabilities

    Available only on servers:

    Accepts the following message:

    Receive hardware capabilities and limitsreceive_hw_capabilities

    Hardware capabilities

    Message IDreceive_hw_capabilities
    object

    Hardware capabilities / limits

    Examples

  • REQUEST m2e/hw_capabilities/get

    Request the most recently published (latched) hw capabilities. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_hw_capabilities

    Available only on servers:

    Accepts the following message:

    Request current hw capabilitiessend_request_get_hw_capabilities

    Request the most recently published (latched) hw capabilities.

    Message IDsend_request_get_hw_capabilities
    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

  • RECEIVE

    Operation IDreceive_reply_get_hw_capabilities

    Available only on servers:

    Accepts the following message:

    Reply to get hw capabilities requestreceive_reply_get_hw_capabilities

    The most recently published hw capabilities.

    Message IDreceive_reply_get_hw_capabilities
    oneOf

    Examples

  • RECEIVE e2m/enforced_limits

    Operation IDreceive_enforced_limits

    Available only on servers:

    Accepts the following message:

    Receive enforced limitsreceive_enforced_limits

    Enforced limits for this node (coming from the EnergyManager)

    Message IDreceive_enforced_limits
    object

    Enforce Limits data type

    Examples

  • REQUEST m2e/enforced_limits/get

    Request the most recently published (latched) enforced limits. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_enforced_limits

    Available only on servers:

    Accepts the following message:

    Request current enforced limitssend_request_get_enforced_limits

    Request the most recently published (latched) enforced limits.

    Message IDsend_request_get_enforced_limits
    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

  • RECEIVE

    Operation IDreceive_reply_get_enforced_limits

    Available only on servers:

    Accepts the following message:

    Reply to get enforced limits requestreceive_reply_get_enforced_limits

    The most recently published enforced limits.

    Message IDreceive_reply_get_enforced_limits
    oneOf

    Examples

  • RECEIVE e2m/selected_protocol

    Operation IDreceive_selected_protocol

    Available only on servers:

    Accepts the following message:

    Receive selected protocol for charging for informative purposesreceive_selected_protocol

    EVSE ID

    Message IDreceive_selected_protocol
    Payload
    string

    The selected protocol for charging

    Examples

  • REQUEST m2e/selected_protocol/get

    Request the most recently published (latched) selected protocol. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_selected_protocol

    Available only on servers:

    Accepts the following message:

    Request current selected protocolsend_request_get_selected_protocol

    Request the most recently published (latched) selected protocol.

    Message IDsend_request_get_selected_protocol
    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

  • RECEIVE

    Operation IDreceive_reply_get_selected_protocol

    Available only on servers:

    Accepts the following message:

    Reply to get selected protocol requestreceive_reply_get_selected_protocol

    The most recently published selected protocol.

    Message IDreceive_reply_get_selected_protocol
    oneOf

    Examples

  • RECEIVE e2m/supported_energy_transfer_modes

    Operation IDreceive_supported_energy_transfer_modes

    Available only on servers:

    Accepts the following message:

    Receive supported energy transfer modesreceive_supported_energy_transfer_modes

    The list of supported energy transfers e.g. AC mono/tri, DC, DC_BPT, etc.

    Message IDreceive_supported_energy_transfer_modes
    array<string>
    non-empty

    List of supported energy transfers e.g. AC mono/tri, DC, DC_BPT, etc.

    Examples

  • REQUEST m2e/supported_energy_transfer_modes/get

    Request the most recently published (latched) supported energy transfer modes. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_supported_energy_transfer_modes

    Available only on servers:

    Accepts the following message:

    Request current supported energy transfer modessend_request_get_supported_energy_transfer_modes

    Request the most recently published (latched) supported energy transfer modes.

    Message IDsend_request_get_supported_energy_transfer_modes
    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

  • RECEIVE

    Operation IDreceive_reply_get_supported_energy_transfer_modes

    Available only on servers:

    Accepts the following message:

    Reply to get supported energy transfer modes requestreceive_reply_get_supported_energy_transfer_modes

    The most recently published supported energy transfer modes.

    Message IDreceive_reply_get_supported_energy_transfer_modes
    oneOf

    Examples

  • RECEIVE e2m/ac_nr_of_phases_available

    Operation IDreceive_ac_nr_of_phases_available

    Available only on servers:

    Accepts the following message:

    Receive Instantaneous phase count available to carreceive_ac_nr_of_phases_available

    Number of phases for AC

    Message IDreceive_ac_nr_of_phases_available
    Payload
    integer
    [ 1 .. 3 ]

    Number of phases

    Examples

  • REQUEST m2e/ac_nr_of_phases_available/get

    Request the most recently published (latched) ac nr of phases available. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_ac_nr_of_phases_available

    Available only on servers:

    Accepts the following message:

    Request current ac nr of phases availablesend_request_get_ac_nr_of_phases_available

    Request the most recently published (latched) ac nr of phases available.

    Message IDsend_request_get_ac_nr_of_phases_available
    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

  • RECEIVE

    Operation IDreceive_reply_get_ac_nr_of_phases_available

    Available only on servers:

    Accepts the following message:

    Reply to get ac nr of phases available requestreceive_reply_get_ac_nr_of_phases_available

    The most recently published ac nr of phases available.

    Message IDreceive_reply_get_ac_nr_of_phases_available
    oneOf

    Examples

  • RECEIVE e2m/ac_pp_ampacity

    Operation IDreceive_ac_pp_ampacity

    Available only on servers:

    Accepts the following message:

    Receive current carrying capacity of the connected cable in ampere for AC chargingreceive_ac_pp_ampacity

    Current carrying capacity of the connected cable in ampere for AC charging with a socket. Publish whenever it changes. This has no meaning for DC or AC charging with a fixed attached cable, it does not need to be implemented and the returned value is not used in those cases.

    Message IDreceive_ac_pp_ampacity
    object

    Current capability (ampacity) of the cable

    Examples

  • REQUEST m2e/ac_pp_ampacity/get

    Request the most recently published (latched) ac pp ampacity. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_ac_pp_ampacity

    Available only on servers:

    Accepts the following message:

    Request current ac pp ampacitysend_request_get_ac_pp_ampacity

    Request the most recently published (latched) ac pp ampacity.

    Message IDsend_request_get_ac_pp_ampacity
    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

  • RECEIVE

    Operation IDreceive_reply_get_ac_pp_ampacity

    Available only on servers:

    Accepts the following message:

    Reply to get ac pp ampacity requestreceive_reply_get_ac_pp_ampacity

    The most recently published ac pp ampacity.

    Message IDreceive_reply_get_ac_pp_ampacity
    oneOf

    Examples

  • RECEIVE e2m/isolation_measurement

    Operation IDreceive_isolation_measurement

    Available only on servers:

    Accepts the following message:

    Receive isolation monitoring measurement resultsreceive_isolation_measurement

    Receive isolation monitoring measurement results

    Message IDreceive_isolation_measurement
    object

    Results of an isolation measurement

    Examples

  • REQUEST m2e/isolation_measurement/get

    Request the most recently published (latched) isolation measurement. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_isolation_measurement

    Available only on servers:

    Accepts the following message:

    Request current isolation measurementsend_request_get_isolation_measurement

    Request the most recently published (latched) isolation measurement.

    Message IDsend_request_get_isolation_measurement
    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

  • RECEIVE

    Operation IDreceive_reply_get_isolation_measurement

    Available only on servers:

    Accepts the following message:

    Reply to get isolation measurement requestreceive_reply_get_isolation_measurement

    The most recently published isolation measurement.

    Message IDreceive_reply_get_isolation_measurement
    oneOf

    Examples

  • RECEIVE e2m/dc_voltage_current

    Operation IDreceive_dc_voltage_current

    Available only on servers:

    Accepts the following message:

    Receive Voltage/Current at the input/outputreceive_dc_voltage_current

    Receive Voltage/Current at the input/output

    Message IDreceive_dc_voltage_current
    object

    Examples

  • REQUEST m2e/dc_voltage_current/get

    Request the most recently published (latched) dc voltage current. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_dc_voltage_current

    Available only on servers:

    Accepts the following message:

    Request current dc voltage currentsend_request_get_dc_voltage_current

    Request the most recently published (latched) dc voltage current.

    Message IDsend_request_get_dc_voltage_current
    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

  • RECEIVE

    Operation IDreceive_reply_get_dc_voltage_current

    Available only on servers:

    Accepts the following message:

    Reply to get dc voltage current requestreceive_reply_get_dc_voltage_current

    The most recently published dc voltage current.

    Message IDreceive_reply_get_dc_voltage_current
    oneOf

    Examples

  • RECEIVE e2m/dc_mode

    Operation IDreceive_dc_mode

    Available only on servers:

    Accepts the following message:

    Receive the current modereceive_dc_mode

    Receive the current mode of the DC power supply

    Message IDreceive_dc_mode
    Payload
    string

    Mode of the DC power supply

    • Off: Power Supply switched off
    • Export: Charge the vehicle
    • Import: V2G etc
    • Fault: Power supply is in error state
      Allowed values:
    • "Off"
    • "Export"
    • "Import"
    • "Fault"

    Examples

  • REQUEST m2e/dc_mode/get

    Request the most recently published (latched) dc mode. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_dc_mode

    Available only on servers:

    Accepts the following message:

    Request current dc modesend_request_get_dc_mode

    Request the most recently published (latched) dc mode.

    Message IDsend_request_get_dc_mode
    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

  • RECEIVE

    Operation IDreceive_reply_get_dc_mode

    Available only on servers:

    Accepts the following message:

    Reply to get dc mode requestreceive_reply_get_dc_mode

    The most recently published dc mode.

    Message IDreceive_reply_get_dc_mode
    oneOf

    Examples

  • RECEIVE e2m/dc_capabilities

    Operation IDreceive_dc_capabilities

    Available only on servers:

    Accepts the following message:

    Receive the capabilities of the DC power supplyreceive_dc_capabilities

    Receive the capabilities of the DC power supply

    Message IDreceive_dc_capabilities
    object

    Examples

  • REQUEST m2e/dc_capabilities/get

    Request the most recently published (latched) dc capabilities. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_dc_capabilities

    Available only on servers:

    Accepts the following message:

    Request current dc capabilitiessend_request_get_dc_capabilities

    Request the most recently published (latched) dc capabilities.

    Message IDsend_request_get_dc_capabilities
    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

  • RECEIVE

    Operation IDreceive_reply_get_dc_capabilities

    Available only on servers:

    Accepts the following message:

    Reply to get dc capabilities requestreceive_reply_get_dc_capabilities

    The most recently published dc capabilities.

    Message IDreceive_reply_get_dc_capabilities
    oneOf

    Examples

  • SEND m2e/random_delay_enable

    Operation IDsend_random_delay_enable

    Available only on servers:

    Accepts the following message:

    Send random delay enablesend_random_delay_enable

    Call to enable the random delay feature

    Message IDsend_random_delay_enable

    Examples

  • SEND m2e/random_delay_disable

    Operation IDsend_random_delay_disable

    Available only on servers:

    Accepts the following message:

    Send random delay disablesend_random_delay_disable

    Call to disable the random delay feature

    Message IDsend_random_delay_disable

    Examples

  • SEND m2e/random_delay_cancel

    Operation IDsend_random_delay_cancel

    Available only on servers:

    Accepts the following message:

    Send random delay cancelsend_random_delay_enable

    Cancels a running random delay. The effect is the same as if the time expired just now.

    Message IDsend_random_delay_enable

    Examples

  • SEND m2e/random_delay_set_duration_s

    Operation IDsend_random_delay_set_duration_s

    Available only on servers:

    Accepts the following message:

    Send random delay set durationsend_random_delay_set_duration_s

    Set the maximum duration of the random delay. Default is 600 seconds.

    Message IDsend_random_delay_set_duration_s
    Payload
    integer

    Maximum duration in seconds

    Examples

  • RECEIVE e2m/random_delay_countdown

    Operation IDreceive_random_delay_countdown

    Available only on servers:

    Accepts the following message:

    Countdown of the currently running random delayreceive_random_delay_countdown

    Random delay countdown

    Message IDreceive_random_delay_countdown
    object

    Count down object

    Examples

  • REQUEST m2e/random_delay_countdown/get

    Request the most recently published (latched) random delay countdown. The reply will be sent to the replyTo address specified in the message headers. If no latched value is available yet, a null payload will be sent.

    Operation IDsend_request_get_random_delay_countdown

    Available only on servers:

    Accepts the following message:

    Request current random delay countdownsend_request_get_random_delay_countdown

    Request the most recently published (latched) random delay countdown.

    Message IDsend_request_get_random_delay_countdown
    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

  • RECEIVE

    Operation IDreceive_reply_get_random_delay_countdown

    Available only on servers:

    Accepts the following message:

    Reply to get random delay countdown requestreceive_reply_get_random_delay_countdown

    The most recently published random delay countdown.

    Message IDreceive_reply_get_random_delay_countdown
    oneOf

    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 to get EVSEsend_request_get_evse

    Request to get EVSE.

    Message IDsend_request_get_evse
    object
  • #2Reply to request to get EVSEreceive_reply_get_evse

    Reply to the request to get the EVSE.

    Message IDreceive_reply_get_evse
    object

    Type that defines properties of an EVSE including its connectors

  • #3Request to enable or disable the EVSEsend_request_enable_disable

    Enables or disables the evse. Turns off PWM with error F. Charging is only possible if an EVSE is enabled.

    Message IDsend_request_enable_disable
    object
  • #4Reply to request to enable or disable the EVSEreceive_reply_enable_disable

    Reply to the request to enable or disable the EVSE.

    Message IDreceive_reply_enable_disable
    Payload
    boolean

    Returns true if evse is enabled after the command, false if it is disabled. This may not be the same value as the request, since there may be a higher priority request from another source that is actually deciding whether it is enabled or disabled.

  • #5Request pause chargingsend_request_pause_charging

    Request to pause charging.

    Message IDsend_request_pause_charging
    object
  • #6Reply to pause charging requestreceive_reply_pause_charging

    Reply to the request to pause charging.

    Message IDreceive_reply_pause_charging
    Payload
    boolean

    Reply to pause charging request. 'true' on success

  • #7Request resume chargingsend_request_resume_charging

    Request to resume charging.

    Message IDsend_request_resume_charging
    object
  • #8Reply to resume charging requestreceive_reply_resume_charging

    Reply to the request to resume charging.

    Message IDreceive_reply_resume_charging
    Payload
    boolean

    Reply to resume charging request. 'true' on success, false otherwise (e.g. resuming a car pause won't work)

  • #9Request stop transactionsend_request_stop_transaction

    Request to stop the current transaction.

    Message IDsend_request_stop_transaction
    object
  • #10Reply to stop transaction requestreceive_reply_stop_transaction

    Reply to the request to stop the current transaction.

    Message IDreceive_reply_stop_transaction
    Payload
    boolean

    Reply to stop transaction request. 'true' on success

  • #11Request force unlocksend_request_force_unlock

    Request to force unlock.

    Message IDsend_request_force_unlock
    object
  • #12Reply to force unlock requestreceive_reply_force_unlock

    Forces connector to unlock connector now. During normal operation, connector will be locked/unlocked in the correct sequence.Do not use this function except if explicitly requested by e.g. management cloud.

    Message IDreceive_reply_force_unlock
    Payload
    boolean

    Returns true if unlocking sequence was successfully executed

  • #13Receive session eventreceive_session_event

    Emits all events related to sessions

    Message IDreceive_session_event
    object

    Emits all events related to sessions

  • #14Request current session eventsend_request_get_session_event

    Request the most recently published (latched) session event.

    Message IDsend_request_get_session_event
    object
  • #15Reply to get session event requestreceive_reply_get_session_event

    The most recently published session event.

    Message IDreceive_reply_get_session_event
    oneOf
  • #16Receive HLC session failed eventreceive_hlc_session_failed

    Emits if a HLC session failed

    Message IDreceive_hlc_session_failed
    object

    Published on the hlc_session_failed variable whenever an HLC session failure occurs. Can fire multiple times per EVerest session (e.g. on retries). Use uuid to correlate with session_event.

  • #17Request current hlc session failedsend_request_get_hlc_session_failed

    Request the most recently published (latched) hlc session failed.

    Message IDsend_request_get_hlc_session_failed
    object
  • #18Reply to get hlc session failed requestreceive_reply_get_hlc_session_failed

    The most recently published hlc session failed.

    Message IDreceive_reply_get_hlc_session_failed
    oneOf
  • #19Receive details about EVreceive_ev_info

    More details about the EV if available.

    Message IDreceive_ev_info
    object

    Information about the connected EV if available

  • #20Request current ev infosend_request_get_ev_info

    Request the most recently published (latched) ev info.

    Message IDsend_request_get_ev_info
    object
  • #21Reply to get ev info requestreceive_reply_get_ev_info

    The most recently published ev info.

    Message IDreceive_reply_get_ev_info
    oneOf
  • #22Receive session and transaction informationreceive_session_info

    Information about the current session and transaction. During a session, data is published with a frequency of ~1Hz. If no session is active, data is published on change. A session starts when the first user interaction occurs, e.g. plug in of an EV or authorization was provided. A session ends when the EV is unplugged or the authorization has timed out. A transaction starts if an EV is plugged in and the user is authorized. A transaction ends when the EV is unplugged or the user is not authorized anymore.

    Message IDreceive_session_info
    object

    Context for Session information

  • #23Request current session infosend_request_get_session_info

    Request the most recently published (latched) session info.

    Message IDsend_request_get_session_info
    object
  • #24Reply to get session info requestreceive_reply_get_session_info

    The most recently published session info.

    Message IDreceive_reply_get_session_info
    oneOf
  • #25Receive powermeterreceive_powermeter

    Powermeter measured dataset

    Message IDreceive_powermeter
    object

    Measured dataset (AC or DC)

  • #26Request current powermetersend_request_get_powermeter

    Request the most recently published (latched) powermeter.

    Message IDsend_request_get_powermeter
    object
  • #27Reply to get powermeter requestreceive_reply_get_powermeter

    The most recently published powermeter.

    Message IDreceive_reply_get_powermeter
    oneOf
  • #28Receive powermeter public key OCMFreceive_powermeter_public_key_ocmf

    Powermeter public key OCMF

    Message IDreceive_powermeter_public_key_ocmf
    Payload
    string

    The public key as string used to sign the OCMF data

  • #29Request current powermeter public key ocmfsend_request_get_powermeter_public_key_ocmf

    Request the most recently published (latched) powermeter public key ocmf.

    Message IDsend_request_get_powermeter_public_key_ocmf
    object
  • #30Reply to get powermeter public key ocmf requestreceive_reply_get_powermeter_public_key_ocmf

    The most recently published powermeter public key ocmf.

    Message IDreceive_reply_get_powermeter_public_key_ocmf
    oneOf
  • #31Receive EVSE IDreceive_evse_id

    EVSE ID

    Message IDreceive_evse_id
    Payload
    string

    EVSE ID including the connector number, e.g. DEPNXE123456*1

  • #32Request current EVSE IDsend_request_get_evse_id

    Request the most recently published (latched) EVSE ID.

    Message IDsend_request_get_evse_id
    object
  • #33Reply to get EVSE ID requestreceive_reply_get_evse_id

    The most recently published EVSE ID.

    Message IDreceive_reply_get_evse_id
    oneOf
  • #34Receive hardware capabilities and limitsreceive_hw_capabilities

    Hardware capabilities

    Message IDreceive_hw_capabilities
    object

    Hardware capabilities / limits

  • #35Request current hw capabilitiessend_request_get_hw_capabilities

    Request the most recently published (latched) hw capabilities.

    Message IDsend_request_get_hw_capabilities
    object
  • #36Reply to get hw capabilities requestreceive_reply_get_hw_capabilities

    The most recently published hw capabilities.

    Message IDreceive_reply_get_hw_capabilities
    oneOf
  • #37Receive enforced limitsreceive_enforced_limits

    Enforced limits for this node (coming from the EnergyManager)

    Message IDreceive_enforced_limits
    object

    Enforce Limits data type

  • #38Request current enforced limitssend_request_get_enforced_limits

    Request the most recently published (latched) enforced limits.

    Message IDsend_request_get_enforced_limits
    object
  • #39Reply to get enforced limits requestreceive_reply_get_enforced_limits

    The most recently published enforced limits.

    Message IDreceive_reply_get_enforced_limits
    oneOf
  • #40Receive selected protocol for charging for informative purposesreceive_selected_protocol

    EVSE ID

    Message IDreceive_selected_protocol
    Payload
    string

    The selected protocol for charging

  • #41Request current selected protocolsend_request_get_selected_protocol

    Request the most recently published (latched) selected protocol.

    Message IDsend_request_get_selected_protocol
    object
  • #42Reply to get selected protocol requestreceive_reply_get_selected_protocol

    The most recently published selected protocol.

    Message IDreceive_reply_get_selected_protocol
    oneOf
  • #43Receive supported energy transfer modesreceive_supported_energy_transfer_modes

    The list of supported energy transfers e.g. AC mono/tri, DC, DC_BPT, etc.

    Message IDreceive_supported_energy_transfer_modes
    array<string>
    non-empty

    List of supported energy transfers e.g. AC mono/tri, DC, DC_BPT, etc.

  • #44Request current supported energy transfer modessend_request_get_supported_energy_transfer_modes

    Request the most recently published (latched) supported energy transfer modes.

    Message IDsend_request_get_supported_energy_transfer_modes
    object
  • #45Reply to get supported energy transfer modes requestreceive_reply_get_supported_energy_transfer_modes

    The most recently published supported energy transfer modes.

    Message IDreceive_reply_get_supported_energy_transfer_modes
    oneOf
  • #46Receive Instantaneous phase count available to carreceive_ac_nr_of_phases_available

    Number of phases for AC

    Message IDreceive_ac_nr_of_phases_available
    Payload
    integer
    [ 1 .. 3 ]

    Number of phases

  • #47Request current ac nr of phases availablesend_request_get_ac_nr_of_phases_available

    Request the most recently published (latched) ac nr of phases available.

    Message IDsend_request_get_ac_nr_of_phases_available
    object
  • #48Reply to get ac nr of phases available requestreceive_reply_get_ac_nr_of_phases_available

    The most recently published ac nr of phases available.

    Message IDreceive_reply_get_ac_nr_of_phases_available
    oneOf
  • #49Receive current carrying capacity of the connected cable in ampere for AC chargingreceive_ac_pp_ampacity

    Current carrying capacity of the connected cable in ampere for AC charging with a socket. Publish whenever it changes. This has no meaning for DC or AC charging with a fixed attached cable, it does not need to be implemented and the returned value is not used in those cases.

    Message IDreceive_ac_pp_ampacity
    object

    Current capability (ampacity) of the cable

  • #50Request current ac pp ampacitysend_request_get_ac_pp_ampacity

    Request the most recently published (latched) ac pp ampacity.

    Message IDsend_request_get_ac_pp_ampacity
    object
  • #51Reply to get ac pp ampacity requestreceive_reply_get_ac_pp_ampacity

    The most recently published ac pp ampacity.

    Message IDreceive_reply_get_ac_pp_ampacity
    oneOf
  • #55Receive isolation monitoring measurement resultsreceive_isolation_measurement

    Receive isolation monitoring measurement results

    Message IDreceive_isolation_measurement
    object

    Results of an isolation measurement

  • #56Request current isolation measurementsend_request_get_isolation_measurement

    Request the most recently published (latched) isolation measurement.

    Message IDsend_request_get_isolation_measurement
    object
  • #57Reply to get isolation measurement requestreceive_reply_get_isolation_measurement

    The most recently published isolation measurement.

    Message IDreceive_reply_get_isolation_measurement
    oneOf
  • #58Receive Voltage/Current at the input/outputreceive_dc_voltage_current

    Receive Voltage/Current at the input/output

    Message IDreceive_dc_voltage_current
    object
  • #59Request current dc voltage currentsend_request_get_dc_voltage_current

    Request the most recently published (latched) dc voltage current.

    Message IDsend_request_get_dc_voltage_current
    object
  • #60Reply to get dc voltage current requestreceive_reply_get_dc_voltage_current

    The most recently published dc voltage current.

    Message IDreceive_reply_get_dc_voltage_current
    oneOf
  • #61Receive the current modereceive_dc_mode

    Receive the current mode of the DC power supply

    Message IDreceive_dc_mode
    Payload
    string

    Mode of the DC power supply

    • Off: Power Supply switched off
    • Export: Charge the vehicle
    • Import: V2G etc
    • Fault: Power supply is in error state
      Allowed values:
    • "Off"
    • "Export"
    • "Import"
    • "Fault"
  • #62Request current dc modesend_request_get_dc_mode

    Request the most recently published (latched) dc mode.

    Message IDsend_request_get_dc_mode
    object
  • #63Reply to get dc mode requestreceive_reply_get_dc_mode

    The most recently published dc mode.

    Message IDreceive_reply_get_dc_mode
    oneOf
  • #64Receive the capabilities of the DC power supplyreceive_dc_capabilities

    Receive the capabilities of the DC power supply

    Message IDreceive_dc_capabilities
    object
  • #65Request current dc capabilitiessend_request_get_dc_capabilities

    Request the most recently published (latched) dc capabilities.

    Message IDsend_request_get_dc_capabilities
    object
  • #66Reply to get dc capabilities requestreceive_reply_get_dc_capabilities

    The most recently published dc capabilities.

    Message IDreceive_reply_get_dc_capabilities
    oneOf
  • #67Send random delay enablesend_random_delay_enable

    Call to enable the random delay feature

    Message IDsend_random_delay_enable
  • #68Send random delay disablesend_random_delay_disable

    Call to disable the random delay feature

    Message IDsend_random_delay_disable
  • #69Send random delay cancelsend_random_delay_cancel

    Cancels a running random delay. The effect is the same as if the time expired just now.

    Message IDsend_random_delay_cancel
  • #70Send random delay set durationsend_random_delay_set_duration_s

    Set the maximum duration of the random delay. Default is 600 seconds.

    Message IDsend_random_delay_set_duration_s
    Payload
    integer

    Maximum duration in seconds

  • #71Countdown of the currently running random delayreceive_random_delay_countdown

    Random delay countdown

    Message IDreceive_random_delay_countdown
    object

    Count down object

  • #72Request current random delay countdownsend_request_get_random_delay_countdown

    Request the most recently published (latched) random delay countdown.

    Message IDsend_request_get_random_delay_countdown
    object
  • #73Reply to get random delay countdown requestreceive_reply_get_random_delay_countdown

    The most recently published random delay countdown.

    Message IDreceive_reply_get_random_delay_countdown
    oneOf
  • #74Receive 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

  • #75Send 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

    Context for authorization event (Authorized or Deauthorized)

  • EvseStateEnum
    string

    State of the EVSE:

    • Unknown: Initial state when state is not known
    • Unplugged: No EV is connected
    • Disabled: EVSE is disabled on not available for energy transfer
    • Preparing: First user interaction occured, e.g. plug in of EV or authorization has been received
    • AuthRequired: EV is plugged in and EVSE is waiting for authorization
    • ChargingPausedEV: Session is paused by EV
    • ChargingPausedEVSE: Session is paused by EVSE
    • Charging: EV is charging
    • AuthTimeout: EV has been plugged in but no authorization has been provided. A replug is required.
    • Finished: Transaction is finished
    • FinishedEVSE: Stop of transaction was initiated by EVSE e.g. by user request
    • FinishedEV: Stopping of transaction was initiated by EV
      Allowed values:
    • "Unknown"
    • "Unplugged"
    • "Disabled"
    • "Preparing"
    • "Reserved"
    • "AuthRequired"
    • "ChargingPausedEV"
    • "ChargingPausedEVSE"
    • "Charging"
    • "AuthTimeout"
    • "Finished"
    • "FinishedEVSE"
    • "FinishedEV"
  • object

    Context for Session information

  • HlcSessionFailedReasonEnum
    string

    Reason for a higher-level-communication (HLC) session failure event. Published via HlcSessionFailed whenever HLC session encounters a failure.

    • ProtocolNegotiationFailed: No common communication protocol or version could be negotiated. Applies to protocols with a version handshake phase.
    • AuthorizationFailed: The authorization phase did not succeed and the EV terminated the session. This covers both explicit rejection (e.g. failed PnC contract or certificate verification) and authorization timeout (the EVSE did not respond within the timeout of the EV).
    • ChargingParametersNotAccepted: The EV terminated during parameter negotiation, indicating it could not accept the offered energy transfer parameters (power levels, voltage range, schedule, etc.).
    • EnergyTransferSetupFailed: The setup phase immediately before energy transfer began (e.g. power delivery request, pre-charge coordination) failed or was rejected by the EV before any energy was transferred.
    • ChargingInterrupted: The EV stopped energy transfer unexpectedly during active charging without completing a normal stop sequence.
    • FailedTLSHandshake: The TLS handshake between EV and EVSE failed before any V2G message exchange could take place, preventing the session from starting.
    • UnexpectedSessionEnd: The communication session ended unexpectedly at a phase not covered by the above reasons, or without completing a normal termination sequence. Catch-all for unclassified EV-side terminations.
      Allowed values:
    • "ProtocolNegotiationFailed"
    • "AuthorizationFailed"
    • "ChargingParametersNotAccepted"
    • "EnergyTransferSetupFailed"
    • "ChargingInterrupted"
    • "FailedTLSHandshake"
    • "UnexpectedSessionEnd"
  • object

    Published on the hlc_session_failed variable whenever an HLC session failure occurs. Can fire multiple times per EVerest session (e.g. on retries). Use uuid to correlate with session_event.

  • object

    Context for ChargingStateChanged event

  • object

    Type for a connector which is an independently operated and managed electrical outlet of an EVSE. It corresponds to a single physical connector

  • ConnectorTypeEnum
    string

    Type of a physical connector

    • cCCS1: Combined Charging System 1 a.k.a. Combo 1
    • cCCS2: Combined Charging System 2 a.k.a. Combo 2
    • cG105: JARI G105-1993 a.k.a. CHAdeMO
    • cMCS: Megawatt Charging System (captive cabled) (IEC 63379 Configuration HH)
    • cTesla: Tesla Connector
    • cType1: IEC62196-2 Type 1 connector a.k.a. J1772
    • cType2: IEC62196-2 Type 2 connector a.k.a. Mennekes connector
    • s309_1P_16A: 16A 1 phase IEC60309 socket
    • s309_1P_32A: 32A 1 phase IEC60309 socket
    • s309_3P_16A: 16A 3 phase IEC60309 socket
    • s309_3P_32A: 32A 3 phase IEC60309 socket
    • sBS1361: UK domestic socket a.k.a. 13Amp
    • sCEE-7_7: CEE 7/7 16A socket a.k.a Schuko
    • sType2: IEC62196-2 Type 2 socket a.k.a. Mennekes connector
    • sType3: IEC62196-2 Type 2 socket a.k.a. Scame
    • Other1PhMax16A: Other single phase (domestic) sockets not mentioned above, rated at no more than 16A. CEE7/17, AS3112, NEMA 5-15, NEMA 5-20, JISC8303, TIS166, SI 32, CPCS-CCC, SEV1011, etc
    • Other1PhOver16A: Other single phase sockets not mentioned above (over 16A)
    • Other3Ph: Other 3 phase sockets not mentioned above. NEMA14-30, NEMA14-50.
    • Pan: Pantograph connector
    • wInductive: Wireless inductively coupled connection (generic)
    • wResonant: Wireless resonant coupled connection (generic)
    • Undetermined: Yet to be determined (e.g. before plugged in)
    • Unknown: Unknown
      Allowed values:
    • "cCCS1"
    • "cCCS2"
    • "cG105"
    • "cMCS"
    • "cTesla"
    • "cType1"
    • "cType2"
    • "s309_1P_16A"
    • "s309_1P_32A"
    • "s309_3P_16A"
    • "s309_3P_32A"
    • "sBS1361"
    • "sCEE_7_7"
    • "sType2"
    • "sType3"
    • "Other1PhMax16A"
    • "Other1PhOver16A"
    • "Other3Ph"
    • "Pan"
    • "wInductive"
    • "wResonant"
    • "Undetermined"
    • "Unknown"
  • object

    Count down object

  • EnableDisableReply
    boolean

    Returns true if evse is enabled after the command, false if it is disabled. This may not be the same value as the request, since there may be a higher priority request from another source that is actually deciding whether it is enabled or disabled.

  • object

    Arguments for enable_disable

  • object

    Source of a Enable or Disable command/event

  • object

    Enforce Limits data type

  • array<string>
    non-empty

    List of supported energy transfers e.g. AC mono/tri, DC, DC_BPT, etc.

  • object

    Type that defines properties of an EVSE including its connectors

  • EvseId
    string

    EVSE ID including the connector number, e.g. DEPNXE123456*1

  • object

    Information about the connected EV if available

  • ForceUnlockReply
    boolean

    Returns true if unlocking sequence was successfully executed

  • ForceUnlockRequest
    integer

    Specifies the ID of the connector that should be unlocked

  • PauseChargingReply
    boolean

    Reply to pause charging request. 'true' on success

  • RandomDelayDuration
    integer

    Maximum duration in seconds

  • Ready
    boolean

    'true' signals ready

  • ResumeChargingReply
    boolean

    Reply to resume charging request. 'true' on success, false otherwise (e.g. resuming a car pause won't work)

  • SelectedProtocol
    string

    The selected protocol for charging

  • object

    Emits all events related to sessions

  • SessionEventEnum
    string

    Session Event enum

    • Authorized: Signaled when the EVSE is authorized for charging
    • Deauthorized: Signaled when the EVSE is not authorized for charging (anymore)
    • Enabled: Signaled when the EVSE is enabled (e.g. after an enable command)
    • Disabled: Signaled when the EVSE is disabled (e.g. after a disable command)
    • SessionStarted: Signaled when a session has been started. A session has been started either when an EV is plugged in or the user has been authorized to start a transaction (e.g. after an authorize command)
    • AuthRequired: Signaled when an EVSE needs authorization to start a transaction
    • TransactionStarted: Signaled when a transaction has been started. Transaction starts at the point that all conditions for charging are met: EV is connected and user has been authorized
    • PrepareCharging: EVSE started to prepare for charging. DC: CableCheck, PreCharge, PowerDelivery. AC: wait for the car to proceed to state C/D
    • ChargingStarted: DC: CurrentDemand has started. AC: Auth is ok and car requested power (state C/D)
    • ChargingPausedEV: Signaled when charging is paused by the EV
    • ChargingPausedEVSE: Signaled when charging is paused by the EVSE
    • StoppingCharging: EVSE has started to stop the charging process. DC: CurrentDemand has finished, now doing WeldingCheck etc, AC: Wait for car to return to state B or A
    • ChargingFinished: Charging is finished. Essentially the same as TransactionFinished, but emitted for clarity
    • TransactionFinished: Signaled when the transaction finished. Transaction finishes at the point where one of the preconditions for charging irrevocably becomes false: When a user swipes to stop the transaction and the stop is authorized.
    • SessionFinished: Session finishes at the point that the EVSE is available again (no cable plugged)
    • ReservationStart: Signaled when a reservation starts
    • ReservationEnd: Signaled when a reservation ends
    • PluginTimeout: Signaled when an EV has been Plugged in but no authorization is present within specified ConnectionTimeout
    • SwitchingPhases: Signals that 1ph/3ph switching was started on AC charging
    • SessionResumed: Signaled when a session is resumed at startup (e.g. because of previous powerloss)
      Allowed values:
    • "Authorized"
    • "Deauthorized"
    • "Enabled"
    • "Disabled"
    • "SessionStarted"
    • "AuthRequired"
    • "TransactionStarted"
    • "PrepareCharging"
    • "ChargingStarted"
    • "ChargingPausedEV"
    • "ChargingPausedEVSE"
    • "StoppingCharging"
    • "ChargingFinished"
    • "TransactionFinished"
    • "SessionFinished"
    • "ReservationStart"
    • "ReservationEnd"
    • "PluginTimeout"
    • "SwitchingPhases"
    • "SessionResumed"
  • object

    Data for the SessionFinished event

  • object

    Data for the SessionStarted event

  • SlacDlinkReady
    boolean

    Inform higher layers about a change in data link status. Emits true if link was set up and false when the link is shut down.

  • StartSessionReason
    string

    Reason for session start

    • EVConnected: Session was started because an EV was plugged in
    • Authorized: Session was started because a valid authorization was presented and the EVSE is authorized to start a transaction immediately when an EV is plugged in
      Allowed values:
    • "EVConnected"
    • "Authorized"
  • StopTransactionReason
    string

    Reason for stopping transaction

    • EmergencyStop: Emergency stop button was used
    • EVDisconnected: Disconnecting of cable, vehicle moved away from inductive charge unit
    • HardReset: A hard reset command was received previously
    • Local: Stopped locally on request of the user at the Charge Point. This is a regular termination of a transaction. Examples: presenting an RFID tag, pressing a button to stop
    • Other: Any other reason
    • PowerLoss: Complete loss of power
    • Reboot: A locally initiated reset/reboot occurred
    • Remote: Stopped remotely on request of the user. This is a regular termination of a transaction. Examples: termination using a smartphone app, exceeding a (non local) prepaid credit
    • SoftReset: A soft reset command was received
    • UnlockCommand: Central System sent an Unlock Connector command
    • DeAuthorized: The transaction was stopped because of the authorization status in a StartTransaction.conf
    • EnergyLimitReached: Maximum energy of charging reached. For example: in a pre-paid charging solution
    • GroundFault: A GroundFault has occurred
    • LocalOutOfCredit: A local credit limit enforced through the Charging Station has been exceeded.
    • MasterPass: The transaction was stopped using a token with a MasterPassGroupId.
    • OvercurrentFault: A larger than intended electric current has occurred
    • PowerQuality: Quality of power too low, e.g. voltage too low/high, phase imbalance, etc.
    • SOCLimitReached: Electric vehicle has reported reaching a locally enforced maximum battery State of Charge (SOC)
    • StoppedByEV: The transaction was stopped by the EV
    • TimeLimitReached: EV charging session reached a locally enforced time limit
    • Timeout: EV not connected within timeout
    • ReqEnergyTransferRejected: OCPP CSMS cannot accept the requested energy transfer type.
      Allowed values:
    • "EmergencyStop"
    • "EVDisconnected"
    • "HardReset"
    • "Local"
    • "Other"
    • "PowerLoss"
    • "Reboot"
    • "Remote"
    • "SoftReset"
    • "UnlockCommand"
    • "DeAuthorized"
    • "EnergyLimitReached"
    • "GroundFault"
    • "LocalOutOfCredit"
    • "MasterPass"
    • "OvercurrentFault"
    • "PowerQuality"
    • "SOCLimitReached"
    • "StoppedByEV"
    • "TimeLimitReached"
    • "Timeout"
    • "ReqEnergyTransferRejected"
  • object

    Request for a stop transaction containing the reason and an optional id tag

  • StopTransactionReply
    boolean

    Reply to stop transaction request. 'true' on success

  • object

    Data for the TransactionStarted event

  • object

    Data for TransactionFinished event

  • 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