Unknown Device - in database

thanks, I will try that with the KeyFob.

I did find the wakeup command for the Zwave.me button and this is what’s in the log:

2018-09-29 11:02:45.328 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: Application Command Request (ALIVE:REQUEST_NIF)

2018-09-29 11:02:45.331 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 40: Incoming command class COMMAND_CLASS_CENTRAL_SCENE, endpoint 0

2018-09-29 11:02:45.332 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 40: SECURITY not supported

2018-09-29 11:02:45.334 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 40: Received COMMAND_CLASS_CENTRAL_SCENE V0 CENTRAL_SCENE_NOTIFICATION

2018-09-29 11:02:45.336 [DEBUG] [dclass.ZWaveCentralSceneCommandClass] - NODE 40: Received scene 1 at key 0 [Single Press]

2018-09-29 11:02:45.348 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Got an event from Z-Wave network: ZWaveCommandClassValueEvent

2018-09-29 11:02:45.357 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_CENTRAL_SCENE, value = 1.0

2018-09-29 11:02:45.358 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: Commands processed 1.

2018-09-29 11:02:45.360 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@930255.

2018-09-29 11:02:46.908 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 40: WakeupTimerTask 0 Messages waiting, state REQUEST_NIF

2018-09-29 11:02:46.909 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 40: No more messages, go back to sleep

2018-09-29 11:02:46.910 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 40: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION

2018-09-29 11:02:46.911 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 40: SECURITY not supported

2018-09-29 11:02:46.912 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 40: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured

2018-09-29 11:02:46.914 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@1f43569

2018-09-29 11:02:46.916 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: Bump transaction 364 priority from Immediate to Immediate

2018-09-29 11:02:46.918 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: Adding to device queue

2018-09-29 11:02:46.922 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: Added to queue - size 14

2018-09-29 11:02:46.927 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 40: Sending REQUEST Message = 01 09 00 13 28 02 84 08 25 30 56 

2018-09-29 11:02:46.960 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 40: sentData successfully placed on stack.

2018-09-29 11:02:46.963 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: TID 364: Transaction not completed

2018-09-29 11:02:51.805 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: sendTransaction org.openhab.binding.zwave.internal.protocol.ZWaveSerialPayload@728997

2018-09-29 11:02:51.807 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: Bump transaction 365 priority from Controller to Immediate

2018-09-29 11:02:51.810 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: Adding to device queue

2018-09-29 11:02:51.811 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: Added to queue - size 14

2018-09-29 11:02:51.962 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 40: TID 364: Timeout at state WAIT_REQUEST. 3 retries remaining.

2018-09-29 11:02:55.067 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 40: SendData Request. CallBack ID = 48, Status = Transmission complete, no ACK received(1)

2018-09-29 11:02:55.068 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 40: WAKE_UP_NO_MORE_INFORMATION. Treated as ACK.

2018-09-29 11:02:55.069 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: TID 364: Transaction not completed

2018-09-29 11:03:03.966 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 40: TID 364: Timeout at state ABORTED. 3 retries remaining.

2018-09-29 11:03:03.970 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

2018-09-29 11:03:03.971 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: notifyTransactionResponse TID:364 CANCELLED

2018-09-29 11:03:03.975 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 40: Went to sleep COMPLETE

2018-09-29 11:03:04.013 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: TID 365: Transaction not completed

2018-09-29 11:03:11.935 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 40: Application update request. Node Info Request Failed.

I still don’t see any wakeup notification message being received, or a NIF received in this log. If the binding doesn’t receive these messages, it doesn’t know that the device is awake, and will not (ie can not) communicate with it.

Please also use code fences when posting logs so they are more readable (I’ve edited your last post so you can see the difference :wink: ).

1 Like

But the wakeup command worked just fine for the Fibaro KeyFob.

Thank you. I should have figured out the wakeup comand by my self :slight_smile: But now I’ve learned something new today

I’ll have a go at the zwave.me button now…

Arild

1 Like

I know it’s sometimes not intuitive - it’s easy to think “I’ve pushed a button on the device, and I see data coming in in the log, so clearly it’s awake”.

However, as above, from a communication perspective, this isn’t the case - when devices like door sensors, and key fobs, send out notifications, they will not turn on their receivers to allow two way communications with the controller, so can not accept configuration, or initialisation requests that are needed for the binding to work out what the device is…

Anyway, I’m pleased that at least the Fibaro is working now :slight_smile:

Woke up the zwave.me button a few times and that is recognized as well now.

My bad :slight_smile:

thanks…

Arild

1 Like