search

pyalarmdotcom / alarmdotcom

Custom component to allow Home Assistant to interface with Alarm.com
MIT License
114 stars 35 forks source link

Status "bouncing" on sensors #381

Open TheWebMachine opened 4 months ago

TheWebMachine commented 4 months ago

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

  1. Open a sensor/door/window (mine are all wireless)
  2. Look at HA ADC sensor entity history for that sensor and you will see the sensor close->open->close->open within 15-20s time
  3. ADC directly only shows one close->open, not two

Screenshots Screenshot_20240225_151105_Home Assistant

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.

ifeign commented 4 months ago

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

TheWebMachine commented 4 months ago

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.

ifeign commented 4 months ago

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

TheWebMachine commented 4 months ago

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

Ah, gotcha. I looked at all the pictures I could find of Qolsys panels and, while mine kinda looks like one of their panels, I couldn't find one (current or legacy) that exactly matches mine. For example, all of the Qolsys panels have their arming indicators as a single light on the right edge or dual LEDs at the top in opposing corners. My Panel has two lights sandwiching the camera in the center of the top bezel, AC Power indicator and Ready/Arm status.

Beyond ripping the panel off the wall and snooping around inside, how can I be sure? ADT and ADC do a pretty good job of rebranding the interface. There isn't even a mention of ADC in ADT's version of the interface, let alone a model number for the panel. ADT only refers to the panel as the Commander 7". Looks like this: ADT-Command-ADT7AIO

TheWebMachine commented 4 months ago

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.

elahd commented 4 months ago

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

TheWebMachine commented 4 months ago

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!

elahd commented 3 months ago

The new version is ready for testing. See #391 if you're able to help. Thanks!