The zigbee sensor updates data several times per minute

Add-ons Bindings
, ,
1

Hello, everyone! I have encountered some strange behavior with the sonoff snzb-02 climate sensors. I have two climate sensors, and they update their data several times per minute. I haven’t noticed this behavior before. Perhaps it appeared after updating to version 5.0.0, but I didn’t notice it.
Now the log looks like this:

info_circle 22:54:32.095	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.84 °C to 20.86 °C
info_circle 22:55:02.201	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.86 °C to 20.84 °C
info_circle 22:55:12.236	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.84 °C to 20.79 °C
info_circle 22:55:22.273	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.79 °C to 20.86 °C
info_circle 22:55:32.308	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.86 °C to 20.84 °C
info_circle 22:56:22.505	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.84 °C to 20.86 °C
info_circle 22:56:32.548	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.86 °C to 20.83 °C
info_circle 22:56:42.577	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.83 °C to 20.86 °C
info_circle 22:56:52.618	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.86 °C to 20.88 °C
info_circle 22:57:02.655	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.88 °C to 20.83 °C
info_circle 22:57:32.784	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.83 °C to 20.81 °C
info_circle 22:57:42.852	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.81 °C to 20.84 °C
info_circle 22:58:22.985	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.84 °C to 20.79 °C
info_circle 22:58:33.014	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.79 °C to 20.75 °C
info_circle 22:58:43.058	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.75 °C to 20.88 °C
info_circle 22:58:53.106	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.88 °C to 20.86 °C
info_circle 22:59:03.139	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.86 °C to 20.84 °C
info_circle 22:59:43.307	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.84 °C to 20.79 °C
info_circle 23:00:03.401	INFO	openhab.event.ItemStateChangedEvent	Item ‘bedroom1_temperature’ changed from 20.79 °C to 20.86 °C

I use Zigbee binding + Sonoff Dongle-E (Ember).
Other types of PIR sensors, such as door opening sensors, behave normally.

2

Hi,

I have several of those exact same sensors and also use same dongle.

I have seen that behavior occur for a few reasons .

One being a breeze or constant air movement passing across the sensor.

2nd reason was the battery in the sensor getting so low that the actual sensor detects the temp change as battery voltage fluctuates

3

Thank you! Wind can be ruled out. No one is home right now, and all the windows and doors are closed. How often do you change the batteries in the sensors? And what does the battery charge indicator on the sensor show? Mine never drops below 80%.

4

I replace mine about every 15 months I do not use % I look at the voltage if it is anywhere near or below 2.85 volts I just replace them the original cheap battery’s the sensors came with only lasted 6 months the energizers I replaced them with get about 12 to 15 months between replacements

5

This solution helped me. It’s a pity that the working setting is not implemented in the UI

6

Yea I knew about changing reporting interval but I had never had to do that as I mentioned before the times, I have had a sensor go into that 100th of a degree change report has always been resolved with a battery replacement. I do recall one time I let the battery on one get so drained I did have to remove the device and rediscover it to get it back to reporting. Kind of wondering why a OH upgrade would have caused your reporting config to change but perhaps it is related to this snippet from documentations

The binding will attempt to configure a connection with the device to receive automatic and instantaneous reports when the device status changes. Should this configuration fail, the binding will resort to using a fast polling (note that “fast” is approximately 30 seconds at this time).

Maybe during your upgrade it failed for that part of the binding activity.

as for adding this to the binding UI that would be a @chris question as he is the binding developer.

7

If you want to change the reporting period of these sensors, it can be done through the UI. This is available in the channel configuration. Or maybe I’ve misunderstood the question and you’re looking for something else?

image
image1476×1368 162 KB

8

Thanks, I have set the polling timings. This is like a temporary solution. I’m trying to figure out why the sensors started sending data every 10 seconds. I’ll change the batteries when I get home.

I have four snzb-02 temperature sensors and two snzb-03 motion sensors. I have tried different batteries, cheap noname and expensive brands. Both of them last for half a year at the most. Then the sensors going offline or start sending false data. False alarms of motion sensors or always 22C and 80% humidity. At the same time, the bindings show a voltage of 3 volts. Besides them I have constant power devices with supporting routing tables. But that doesn’t help much…