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

Site updated at 2017-08-16 19:55:12 UTC

Browse source
This commit is contained in:
Travis CI 2017-08-16 19:55:13 +00:00
parent de24f14701
commit 9b2600b022
32 changed files with 51 additions and 50 deletions
Download patch file Download diff file Expand all files Collapse all files

4
hassio/external_storage/index.html
View file

@ -76,11 +76,11 @@
</header>
<hr class="divider">
<h3><a class="title-link" name="resinos--generic" href="#resinos--generic"></a> ResinOS / Generic</h3>
<p>Map the USB drive into add-on with <code class="highlighter-rouge">devices</code> options. If you need it on multiple add-ons you can use the <code class="highlighter-rouge">/share</code> folder which is accessible from multiple add-ons.
<p>Map the USB drive into add-on with <code class="highlighter-rouge">devices</code> options. If you need it on multiple add-ons, you can use the <code class="highlighter-rouge">/share</code> folder which is accessible from various add-ons.
It is also possible to create an add-on that only mounts stuff to <code class="highlighter-rouge">share</code>.</p>
<p>You can format the USB device with multiple volumes and map it to a specific add-on.</p>
<h3><a class="title-link" name="generic" href="#generic"></a> Generic</h3>
<p>The <code class="highlighter-rouge">share</code> is default on <code class="highlighter-rouge">/usr/share/hassio/share</code> so you can mount your volumes into this folder.</p>
<p>The <code class="highlighter-rouge">share</code> defaults to <code class="highlighter-rouge">/usr/share/hassio/share</code> so you can mount your volumes into this folder.</p>
</article>
</div>
<aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole">

2
hassio/index.html
View file

@ -75,7 +75,7 @@
</h1>
</header>
<hr class="divider">
<p>Hass.io turns your Raspberry Pi (or other device) into the ultimate home automation hub powered by Home Assistant. With Hass.io you can focus on integrating your devices and writing automations.</p>
<p>Hass.io turns your Raspberry Pi (or another device) into the ultimate home automation hub powered by Home Assistant. With Hass.io you can focus on integrating your devices and writing automations.</p>
<p><a href="/hassio/installation/">Go to the installation instructions »</a></p>
<p>The advantages of using Hass.io:</p>
<ul>

4
hassio/installing_third_party_addons/index.html
View file

@ -75,7 +75,7 @@
</h1>
</header>
<hr class="divider">
<p>Hass.io allows anyone to create add-on repositories to easily share their add-ons for Hass.io. To try this locally, you can use our example add-on repository at</p>
<p>Hass.io allows anyone to create add-on repositories to share their add-ons for Hass.io easily. To try this locally, you can use our example add-on repository at</p>
<div class="language-text highlighter-rouge"><pre class="highlight"><code>https://github.com/home-assistant/hassio-addons-example
</code></pre>
</div>
@ -91,7 +91,7 @@ From the Hass.io main panel open the add-on store.
Add the URLs of repositories (one per line) and then press “Save”. A new card for the repository will appear.
</p>
<h3><a class="title-link" name="help-repository-is-not-showing-up" href="#help-repository-is-not-showing-up"></a> Help: Repository is not showing up</h3>
<p>If you have added a repository but it’s not showing up, it means that the repository contains invalid configuration. Go to the Hass.io panel -&gt; Three dot menu -&gt; Advanced Settings -&gt; Supervisor card -&gt; View logs and scroll to the bottom. It should tell you what went wrong. Report this information to the repository author.</p>
<p>If you have added a repository, but it’s not showing up, it means that the repository contains invalid configuration. Go to the Hass.io panel -&gt; Three dot menu -&gt; Advanced Settings -&gt; Supervisor card -&gt; View logs and scroll to the bottom. It should tell you what went wrong. Report this information to the repository author.</p>
</article>
</div>
<aside id="sidebar" class="grid__item one-third lap-one-whole palm-one-whole">

4
hassio/run_local/index.html
View file

@ -75,9 +75,9 @@
</h1>
</header>
<hr class="divider">
<p>Hass.io is a managed environment. This means that you can install applications that can be embedded into Home Assistant using the <code class="highlighter-rouge">command_line</code> sensor/switch.</p>
<p>Hass.io is a managed environment, which means that you can install applications that can be embedded into Home Assistant using the <code class="highlighter-rouge">command_line</code> sensor/switch.</p>
<p>There are two options if you need to run a script to read data from a sensor or send commands to other devices on Hass.io.</p>
<p>First option is to write a custom component for Home Assistant. Using Python you can communicate with your device. For custom component, take a look at the <a href="/developers/component_loading/">developer documentation</a>.</p>
<p>The first option is to write a custom component for Home Assistant. Using Python, you can communicate with your device. For more information about developing a custom component, take a look at the <a href="/developers/component_loading/">developer documentation</a>.</p>
<p>The second option is to make a local add-on for Hass.io that sends the data to Home Assistant via MQTT. Before we dive into this, read up on <a href="/developers/hassio/addon_tutorial/">Hass.io add-on development</a> first.</p>
<p>For security and speed, Hass.io does not provide a way for containers to communicate directly. So the first step is to set up a communication channel. We’re going to use MQTT for this using the <a href="/addons/mosquitto/">MQTT broker add-on</a>.</p>
<h3><a class="title-link" name="sensors" href="#sensors"></a> Sensors</h3>

5
hassio/zwave/index.html
View file

@ -84,11 +84,12 @@
<div class="highlighter-rouge"><pre class="highlight"><code>dtoverlay=pi3-miniuart-bt
</code></pre>
</div>
<p>For very special device, the <code class="highlighter-rouge">/dev/ttyAMA0</code> will not detect by udev and not mapped with docker. So you need explicit set this device for mapping to Home-Assistant. Execute this command on ssh add-on:</p>
<p>For some exceptional devices, the <code class="highlighter-rouge">/dev/ttyAMA0</code> will not be detected by udev and are therefor not mapped with docker.
So you need explicit set this device for mapping to Home-Assistant. Execute this command on ssh add-on:</p>
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>curl -d <span class="s1">'{"devices": ["ttyAMA0"]}'</span> http://172.17.0.2/homeassistant/options
</code></pre>
</div>
<p>After that you need change <code class="highlighter-rouge">usb_path</code> to <code class="highlighter-rouge">/dev/ttyAMA0</code>.</p>
<p>After that, you need change <code class="highlighter-rouge">usb_path</code> to <code class="highlighter-rouge">/dev/ttyAMA0</code>.</p>
<h3>HUSBZB-1:</h3>
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="s">zwave</span><span class="pi">:</span>
<span class="s">usb_path</span><span class="pi">:</span> <span class="s">/dev/ttyUSB0</span>