"Unknown device" after reincluding Z-Wave.me Wall Controller WALLC (switch)

Add-ons Bindings
, ,
1

Hey folks,

I had an issue where I couldn’t update the properties for my “Z-Wave.me Wall Controller WALLC” device in Habmin because of an “duplicate channels” error.
I thought updating Openhab 2 (online SNAPSHOT releases) and reincluding the device would maybe fix the problem, but now it says “Unknown device” in Habmin and I can’t see any channels. Before the reinclusion, the type of the device was detected without problems.
I already tried reincluding the device multiple times in Standard inclusion mode and also waking it up a few items and deleting it again, but it always says “Unknown device” now :frowning: and in the log it states that the device has the thingType 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0

Her is the filtered log for this Zwave Node:

2017-01-08 19:53:20.196 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer: loop - INIT_NEIGHBORS try 1: stageAdvanced(false)
2017-01-08 19:53:20.196 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer - advancing to FAILED_CHECK
2017-01-08 19:53:20.196 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Got an event from Z-Wave network: ZWaveInitializationStateEvent
2017-01-08 19:53:20.197 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer: loop - FAILED_CHECK try 0: stageAdvanced(true)
2017-01-08 19:53:20.197 [DEBUG] [rialmessage.IsFailedNodeMessageClass] - NODE 23: Requesting IsFailedNode status from controller.
2017-01-08 19:53:20.197 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer - queued packet. Queue length is 1
2017-01-08 19:53:20.233 [DEBUG] [rialmessage.IsFailedNodeMessageClass] - NODE 23: Is currently marked as healthy by the controller
2017-01-08 19:53:20.237 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer - FAILED_CHECK: Transaction complete (IsFailedNodeID:Request) success(true)
2017-01-08 19:53:20.238 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer - checking initialisation queue. Queue size 1.
2017-01-08 19:53:20.238 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer - message removed from queue. Queue size 0.
2017-01-08 19:53:20.239 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer - FAILED_CHECK: queue length(0), free to send(true)
2017-01-08 19:53:20.240 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer: loop - FAILED_CHECK try 1: stageAdvanced(false)
2017-01-08 19:53:20.240 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer - advancing to WAIT
2017-01-08 19:53:20.242 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Got an event from Z-Wave network: ZWaveInitializationStateEvent
2017-01-08 19:53:20.242 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer: loop - WAIT try 0: stageAdvanced(true)
2017-01-08 19:53:20.243 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer: WAIT - Listening=false, FrequentlyListening=false
2017-01-08 19:53:20.244 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer: WAIT - Still waiting!
2017-01-08 19:53:20.245 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 23: Sending REQUEST Message = 01 09 00 13 17 02 72 04 25 73 D0 
2017-01-08 19:53:20.331 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 23: Sent Data successfully placed on stack.
2017-01-08 19:53:22.896 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 23: Transaction not completed: node address inconsistent.  lastSent=23, incoming=255
2017-01-08 19:53:23.458 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 23: Transaction not completed: node address inconsistent.  lastSent=23, incoming=255
2017-01-08 19:53:25.268 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 23: Timeout while sending message. Requeueing - 2 attempts left!
2017-01-08 19:53:25.278 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 23: Got an error while sending data. Resending message.
2017-01-08 19:53:25.280 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 23: Sending REQUEST Message = 01 09 00 13 17 02 72 04 25 74 D7 
2017-01-08 19:53:25.373 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 23: Sent Data successfully placed on stack.
2017-01-08 19:53:27.362 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 23: SendData Request. CallBack ID = 116, Status = Transmission complete, no ACK received(1)
2017-01-08 19:53:27.362 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 23: Got an error while sending data. Resending message.
2017-01-08 19:53:27.363 [DEBUG] [curityCommandClassWithInitialization] - NODE 23: updating lastSentMessageTimestamp
2017-01-08 19:53:27.363 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2017-01-08 19:53:27.363 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 23: Node advancer - WAIT: Transaction complete (SendData:Request) success(false)
2017-01-08 19:53:27.363 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 23: Response processed after 2063ms/4983ms.
2017-01-08 19:53:27.364 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 23: Sending REQUEST Message = 01 09 00 13 17 02 72 04 25 75 D6 
2017-01-08 19:53:27.451 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 23: Sent Data successfully placed on stack.
2017-01-08 19:53:32.380 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 23: Timeout while sending message. Requeueing - 1 attempts left!
2017-01-08 19:53:32.381 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 23: Node is DEAD.
2017-01-08 19:53:32.381 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2017-01-08 19:53:32.381 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Setting OFFLINE
2017-01-08 19:53:32.856 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: MANUFACTURER not set
2017-01-08 19:53:32.857 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Controller status changed to ONLINE.
2017-01-08 19:53:32.857 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Controller is ONLINE. Starting device initialisation.
2017-01-08 19:53:32.859 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Updating node properties.
2017-01-08 19:53:32.859 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Updating node properties. MAN=2147483647
2017-01-08 19:53:32.860 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Properties synchronised
2017-01-08 19:53:32.861 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Initialising Thing Node...
2017-01-08 19:53:32.862 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Polling intialised at 1800 seconds - start in 1800000 milliseconds.
2017-01-08 19:53:34.112 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 23: SendData Request. CallBack ID = 117, Status = Transmission complete, no ACK received(1)
2017-01-08 19:53:34.112 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 23: Node is DEAD.
2017-01-08 19:53:34.112 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2017-01-08 19:53:34.112 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Setting OFFLINE
2017-01-08 19:53:34.491 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 23: SendData Request. CallBack ID = 117, Status = Transmission complete, no ACK received(1)
2017-01-08 19:53:34.492 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 23: Node is DEAD.
2017-01-08 19:53:34.492 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2017-01-08 19:53:34.492 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Setting OFFLINE
2017-01-08 19:53:53.927 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 23: Transaction not completed: node address inconsistent.  lastSent=23, incoming=255
2017-01-08 19:54:04.517 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 23: Transaction not completed: node address inconsistent.  lastSent=23, incoming=255
2017-01-08 19:54:35.047 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 23: Transaction not completed: node address inconsistent.  lastSent=23, incoming=255
2017-01-08 19:55:19.047 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 23: Transaction not completed: node address inconsistent.  lastSent=23, incoming=255
2017-01-08 19:55:24.957 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 23: Serialise aborted as static stages not complete
2017-01-08 19:55:27.637 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 23: Device discovery completed
2017-01-08 19:55:27.637 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 23: Checking zwave:sigma_zwck8_00_000
# Text removed
2017-01-08 19:55:27.714 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 23: Checking zwave:everspring_an180_00_000
2017-01-08 19:55:27.715 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 23: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2017-01-08 19:55:34.388 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: MANUFACTURER not set
2017-01-08 19:55:34.389 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Controller status changed to ONLINE.
2017-01-08 19:55:34.389 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Controller is ONLINE. Starting device initialisation.
2017-01-08 19:55:34.391 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Updating node properties.
2017-01-08 19:55:34.391 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Updating node properties. MAN=2147483647
2017-01-08 19:55:34.392 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Initialising Thing Node...
2017-01-08 19:55:34.393 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 23: Polling intialised at 1800 seconds - start in 1800000 milliseconds.
2017-01-08 19:55:49.217 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 23: Transaction not completed: node address inconsistent.  lastSent=23, incoming=255
2017-01-08 19:55:52.098 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 23: Transaction not completed: node address inconsistent.  lastSent=23, incoming=255
2017-01-08 19:58:09.189 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 23: Transaction not completed: node address inconsistent.  lastSent=23, incoming=255
2017-01-08 20:00:46.721 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 23: Transaction not completed: node address inconsistent.  lastSent=23, incoming=255
2017-01-08 20:01:35.422 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 23: Transaction not completed: node address inconsistent.  lastSent=23, incoming=255
2

