Battery Status not changing

Posted on
Fri Mar 24, 2017 12:32 pm
mlew offline
Posts: 33
Joined: Jan 08, 2016
Location: Lincs UK

Battery Status not changing

Hi

Since upgrading to 7 seem to be having issues with battery status on devices when i changed their batteries. for example i have a Fibaro door sensor that went to 0% so changed battery around 3 months go and battery has stayed at 0% but device works fine. noticed i had same issue with Fibaro smoke alarm, battery went to 5% so changed yesterday and its still showing 5%. Am i missing something? Any help would be appreciated.

Thanks

Mark

Posted on
Fri Mar 24, 2017 4:37 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Battery Status not changing

How often is the Fibaro smoke alarm set to wake (in its settings dialog)? I'd expect it to update with 24 hours after: 1) the batter is replaced), 2) the wake interval has occurred at least once or twice.

If you wake the module and re-sync it does it update?

Image

Posted on
Sat Mar 25, 2017 4:09 am
mlew offline
Posts: 33
Joined: Jan 08, 2016
Location: Lincs UK

Re: Battery Status not changing

Hi Matt

The smoke alarm is set to update every hour, have just done a sync on both door sensor and smoke alarm and neither has changed. i have even changed the battery in smoke alarm to another brand new one and still says 5% after sync.

I also have a Aeotec motion sensor and ever spring motion both showing 0% but working fine.

Thanks

Mark

Posted on
Sat Mar 25, 2017 10:41 am
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Battery Status not changing

Hi Mark,

Can you turn on the Z-Wave debug logging checkbox (via the Interfaces->Z-Wave->Configure... menu item), then perform the re-sync again with both modules? I would like to see what is occurring at the lower level.

Image

Posted on
Sat Mar 25, 2017 1:11 pm
mlew offline
Posts: 33
Joined: Jan 08, 2016
Location: Lincs UK

Re: Battery Status not changing

Hi Matt

below is log for smoke alarm took me couple of attempts to wake device, will do door sensor now.


Z-Wave sent "Landing Smoke Tamper" status request
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 00 2D 07 9C 02 2D 00 FF 00 00 90
Z-Wave Debug . . requestSensAlarmSensorStatus: node 045, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave Debug filtering duplicate command -- old: 9C00FF, 0, FF, new: 9C00FF, 0, FF (0.2824 secs)
Z-Wave Debug SENT requestVarSensorStatus: 01 09 00 13 2D 02 31 04 25 D0 0A
Z-Wave sent "Landing Smoke Temperature" status request
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 2D 06 31 05 01 22 00 D4 1F
Z-Wave Debug . . requestVarSensorStatus: node 045, endpoint None, type 1, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 21.2 °C (float: 21.200000)
Z-Wave received "Landing Smoke Temperature" sensor update to 21.2 °C
Z-Wave Debug SENT goToSleep: 01 09 00 13 18 02 84 08 24 D1 86
Z-Wave Debug RCVD packet: 01 07 00 13 D1 00 00 01 3B (hex)

25 Mar 2017, 19:08:56
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 26 06 31 05 04 22 01 80 44
Z-Wave Debug . . requestVarSensorStatus: node 038, endpoint None, type 4, raw value 2201...
Z-Wave Debug . . requestVarSensorStatus: 38.4 W (float: 38.400000)
Z-Wave Debug received "Kitchen Lights" power load to 38.4 W

25 Mar 2017, 19:09:26
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 2B 06 31 05 04 22 00 E1 29
Z-Wave Debug . . requestVarSensorStatus: node 043, endpoint None, type 4, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 22.5 W (float: 22.500000)
Z-Wave Debug received "Kitchen Light 2" power load to 22.5 W
Schedule Landing Lights On/Off (delayed action)
Z-Wave Debug SENT setMultiLevelValue: 01 0E 00 13 1C 07 60 0D 01 01 26 01 00 25 D2 44
Z-Wave sent "Landing Light" off
Z-Wave Debug queueing energy request of "028 - Landing Light" (activity detected)
Z-Wave Debug RCVD requestDimmerStatus: 01 09 00 04 00 1C 03 26 03 00 C8
Z-Wave Debug . . requestDimmerStatus: node 028, endpoint None, value 0
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 2D 06 31 05 01 22 00 DC 17
Z-Wave Debug . . requestVarSensorStatus: node 045, endpoint None, type 1, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 22.0 °C (float: 22.000000)

Posted on
Sat Mar 25, 2017 1:13 pm
mlew offline
Posts: 33
Joined: Jan 08, 2016
Location: Lincs UK

Re: Battery Status not changing

door sensor has much bigger log!

5 Mar 2017, 19:11:26
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 2B 06 31 05 04 22 00 E1 29
Z-Wave Debug . . requestVarSensorStatus: node 043, endpoint None, type 4, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 22.5 W (float: 22.500000)
Z-Wave Debug received "Kitchen Light 2" power load to 22.5 W
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 00 10 07 9C 02 10 00 FF 00 00 90
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave received "Back Door Tamper" status update is on
Trigger Back Door Tamper Reset
Z-Wave Debug intiatingSyncUI (timeout in 1500 seconds)
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 00 10 07 9C 02 10 00 00 00 00 6F
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 0, classSubKey 9C0000
Z-Wave received "Back Door Tamper" status update is off
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 00 10 07 9C 02 10 00 FF 00 00 90
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave received "Back Door Tamper" status update is on
Trigger Back Door Tamper Reset
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 00 10 07 9C 02 10 00 00 00 00 6F
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 0, classSubKey 9C0000
Z-Wave received "Back Door Tamper" status update is off
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 00 10 07 9C 02 10 00 FF 00 00 90
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave received "Back Door Tamper" status update is on
Trigger Back Door Tamper Reset
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 00 10 07 9C 02 10 00 00 00 00 6F
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 0, classSubKey 9C0000
Z-Wave received "Back Door Tamper" status update is off
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 00 10 07 9C 02 10 00 FF 00 00 90
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave received "Back Door Tamper" status update is on
Trigger Back Door Tamper Reset
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 00 10 07 9C 02 10 00 00 00 00 6F
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 0, classSubKey 9C0000
Z-Wave received "Back Door Tamper" status update is off
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 00 10 07 9C 02 10 00 FF 00 00 90
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave received "Back Door Tamper" status update is on
Trigger Back Door Tamper Reset
Z-Wave Syncing - started for "Back Door Sensor"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 10 01 01 69
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 00 00 41 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1E
Z-Wave Debug . . getNodeNeighbors: nodeId 016, neighbors: 17, 23, 25
Z-Wave Syncing - retrieved module neighbors list: 17, 23, 25
Z-Wave Syncing - assigning return route to "016 - Back Door Sensor"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 10 01 AD
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 016, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 10 24 D5 78
Z-Wave Debug RCVD nodeInfoFrame: 01 15 00 49 84 10 0F 04 20 01 30 9C 85 72 70 86 80 56 84 7A EF 2B 5C
Z-Wave Debug . . nodeInfoFrame: node 016, combined class list: 20v1 80v1 84v1 85v1 86v1 70v1 30v1 72v1 56v1 7Av1 9Cv1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 10 02 72 04 25 D6 72
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 10 08 72 05 01 0F 07 00 10 00 83
Z-Wave Debug . . requestManufactureInfo: node 016, manufacturerId 010F, productId 07001000
Z-Wave Debug . . requestManufactureInfo: Fibaro System, Door/Window Sensor (FGK101)
Z-Wave Syncing - retrieved manufacture and model names: Fibaro System - 010F, Door/Window Sensor (FGK101) - 07001000
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 10 02 86 11 25 D7 92
Z-Wave Debug RCVD requestVersInfoGen: 01 0D 00 04 00 10 07 86 12 03 03 43 02 05 31
Z-Wave Debug . . requestVersInfoGen: node 016, protoVers 3.67, appVers 2.05
Z-Wave Syncing - retrieved protocol version 3.67, app version 2.05
Z-Wave Debug SENT requestVersInfoCmdClass: 01 0A 00 13 10 03 86 13 84 25 D8 19
Z-Wave Debug RCVD requestVersInfoCmdClass: 01 0A 00 04 00 10 04 86 14 84 01 F2
Z-Wave Debug . . requestVersInfoCmdClass: node 016, class command 84 using version 1
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Binary Sensor : Binary Sensor (routing) (04 : 20 : 01, base 30)
Z-Wave Syncing - retrieved command classes: 20v1 80v1 84v1 85v1 86v1 70v1 30v1 72v1 56v1 7Av1 9Cv1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, battery, beaming, waking
Z-Wave Debug SENT requestWakeInterval: 01 09 00 13 10 02 84 05 25 D9 8A
Z-Wave Debug RCVD requestWakeInterval: 01 0C 00 04 00 10 06 84 06 00 0E 10 01 7C
Z-Wave Debug . . requestWakeInterval: node 016, interval 60 minutes, wakeTarget 001
Z-Wave Syncing - retrieved wake interval of 60 minutes
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 2B 06 31 05 04 22 00 E2 2A
Z-Wave Debug . . requestVarSensorStatus: node 043, endpoint None, type 4, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 22.6 W (float: 22.600000)
Z-Wave Debug received "Kitchen Light 2" power load to 22.6 W
Z-Wave Debug SENT setWakeInterval: 01 0D 00 13 10 06 84 04 00 0E 10 01 25 DA 97
Z-Wave Syncing - device "016 - Back Door Sensor" wake interval changed to 60 minutes
Z-Wave Debug SENT requestAssociationGroupCount: 01 09 00 13 10 02 85 05 25 DB 89
Z-Wave Debug RCVD requestAssociationGroupCount: 01 09 00 04 00 10 03 85 06 03 61
Z-Wave Debug . . requestAssociationGroupCount: node 016, group count: 3
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 10 03 85 02 01 25 DC 8A
Z-Wave Debug RCVD requestAssociations: 01 0C 00 04 00 10 06 85 03 01 05 00 01 62
Z-Wave Debug . . requestAssociations: node 016, group: 1, num associations: 1, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 016, group: 1, associations: [1]
Z-Wave Syncing - retrieved group 1 associations: [1]
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 10 03 85 02 02 25 DD 88
Z-Wave Debug RCVD requestAssociations: 01 0C 00 04 00 10 06 85 03 02 05 00 01 61
Z-Wave Debug . . requestAssociations: node 016, group: 2, num associations: 1, max associations: 5, replies left: 0
Z-Wave Debug . . requestAssociations: node 016, group: 2, associations: [1]
Z-Wave Syncing - retrieved group 2 associations: [1]
Z-Wave Debug SENT requestAssociations: 01 0A 00 13 10 03 85 02 03 25 DE 8A
Z-Wave Debug RCVD requestAssociations: 01 0C 00 04 00 10 06 85 03 03 01 00 01 64
Z-Wave Debug . . requestAssociations: node 016, group: 3, num associations: 1, max associations: 1, replies left: 0
Z-Wave Debug . . requestAssociations: node 016, group: 3, associations: [1]
Z-Wave Syncing - retrieved group 3 associations: [1]
Z-Wave Syncing - group 1 association to interface already exists (skipping)
Z-Wave Syncing - group 2 association to interface already exists (skipping)
Z-Wave Syncing - group 3 association to interface already exists (skipping)
Z-Wave Debug SENT requestConfigVal: 01 0A 00 13 10 03 70 05 05 25 DF 7F
Z-Wave Debug RCVD requestConfigVal: 01 0B 00 04 00 10 05 70 06 05 01 FF 68
Z-Wave Debug . . requestConfigVal: node 016, parm index 5, value 255 (size 1)
Z-Wave Syncing - retrieved parameter 5 "Group 1 command type" is 255
Z-Wave Debug . . requestConfigVal: node 016, combined config vals: 5:255
Z-Wave Debug SENT requestConfigVal: 01 0A 00 13 10 03 70 05 09 25 E0 4C
Z-Wave Debug RCVD requestConfigVal: 01 0B 00 04 00 10 05 70 06 09 01 00 9B
Z-Wave Debug . . requestConfigVal: node 016, parm index 9, value 0 (size 1)
Z-Wave Syncing - retrieved parameter 9 "Disable off commands" is false
Z-Wave Debug . . requestConfigVal: node 016, combined config vals: 9:0 5:255
Z-Wave Debug SENT requestConfigVal: 01 0A 00 13 10 03 70 05 03 25 E1 47
Z-Wave Debug RCVD requestConfigVal: 01 0B 00 04 00 10 05 70 06 03 01 00 91
Z-Wave Debug . . requestConfigVal: node 016, parm index 3, value 0 (size 1)
Z-Wave Syncing - retrieved parameter 3 "Switch type" is 0 "Normally Closed"
Z-Wave Debug . . requestConfigVal: node 016, combined config vals: 9:0 3:0 5:255
Z-Wave Debug SENT requestConfigVal: 01 0A 00 13 10 03 70 05 01 25 E2 46
Z-Wave Debug RCVD requestConfigVal: 01 0D 00 04 00 10 07 70 06 01 02 00 00 05 91
Z-Wave Debug . . requestConfigVal: node 016, parm index 1, value 0 (size 2)
Z-Wave Syncing - retrieved parameter 1 "Delayed off" is 0 seconds
Z-Wave Debug . . requestConfigVal: node 016, combined config vals: 9:0 3:0 5:255 1:0
Z-Wave Debug SENT requestConfigVal: 01 0A 00 13 10 03 70 05 0C 25 E3 4A
Z-Wave Debug RCVD requestConfigVal: 01 0B 00 04 00 10 05 70 06 0C 01 08 96
Z-Wave Debug . . requestConfigVal: node 016, parm index 12, value 8 (size 1)
Z-Wave Syncing - retrieved parameter 12 "Temperature sensitivity" is 8
Z-Wave Debug . . requestConfigVal: node 016, combined config vals: 9:0 3:0 12:8 5:255 1:0
Z-Wave Debug SENT requestConfigVal: 01 0A 00 13 10 03 70 05 02 25 E4 43
Z-Wave Debug RCVD requestConfigVal: 01 0B 00 04 00 10 05 70 06 02 01 01 91
Z-Wave Debug . . requestConfigVal: node 016, parm index 2, value 1 (size 1)
Z-Wave Syncing - retrieved parameter 2 "Enable LED flash on change" is true
Z-Wave Debug . . requestConfigVal: node 016, combined config vals: 1:0 2:1 3:0 5:255 9:0 12:8
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 10 02 80 02 25 E5 B5
Z-Wave Debug RCVD requestBatteryLevel: 18 (RETRANSMIT REQUEST)
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 10 02 80 02 25 E5 B5 (re-sent because retransmit request)
Z-Wave Debug . . requestBatteryLevel: requeuing 1 unsolicited packets
Z-Wave Debug . . requestBatteryLevel: requeuing 1 unsolicited packets
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 00 10 07 9C 02 10 00 00 00 00 6F
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 0, classSubKey 9C0000
Z-Wave received "Back Door Tamper" status update is off
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 10 10 07 9C 02 10 00 FF 00 00 80
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave received "Back Door Tamper" status update is on
Trigger Back Door Tamper Reset
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 10 10 07 9C 02 10 00 FF 00 00 80
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave Debug filtering duplicate command -- old: 9C00FF, 0, FF, new: 9C00FF, 0, FF (0.1229 secs)
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 10 10 07 9C 02 10 00 FF 00 00 80
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave Debug filtering duplicate command -- old: 9C00FF, 0, FF, new: 9C00FF, 0, FF (0.0205 secs)
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 10 10 07 9C 02 10 00 FF 00 00 80
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave Debug filtering duplicate command -- old: 9C00FF, 0, FF, new: 9C00FF, 0, FF (0.0397 secs)
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 10 10 07 9C 02 10 00 FF 00 00 80
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave Debug filtering duplicate command -- old: 9C00FF, 0, FF, new: 9C00FF, 0, FF (0.0371 secs)
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 00 10 07 9C 02 10 00 00 00 00 6F
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 0, classSubKey 9C0000
Z-Wave received "Back Door Tamper" status update is off
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 10 10 07 9C 02 10 00 FF 00 00 80
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave received "Back Door Tamper" status update is on
Trigger Back Door Tamper Reset
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 10 10 07 9C 02 10 00 FF 00 00 80
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave Debug filtering duplicate command -- old: 9C00FF, 0, FF, new: 9C00FF, 0, FF (0.1325 secs)
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 10 10 07 9C 02 10 00 FF 00 00 80
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave Debug filtering duplicate command -- old: 9C00FF, 0, FF, new: 9C00FF, 0, FF (0.1329 secs)
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 10 10 07 9C 02 10 00 FF 00 00 80
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave Debug filtering duplicate command -- old: 9C00FF, 0, FF, new: 9C00FF, 0, FF (0.0710 secs)
Z-Wave Debug RCVD requestSensAlarmSensorStatus: 01 0D 00 04 10 10 07 9C 02 10 00 FF 00 00 80
Z-Wave Debug . . requestSensAlarmSensorStatus: node 016, endpoint None, cmdClass 9C, alarmType 0, value 255, classSubKey 9C00FF
Z-Wave Debug filtering duplicate command -- old: 9C00FF, 0, FF, new: 9C00FF, 0, FF (0.1863 secs)
Z-Wave Debug timeout waiting for reply from module (retrying)
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 10 02 80 02 25 E6 B6
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 10 03 80 03 FF 9D
Z-Wave Debug . . requestBatteryLevel: node 016, level 255
Z-Wave Syncing - retrieved battery level of 0%
Z-Wave Syncing - complete
Z-Wave Debug terminatingSyncUI

25 Mar 2017, 19:12:26
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 2B 06 31 05 04 22 00 E1 29
Z-Wave Debug . . requestVarSensorStatus: node 043, endpoint None, type 4, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 22.5 W (float: 22.500000)
Z-Wave Debug received "Kitchen Light 2" power load to 22.5 W
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 2D 06 31 05 01 22 00 D2 19
Z-Wave Debug . . requestVarSensorStatus: node 045, endpoint None, type 1, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 21.0 °C (float: 21.000000)
Z-Wave received "Landing Smoke Temperature" sensor update to 21.0 °C

25 Mar 2017, 19:12:57
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 2B 06 31 05 04 22 00 E2 2A
Z-Wave Debug . . requestVarSensorStatus: node 043, endpoint None, type 4, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 22.6 W (float: 22.600000)
Z-Wave Debug received "Kitchen Light 2" power load to 22.6 W
Schedule Back Door Tamper Reset (delayed action)
Z-Wave updated "Back Door Tamper" to off

Posted on
Sat Mar 25, 2017 2:28 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Battery Status not changing

Your Event Log snippet for the smoke alarm doesn't include a sync.

The one for the door sensor does, and here is where it reports the battery level:

Code: Select all
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 10 02 80 02 25 E6 B6
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 10 03 80 03 FF 9D
Z-Wave Debug . . requestBatteryLevel: node 016, level 255
Z-Wave Syncing - retrieved battery level of 0%

Unfortunately, the module is indeed reporting that the battery is almost dead in this case. If it is a fresh battery then I don't know why it is misreporting it, but Indigo is definitely receiving a command telling it the battery is very low based on the bytes shown above.

Image

Posted on
Sun Mar 26, 2017 5:53 am
mlew offline
Posts: 33
Joined: Jan 08, 2016
Location: Lincs UK

Re: Battery Status not changing

Hi Matt

Have redone the smoke alarm below is section for battery, does the error mean anything? What else can i try as appear to have this issue with any device thats battery needs changing?

Z-Wave Syncing - retrieved parameter 31 "Temperature alarm" is 1 "10 Seconds"
Z-Wave Debug . . requestConfigVal: node 045, combined config vals: 1:2 2:3 3:0 4:0 21:10 20:1 10:0 11:255 30:55 31:1
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 2D 02 80 02 25 A5 C8
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 2D 03 80 03 05 5A
Z-Wave Debug . . requestBatteryLevel: node 045, level 5
Z-Wave Syncing - retrieved battery level of 5%
Z-Wave Syncing - complete
Z-Wave Error device "Landing Smoke Alarm" does not support status request command

Posted on
Mon Mar 27, 2017 8:15 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Battery Status not changing

Looking a the raw packet bytes the module is reporting the battery level is 5.

Is anyone else having these problems with their Fibaro modules? I know that battery level reporting for some module is very inaccurate, but if these are fresh batteries then it seems the values are totally wrong. This looks like a firmware bug in the module to me, but I would expect others to see it as well. It might be specific to certain firmware versions.

You might want to see what Fibaro has to say about this – it might be a known problem.

Image

Posted on
Tue Mar 28, 2017 12:19 am
mlew offline
Posts: 33
Joined: Jan 08, 2016
Location: Lincs UK

Re: Battery Status not changing

ok thanks Matt will have play with my devices to see if any other make is an issue. have a few other Fabaro devices too so will test them and let you know outcome.

Posted on
Mon Apr 03, 2017 9:28 am
mlew offline
Posts: 33
Joined: Jan 08, 2016
Location: Lincs UK

Re: Battery Status not changing

ok so tried removing device from system and then added back still same showing 5%. Appears to just be couple of Fibaro devices, smoke alarm and door sensor, other devices updating no issues. Will email Fibaro and see what they say.

Posted on
Mon Apr 03, 2017 5:01 pm
krissh offline
Posts: 105
Joined: Nov 18, 2012
Location: Norway

Re: Battery Status not changing

I don't have these but remembered something from another forum. Did you press a button for 3 seconds while the batteries are out? See the manual http://manuals.fibaro.com/content/manua ... -v1.01.pdf

Posted on
Tue Apr 04, 2017 12:02 pm
mlew offline
Posts: 33
Joined: Jan 08, 2016
Location: Lincs UK

Re: Battery Status not changing

good spot Krissh thanks will give that a try.

Posted on
Fri Oct 13, 2017 8:54 am
InsteonDiego offline
Posts: 48
Joined: Dec 07, 2016

Re: Battery Status not changing

Hello -

In lieu of starting a new topic, this issue seems related to an issue I am seeing with the Zooz 4-in-1 sensor not updating their battery level once depleted and changed. This issue only occurs on sensors with encryption enabled, those with encryption disabled function normally. I graph the battery levels of the motion sensors and can clearly see the battery level deplete to zero over time. Those with encryption stay at zero after the battery is replaced, those unencrypted will update their battery level after a couple of hours have passed. The only solution I have found is to use the Define & Sync process several times and once in a while I get lucky and the battery status updates.

The issue would be more clear if battery updates were never sent, however I only see this once new batteries are placed. Is it possible the update is being lost during decryption (or not being sent at all)?

Here is info on the device:
Indigo Z-Wave Version: 2.0.68
Node ID: 20
Model: Zooz Multi Sensor (ZSE40)
Model ID: 20212101
Manufacturer: Zooz
Manufacturer ID: 027A
Protocol Version: 4.05
Application Version: 16.09
Model Definition Version: 1
Library Type: 3
Class Name: Notification Sensor
Class Hierarchy: 04 : 07 : 01
Command Class Base: 00
Command Versions: 20v1 80v1 84v2 85v1 86v1 71v1 70v1 31v7 72v1 73v1 98v1 59v1 5Av1 7Av1 5Ev1
Encryption Status: Enabled for Commands 80 84 85 86 71 70 31 72 73 59 5A 7A
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, security, waking
Neighbors: 6, 14, 15, 16
Associations: 1:[1]
Config Values: 1:1 2:1 3:1 4:5 5:2 6:2 7:1

Here is an update received from the device that may be battery related, with value 255 showing that the battery is still dead (but not entirely sure!)

RCVD nonceFetch: node 020
Z-Wave Debug SENT nonceReport: 01 11 00 13 14 0A 98 80 65 09 E1 9D BB 2D 2C 71 25 7F 7A
Z-Wave Debug RCVD encryptedPacket: 00 71 05 07 FF 00 FF 07 08 00 00 (decrypted)
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 14 0A 71 05 07 FF 00 FF 07 08 00 00 FF
Z-Wave Debug . . requestAlarmSensorStatus: node 020, endpoint None, cmdClass 71, type 7, value 255, classSubKey 7107FF
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7107FF0708

Thanks in advance for any steps towards resolution!

Posted on
Fri Oct 13, 2017 4:10 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Battery Status not changing

I don't think that log is related to battery level polling.

Indigo polls/queries the battery status (command 80 02) when a module sends an awake command to Indigo. Indigo has additional logic (to conserve battery) of only querying the battery level once every 12 hours. So if the wake interval (as set in the device settings dialog) is more often than a couple of times a day Indigo will not query every time the module wakes. You can reset Indigos 12 hour battery polling timer by restarting the Z-Wave interface. So try the following:

1) Turn on Z-Wave debug logging (looks like you've already done that).
2) Choose the Interfaces-Z-Wave->Reload menu item (resets Indigo's internal timer).
3) Wake the module manually (normally by tapping its inclusion button) or wait until it wakes based on the interval you set in the device settings dialog.
4) Copy/paste the Event Log contents into a reply for me of what occurs when the module wakes.

Image

Who is online

Users browsing this forum: No registered users and 3 guests