I’m struggling with this sensor - when I add it as a new sensor it comes with a default wakeup time of 21600. However when I change z-wave notifications status to ‘all notifications enabled’ then the wakeup time changes to 4200?
When I wake up the sensor with the B-button and change the parameter to 21600, save, the 4200 value pops up again. Does anyone see the same behavior (and is it a bad thing)? Obviously I don’t want to drain the battery for no reason so a high interval would seem better? Other values like 4201, 5000, 10000 give the same result.
Only devices in the zwave network for now are Aeotec ZW90 gen5 stick and this smoke sensor (in a Hassio on a PI3).
Tips to trick the sensor in a higher wakeup value are more than welcome.
I’m also having the same problem, however I would like to change the wakeup to something lower since I don’t get temperature reports often at all, sometimes it waits 8hours before it transmittal something. Why use a tempsensor in that case I wonder… How has your battery drainage been with the lower wakeup interval?
I have them now at 21600 wakeup time and have battery percentages from 25% to 100% over 5 detectors that I have installed.
If you want to have temperature reporting you may want to decrease the threshold of 1° which is default for sending out change readings.
My guess is that the distance to the ZWAVE network seems to have more impact than wakeup frequency. But that is just a guess I can only observe their location and see that it has a major impact.