Thanks Cplant … I tried deleting the lock file as you did but didn’t make any difference … but, I do think think it is somehow related.
In a normal case where the Zwave comes up (less than 50/50 now) … the debug log shows:
2022-08-01 17:32:35.298 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyUSB0'
2022-08-01 17:32:35.321 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Starting receive thread
2022-08-01 17:32:35.331 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Starting ZWave thread: Receive
2022-08-01 17:32:35.331 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
2022-08-01 17:32:35.333 [DEBUG] [zwave.handler.ZWaveControllerHandler] - Initialising ZWave controller
2022-08-01 17:32:35.393 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-08-01 17:32:35.394 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
2022-08-01 17:32:35.396 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2022-08-01 17:32:35.396 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
However, in the failed case (just now) it shows only:
2022-08-02 15:58:41.420 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyUSB0'
And no other messages … so clearly it is not receiving any data from the Zwave device.
Are there any experts in this area that can comment? I have seen other threads talking about a recent issue with Serial Manager on OH3, but I have no idea if its related.
I have not tried the ser2net workaround … my problem is intermittent (sometimes works) … so not sure if it is the same isssue.