Zwave stops processing messages

Add-ons Bindings
1

Hello! This will be my first post on the OpenHAB forums and I’m still new to the entire OH system, so excuse me if I’m missing information in this post.

I’ve been working on experimenting with OH2 for several months now and have made significant progress with the implementation of control of my varying systems.

However this brings me to the most important part of any OH setup! Environment input, and unfortunately I can’t quite figure this one out. Below are the details about my issue along with logging information.

I’m experiencing an issue where the zwave binding (Ver. 2.0.0) stops processing messages from my test node, a Fibaro motion sensor (FGMS-001 ZW5). After restarting the binding through the bundle:restart command in the Karaf console, it resumes working for a short period of time only with the same result. I’ve snooped the serial controllers connection and I can see it still receiving the messages from the sensor, but OH has no reaction (at least none that I can see via the debug logging of the binding). Below is a log starting after the initialization from the bundle:restart, to the point it stops processing messages.

My environment is an Ubuntu 16.04.2 LTS based server, running Java 1.8.0_131 x86, on an ESXi 6.5 VM, OH2 was installed via package manager and the binding was installed via the installer within OH2 Paper UI.

I’ve searched high and low for a resolution and haven’t find anything with this issue and have hit a brick wall with it…

Anyone that could lend a hand with this issue, I’d greatly appreciate the help!

2017-05-21 04:02:34.819 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 02 0A 71 05 00 00 00 FF 07 00 01 03 6D
2017-05-21 04:02:34.823 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-05-21 04:02:34.823 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 02 0A 71 05 00 00 00 FF 07 00 01 03 6D
2017-05-21 04:02:34.823 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 02 0A 71 05 00 00 00 FF 07 00 01 03 6D
2017-05-21 04:02:34.823 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 0A 71 05 00 00 00 FF 07 00 01 03
2017-05-21 04:02:34.823 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (FAILED:WAIT)
2017-05-21 04:02:34.823 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Node is ALIVE. Init stage is WAIT.
2017-05-21 04:02:34.823 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveNodeStatusEvent
2017-05-21 04:02:34.823 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Node Status event during initialisation - Node is ALIVE
2017-05-21 04:02:34.823 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Node advancer - WAIT: queue length(0), free to send(true)
2017-05-21 04:02:34.823 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Node advancer: loop - WAIT try 1: stageAdvanced(false)
2017-05-21 04:02:34.823 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Node advancer: WAIT - Listening=false, FrequentlyListening=false
2017-05-21 04:02:34.823 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 2: Node advancer: WAIT - Still waiting!
2017-05-21 04:02:34.823 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2017-05-21 04:02:34.823 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Setting ONLINE
2017-05-21 04:02:34.823 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 2: Node Status event - Node is ALIVE
2017-05-21 04:02:34.824 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class ALARM
2017-05-21 04:02:34.824 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Received ALARM command V5
2017-05-21 04:02:34.824 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Process NOTIFICATION_REPORT V5
2017-05-21 04:02:34.824 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 0 = 0, event=0, status=255
2017-05-21 04:02:34.824 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = BURGLAR (0)
2017-05-21 04:02:34.824 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2017-05-21 04:02:34.824 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-05-21 04:02:34.824 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value =
255
2017-05-21 04:02:34.824 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-05-21 04:02:34.824 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 0, type OnOffType
2017-05-21 04:02:34.824 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:b39a3f42:node2:alarm_motion to OFF [OnOffType]
2017-05-21 04:02:34.824 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-05-21 04:02:34.824 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 0, type OnOffType
2017-05-21 04:02:34.824 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:b39a3f42:node2:alarm_tamper to OFF [OnOffType]
2017-05-21 04:02:34.824 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 255: Transaction not completed: node address inconsistent.  lastSent=255, incoming=255
2017-05-21 04:02:38.504 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 02 09 71 05 00 00 00 FF 07 03 00 70
2017-05-21 04:02:38.508 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-05-21 04:02:38.508 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0F 00 04 00 02 09 71 05 00 00 00 FF 07 03 00 70
2017-05-21 04:02:38.508 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0F 00 04 00 02 09 71 05 00 00 00 FF 07 03 00 70
2017-05-21 04:02:38.508 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 09 71 05 00 00 00 FF 07 03 00
2017-05-21 04:02:38.508 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:WAIT)
2017-05-21 04:02:38.508 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class ALARM
2017-05-21 04:02:38.508 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Received ALARM command V5
2017-05-21 04:02:38.508 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Process NOTIFICATION_REPORT V5
2017-05-21 04:02:38.508 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 0 = 0, event=3, status=255
2017-05-21 04:02:38.508 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = BURGLAR (0)
2017-05-21 04:02:38.509 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2017-05-21 04:02:38.509 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-05-21 04:02:38.509 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value =
255
2017-05-21 04:02:38.509 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-05-21 04:02:38.509 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 3, type OnOffType
2017-05-21 04:02:38.509 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-05-21 04:02:38.509 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 3, type OnOffType
2017-05-21 04:02:38.509 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:b39a3f42:node2:alarm_tamper to ON [OnOffType]
2017-05-21 04:02:38.509 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 255: Transaction not completed: node address inconsistent.  lastSent=255, incoming=255
2017-05-21 04:03:08.676 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 02 0A 71 05 00 00 00 FF 07 00 01 03 6D
2017-05-21 04:03:08.680 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-05-21 04:03:08.680 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 02 0A 71 05 00 00 00 FF 07 00 01 03 6D
2017-05-21 04:03:08.680 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 02 0A 71 05 00 00 00 FF 07 00 01 03 6D
2017-05-21 04:03:08.681 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 0A 71 05 00 00 00 FF 07 00 01 03
2017-05-21 04:03:08.681 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:WAIT)
2017-05-21 04:03:08.681 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class ALARM
2017-05-21 04:03:08.681 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Received ALARM command V5
2017-05-21 04:03:08.681 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Process NOTIFICATION_REPORT V5
2017-05-21 04:03:08.681 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 0 = 0, event=0, status=255
2017-05-21 04:03:08.681 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = BURGLAR (0)
2017-05-21 04:03:08.681 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2017-05-21 04:03:08.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-05-21 04:03:08.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value =
255
2017-05-21 04:03:08.681 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-05-21 04:03:08.681 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 0, type OnOffType
2017-05-21 04:03:08.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:b39a3f42:node2:alarm_motion to OFF [OnOffType]
2017-05-21 04:03:08.681 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-05-21 04:03:08.681 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 0, type OnOffType
2017-05-21 04:03:08.682 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:b39a3f42:node2:alarm_tamper to OFF [OnOffType]
2017-05-21 04:03:08.682 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 255: Transaction not completed: node address inconsistent.  lastSent=255, incoming=255
2017-05-21 04:03:10.236 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 02 09 71 05 00 00 00 FF 07 03 00 70
2017-05-21 04:03:10.239 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-05-21 04:03:10.239 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0F 00 04 00 02 09 71 05 00 00 00 FF 07 03 00 70
2017-05-21 04:03:10.239 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0F 00 04 00 02 09 71 05 00 00 00 FF 07 03 00 70
2017-05-21 04:03:10.240 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 09 71 05 00 00 00 FF 07 03 00
2017-05-21 04:03:10.240 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:WAIT)
2017-05-21 04:03:10.240 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class ALARM
2017-05-21 04:03:10.240 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Received ALARM command V5
2017-05-21 04:03:10.240 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Process NOTIFICATION_REPORT V5
2017-05-21 04:03:10.240 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 0 = 0, event=3, status=255
2017-05-21 04:03:10.240 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = BURGLAR (0)
2017-05-21 04:03:10.240 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2017-05-21 04:03:10.240 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-05-21 04:03:10.240 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value =
255
2017-05-21 04:03:10.240 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-05-21 04:03:10.240 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 3, type OnOffType
2017-05-21 04:03:10.240 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-05-21 04:03:10.240 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 3, type OnOffType
2017-05-21 04:03:10.240 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:b39a3f42:node2:alarm_tamper to ON [OnOffType]
2017-05-21 04:03:10.240 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 255: Transaction not completed: node address inconsistent.  lastSent=255, incoming=255
2017-05-21 04:03:40.542 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 02 0A 71 05 00 00 00 FF 07 00 01 03 6D
2017-05-21 04:03:40.547 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-05-21 04:03:40.547 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 02 0A 71 05 00 00 00 FF 07 00 01 03 6D
2017-05-21 04:03:40.547 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 02 0A 71 05 00 00 00 FF 07 00 01 03 6D
2017-05-21 04:03:40.547 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 0A 71 05 00 00 00 FF 07 00 01 03
2017-05-21 04:03:40.547 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:WAIT)
2017-05-21 04:03:40.547 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class ALARM
2017-05-21 04:03:40.547 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Received ALARM command V5
2017-05-21 04:03:40.547 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Process NOTIFICATION_REPORT V5
2017-05-21 04:03:40.547 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 0 = 0, event=0, status=255
2017-05-21 04:03:40.547 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = BURGLAR (0)
2017-05-21 04:03:40.547 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2017-05-21 04:03:40.547 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-05-21 04:03:40.547 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value =
255
2017-05-21 04:03:40.548 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-05-21 04:03:40.548 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 0, type OnOffType
2017-05-21 04:03:40.548 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:b39a3f42:node2:alarm_motion to OFF [OnOffType]
2017-05-21 04:03:40.548 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-05-21 04:03:40.548 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 0, type OnOffType
2017-05-21 04:03:40.548 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:b39a3f42:node2:alarm_tamper to OFF [OnOffType]
2017-05-21 04:03:40.548 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 255: Transaction not completed: node address inconsistent.  lastSent=255, incoming=255
2017-05-21 04:03:41.059 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 02 09 71 05 00 00 00 FF 07 03 00 70
2017-05-21 04:03:41.064 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-05-21 04:03:41.064 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0F 00 04 00 02 09 71 05 00 00 00 FF 07 03 00 70
2017-05-21 04:03:41.064 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0F 00 04 00 02 09 71 05 00 00 00 FF 07 03 00 70
2017-05-21 04:03:41.064 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 09 71 05 00 00 00 FF 07 03 00
2017-05-21 04:03:41.064 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:WAIT)
2017-05-21 04:03:41.064 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Incoming command class ALARM
2017-05-21 04:03:41.064 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Received ALARM command V5
2017-05-21 04:03:41.064 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Process NOTIFICATION_REPORT V5
2017-05-21 04:03:41.064 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: NOTIFICATION report - 0 = 0, event=3, status=255
2017-05-21 04:03:41.064 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Alarm Type = BURGLAR (0)
2017-05-21 04:03:41.064 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2017-05-21 04:03:41.064 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-05-21 04:03:41.065 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value =
255
2017-05-21 04:03:41.065 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-05-21 04:03:41.065 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 3, type OnOffType
2017-05-21 04:03:41.065 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2017-05-21 04:03:41.065 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 3, type OnOffType
2017-05-21 04:03:41.065 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:b39a3f42:node2:alarm_tamper to ON [OnOffType]
2017-05-21 04:03:41.065 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 255: Transaction not completed: node address inconsistent.  lastSent=255, incoming=255
2

