Recently replaced my garage door tilt detectors with Zooz ZSE43 sensors.
They seem to be consuming battery power at a high rate.
I used the default configuration parameters.
The wake-up interval is set to once an hour…that seems unnecessary. Here are the parameters.
UID: zwave:device:64793565f1:node66
label: "Z-Wave Node 066: ZSE43 Tilt / Shock SensorLeft"
thingTypeUID: zwave:zooz_zse43_00_000
configuration:
wakeup_interval: 3600
group_1:
- controller
group_3: []
group_2: []
config_1_1: 3
config_2_1: 5
config_7_1: 2
wakeup_node: 1
config_5_4: 0
config_6_3: 0
config_8_1: 3
config_9_1: 3
config_3_1: 20
config_4_1: 0
node_id: 66
bridgeUID: zwave:serial_zstick:64793565f1
channels:
- id: sensor_binary
channelTypeUID: zwave:sensor_binary
label: Binary Sensor
description: Indicates if a sensor has triggered
configuration: {}
- id: alarm_access
channelTypeUID: zwave:alarm_access
label: Alarm (access)
description: Indicates if the access control alarm is triggered
configuration: {}
- id: alarm_tamper
channelTypeUID: zwave:alarm_tamper
label: Alarm (vibration)
description: Indicates if the tamper alarm is triggered
configuration: {}
- id: sensor_door
channelTypeUID: zwave:sensor_door
label: Door State
description: Indicates if the door/window is open or closed
configuration: {}
- id: battery-level
channelTypeUID: system:battery-level
label: Battery Level
description: Battery level as a percentage (0-100%)
configuration: {}
Any recommendations on what the Wake-Up interval should be?
### VER. 1.20 (released 4/2022) -from ZOOZ support site
**Firmware: 1.20**
* Optimized battery reporting
For maximum battery life use the max allowed interval (generally 86400). A once-a-day battery reading is fine IMO. In OH, I time stamp the battery update to make sure the device is still there. The binding max is 864000, so you can’t exceed that as an upper limit, even if allowed by the device.
Ultimately I went back to my Ecolink tilt devices with the CR123 battery.
I have a Zooz ZS41 door sensor that appears to drain the battery quickly. I updated the firmware but no change. However, it’s being used to turn on a closet light which isn’t too critical, so I let it go with what appears to be “low” battery to see what would happen. 3 months later, with it reporting “0” battery, it continues to work fine. Perhaps Zooz has a problem with battery reporting and not with battery consumption? Or it could be both.
I think that’s largely due to the method most devices use to determine when a battery is low (usually voltage). CR2032 coin cells tend to lose voltage on a curve, so it’ll look like they’re depleting quickly, and then like they aren’t depleting at all. As you’re finding, the voltage might still be enough for the device to work, even if it’s below the threshold that is reported as 0%.
Some folks ignore the percentages and instead look at the reported voltage to determine when batteries need replacing.
I did put one of these (ZSE43) back in service 4 months ago with a new battery (non-critical location) just to see when it actually runs out (86400 wake). As noted above, rapidly down from 100% but still at 30-ish.
