You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today was a planned power outage . On restoration of power I noticed that all the solax modbus entities were unavailable . I had to also restart the inverter to get the solis data logger to communicate with the solis cloud but the reset did not restore the entity data . If i added a new solax mobus device then the data became available to that new device entities
The log entry below seems to give an indication as to the issue
I would like to be able to restore communication for the original device to save a lot of rework dashboards / automations etc.
Describe the bug
Today was a planned power outage . On restoration of power I noticed that all the solax modbus entities were unavailable . I had to also restart the inverter to get the solis data logger to communicate with the solis cloud but the reset did not restore the entity data . If i added a new solax mobus device then the data became available to that new device entities
The log entry below seems to give an indication as to the issue
I would like to be able to restore communication for the original device to save a lot of rework dashboards / automations etc.
config_entry-utility_meter-f18cb27d27480c4ebc966ba920865975.json
Integration Version
3A0030-030000
Homeassistant core version
2024.10.1
Inverter brand
solis
Plugin used
plugin_solis.py
Serial prefix
6031020223
Connection Method
USR 610 wifi adapter
Detailed Error Log
No response
Additional context
This error originated from a custom integration.
Logger: custom_components.solax_modbus.plugin_solis
Source: custom_components/solax_modbus/plugin_solis.py:2456
integration: SolaX Inverter Modbus (documentation, issues)
First occurred: 12:27:38 (268 occurrences)
Last logged: 15:47:59
unrecognized solis-w610 inverter type - serial number : unknown
The text was updated successfully, but these errors were encountered: