OH2 and Z-Wave not working, no include mode

[msi (Marcel)]

Hello,

I had a working Z-Wave setup with OpenHAB 1.1 in the beginnig of this year. After I talked to @teichsta on a conference some months ago, I decided to give OH2 a try and wanted to start with the Z-Wave devices I configured the last time.
So I have got a Raspberry Pi 3 with 2016-05-10-raspbian-jessie and updates and latest OH2. I connected a Z-Wave.me UZB Stick and two Switches (a Fibaro Wall Plug FGWPF-102 and a Duewi Switch which i think is discontinued now). So, the two switches were included under the old setup and OH2 with Habmin installed sees the 3 devices. But I cannot find the include button wich, according to http://www.cd-jackson.com/index.php/openhab/habmin/10-habmin-zwave-binding-initialisation should exist. And I cannot manually switch the switches by clicking on the Switch item in the item description, but it produces these log messages:
2016-06-26 19:18:00.029 [ItemStateChangedEvent ] - Wifi_Level changed from 1 to 0 2016-06-26 19:18:00.624 [ItemCommandEvent ] - Item 'zwave_device_cb8c2742_node4_switch_binary' received command OFF 2016-06-26 19:18:00.638 [ItemStateChangedEvent ] - zwave_device_cb8c2742_node4_switch_binary changed from ON to OFF 2016-06-26 19:18:01.839 [ItemCommandEvent ] - Item 'zwave_device_cb8c2742_node4_switch_binary' received command ON 2016-06-26 19:18:01.853 [ItemStateChangedEvent ] - zwave_device_cb8c2742_node4_switch_binary changed from OFF to ON
So it looks like something basic is missing. Any idea?
Thanks in advance
Marcel

[chris (Chris Jackson)]

The include button should be there (I don’t think it can be disabled or hidden at all!), and once the controller is added, it should add ZWave to the list once you press the button.

Can you provide a screenshot of what you’re seeing?

[msi (Marcel)]

This is what I can see. The “+”-Looking-Glass-“Add”-Menu is empty…

[chris (Chris Jackson)]

@msi

The “+”-Looking-Glass-“Add”-Menu is empty.

This is because the controller isn’t yet initialised - you need to work out why this is first.

[msi (Marcel)]

Thanks, Chris,
I was just browsing through the logs, fetching relevant information as the devices changed their status to green. So, I just had to wait 10 to 15 minutes or something. Strange. Anyway. I could activate the include mode and include another device. This is now shown as “Node 5 - Unknown Device” although it is the same device as the other Fibaro plug (bought later, so maybe a different revision), but without manufacturer and type id. Shouldn’t at least these be there?
^
There are some log messages regarding the device which look like it’s not recognized correctly:
22:12:50.867 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 5: Timeout while sending message. Requeueing - 0 attempts left! 22:12:50.868 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 5: Got an error while sending data. Resending message. 22:12:51.147 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 5: Unsupported command class MULTI_INSTANCE_ASSOCIATION 22:12:53.371 [INFO ] [ommandclass.ZWaveVersionCommandClass] - NODE 5: Command Class NO_OPERATION has version 0! 22:12:54.248 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing 'zwave:device:cb8c2742:node5' has been updated.

[chris (Chris Jackson)]

@msi

So, I just had to wait 10 to 15 minutes or something.

Strange - the controller should normally start quickly (ie immediately).

@msi

Shouldn’t at least these be there?

Yes - it should. Can you provide a debug log?

@msi

There are some log messages regarding the device which look like it’s not recognized correctly:

I don’t think there’s anything that says it’s not being recognised correctly. Timeouts will happen occasionally.

What version of the binding are you using?

[msi (Marcel)]

@chris

Shouldn’t at least these be there?

Yes - it should. Can you provide a debug log?

i did
log:set debug org.openhab.binding.zwave log:display zwave
and got this when starting

