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
not using configuration.yaml, set up via config flows.
Describe the bug
Every once in a while the AC Lifetime Energy Produced value of the inverter goes unavailable. Apparently it happens when there is an error reading the value and the root cause may be with my Fronius inverter. Based on a short test via modbus poll it appears that the inverter occasionally does not respond to the query for that particular register.
My problem is that this value can only be read again if I restart the whole integration. Ideally the integration would keep trying to read the value even if there is no response.
Debug log
Relevant Home assistant log entry:
2024-09-17 19:21:24.086 ERROR (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: Fimer100: Error: device: 1 address: 40233 -> Modbus Error: [Input/Output] ERROR: No response received after 3 retries
The text was updated successfully, but these errors were encountered:
SunSpec version: 0.0.26
Configuration
not using configuration.yaml, set up via config flows.
Describe the bug
Every once in a while the
AC Lifetime Energy Produced
value of the inverter goes unavailable. Apparently it happens when there is an error reading the value and the root cause may be with my Fronius inverter. Based on a short test via modbus poll it appears that the inverter occasionally does not respond to the query for that particular register.My problem is that this value can only be read again if I restart the whole integration. Ideally the integration would keep trying to read the value even if there is no response.
Debug log
Relevant Home assistant log entry:
The text was updated successfully, but these errors were encountered: