I've had the chime exposed as a switch for a year and a half. I use it in an automation to turn the alarm chime on at dusk/off at sunrise.
Ensure you have the packages definition in your configuration.yaml as demonstrated below,
as well as the alarm_code present in your secrets.yaml.
Once that is done, add the alarm_chime.yaml to packages/alarm/ folder, updating the two entities as commented at the top of that file.
| # NOTE | |
| # You will need to change `alarm_control_panel.home_alarm` and `sensor.home_alarm_keypad` to match the entity names you have. | |
| script: | |
| send_alarm_command_with_pin: | |
| fields: | |
| command_after_pin: | |
| description: "The command to send after the pin" | |
| variables: | |
| alarm_code: !secret alarm_code | |
| sequence: | |
| - service: envisalink_new.alarm_keypress | |
| data: | |
| entity_id: alarm_control_panel.home_alarm | |
| keypress: "{{ alarm_code }}{{ command_after_pin }}" | |
| - delay: | |
| milliseconds: "1000" | |
| toggle_alarm_chime: | |
| sequence: | |
| - service: script.send_alarm_command_with_pin | |
| data: | |
| command_after_pin: "9" | |
| turn_on_alarm_chime: | |
| sequence: | |
| - condition: state | |
| entity_id: sensor.home_alarm_keypad | |
| attribute: chime | |
| state: off | |
| - service: script.toggle_alarm_chime | |
| turn_off_alarm_chime: | |
| sequence: | |
| - condition: state | |
| entity_id: sensor.home_alarm_keypad | |
| attribute: chime | |
| state: on | |
| - service: script.toggle_alarm_chime | |
| switch: | |
| - platform: template | |
| switches: | |
| alarm_chime: | |
| friendly_name: "Alarm Chime" | |
| value_template: "{{ state_attr('sensor.home_alarm_keypad', 'chime') }}" | |
| turn_on: | |
| service: script.turn_on_alarm_chime | |
| turn_off: | |
| service: script.turn_off_alarm_chime |
| homeassistant: | |
| packages: !include_dir_named packages |
| alarm_code: 1234 |