From 44c12e1ba173ab1bbb3cd676461b61e7ddaf9bae Mon Sep 17 00:00:00 2001 From: jnimmo Date: Sat, 19 Nov 2016 09:01:55 +1300 Subject: [PATCH] Add supported services (#1249) To document the new alarm_keypress * Add supported services * Update envisalink.markdown --- source/_components/envisalink.markdown | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/source/_components/envisalink.markdown b/source/_components/envisalink.markdown index f5554c73228..522d7f52e9d 100644 --- a/source/_components/envisalink.markdown +++ b/source/_components/envisalink.markdown @@ -69,3 +69,12 @@ Configuration variables: - **zones** (*Optional*): Envisalink boards have no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the [Binary Sensor](/components/binary_sensor.envisalink/) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor components.* - **partitions** (*Optional*): Again, Envisalink boards do not tell us what is in use and what is not, so each partition must be configured with a partition name. If no partition parameter is specified, then no alarm_panel or sensor components are loaded. +Supported services: + +The following services are supported by Envisalink and can be used to script or automate the alarm. + +- **alarm_disarm**: Disarms the alarm with the user code provided, or the code specified in the configuration. +- **alarm_arm_home**: Arms the alarm in home mode. +- **alarm_arm_away**: Arms the alarm in standard away mode. +- **alarm_trigger**: Trigger an alarm on the Envisalink connected alarm system. For example, a newer zwave/zigbee sensor can now be integrated into a legacy alarm system using a Home Assistant automation. +- **alarm_keypress**: Sends a string of up to 6 characters to the alarm. *DSC alarms only*