Checklist
Proposal
Currently, all user and code settings in Alarmo are global: code_arm_required, code_disarm_required, and user accounts all apply equally to every area. There is no way to configure these differently per area.
Use case
With multiple areas configured, it is common to want different security requirements per area. For example:
- A main house alarm should require a code to arm/disarm.
- A garage or outbuilding alarm should be operable without a code (e.g. for automation use or lower-security zones).
- Certain users should only have access to specific areas, not all of them.
Proposed solution
Move code and user configuration from the global level to the per-area level:
code_arm_required and code_disarm_required should be configurable per area.
- Users should be assignable to specific areas, so a user can arm/disarm only the areas they are permitted to access.
This would be consistent with how other settings (arm modes, delays, sensors) are already scoped per area, and would make Alarmo significantly more flexible for multi-area setups.
Checklist
Proposal
Currently, all user and code settings in Alarmo are global:
code_arm_required,code_disarm_required, and user accounts all apply equally to every area. There is no way to configure these differently per area.Use case
With multiple areas configured, it is common to want different security requirements per area. For example:
Proposed solution
Move code and user configuration from the global level to the per-area level:
code_arm_requiredandcode_disarm_requiredshould be configurable per area.This would be consistent with how other settings (arm modes, delays, sensors) are already scoped per area, and would make Alarmo significantly more flexible for multi-area setups.