Site updated at 2017-10-29 00:07:46 UTC
This commit is contained in:
parent
065116d821
commit
17b5b61441
31 changed files with 161 additions and 109 deletions
|
@ -86,7 +86,7 @@
|
|||
<ul>
|
||||
<li><strong>max_gps_accuracy</strong> (<em>Optional</em>): Sometimes Owntracks can report GPS location with a very low accuracy (few kilometers). That can trigger false zoning in your Home Assistant installation. With the parameter, you can filter these GPS reports. The number has to be in meter. For example, if you put 200 only GPS report with an accuracy under 200 will be take in account.</li>
|
||||
<li><strong>waypoints</strong> (<em>Optional</em>): Owntracks users can define <a href="http://owntracks.org/booklet/features/waypoints/">waypoints</a> (a.k.a regions) which are similar in spirit to Home Assistant zones. If this configuration variable is <code class="highlighter-rouge">True</code>, the Owntracks users who are in <code class="highlighter-rouge">waypoint_whitelist</code> can export waypoints from the device and Home Assistant will import them as zone definitions. Defaults to <code class="highlighter-rouge">True</code>.</li>
|
||||
<li><strong>waypoint_whitelist</strong> (<em>Optional</em>): A list of user names (as defined for <a href="/components/device_tracker.owntracks/">Owntracks</a>) who can export their waypoints from Owntracks to Home Assistant. Defaults to all users who are connected to Home Assistant via Owntracks.</li>
|
||||
<li><strong>waypoint_whitelist</strong> (<em>Optional</em>): A list of user names (as defined for <a href="/components/device_tracker.owntracks/">Owntracks</a>) who can export their waypoints from Owntracks to Home Assistant. This would be the <code class="highlighter-rouge">username</code> portion of the Base Topic Name, (e.g. owntracks/<strong>username</strong>/iPhone). Defaults to all users who are connected to Home Assistant via Owntracks.</li>
|
||||
<li><strong>secret</strong> (<em>Optional</em>): <a href="http://owntracks.org/booklet/features/encrypt/">Payload encryption key</a>. This is usable when communicating with a third-party untrusted server or a public server (where anybody can subscribe to any topic). By default the payload is assumed to be unencrypted (although the communication between Home Assistant and the server might still be encrypted). This feature requires the <code class="highlighter-rouge">libsodium</code> library to be present.</li>
|
||||
</ul>
|
||||
<p>A full sample configuration for the <code class="highlighter-rouge">owntracks</code> platform is shown below:</p>
|
||||
|
|
|
@ -111,6 +111,7 @@
|
|||
<li>U6300 (port must be set to 8001, and <code class="highlighter-rouge">pip3 install websocket-client</code> must be executed)</li>
|
||||
<li>K6500AF (port must be set to 8001)</li>
|
||||
<li>KS8005 (port must be set to 8001, and <code class="highlighter-rouge">pip3 install websocket-client</code> must be executed)</li>
|
||||
<li>KS7502 (port must be set to 8001, and <code class="highlighter-rouge">pip3 install websocket-client</code> must be executed, turn on doesn’t work, turn off works fine)</li>
|
||||
<li>K5600AK (partially supported, turn on works but state is not updated)</li>
|
||||
</ul>
|
||||
<p>Currently tested but not working models:</p>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue