Battery powered nodes won't initialize

markee · January 4, 2017, 8:43pm

Hi !
I’m using an ZME_UZB1 Stick with openhab2, and tried to get different battery powered devices to work.
I knew about the problem to wake up the devices manually to get them completly initialized, but i have no more ideas to get this to work.
The nodes are recognized shortly as “unknown device”, but many manuell “wake up’s” or re-add’s haven’t solved the problem. I’m waiting for 1 - 2 days, to check if the devces wake up itself and getting initializing done…but no way !

For example i want to add an Philio PST02-1C and the debug log always have the same entries (by pressing the tamper button to wake up …)

21:30:21.754 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Putting message SendData in wakeup queue.
21:30:21.755 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
21:30:21.756 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Message already on the wake-up queue. Removing original.
21:30:21.757 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Putting message SendData in wakeup queue.
21:30:53.633 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 04 03 02 84 07 75
21:30:53.637 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
21:30:53.641 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 04 04 03 02 84 07 75
21:30:53.643 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 08 00 04 04 03 02 84 07 75
21:30:53.645 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=04 03 02 84 07
21:30:53.646 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 3: Application Command Request (ALIVE:MANUFACTURER)
21:30:53.647 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 3: Incoming command class WAKE_UP
21:30:53.648 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Received Wake Up Request
21:30:53.648 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Received WAKE_UP_NOTIFICATION
21:30:53.649 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Is awake with 1 messages in the wake-up queue.
21:30:53.650 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
21:30:53.651 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Wakeup during initialisation.
21:30:53.652 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Node advancer - MANUFACTURER: queue length(1), free to send(false)
21:30:53.653 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Node advancer: loop - MANUFACTURER try 4: stageAdvanced(false)
21:30:53.654 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Node advancer: MANUFACTURER - send ManufacturerSpecific
21:30:53.655 [DEBUG] [WaveManufacturerSpecificCommandClass] - NODE 3: Creating new message for command MANUFACTURER_SPECIFIC_GET
21:30:53.656 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Node advancer - queued packet. Queue length is 1
21:30:53.657 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
21:30:53.657 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
21:30:53.658 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
21:30:53.659 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 03 02 72 04 25 3A 8D
21:30:53.660 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Message has Ack Pending: Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=3, callback=59, payload=03 02 72 04
21:30:53.660 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 3: Sending REQUEST Message = 01 09 00 13 03 02 72 04 25 3A 8D
21:30:53.672 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
21:30:53.673 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
21:30:53.674 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
21:30:53.676 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
21:30:53.677 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
21:30:53.679 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: Sent Data successfully placed on stack.
21:30:58.065 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 3A 01 01 B8 69
21:30:58.069 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
21:30:58.070 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 3A 01 01 B8 00 00 67
21:30:58.072 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 3A 01 01 B8 00 00 67
21:30:58.074 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=3A 01 01 B8
21:30:58.076 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 3: SendData Request. CallBack ID = 58, Status = Transmission complete, no ACK received(1)
21:30:58.076 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Is sleeping
21:30:58.078 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Putting message SendData in wakeup queue.
21:30:58.080 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
21:30:58.080 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 3: Node advancer - MANUFACTURER: Transaction complete (SendData:Request) success(false)
21:30:58.082 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Putting message SendData in wakeup queue.
21:30:58.083 [DEBUG] [curityCommandClassWithInitialization] - NODE 3: updating lastSentMessageTimestamp
21:30:58.085 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 3: Response processed after 4423ms/4548ms.
21:30:58.086 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
21:30:58.086 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Message already on the wake-up queue. Removing original.
21:30:58.087 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 3: Putting message SendData in wakeup queue.

I’ve the same issue with an other device (Fibaro FGK10x) and no more ideas what to do to fix this … Please, can anybody figure out the problem and help me ?

sihui · January 4, 2017, 9:06pm

Wake it up manually, again and again … sometimes you have to do that 10 times …and put it close to the controller.

markee · January 5, 2017, 9:01pm

thank for the tip … i tried again and again and again…still no proper initialize … so what … i couldn’t believe that i’m to stupid for this, or all the battery powered devices have an issue … now i’m trying to test another zwave controller … let’s see what’s happening … i’ll tell, soon

markee · January 11, 2017, 7:41pm

Hi,
now i’ve switched my ZME_UZB1 Stick to an Aeotec Z-Stick Gen5. The Philio device initialized properly at “first touch”. The Fibaro device was a little more tricky, but still initialized without any problems (just entered the “Exclude” mode by pressing the button on the stick for a few seconds, than unregistered the fibaro device, activated the “Include” mode with button press and registered the fibaro fgk-10x … and habmin brings up an new zwave node and initializes immediatly)…

Now, my problems are solved (caused by an buggy zwave stick).

sihui · January 11, 2017, 7:58pm

Glad to hear. Yes, that stick must have been buggy because I have the same stick and no problems at all.