SONOFF SNZB-02

[cllatser]

Device

• Product name: SNZB-02
• Manufacturer: SONOFF EWELINK
• Model identifier: TH01
• Device type:
  • Light
  • Lock
  • Remote
  • Sensor Temperature and Humidity
  • Siren
  • Thermostat
  • Other:

Screenshots

[SwoopX]

Closing this as device is now supported with .79 beta.

[Plaatjesdraaier]

Unfortunately, the Sonoff devices are only added in the app, but they do not indicate any values

[0nlytom]

It actually does work and connects properly. Can you please confirm the Appilication Version is 5? I managed to get mine to report data after manually setting the maximum reporting value to 600 second for the Temperature and humidity.

[Plaatjesdraaier]

Thanks for your reply. Where can I check the application version ?
I can only see Version 2.13.01 / 6-10-2021 and firmware 2672070

[tiix95]

Same issue here. Can connect SNZB-02 correctly but Phoscon app shows "Status : Not reachable".
Same version as @Plaatjesdraaier but firmware 26660700

[Smanar]

Have just buy one and have same issue.

After 3 tries it have finally worked, my procedure

• Long press (around 5s)
• Wait for 3 red blink
• press the button every 0.5s (during 4/5 s seconds)
• Force a read temperature in the GUI (not sure if it have an impact)

It have worked, at least 1 time, now I m waiting if it make report.

Edit:
So It still not working, no report, even with a bind made manualy.
And the device answer only during the pairing (during the short press), after that impossible to awake it. I think it have disconnect from the zigbee network.

[0nlytom]

The issue is that the reporting time interval is between 30 seconds and 65535 seconds. To get the sensors to increase the reporting frequency, the upper value needs to be changed. Please note, that once the device is pair, it maintains a connection with the coordinator for 30 to 60 seconds. All steps need to be complete before the sensor goes into sleep mode.
You will need to have deCONZ GUI open for this and pair the device via deCONZ, which is under the Control tab. Have the Cluster info tab open.
So, please read through everything first, as there is limited time to change the values.

1. Delete the old device
2. Set deCONZ into Pairing mode and switch to the Cluster info tab
3. Reset the sensor, hold the button down until the red LED flashes.
4. Wait for a new device to show up
5. Enable the dropdown menu by click the circle on the far right of the sensor.

5. Click on the Temperature measurement and go to the Cluster info tab.
6. Double click on the Meaured Value, this will open a new window allowing you to edit the attributes
7. Change to the Max Report Interval to 900. This is in seconds.

8. Now click write config. Above the button it edit notify you if it was a success
9. Do the same for the humidity.

Please note that the less the Max Report Interval, is sooner you will have to replace the battery

[Smanar]

Ha yes it have worked after some tries.
Have used 30/3000/100 as setting on my side.

The issue is that the reporting time interval is between 30 seconds and 65535 seconds

So it mean there is a problem, deconz need to set the reporting with thoses value for temperature

            rq.minInterval = 10;           // value used by Hue bridge
            rq.maxInterval = 300;          // value used by Hue bridge
            rq.reportableChange16bit = 20; // value used by Hue bridge

But we are not alone with issue on inclusion for this device ATM
Koenkk/zigbee2mqtt#8971
Koenkk/zigbee2mqtt#5562

And it s strange Max value prevent report, Min value ok, but max ....

[Plaatjesdraaier]

Hi Onlytom,
Thank your for your clear contribution.
At first it seems to work, but unfortunately the values are not refreshed

[Mimiix]

It probably takes a while

[Plaatjesdraaier]

Everything else updates except the SNZB-02's

It is also useful if the update frequency is not too low because, for example, I also use these sensors to activate the fan as soon as the humidity gets too high in the shower.
It is of course the intention here that the sensor detects the increased humidity as soon as the shower is switched on, not when I have finished showering

[Mimiix]

What happens if you click the button on them?

[Plaatjesdraaier]

I removed the sensors and added them again with the values: min 30 / max 600 / reportable 100 and now it works
(clicking the button did nothing)

[Smanar]

Yes, have same result.

The device can be included easily , but no report at all (for me it leave the network).
But if you just set a reporting setting like said 0nlytom it can work immediatly.

I have tried to wake up the device to set report after the inclusion procedure, almost impossible, even pressing the button, no way to wake up the device.
But I don't see why deconz can't set the reporting itself ....

[andreasgruener]

I followed the very precise and detailed description by 0nlytom and added 3 eWelink TH01, successfully.
Perfect!

[george-andrei]

For me too, I followed the steps described by 0nlytom and its working fine. Just be fast to add the humidity sensor as well.
Thanks!

[mgrn0]

adding two of the snzb-02 sensors with latest beta worked out of the box for me without ANY problems, no manual steps required.

[camarril]

adding two of the snzb-02 sensors with latest beta worked out of the box for me without ANY problems, no manual steps required.

Thank you!
I was setting up sizbee2mqtt for the fist time yesterday, using the latest stable version (1.22.1) and my SNZB-02 only sent battery and signal strength information once after pairing and then stopped working. No temperature or humidity. Today I tried the latest-dev image (published 11 hours ago) and now it works perfectly.

[mgrn0]

very weird, both my snzb-02 sensors lost connection today and I cannot get them to re-connect at all. removing (once) and re-pairing does not work, deconz does not 'see' them anymore. updating to latest beta did not help, both sensors are not recognized. battery levels were 100%, using a new battery does not help, neither.

any ideas?

[Mimiix]

@mgrn0 I suggest opening a forum post and add some logs.

[nook24]

@mgrn0 I have the exact same issue with the exception that my setup is brand new :(

---

Update and Solution
@mgrn0 pointed out that it is recommended to use a USB extension cable instead of plugging the ConBee 2 directly into the Pi.

Since I added the USB extension cable, my SonOff SNZB-02 and SNZB-04 are working as expected. Many thanks.

[AndRe5575]

@0nlytom is there a way to do this without GUI? I installed deconz without because I also use openmediavault on my PI and therefore I had to use the lite OS version without GUI. Pairing my sonoff sensor just works for about one day and then it´s not found anymore so I have to pair them again.

[0nlytom]

@AndRe5575 which version are you running? I know that in the latest version 2.13.04 everything work fine. Please try and upgrade.

[AndRe5575]

@0nlytom I use Version 2.14.01 and a Raspbee II with FW 26720700

[0nlytom]

@AndRe5575 Please try and reconnect the sensors. I successfully re-provisioned one sensor on version 2.14.01

[AndRe5575]

@0nlytom I reconnected them. One is working at the moment and one shows no new update since a few hours. The one which is working shows sometimes that the last update was / will be in 1 hour. A bit strange.

Edit: Now both are offline since hours.

Reconnected one sensor again and it shows an update time in the future.

seems that there are different time zones.

[Stubbs]

It appears that any devices added with an earlier version that had the default Max Report Interval set to 65535 still retain this value when re-added to the network, new devices work as expected.

I have tried updating the value while the device is awake immediately after adding to the network as described by @0nlytom however it seems to keep the incorrect value.

The local config still thinks it's set to 300 max, so I'm going to leave it overnight and see if it downloads this new config when massive timeout expire & it tries to connect in ~18 hours.

Can these devices be factory reset?

[TheSOMGuy]

Is there a working solution for this problem bc i run in the same situation with a completely new setup.
My door sensor is recognized as it should be but the Multisensor ( Temp/Humidity ) is not.
I can't use the deconz-gui bc of my headless openhabian installation and therefor i have to solve this by hand or has to by a new sensor.
And i really prefer the first one.

Any new suggestions?
Thanks

[Smanar]

What is the issue ?
Have you tried to re-include the device without deleting it ?

[BabaIsYou]

Can't it be included in a DDF that will be loaded at inclusion ?

[Smanar]

Yeah can use a DDF to bypass the legacy code, but I don't see what we need.
It's possible to change the "Max report interval" using a DDF too, but the legacy code do that too, the request probably fail

it should be but the Multisensor ( Temp/Humidity ) is not.

It's incomplete, bad values ....
A second inclusion can help for detection if this one is not finished on first try.

[BabaIsYou]

@0nlytom I use Version 2.14.01 and a Raspbee II with FW 26720700

Version 2.15.03 and ConBee II with FW 26720700 on RPi4 and no issue with my 3 devices.

[harphere]

Could someone kindly explain what is required to make these devices show values for temperature and humidity? I'm running deconz in Docker:

I've had the sensor for almost a week and I see only this:

and

[nook24]

In case you are using a Raspberry Pi it is important to connect the ConBee via an USB extension cord. That is very important.
Beside from this, start scanning for new sensors via the Phoscon Website and press the button on the Sonoff sensor to start pairing.

Also make sure that the battery in the Sensor has charge

That's basically it.

[dennisb1]

Could someone kindly explain what is required to make these devices show values for temperature and humidity? I'm running deconz in Docker: )

Just a tought but maybe a good idea to do update of deCONZ first? At the moment it is 2.20.01 / 19-9-2022
I'm almost also sure you need to do a firmware upgrade of ConBee afterwards.

[Smanar]

Lol, ha yes, haven't see that, 2.13 ^^, I think it s a new record.

[BabaIsYou]

@0nlytom I use Version 2.14.01 and a Raspbee II with FW 26720700

Version 2.15.03 and ConBee II with FW 26720700 on RPi4 and no issue with my 3 devices.

After upgrading to 2.19 and even on 2.20.1 I got the same issue than others.
SNZB-02 are visible after re-pairing (press button until blinking), without prior deleting it from Deconz, for a moment (between 1 to 3 hours) with green LQI line ... and then no more reports and greyed in Deconz-GUI until next retry with the same process.

[misel86]

very weird, both my snzb-02 sensors lost connection today and I cannot get them to re-connect at all. removing (once) and re-pairing does not work, deconz does not 'see' them anymore. updating to latest beta did not help, both sensors are not recognized. battery levels were 100%, using a new battery does not help, neither.

any ideas?

Hello, did you manage to solve this? I have the same setup and the status is Not Reachable after multiple restart/pairing/etc

[Smanar]

Do you have some logs ? or a capture from the GUI ?
What is your deconz version ? On the capture was the 2.13, so a realy old one.

[misel86]

Hello:

and I'm using DDF from #6697 with this modification:

[Smanar]

So same answer, update your deconz version, you have the 2.13 we are ATM at 2.23 (10 more offical versions)

[misel86]

Oh, okay, looks like I'm using the old docker image. My bad, thanks :D

/EDIT: updated to 2.23 and it works

[boelle]

i have the same issue and when i try to change the config from within deconz app i fails to write the config

even reading config fails

not that it matter i think but in zigbee2mqtt everything works except the addon stops a few times a week and faisls to restart on its own... i have to reboot the pi completely

[Mimiix]

@Smanar can you check the comment of @boelle ?

[Smanar]

Hello,
What are you trying to do ?
Those device are slepper, so you can need to awake them in same time you press the "read" button, generaly with short press on the reset button.

Can you show the cluster list ? (with pressing the "+" on the node title.

And you have no report at all, no temperature, no humidity, no battery ?

Nothing in logs about this device in deconz/help/debug view, with flag "info" * 2 and "error" * 2 ?

[boelle]

What are you trying to do ?

add the device just like a light bulb or switch

Can you show the cluster list ?

And you have no report at all, no temperature, no humidity, no battery ?

correct

Nothing in logs about this device in deconz/help/debug view, with flag "info" * 2 and "error" * 2 ?

will edit this post tomorrow, i have to switch from zigbee2mqtt to deconz each time i do testing. zigbee2mqtt works but crashes once a week, that is why i try to switch to deconz as i remember that as stable

EDIT:

the manual says this:

but it does not tell how to get there and i have a hard time finding the permit join

@Smanar can you tell how?

EDIT2:

found out... enable control panel, click the gateway... click the pairing tab

[boelle]

so i got one sensor added.... along with some other lights i have

if i blow air with my mouth it updates instantly

now to check if i'm also lucky with the other 4 i have

[boelle]

@Smanar everything worked first time today, not sure why it was such a pain yesterday

[Smanar]

Lol, zigbee is magic.
No seriously it's not normal, to add new sensor you don't need to use the "permit join" in deconz, just use phoscon, select "add new sensor" and make the procedure on the sensor.
Phoscon will enable itself the "permit join" for a limited period.

And you have other problem. Too much device with name like "0xXXXX" ....

@boelle You NEED to use phoscon, not deconz to include device. Deconz is a zigbee application, so you can include device using it, but you can bypass the API (it's just a deconz plugin).
If you use Phoscon, it make the "permit join" AND look at it to add device in the API. Else you can have the device in the zigbee network, but not in the API, and can explain the name like "0xXXXX"

[boelle]

And you have other problem. Too much device with name like "0xXXXX" ....

those changed when i began to add my light bulbs in phoscon

and yes i would normal use phoscon to add the sensors but that did not worked so i tried with deconz instead, that with all 5 of them, the day before even decons did not work for the sensors

but yeah, very "strange" that it did not work one day and then the next it does

EDIT: btw.... would it be in the near future to see an update function inside phoscon so we can easy update the firmware in devices?

[Smanar]

EDIT: btw.... would it be in the near future to see an update function inside phoscon so we can easy update the firmware in devices?

Yes, for the moment you can use the desktop version or enable automatic update with "router" devices, but yes there is nothing for sensor out of deconz.

[boelle]

i was thinking in phoscon, there are no section for updates

[Smanar]

Not for sensor, but you can enable OTAU for router device in the settings (automatic working mode, no specific action possibles). And you need to put files in a specific folder.

[boelle]

that is something i will miss from zigbee2mqtt, they have updates in one single screen for everything

but i guess a stable system that do not crash 1-2 times a week is better than easy updates :-D