Replies: 2 comments 1 reply
-
Hi @GolfOWL. Not really a solution, but I might add to this for my own purposes. If you're reading data successfully I might guess they're network hiccups? I get these messages, but I don't see ANY data when I try to connect to the modbus/ESM LAN port on the back of the SH8.0RT I can see it gets an IP address in the router, but the DHCP IP goes to status "offline" "active" and connections on it to port 502 for modbus fail continuously. So, I checked in the configuration of the WiNet-S interface that modbus 502 switch was activated, it was/is. It's the only way I can get some data, though some erroneous data as well (like the charging/discharging state). My perdicament is that polling the WiNet-S LAN IP is not supported by this project. So I'm at a loss here... Is it or is not officially possible from a Sungrow provider perspective to query the ESM/MODBUS LAN port on port 502 (not the WiNet-S LAN port)? Is there anything I am overlooking in my configuration settings in the Inverter (mind you, I only have a few possibilities as my solar provider controls it still)? I really have the feeling that Sungrow are rerouting traffic internally from ESM/Modbus to WiNet-S LAN and it's screwing everything up for me... how else to explain this incapability to connect on ESM/Modbus LAn port 502? (I tried with QModMaster as well, same odds) Cheers all. |
Beta Was this translation helpful? Give feedback.
-
Might sound stupid, but have you tried another network cable? You can query the WiNet-S with the configuration provided by this project, but you'll probably have to comment out some blocks in the Finally, the LAN port is listed in chapter 6.7 of the inverter manual for third party EMS / data logger purposes. So, yes, I'd say it's normal to expect it to work for that purpose. ;-) |
Beta Was this translation helpful? Give feedback.
-
Hello everybody,
I have integrated the ModBus-Integration til last weekend I got the following error 35638x in my HA log file. Did anyone have an idea? Is this "normal" - or have I do something? Many thanks in advance for your help.
Thomas
Logger: homeassistant.components.modbus.modbus
Source: components/modbus/modbus.py:375
Integration: Modbus
First occurred: 25. Januar 2024 um 13:50:45 (35638 occurrences)
Last logged: 14:46:04
Pymodbus: SungrowSHx: Error: device: 1 address: 6601 -> Modbus Error: [Input/Output] Unable to decode request
Pymodbus: SungrowSHx: Error: device: 1 address: 6631 -> Modbus Error: [Input/Output] Unable to decode request
Pymodbus: SungrowSHx: Error: device: 1 address: 13031 -> Modbus Error: [Connection] Failed to connect[ModbusTcpClient(192.168.178.150:502)]
Pymodbus: SungrowSHx: Error: device: 1 address: 5725 -> Modbus Error: [Input/Output] Unable to decode request
Pymodbus: SungrowSHx: Error: device: 1 address: 6226 -> Modbus Error: [Input/Output] Unable to decode request
Beta Was this translation helpful? Give feedback.
All reactions