SolarEdge API V2 Uses OAuth. Old API will be turned off in November,

[P_J_Hardman (Peter)]

My solar installer sent me an email today to let me know that I am still using the V1 API to access my solar panel production data and that this service will be discontinued in November.

It is not clear to me if the current integration supports the V2 API, and if it does how do I setup the OAuth? It looks like I have to tell OAuth setup which computer is going to request the authentication.

Here is what they said.

SolarEdge has announced that its current API platform (known as V1) will be retired on November 3, 2026. After that date, applications that rely on the older API connection method will stop working unless they are updated to SolarEdge’s new V2 platform.

What does this mean for you?
If you use a third-party application that connects to your SolarEdge monitoring account, you may need to reconnect that application using SolarEdge’s new authorization process.

The good news is that SolarEdge has designed the new system so homeowners can authorize applications directly. In most cases, you should not need a new API key from ReVision.

What should you do?

1. Identify any applications, services, dashboards, or automations that currently connect to your SolarEdge system.

2. Reach out to the provider of that application and ask if they support the SolarEdge V2 API.

3. Follow any migration or reconnection instructions provided by that application’s developer.

4. Complete the migration before November 3, 2026 to avoid interruptions in data access.

Where can I learn more?

SolarEdge provides documentation and self-service tools for homeowners who want to access their own data:

1. SolarEdge Developer Portal: https://developer.solaredge.com
   Homeowner and Self-Access Guide | 1 - Developer Platform Docs

[jlv (John)]

exisiting topic:

SolarEdge V1 retirement: what are other Home Assistant users doing?

SolarEdge says its Monitoring API V1 will retire in November 2026. What are other Home Assistant users planning to use for solar and battery data? I tried the local SolarEdge Modbus Multi integration as a fallback. It reads my SE7600 inverter and WattNode meter, but it cannot see my LG battery: direct read-only probes of all supported battery register blocks return Illegal Data Address. So local Modbus is not a full replacement for me—no battery SOC or battery power. Has anyone found a workaro…

[solfoit]

Hi,

My Solar installer provided me with the same document.

I’ve tried it but i’m an absolute newbee in regard to api and OAuth so i don’t know what to fill in for my redirect url. Do i have to make my home assistant environment accessible from the internet? I hope not.

Greetings,

Ruud

[wmaker (Tommy Long)]

@solfoit

Do i have to make my home assistant environment accessible from the internet? I hope not.

This API is used to talk to SolarEdge’s cloud services, so if you want to use this API, then yes. Otherwise search around for users who have used Modbus directly with SolarEdge’s inverter.

[wimjanse]

The HACS integration SolarEdge modbus multi connects directly to your inverter, no cloud connection, direct tcp connection over your wired or WiFi network.

[Dave2 (Dave)]

See the original message where modbus shows basic data but does not expose my battery information.

[WillCodeForCats]

SolarEdge does not universally implement (or enable) individual battery data over modbus on their inverters.

However, DER battery might be universal, but it only provides a single data point per inverter: the SOC.