Site updated at 2017-02-26 00:49:31 UTC
This commit is contained in:
Travis CI
parent
092dbe14ce
commit
87b3c263a3
500 changed files with 9754 additions and 1957 deletions
|
|
@ -114,6 +114,13 @@
|
|||
<span class="s">icon</span><span class="pi">:</span> <span class="s">mdi:kettle</span>
|
||||
<span class="s">switch.rfxtrx_switch</span><span class="pi">:</span>
|
||||
<span class="s">assumed_state</span><span class="pi">:</span> <span class="s">false</span>
|
||||
<span class="s">customize_domain</span><span class="pi">:</span>
|
||||
<span class="s">light</span><span class="pi">:</span>
|
||||
<span class="s">icon</span><span class="pi">:</span> <span class="s">mdi:home</span>
|
||||
<span class="s">customize_glob</span><span class="pi">:</span>
|
||||
<span class="s2">"</span><span class="s">light.kitchen_*"</span><span class="pi">:</span>
|
||||
<span class="s">icon</span><span class="pi">:</span> <span class="s">mid:description</span>
|
||||
|
||||
</code></pre>
|
||||
</div>
|
||||
|
||||
|
|
@ -148,8 +155,8 @@
|
|||
<td>For switches with an assumed state two buttons are shown (turn off, turn on) instead of a switch. By setting <code class="highlighter-rouge">assumed_state</code> to <code class="highlighter-rouge">false</code> you will get the default switch icon.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code class="highlighter-rouge">sensor_class</code></td>
|
||||
<td>Sets the <a href="/components/binary_sensor/">class of the sensor</a>, changing the device state and icon that is displayed on the UI (see below).</td>
|
||||
<td><code class="highlighter-rouge">device_class</code></td>
|
||||
<td>Sets the class of the device, changing the device state and icon that is displayed on the UI (see below).</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
@ -163,6 +170,15 @@
|
|||
<li><a href="/components/cover/">Cover</a></li>
|
||||
</ul>
|
||||
|
||||
<h3><a class="title-link" name="device-class" href="#device-class"></a> Device Class</h3>
|
||||
|
||||
<p>Device class is currently supported by the following platforms:</p>
|
||||
|
||||
<ul>
|
||||
<li><a href="/components/binary_sensor/">Binary Sensor</a></li>
|
||||
<li><a href="/components/cover/">Cover</a></li>
|
||||
</ul>
|
||||
|
||||
<h3><a class="title-link" name="reloading-customize" href="#reloading-customize"></a> Reloading customize</h3>
|
||||
|
||||
<p>Home Assistant offers a service to reload the core configuration while Home Assistant is running called <code class="highlighter-rouge">homeassistant/reload_core_config</code>. This allows you to change your customize section and see it being applied without having to restart Home Assistant. To call this service, go to the <img src="/images/screenshots/developer-tool-services-icon.png" alt="service developer tool icon" class="no-shadow" height="38" /> service developer tools, select the service <code class="highlighter-rouge">homeassistant/reload_core_config</code> and click “Call Service”.</p>
|
||||
|
|
|
|||
|
|
@ -92,7 +92,15 @@
|
|||
<hr class="divider">
|
||||
|
||||
|
||||
<p>The following configuration has been tested on Synology 413j running DSM 6.0-7321 Update 1.</p>
|
||||
<p>There are 2 alternatives, when using Home Assistant on Synology NAS:</p>
|
||||
<ol>
|
||||
<li>using Docker</li>
|
||||
<li>directly running on DSM</li>
|
||||
</ol>
|
||||
|
||||
<p>Option 1 is described on the <a href="/docs/installation/docker/">Docker installation page</a>, whereas Option 2 is described below.</p>
|
||||
|
||||
<p>The following configuration has been tested on Synology 413j running DSM 6.0-7321 Update 1.</p>
|
||||
|
||||
<p>Running these commands will:</p>
|
||||
|
||||
|
|
@ -121,28 +129,29 @@
|
|||
|
||||
<p>Check the path to python3 (assumed to be /volume1/@appstore/py3k/usr/local/bin)</p>
|
||||
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span><span class="nb">cd</span> /volume1/@appstore/py3k/usr/local/bin
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c"># cd /volume1/@appstore/py3k/usr/local/bin</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
|
||||
<p>Install PIP (Python’s package management system)</p>
|
||||
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>./python3 -m ensurepip
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c"># ./python3 -m ensurepip</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
|
||||
<p>Use PIP to install Homeassistant package</p>
|
||||
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>./python3 -m pip install homeassistant
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c"># ./python3 -m pip install homeassistant</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
|
||||
<p>Create homeassistant config directory & switch to it</p>
|
||||
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>mkdir /volume1/homeassistant
|
||||
<span class="gp">$ </span><span class="nb">cd</span> /volume1/homeassistant
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c"># mkdir /volume1/homeassistant</span>
|
||||
<span class="c"># cd /volume1/homeassistant</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
<p>Hint: alternatively you can also create a “Shared Folder” via Synology WebUI (e.g. via “File Station”) - this has the advantage that the folder is visible via “File Station”.</p>
|
||||
|
||||
<p>Create hass-daemon file using the following code (edit the variables in uppercase if necessary)</p>
|
||||
|
||||
|
|
@ -253,21 +262,21 @@ esac
|
|||
|
||||
<p>Create links to python folders to make things easier in the future:</p>
|
||||
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>ln -s /volume1/@appstore/py3k/usr/local/bin python3
|
||||
<span class="gp">$ </span>ln -s /volume1/@appstore/py3k/usr/local/lib/python3.5/site-packages/homeassistant
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c"># ln -s /volume1/@appstore/py3k/usr/local/bin python3</span>
|
||||
<span class="c"># ln -s /volume1/@appstore/py3k/usr/local/lib/python3.5/site-packages/homeassistant</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
|
||||
<p>Set the owner and permissions on your config folder</p>
|
||||
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>chown -R homeassistant:users /volume1/homeassistant
|
||||
<span class="gp">$ </span>chmod -R 664 /volume1/homeassistant
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c"># chown -R homeassistant:users /volume1/homeassistant</span>
|
||||
<span class="c"># chmod -R 664 /volume1/homeassistant</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
|
||||
<p>Make the daemon file executable:</p>
|
||||
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>chmod 777 /volume1/homeassistant/hass-daemon
|
||||
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="c"># chmod 777 /volume1/homeassistant/hass-daemon</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
|
||||
|
|
|
|||
|
|
@ -157,6 +157,20 @@
|
|||
<span class="s">delay</span><span class="pi">:</span> <span class="s1">'</span><span class="s">00:{{</span><span class="nv"> </span><span class="s">states.input_slider.minute_delay.state</span><span class="nv"> </span><span class="s">|</span><span class="nv"> </span><span class="s">int</span><span class="nv"> </span><span class="s">}}:00'</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
<h3><a class="title-link" name="wait" href="#wait"></a> Wait</h3>
|
||||
|
||||
<p>Wait until some things are complete. We support at the moment <code class="highlighter-rouge">wait_template</code> for waiting until a condition is <code class="highlighter-rouge">true</code>, see also on <a href="/getting-started/automation-trigger/#template-trigger">Template-Trigger</a>. It is possible to set a timeout after that will the script abort his execution. Timeout have same syntax as <code class="highlighter-rouge">delay</code>.</p>
|
||||
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># wait until media player have stop the playing</span>
|
||||
<span class="s">wait_template</span><span class="pi">:</span> <span class="s2">"</span><span class="s">{{</span><span class="nv"> </span><span class="s">states.media_player.floor.states</span><span class="nv"> </span><span class="s">==</span><span class="nv"> </span><span class="s">'stop'</span><span class="nv"> </span><span class="s">}}"</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
|
||||
<div class="language-yaml highlighter-rouge"><pre class="highlight"><code><span class="c1"># wait until a valve is < 10 or abort after 1 minutes.</span>
|
||||
<span class="s">wait_template</span><span class="pi">:</span> <span class="s2">"</span><span class="s">{{</span><span class="nv"> </span><span class="s">states.climate.kitchen.attributes.valve</span><span class="nv"> </span><span class="s"><</span><span class="nv"> </span><span class="s">10</span><span class="nv"> </span><span class="s">}}"</span>
|
||||
<span class="s">timeout</span><span class="pi">:</span> <span class="s">00:01:00</span>
|
||||
</code></pre>
|
||||
</div>
|
||||
|
||||
<h3><a class="title-link" name="fire-an-event" href="#fire-an-event"></a> Fire an Event</h3>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue