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

Cannot connect to SUNNY TRIPOWER 10.0 SE #269

Open
danielbierstedt opened this issue May 22, 2024 · 3 comments
Open

Cannot connect to SUNNY TRIPOWER 10.0 SE #269

danielbierstedt opened this issue May 22, 2024 · 3 comments

Comments

@danielbierstedt
Copy link

Hello,

I cannot connect to an SMA Tripower 10 and cannot figure out why. First thing maybe is that I don't understand the "slave id". I only have the "Unit ID" that is given in the webinterface.
I configure the inverter over webinterface on IP .43, thats where SunSpec received an answer. I suspect the IP and Port to be correct, but the "Slave ID" seems to be wrong.

Any help highly appreciated!

Debug log


Logger: custom_components.sunspec
Source: custom_components/sunspec/config_flow.py:127
integration: SunSpec ([documentation](https://github.com/cjne/ha-sunspec), [issues](https://github.com/cjne/ha-sunspec/issues))
First occurred: 17:03:15 (12 occurrences)
Last logged: 17:32:03

Failed to connect to host 192.168.0.170:502 slave 3 - Failed to connect to 192.168.0.170:502 slave id 3
Failed to connect to host 192.168.0.20:502 slave 3 - Failed to connect to 192.168.0.20:502 slave id 3
Failed to connect to host 192.168.0.43:502 slave 1 - Device responded - not SunSpec register map
Failed to connect to host 192.168.0.43:502 slave 126 - Failed to connect to 192.168.0.43:502 slave id 126
Failed to connect to host 192.168.0.43:502 slave 2 - Device responded - not SunSpec register map

@Sorentino1964
Copy link

I have the same problem!

@Dr-know
Copy link

Dr-know commented Aug 20, 2024

i have the same problem !
I have a SMA Tripower 4.0 firmware 4.0.70.R
is this integration using TCP or UDP ??

Modbus
You can enable the Modbus TCP server and set the TCP port and the Unit ID.
If you would like to use Modbus via UDP, you must turn on the UDP server via Device parameters and set the UDP port.

@SmileyMan
Copy link

I reverted to 0.0.25 and it started working ok again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants