SolarEdge Modbus
binsentsu/home-assistant-solaredge-modbus · vV2.3.0
Home assistant Component for reading data locally from Solaredge inverter through modbus TCP
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.
| Entity | Shows up as | Note |
|---|---|---|
sensor | Sensor (temperature, humidity, air quality…) | |
select | Mode picker (as switches) |
1 report below say how a device from this integration behaves in the Home app.
What people report
SolarEdge inverters read over Modbus TCP; battery and meter registers work on common models. Firmware 4.21.x and later reportedly breaks remote battery commands and data reads until rolled back.
- Works1
- Partly works2
- Not working2
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| SolarEdge HD Wave SE3680 with LG RESU 7kWh | Works Local | Battery power and energy storage sensors addedSaved copyAdd support for reading the modbus registers for storage status. This works with my Solaredge HD Wave SE3680 inverter with LG RESU 7kWh battery. The sensors give access to the battery power and energy flows which can be used for Home Assistants energy dashboard. Much inspiration for the code taken from https://github.com/mkrasselt1/solaredge-modbus-hass/commit/58adaffbcfced20f966d5edf38b7d8c401000c8d Additionally set all sensors to "STATE_UNKNOWN" instead of a numeric value, such that cumulative sensors like "acenergy" do not go backwards and trigger a reset of home assistants internal value. Excerpt saved from GitHub on 2026-10-23. | PR #35 · 2021-09 | |
| SolarEdge inverter with SMA and Zucchetti meters | Partly works Local | Meter 3 shows wrong or frozen data; Meter 1 setup failsSaved copyHi everyone, I’m having trouble setting up the SolarEdge Modbus integration over Ethernet. Setup details: SolarEdge inverter connected via Ethernet Two external meters: SMA and Zucchetti Issue: During setup, if I select Meter 1, the installation fails. If I select Meters 2 and 3, the integration works and I get data. Meter 3 shows completely wrong or frozen values, but the total production between SolarEdge, SMA, and Zucchetti is correct. In the SolarEdge installer app, I can see the production values of the individual optimizers connected to the inverter. However, these values do not appear … Excerpt saved from GitHub on 2026-10-23. | Issue #353 · 2025-10 | |
| SolarEdge storage backup reserved entity | Partly works Local | Partly in Home Storage_backup_reserved missing in Home app; Storage_AC_Charge_Policy shows | Storage backup reserved entity not exposed to HomeKit bridgeSaved copyStorage_ backup_reserved entity is not being exposed to HomeKit. Other entities such as Storage_AC_Charge_Policy are available to be modified via iOS and MacOS Home App. Excerpt saved from GitHub on 2026-10-23. | Issue #98 · 2022-08 |
| SolarEdge SE10K-RWS inverter | Not working Local | Firmware 4.21.xx/4.22.xx stops remote battery commands; downgrade to 4.20.xx fixesSaved copyHey folks, I installed firmware 4.21.xx to my Solaredge SE10K-RWS and found out, that my HA remote storage commands stopped working after that upgrade, no effects from the remote battery commands. I enabled debug mode for the integration without any entries in the logs. A test with firmware 4.22.xx resulted in the same issue. I requested a firmware rollback from Solaredge support to 4.20.xx and remote battery storage commands are back. Solaredge startet to introduce new battery profiles in the latest releases so maybe modbus registers changed. Any ideas? Excerpt saved from GitHub on 2026-10-23. | Issue #259 · 2024-11 | |
| SolarEdge SE5000H inverter | Not working Local | Data errors after automatic upgrade to firmware 4.21.23Saved copyHi, I have a similar effect after the SolarEdge SE5000H upgraded automatically to 4.21.23. I cannot receive any data due to data errors. ``` 2024-12-06 11:04:46.448 ERROR (SyncWorker_8) [custom_components.solaredge_modbus] Error reading modbus data Traceback (most recent call last): File "/config/custom_components/solaredge_modbus/init.py", line 244, in _refresh_modbus_data update_result = self.read_modbus_data() ^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/solaredge_modbus/init.py", line 324, in read_modbus_data and self.read_modbus_data_battery1() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ … Excerpt saved from GitHub on 2026-10-23. | Issue #259 · 2024-11 |
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
Connection not stated
The integration doesn’t declare how it connects.
Its README mentions local or LAN control.
Details
| Installs (analytics) | 1,875 (0.26%) |
|---|---|
| GitHub stars | 418 |
| Latest version | V2.3.0 (2026-07-02) |
| Set up in the UI | Yes |
| Maintainers | @binsentsu |
Notable forks
Forks with stars, or with code pushed at least 90 days after the original’s last push. Useful when the original goes quiet.
| Fork | Stars | Last push | Description |
|---|---|---|---|
| Tapematch/home-assistant-solaredge-modbus | ★ 8 | 2021-10-08 | Home assistant Component for reading data locally from Solaredge inverter through modbus TCP |
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.
