Binary Sensor (or Alarm) Issue

Community,

I’ve been using the alarm feature in Hass.IO to monitor and interact with my DSC alarm. It works wonderfully for arming/disarming and triggering events when a door opens/closes. One thing I noticed when attempting to automate a notification when it’s after midnight and my garage door is open is that the binary sensors go back to “off” or “closed” after a minute or two. I can reproduce the issue by just leaving a door or window with a sensor on it open, sure enough, I get the initial switch to “on” or “open” but then after a minute or so, it goes back to “off” or “closed”, the door/window is still OPEN!

I’ve been racking my brain on this one; any help is much appreciated.

The latest version of Hass.IO with a DSC alarm connecting to Hass.IO through an EnvisaLink 3 module.

I just integrated Envisalink with my HA setup and have a similar issue occassionally. However, mine goes from closed to open which triggers a light to come on (at night) after I’ve turned it off! It fixes itself after maybe 30 seconds.

My guess at the moment is that there is a race condition between the status update and the zone dump. Since the zone dump isn’t needed for DSC, I set the zonedump_internal to 86400 so that it only dumps once a day. While this may still have a race condition once a day, I have my HA restart daily (just because), so I think everything will get restarted and will be good.

I dug through the pyenvisalink code and it doesn’t look like there is a way to completely disable the zone dump.

You solved my problem! It works but seems like a bit of a hack to get what we need. In my case, I’m not sure how it’ll work out as I was using some automation to close the garage doors at 8PM if they were left opened by mistake. I use the alarm binary sensor as the condition of my automation, not sure it’ll work if I’ve rebooted my HASSIO system before 8PM on any given day…

Thanks for the help!