Default Alarm Code and Panic buttons

[Lou-Der]

Hello!

I want to thank you so much for your integration. It was so much easier than the old method and I'm sure it took a lot of effort.

Your integration is what made me go forward with Eyezon DUO as an alarm integration for my Honeywell P20. You might want to reach out for a sales lead option from Eyezon, perhaps you can get funded for this continued effort.

I am a bit confused on how to configure the system to prompt for the user codes on arm/disarm. When I remove the "alarm code" from the default configuration it prompts properly for the code but then disables multiple entities like the panic buttons and chime toggle.

Perhaps a toggle to "Force Code entry" on the alarm_control_panel.alarm_partition_1 entity would be the simplest solution. You could also put default "user code" on the panic buttons I guess. Not sure of the requirements for these buttons and having to prompt for the code during a panic button would be sub-optimal.

I've also configured my panic buttons to toggle only on Icon Hold. For some this may be unclear on how to setup, maybe make it default as accidental alarms are a big issue!?

Thanks again!

[ufodone]

When I remove the "alarm code" from the default configuration it prompts properly for the code

This is the expected behaviour for the integration which dates back before I got involved with it. However, I just released a 1.0.0-beta2 version which has a new setting which allows you to control when the keypad is displayed. This would allow you to set a default code but then separately choose when you want the keypad to be displayed.

but then disables multiple entities like the panic buttons and chime toggle

That shouldn't be the case and is possibly a bug. Have you checked the logs for any errors?

Some of what you're suggesting isn't likely possible to do from the integration itself as Home Assistant has entity classes (like switches, sensors, etc.) that have defined interfaces that the integrations much conform to. So, for example, I don't think it's possible for the integration to add an alarm code or a "long press" for the panic buttons. I have considered making the panic buttons something that need to be explicitly enabled in the config though to at least have people have to think about it before enabling.

[Lou-Der]

Nothing in the system logs. I turned on your debug logging and didn't see any errors when removing and adding the user code.

I've confirmed once default user code is removed the 3 panic buttons and chime toggle become "unknown/unavailable". I even tried a reboot.
Also the chime toggle displays:
This entity is no longer being provided by the envisalink_new integration. If the entity is no longer in use, delete it in settings.

Does the beta version with the keypad setting "force/require" entering the code, or does it allow to send an "arm" request without it and then the default is used? If it's required that would work for me :)

[ufodone]

The chime switch becoming unavailable when the code is removed is to be expected because toggling the chime on a Honeywell panel requires the code. So if the integration doesn't have one available, there isn't any value in creating the chime switch.

I'm still at a bit of a loss as to why the panic buttons would disappear though as activating them doesn't require a code. I tried to reproduce that on my own system with a mocked Honeywell panel and I don't see the panic buttons disappearing.

Does the beta version with the keypad setting "force/require" entering the code, or does it allow to send an "arm" request without it and then the default is used?

The behaviour of the alarm control panel entity is largely controlled by how HA has defined these entities to work. If the user enters a code on the keypad and then tries to arm/disarm the system, it will pass that code to the integration. If the user does not enter a code on the keypad and tries to arm/disarm then it will pass the default code to the integration if one has been configured.

The keypad setting for this integration just controls when the keypad will be shown in the UI and doesn't change the arm/disarm behaviour.

If I understand you correctly, you want it to be required that the user enters a code to arm and disarm the alarm via HA. If so, the only way to do that at the moment is to NOT set a default code. That, as discussed above, has the side effect of disabling the chime switch though.