DataTransfer Support (1.4.4+)

🚧

The VendorId of Easee boxes for all DataTransfer calls is 'no.easee', and all message ids are case insensitive. Our recommendation is that commands are sent in camel case for clarity.
Any call not using 'no.easee' as VendorId, and a MessageId that is listed below will result in a DataTransfer status with the corresponding error code.

OverrideSchedule

This overrides the currently set charger schedule for the ongoing charging session. No additional parameters are allowed and the data field should be empty.

See below for an example OCPP call:

[
  2,
  "f66f316e-e2c1-4f7c-a509-ad4cb0cf1cd2",
  "DataTransfer",
  {
    "vendorId": "no.easee",
    "messageId": "OverrideSchedule"
  }
]

If the call is successfully forwarded to the command queue OCPP will respond with Accepted, if handoff to IoT backend fails the call will be rejected.

ListEaseeSessions

Input

ISO8601 - DateTime "Start"

List charging sessions started after specified timestamp

ISO8601 - DateTime "Stop"

List charging sessions started before specified timestamp

Restrictions

Start and Stop cannot define a timespan longer than 31 days.

Result

Returns the list of charger sessions in an array of session objects. The session objects will be comparable to the object sent in a StartTransaction message, but will also contain a sequence id set by charger firmware. Sequence ids are strictly increasing and defined by the hardware to uniquely identify charging sessions.

Example DataTransfer request payload

{
   "vendorId":"no.easee",
   "messageId":"ListEaseeSessions",
   "data":"{start:\\'2021-03-01T00:00:00.000Z\\',stop:\\'2021-03-08T00:00:00.000Z\\'}"
}

Example DataTransfer response

{
   "status":"Accepted",
   "data":"[{connectorId:1,idTag:\\'AF18EE010486FF3E\\',meterStart:12345,start:\\'2021-03-02T13:22:31.456Z\\',meterStop:13345,stop:\\'2021-03-02T21:16:33.333Z\\',sequenceNumber:32}]"
}

ImportEaseeSessions

Input

ISO8601 - DateTime "Start"

List charging sessions started after specified timestamp

ISO8601 - DateTime "Stop"

List charging sessions started before specified timestamp

Restrictions

Start and Stop cannot define a timespan longer than 31 days.

Result

Returns an empty DataTransfer response if successfull, or a FormationError if the timespan is too large. On a successful response, the CP will immediately start reporting backdated transactions from the given span. These will be reported in a similar manner to offline transactions with times and consumption fetched from the Easee session objects.

❗️

This command is intended for reimporting old data that has been dropped either due to CSMS issues, network problems or any other reason. The operator is in full control of the import, so no duplicate checks are done by the device. All transactions in span are immediately scheduled for retransmission. Always verify sessions to be imported by running the "ListEaseeSessions" command first.

Example DataTransfer request

{
   "vendorId":"no.easee",
   "messageId":"ImportEaseeSessions",
   "data":"{start:\\'2021-03-01T00:00:00.000Z\\',stop:\\'2021-03-08T00:00:00.000Z\\'}"
}

Example DataTransfer response

{
   "status":"Accepted",
   "data":""
}