No it doesn’t output back to HA however this could be implemented using a sensor template. If I get a chance I’ll knock one up as this will also be handy for my FloorPlan SVG.
Those sensors need to be part of your immediate group too as the notathome title is a little misleading this group prevents the sensors triggering the alarm when in home mode
This was a little trickier than expected and no doubt there will be a cleaner way to do this. I couldn’t figure out how to feed in allsensors from alarm control panel so we dont have to add each individual sensor. I tried to monitor the sensors using
{%- set alarm = states.alarm_control_panel.house %}
{%- set sensors = alarm.attributes.allsensors %}
which works in the template renderer however HA doesnt update when used in template sensors. I’m not a fan of jinja tbh
Yeah thats part of the pending time config. I’ve set mine to 25 seconds. If any of the sensors in your ‘delayed’ config are triggered within 25 seconds it will be ignored if they are triggered afterwards they will activate the alarm
i have been playing about with it today and I get the following results
1 - Set the Alarm Away Home, with all the sensors closed (Off) works fine
2 - Set the Alarm Away Home, then open the day to leave and close within 30 Seconds all works fine
3 - Set the Alarm Away Home, with a sensor open in this case the Front Door Sensor (Delayed), then close the door within the 30 Seconds, the Sensor becomes inactive and does says inactive. until the alarm is disarmed.
Are you trying it with both arm away and arm home?
Arm Away Mode - The front door invokes the 30 second delay providing you have that sensor in the ‘delayed’ group. then triggers alarm if tripped after 30 seconds
Arm Home Mode - The front door sensor would immediately activate the alarm if tripped. There is no delay. I haven’t tried to ‘open’ the door then activate home mode, really you should be checking all the perimeter sensors are closed before you activate home mode. Home mode should be used at night time or when you want to arm the perimeter. This is why the ‘notathome’ group is there any sensors in that group don’t trigger the alarm if tripped during home mode.
To be honest I haven’t had the time to do any extensive testing with a baby in the house.
Updated bwalarm.py code below. I have modified drytoastmans original code to prevent the exclusion of these open sensors, there is probably a good reason for his original code but it doesn’t suit my needs. Would appreciate if you could test it, I have and it seems to work for me. If the sensor is open and the alarm activates in away mode it will still include the sensor in the watch list and reset its state to closed once its received even after the alarm has been set. I’ll get all this on github eventually either through proposed changes to drytoastmans or as a branch
im bless with a 16 and 4 year old girls, and I am not sure which one is the biggest pain / headache
the count down and panic button is great idea. i recorded the 30 sec bleep off our old alarm within the XIAOMI App, and when the alarm Home Away is set it kicks off an automation to play they 30 secs bleep through the Xiaomi hub so there is an audible bleep, and use a single longer bleep when its disarmed
Another feature could be that if an sensor in the immediate group is open the alarm will not set, and give you a warning, that you can overdrive is another maybe.
I am yet to implement this alarm into my system, which I hope to do next week. As I used to be a security installer I figured I would add a quick comment.
The way most commercial alarm systems work (as Hefford27 has indicated towards) is to notify you if a sensor is not in the correct state before arming (ie: ether open or in tamper) Generally the system would tell you which sensor(s) are not healthy and give you a prompt to either sort it out or isolate that input (ie: arm anyway and just not include that sensor in the code for that instance)
I really like the idea of having a countdown and warning tones being played from a Xiaomi hub, I will definitely try to do that at my place.
Once I get it programmed next week, I’ll be more than happy to test things out to help where I can.
Timer is implemented on both pending and warning. See attached screenshots. Will upload the code shortly.
I’ll crack the open sensor notification/override next. Tamper detection will be difficult as most sensors (zwave, zigebee etc) define different states/descriptions for tamper, I’m not certain we could have one solution that encompasses all.
As for the warning tones this should be built into your automations. Keep the ideas coming and any suggestions to improve the design.