Enode Developers
Create accountLog in

Changelog

RSS

Keep track of updates and new API versions. More on versioning here.

  • New Smart charge version 2023-04-01

    Released

    A new version with breaking changes to smart charging. This version simplifies considerations further.

    • The isSmartChargeCapable, singleUser, needsSignificantCharge, wontStopExistingChargingSession, hasChargeAboveThreshold and likelyToGenerateSavings considerations have been removed from the consideration object in the Vehicle Smart Charging StatusAPI API.

      • Renaming consideration recentlyAtChargingLocation to atChargingLocation in the Vehicle Smart Charging StatusAPI API.

      • 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 404 response will be returned.

      • A new state, FULLY_CHARGED, has been introduced. This state 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.

    Pass 2023-04-01 as your version header to use this new version.

  • Made spec more compatible with openapi-generator

    Released

    Removed invalid default property in VehicleFieldParameter

    • Fixed a bug in the OpenAPI spec where the default value of VehicleFieldParameter was located inside items instead of next to it, causing openapitools/openapi-generator to fail. The intended default for fields was ["capabilities", "smartChargingPolicy"]. It's not necessary to specify these fields since they are always returned.

  • Power delivery states and richer action failure reasons

    Released

    This update brings new features to our vehicles and chargers APIs. The new fields will be available across all versions.

    • Introducing chargeState.powerDeliveryState. This field represents the current power delivery state between a vehicle and a charger. For more information, see Get VehicleAPI.

      • Introducing failureReason. This field provides more information about why was a given action not executed successfully. For more information, see Get Charge ActionAPI.

  • Changes to smart charging considerations

    Released

    Changes made to simplify smart charging considering phase.

    • Instead of staying in the considering phase in cases where you should charge right away, we will make a plan to start now. This is particularly important when there are very little savings. The charging behavior will remain the same as before; the only difference is that we are giving users a plan.
      • As a result of this change, wontStopExistingChargingSession and likelyToGenerateSavings are now deprecated will always return true.
      • Locations no longer have to be fresh in order to receive a smart charge plan.

  • Version 2023-03-01

    Released

    The first version with breaking changes. This API version removes deprecated functionality and fields that have accumulated before Enode launched versioning.

    • The fields chargeableId, chargeableType, entityId, and entityType have been replaced with targetId and targetType on the ScheduleAPI endpoints, as well in Control Charging for chargersAPI and for vehiclesAPI.

      • The External Start APIs for VehiclesAPI and ChargersAPI have been renamed to Smart override, which better reflects their intended use.

      • The Set Temperature endpoint for HVACs has been replaced by the Set Permanent HoldAPI and Follow ScheduleAPI endpoints. The latter offer increased control over the underlying hardware, like the ability to change the thermostat's mode.

      • PUT /hvacs/{hvacId} and GET /hvacs/{hvacId} responses no longer contain targetTemperature.

      • The vehicleId request body parameter to Get Charging StatisticsAPI has been replaced with id and type in order to support different types of hardware.

      • The chargeState.isChargingReasons response field on the Vehicle APIAPI has been removed.

      • The information.id response field on the Vehicle APIAPI has been removed. Use information.vin instead.

      • The user:charge-action:updated webhook event has been renamed to user:vendor-action:updated.

    Pass 2023-03-01 as your version header to use this new version.

  • Vendor types are now returned for linked vendors

    Released

    This update brings a small quality of life improvement for re-linking vendors. The update is available across all versions.

    • vendorType is now returned in the response from the MeAPI endpoint. This makes it easier to re-link vendors in a isValid = false state since vendorType is required when calling link endpoint. For more information see MeAPI.

  • Version 2023-02-01

    Released

    The first calendar version for Enode API. No breaking changes have been made. Existing clients are pinned to version 2023-02-01, and will use this version by default if no version header is sent.

    • Version 2023-02-01 is the same as before and has no breaking changes.
      • API endpoints now accept an Enode-Version header. To prepare for future API versions you can optionally start sending Enode-Version=2023-02-01.
      • Note: New clients will be pinned to the latest stable version at the time of creation.

  • New smart charging features

    Released

    This update brings a few new features to our smart charging APIs. The updates will be available across all versions.

    • Altered the hasChargeAboveThreshold smart charge consideration such that vehicles stop charging ScheduleAPI immediately, regardless of battery level. Previously the smart charging algorithm would wait until a vehicle reached 20% before issuing a stop command.