Seems like the SNZB-02 in general has issues based on the thread and such, I currently have the SNZB-02P that has been working without issue… so far, paired through ZHA on the skyconnect.
The thing is: are you questioning the device because of a zigbee issue that comes from your mesh which results in connection loss/having to repair or the accuracy of the sensor.
If you are running a zigbee network, you know that it’s not that obvious to have a reliable mesh.
In my HA, I am running Zigbee2MQTT version 1.40.2 with a EmberZNet coordinator on a flashed Sonoff ZBDongle-E.
My Sonoff SNZB-02D H-T sensor is not consistently updating Temp and humidity consistently 3/4 times an hour as seems to be the expected default. There are long, 3-5 hour periods when I receive no updates at all.
The Sonoff HT sensor is located about 6m from the Zigbee coordinator and it displays a fairly good link quality of 118.
Anyone else having the same problem?
I am using an automation based on THIS to manually poll all SNZB-02 sensors every 5 minutes. Works flawlessly.
trigger:
- trigger: time_pattern
minutes: /5
action:
- action: homeassistant.update_entity
target:
entity_id: >
{{ integration_entities('sonoff')
| select('search', 'temperature|humidity') | list }}
3 Likes
I have the very same behavior, but its the humidity that gets updated only once after pairing. Did you find a solution?
Try a new battery regardless of what the battery % the sensor tells you.
Mine said 72% battery, and still have iirc 3v when I use a multimeter to test the battery. So out of desperation I went ahead and used a fresh battery.
Et voala. It worked, at least for me.
Oh and btw, I have since changed the sensor readings reporting frequency & threshold.
1 Like
I also had an issue where the temp was reported at discovery, and then not updated and just went “Unavailable”.
The solution was to put the device into pairing mode
Put HA to discover devices
As soon as discovered / configured, go to device and hit reconfigure. Once that completes, it works perfectly. Doing reconfigure immediately after discovery is key, as just hitting reconfigure, and nothing was found, so needs to be done when it is “fully awake” after discovery.
Just an update here, I’ve been running around a dozen of these since then and I’ve experienced a roughly 60% failure rate since then, ranging from some that regularly drop off the network or quickly drain the battery, a couple that refuse to connect at all, a few that work for a while but then silently freeze and display a constant number like 73F 80% humidity. Another has failed such that the temperature works but the humidity always displays 100%. I’m slowly phasing these out and replacing them with the more expensive but so far much more reliable Aqara sensors. I haven’t had one of those fail yet.
Its funny. I’ve had aqara temp sensors for years and I’m looking to replace then since they are working so badly. Drops out from time to time and requires physical access to re-pair which is a pain. I thought mostly it was because they don’t follow the ZigBee standard. I was looking to get the sonoff ones but reading this thread they seem just as bad?
I have both. Sonoff ones are better.
The only time it stopped updating temperature changes was because of low battery (while the sonoff device still saying it has 50% battery…) So there are still some quirks… but miles better than Aqara’s dropping off unexpectedly.
Obviously that’s personal opinion - one data point. I’m not testing hundreds of those to show any conclusions statistically.
1 Like
It is funny I have exact opposite experience.
Out of 4 Sonoff I trashed 2 and replaced with Aqara.
Since then my setup is more stable.
1 Like