Modbus error decoding or received no data (TCP/IP)!

[jg117945]

It seems that the logs here below have started with the upgrade to latest domoticz version. I’m currently running:

Version: 2024.4
Build Hash: 731719420
Compile Date: 2024-01-30 09:16:34
dzVents Version: 3.1.8
Python Version: 3.7.3 (default, Oct 11 2023, 09:51:27) [GCC 8.3.0]

I have a sunny tri power 10kw and haven’t changed any configuration nor on the tri-power nor in domoticz for years.

Sometimes the devices updates correctly in domoticz, sometimes not.

Here the log I have with debug tcp:

2024-02-02 14:17:42.625 Sun: MODBUS DEBUG RESPONSE: None
2024-02-02 14:17:42.625 Sun: MODBUS DEBUG - VALUE before conversion: None
2024-02-02 14:17:42.625 (Sun power) Updating device from 1:'0' to have values 1:'0'.
2024-02-02 14:17:42.644 (Sun power) Updating device from 1:'0' to have values 1:'0'.
2024-02-02 14:17:42.657 Sun: Acquiring GIL for 'onHeartbeatCallback'
2024-02-02 14:17:42.708 Sun: Pushing 'onHeartbeatCallback' on to queue
2024-02-02 14:17:42.758 Sun: Processing 'onHeartbeatCallback' message
2024-02-02 14:17:42.758 Sun: Acquiring GIL for 'onHeartbeatCallback'
2024-02-02 14:17:42.758 Sun: Calling message handler 'onHeartbeat' on 'module' type object.
2024-02-02 14:17:42.758 Sun: onHeartbeat called
2024-02-02 14:17:42.758 Sun: MODBUS DEBUG - INTERFACE: IP=192.168.1.20, Port=502
2024-02-02 14:17:42.758 Sun: MODBUS DEBUG - SETTINGS: Method=tcpip, Device ID=33, Register=30775, Function=4, Data type=int32, Pollrate=1
2024-02-02 14:17:42.625 Error: Sun: Modbus error decoding or received no data (TCP/IP)!, check your settings!
2024-02-02 14:17:42.644 Error: Sun: Modbus error decoding or received no data!, check your settings!
2024-02-02 14:17:44.766 Sun: MODBUS DEBUG RESPONSE: None
2024-02-02 14:17:44.766 Sun: MODBUS DEBUG - VALUE before conversion: None
2024-02-02 14:17:44.767 (Sun power) Updating device from 1:'0' to have values 1:'0'.
2024-02-02 14:17:44.786 (Sun power) Updating device from 1:'0' to have values 1:'0'.
2024-02-02 14:17:44.794 Sun: Acquiring GIL for 'onHeartbeatCallback'
2024-02-02 14:17:44.844 Sun: Pushing 'onHeartbeatCallback' on to queue
2024-02-02 14:17:44.895 Sun: Processing 'onHeartbeatCallback' message
2024-02-02 14:17:44.895 Sun: Acquiring GIL for 'onHeartbeatCallback'
2024-02-02 14:17:44.895 Sun: Calling message handler 'onHeartbeat' on 'module' type object.
2024-02-02 14:17:44.895 Sun: onHeartbeat called
2024-02-02 14:17:44.895 Sun: MODBUS DEBUG - INTERFACE: IP=192.168.1.20, Port=502
2024-02-02 14:17:44.895 Sun: MODBUS DEBUG - SETTINGS: Method=tcpip, Device ID=33, Register=30775, Function=4, Data type=int32, Pollrate=1
2024-02-02 14:17:44.767 Error: Sun: Modbus error decoding or received no data (TCP/IP)!, check your settings!
2024-02-02 14:17:44.786 Error: Sun: Modbus error decoding or received no data!, check your settings!
2024-02-02 14:17:45.019 Sun: Pushing 'onStopCallback' on to queue
2024-02-02 14:17:45.019 Status: Sun: Stop directive received.
2024-02-02 14:17:46.899 Sun: MODBUS DEBUG RESPONSE: None
2024-02-02 14:17:46.899 Sun: MODBUS DEBUG - VALUE before conversion: None
2024-02-02 14:17:46.900 (Sun power) Updating device from 1:'0' to have values 1:'0'.
2024-02-02 14:17:46.913 (Sun power) Updating device from 1:'0' to have values 1:'0'.
2024-02-02 14:17:46.925 Sun: Acquiring GIL for 'onHeartbeatCallback'
2024-02-02 14:17:46.925 Sun: Processing 'onStopCallback' message
2024-02-02 14:17:46.925 Sun: Acquiring GIL for 'onStopCallback'
2024-02-02 14:17:46.926 Sun: Calling message handler 'onStop' on 'module' type object.
2024-02-02 14:17:46.926 Sun: onStop called
2024-02-02 14:17:46.900 Error: Sun: Modbus error decoding or received no data (TCP/IP)!, check your settings!
2024-02-02 14:17:46.913 Error: Sun: Modbus error decoding or received no data!, check your settings!

any help would be greatly appreciated.

Regards

Hardware configuration is:

[pizzulicchio]

I have got the same problem when i'm searching to acquire data from my SAJ solar inverter . The AIO3 module ( a modbus wifi adapter ) seems to stop responding after some requests... and come back online after some seconds or minutes.

Is it possible to keep the previous data (latest good value) instead of set to zero when it's impossible to acquire data or in timeout?
Otherwise , every timeout it's a zero value... and it's a pita.