Aeotec ZWA005 battery channel always returning 0%

Hi all,

in my ZWave network I currently also run two motion sensors from Aeotec. The devices work well (motion detection) and I also get information from the temperature and luminance channels.

I also track the battery state of all my battery Zwave devices, but I am not able to do that for the Aeotec ZWA005. I set the intervall for polling to 1 hour and can confirm from the log files, that the polling is done:

2020-05-05 04:41:51.927 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 14 03 80 03 00 66
2020-05-05 04:41:51.932 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=20, callback=0, payload=00 14 03 80 03 00
2020-05-05 04:41:51.935 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=20, callback=0, payload=00 14 03 80 03 00
2020-05-05 04:41:51.936 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2020-05-05 04:41:51.938 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 20: Application Command Request (ALIVE:DELETE_SUC_ROUTES)
2020-05-05 04:41:51.939 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: Incoming command class COMMAND_CLASS_BATTERY, endpoint 0
2020-05-05 04:41:51.941 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 20: SECURITY NOT required on COMMAND_CLASS_BATTERY
2020-05-05 04:41:51.943 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 20: Received COMMAND_CLASS_BATTERY V1 BATTERY_REPORT
2020-05-05 04:41:51.944 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 20: Battery report value = 0
2020-05-05 04:41:51.946 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2020-05-05 04:41:51.947 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_BATTERY, value=0
2020-05-05 04:41:51.950 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Updating channel state zwave:device:91e76c4c:node20:battery-level to 0 [DecimalType]
2020-05-05 04:41:51.953 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 20: Commands processed 1.
2020-05-05 04:41:51.954 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 20: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1c53d65.
2020-05-05 04:41:51.956 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-05-05 04:41:51.958 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-05-05 04:41:51.960 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-05-05 04:41:51.962 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-05-05 04:41:52.211 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 14 02 84 07 66
2020-05-05 04:41:52.215 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=20, callback=0, payload=00 14 02 84 07
2020-05-05 04:41:52.217 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=20, callback=0, payload=00 14 02 84 07
2020-05-05 04:41:52.218 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2020-05-05 04:41:52.220 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 20: Application Command Request (ALIVE:DELETE_SUC_ROUTES)
2020-05-05 04:41:52.222 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 20: Commands processed 1.
2020-05-05 04:41:52.224 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 20: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@94ea39.
2020-05-05 04:41:52.225 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-05-05 04:41:52.227 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-05-05 04:41:52.228 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-05-05 04:41:52.230 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

AND:

2020-05-05 08:29:43.532 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Application Command Request (ALIVE:DELETE_SUC_ROUTES)
2020-05-05 08:29:43.533 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: Incoming command class COMMAND_CLASS_BATTERY, endpoint 0
2020-05-05 08:29:43.534 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 22: SECURITY NOT required on COMMAND_CLASS_BATTERY
2020-05-05 08:29:43.535 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 22: Received COMMAND_CLASS_BATTERY V1 BATTERY_REPORT
2020-05-05 08:29:43.536 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 22: Battery report value = 0
2020-05-05 08:29:43.537 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2020-05-05 08:29:43.538 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_BATTERY, value=0
2020-05-05 08:29:43.540 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 22: Updating channel state zwave:device:91e76c4c:node22:battery-level to 0 [DecimalType]
2020-05-05 08:29:43.542 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 22: Commands processed 1.

As you can see the value is 0. And it’s always zero. But the devices and batteries are quite new and working. So zero should not be right.

Any suggestions how I can further look into this issue?

Thanks and best,
David

P.S.: attached the configuration of a thing.

I have the same issue with a ZWA005-C, I included first time this weekend. Battery is new.

Clearly this is an issue with the device. If it is reporting 0, then I’m not sure the binding is able to do a lot :wink:

1 Like

Exclude from the network, factory reset the device & then include again? It may get a different node number though.

For me it was solved by taking out and putting in again the battery.

1 Like