Seth

This is not a critical problem (you can just delete and re-add the integration) but there are probably ways it can be better.

configuration.yaml ``` logger: logs: pymodbus: debug ```

I would try giving the inverter a cold boot if you haven't already done that. Turn the red switch to 0, wait for it to shut down, then open the...

This might also be a connection race from an uncaught exception during setup; I've corrected that in PR #515 and I'll push a pre release shortly for you to try.

[Release v2.4.9-pre.4](https://github.com/WillCodeForCats/solaredge-modbus-multi/releases/tag/v2.4.9-pre.4) contains the change.

Basically what wasn't happening is when an IO error occurred during setup it wasn't calling disconnect. It would then loop back around holding onto a possibly dead connection. What's supposed...

During setup when the configuration is first loaded (or reloaded), Home Assistant will turn all errors into `ConfigEntryNotReady` which signals HA that setup failed for that integration and to try...

I checked the core code, they are disabling failure logging at that stage: https://github.com/home-assistant/core/blob/dev/homeassistant/helpers/update_coordinator.py#L279

I would need to know the modbus register address, size, and type. 1404 is way outside the holding register range that starts at 40000.

I did try naming like that, but reverted it for reasons I can't remember now. It might be in the history. The repair isn't raised during setup, but its easy...