The log looks ok - it’s not stopping half way through processing a message or anything so I don’t think there’s an exception. However I would check to see if there are there any exceptions showing in the logs, or in the Karaf console?

VMs have been known to have problems with serial ports, so this is my best guess at what the problem could be. I would suggest to search around the forum to see what others have found when running serial apps under a VM.

3

Hi,

Did you recently upgrade to ESX 6.5? There is a known issue with virtual usb ports and USB passtrough trough virtual machines.

You can try the old usb drivers here: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2147650

If you search the internet you find more people with USB (disk drives, serial dongeles, card readers) passtrough problems on the new ESXi 6.5 usb drivers.

Hope this helps,
Best regards,
Wouter

1 Like
4

ESXi 6.5 has problems with USB, I’ve had the exact same problems in the past when running FHEM on ESXi 6.5, it suddenly stops working. The log on the hypervisor shows USB errors.

I managed to fix it by reconfiguring the VM, I stopped using USB passthrough and used passthrough on the USB controller instead as a PCI device. This fixed all problems. Unfortunately this also means that you have to reserve some physical memory for the VM, otherwise PCI passthrough won’t work. It also means that the VM gets access to all USB ports on the physical host that are controlled by the USB controller.

5

Hi guys,

Thank you all for your help! I was beginning to pull my hair out over this, and didn’t even think to look at ESXi!

@Stripe68 I attempted your solution first, since I have other devices on this server (I use it for managing all of my other systems within my home) with no avail unfortunately. I was able to get the zwave controller to communicate through to the VM but unreliably when having to remove the controller from the chassis to add additional devices.

@Woutch your solution was the ultimate solution to this. After playing with it for a bit once I made the change to the ESXi drivers, it began working consistently and so far (it’s been about 4 hours now) continuously. Since I have other VM’s on this server I couldn’t fathom it actually being ESXi so I greatly appreciate your suggestion.

I’ll continue to monitor for any more issues with this and update here if I find more, and of course the solution if I’m able to track it down and resolve it.

Thank you both again for your help! And big thanks to @chris for all the hard work developing the binding of course!