generated from issacg/hassio-addon-devcontainer
-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Full Arm issue from Home Assistant #44
Comments
This is really odd. I use the exact same setup (full_arm = armed_away) which works as expected and I've never had a report of the app doing this before. The only thing I can assume is that your panel is configured differently? |
No problem, glad you've got it sorted 🙂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I have 'full_arm' mapped to 'armed_away' in Home Assistant config (screenshot below).
It successfully detects as 'armed_away' in the alarm_control_panel entity, when I manually arm with the Texecom keypad.
However, when trying in Home Assistant, it arms it in to the part_arm_1 mode. This happens with both the 'alarm_control_panel.alarm_arm_away' service and a manual publish to the relevant MQTT topic (with 'full_arm' as payload).
Application version
1.1.15
config below
Texecom alarm type
Premier Elite 48
Home Assistant version
2021.12.8
Debug log
The text was updated successfully, but these errors were encountered: