You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I buyed zigbee stick and i don't know why, other sonoff devices works great, but there is a problem with keeping connection with snzb-02 temperature sensor alive. I can connect sensor to Home Assistant, but unfortunatelly after that device is going dark and device is not showing in HA devices tab. In zigbee2mqttassistant i can see only that device was online for example 2 hours.
To Reproduce
Steps to reproduce the behavior:
Connect sonoff snzb-02 device to ha
Wait ~10-20 minutes
Expected behavior
Sensor should be available as other sonoff devices
Steps I took to try resolve the problem
I removed device and connected again(three times), i added paper to battery, to make sure that there is no issue with battery
Screenshots
Installation
Version of Zigbee2MqttAssistant (this software): 0.3.157
Version of Zigbee2Mqtt: 1.20.0
Installation type (HASS.IO, Docker...): HASS.IO/superviser?
Pertinent logs
I don't know where i can find logs for this issue
The text was updated successfully, but these errors were encountered:
Describe the bug
I buyed zigbee stick and i don't know why, other sonoff devices works great, but there is a problem with keeping connection with snzb-02 temperature sensor alive. I can connect sensor to Home Assistant, but unfortunatelly after that device is going dark and device is not showing in HA devices tab. In zigbee2mqttassistant i can see only that device was online for example 2 hours.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Sensor should be available as other sonoff devices
Steps I took to try resolve the problem
I removed device and connected again(three times), i added paper to battery, to make sure that there is no issue with battery
Screenshots
Installation
Pertinent logs
I don't know where i can find logs for this issue
The text was updated successfully, but these errors were encountered: