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

Site updated at 2018-01-28 22:02:31 UTC

Browse source
This commit is contained in:
Travis CI 2018-01-28 22:02:31 +00:00
parent 57a21e9eb0
commit 01b474f87c
268 changed files with 412 additions and 412 deletions
Download patch file Download diff file Expand all files Collapse all files

2
developers/hassio/addon_communication/index.html
View file

@ -76,7 +76,7 @@
<hr class="divider">
<p>There are different ways to communication between add-ons inside Home Assistant.</p>
<h2><a class="title-link" name="network" href="#network"></a> Network</h2>
<p>We use a internal network. That allow to speak with every add-on or from Home Assistant to add-on by name or alias. Only the add-ons which runs on the host network are a bit limited. They can speak with all internal add-ons over their name but all other add-on can’t address the add-on in question with its name. But using an alias work well. Thus the name/alias is used to communicate inside Hass.io. The name have the following format <code class="highlighter-rouge"><span class="p">{</span><span class="err">REPO</span><span class="p">}</span><span class="err">-</span><span class="p">{</span><span class="err">SLUG</span><span class="p">}</span></code>, e.g. <code class="highlighter-rouge">local-xy</code> or <code class="highlighter-rouge">3283fh-myaddon</code>.</p>
<p>We use an internal network. That allow to speak with every add-on or from Home Assistant to add-on by name or alias. Only the add-ons which runs on the host network are a bit limited. They can speak with all internal add-ons over their name but all other add-on can’t address the add-on in question with its name. But using an alias work well. Thus the name/alias is used to communicate inside Hass.io. The name have the following format <code class="highlighter-rouge"><span class="p">{</span><span class="err">REPO</span><span class="p">}</span><span class="err">-</span><span class="p">{</span><span class="err">SLUG</span><span class="p">}</span></code>, e.g. <code class="highlighter-rouge">local-xy</code> or <code class="highlighter-rouge">3283fh-myaddon</code>.</p>
<p>Use <code class="highlighter-rouge">hassio</code> to speak with the internal API.</p>
<h2><a class="title-link" name="home-assistant" href="#home-assistant"></a> Home Assistant</h2>
<p>An add-on can speak to the <a href="https://home-assistant.io/developers/rest_api/">Home Assistant API</a> with our internal proxy. That makes it very easy to communicate with the API without knowing the password, port or any other information of the Home Assistant instance. Use this URL: <code class="highlighter-rouge">http://hassio/homeassistant/api</code> and internal communication is redirected to the right place. The next stept is to add <code class="highlighter-rouge">homeassistant_api: true</code> to <code class="highlighter-rouge">config.json</code> and read the environment variable <code class="highlighter-rouge">HASSIO_TOKEN</code> and use this as Home-Assistant password.</p>