As @xsnrg said, we were discussing this offline, but I figured others would benefit from the discussion - or my analyses of the result.
Firstly, debug logs are imperative to work out what’s up. In this case, the errors are caused by timeouts to device requests or config parameters - ultimately caused by database errors.
So, to analyse this issue, I would strongly recommend running your debug logs into the log view. This should help you visualise what is happening in a reasonably easy to digest way. From Jims log, we see things like the following -:
This shows timeouts on node 14. We can see that openHAB is sending a CONFIGURATION_GET command - the “Send OK” message means the controller accepted the message, and the “ACK’d by device” message means the device received the command. However, we time out, so either we just happened to miss the response, or, the device didn’t send one. We can assume the latter given this happens multiple times.
This is an annoying feature of ZWave - when a device doesn’t process a request, it doesn’t respond at all - personally I’d prefer if it sent a NAK so we know! Anyway, we can now assume (hopefully correctly!) that node 14 doesn’t have a parameter 2, and we should update this in the database to solve this problem.
We also see the same thing for parameter 100 of node 6 further down, and the same for parameter 255 - in this case, I believe this is a ZW100, and these parameters should be set to write only
as they are reset commands.
So, I would urge people to use the log viewer if you are seeing issues like this - it should help to debug any problems in the binding, and the database.