Open Stony111 opened 3 months ago
The integration currently uses the host or IP to determine duplicates, even if the port is different.
It's on the to-do list to update this
Thanks a lot for the fast info. Do you have a plan for when you would implement it? Just so I can judge whether it's worth waiting ;-)
I don't have an estimated time right now, but I would probably work on it after the non-sequential inverter ID changes.
Describe the bug
System architecture is like follow described:
When I now want to configure the second inverter, the IP-Adress is the same, as of Inverter 1, because it's always the IP-Adress of ModBusProxy-Instance 192.168.0.3 - but the Port would be different: 2502 for Inverter 1 and 2503 for Inverter 2.
When I want to save the new Hub Configuration an error appears: Inverter is already configured! I think in this check only IP-Adress is validated not the combination of IP-Adress and Port
Expected behavior
Creating a complete new Hub Instance of a second standalone Inverter, when Connection to all Inverters are handled via ModBusProxy!
Screenshots
Diagnostic File
There is no diagnostic file - its only a UI / check Problem.
Debug logs
No response
Home Assistant Version
2024.7.3
solaredge-modbus-multi Version
2.4.18
Installation Type
HAOS
Read the Instructions
Additional Context
No response