We have added support for controlling the operation modes of Huawei batteries.

Check the capabilities object in the battery response to determine which operation modes are supported by the linked battery.

We are excited to announce EU and US support for integrating with Subaru vehicles is now in beta.

To opt-in, please navigate to the enabled-brands section under your Enode client and activate it.

Vehicle linking support has been expanded to include Fiat in North America. Jeep is now available for Beta testing in both North America and Europe.

For detailed information on supported regions and models, refer to Vehicle capabilities.

To enable Jeep support, navigate to the enabled-brands section under your Enode client.

The 1.0.2 release of the iOS SDKs brings improved memory management.

We recommend all users of Link UI v4 to implement the SDKs or upgrade from <1.0 versions.

Get the 1.0.2 iOS SDK from our documentation:

• iOS

The 1.0.1 release of the iOS SDKs brings improved reporting of a result of the Linking process completion.

We recommend all users of Link UI v4 to implement the SDKs or upgrade from <1.0 versions.

Get the 1.0.1 iOS SDK from our documentation:

• iOS

A new state PLUGGED_IN:DISCHARGING has been added to the PowerDeliveryState enum. This state indicates that the vehicle or charger is actively discharging power to the home/grid, causing the battery level to decrease.

We are excited to announce that support for integrating with Schneider Electric chargers using Wiser Home is now in beta.

To opt-in, please navigate to the enabled-brands section under your Enode client.

Users often own multiple energy devices from the same vendor. For example, home energy devices such as solar inverters, batteries, or meters are frequently purchased together as a package, with their API access managed under a single vendor account.

To improve the linking process of different devices under the same account, we have enabled the re-use of vendor authentication across different device categories. Users after the initial linking flow, are able to skip repeating the same step of entering credentials with all subsequent sessions with LinkUI automatically using the previously granted authorization of the vendor account. This reduces friction and enhances the overall user experience.

SMA support is enabled by default. You can disable SMA in the enabled-brands section under your Enode client.

SMA support is enabled by default. You can disable SMA in the enabled-brands section under your Enode client.

These IPs can be used for additional verification or allowlists. More in the Webhooks docs.

Vendor sign-in is now available for BMW and MINI vehicles for a more streamlined authentication flow.

Note that an SDK version of 1.0.2 or higher is required to use this feature in Android. For iOS, the minimum required SDK version is 1.0.0.

The integration currently only enables Information capabilities for these batteries and does not allow controlling of modes. To opt-in, please navigate to the enabled-brands section under your Enode client.

The integration has been stable for several months. Micromatic HVACs can now be linked to all Enode clients without manual activation.

We are excited to announce that we added support for integrating with Garo chargers.

To opt-in, please navigate to the enabled-brands section under your Enode client.

We are excited to announce that we added support for integrating with SolarEdge meters.

To opt-in, please navigate to the enabled-brands section under your Enode client.

We are excited to announce that we added support for integrating with Hyundai Australia vehicles.

We are excited to announce that we added support for integrating with Huawei batteries and meters.

To opt-in, please navigate to the enabled-brands section under your Enode client.

You can now request a linking session with the nl-BE language code to present the LinkUI in Dutch (Belgium). To use this feature, set the language attribute to nl-BE when creating a linking session.

Additionally, interventions will now be available in Dutch (Belgium) as well. Similarly, set the language query parameter to nl-BE when fetching interventions to receive the resolution descriptions in Dutch (Belgium).

We are excited to announce that we added support for integrating with Ohme chargers.

To opt-in, please navigate to the enabled-brands section under your Enode client.

Customers can now pick between MyŠkoda and MyŠkoda Essentials when linking their accounts. We expect Škoda to migrate their vehicles away from MyŠkoda Essentials.

During the creation of a virtual vehicle you can now choose to automatically link it to a user. You can chose to link it to an existing user ID or let Sandbox create a new user ID for you automatically. This will save you time and make it easier to test your integration with Enode.

The configured battery discharge limit is now available under chargeState.dischargeLimit. This value can be used to determine whether the battery will discharge.

User-defined vehicle nicknames are now surfaced in our Vehicle Asset API under information.displayName. These display names are easily recognizable by users and can be used to identify vehicles in your app.

Ford vehicles can now only be linked using the Enode Link SDKs. This is because Ford has a new authentication flow that requires the use of the Vendor sign-in feature in the Link SDKs.

We are excited to announce that we added support for integrating with Netatmo HVACs.

To opt-in, please navigate to the enabled-brands section under your Enode client.

• 2024-05-16: Previously, code generated from our spec by openapi-generator and similar tools would attempt to pass pagination parameters as a single field query param, e.g. ?field={"after": "abc"} or ?field[after]=abc, neither of which are accepted by our API. After removing explode: true, code produced by openapi-generator is now passing pagination params correctly: ?after=abc&pageSize=50.

• 2024-05-16: Ensured that all paginated endpoints correctly document their query parameters.

• 2024-05-21: Inlined nullable timestamps and HourMinute since allOf: [{ $ref }, { description }] was not supported by openapi-generator.

We are excited to announce that we added support for integrating with FoxESS inverters using Fox Cloud.

To opt-in, please navigate to the enabled-brands section under your Enode client.

We are excited to announce that we added support for integrating with Tesla Wall Connector chargers.

To opt-in, please navigate to the enabled-brands section under your Enode client.

The about:blank URI scheme is no longer permitted as a redirect URI for Link UI v4. This change is to prevent errors with respect to Tesla linking.

We are excited to announce that we added support for integrating with Fronius Wattpilot chargers.

We are excited to announce that we added support for integrating with Sol-Ark inverters.

In certain situations our API to stop charging (POST /{assetCategory}/{assetId}/charging) could delay future charging sessions due to flawed state. From now on, Enode will clear any such state when the vehicle is plugged out, ensuring that charging resumes correctly when plugged in.

We are excited to announce US support for Toyota and Lexus.

The 1.0 releases of both SDKs bring several improvements when linking through Enode:

• Rendering of Link UI in fullscreen for a native user experience on mobile devices

For linking and pairing Teslas:

• Pairing flow polished with many UX improvements
• Automatic selection of vehicle during pairing
• Automatic pairing without keycard or other interaction with the vehicle
• Gracefully falling back to manual selection or pairing
• Improved error handling and retry-flows for pairing

For linking Google Nest and Teslas:

• Vendor sign-in for better and faster authentication

We recommend all users of Link UI v4 to implement the SDKs or upgrade from <1.0 versions.

Get the 1.0 SDKs from our documentation:

• iOS
• Android

Charge Actions sent to unplugged chargers and vehicles will now be rejected with a HTTP 400 Bad Request and no Action will be created. Previously, such Actions would be accepted with a HTTP 200 OK and then transitioned to a CANCELLED state when asynchronously processed. Enode doesn't deliver Charge Actions to Vendor APIs when vehicles or charges are unplugged, and therefore, we believe this change better reflects how our platform handles such actions.

With this update, we're taking 15 integrations that previously required an opt-in and are making them available by default. Unless they've been manually disabled in the Developers Dashboard, these brands will be available for linking in LinkUI. We do this periodically when we've determined that these brands are stable and reliable enough to be present in most Link sessions.

• Vehicles: Rivian & Mercedes
• Meters: Enphase & Tesla
• Batteries: Enphase & Tesla
• Chargers: GoE
• Hvacs: Panasonic & Hoymiles
• Inverter: Huawei, Sofar, Solax, Sungrow & Tesla

Note that the Meters and Batteries categories are still in Beta, and may see breaking changes in the future.

We are excited to announce that we added support for integrating with Lexus vehicles.

We are excited to announce Canada support for Hyundai, KIA and Nissan.

We are excited to announce US support for Mitsubishi kumo cloud HVAC models. Additionally, we have expanded our inverter lineup by integrating Fox ESS and SunSynk.

Fox ESS and SunSynk are in beta. To opt-in, please navigate to the enabled-brands section under your Enode client and activate them.

We added beta support for 5 models of XPENG:

• G3i
• G9
• P5
• P7
• P7i

To opt-in, please head to the enabled-brands under your Enode client and activate the vendor.

We have optimized the retry logic for actions, which enables Enode to terminate unsuccesful actions quicker. The exact timings and re-try logic depends on the vendor. Actions will now transition quicker from PENDING to FAILED or CANCELLED while maintaining the same level of confidence.

Fresher data, less aggressive caching

Inverter vendor statistics had a bug where stale data was returned. For example, if energy production for the current day (not yet finished) was requested, the initial value would also be returned for all subsequent requests.

This has been fixed, and real-time data (with in-progress buckets) will now be cached for a maximum of 15 minutes, instead of indefinitely.

Growatt timezone fix

Responses for Growatt inverters had an issue where data was aligned with the wrong timezone, and the data would be shifted by an amount that depended on the startDate parameter of the request. Due to this, we have invalidated all existing cached data for Growatt inverters, so that the correct data will be returned from now on.

Stricter input validation

Additionally, start dates must now start exactly at the beginning of an hour. Previously, it was possible to ask for an hour of data between e.g. 12:30 to 13:30, but this should not have been possible, and the results were unpredictable. Inverters with non-integer timezone offsets are not supported yet.

Copy linkFord now opt-in

Due to reliability issues with the vendor, we have made Ford opt-in. Head to enabled-brands in the settings to switch it on for your clients. Already existing connections are not affected, but to continue linking Ford, opting in is required.

Copy linkFixed consumption rate

HVACs falsely reported consumptionRate as 0 even though it was unavailable on the device. This has now been improved and made more explicit:

• If the data point is unavailable, we report null.
• If the data point is available but the device is idle, we report 0.
• If the data point is available and the device is consuming energy, we report the actualValue.

Customers can now configure header-based authentication on their webhooks. More details can be found in the Webhooks Guide.

The 0.10.0 releases of both SDKs bring several improvements when linking Teslas through Enode:

• fixed a bug when the Tesla 1st party app was on the same device
• improved error handling and reporting
• improved connection handling
• improved and simplified UX in Link UI
• avoid native Bluetooth dialog by selecting the car in the background
• new Vendor sign-in which makes the authentication easier and faster

Furthermore, linking sessions using SDK versions 0.10.0+ also support Google Nest.

Get the new SDKs from our documentation:

• iOS
• Android

Start dates not aligned with midnight (UTC), for example 2023-08-03T22:00:00Z, were shifted to 2023-08-03T00:00:00Z, causing the response to include too many data points. All resolutions were affected by this bug. This has been fixed and the start date is no longer shifted.

Additionally, these endpoints are no longer locked behind a feature flag and are now available to all customers.

Invalid credentials used to cause the automatic deletion of the underlying connected asset(s). From users we have learned that the vast majority of these deletions are involuntary. To address this, and help users to re-gain access to their asset(s), we no longer remove these assets from the system automatically and instead apply an intervention prompting the user to re-link their account.

In the event of invalid credentials or expired oauth authorization token:

• Asset becomes unreachable.
• A user:credentials:invalidated webhook event is sent.
• A Re-link your {asset} to re-enable telemetry intervention gets added and all capabilities become isCapable: false.
• GET /users/{userId} will return an array linkedVendors[].isValid where isValid indicates if credentials are valid.

This change avoids data loss around the asset and users can now be guided through re-linking using the interventions.

New BatteriesAPI Endpoints (Beta):

New MetersAPI Endpoints (Beta):

These new hardware categories are currently in beta. Developers are encouraged to provide feedback and report any issues. Refer to the API referenceAPI for in-depth details and integration steps.

The response contains general information as well as more detailed information about the resolution of the intervention. The resolution description is Markdown formatted and is available in language-localized versions.

Please refer to our updated Intervention guide and API referenceAPI for more detailed information.

Copy linkNew endpoints:

Deprecated endpoints:

New endpoints:

Old firehose webhook is still accessible through the deprecated endpoints as well as the new endpoints. Use GET /webhooks to receive its id to start using the new endpoints.

• Affected endpoints: /users/{userId}/statistics/charging, /statistics/charging, /users/{userId}/statistics/production and /statistics/production.
• Before, for DAY resolution, an end date of 2023-08-03T00:00:00Z was rounded up to 2023-08-04T00:00:00Z.
• Before, for MONTH resolution, an end date of 2023-08-01T00:00:00Z was rounded up to 2023-09-01T00:00:00Z.
• Now, the end date is not rounded up. The same applies for all other resolutions.
• To keep backwards compatibility, the old rounding behavior will still be used if the start time is equal to the end time.

Going forward, we'll publish a separate specification file for each breaking change we release. As a result, each of the specifications will be simpler, as they don't have to include another version's schema. In addition, resource names such as Vehicle_2023_02_01 become just Vehicle. The new specifications are available through our API. To see a specific version, replace the latest argument with a version like 2023-05-01.

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.

• 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.

• 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.

• 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.

• 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.