From dc54895a696cfe89ce154293fcaf1ed6144ec40d Mon Sep 17 00:00:00 2001 From: jnimmo Date: Sat, 15 Oct 2016 23:01:10 +1300 Subject: [PATCH 1/4] Add supported services To document the new alarm_keypress and alarm_output_control services --- source/_components/envisalink.markdown | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/source/_components/envisalink.markdown b/source/_components/envisalink.markdown index 529ee1e9fdbc..00c942b180fa 100644 --- a/source/_components/envisalink.markdown +++ b/source/_components/envisalink.markdown @@ -69,3 +69,11 @@ 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. *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: + +- **alarm_disarm** +- **alarm_arm_home** +- **alarm_arm_away** +- **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. +- **alarm_output_control**: Activates the specified programmable output on the alarm to control a connected device. From a6ed3fc76b852da75e548e5c7a3cdb72af9c275d Mon Sep 17 00:00:00 2001 From: jnimmo Date: Thu, 20 Oct 2016 22:05:48 +1300 Subject: [PATCH 2/4] Update envisalink.markdown --- source/_components/envisalink.markdown | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/source/_components/envisalink.markdown b/source/_components/envisalink.markdown index 00c942b180fa..6ca2602ff3fc 100644 --- a/source/_components/envisalink.markdown +++ b/source/_components/envisalink.markdown @@ -70,10 +70,11 @@ Configuration variables: - **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** -- **alarm_arm_home** -- **alarm_arm_away** +- **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. -- **alarm_output_control**: Activates the specified programmable output on the alarm to control a connected device. +- **alarm_keypress**: Sends a string of up to 6 characters to the alarm. *DSC alarms only* +- **alarm_output_control**: Activates the specified programmable output on the alarm to control a connected device. *DSC alarms only* From 8744d42d18ab24dcbc38547d0c6659727f5a6df8 Mon Sep 17 00:00:00 2001 From: jnimmo Date: Thu, 20 Oct 2016 22:06:30 +1300 Subject: [PATCH 3/4] Update envisalink.markdown --- source/_components/envisalink.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/_components/envisalink.markdown b/source/_components/envisalink.markdown index 6ca2602ff3fc..9fd8569d4cc8 100644 --- a/source/_components/envisalink.markdown +++ b/source/_components/envisalink.markdown @@ -70,6 +70,7 @@ Configuration variables: - **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. From 07bfa70d46d31d3c83df76bc813aa6437819a737 Mon Sep 17 00:00:00 2001 From: jnimmo Date: Sat, 19 Nov 2016 08:59:28 +1300 Subject: [PATCH 4/4] Removed output control service not currently implemented --- source/_components/envisalink.markdown | 1 - 1 file changed, 1 deletion(-) diff --git a/source/_components/envisalink.markdown b/source/_components/envisalink.markdown index 9fd8569d4cc8..ef4f529db99d 100644 --- a/source/_components/envisalink.markdown +++ b/source/_components/envisalink.markdown @@ -78,4 +78,3 @@ The following services are supported by Envisalink and can be used to script or - **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* -- **alarm_output_control**: Activates the specified programmable output on the alarm to control a connected device. *DSC alarms only*