Sonoff SNZB-02 Temp Sensor Reporting Interval

It is interesting to see others with the same concerns I had. I never found a solution to this problem/issue/concern that I had. However I am not sure if it is actually a problem unless you want smooth regular graphs.

My final solution was Tasmotised Sonoff Zbridge to ZHA. 12 SNZB-02 sensors to cover the rooms in the house and an Ikea TRÅDFRI plug to act as a bridge for two of the rooms that were just too far from the bridge. All sensors are paired with the bridge the Tradfri is only a repeater and controls a lamp on the landing.

I have now been running my heating system since August using the room temps from these devices and it works. Most sensors are still at over 90% battery with the kitchen (which has the most temp and humidity changes) at 64%. So it looks like I will get a year or more out of a battery.

I do have temperature graphs with all sorts of reporting intervals. But to put my mind at rest I have two LYWSDCGQ 01ZM sensors that I have moved around and on the whole agree (although with more data points) with the sonoff sensors. It is strange how depending on people in rooms, wind outside and many other things room temperatures do not change much. I think I would prefer the Mijia sensors (screen is nice and AAA battery is better) but the overhead of getting good BLE coverage in my house is not worth it.

I was also tempted by zigbee2mqqt but the Tasmotised Sonoff Zbridge can be placed in the middle of the house, is cheap and prebuilt hardware. I am also not sure what a decreased/regular reporting interval for temperature would do to the battery life. It would be nice to have a max interval of 15mins though.

Not sure this will help anyone but thought I would share my current experience. Maybe in the summer when I do not need the heating I will look at this again.

@AndySM 15 mins interval for reporting the temperature is indeed reasonable, but when that interval goes up to 2, even 2.5 hours, there’s a problem. A thermostat can no longer rely on that sensor.

I have the same problem, I need more frequent update on temp. I am using ZHA with ziGate.
I saw that it’s possible to change the report interval using Zigbee2MQTT, so I thought it might be possible with ZHA.
In the device property I found some attributes to set, but even with the sensor awake, it doesn’t seem to update anything. Is it expected ?

Can you tell me how (and where) in the zigbee1mqtt interface i can change the reporting interval? I can’t fin it anywhere!

I came across this thread because I have the same question, though mine stems from devices behaving differently from one another. I bought 6xSNZB-02 in 2 batches of 3, from the ITEAD store, a couple of months apart. The humidity graph speaks for itself, you can tell which ones were bought together. I can’t work out why they would be different unless they have different hardware inside. Humidity

3 Likes

Hi Everyone,

I managed to fix the issue with sensor updating interval on Zigbee2MQTT integration.

Here is what I’ve done:
-Enable ‘Permit join’
-Put sensor in pairing mode
-Using Zigbee2MQTT interface select desired sensor and manage to the tab: ‘Reporting’
Your screen should look like this:

-Adjust Max and Min rep interval properties (in seconds) to your needs and click ‘Apply’

The whole process should be done before device gets out the pairing mode (~60 seconds), otherwise You won’t be able to save settings.

Hope that might help someone.

14 Likes

Worked perfectly for me, thanks for the tip!

I’m using ZHA. Wonder if I use Zigbee2MQTT just to do this setting, and then re-pair with ZHA, will it keep it?

Hi,

I didn’t try it with ZHA, so can’t really help You. Might be worth to try.

I can’t seem to find the things you’re referring to here. I’m using the same sensor and zigbee2mqtt in HA. I see no place where I can adjust the minimum report interval or a button to activate the device. I feel like a noob now. Can you be more specific as to the place where these settings can be adjusted?

I can never get to that screen that has Reporting as a tab. It seems strange to me that one has to have the device in pairing mode to set this. Wouldn’t these things be set on an already-paired device?

If you don’t have the Reporting tab, you probably have a very very old Z2M version since it has been available for months now with the new embedded Z2M GUI.

Thanks for that. I have version 1.15.0 of Zigbee2MQTT which I think is the most recent. I have Auto-Update switched on. Oh wait. I see on the Github page that the version is now 1.19.0. Not sure why I am not auto-updating. Must correct that!

Using Home Assistant OS Plugin, the last version is 1.18.1-1.
Have you access to Z2M GUI ? all settings ? the dashboard ? the map ? OTA ? Logs ?

I don’t recall the exact method I used to install it. I do have access to the Z2M GUI, the dashboard, map, OTA and logs. But no Reporting tab. I just have to uninstall this version and install the newer version from the Github link. Hoping I won’t have to repair all my devices…

Reporting tab is one the several tabs available for each device.

Sir, you saved my day :wink: thanks!

Thanks a lot, your solution works perfect!!!

Hi all

Found this post by seeking for temp range supported by Sonoff (spoiler: I’ve put it in freezer a couple hours ago and it is still reporting ATM).
Regarding the refresh rate, I think the refresh frequency is simply linked to a hardcoded temp delta before reporting.

Using this query in SQLite Web

SELECT created, state
FROM "states"
where entity_id = 'sensor.sonde_garage_temperature'
order by created desc

We see the interval is looking random, but the temp is changing fast in such situation and the report is done when temperature changed by at least 0.5°C :


For humidity, this seems to be 0.1%


I’d add there’s a minimum delay of 30 secs between pushes.

1 Like

I’m using ZHA and I was able to configure the reporting manually using following command:

bellows -v INFO -d socket://192.168.192.47:8888 zcl -D /home/homeassistant/.homeassistant/zigbee.db '00:12:4b:00:23:ad:cf:a1' 1 1026 configure-reporting 0 10 1200 10

You have to stop home assistant so bellows can communicate with the gateway. The command won’t succeed when the sensor sleeps, so you’ll have to repeat it until you see following message in the output:

[[ConfigureReportingResponseRecord(status=0)]]

Btw. re-pairing sets the default reporting configuration back.