CJNE
only reconnecting after inverter restart
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
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. Thank you for pointing me in the right direction @SmileyMan
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.
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
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.
Wow, it works! Ty! The way I did it was before the downgrade just copied the sensor.py and put it on another folder. Then proceed with the downgrade and replace the file in the same folder. First-time users the folder you're looking is located in custom_components/sunspec/sensor.py in my case, I'm running HAOS on Raspberry py 4.
