The web UI for the Waveshare is also usually very slow to respond - 10-15 seconds when selecting a menu item, for example.
I am using the FoxESS-Modbus integration, and the Waveshare adapter is connected via ethernet. The pattern seems to be that it (eventually) connects to the Waveshare, retrieves the values for Force Charge and Force Discharge, then reports alot of "became unavailable" messages, and none of the other Control or Sensor data is populated.
These are the two most common errors that I see in the Activity log:
Code: Select all
FoxESS - Modbus (FoxESS-KH7) Connection Status (FoxESS-KH7) changed to Modbus Error: [Connection] Failed to connect[CustomModbusTcpClient 192.168.1.254:502]Code: Select all
FoxESS - Modbus (FoxESS-KH7) Connection Status (FoxESS-KH7) changed to Error reading registers. Type: RegisterType.HOLDING; start: 31000; count: 4; slave: 247 from tcp://192.168.1.254:502: Modbus Error: [Input/Output] No Response received from the remote slave/Unable to decode response