Closed palazzem closed 3 months ago
cc @andr3a88 who is impacted by this issue.
After some investigation, I discovered that the issue happens for two main reasons:
STATE_ALARM_ARMING
with HK_ALARM_AWAY_ARMED
. When users activates a given mode (e.g. Arm Home), the integration goes in this state transition:
What can be fixed in the integration has been fixed, but the issue still persist. Further changes should happen in the Home Assistant code base as other developers are trying to fix it (e.g. https://github.com/home-assistant/core/pull/108863).
@andr3a88 I'm moving the conversation in HA repository as the change should happen there.
Describe the bug The integration changes the alarm state temporarily (a blip) when the state is changed via HomeKit. For instance, when "Arm Home" is activated, the alarm goes temporarily into "Arm Away" and then "Arm Home" after few seconds.
This blip, triggers also unwanted integrations.
Error message None, other than the incorrect behavior.
Expected behavior When a user select an alarm mode (e.g. "Arm Night"), the alarm should go directly to that state.
Additional context It seems happening only while HomeKit, but it may happen also if you change states using the alarm panel without code.
To Reproduce
Environment