Are you waking up the device once it’s included? I don’t see any communication with the device in the log - it’s a battery device, so you must wake it up manually (probably a few times) so that the binding can download device information such as the manufacturer data, and the command classes…

3

Hey chris,

yeah like 4 times, I even tried it when being close to the controller. It’s quite annoying with this device tho, because you first have to enter Maintenance mode in order to do this… and it already worked before, so I’m a bit confused. I even did a controller hard reset yesterday (I have 20 Zwave devices…) and a few device factory resets. I’m starting to believe that the device is broken somehow, because it even does not work with the original Razberry z-way software now, and it’s working fine with another Z-Wave device.

4

Ok - the log doesn’t show that, but maybe it’s just because it’s a short log. My next suggestion would have been to exclude and re-include it as sometimes the controller can get confused and the device things it’s node X, but the controller (and hence the binding!) thinks it’s node Y. However, I think you’ve already tried this more than once? If not though, I would try exclude/reinclude to see if it helps…

5

Problem solved, I was able to include the switch again. Appearently I was using the wrong manual from Z-WAVE.me, that wrong manual stated that Button 3 is the button for standard inclusion/exclusion instead of Button 1 (although I thought I tried this button also) Maybe there was also a problem with Openhab / The binding before I hard-resetted the controller. Anyway, the problem is gone, thanks for your help tho chris.

6

When trying to update the name or location of the device, it doesn’t work and I get the following error in the Network tab of the Developer tools:

{
  "error": {
    "message": "Duplicate channels zwave:device:158d5d4bbda:node3:scene_number",
    "http-code": 500,
    "exception": {
      "class": "java.lang.IllegalArgumentException",
      "message": "Duplicate channels zwave:device:158d5d4bbda:node3:scene_number",
      "localized-message": "Duplicate channels zwave:device:158d5d4bbda:node3:scene_number"
    }
  }
}