You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
If I want to make a restricted alarmdotcom user (custom, who cannot read the arming codes), this integration cannot get the arming state.
I would like to give my users as less Rights as possible.
I would like to not allow security code access to this user, but still read the arming state with this integration.
Of not possible, no harm.
Sincerely
The text was updated successfully, but these errors were encountered:
Thanks for the feedback. Possibly in a future release. Home Assistant doesn't have a read only concept for alarm control panels, lights, garage doors, etc. If you have read only access to an alarm system, Home Assistant will still show the Arm Home and Arm Away buttons. It's a bad experience.
There are two options here:
Build custom "read only" sensors in this integration for all supported Alarm.com devices. I.e.: A "sensor" type entity for your alarm control panel.
Petition HA devs to implement read only modes on an entity-by-entity basis. Once that's done, update this integration to use that feature.
There's also a third option of just not breaking on read-only devices, showing them as-is in HA with controls that do nothing.
In v0.2.4 of this integration and v0.2.6 of pyalarmdotcomajax, I released a "read_only" attribute for all supported devices. This can be used for building out either one of the two above options.
Hi
If I want to make a restricted alarmdotcom user (custom, who cannot read the arming codes), this integration cannot get the arming state.
I would like to give my users as less Rights as possible.
I would like to not allow security code access to this user, but still read the arming state with this integration.
Of not possible, no harm.
Sincerely
The text was updated successfully, but these errors were encountered: