Setup guides → SolarEdge

SolarEdge

Read SolarEdge locally with the Sunplug Agent, or through SolarEdge's cloud with nothing at home.

With the Sunplug Agent

Every 30 seconds, day and night, over Modbus: production, battery power and charge level, and the grid when a SolarEdge meter is fitted at the supply point. No account; nothing leaves the house.

1. Enable Modbus TCP on the inverter. It is off from the factory. Your installer can do it in SetApp under Site Communication, or you can do it yourself in two minutes, as shown below.
2. Set up the Sunplug Agent at home, on the same network as the inverter
3. The agent finds the inverter itself on port 1502 — you do not need its address
4. In Settings → Solar system, pick the inverter the agent found

Many SolarEdge installs have no meter at the supply point. Without one, Sunplug sees production but not surplus, through the agent or the cloud: add a Shelly meter.

Through the SolarEdge cloud

Nothing at home. Every three minutes, day and night, with house load and the grid when a SolarEdge meter is fitted. You sign in with your SolarEdge monitoring email and password.

Your SolarEdge account needs a site on it before you start. If your installer set the system up under their own account, ask them to share it to yours first.

1. Settings → Solar system → SolarEdge
2. Enter the email and password you use for SolarEdge monitoring
3. Save. Sunplug finds your site and takes the first reading straight away

Sunplug only reads your energy data and never changes anything in your SolarEdge account. Your password is stored encrypted and used only to sign in to SolarEdge. While the agent is sending readings, the cloud is not read, and switching loses no history.

When it does not work

SolarEdge does not accept your email and password

Check them by signing in at monitoring.solaredge.com. Sunplug tries once more, then stops and sends a notification until you save them again in Settings → Solar system.

SolarEdge asks for an extra verification step

Sunplug cannot complete it. Sign in at monitoring.solaredge.com once yourself, then save the connection again.

The account has several sites

Sunplug reads accounts with one site. Write to me if yours has more.

The agent cannot find the inverter

Modbus TCP is off by default: check SetApp, or ask your installer. The agent must be on the same network as the inverter. You can switch it on yourself, as shown above.

A factory reset switches Modbus off again. If the inverter goes quiet after a service visit, check that first.

The agent cannot read an inverter your own tools can

Update the agent. Versions before 0.2.49 opened a new connection for every block of registers, and a SolarEdge refuses a new connection for a moment after the last one closes. The agent found the inverter, then failed with "no SunSpec magic at any known base", "connection refused" or a timeout, while a script or Home Assistant read it without trouble. From 0.2.49, a reading is one connection.

Readings stop while another tool reads the inverter

A SolarEdge serves one Modbus TCP connection at a time. While a home automation system, monitoring app or Modbus scanner holds it, the agent's reads are refused or time out. Stop the other tool, or point it at Sunplug's data instead; readings return within a minute. The unit ID is not the problem: SolarEdge answers on unit ID 1; other IDs are follower inverters and meters.

The battery is not showing

Very old firmware may lack the battery registers. Everything else keeps working; Sunplug treats the house as having no battery.

Stuck? Write to me with the logs.