codyc1515
commented
9 months ago Device seems to have remained on the network around 10 minutes now.
EDIT: Nope, the device is unresponsive (despite showing as Clear).
Open codyc1515 opened 9 months ago
codyc1515
commented
9 months ago Device seems to have remained on the network around 10 minutes now.
EDIT: Nope, the device is unresponsive (despite showing as Clear).
Hedda
commented
9 months ago What exact Zigbee Coordinator adapter and what firmware build / firmware version? Is the device connected via a other Zigbee Router or directly to the Zigbee Coordinator and if so which exact one? And are you following best practices to avoid EMF/EMI/RMI interference?
Is that an issue that can only be seen with zigpy-zboss radios or can it also be replicated with either the bellows or the zigpy-znp radio libraries using Silicon Labs EmberZNet NCP and Texas Instruments Z-Stack ZNP respective Zigbee Coordinator radio adapters? If it can also be replicated with other radio types then this should instead be reported as new issues to the GitHub repository for the main zigpy library -> https://github.com/zigpy/zigpy or to the ZHA Device Handlers (also known as zha-quirks) repository on GitHub -> https://github.com/zigpy/zha-device-handlers
Note! Aqara devices are a really bad use case for testing this early in development because you need to be aware that many Zigbee devices from Aqara (and Xiaomi) infamous for issues with both pairing/joining and having intermittent connection problems regardless if you which Zigbee gateway solution you use, and especially if those devices are connecting/connected via Zigbee Router devices that they too are known to have issues specifically with Aqara and Xiaomi devices, see -> https://community.hubitat.com/t/xiaomi-aqara-devices-pairing-keeping-them-connected/623 (which also applies here)
The fact is that Aqara and Xiaomi (plus also Tuya) are infamously known in the Zigbee community for not exactly following the official Zigbee specifications, and that makes them unpredictable to say the least. I therefore suggest simply staying away from them those devices this early in the development of this new radio library, or else the developers will end up having to focus on implementing special hacks around Aqara and Xiaomi instead of just focusing on getting this library fully compatible with the main zigpy library.
As such I recommend that you do not test Aqara, Xiaomi, or Tuya devices with this new radio library at this point. If you want to use those devices then better keep them on a separate Zigbee network that uses the bellows or zigpy-znp radio libraries.
PS: Anyway, best practices to avoid EMF/EMI/RMI interference always need to be followed, meaning using the radio dongle with a longer USB extension cable to a USB 2.0 port or via a powered USB 2.0 hub, see -> https://community.home-assistant.io/t/zigbee-networks-how-to-guide-for-avoiding-interference-and-optimize-for-getting-better-range-coverage/515752
The Aqara Smart Vibration Sensor leaves the network immediately after pairing (showing as Unavailable in HA). Does not come back when pressing the identify button on the device and requires re-pairing.