22:57:42.306 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 4: Sending REQUEST Message = 01 08 00 13 04 01 00 25 17 D3
22:57:42.315 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
22:57:42.316 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
22:57:42.318 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
22:57:42.318 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
22:57:42.319 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
22:57:42.320 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 4: Sent Data successfully placed on stack.
22:57:42.331 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 17 00 00 02 FE
22:57:42.333 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
22:57:42.334 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 17 00 00 02 00 00 F0
22:57:42.335 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 17 00 00 02 00 00 F0
22:57:42.336 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=17 00 00 02
22:57:42.336 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 4: SendData Request. CallBack ID = 23, Status = Transmission complete and ACK received(0)
22:57:42.337 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: Starting initialisation from DONE
22:57:42.338 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1e410bd already registered
22:57:42.340 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Poll, dest=4, callback=23, payload=04 01 00
22:57:42.341 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=17 00 00 02
22:57:42.341 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=23, expected=SendData, cancelled=false        transaction complete!
22:57:42.342 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
22:57:42.342 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
22:57:42.343 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 4: Response processed after 36ms/1050ms.
22:57:42.343 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 1
22:57:42.344 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 13 04 01 00 25 17 D3
22:57:42.344 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 4: Sending REQUEST Message = 01 08 00 13 04 01 00 25 17 D3
22:57:42.354 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
22:57:42.355 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
22:57:42.356 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
22:57:42.357 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
22:57:42.357 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
22:57:42.358 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 4: Sent Data successfully placed on stack.
22:57:42.371 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 17 00 00 03 FF
22:57:42.374 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
22:57:42.375 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 17 00 00 03 00 00 F1
22:57:42.376 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 17 00 00 03 00 00 F1
22:57:42.377 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=17 00 00 03
22:57:42.385 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 4: SendData Request. CallBack ID = 23, Status = Transmission complete and ACK received(0)
22:57:42.386 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 4: Starting initialisation from DONE
22:57:42.387 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@1e410bd already registered
22:57:42.388 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Poll, dest=4, callback=23, payload=04 01 00
22:57:42.389 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=17 00 00 03
22:57:42.389 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=23, expected=SendData, cancelled=false        transaction complete!
22:57:42.390 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
22:57:42.390 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
22:57:42.391 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 4: Response processed after 46ms/1050ms.
22:57:42.391 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
22:57:42.392 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 13 05 01 00 25 09 CC
22:57:42.393 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 5: Sending REQUEST Message = 01 08 00 13 05 01 00 25 09 CC
22:57:42.404 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
22:57:42.406 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
22:57:42.406 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
22:57:42.407 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
22:57:42.407 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
22:57:42.408 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 5: Sent Data successfully placed on stack.
22:57:42.544 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 09 00 00 0F ED
22:57:42.557 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
22:57:42.558 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 09 00 00 0F 00 00 E3
22:57:42.559 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 09 00 00 0F 00 00 E3
22:57:42.559 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=09 00 00 0F
22:57:42.560 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 5: SendData Request. CallBack ID = 9, Status = Transmission complete and ACK received(0)
22:57:42.560 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 5: Starting initialisation from DONE
22:57:42.560 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@fcacb9 already registered
22:57:42.561 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Poll, dest=5, callback=9, payload=05 01 00
22:57:42.561 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=09 00 00 0F
22:57:42.562 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=9, expected=SendData, cancelled=false        transaction complete!
22:57:42.562 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
22:57:42.562 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
22:57:42.563 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 5: Response processed after 168ms/1050ms.

(by the way: is it on purpose that you can’t upload plain txt files?)

@chris

What version of the binding are you using?

202 | Active | 80 | 2.0.0.b3 | ZWave Binding
206 | Active | 80 | 0.8.0.201606191001 | HABmin User Interface

Is that the information you wanted?

Thanks a lot
Marcel

[chris (Chris Jackson)]

@msi

202 | Active | 80 | 2.0.0.b3 | ZWave Binding

It would be worth upgrading the binding to a more recent version. I’m not sure it will solve the issue as I’m still looking into this problem, but it might help as there have been some updates since beta 3.

[msi (Marcel)]

@chris

It would be worth upgrading the binding to a more recent version. I’m not sure it will solve the issue as I’m still looking into this problem, but it might help as there have been some updates since beta 3

I tried upgrading the binding. I formerly installed OH2 from the apt repository, So I think there is not official “apt way” to upgrade. Not knowing if that is the right way, I replaced the old binding jar by /usr/share/openhab2/runtime/karaf/system/org/openhab/binding/org.openhab.binding.zwave/2.0.0-SNAPSHOT/org.openhab.binding.zwave-2.0.0-SNAPSHOT.jar, but karaf still reports 202 | Active | 80 | 2.0.0.b3 | ZWave Binding, so I think the upgrade didn’t work. I didn’t find any other zwave*jar on the RPis file system.
But I discovered /var/lib/openhab2/zwave/node[3|5].xml and found out that they are identical (except timestamps and node ids). I excluded and re-included the “Unknown device”, but that didn’t change anything.

[msi (Marcel)]

I installed a fresh version (downloaded OH2-Offline snapshot from monday (2016-06-27) evening - Z-Wave binding 2.0.0.201606271619) in parallel, started it with just Z-Wave binding activated and that installation sees the new node (node 5 above) and can also switch the wall plug. So I had another new wall plug and wanted to include that one also. Same as for the other new one, shown as unknown device (Node 6 now), The node-xml is a bit different this time.^
The log for inclusion:

19:47:20.038 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Initialising Thing Node...
19:47:20.051 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Initialising Thing Node...
19:47:21.647 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising Thing Node...
19:47:21.675 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising Thing Node...
19:47:34.204 [ERROR] [ve.internal.protocol.ZWaveController] - Neither inclusion nor exclusion was active!
19:47:53.222 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 6: Unsupported command class MULTI_INSTANCE_ASSOCIATION
19:47:53.890 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:15598d1fccc:node6' to inbox.
19:47:53.917 [ERROR] [WaveSerialHandler$ZWaveReceiveThread] - Protocol error (CAN), resending
19:47:53.921 [WARN ] [rialmessage.IdentifyNodeMessageClass] - Got IdentifyNodeMessage without request, ignoring. Last message was SendData.
19:47:58.914 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 6: Timeout while sending message. Requeueing - 2 attempts left!
19:47:58.915 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Got an error while sending data. Resending message.
19:48:03.926 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 6: Timeout while sending message. Requeueing - 1 attempts left!
19:48:03.928 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Got an error while sending data. Resending message.
19:48:08.938 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 6: Timeout while sending message. Requeueing - 0 attempts left!
19:48:08.939 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Got an error while sending data. Resending message.
19:48:09.067 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising Thing Node...
20:47:19.635 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 3: Timeout while sending message. Requeueing - 2 attempts left!
20:47:19.637 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 3: Got an error while sending data. Resending message.
21:22:37.161 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 6: Timeout while sending message. Requeueing - 0 attempts left!
21:22:37.171 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Got an error while sending data. Resending message.
21:22:37.374 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 6: Unsupported command class MULTI_INSTANCE_ASSOCIATION

node5.xml (11.7 KB)

node6.xml (10.7 KB)

The network view looks like the node is not working:

Strange things…

[chris (Chris Jackson)]

It’s hard to tell what’s happening without a debug log, but it does look like commands are timing out for some reason. This could be network topology - looking at the plot it looks like nodes 3/4/5 can’t talk to node 6, but this may just be because the neighbour lists haven’t all updated after node 6 was added.

[msi (Marcel)]

Thank you Chris.

openhab2-zwave-debug.xml (969.4 KB)

Node 6 and the other ares are seeing each other by now, but Node 6 is still unknown. I attached the debug output of starting up OH2. Looks like the thread Fibaro FGMS-001 Showing as Unknown Device could be a similar problem?

[chris (Chris Jackson)]

At least in this log, I don’t see the initialisation proceeding, so the binding doesn’t know the manufacturer and device IDs. I guess given you have an XML, that it has done this previously.

What happens if you don’t add the thing - just include the device, but when it appears in the inbox, don’t add it. Does it finally get found?

[msi (Marcel)]

Unfortunately i cannot exclude the devices (not the unknown and not the correctly recognized). This is for a correct one:

