From 497dfc4bcb77a4e79c1db8f77cec27d9ff541bb7 Mon Sep 17 00:00:00 2001 From: Eleftherios Chamakiotis Date: Tue, 7 Jan 2020 03:17:29 +0200 Subject: [PATCH] Added documentation for "autobypass" option added to the AlarmDecoder integration (#11470) * Added documentation for "autobypass" option added to the AlarmDecoder integration * Update source/_integrations/alarmdecoder.markdown Co-Authored-By: Franck Nijhof * Removed the autobypass option from the default configuration, as suggested * Minor text change * Jekyll build is failing, so trying to spot the problem * Update source/_integrations/alarmdecoder.markdown Co-Authored-By: Franck Nijhof * Restored original zone numbers in the example configuration, as it was not related to the preview-deploy problem Co-authored-by: Franck Nijhof --- source/_integrations/alarmdecoder.markdown | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/source/_integrations/alarmdecoder.markdown b/source/_integrations/alarmdecoder.markdown index 7bf65735817..4ec7c71d9f6 100644 --- a/source/_integrations/alarmdecoder.markdown +++ b/source/_integrations/alarmdecoder.markdown @@ -80,6 +80,11 @@ panel_display: required: false default: false type: boolean +autobypass: + description: "If this is set to `true`, then when arming (home or away), it will automatically bypass all open zones (sending '6#')." + required: false + default: false + type: boolean zones: description: "AlarmDecoder has 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](/integrations/alarmdecoder) docs. *Note: If no zones are specified, Home Assistant will not load any binary_sensor integrations.*" required: false