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

only reconnecting after inverter restart #285

Open
Zef-X opened this issue Aug 22, 2024 · 5 comments
Open

only reconnecting after inverter restart #285

Zef-X opened this issue Aug 22, 2024 · 5 comments

Comments

@Zef-X
Copy link

Zef-X commented Aug 22, 2024

Version of the custom_component

0.0.26
SMA Tripower X 25 firmware 03.06.19.R

Configuration

Inverter not active on 192.168.20.103:502
Failed to connect to 192.168.20.103:502 slave id 126

Describe the bug

After restarting HASS or restarting the integration, SunSpec wont connect to Inverter.
Stoping and starting Modbus Server or replugging Ethernet dosnt help.

When restarting Inverter, I get data as intended without problem.
But again, when I wanna change the config SunSpec tells me it can't connect to Inverter even though data is recieved and everything works as intended.

Debug log

2024-08-22 15:11:36.089 WARNING (MainThread) [custom_components.sunspec] Inverter not active on 192.168.20.103:502
2024-08-22 15:12:25.419 WARNING (MainThread) [custom_components.sunspec] Failed to connect to 192.168.20.103:502 slave id 126

@SmileyMan
Copy link

Same. Reverted to 0.0.25

@SmileyMan
Copy link

Temp fix for me was downgrading to 0.0.25 and replacing sensor.py with sensor.py from 0.0.26 (Constants in use by 0.0.25 get removed Jan 2025).

Suspect "Bump pysunspec2 from 1.0.8 to 1.1.5" is the source of this new issue.

@borrelan
Copy link

That worked for me as well. Thank you for pointing me in the right direction @SmileyMan

@eshattow
Copy link

eshattow commented Nov 9, 2024

I see the error "Failed to connect to host (hostname):502 slave 1 - Inverter not active on (hostname):502".

Edit: After removing this integration and installing again, it does not connect anymore. I have used 'mbpoll' utility on another computer to verify that the modbus target is responding to queries. It seems that sunspec integration is just broken about making connections to network hosts and the logs do not show anything more useful to say.

@lpgn
Copy link

lpgn commented Jan 6, 2025

Temp fix for me was downgrading to 0.0.25 and replacing sensor.py with sensor.py from 0.0.26 (Constants in use by 0.0.25 get removed Jan 2025).

Suspect "Bump pysunspec2 from 1.0.8 to 1.1.5" is the source of this new issue.

that worked for me as well downgraded to 0.0.25 and uploaded sensor.py from 0.0.26 Thanks @SmileyMan

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

5 participants