A core component of EV Charger Pairing is the EV System, a logical system that augments the Vehicle API and is:

• Created once as a vehicle and charger are linked to the same user, immediately unlocking vehicle capabilities (like startCharging for incapable vehicles).
• Activated when the two devices are physically plugged into one another, enabling unified steering, synchronized charging state, and returning the pluggedInChargerId and pluggedInVehicleId.

Copy linkKey benefits

• Increase your market reach: Start onboarding users whose vehicles are otherwise incapable for managed charging by leveraging the capabilities of their charger. You no longer need to turn away customers due to their choice of vehicle.
• Improve control performance and reliability: Even for capable vehicles, a paired charger provides faster plug-in detection and a fallback for control commands to improve reliability.
• Capture more flex value: More reliable data and controls enables more sophisticated flex optimizations and value capture.
• Simplify integration: Offload the complexity of pairing logic, merging data, and control routing across a large range of unique devices to Enode so that you can focus on your core product.

Copy linkWhat's new in the Beta?

Key features that were previously available to Early Adopters are now available to all customers including:

• Unlocked capabilities: You can unlock startCharging, stopCharging and location capabilities for incapable vehicles through the paired charger.
• Unified control: We offload the complexity of pairing logic, data merging, and control routing. You only need to interact with the Vehicle API to manage both assets.
• Enhanced performance and reliability: By orchestrating commands across both assets, we ensure the highest possible success rate and provide a seamless fallback if one of the devices is offline. You also benefit from faster plug-in detection and unified charge state.

We have also rolled out a number of bug fixes, product improvements and made it easier for customers to start integrating and testing the solution including:

• Full sandbox support: You can now use Sandbox to test your integration before moving to production. We've added support for managing locations and the common pairing/unpairing flows.
• A new product guide: We have published a comprehensive and completely revamped Product Guide to our public documentation. This guide walks you through the entire process, from initial integration steps to full production rollout.

Copy linkHow do I get started?

EV Charger Pairing is now enabled by default for all new and most of our existing customers on API version 2024-10-01. We first recommend diving straight into our comprehensive Product Guide.

PLEASE NOTE: We've disabled certain features for some customers

To mitigate any risk of disruption for customers who 1) link both vehicles and chargers AND 2) directly control those chargers via our API, we have proactively disabled certain EV Charger Pairing features across all of your API clients. This includes capability unlocking and command orchestration features.

The features released to all customers, including returning the pluggedInChargerId and pluggedInVehicleId on the Vehicle and Charger endpoints respectively and improved charge rate handling, will continue to work as they did before.

Please contact your Customer Success Manager or Support if you would like to enable the full EV charger pairing solution.

Need help integrating?

For technical questions & bug reports, report issues through Zendesk. We're actively developing EV Charger Pairing and welcome your feedback to help shape its future.

IDLE mode allows to enforce the battery into an a state where it maintains its current state of charge.

The 1.0.6 release of the Android SDK improves handling of OAuth flows powered by our partners.

➡️ Read our Android SDK documentation to learn about the SDK.

Virtual accounts are now available in Sandbox, giving you a realistic way to test how OEM accounts behave in production.

With virtual accounts, you can recreate any real-world device setup and test every stage of the linking process, from connecting accounts to managing devices after linking.

You can:

• Create accounts with one or many devices across asset types such as vehicles, batteries, and chargers
• Automatically link all devices in an account to a user, or retrieve credentials to test linking using LinkUI
• Add or remove devices after linking to simulate real-world API behavior

To try it out, head to your dashboard and open the Virtual accounts section on your Sandbox client. ➡️ Read the Sandbox guide to learn more

Copy linkHEM System API

The Home Energy Management (HEM) System models how energy devices work together in the real world. It links a user’s inverter, battery, and meter into one synchronized system within the Enode API - laying the foundation for consistent, end-to-end energy insights.

Instead of leaving our customers with the task to turn devices that belong together into a system, we solve it for them by providing system level data, insights and statistics in one easy to use and central API: The HEM System

Copy linkKey benefits

• Energy metrics: Easy access to solar generation, household consumption, grid imports/exports, and battery charge/discharge data.
• Synchronized data collection: All devices are polled together, ensuring consistency across generation, consumption, and storage metrics.
• Comprehensive statistics: Access detailed time series data with 5–15 minute resolution (vendor dependent).
• Simplified development: A single API endpoint for complete home energy insights that match what users see in vendor apps.
• Optimization-ready data: Accurate, synchronized data enables both behind-the-meter and grid-level optimization strategies.

The HEM System is currently in beta and supported for Enphase, FoxESS, GivEnergy, Huawei, SMA, SolarEdge, Solax, Solis, and Tesla on API version 2024-10-01 and later.

To learn more, please visit our integration guide and API documentation on HEM SystemsAPI.

Interested in testing these features and helping us shape this solution? Inquire with your Customer Success Manager about joining our beta.

Setting a battery into IDLE mode enables battery optimization use cases such as:

• Prevent the battery from discharging to cover household load - this is useful to shift discharging to a later point in time, for example when prices are high.
• Prevent the battery from charging from solar - This is useful to ensure free battery capacity is available at a later point in time, for example when prices are low. Solar will continue to produce as normal, but the battery will not charge from it.

IDLE mode is an important building block when optimizing batteries. Our initial release adds support for SolarEdge and Solis (hybrid) inverters connected to a battery. We are working towards supporting more vendors soon.

To learn more, please visit our API documentation on battery modesAPI.

The 1.0.7 release of the iOS SDK brings full screen support for Link UI.

You can now choose between the following presentation styles:

• Sheet (default)
• Fullscreen

➡️ Read our iOS SDK documentation to learn more

The Find by ID feature has been refined to increase successful searches and provide clearer guidance when no results are found. Enhancements include:

• Built-in support for search by VIN
• A revamped UI that makes the process clearer and more intuitive
• Context-aware hints for cases such as attempting to search under an unintended client account, looking up users without associated assets, or entering familiar terms like vendor names instead of IDs

The integrations have been stable for several months. These assets can now be linked to all Enode clients without manual activation.

Copy linkUnified Control

Unified Control allows you to manage EV charging using the Vehicle APIAPI and leverage any supported charger linked to the same Enode userId.

When a vehicle is plugged into a charger:

• Seamless orchestration: Send commands to the Vehicle API as usual. Enode automatically coordinates with the charger for optimal control
• Fallback compatibility: If the vehicle is unplugged or connected to a different charger, control remains unchanged via the vehicle only
• Smart Charging enhancement: Vehicles with Smart Charging enabled automatically leverage charger controls when executing their plan
• Scheduling enhancements: Vehicles using Schedules automatically leverage charger controls when executing their schedule

Copy linkUnlocked Capabilities

Linking a charger to the same user immediately unlocks previously unavailable vehicle capabilities:

• Charging control: Vehicles gain isCapable: true for startCharging and stopCharging the moment a charger is linked
• Location detection: Vehicles gain isCapable: true for location when it can be inferred from the charger
• Smart Charging eligibility: Vehicles that previously lacked control capabilities are now eligible for Smart Charging

By leveraging these unlocked capabilities, customers can expand the market reach of their managed EV charging programs.

Interested in testing these features and helping us shape this solution? Inquire with your Customer Success Manager about joining our Early Adopter Program.

Solis battery and meter asset types are now ready for beta testing.

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

As part of our commitment to providing accurate and meaningful reliability scores, we will now always mark Beta models as having an "N/A" reliability score. Beta models by definition are newer where we don't have the typical data needed to assign a reliability score.

This policy ensures consistency across our platform and avoids presenting scores that may not reflect real-world performance due to limited data. Our goal is to move models out of Beta as soon as possible and only assign a reliability score once we've gathered enough data to feel confident in its accuracy.

To solve this, our new EV Charger Dynamic Pairing solution automatically detects when a user's vehicle is plugged into their charger, forming a dynamic charging pair that can be fully controlled via the vehicle API. Once your user links both their vehicle and charger, you can overcome capability limitations, improve charging reliability, and simplify your integration by letting Enode handle the complex pairing logic and command orchestration between the two devices.

We have released foundational components to EV Charger Dynamic Pairing for all customers. Starting today:

• Charger identification: Vehicle APIAPI responses now include a new attribute, pluggedInChargerId, identifying which of a user's chargers is currently plugged into their vehicle. By default, this attribute will be null and will only be populated if:

  • The charger and the vehicle are linked to the same Enode userId.
  • AND Enode has determined that the vehicle and charger are currently plugged into each other.

• Improved charge rate handling: When a vehicle doesn't report a chargeRate, we now automatically fall back to using the charger's provided rate, giving you consistent and accurate charging information.

• Faster plug-in detection: Reduced plug-in detection time by leveraging direct signals from the charger.

More advanced features coming soon! Interested in using chargers to control previously incompatible vehicles or to further increase command reliability? Get exclusive, early access to these features by joining our Early Adopter Program. You will collaborate closely with our product team and help shape the future of this solution. Enquire with your Customer Success Manager about joining.

You can now request a linking session with the following language codes to present the LinkUI in additional languages:

• Latvian (lv-LV)
• Lithuanian (lt-LT)
• Japanese (ja-JP)
• Polish (pl-PL)

To use this feature, set the language attribute to the desired code when creating a linking session.

Additionally, interventions will now also be available in these languages. Set the language query parameter accordingly when fetching interventions to receive the resolution descriptions in the selected language.

BYD vehicles are available for beta testing in Australia. These vehicles are "read only", meaning they cannot be started or stopped.

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

Asset History lets you see a chronological timeline of events for each vehicle. It includes charging actions, power delivery changes, and interventions – so you can understand how a vehicle has been used and identify the root cause of issues faster.

Use it to:

• Trace the full sequence of events for any vehicle
• Understand how vehicles are being used and controlled over time
• View failed charging actions and interventions with rich detail
• Spot and resolve integration issues early

How to find it: Simply head to your dashboard, use Find by ID to locate a vehicle asset, and click “History” in the top-right corner of the Asset View.

➡️ Read the Asset History guide to learn more

Note: This is a beta release. We'd love your feedback to help shape what comes next. You can share it directly through the built-in feedback form in the Asset History view or reach out to your Enode contact.

BYD vehicles are available for beta testing in Europe.

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

Dacia and Alpine vehicles are now available for beta testing.

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

As part of ongoing system maintenance, we've cleaned up Zaptec device model names to remove redundant prefixes in the information.model field in our API. Your devices will now display with simpler names for improved readability. For example, information.model values that were previously Zaptec Go will now simply be Go.

Insights is a new section in the customer dashboard that gives you a clear overview of your integration health — with aggregated data on connection growth, connection mix, and potential issues. It's designed to support faster decision-making and increase visibility across technical and product teams.

With Insights, you can:

• View week-over-week trends in connections and interventions
• Drill down into specific metrics by asset type and vendor
• Pin your most important insights for quick weekly check-ins
• Access Enode's expert guidance directly alongside the data

Note: This is a beta release. We'd love your feedback to help shape what comes next — you can share it directly through the built-in feedback form in the dashboard or reach out to your Enode contact.

To explore Insights, head to your dashboard and open the Insights tab.

More information is available in our guide.

FOXESS batteries and meters are now available for beta testing. Please note that the support for setting operation mode on batteries is pending. We are working on it and will update the changelog once ready.

Asset View provides real-time asset data to help you quickly resolve customer issues and conduct thorough QA on new features, empowering you to work faster and support users more effectively.

With Asset View, you can:

• Find any asset quickly given the asset ID or user ID
• View real-time asset states and live/historical webhook data
• See automatic issue warnings that flag common problems
• Escalate to Enode with confidence, using Zendesk integration and auto-filled ticket data.

To access asset view, go to your dashboard and select a production client.

More information is available in our guide.

We're retiring Sandbox 1, and after 4 September 2025, it will no longer be available.

To avoid disruptions, please check whether your integration is using Sandbox 1 clients and migrate to our new Sandbox environment if needed.

To verify your setup, log in to your customer dashboard and check your clients. Sandbox 1 clients are labeled "Sandbox (legacy)" in the dashboard overview.

Copy linkKey Dates

• 3 & 17 April: API requests to Sandbox 1 return 401 Unauthorized throughout the day.
• 4 September: Sandbox 1 is fully disabled; all API requests permanently return 401 Unauthorized.
• 6 October: All remaining Sandbox 1 clients will be deleted.

Copy linkAction Required

To ensure a smooth transition, complete the migration before 2 June:

1. Create a new Sandbox client: Log in to your customer dashboard and follow our setup guide.
2. Update your API credentials: Replace your Sandbox 1 client ID and secret with your new Sandbox client credentials.
3. Adjust authentication flow: In the new Sandbox, users must log in using an email/password from a virtual asset (manual logins are not supported).
4. Check dependencies: If you have automated tests or integrations relying on Sandbox 1, they may require updates—especially if they interact with Link UI.

Please complete your migration by 2 June to prevent service disruptions.

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

Our new Sandbox experience offers a simpler, faster and more reliable way to test your Enode integration with fully controllable virtual assets.

• Expanded coverage: Sandbox now supports all asset categories. Create and control vehicles, batteries, and other asset types.
• Full control: Modify asset states instantly to simulate real-world conditions. You can now control the full asset state.
• Webhook integration: Monitor live updates and changes directly in the Sandbox UI.
• Intervention simulations: Test interventions and their effects on assets in a controlled environment.

Learn more about how to use Sandbox for building and testing energy apps in our Sandbox guide.

We are introducing a new relinking endpoint. Integrating with this endpoint allows you to:

• Resolve interventions which require user interaction within LinkUI
• Reconnect a device which Enode no longer has access to

To start using this functionality, please see our relinking documentation.

Sometimes linking a single asset type is not enough. When your customer owns multiple asset types from the same vendor, Link UI can now be configured to link all of them at once in a single session. This can significantly reduce friction for users by helping to consolidate linking flows and to get devices connected to your app faster.

Multi-type linking is particularly useful when connecting solar inverters, batteries and meters or when connecting other vendors with a wide range of devices supported by Enode.

To learn everything about it, please visit our documentation.

Soon, our Get Chargers API and webhooks will show the serial number of a connected charger.

We're exposing a nullable attribute inside the information object, under information.serialNumber.

Reach out to us if you'd like to opt-in early.

Afore integration is available for beta testing.

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

The 1.0.5 release of the iOS SDK brings fixes for redirect URI values requiring encoding. We recommend all users of Link UI v4 to implement the SDKs or upgrade from <1.0 versions. Get the 1.0.5 iOS SDK from our documentation:

• iOS

We are excited to announce that support for integrating with Heidelberg chargers is now in beta.

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

Previously, the default charge limit for vehicles was always 100%. When Enode wasn't able to determine the charge limit, it would default to 100%.

This has now been changed. When Enode isn't able to determine the charge limit, it will now default to null. This indicates that the vehicle isn't reporting a charge limit, or Enode isn't able to determine what it is. If you are using this value in calculations, we still recommend defaulting to 100%. However, a default 100% should not be presented in user interfaces.

Our GivEnergy support is available for beta testing.

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

Acura vehicles are available for beta testing in North America.

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

To check available vendor integrations for one or more assetTypes, we are adding a new "/integrations" endpoint.

This makes it convenient to check support and scopes across asset types for our vendor integrations. It reduces the need for multiple requests to "/health/<assetType>" for different asset types.

Enphase batteries with the ability to configure a timer for discharging to the grid are now marked as EXPORT_FOCUS capable and can be switched into that mode.

We'll update the capabilities table as we learn more about which Enphase batteries are capable of discharging to the grid.

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

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

Lucid vehicles are available for beta testing in Europe and North America.

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

NIO vehicles are available for beta testing in Europe.

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

The 1.0.3 release of the iOS SDK brings fixes for linking Nibe devices. We recommend all users of Link UI v4 to implement the SDKs or upgrade from <1.0 versions. Get the 1.0.3 iOS SDK from our documentation:

• iOS

Polestar vehicles are now available beta for Europe and North America. These vehicles are "read only", meaning they cannot be started or stopped.

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

Chrysler, Dodge, and Ram vehicles are now available for beta testing in North America. Alfa Romeo is available for beta testing in both North America and Europe. Finally, Lancia vehicles are available for beta testing exclusively in Europe.

To opt-in, please activate the desired brands in the enabled-brands section under your Enode client.

We are excited to announce that support for integrating with myenergi chargers is now in beta.

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

Mazda vehicles are now available in beta for Europe and North America.

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

Honda vehicles are now available in beta for North America, and MG vehicles are supported in Europe.

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

We've expanded charger linking support to include Keba.

To opt-in, please update the enabled-brands section in your Enode client and toggle Keba.

We are excited to announce that support for integrating with Hypervolt chargers is now in beta.

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

Volvo EX models can now be linked to Enode. These vehicles are "read only", meaning they cannot be started or stopped.

To opt-in, please reach out to your Enode contact, or send us a ticket at support@enode.io.

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.