Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ZHA - Aqara Motion sensor timeout? #548

Closed
KentuckyMC opened this issue Nov 12, 2020 · 3 comments
Closed

ZHA - Aqara Motion sensor timeout? #548

KentuckyMC opened this issue Nov 12, 2020 · 3 comments
Labels

Comments

@KentuckyMC
Copy link

Just a small question here as well: Someone mentioned a software based solution which was available in zha_new component for the Aqara Motion Sensor Timeouts. (https://community.home-assistant.io/t/xiaomi-motion-sensor-with-zha-vs-zha-new/181215)

Is there a way to look into a way to get the Aqara motion sensors to work with less timeout? Now the timeout for motion is something like 2 minutes.

@puddly
Copy link
Collaborator

puddly commented Nov 20, 2020

Unless you've done the hardware mod to reduce their reset period, the two minute timeout is what it takes to get the sensor to stay triggered continuously as long as there is motion.

If you want to change it you can either modify ZHA or patch it at runtime with this custom component https://github.com/walthowd/ha-constant-modifier (see the example config, specifically the second option).

@Hedda
Copy link
Contributor

Hedda commented Nov 30, 2020

FYI, believe this is the referred Aqara / Xiaomi hardware mod to make it send motion every 5 seconds instead of every 2 minutes:

https://community.home-assistant.io/t/aqara-motion-sensor-hack-for-5-sec/147959

https://community.smartthings.com/t/making-xiaomi-motion-sensor-a-super-motion-sensor/139806

@github-actions
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants