Skip to content
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

Closed
joshward9182 opened this issue Jan 8, 2022 · 3 comments
Closed

Full Arm issue from Home Assistant #44

joshward9182 opened this issue Jan 8, 2022 · 3 comments
Assignees

Comments

@joshward9182
Copy link

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
Screenshot_20220108-194223.jpg

Texecom alarm type
Premier Elite 48

Home Assistant version
2021.12.8

Debug log
Screenshot_20220108-195155.jpg

@dchesterton
Copy link
Owner

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?

@joshward9182
Copy link
Author

I just went through and started messing with some settings and you were right, it was a panel setting..
This was the culprit:
IMG_20220112_151901__01.jpg

Apologies for raising this as an issue and appreciate the response 🙂

@dchesterton
Copy link
Owner

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants