2 @tom_l and All:
Do you know what is expected behaviour of the component if you run this sequence when Require a code to set the alarm is enabled in settings?
I’m currently changing the code because of this FR and it’s a bit unclear to me…
UPDATE: the current behaviour is ‘override’ always works so even if Require a code enabled, it works as a code.
Greetings,
I’m using Google Assistant Cloud to arm and disarm my alarm based on the original instructions:
This works fine except that it ignores open sensors and arms the alarm. If the same sensor is open and I try to set it through this projects alarm panel I get the Open Sensors Found message. Is there a different way to call the script so that it just refuses to arm if a non-overridden sensor is open?
Alright! Here is a thank you from me too, for keeping this alive. I really hope Gaz is ok since we havent heard from him for a long time.
Here is a request, if this is possible:
Can we have a mode that will arm_away the alarm without motion sensors enabled, but after some time, it will arm the sensors too?
To give you my real life example, here is my problem:
I have a roomba cleaning my house and we activate it when we leave for work every morning. This thing needs a couple of hours to clean the house and if I arm_away the motion sensors will pick up the roomba and will trigger the alarm.
So, can I have an option to have the sensors disabled for 2 hours for example and auto activate them after that period of time?
My plan is to have a button on my interface using a boolean, something like Roomba is cleaning and when I arm the alarm , the sensors will be offline. The boolean will auto disable after 2 hours and the sensors will be online again.
I hope I made clear of my request. Please let me know if you wanna ask anything.
One simple way around this is to create a script. The script can be a simple delay, followed by a service call to arm the alarm. Create a button on your UI that you can press to trigger the script.
Even better…
If you can integrate the Roomba into HA, get it done via the same script but instead of the delay, use a wait_template to arm the alarm once the Roomba is finished.
An automation triggered by the vacuum docking with a condition that there is no one home and an action to arm the alarm would do away with the delay or wait template.
This is the sort of thing you automate yourself rather than asking an alarm component to be everything for everyone.
Thank you for the suggestions!
Automations would be useful in this case, but I cant leave the house unarmed.
As I understand it, you are suggesting to leave the house unarmed, and have it armed after the roomba is finished. This is no option unfortunately.
My request is to have the alarm armed away like it is now, but have an extra option to keep the motion sensors offline for a period of time.
Edit: Also roomba integration is not an option too. This is an old roomba 620 with no wifi. I have seen a lot of roomba hacks all over the internet (and for my surprise in this forum too!) but I dont think I could make it work.
Hi Just a quick question If the alarm is triggered and I have an automation to turn on the siren, how does it receive the order to turn off the siren when the triggered time has expired and the alarm turns back to armed.
i.e a possum or animal has triggered the alarm but then the pir goes back to clear after the trigger time has expired shouldnt the siren turn off?
How about arming the house in perimeter mode (arming door / window sensors etc.) when you leave and then have the automation arm it in away mode once the Roomba is finished? That way you still have some security while the PIR’s are not in use
This is where the delay could work. Arm the house in ‘perimeter mode’ and have a delay to then re-arm but in ‘away mode’ after your desired set period (the time expected for the Roomba to finish)
I guess in this case the automation / script to do what you want @argykaraz in switching from perimeter to away mode would need to have a disarm step in between, but in reality that would happen so fast that it really wouldn’t matter.
This would be nice - or at least if it can return a message when arming in an automation.
Another thing I’ve noticed, when I disarm my alarm through an automation, the HASS log reports [ALARM] PANIC MODE ACTIVATED!!! even though I don’t think that event ever fires and the alarm log doesn’t show it. Is this a bug?
Sorry I think you misunderstood I’m not trying to activate panic mode (I haven’t set it up yet), but I’ve noticed that when disarming via node-red, a “PANIC MODE ACTIVATED” entry gets put into the HASS logs when it hasn’t been activated.