Problem with SNZB-02D

Hello I have a problem with the temperature sensor SNZB-02D. I have connected it via zigbee bridge, it’s working properly in the app and in scenes, but its indication doesn’t appear neither the insight menu, neither in Nspanel pro. I also use a SNZB-02 connected with the same bridge, and its’ working perfect. Both indications of temperature and moisture appear and in insight menu, and in nspanel.

Any idea?

Readings from more than one sensor cannot be displayed, regardless of the number of sensors. Only one sensor can be selected from the list. None of the Sonoff ecosystem devices allow anything else. The NSPanel, which has a built-in sensor, cannot display readings from its own sensor and an external sensor at the same time, even though there is plenty of space on the screen to present the data.
Some time ago I wrote to eWeLink (ticket) about this, suggesting that this should be changed. Perhaps a rotating display of the readings would solve this problem?

Yes I know that, but it doesn’t even appears in the list, so i can choose only this.

It means that your SNZB-02D is not connected. Do you see a Zigbee signal icon?

Screenshot 2024-01-15 033532

If you don’t, give the SNZB-02D another try.

I think you didnt understand me. The device is connected properly in ewelink in the main menu and in scenes menu. I can use it for scenes or for notifications.
The only problem is that it didnt give me the chance to use it as main detector in the insight menu, or in the ns panel pro menu (Ns panel has a temperature monitoring from a device in the main screen).It is not apperaring in the list where you can choose detector device.

I see. It’s weird. I have no problem with selecting in NSPanel, NSPanel Pro and eWeLink app.

I have SNZB-02D and SNZB-01P which I connected with ZBBridge-pro

They are working fine till… my router loose connection… than my wifi network stops working untill router reboots… Afterwards all deviced (for example S60TPF and ZBBridge-pro) comes back to their functionallity and historical data apart of SNZB-02D and SNZB-01P

Why they don`t reconect themselfs. They has to be removed and conected again manually… as a rasult of this I loose all temperature data and setup scenes…

Do You have any idea how to fix this?

If you delete the device from the APP, the data will be deleted and cannot be restored, even if the device is added back

So… how to force devices to reconect automatically with ZBBridge-pro?

try to re-power the zigbee bridge or sub-devices

Are You kidding me? How can I re-power sub-devices??? They are battery powered.

I think You don`t understand my question…

My zbbridge is powered all the time and after wifi router restarts zbbrigde comes back and I have access to this device after all… but what I don`t have access is snzb-02d and snzb-01p they are greyed out

Why those devices don`t connect do zbbridge-pro automatically?

Anticipating the next question, yes they are within reach of zbbridge (1-2m)

Repowering sub-devices usually means giving them a gentle poke, just a quick press of the reset/pairing button. Sometimes, yes, you’ll need a pin or something equally glamorous. But no, @StephenJ wasn’t suggesting you perform surgery and extract the battery with tweezers. Let’s not get dramatic.

It is dramatic to me…

I`m loosing all my temperature and humidity history and can`t use any scenes assigned to those devices… My heating system, air conditioning system, dehumidifier thay are all don`t work.

Single pressing reset/pairing button doesn`t work…

Only long press is working but it meens devices have to be re-add (they disappear form conneccted zbbridge devices) and therefore all their history disappears

In such a situation I disconnect the power of the ZBBridge Pro and turn it back on. ZBBridge Pro reconnects to wifi but also all zigbee devices reconnect to the ZBBridge Pro.

It works… thank You, but to do this I have to be myself at the place of zbbrigde…

eWelink app should allow remote restart

I’ve had many issues with the ZBBridge-P. The latest firmware update (2.7.0) seems to have sorted mine so hopefully it will fix your issues as well. :crossed_fingers: :crossed_fingers: :crossed_fingers: