Skip to content
Home Assistant TestFlight
Energy

SolarEdge Modbus Multi

WillCodeForCats/solaredge-modbus-multi · vv4.0.9

HACSLocal polling

The Complete Local (Modbus/TCP) SolarEdge Integration for Home Assistant

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

EntityShows up asNote
switchSwitch or outlet
binary_sensorSensor (motion, contact, leak, smoke…)
sensorSensor (temperature, humidity, air quality…)
buttonButton (as a switch)
selectMode picker (as switches)

What people report

Local Modbus integration for SolarEdge inverters, meters and batteries; firmware updates sometimes hang Modbus until the inverter is power cycled, and some legacy or gateway units need Modbus enabled.

  • Works3
  • Partly works3
  • Requested1
DeviceIn Home AssistantIn Apple HomeWhat they saidSource
SolarEdge CCG-1000 Commercial GatewayWorks LocalWorks like an inverter after enabling Modbus TCP on LAN
Saved copy
hi, First many thanks for all the work that you have put into this project!🙏🏻✌🏻. I want to connect the Solaredge gateway CCG-1000 (Commercial Communication Gateway) over local network instead of logging into the monitoring server. The problem is that the gateway is connected over the ethernet connection and modbus poort is set to 1502. I think the rs485 ID is 1 because everything is is connected on the RS485-1 the inverters RS485-2 the Nodewatt meter with ID 2, And RS485-E for the inverter with 2 Powerwalls 1 connected ID 24 & 25. The problem is it will not find or connect to it over the …

Excerpt saved from GitHub on 2026-10-23.

Issue #990 · 2026-06
SolarEdge inverter firmware 3.20.0+Works LocalStatus Vendor 4 sensor added for SetApp-style error codes
Saved copy
Add a Status Vendor 4 sensor if inverter if firmware version detected during setup is 3.20.0 and newer. This will display "0x0" formatted error codes to match the error codes you would see in SetApp. The VENDOR4_STATUS dict will need expanding. This PR only includes two to start with. Tested with 3x6E by disconnecting the meter (removed power) long enough to generate the error in SetApp and for HA to poll it.

Excerpt saved from GitHub on 2026-10-23.

PR #977 · 2026-05
SolarEdge inverter with SE-RGMTR-1D-240C-A meterWorks LocalDuplicate meter device bug fixed in PR 103
Saved copy
Describe the bug On 2.2.1 I had two devices: I1 (inverter) M1 (attached meter with model SE-RGMTR-1D-240C-A). Attached meter showed as model "SE-RGMTR-1D-240C-A". Since 2.2.2. I have: I1 (inverter) M1 (SE-MTR-3Y-400V-A) <- no entities M1 (SE-RGMTR-1D-240C-A) <- has all the expected entities Expected behavior not sure if this is really a bug or expected, but at least physically only one meter is attached. Screenshots Home Assistant (please complete the following information): - Home Assistant Core Version: 2022.9.5 - solaredge-modbus-multi Version: 2.2.2

Excerpt saved from GitHub on 2026-10-23.

Issue #100 · 2022-09
Fronius Galvo inverterPartly works LocalSensors mostly work via SunSpec; status codes differ and manufacturer shows SolarEdge
Saved copy
I have a SolarEdge inverter and also a Fronius Galvo inverter. I've installed this component for both inverters. The sensors of the Solaredge inverter looks very good. Better then other modbus components I've tested so far. Good work! The sensors of the Fronius inverter looks good. Some small improvement could be made. As you can see the main sensor values are ok. The Fronius status codes are different and also the power factor is different. So with no modifications I can use this custom component already for both inverters! I think with some minor changes this component could also be …

Excerpt saved from GitHub on 2026-10-23.

Issue #12 · 2022-01
SolarEdge inverter firmware 0004.0023.0036Partly works LocalModbus stopped connecting after update; power cycling inverter fixed it
Saved copy
TLDR: If Home Assistant has lost connection to the inverter, cut power to the inverter for ~10 seconds and then turn it back on. Hopefully this information can help others in the future if they lose connection after a firmware update. My solaredge inverter and this modbus integration have been rock solid for years, so I was very surprised when a "fault" was detected by Home Assistant and all sensors became unavailable. I saw in the logbook that the firmware had changed from 0004.0021.0023 to 0004.0023.00036. This has never been a problem before, my inverter started somewhere around …

Excerpt saved from GitHub on 2026-10-23.

Discussion #906 · 2025-09
SolarEdge StorEdge batteryPartly works LocalAC charge limit cannot force charging at night; likely SolarEdge firmware behaviour
Saved copy
… perfect. I tried to change AC Charge Limit from Always Allowed to the other options, even if I dont understand how it would affect the Charge Limit of the battery; the result is the same I can't modify the Charge Limit, the value won't save. Lets further explain my installation: - Leader SE inverter is an EV inverter - Follower SE inverter is an Storedge inverter. I change the Charge limit and Discharge limit on this inverter which is the one connected to a LG battery. Discharge limit can be modified any time but not the Discharge limit Could it be related to the status of the leader …

Excerpt saved from GitHub on 2026-10-23.

Issue #691 · 2024-10
SolarEdge SE3500-ER-01 legacy inverterRequested LocalCPU 2.1049 has no Modbus TCP menu or open ports
Saved copy
Hello, I'm trying to integrate an older SolarEdge SE3500 inverter into Home Assistant for local monitoring and future energy-based automations. Inverter details - Model: SolarEdge SE3500-ER-01 - CPU firmware: 0002.1049 - DSP1/2: 1.0210 / 2.0052 - Country setting: GBR2 - Inverter IP: 192.168.0.72 - Ethernet connection to my local network Tests performed - The inverter responds to ping from my Ubuntu server with 0% packet loss. - TCP ports 502, 80, 443 and 2222 all return “Connection refused”. - In the inverter communication menu I can see `Server `, `RS485-1 Conf `, `ZigBee Conf `, `Wi-Fi Conf …

Excerpt saved from GitHub on 2026-10-23.

Discussion #1157 · 2026-10

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Local polling

Talks to the device on your network, asking it for updates every so often.

Found automatically over

  • Bonjour (zeroconf)

Details

Installs (analytics)3,169 (0.45%)
GitHub stars332
Latest versionv4.0.9 (2026-10-21)
Set up in the UIYes
Maintainers@WillCodeForCats
LicenseApache-2.0

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.