improved
2.0
about 1 month ago by Michaël TÉCOURT
The overall structure of the CSMS API remains, but with some significant changes detailed below. ...
Use of Dreev generated identifiers
API Endpoints and objects now use Dreev internal identifiers, instead of CSMS identifiers.
This change allows clients to use consistent identifiers across all Dreev APIs, including :
- Provisioning
- CSMS
- Charging Statistics
- Rewards
When using CSMS identifiers, fields are explicitely named csmsXxxId.
For example : csmsTransactionId vs transactionId (generated by Dreev).
See CSMS Protocol documentation and API Docs for more details.
Support for Multi-EVSE Charging Stations
- Add Charging Station concept on top of EVSE.
- Support for Multi-EVSE Charging Stations.
- Dreev's platform remains EVSE centric. Each EVSE has a unique identifier generated by Dreev. In this regard the CSMS API differs from OCPP 2+, where EVSEs only have a number relative to their Charging Station.
- The communication (i.e. heartbeats) is handled at the Charging Station level.
- Transactions, measurements and charging state remain at the EVSE level.