Zwave battery drain: handling of device wakeup message with 1 second delay ("sleepDelay = 1000")

I was surprised too. So I was documenting the behaviour in this posting. And got confirmation by Aeotec in the subsequent posting.

Actually, at that time I checked the response time of the zwave binding to the device’s wakeup notification. And I was happy that the zwave binding did immediately responded with a “wake up no more information”. There was no 1 s delay at the good old times (about 5 years ago!).

I don’t really understand then why you can configure the device to report on change - if I set this up to report on change of (say) 1 deg, will it still only report that on a wakeup period?

Yes, exactly. Also threshold reporting only occurs at wakeup intervals.

Theshold reporting allows to reduce network traffic (and I assume this may also imply some battery savings). Only when a threshold is exceeded (checked by the device at each wakeup), then a report is sent out.


Does this also mean that the motion sensor will only work on a wakeup?

No, the motion sensor notifications are transmitted immediately, without any delay. But sensor reports are only transmitted on wakeup (temperature, humidity, …).

With best regards,
Gert

1 Like