I have one since february, that one works normally ever since.
Recently bought two more, but these do not report data normally.
one of the new sensors and the old one are next to each other, one reports data as it changes, the other only reports rarely, and inaccurately
the model and the fw-version is the same for all (at least as reported by zb2mqtt)
Case solved by setting up the reporting parameters with the zigbee2mqtt frontend (web UI)
Many error toaster rise during the setup, but the process works fine eventually
I also made the reports from the 02(not D) devices rarer to spare battery
now all devices report by the same schedule
I also have big trouble with my 8 SONOFF SNZB-02D. In average two of these eight per day stop reporting values and need repairing with removing battery, restarting Z2M and all this stuff. And problems got this bad when I switched from ZHA to Z2M. Using ZHA I had very few problems, maybe once per 2-3 months.
Using both Z2M and ZHA with one coordinator isnât supported, right?
try to adjust the report interval using z2mâs web frontend!
solved te case for me
@heidricha Iâm having the very same issue, unfortunately as newbie I fail to understand the mentioned solution.
Maybe youâd have a reference to understand âhow setting up the reporting parameters with the zigbee2mqtt frontend (web UI)?â
Update:
using a USB 2.0 hub that uses an external power supply my issue was fixed!
I managed to change reporting interval to 30/300/20 for three of my eight devices for now. Changing the reporting interval needs MANY attempts to be successful and only worked after fresh restart of z2m and âa bunch of luckâ.
All this smells like a lot of bugs hidden in firmware and/or z2m.
FWIW.
My experience August 2024. RPi-4.
I started with three SNZB-02D sensors and had a lot of issues with data collection, using ZHA. I had the earlier Sonoff Zigbee 3.0 Dongle-P as a co-ordinator.
Adding the devices to HA resulted in:-
one providing temperature and humidity data.
one providing temperature only.
one providing humidity only.
Numerous resets, battery installs, deleting and re-adding devices, with the sensors within 1metre of the Dongle, resulted in all three providing temperature and humidity but update time rather flakey.
I was keen to use these T&H sensors, so decided to change the Sonoff zigbee dongle from the earlier -P type to the new -E type.
Added each device again, located within 1m of the new dongle.
It made a significant improvement on data stability.
LQIâs jumped from around 100 to nearer the 200 mark. (When moved back to their original locations).
Eventually added four more, which seems to have gone wellâŚ
Iâm getting what I consider to be an acceptable update rate.
I flashed the original zigbee dongle with repeater software.
But thatâs another story!
All battery powered devices goes to deep sleep mode for most of the time to save battery juice. Sensor is awake for brief moment just to send data and only during this time you can send config to it. Have you tried to wake sensor up before sending new config? Wake the sensor up by pushing a pairing button for a moment just before sending config via zigbee2mqtt gui.
I also have those sensors, and for me, setting up the reporting configuration in Z2M fixed the issue. I believe the problem occurs because the SNZB-02D sends data with one decimal place precision, unlike the SNZB-02, which uses two decimal places. Adjusting the value difference threshold that triggers data transmission helped resolve the issue in my case.
IMO itâs a home assistant issue not a Sonoff issue, hence deleting the sensor and re-adding it fixes it. Always been the same for me for last 3 years. Just had to do 2 of mine today, first time in 3 months following a restart of HA
Clearly HA is getting the readings else they wouldnt suddenly work once device is deleted and re-added
I suspect this is a database issue and deleting the sensor removes it from the db and creates a new entry with new ID. Leaving the device configured and re-pairing it without deleting it first rarely fixes it. But deleting the device and re-pairing it with the same name usually does.
I wouldnât hold your breath on a fix, itâs just part of the HA experience.
My eight snzb-02d devices are (were) running quite stable for several days⌠until the weekly automatic reboot of my home assistant system last night. Two of the devices didnât report after the reboot (showing constant values for temperature and humidity and a âlast seenâ value before the reboot).
What is interesting: I could heal the problem for both devices by a manual ârefreshâ of temperature and humidity in the z2m device details.
Since that manual refresh both devices are reporting regularly ever few minutes again.
So this may be a problem in z2m? Or at least a possibility to workaround a device problem by an automatic refresh triggered in z2m?