grouts112
grouts112
While Waiting for a fix to the daily ERROR stopping this not working, I have made an automation to trigger on the error and restart the integration. Working nicely.
Looking at https://github.com/pymodbus-dev/pymodbus/issues?q=is%3Aissue%20state%3Aclosed it seems some similar issues reported against pymodbus 3.7.4 which is what was updated from pymodbus 3.6.9 in the recent solareedge_modbus update to fix the 2025.1 issues....
Seems pymodbus 3.8.3 is merged into core. https://github.com/home-assistant/core/pull/134809 I can't tell what release that will be in. 2025.1.4 ?? Maybe that will fix this.
here is the Automation: Note... you will need to find your specific "entry_id" for your solaredge_modbus integration on your HA. Check in the 'config/.storage/config_entries' file... search for "solaredge_modbus" and copy...
I suspect that your ‘target’ device id: will need changing also. When in the automation editor, (not yaml view) Expand the action and change the device to pick your solaredge...
Ooh just re read your post.. That is the message i put in the automation, so you get a notification that it did it, otherwise you wouldnt know. You could...
Thank you @ binsentsu