Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Two separate SE Inverters not possible over ModBusProxy #638

Open
3 tasks done
Stony111 opened this issue Jul 30, 2024 · 3 comments
Open
3 tasks done

Two separate SE Inverters not possible over ModBusProxy #638

Stony111 opened this issue Jul 30, 2024 · 3 comments
Assignees
Labels
update Update or change to something

Comments

@Stony111
Copy link

Stony111 commented Jul 30, 2024

Describe the bug

System architecture is like follow described:

  • SE Inverter 1 with Meter and Battery on IP-Adress 192.168.0.1 - Port 1502 (for example)
  • SE Inverter 2 (no Meter no Battery) on IP-Adress 192.168.0.2 - Port 1502 (for example)
  • Both Inverters NOT connected together via RS485 - both runs complete separate
  • ModbusProxy, which manage both IP-Adresses; IP-Adress of ModBusProxy Instance 192.168.0.3 (for example)
    ++ Inverter 1 is listen on port 2502 on this proxy
    ++ Inverter 2 is listen on port 2503 on this proxy
  • Home Assistant with this integration

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

grafik

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

@WillCodeForCats
Copy link
Owner

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

@WillCodeForCats WillCodeForCats self-assigned this Jul 30, 2024
@Stony111
Copy link
Author

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 ;-)

@WillCodeForCats
Copy link
Owner

I don't have an estimated time right now, but I would probably work on it after the non-sequential inverter ID changes.

@WillCodeForCats WillCodeForCats added the update Update or change to something label Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
update Update or change to something
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants