Battery level not updated for Aeotec WallMote

Tags: #<Tag:0x00007fe734c68b80> #<Tag:0x00007fe734c68a68> #<Tag:0x00007fe734c68860>

Just got it a few days ago. Set it up ad its working fine, except the battery binding is not reporting the level of the battery. Initially I thought it might be reported after waking, so I set a 15 minute wake to see if that was the problem, but no updates have been received since I’ve had the device. Habmi displays “Node initializing: SET_WAKEUP”. The “Notification Report” is set Central Scene and Config (from default of Central Scene). Z-Wave Plus Lifeline is set to OpenHab Controller.

I put the wave binding into Debug and here is the output:
2017-11-11 12:04:18.314 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 07 02 84 07 75
2017-11-11 12:04:18.319 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2017-11-11 12:04:18.322 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 08 00 04 00 07 02 84 07 75
2017-11-11 12:04:18.324 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 08 00 04 00 07 02 84 07 75
2017-11-11 12:04:18.327 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 07 02 84 07
2017-11-11 12:04:18.347 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 7: Application Command Request (ALIVE:ASSOCIATIONS)
2017-11-11 12:04:18.352 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 7: Incoming command class WAKE_UP
2017-11-11 12:04:18.356 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Received Wake Up Request
2017-11-11 12:04:18.368 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Received WAKE_UP_NOTIFICATION
2017-11-11 12:04:18.370 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Is awake with 2 messages in the wake-up queue.
2017-11-11 12:04:18.373 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
2017-11-11 12:04:18.375 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Wakeup during initialisation.
2017-11-11 12:04:18.376 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node advancer - ASSOCIATIONS: queue length(8), free to send(false)
2017-11-11 12:04:18.378 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node advancer: loop - ASSOCIATIONS try 1: stageAdvanced(false)
2017-11-11 12:04:18.380 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node advancer - advancing to SET_WAKEUP
2017-11-11 12:04:18.382 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInitializationStateEvent
2017-11-11 12:04:18.384 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveInitializationStateEvent
2017-11-11 12:04:18.388 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node advancer: loop - SET_WAKEUP try 0: stageAdvanced(true)
2017-11-11 12:04:18.391 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node advancer: SET_WAKEUP - Interval is currently 0. Set to 30
2017-11-11 12:04:18.393 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node advancer: SET_WAKEUP - Set wakeup node to controller (1), period 30
2017-11-11 12:04:18.394 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Creating new message for application command WAKE_UP_INTERVAL_SET to 30
2017-11-11 12:04:18.396 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0D 00 13 07 06 84 04 00 00 1E 01 00 00 7F
2017-11-11 12:04:18.398 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Sending REQUEST Message = 01 0D 00 13 07 06 84 04 00 00 1E 01 00 00 7F
2017-11-11 12:04:18.399 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 7: Node advancer - queued packet. Queue length is 1
2017-11-11 12:04:18.400 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 6. Queue={}
2017-11-11 12:04:18.402 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Creating new message for application command WAKE_UP_INTERVAL_GET
2017-11-11 12:04:18.403 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveWakeUpEvent
2017-11-11 12:04:18.405 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 7. Queue={}
2017-11-11 12:04:18.407 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=7, callback=244, payload=07 08 60 0D 01 01 59 05 00 05
2017-11-11 12:04:18.408 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 07 02 84 07
2017-11-11 12:04:18.409 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=244, expected=ApplicationCommandHandler, cancelled=true MISMATCH
2017-11-11 12:04:20.815 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 7: Timeout while sending message. Requeueing - 2 attempts left!
2017-11-11 12:04:20.815 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Is sleeping
2017-11-11 12:04:20.816 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Putting message SendData in wakeup queue.
2017-11-11 12:04:20.817 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 6
2017-11-11 12:04:20.818 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Putting message SendData in wakeup queue.
2017-11-11 12:04:20.818 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 5
2017-11-11 12:04:20.819 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Putting message SendData in wakeup queue.
2017-11-11 12:04:20.820 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 4
2017-11-11 12:04:20.821 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Putting message SendData in wakeup queue.
2017-11-11 12:04:20.822 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 3
2017-11-11 12:04:20.822 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Putting message SendData in wakeup queue.
2017-11-11 12:04:20.823 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 2
2017-11-11 12:04:20.824 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Message already on the wake-up queue. Removing original.
2017-11-11 12:04:20.825 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Putting message SendData in wakeup queue.
2017-11-11 12:04:20.825 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 1
2017-11-11 12:04:20.826 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Message already on the wake-up queue. Removing original.
2017-11-11 12:04:20.827 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Putting message SendData in wakeup queue.
2017-11-11 12:04:20.827 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2017-11-11 12:04:20.828 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Putting message SendData in wakeup queue.
2017-11-11 12:04:38.360 [WARN ] [ore.internal.events.OSGiEventManager] - Dispatching event to subscriber ‘org.eclipse.smarthome.io.monitor.internal.EventLogger@70f5e3’ takes more than 5000ms.
2017-11-11 12:09:09.555 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Configuration update received
2017-11-11 12:09:09.589 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Configuration update wakeup_interval to 3000
2017-11-11 12:09:09.591 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Set wakeup interval to '3000’
2017-11-11 12:09:09.593 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Creating new message for application command WAKE_UP_INTERVAL_SET to 3000
2017-11-11 12:09:09.595 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0D 00 13 07 06 84 04 00 0B B8 01 00 00 D2
2017-11-11 12:09:09.597 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Sending REQUEST Message = 01 0D 00 13 07 06 84 04 00 0B B8 01 00 00 D2
2017-11-11 12:09:09.599 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Putting message SendData in wakeup queue.
2017-11-11 12:09:09.601 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Creating new message for application command WAKE_UP_INTERVAL_GET
2017-11-11 12:09:09.603 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Message already on the wake-up queue. Removing original.
2017-11-11 12:09:09.604 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 7: Putting message SendData in wakeup queue.

There is nothing else after this final line for node 7 (Wallmote). I contacted Aeotec to see if there were particular config param that might help with this, but they felt my settings were adequate. So any ideas would be greatly appreciated.
Thanks

I know for my smoke alarms they only report battery a couple of times a week. How long have you been waiting?

Its been 4 days now. I’ve awaken the device any number of times since, as I read that it may send an update when it awakened or when the battery is charged. I also noticed this in the logs when I wake it:

2017-11-12 19:12:02.178 [INFO ] [l.commandclass.ZWavePlusCommandClass] - NODE 7: unknown ZWavePlus device type: 7169
2017-11-12 19:12:02.373 [INFO ] [l.commandclass.ZWavePlusCommandClass] - NODE 7: unknown ZWavePlus device type: 7169
2017-11-12 19:12:02.541 [INFO ] [l.commandclass.ZWavePlusCommandClass] - NODE 7: unknown ZWavePlus device type: 7169
2017-11-12 19:12:02.708 [INFO ] [l.commandclass.ZWavePlusCommandClass] - NODE 7: unknown ZWavePlus device type: 7169
2017-11-12 19:12:02.832 [INFO ] [l.commandclass.ZWavePlusCommandClass] - NODE 7: unknown ZWavePlus device type: 7172```

I just got a battery update. Not sure why. I was playing with waking the device while looking through the parameters in Habmin. At some point the device turned purple, and then green. (Apparently, I held the Action button down long enough to invoke a network health check). I looked at the sitemap again, and the battery showed 100%. I wish I could provide a more definitive answer for those looking for help.