Site updated at 2017-10-05 09:01:16 UTC

This commit is contained in:
Travis CI 2017-10-05 09:01:17 +00:00
parent 2e11128e04
commit 48d89ec42a
49 changed files with 104 additions and 104 deletions

View file

@ -120,7 +120,7 @@
<li><strong>evl_version</strong> (<em>Optional</em>): 3 for evl3, or 4 for evl4. Default: <code class="highlighter-rouge">3</code></li>
<li><strong>keepalive_interval</strong> (<em>Optional</em>): This is a periodic heartbeat signal (measured in seconds) sent to your Envisalink board to keep it from restarting. This is required for DSC and Honeywell systems. Defaults to <code class="highlighter-rouge">60</code> seconds.</li>
<li><strong>zonedump_interval</strong> (<em>Optional</em>): This is an interval (measured in seconds) where the evl will dump out all zone statuses. This is required for Honeywell systems, which do not properly send zone closure events. DSC boards do not technically need this. Default: <code class="highlighter-rouge">30</code></li>
<li><strong>panic_type</strong> (<em>Optional</em>): Both DSC and Honeywell boards support a “panic” alarm. This is used when the alarm_trigger service is called in home assistant. This determines which type of panic alarm to raise. Default = Police. Valid values are: Police, Fire, Ambulance</li>
<li><strong>panic_type</strong> (<em>Optional</em>): Both DSC and Honeywell boards support a “panic” alarm. This is used when the alarm_trigger service is called in Home Assistant. This determines which type of panic alarm to raise. Default = Police. Valid values are: Police, Fire, Ambulance</li>
<li><strong>zones</strong> (<em>Optional</em>): 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 <a href="/components/binary_sensor.envisalink/">Binary Sensor</a> docs. <em>Note: If no zones are specified, Home Assistant will not load any binary_sensor components.</em></li>
<li><strong>partitions</strong> (<em>Optional</em>): 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.</li>
</ul>