Site updated at 2017-10-05 09:01:16 UTC
This commit is contained in:
Travis CI
parent
2e11128e04
commit
48d89ec42a
49 changed files with 104 additions and 104 deletions
|
|
@ -75,7 +75,7 @@
|
|||
</header>
|
||||
<hr class="divider">
|
||||
<p>The <code class="highlighter-rouge">flic</code> platform allows you to connect with multiple <a href="https://flic.io">flic</a> smart buttons.</p>
|
||||
<p>The platform does not directly interact with the buttons, but communicates with the flic service that manages the buttons. The service can run on the same instance as home assistant or any other reachable machine. For setup instructions visit the GitHub repository of the service for <a href="https://github.com/50ButtonsEach/fliclib-linux-hci">Linux</a>, <a href="https://github.com/50ButtonsEach/flic-service-osx">OS X</a> or <a href="https://github.com/50ButtonsEach/fliclib-windows">Windows</a>.</p>
|
||||
<p>The platform does not directly interact with the buttons, but communicates with the flic service that manages the buttons. The service can run on the same instance as Home Assistant or any other reachable machine. For setup instructions visit the GitHub repository of the service for <a href="https://github.com/50ButtonsEach/fliclib-linux-hci">Linux</a>, <a href="https://github.com/50ButtonsEach/flic-service-osx">OS X</a> or <a href="https://github.com/50ButtonsEach/fliclib-windows">Windows</a>.</p>
|
||||
<p>To use your flic buttons in your installation, add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
|
||||
<span class="s">binary_sensor</span><span class="pi">:</span>
|
||||
|
|
|
|||
|
|
@ -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>
|
||||
|
|
|
|||
|
|
@ -113,7 +113,7 @@ Jun 20 19:41:18 androlapin hass[29588]: OSError: [Errno 8] Exec format error
|
|||
1. Go to your <code class="highlighter-rouge">.homeassistant</code> folder
|
||||
2. Then go to <code class="highlighter-rouge">deps/bluepy</code> subfolder.
|
||||
3. Then run <code class="highlighter-rouge">make all</code>
|
||||
4. Restart home assistant
|
||||
4. Restart Home Assistant
|
||||
</p>
|
||||
</article>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -75,9 +75,9 @@
|
|||
</header>
|
||||
<hr class="divider">
|
||||
<p>Philips Hue support is integrated into Home Assistant as a light platform. The preferred way to setup the Philips Hue platform is by enabling the <a href="/components/discovery/">discovery component</a>.</p>
|
||||
<p>Once discovered, if you have a custom default view, locate <code class="highlighter-rouge">configurator.philips_hue</code> in the entities list ( < > ) and add it to a group in <code class="highlighter-rouge">configuration.yaml</code>. Restart Home Assistant so that the configurator is visible in the Home Assistant dashboard. Once Home Assistant is restarted, locate and click on <code class="highlighter-rouge">configurator.philips_hue</code> to bring up the initiation dialog. This will prompt you to press the Hue button to register the Hue hub in home assistant. Once complete, the configurator entity isn’t needed anymore and can be removed from any visible group in <code class="highlighter-rouge">configuration.yaml</code>.</p>
|
||||
<p>Once discovered, if you have a custom default view, locate <code class="highlighter-rouge">configurator.philips_hue</code> in the entities list ( < > ) and add it to a group in <code class="highlighter-rouge">configuration.yaml</code>. Restart Home Assistant so that the configurator is visible in the Home Assistant dashboard. Once Home Assistant is restarted, locate and click on <code class="highlighter-rouge">configurator.philips_hue</code> to bring up the initiation dialog. This will prompt you to press the Hue button to register the Hue hub in Home Assistant. Once complete, the configurator entity isn’t needed anymore and can be removed from any visible group in <code class="highlighter-rouge">configuration.yaml</code>.</p>
|
||||
<p>When you configure the Hue bridge from Home Assistant, it writes a token to a file in your Home Assistant <a href="/docs/configuration/">configuration directory</a>. That token authenticates the communication with the Hue bridge. This token uses the IP Address of the Hue Bridge. If the IP address for the Hue Bridge changes, you will need to register the Hue Bridge with Home Assistant again. To avoid this you may set up DHCP registration for your Hue Bridge, so that it always has the same IP address.</p>
|
||||
<p>Restarting Home Assistant once more should result in the Hue lights listed as “light” entities. Add these light entities to configuration.yaml and restart home assistant once more to complete the installation.</p>
|
||||
<p>Restarting Home Assistant once more should result in the Hue lights listed as “light” entities. Add these light entities to configuration.yaml and restart Home Assistant once more to complete the installation.</p>
|
||||
<p>If you want to enable the component without relying on the <a href="/components/discovery/">discovery component</a>, add the following lines to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
|
||||
<span class="s">light</span><span class="pi">:</span>
|
||||
|
|
|
|||
|
|
@ -84,7 +84,7 @@
|
|||
</ul>
|
||||
<p>This component was developed and tested with a Hama <a href="https://www.hama.com/00054824/hama-digitalradio-dir3110-internetradio-dab+-fm-multiroom-app-steuerung">DIR3110</a> and a Medion <a href="https://www.medion.com/de/shop/internet-dab-radios-medion-kuechen-internetradio-medion-p83302-md-87466-50051273a1.html">MD 87466</a>.</p>
|
||||
<h2>Configuration</h2>
|
||||
<p>Your Frontier Silicon based device should be automatically discovered by home assistant. The auto-discovery service assumes that the device uses the default PIN code: <em>1234</em>. If you have changed the PIN code, the auto-discovery will fail as home assistant will not be able to connect to the device. You can set the PIN code of your device (depending on manufacturer) under:</p>
|
||||
<p>Your Frontier Silicon based device should be automatically discovered by Home Assistant. The auto-discovery service assumes that the device uses the default PIN code: <em>1234</em>. If you have changed the PIN code, the auto-discovery will fail as Home Assistant will not be able to connect to the device. You can set the PIN code of your device (depending on manufacturer) under:</p>
|
||||
<p><em>MENU button > Main Menu > System setting > Network > NetRemote PIN setup</em></p>
|
||||
<p>If your device was not automatically discovered or you have changed the PIN you can alternatively add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
|
||||
|
|
@ -128,8 +128,8 @@
|
|||
is based on <a href="https://github.com/tiwilliam/fsapi">tiwillam</a>’s fsapi project. Special thanks to both developers, this component would have not been possible without their work.</p>
|
||||
<h2>Notes and Limitations</h2>
|
||||
<p class="note warning">
|
||||
The Frontier Silicon API does not provide a multi-user environment. There is always a single user (session) controlling a device, which means that once home assistant connects to a device all other sessions will be invalidated. This renders the usage of <a href="http://www.frontier-silicon.com/undok">UNDOK</a> almost impossible, as the home assistant component polls the device state every 30 seconds or issues a command by creating a new session.
|
||||
<em>If you want to prevent home assistant to auto connect to your device, simply change the PIN code of the device to something else than: 1234</em>
|
||||
The Frontier Silicon API does not provide a multi-user environment. There is always a single user (session) controlling a device, which means that once Home Assistant connects to a device all other sessions will be invalidated. This renders the usage of <a href="http://www.frontier-silicon.com/undok">UNDOK</a> almost impossible, as the Home Assistant component polls the device state every 30 seconds or issues a command by creating a new session.
|
||||
<em>If you want to prevent Home Assistant to auto connect to your device, simply change the PIN code of the device to something else than: 1234</em>
|
||||
</p>
|
||||
</article>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -235,7 +235,7 @@ The MQTT gateway requires MySensors version 2.0 and only the MQTT client gateway
|
|||
<h3><a class="title-link" name="heartbeats" href="#heartbeats"></a> Heartbeats</h3>
|
||||
<p>Sending a heartbeat from the MySensors device to Home Assistant activates the SmartSleep functionality in Home Assistant. This means that messages are buffered and only sent to the device upon receiving a heartbeat from the device. State changes are stored so that only the last requested state change is sent to the device. Other types of messages are queued in a FIFO queue. SmartSleep is useful for battery powered actuators that are waiting for commands. See the MySensors library API for information on how to send heartbeats and sleep device.</p>
|
||||
<h3><a class="title-link" name="message-validation" href="#message-validation"></a> Message validation</h3>
|
||||
<p>Messages sent to or from Home Assistant from or to a MySensors device will be validated according to the MySensors <a href="https://www.mysensors.org/download/serial_api_20">serial API</a>. If a message doesn’t pass validation, it will be dropped and not be passed forward either to or from home assistant. Make sure you follow the serial API for your version of MySensors when writing your Arduino sketch.</p>
|
||||
<p>Messages sent to or from Home Assistant from or to a MySensors device will be validated according to the MySensors <a href="https://www.mysensors.org/download/serial_api_20">serial API</a>. If a message doesn’t pass validation, it will be dropped and not be passed forward either to or from Home Assistant. Make sure you follow the serial API for your version of MySensors when writing your Arduino sketch.</p>
|
||||
<p>If you experience dropped messages or that a device is not added to Home Assistant, please turn on debug logging for the <code class="highlighter-rouge">mysensors</code> component and the <code class="highlighter-rouge">mysensors</code> package.</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">logger</span><span class="pi">:</span>
|
||||
<span class="s">default</span><span class="pi">:</span> <span class="s">info</span>
|
||||
|
|
|
|||
|
|
@ -169,7 +169,7 @@
|
|||
<li><strong>inline_keyboard</strong> (<em>Optional</em>): List of rows of commands, comma-separated, to make a custom inline keyboard with buttons with associated callback data.</li>
|
||||
</ul>
|
||||
<p class="note">
|
||||
Since Homeassistant version 0.48 you have to <a href="/docs/configuration/basic/">whitelist the source folder</a> of the file you want to include in the notification.
|
||||
Since Home Assistant version 0.48 you have to <a href="/docs/configuration/basic/">whitelist the source folder</a> of the file you want to include in the notification.
|
||||
<code class="highlighter-rouge">yaml
|
||||
configuration.yaml
|
||||
...
|
||||
|
|
|
|||
|
|
@ -75,8 +75,8 @@
|
|||
</header>
|
||||
<hr class="divider">
|
||||
<p><a href="https://www.pilight.org/">Pilight</a> is a modular and open source solution to communicate with 433 MHz devices and runs on various small form factor computers. A lot of common <a href="https://wiki.pilight.org/doku.php/protocols">protocols</a> are already available.</p>
|
||||
<p>This pilight hub connects to the <a href="https://wiki.pilight.org/doku.php/pdaemon">pilight-daemon</a> via a socket connection to receive and send codes. Thus home assistant does not have to run on the computer in charge of the RF communication.</p>
|
||||
<p>The received and supported RF codes are put on the event bus of home assistant and are therefore directly usable by other components (e.g. automation). Additionally a send service is provided to send RF codes.</p>
|
||||
<p>This pilight hub connects to the <a href="https://wiki.pilight.org/doku.php/pdaemon">pilight-daemon</a> via a socket connection to receive and send codes. Thus Home Assistant does not have to run on the computer in charge of the RF communication.</p>
|
||||
<p>The received and supported RF codes are put on the event bus of Home Assistant and are therefore directly usable by other components (e.g. automation). Additionally a send service is provided to send RF codes.</p>
|
||||
<p>To integrate pilight into Home Assistant, add the following section to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yaml entry</span>
|
||||
<span class="s">pilight</span><span class="pi">:</span>
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@
|
|||
</h1>
|
||||
</header>
|
||||
<hr class="divider">
|
||||
<p>This <code class="highlighter-rouge">pilight</code> sensor platform for 433 MHz devices uses a value in the message payload as the sensor value. Unique identifiers (e.g. <em>uuid</em>) can be set to distinguish between multiple pilight devices. To use a pilight sensor the pilight home assistant hub has to be set up.</p>
|
||||
<p>This <code class="highlighter-rouge">pilight</code> sensor platform for 433 MHz devices uses a value in the message payload as the sensor value. Unique identifiers (e.g. <em>uuid</em>) can be set to distinguish between multiple pilight devices. To use a pilight sensor the pilight Home Assistant hub has to be set up.</p>
|
||||
<p>To use your sensor via pilight, make sure it is <a href="https://wiki.pilight.org/doku.php/protocols">supported</a> and add the following to your <code class="highlighter-rouge">configuration.yaml</code> file:</p>
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># Example configuration.yml entry</span>
|
||||
<span class="s">sensor</span><span class="pi">:</span>
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ The easiest way to find your switches is to add this to your <code class="highli
|
|||
<span class="s">automatic_add</span><span class="pi">:</span> <span class="s">True</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>Launch your homeassistant and go the website.
|
||||
<p>Launch your Home Assistant and go the website.
|
||||
Push your remote and your device should be added:</p>
|
||||
<p class="img">
|
||||
<img src="/images/components/rfxtrx/switch.png" />
|
||||
|
|
@ -116,7 +116,7 @@ Then you should update your configuration to:</p>
|
|||
</div>
|
||||
<ul>
|
||||
<li>Use this code to add a new switch in your configuration.yaml</li>
|
||||
<li>Launch your homeassistant and go the website.</li>
|
||||
<li>Launch your Home Assistant and go the website.</li>
|
||||
<li>Enable learning mode on your switch (i.e. push learn button or plug it in a wall socket)</li>
|
||||
<li>Toggle your new switch in the Home Assistant interface</li>
|
||||
</ul>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue