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

PIN to disarm alarm #105

Closed
ajobbins opened this issue Oct 6, 2020 · 8 comments
Closed

PIN to disarm alarm #105

ajobbins opened this issue Oct 6, 2020 · 8 comments
Labels
enhancement New feature or request

Comments

@ajobbins
Copy link

ajobbins commented Oct 6, 2020

There is an option in the scheduler to disarm an alarm panel, but this fails without the pin code to the alarm. Could this be added to to scheduler card so that the PIN can be sent as part of the service call to disarm?

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label enhancement to this issue, with a confidence of 0.75. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the enhancement New feature or request label Oct 6, 2020
@KTibow
Copy link
Contributor

KTibow commented Oct 6, 2020

Is it possible to look for the pin in config, so you don't need it?

@KTibow
Copy link
Contributor

KTibow commented Oct 6, 2020

That is Home Assistant config, somewhere in configuration.yaml or .storage there's a PIN.

@ajobbins
Copy link
Author

ajobbins commented Oct 6, 2020

Yes, it's set in the config when setting up the alarm, but you have to pass it into the service call to disarm (I guess to ensure that you're not able to call a disarm without knowing the disarm PIN).

If doing it with a service call (say in an automation), you have to pass in the PIN in the service data, e.g.

- service: alarm_control_panel.alarm_disarm
  entity_id: alarm_control_panel.alarm_name
  data:
    code: 1234

@KTibow
Copy link
Contributor

KTibow commented Oct 6, 2020

I think this just requires being able to disable the slider for a variable and use a text field instead.

@nielsfaber
Copy link
Owner

The pin code of the alarm_control_panel is not a property that I could detect, so you will have to enter manually.
You could customize the action for disarming and add the pin:

customize:
  alarm_control_panel.my_alarm:
    actions:
      - service: alarm_disarm
        service_data: {code: 1234}

Adding a text field in the scheduler for setting it up would be another option (as @KTibow says).

But I must warn you. The pin code will not be encrypted, it will be visible in the properties of the schedule entity.
And there is also the safety hazard that if you go out of town for a couple of days, you really need to disable the schedule.
If you're OK with these risks, no problem.

@KTibow
Copy link
Contributor

KTibow commented Oct 6, 2020

There's a reason most non-HA automation only lets you arm an alarm and not disable it automatically, for security. It could help, but is it really worth the risks?

@nielsfaber
Copy link
Owner

Time to clean up old issues.. Please re-open if the issue is not resolved.

@p6sfrx725z28knfy
Copy link

The ability to disarm an Alarm panel via a schedule is something that I would find useful, and in my case would use the condition so that automated disarming only happens from the armed_home state.. ie would not present any risks should we be "out of town for a couple of days"..

However the challenge I face with the suggestion to customize the alarm panel is that this may impact other service calls to disarm the alarm, while obviously I would still require a PIN code to be used to disarm the alarm via the physical keypad.

So it would appear this is one of several use cases to pass additional data or parameters when calling a service from a scheduler, which would help make the already very useful scheduler-card even more flexible :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants