Osram Smart+ Zigbee motion sensor reporting interval to fast

I just bought and set up a few Osram motion sensors.
The first one had an empty battery after about a week.

Me being new to OpenHAB, didn’t’t know what to look for. SO I assumed the battery was faulty or something. So after adding a brand new battery I started to keep an eye on it. With my new gained experience with OpenHAB I took a look at the logs and found the motion sensor reporting changes down to 0.01C every minute.

Not only are those temperature changes within the error-range, but also not useful and draining a lot of battery.

For my only battery powered z-wave thing, I found a configuration that can set the change-reporting threshold. SO I’m looking for something similar for this Zigbee thing. but I cannot seem to find any such setting.

Searching the forums and google, the only thing I can find is a thread talking about how the Zigbee reporting interval is hardcoded to be within 1s-10mins in the binding. Zigbee polling frequency change? Devices reporting every 5 minutes

Is anyone else having such problems or is it just me? Because this way, the motion sensors are useless, requiring a new battery every other week due to the power/battery drain, probably caused by the reporting interval

So my question is. How can I change the reporting interval of the Zigbee battery powered devices, like I can change it for the z-wave thing? Or even switch to polling.

2018-11-03 14:42:56.362 [vent.ItemStateChangedEvent] - MotionSensorA_Temperature changed from 19.08 °C to 19.09 °C
2018-11-03 14:43:15.167 [vent.ItemStateChangedEvent] - MotionSensorA_MotionPresence changed from OFF to ON
2018-11-03 14:43:45.911 [vent.ItemStateChangedEvent] - MotionSensorA_MotionPresence changed from ON to OFF
2018-11-03 14:43:56.494 [vent.ItemStateChangedEvent] - MotionSensorA_Temperature changed from 19.09 °C to 19.15 °C
2018-11-03 14:44:56.649 [vent.ItemStateChangedEvent] - MotionSensorA_Temperature changed from 19.15 °C to 19.17 °C
2018-11-03 14:45:56.798 [vent.ItemStateChangedEvent] - MotionSensorA_Temperature changed from 19.17 °C to 19.19 °C
2018-11-03 14:46:56.924 [vent.ItemStateChangedEvent] - MotionSensorA_Temperature changed from 19.19 °C to 19.20 °C

Thanks in advance

By any means, that sounds way to fast a drain. I’ve got six hue motion sensors, they have a 5-minute reporting interval, and all of them still do fine after well more than a year. You said you got several, do the other sensors misbehave the same way? Or maybe just this one is having a real hardware problem?

the others are showing the same behavior, reporting tiny temperature changes every minute. Didn’t want to waste even more batteries on those, so I kept them unpowered after I saw they were reporting the same way.

2018-11-03 15:50:37.335 [vent.ItemStateChangedEvent] - MotionSensor2_Temperature changed from 19.45 °C to 19.46 °C
2018-11-03 15:51:07.481 [vent.ItemStateChangedEvent] - MotionSensor2_MotionPresence changed from OFF to ON
2018-11-03 15:51:37.451 [vent.ItemStateChangedEvent] - MotionSensor2_Temperature changed from 19.46 °C to 19.47 °C

A reporting interval of 1 minute is just way too high, and will drain the battery way to quick. maybe not in a few weeks with quality batteries, but it will certainly not last a year like that. it’s just tiny batteries.

Well, of course they show the same reporting interval if this is hardcoded. A CR2 is small, but packs quite a few mAh, just a little less that the typical Alcaline AAA, in fact. https://www.techhive.com/article/3176321/lighting/philips-hue-and-sylvania-lightify-motion-sensor-reviews-these-add-ons-make-your-smart-lighting-smar.html says it should last about two years. So I still suspect the unit itself has a problem. You should test the others the same way.

I have one of the others running right now.

I assumed that other bridges might set a different reporting interval on those devices when they get paired, but for some reason openhab might not do that. Just like I was able to set the interval on the z-wave thing.

How do you come to the conclusion that the reporting interval is hardcoded into the DEVICE, and not settable?

For hue, the bridge sets this, the api does not offer a documented way to set this from outside. So it is hardcoded in the bridge, but unless you program that yourself or the api explicitely offers it this is not accessible to you.