GE Fan Switch 14287 shows as Unknown Device

  • Platform information:
    • Hardware: iMAC
    • OS: OSX 10.13.1
    • Java Runtime Environment: Zulu 8.25.0.1
    • openHAB version: 2.1.0

Hello,

I am brand new to OpenHab and switching from Indigo. I have been able to set up my Z-Stick and a large number of devices, but have three Z-Wave fan switches that are showing as “Unknown Device”. These are GE 14287 switches like the ones here.

After some searching it looks like these have already been added to the database here:
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/281

However, I am unsure of how to tell OpenHab this is really what my device is. I turned on Z-Wave debugging and toggled the fan switch and this is what I received:

 15:50:31.608 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Incoming command class SWITCH_MULTILEVEL
15:50:31.608 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 13: Received SWITCH_MULTILEVEL command V0
15:50:31.608 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 13: Switch Multi Level report, value = 99
15:50:31.608 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
15:50:31.608 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
15:50:31.608 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got a value event from Z-Wave network, endpoint = 0, command class = SWITCH_MULTILEVEL, value = 99
15:50:31.608 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 255: Transaction not completed: node address inconsistent.  lastSent=255, incoming=255
15:50:35.007 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 17 00 49 84 0D 11 04 11 08 5E 86 72 5A 85 59 73 26 27 70 56 2C 2B 7A 21
15:50:35.007 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
15:50:35.008 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 17 00 49 84 0D 11 04 11 08 5E 86 72 5A 85 59 73 26 27 70 56 2C 2B 7A 21
15:50:35.008 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 17 00 49 84 0D 11 04 11 08 5E 86 72 5A 85 59 73 26 27 70 56 2C 2B 7A 21
15:50:35.008 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 0D 11 04 11 08 5E 86 72 5A 85 59 73 26 27 70 56 2C 2B 7A
15:50:35.008 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 13: Application update request. Node information received.
15:50:35.008 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=IdentifyNode[0x41], type=Request[0x00], priority=High, dest=255, callback=0, payload=0D
15:50:35.008 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 0D 11 04 11 08 5E 86 72 5A 85 59 73 26 27 70 56 2C 2B 7A
15:50:35.008 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationUpdate, callback id=0, expected=IdentifyNode, cancelled=false      MISMATCH
15:50:35.041 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 0D 03 26 03 00 D9
15:50:35.041 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
15:50:35.041 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 0D 03 26 03 00 D9 
15:50:35.041 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 0D 03 26 03 00 D9
15:50:35.041 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0D 03 26 03 00
15:50:35.041 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Application Command Request (ALIVE:PROTOINFO)
15:50:35.041 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 13: Incoming command class SWITCH_MULTILEVEL
15:50:35.041 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 13: Received SWITCH_MULTILEVEL command V0
15:50:35.041 [DEBUG] [ss.ZWaveMultiLevelSwitchCommandClass] - NODE 13: Switch Multi Level report, value = 0
15:50:35.041 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
15:50:35.041 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
15:50:35.041 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 13: Got a value event from Z-Wave network, endpoint = 0, command class = SWITCH_MULTILEVEL, value = 0
15:50:35.042 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 255: Transaction not completed: node address inconsistent.  lastSent=255, incoming=255
15:50:42.474 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Stage PROTOINFO. Initialisation retry timer triggered. Increased to 320000
15:50:42.474 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Node advancer - PROTOINFO: queue length(0), free to send(false)
15:50:42.474 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Initialisation retry timer started 320000
15:50:42.474 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Node advancer: Retries exceeded at PROTOINFO
15:50:42.474 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 13: Retry timout: Can't advance

Any direction would be appreciated.

What exactly does it say for the name - just unknown, or are there some numbers as well? Alterniatively, if you look at the thing properties what does it show for the device type and device id?

Here is the screenshot with the device info. Thanks for the help!

So it looks like the device is not initialised at all. Maybe it didn’t include properly or some other error, but until the device properties are discovered it won’t be able to recognise the device…

I would suggest to reset it and reinclude it using HABmin or PaperUI.

Hey thanks again for your help. I have:

  • Deleted the things in Paper UI
  • Disassociated all three of these switches using the Z-Wave stick
  • Re-associated all three of these switches using the Z-Wave stick
  • Discovered new things in Paper UI

However I still get the same:

I also installed HABmin and even tried doing a factory reset on one of the switches and then added it in again, but still get the same thing.

FWIW the switches did work in Indigo.

As above - I would suggest to use either HABmin or PaperUI to include the devices. This way you know the device can communicate with the controller.

At the moment, it looks to me like there’s no communications - maybe you move the device too far away from the controller after inclusion for example? This might not be the case of course, and the next step would be to get the debug log and see what’s really going on…

FYI for anyone else who searches and gets this thread. I was able to fix this by updating to the 2.2 snapshot.