core: Xiaomi Aqara motion sensor detects motion only after being `Unavailable`
Home Assistant release with the issue:
0.88
Last working Home Assistant release (if known): 0.87.1
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io running on Raspberry PI 3
Component/platform:
https://www.home-assistant.io/components/zha/
Description of problem:
After upgrading to 0.88 release my Xiaomi Aqara motion sensor doesn’t detect motion any more. Instead it is constantly in the Detected mode, when it’s on.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
zha:
usb_path: /dev/ttyUSB1
database_path: /config/zigbee.db
Traceback (if applicable):
Additional information:
Here is the initial availability of the sensor:
The gray period in between is when the sensor goes offline (expected for batter-operated devices), and then it again reports detected (I guess here it did detect motion):
And then again will stay in the Detected state until the device goes offline - Unavailable.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 16 (10 by maintainers)
Quirk isn’t applied… this isn’t going to work. Remove the device and rejoin it. If you use the dev branch this will no longer happen, or wait until the beta launches this evening.
Definitely nothing around this. It’s intrinsic to the stack itself and isn’t something we can really affect. If you have no communication errors in the logs then zha is most likely not involved. The only possibility is that your devices chose a different parent (some sort of router: smart plug, bulb etc.) that is closer to them and ages them differently or the keep alive messages from the device were sent during restart cycles and missed (if the devices have the stick as a parent)
All of this said, we did make a change to Zigpy that I believe is going to be in .89 that will increase the coordinator aging to 256 minutes for end devices. This will only help if they are directly connected to the coordinator.