Version 2023-04-01
Released
A new version with breaking changes to smart charging. This version simplifies considerations further.
| Endpoint | Change description |
|---|---|
GET /vehicles/{vehicleId}/smart-charging-status | isSmartChargeCapable, singleUser, needsSignificantCharge, wontStopExistingChargingSession, hasChargeAboveThreshold and likelyToGenerateSavings considerations have been removed from the consideration object |
GET /vehicles/{vehicleId}/smart-charging-status | Consideration recentlyAtChargingLocation has been renamed to atChargingLocation in the Vehicle Smart Charging StatusAPI API |
GET /vehicles/{vehicleId}/smart-charging-status | A new state, FULLY_CHARGED, has been added to the state enum. FULLY_CHARGED, will replace CONSIDERING when the vehicle does not need to be charged. This can be due to the vehicle having reached its charging limit or the battery being close to 100% charged. The vehicle will transition back into CONSIDERING once we detect that the vehicle has been used and needs to be charged. |
PUT /vehicles/{vehicleId}/smart-charging-policy | The logic for checking if the vehicle is capable of smart charging and if the user is a single user has been moved to the Update Vehicle Smart Charging PolicyAPI API. If the vehicle is not capable of smart charging or the user is not a single user, smart charging will not be turned on, and a 400 Bad Request will be returned. |
Pass 2023-04-01 as your version header to use this new version.