Adam Petrovic

In my case the difference is quite significant. Though the same difference is not observed in notes further up in the same document: Edit Mode:  Reader Mode: 

Can we get an update on this please? It's been sitting in pending for almost 6 months and is a pretty simple semantic change that doesn't impact existing configurations and...

It's not about the fact that I can build a workaround to this problem, it's that a core component is provided by Home Assistant that manages that state machine for...

Honestly, if you think that the notion of Instant vs Delay zones is an edge case in the design of any basic alarm system I would question whether you've ever...

> This would require research into existing integrations the provide alarm control panels and which ones could benefit/implement the suggested addition/change. Wouldn't this be, by definition, all of them? As...

All of the provided Alarm integrations have their own workflow for handling "triggered" alarms. They almost all exclusively use the alarm panel state machine to handle the armed and disarmed...

Can you clarify this logic? As far as I can tell, none of these other alarm integrations make use of the alarm PIN code feature either which is an attribute...

Agreed, let's move on. To give a generic example of how I imagine this could be useful: **Standard Alarm Integration Scenario** As a HASS user, I have an alarm system...

 Also seeing the same issue.

In my case the conflict exists with the [Linter](https://github.com/platers/obsidian-linter/tree/master/src) plugin