@chris Could this have something to do with multi-channel v3 not being supported in the binding? The manual says the device supports the multi-channel v3 command class, but in the source code of the binding I can only find references to the multi-instance v2 command class.
I’m pretty much a noob regarding Z-wave, so I’m only reporting what I am seeing 
Multi-channel is definitely supported in the binding - not just multi-instance. The extra commands in V3 almost certainly won’t matter. The fact that the report says V0 indicates something else has probably gone wrong. That said, the XML doesn’t show the V0, so I don’t really know what’s causing this without the log…
Sorry - I’ve not had the chance to look at this as I’ve been tied up with other things - I just had a quick look at your log and there’s no debug information included so you’ll need to update this and then I’ll try and take a look to see what’s up.
No worries, I’m happy you’re even trying to help! 
I set the log level to DEBUG and created a new log. The errors mentioned above are in the log file.
@chris Have you had any time to look at this?
Sorry if I’m being pushy, I understand if you are busy and haven’t had the time
Sorry - I missed your previous message (it’s always best to reply or mention me - otherwise there’s no notifications sent).
I’ve just had a quick look in the logs, but there’s really nothing to go on. There’s next to no information from the zwave binding in the log - nothing at all showing any received or transmitted messages (ie no zwave messages) so really I can’t comment much - sorry.
Have you tried deleting the XML and restarting the binding? I would suggest this, and grabbing the debug log during the startup so we can actually see what’s happening during the interrogation period.
@chris Thanks for replying!
I’ve shut down openHAB, removed the XML and restarted openHAB in this new log file.
Also, I tried to use the physical switch again, so that should be in the logs too.
The log files are in this shared folder:
https://stack.lowijs.io/s/1RXvs2J6LGb82ER
Sorry, but there’s no zwave debug information in the log - there are debug messages from other parts of the system, but not the zwave binding…
The log looks fine - is the problem still there? I dont see the error you reported in the log…
@chris Wow, I really suck at making log files, don’t I…
Here the relevant parts of the log:
20:37:36.504 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 02 07 60 0D 01 00 20 01 FF 41
20:37:36.515 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
20:37:36.521 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0D 00 04 00 02 07 60 0D 01 00 20 01 FF 41
20:37:36.527 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0D 00 04 00 02 07 60 0D 01 00 20 01 FF 41
20:37:36.533 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 07 60 0D 01 00 20 01 FF
20:37:36.536 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (DEAD:DONE)
20:37:36.539 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Node is ALIVE. Init stage is DONE.
20:37:36.541 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveNodeStatusEvent
20:37:36.543 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveNodeStatusEvent
20:37:36.546 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Setting ONLINE
20:37:36.554 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 2: Node Status event - Node is ALIVE
20:37:36.557 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
20:37:36.556 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'zwave:device:zwave0:node2' changed from OFFLINE (COMMUNICATION_ERROR): Node is not communicating with controller to ONLINE
20:37:36.559 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@75e1e4 already registered
20:37:36.561 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class MULTI_INSTANCE
20:37:36.563 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Command class MULTI_INSTANCE not found, trying to add it.
20:37:36.565 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Creating new instance of command class MULTI_INSTANCE
20:37:36.569 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Command class MULTI_INSTANCE, endpoint null created
20:37:36.572 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Adding command class MULTI_INSTANCE
20:37:36.574 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Adding command class MULTI_INSTANCE to the list of supported command classes.
20:37:36.577 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 2: Received MULTI_INSTANCE command V0
20:37:36.581 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 2: Requested Command Class = BASIC (0x20)
20:37:36.583 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 2: Endpoint 1 not found. Cannot set command classes.
20:37:36.588 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=2, callback=117, payload=02 03 32 01 00
20:37:36.593 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 07 60 0D 01 00 20 01 FF
20:37:36.596 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=117, expected=ApplicationCommandHandler, cancelled=false transaction complete!
20:37:36.598 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
20:37:36.600 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
20:37:52.510 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0D 00 04 00 02 07 60 0D 01 00 20 01 00 BE
20:37:52.519 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
20:37:52.526 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0D 00 04 00 02 07 60 0D 01 00 20 01 00 BE
20:37:52.533 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0D 00 04 00 02 07 60 0D 01 00 20 01 00 BE
20:37:52.538 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 07 60 0D 01 00 20 01 00
20:37:52.541 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
20:37:52.544 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
20:37:52.546 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@75e1e4 already registered
20:37:52.548 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class MULTI_INSTANCE
20:37:52.550 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 2: Received MULTI_INSTANCE command V0
20:37:52.553 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 2: Requested Command Class = BASIC (0x20)
20:37:52.556 [ERROR] [class.ZWaveMultiInstanceCommandClass] - NODE 2: Endpoint 1 not found. Cannot set command classes.
20:37:52.561 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=2, callback=117, payload=02 03 32 01 00
20:37:52.566 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 07 60 0D 01 00 20 01 00
20:37:52.569 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=117, expected=ApplicationCommandHandler, cancelled=false transaction complete!
20:37:52.572 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
20:37:52.574 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveTransactionCompletedEventNo problem. I checked the last two logs which ran from 07:00 to 14:30 today and there’s no errors. Is this error here from yesterday or today (there’s no date on this log ;)).
I’m just wondering if the problem has gone after resetting the XML which is quite possible as it should re-interrogate the device.
@chris I just forgot to trigger the error in the log before the last snippet. They’re both from today. The problem still exists.
You’ve probably said somewhere above, but I can’t see it (sorry) - what version of the binding are you using? Is this the latest snapshot of the release (or another)?
@chris This is some pre-2.0 release snapshot, but I got the same errors with 2.0 release and latest snapshot. I haven’t tried in a few weeks though, I’ll try to setup a new latest snapshot to see what happens.
@chris I’ve installed the latest 2.1.0 snapshot.
In the new log files you can see me unlinking and relinking the Binary Sensor channel. You’ll see the ‘unsupported multi instance’ error popping up several times.
The ‘endpoint 1 not found’ error seems to be reported as DEBUG now, but it’s there in the logs.
They’re in the shared folder: https://stack.lowijs.io/s/1RXvs2J6LGb82ER
@MLowijs, this is a while ago … did you find any solution on this?
I am just setting up Openhab2 and got stuck with this at the rather beginning …
Regards,
Marcus.
Unfortunately, no. I’m still getting lots of errors with this Thing.
It works fine on other home automation systems… 
Seems like the exact same thing, I was just reading that thread!