I’m using an integration to an external alarm system. Now a requirement came up to require PIN to disarm, only when the disarm action comes from certain locations (e.g. certain devices), and not require it when it comes from other locations.
The integration, as I believe all such integrations, has one setting - “require PIN to disarm”. Is there a good way to make this setting more granular? By device, by user, etc.?
One solution I thought of is to configure a second, manual, alarm system, and define its arm/disarm actions back to back onto my integrated system. That’d be a bit awkward but sounds like it would achieve this goal. Is there a better way?
Require pin. In the activities you want no pin required, use an automation or script that sends the correct pin. Use secrets so you don’t expose the pin in the wild.
My system will auto disarm on accepted unlock code on my door (i duplicate the pins in the locks) so if you correctly entered your pin in the lock, I can safely assume that I can also disarm the alarm so I embed the pin in the alarm disable service call. (check developer tools to learn how, it’s in the sample)
But if you open an alarm control panel on a tablet you’re still challenged for Pin because I do not embed the pin in any Lovelace controls.
I need to see whether embedding works in all my scenarios, but it sure is a better way to go at it then over-engineering a second alarm system just for that.
Thanks!
