How does on time value affect battery lifetime?

[elvizgz]

Hello!

I would like to know if setting on time value to a low value (such as 10 seconds) will affect battery lifetime. Maybe it's an obvious question but I'm a complete newbie. I'm working with AEON Multisensor 4 in 1.

Thanks in advance.

[RCC]

I don't know the "official" answer, but with my Aeon multisensor the Razberry seems to puts it back to sleep when it is done with it, so it never actually stays on for more than a couple of seconds regardless of the on-time value. So I take that value to mean more "how long should I stay awake if no one puts me back to sleep."

[elvizgz]

I don't understand quite well your reply... As far as I know, on time value means "how long should the device keep state On before sending it Off command" when movement is detected. The sensor is who puts himself back to sleep, not the RazBerry, isn't it?

Anyway, does a low value decrease battery faster or doesn't affect battery lifetime?

Thanks for your reply!

[pz1]

RaZberry does send a go to sleep in the command queue when it is done dealing with other commands/messages. If it was left to the battery driven device, battery lifetime would be much shorter

[mMarcVD]

I think two things are being messed up here:
- the device on time value (parameter 3) gives the time to stay "on" when "something is detected in the room". When this on time is high, and there is only movement in the room now and then, there will be many on/off messages sent and sending costs energy. If movement is permanently however, it won't matter much in number of messages and energy. I guess the PIR sensor itself, as it is always active anyhow, doesn't consume much.
- the time the device goes to or is put to sleep. My experience is that Razberry sends it out too fast. I can't get this device to work in battery mode for more than some hours with automatic sensor updates every four minutes. After some cycles, the sleep comes in too fast / a bad moment and the device goes "tilt" (blinking led, reset needed). Can this parameter be adapted on the RaZberry?

[RCC]

I still have no idea what I'm doing, but I struggled with the same problem until I found the right set of values by trial and error:

1: None
2: 1
3: 240
4: 1
101: 225
102: 0
103: 0
111: 720
112: 720
113: 720
Wakeup: 480

The key values for me where 101 and the wakeup time. Value 101 makes the device push temperature/light/humidity data every 720 (parameter 111) seconds to Group One. Setting the wakeup time below 480 results in blinking red lights and no sensor data, setting 101 to 1 or 0 results in sporadic sensor data and negative values of temperature.

The trick to setting the values and having them stick was using the Blue UI instead of the expert UI (which doesn't know what to do with 101-103, and for which the advanced settings just don't work).

I have two sensors, one on battery and one on USB and both have been functioning absolutely perfectly for a week with those settings... I hope that helps.

Parameter 3 is the "stay awake time" and it either tells the device to stay awake for that amount of time after waking up (if not put back to sleep) or it tells it not to report motion events that occur fewer than n seconds apart. It is not documented very well, but the latter behavior is what the equivalent parameter on the Fibaro sensor does.

[elvizgz]

- the device on time value (parameter 3) gives the time to stay "on" when "something is detected in the room". When this on time is high, and there is only movement in the room now and then, there will be many on/off messages sent and sending costs energy. If movement is permanently however, it won't matter much in number of messages and energy. I guess the PIR sensor itself, as it is always active anyhow, doesn't consume much.

Thanks mMarcVD. My question was that. All clear!