22:45:10.982 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration update received
22:45:11.032 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Configuration update action_remove to -232323.0
22:45:11.034 [DEBUG] [message.RemoveFailedNodeMessageClass] - NODE 5: Marking node as having failed.
22:45:11.035 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
22:45:11.036 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 0. Queue={}
22:45:11.036 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 61 05 01 9F
22:45:11.037 [DEBUG] [rialmessage.IsFailedNodeMessageClass] - NODE 5: Requesting IsFailedNode status from controller.
22:45:11.038 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 61 05 01 9F
22:45:11.038 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
22:45:11.132 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 61 08 93
22:45:11.134 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
22:45:11.135 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 61 08 93
22:45:11.136 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 61 08 93
22:45:11.138 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=RemoveFailedNodeID[0x61], type=Response[0x01], priority=High, dest=255, callback=0, payload=08
22:45:11.139 [DEBUG] [message.RemoveFailedNodeMessageClass] - Got RemoveFailedNode response.
22:45:11.140 [ERROR] [message.RemoveFailedNodeMessageClass] - NODE 5: Remove failed node failed as node not found
22:45:11.142 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
22:45:11.143 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 104ms/1015ms.
22:45:11.144 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
22:45:11.146 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 00 62 05 9C
22:45:11.148 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 04 00 62 05 9C
22:45:11.153 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 62 00 98
22:45:11.155 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
22:45:11.156 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 62 00 98
22:45:11.158 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 62 00 98
22:45:11.159 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=IsFailedNodeID[0x62], type=Response[0x01], priority=High, dest=255, callback=0, payload=00
22:45:11.160 [DEBUG] [rialmessage.IsFailedNodeMessageClass] - NODE 5: Is currently marked as healthy by the controller
22:45:11.162 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=IsFailedNodeID[0x62], type=Request[0x00], priority=High, dest=255, callback=0, payload=05
22:45:11.163 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=IsFailedNodeID[0x62], type=Response[0x01], priority=High, dest=255, callback=0, payload=00
22:45:11.164 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=IsFailedNodeID, callback id=0, expected=IsFailedNodeID, cancelled=false        transaction complete!
22:45:11.165 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
22:45:11.166 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 17ms/1015ms.

I did “remove device from controller”. So I think I cannot include it again. Or is there a “harder” way to force exclusion?

[chris (Chris Jackson)]

I’m not completely sure what you want to do now… If you want to exclude the device, then you can do this by clicking on the controller, and clicking on “Exclude Devices”. This puts the controller into exclude mode, and you then need to click on the device.

You won’t be able to use the “Remove device from controller option” - the controller will not allow this to be used with a device that is working (ie not FAILED) and we know this device is ok as it is marked healthy. For healthy devices, if you want to remove them, then use the exclude option as this is the normal way to remove devices in ZWave networks.

However, you shouldn’t need to remove it - just delete the thing, delete the XML and restart the binding. It should be rediscovered and then leave the initialisation to complete to see if it is then discovered. You can email me the complete log if you like.

[msi (Marcel)]

Thank you, I was not aware of the difference between remove and exclude. But now it’s clear. I excluded the plug and included it, I is now in the inbox. I sent the log to chris personally.

[chris (Chris Jackson)]

Thanks for the log. I think I’ve worked out the problem. I believe that this is a bug in the way properties are handled in ESH.

Issue: Unable to get information or update properties on existing inbox entry

[msi (Marcel)]

Thank you Chris for investigating it. I has some time yesterday to play around with my Z-Wave devices and OpenHAB.Deleting thing and XML and restart the binding worked fine for the wall plugs.I received a Fibaro Motion Sensor (FGMS-001) and had really trouble including it, even with the delete trick. After several times (includingt waiting something happens after some time and restarting the whole server) it finally worked. Maybe the trick dosn’t work as well for battery devices. Anyway, I can see all my devices now.
Many times, after a server restart, the whole Z-Wave stack doesn’t seem to work (everything is uninitialized, no debug messages), but after 1 to 5 restarts, it finally works.
So, now I will finally have a look at how the rest of OpenHAB2 works.

[chris (Chris Jackson)]

@msi

Many times, after a server restart, the whole Z-Wave stack doesn’t seem to work (everything is uninitialized, no debug messages), but after 1 to 5 restarts, it finally works.

You might want to follow this thread -:

Binding not starting consistently since 6/19 build

@chris I’m seeing some odd behavior at startup in the last 2 nightly builds (6/19 and 6/20). When starting OH2, the zwave binding starts up, but it doesn’t start it’s discovery process. If I stop and restart OH2, it eventually works. Sometimes it takes a couple restarts. I have a log file that shows the behavior, but I think it’s too long to post here. I can email it to you, if that’s ok. I see this behavior happening on two separate systems, one of which was a clean install of the 6/20 n…

It looks like there are problems with OH2 startup and I don’t think it’s a ZWave issue…

[msi (Marcel)]

@chris

You might want to follow this thread -:

Yes, definitely, thank you!