-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
WiFi vs Ethernet #53
Comments
I've discovered that I now cannot connect to the modbus. I've tried it from a few different systems but it won't read the input registers (e.g. 5000 + 1000) as it returns illegal address details. The only thing I can pull is the holding registers 4999 + 10 (so I know it's connecting). From the inverter web interface I can read these input registers from the testing page so I know the address is correct. Any ideas? |
This is the error I'm now getting trying to read the input registers.
|
The full debug log. I'm at a loss as to why it's stopped working.
|
Try the latest code which addresses the pymodbus version issue. |
Still get the same error. |
Hi, |
DEBUG:pymodbus.client.sync:Connection to Modbus server established. Socket ('192.168.1.148', 64489) |
This is my exact issue. Perhaps coincidental that it was working and stopped when I went to LAN, but it doesn't matter if I remove LAN now or not. I have the same error log file as you. |
Hi, please see #66, I have created a new library SungrowModbusWebClient to pull the modbus via HTTP requests. It's dirty but I have been running it now for a week. |
I had my inverter connected via Wi-Fi until I had time to run an ethernet cable to it. Switched it over to an ethernet connection and iCloudsolar etc continued to work without issue.
But solaroit.py kept reporting 'Modbus connection failed' and 'Failed to scrape inverter, sleeping until next scan' in the log file.
I'd updated the config.py to the ethernet ip address but it didn't work still. I could run a Modbus poll from another machine without any issue.
Also tried;
I turned wifi back on (and ethernet still on), pointed config.py to the wifi ip, and it started working again.
Why the issue with ethernet?
The text was updated successfully, but these errors were encountered: