Release v2.4.18 is now available. This release adds a Grid Power binary sensor you can use to determine if you’re running on battery backup or grid power.
I’ve tried searching around, including checking the power control options wiki page - sorry if I missed it; what is the “Commit Power Settings” button for exactly? When should we use it or not use it?
Does anybody using this extension have the SolarEdge Home Load Controller integrated?
I would like to switch the relais modes on/off/auto via an automation.
See datasheet here:
No, there are no modbus registers that I’m aware of for the load controller.
I would be happy to add them if they are just undocumented and someone passes along the information.
heyhey
Ive been using this integration for about 2 years now. Without any bigger issues (or atleast without any issues i didnt cause :o)
Since two or three days my homeassistant is unable to connect to my inverter.
The integration sais: "Modbus/TCP connect to: 192.168.178.45:1502 failed.
(without me consciously doing something)
I registered the problems at the morning. So I think it was broken over night.
But I really dont have any idea what could have happened.
I got two SolarEdge inverters in total and an energymeter, all connected to the main inverter.
Even if I didnt change anything in the inverters configuration I checked if anything is correct.
And it looks like everything is fine here (checked with the help of installation tutorial of this respository). But again I didnt change anything, so I expected this.
But I really have no idea where to start searching for the problem.
The Inverters are online (watched in FritzBox), IP and port are correct. And the SolarEdge App is reporting.
Im using HomeAssistant OS 13.1 - Core 2024.8.3 and solaredge Modbus Multi 2.4.20.
Does anyone have an idea where to start to search for the reason it doesnt work anymore?
I don’t use solar edge but I use Sungrow with modbus and similar issue, mine stopped recording on Homeassistant on 28th August 2024 at a bit before 4:05pm in the afternoon (Australian easter standard time). No updates at that point or near that time that I am aware of. I updated homeassistant core and supervisor to no avail. Sungrow app working fine.
Hi! I am new to HA and to this topic so I apologise upfront for asking these newbie questions.
I am looking for advice how to:
a) steer the production from my SolarEdge SE25k
b) to match the consumption from my own household (believe it is called dynamic export limitation)
c) during hours when the electricity price on Nordpool is negative.
I have a smartmeter from the eletricity company + a loadbalancer (measuring local consumption). Inverter network connection is via wireless network.
I do NOT have any batteries as the inverter does not support that.
Is this the right place to start? Any advise is highly appreciated. The development with negative electricity prices are horrible.
Cheers
I think that after I upgraded to 3.0.0 I lost some values:
This entity is no longer being provided by the solaredge_modbus_multi integration. If the entity is no longer in use, delete it in settings.
Any idea ?
There are no changes to entities in the 3.0.0 release.
You can turn on debug logging to see why they aren’t detected.
I am encountering the same issue.
I’ve enabled advanced power mode and RCRR, but the settings seem to revert. I’m trying to set the export control limit and site limit to 200W, but it only holds for about 30 seconds.
Does anyone know what I might be doing wrong?
This is for a scenario where my solar system is exporting, and I want to limit the export to minimize it while ensuring my home gets all the power it needs without relying heavily on the battery.
Additionally, how can I tell if I’m exporting? Does this integration show my export data, or do I need to use something like an Effergy device and compare it to another sensor?
Also I can update the settings like storage control mode directly in the integration from home assisant but i cannot get selection options to update it to Remote Control for example. Either via dev tools / actions or from node red.
But it lets me update it n the integration page - what could I be doing wrong?
thanks very much
Thank you.
Logs:
2024-10-03 19:10:30.324 ERROR (MainThread) [homeassistant.components.binary_sensor] rpi_power: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 724, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1302, in async_device_update
await hass.async_add_executor_job(self.update)
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/rpi_power/binary_sensor.py", line 53, in update
value = self._under_voltage.get()
^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'get'
....
2024-10-03 19:10:30.795 WARNING (ImportExecutor_0) [homeassistant.const] POWER_VOLT_AMPERE_REACTIVE was used from solaredge_modbus_multi, this is a deprecated constant which will be removed in HA Core 2025.9. Use UnitOfReactivePower.VOLT_AMPERE_REACTIVE instead, please report it to the author of the 'solaredge_modbus_multi' custom integration
Link to full log Dropbox
If someone can check…
Do you happen to have an example of calling the storage control mode and changing it to remote control, for example in node-red or automation?
My calls.simply are not going through. It doesn’t change but I can change it in the UI from the integration . 
edit: OK so it works from automations in HA but not from node red using select.select_option odd
edit2 :
i discovered the issue 
- Original Node:
entityIdis a string. Doesn’t work
"entityId": "select.solaredge_i1_storage_control_mode"
- New Node:
entityIdis an array.
"entityId": ["select.solaredge_i1_storage_control_mode"]
This is the node that worked for me - hopefull this helps others too:
{
"id": "3a36fa5639176568",
"type": "api-call-service",
"name": "",
"server": "f9088194.9ff3a",
"version": 5,
"domain": "select",
"service": "select_option",
"entityId": ["select.solaredge_i1_storage_control_mode"],
"data": "{ \"option\": \"Remote Control\" }",
"dataType": "json",
"x": 1310,
"y": 820,
"wires": [
[]
]
}
U thx - Auto-Detect Additional Entities that was it. But I didn’t manually turned off this option.
Anyway big thank you for this info (and naturally also for the component itself)
It’s in the release notes:
I recently upgraded my Solaredge inverter with display, to display with Setapp.
Since then the ‘Solaredge multi’ integration from time to time ‘freezes’ and all the entities become unavailable.
I use a modbus proxy for years without issues, and my other integrations (EVCC) keep working.
I assume it has something to do with the new setapp inverter, but still it is strange… anybody has experienced this before?
Yes, the same here.
My log is full with multiple daily errors of not connecting, connection errors which results in unavailable entities in the dashboards… Quite annoying as it was stated to me that solaredge_modbus_milti should’ve been more stable than the core one… Although, it’s still a mess and do not seem to have a stable connection at all…
I use my own integration and would not release something that doesn’t meet my own standards. I do not see connection issues with my own inverters.
The usual advice applies: make sure nothing else is trying to conect to the inverter (it only allows one connection), and using wifi is known to cause problems (wired connection is better).
I develop the integration on SetApp inverters, but I don’t use any proxies, only a direct connection. I would recommend trying a direct connection without the proxy to see if the connection problem continues or not. What proxy are you using?
My integration can coexist with others as long as everything is using polling and the timing isn’t too fast (and the keep connection option is disabled). I don’t use EVCC to know if it holds the connection open for itself.
You can also upload debug logs and diagnostic file at the time the problem occurs.
Yeah I tried direct without any other connections and I had the same problems.
Maybe it has something to do with the latest setapp firmware
I will try to find logs.