jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Site updated at 2017-10-21 23:33:52 UTC

Browse source
This commit is contained in:
Travis CI 2017-10-21 23:33:53 +00:00
parent b95006b9eb
commit a6fbc15960
1416 changed files with 21669 additions and 4045 deletions
Download patch file Download diff file Expand all files Collapse all files

19
components/knx/index.html
View file

@ -23,7 +23,7 @@
<meta name="twitter:title" content="KNX">
<meta name="twitter:description" content="Instructions on how to integrate KNX components with Home Assistant.">
<meta name="twitter:image" content="https://home-assistant.io/images/default-social.png">
<link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet">
<link href="/stylesheets/screen.css" media="screen, projection, print" rel="stylesheet">
<link href="/atom.xml" rel="alternate" title="Home Assistant" type="application/atom+xml">
<link rel='shortcut icon' href='/images/favicon.ico' />
<link rel='icon' type='image/png' href='/images/favicon-192x192.png' sizes='192x192' />
@ -129,8 +129,11 @@
</code></pre>
</div>
<ul>
<li><strong>fire_event</strong> (Optional) if set to True, platform will write all received KNX messages to event bus</li>
<li><strong>fire_event_filter</strong> If <code class="highlighter-rouge">fire_event</code> is set <code class="highlighter-rouge">fire_event_filter</code> has to be specified. <code class="highlighter-rouge">fire_event_filter</code> defines a list of patterns for filtering KNX addresses. Only telegrams which match this pattern are sent to the HASS event bus.</li>
<li><strong>fire_event</strong> (<em>Optional</em>): If set to True, platform will write all received KNX messages to event bus</li>
<li>
<p><strong>fire_event_filter</strong> (<em>Optional</em>): If <code class="highlighter-rouge">fire_event</code> is set <code class="highlighter-rouge">fire_event_filter</code> has to be specified. <code class="highlighter-rouge">fire_event_filter</code> defines a list of patterns for filtering KNX addresses. Only telegrams which match this pattern are sent to the HASS event bus.</p>
</li>
<li><strong>state_updater</strong> (<em>Optional</em>): The component will collect the current state of each configured device from the KNX bus to display it correctly within Home-Assistant. Set this option to False to prevent this behaviour.</li>
</ul>
<h2>Service</h2>
<p>In order to directly interact with the KNX bus, you can now use the following service:</p>
@ -140,8 +143,8 @@ Service Data: {"address": "1/0/15", "payload": 0}
</code></pre>
</div>
<ul>
<li><strong>address</strong> : KNX group address</li>
<li><strong>payload</strong> : payload, either an integer or an array of integers</li>
<li><strong>address</strong>: KNX group address</li>
<li><strong>payload</strong>: Payload, either an integer or an array of integers</li>
</ul>
<h2>Known issues:</h2>
<p>Due to lame multicast support the routing abstraction and the gateway scanner
@ -343,6 +346,9 @@ only work with python &gt;=3.5.</p>
<li>
<a href='/components/satel_integra/'>Satel Integra Alarm</a>
</li>
<li>
<a href='/components/skybell/'>Skybell</a>
</li>
<li>
<a href='/components/sleepiq/'>SleepIQ</a>
</li>
@ -364,6 +370,9 @@ only work with python &gt;=3.5.</p>
<li>
<a href='/components/thethingsnetwork/'>The Things Network</a>
</li>
<li>
<a href='/components/toon/'>Toon</a>
</li>
<li>
<a href='/components/twilio/'>Twilio</a>
</li>