-
Notifications
You must be signed in to change notification settings - Fork 35
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
Status "bouncing" on sensors #381
Comments
If you’re relying on sensors to trigger automations, you’ll have a much more stable experience if you use the Qolsys Appdaemon integration with home assistant, or the Homebridge Qolsys plugin that you can then connect to via the HomeKit component. It gives you local access to sensors and works in realtime |
I don't want to add more sensors, if that's what you are suggesting. I'd rather not add duplicate sensors to the doors and windows (there are a lot of windows in my house). The sensors I'm referring to are part of my existing alarm system. If I'm missing something about your suggestion, my apologies. |
I am not suggesting that, I’m suggesting you use a different method to integrate your alarm panel into Home Assistant, assuming yours is made by Qolsys like many alarm.com panels |
Just a thought, instead of discussing the use of Qolsys as an alternative here in this bug report, we should probably talk about this as its own Discussion topic since this contributes nothing to the bug report, itself. |
This will be fixed in the next version of the integration. I'll post instructions for testing the new python library tonight. Your ADT Commander is made by Ademco. Here's the FCC filing: https://fccid.io/CFS8DL-GRIPAIO7A/External-Photos/External-Photos-20190923-v1-ADT7AIO-EXHIBIT-4-1-External-Photos-4617041 |
Thanks for the info! |
The new version is ready for testing. See #391 if you're able to help. Thanks! |
Describe the bug
I have automation set up for things like turning off the HVAC when a window is open. Since this latest version of the integration, I am experiencing what I'd describe as a "status bounce" when opening a window or door. I noticed it because I have a complimentary automation for when all windows close that started getting triggered immediately after the open automation. Upon further inspection, it turns out the status is bouncing twice, settling into the correct status in the end. I've had to introduce 15s status durations to overcome it.
To Reproduce
Screenshots
![Screenshot_20240225_151105_Home Assistant](https://private-user-images.githubusercontent.com/1045052/307623069-cd831219-56ac-4ea8-bc46-140e5f66eb81.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM1NTM0MzMsIm5iZiI6MTcyMzU1MzEzMywicGF0aCI6Ii8xMDQ1MDUyLzMwNzYyMzA2OS1jZDgzMTIxOS01NmFjLTRlYTgtYmM0Ni0xNDBlNWY2NmViODEuanBnP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgxMyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MTNUMTI0NTMzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZTczMzI3NTI3YmVkYWE1YmY0MGZmNjM0OTY5MmY4MTJiZDI5M2UxNDIxNGI2Y2I5NTM5NjhkZTg5ZDZjOTFhYiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.IkL58Rc9Y0C4u1pJwPnFPqlxqhRKRRMqU--xYZEpjZg)
Version Information:
Core 2024.2.3
Supervisor 2024.02.0
Operating System 11.5
Frontend 20240207.1
Integration Version: 3.0.13
Using Update Int 10s and Websocket Timeout 300s, in case it matters.
The text was updated successfully, but these errors were encountered: