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

Site updated at 2018-02-08 19:29:57 UTC

Browse source
This commit is contained in:
Travis CI 2018-02-08 19:29:57 +00:00
parent d866642af7
commit 823567f52f
196 changed files with 1612 additions and 2617 deletions
Download patch file Download diff file Expand all files Collapse all files

16
components/device_tracker.unifi/index.html
View file

@ -123,17 +123,13 @@
</div>
<p>See the <a href="/components/device_tracker/">device tracker component page</a> for instructions how to configure the people to be tracked.</p>
<h3><a class="title-link" name="configuring-users" href="#configuring-users"></a> Configuring Users</h3>
<p>The Unifi controller allows you to create multiple users on it besides
the main administrator. It is recommended that you create a limited
user that has <code class="highlighter-rouge">read-only</code> permissions for the Unifi device tracker.</p>
<p>The Unifi controller allows you to create multiple users on it besides the main administrator. It is recommended that you create a limited user that has <code class="highlighter-rouge">read-only</code> permissions for the Unifi device tracker.</p>
<h3><a class="title-link" name="conflicts-with-mqtt" href="#conflicts-with-mqtt"></a> Conflicts with MQTT</h3>
<p>The Unifi controller can either be a dedicated hardware device
(Unifi’s cloud key), or as software any Linux system. If you run the
the Unifi controller on the same operating system as Home Assistant
there may be conflicts in ports if you have the MQTT component as
well.</p>
<p>It is recommended that you run the Unifi controller in a dedicate
virtual machine to avoid that situation.</p>
<p>The Unifi controller can either be a dedicated hardware device (Unifi’s cloud key), or as software any Linux system. If you run the the Unifi controller on the same operating system as Home Assistant there may be conflicts in ports if you have the MQTT component as well.</p>
<p>It is recommended that you run the Unifi controller in a dedicate virtual machine to avoid that situation.</p>
<h3><a class="title-link" name="troubleshooting-and-time-synchronization" href="#troubleshooting-and-time-synchronization"></a> Troubleshooting and Time Synchronization</h3>
<p>Presence detection depends on accurate time configuration between Home Assistant and the Unifi controller.</p>
<p>If Home Assistant and the Unifi controller are running on separate machines or VMs ensure that all clocks are syncronized. Failing to have syncronized clocks will lead to Home Assistant failing to mark a device as home.</p>
<p><a href="https://github.com/home-assistant/home-assistant/issues/10507">Related Issue</a></p>
</article>
</div>

13
components/google_assistant/index.html
View file

@ -169,6 +169,19 @@ To use Google Assistant, your Home Assistant configuration has to be externally
</dd>
</dl>
</div>
<h3><a class="title-link" name="available-domains" href="#available-domains"></a> Available domains</h3>
<p>Currently, the following domains are available to be used with Google Assistant, listed with their default types:</p>
<ul>
<li>group = switch (on/off)</li>
<li>scene = scene (on)</li>
<li>script = scene (on)</li>
<li>switch = switch (on/off)</li>
<li>fan = switch (on/off)</li>
<li>light = light (on/off/brightness/rgb color/color temp)</li>
<li>cover = switch (on/off/set position (brightness) )</li>
<li>media_player = switch (on/off/set volume (brightness) )</li>
<li>climate = thermostat (temperature setting)</li>
</ul>
<p>It’s very important that you use very long strings for <code class="highlighter-rouge">client_id</code> and <code class="highlighter-rouge">access_token</code>. Those are essentially the credentials to your Home Assistant instance. You can generate them with the following command:</p>
<div class="language-bash highlighter-rouge"><pre class="highlight"><code><span class="gp">$ </span>cat /dev/urandom | fold -w 120 | head -n 1 | base64 -w 0 | tr -dc <span class="s1">'0-9A-Za-z'</span> | cut -c -80
</code></pre>