Binding Modbus 2.5.7. Stops working after unsuccessful read attempt

Add-ons Bindings
, ,
77

@bhall sorry to say this but it’s impossible to get to the root of the issue with this little information. To help you, I would need verbose logs from the time it works, and when it starts to not work.

I suggest considering to update your openHAB and binding to stable 2.5.8, now that it is out. This also introduces some small logging fixes that are needed to diagnose traffic using DEBUG level.

You can reduce the amount of logging by

  • lowering poll rate to 30 s
  • simplifying your item configuration, leave only Number HVAC_Temp, DateTime HVAC_Temp_Last_Success and DateTime HVAC_Temp_Last_Error
  • Simplify your things, remove diXX things and leave only the tcp, poller and data reg32768
  • Setting log level to DEBUG instead of TRACE: log:set DEBUG org.openhab.io.transport.modbus and log:set DEBUG org.openhab.binding.modbus.

Let it run as long as needed, so it eventually stops working.

You should see log lines like the below Thing modbus:poller:fc8f3903 received response ...

20:52:32.321 [DEBUG] [dbus.handler.ModbusPollerThingHandler] - Thing modbus:poller:fc8f3903 received response PollResult(result=AsyncModbusReadResult(request = ModbusPollerThingHandler.ModbusPollerReadRequest@412a0b1a[slaveId=1,functionCode=READ_MULTIPLE_REGISTERS,start=0,length=5,maxTries=3], registers = ModbusRegisterArrayImpl(00 00 00 00 00 00 00 00 00 00)))