Seth

Scanning all possible modbus addresses isn't really practical. With minimum timeouts would take at least 12 minutes, and nobody is going to wait that long for HA to finish startup...

For what it's worth when my system was installed the installers left unit ID settings set to '1', so it's possible that in general it's not well understood why that...

There are commercial size installations using this integration, so we can't make any assumptions about small sites.

> It is my suspicion that distinguishing between an empty response and a lack of response will prove very fruitful in detecting an empty device ID. My inverters don't have...

I've already been working on stuff in regards to invalid IDs from #460 and the wish list has non-consecutive IDs on it, but I've not uploaded anything yet since it's...

I should add that I don't really care if some auto-detect takes 5 minutes to run, but I don't know how HA reacts to long running setups and end users...

PR #518 will raise the repair issue if setup fails, previously it would just raise on connection issues post-setup.

A modbus frame always has its headers, id, function code, and data bytes. TCP only differs from RTU in that modbus TCP doesn't include a checksum after the data bytes...

> The device ids were set by the installer company and I dont want to change them. If you don't want to use a compatible config for right now, then...

Non sequential ID support is already on the project idea list, but there is no timeline for it.