We’ve been trying out a simple configuration of the V2 hub, an arrival sensor and two multi-purpose sensors in about 8 different locations. Except in two locations, we’ve found that the arrival sensor fails to operate properly after about a week or so.
The failure is that the state gets reported as “not present” even though the sensor is very much in the home and within feet of the hub. Removing and replacing the battery in the Arrival sensor fixes the problem (for another week or two). In some cases, we have had to go through the pairing process again for the sensor.
To try to understand the failure mechanism better I’ve set up a Zigbee sniffer with the TI CC2531EMK USB dongle and the Ubiqua sniffer software.
This was very helpful to understand the normal operation of the Arrival sensor but unfortunately did not shed any light on the failure as the failed sensors were not transmitting anything. After removing and replacing the battery, they did start sending Beacon Requests sequentially on all channels.
We believe we’ve followed the deployment best practices detailed in this forum and elsewhere - separating the AP and the hub by several feet, ensuring insecure rejoin is enabled, etc.
It’s not clear exactly how the Wi-Fi interference causes the failure - can someone shed any light? Even if the channel was busy or there was receiver de-sense one would thing eventually a ZigBee Rejoin would go through. What we’re seeing seems to imply a sensor firmware crash but of course we have no way to verify this.
One other factor - the locations where we see the failures have Xfinity gateways (with Wi-Fi APs) whereas in the two locations where the arrival sensors have worked without issues we have older 802.11n conventional APs.
I would appreciate any hints about how we can understand what’s going on here and how we improve the reliability of the Arrival sensors.
Thanks!