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

Site updated at 2016-07-17 08:10:59 UTC

Browse source
This commit is contained in:
Travis CI 2016-07-17 08:10:59 +00:00
parent c88424152a
commit 8567cd024c
21 changed files with 54 additions and 40 deletions
Download patch file Download diff file Expand all files Collapse all files

40
components/sensor.google_travel_time/index.html
View file

@ -124,8 +124,8 @@
</li>
</ul>
<p>###Dynamic Configuration<br />
Tracking can be setup to track entities of type device_tracker, zone, and sensor. If an entity is placed in the origin or destination then every 5 minutes when the component updates it will use the latest location of that entity.</p>
<h3>Dynamic Configuration</h3>
<p>Tracking can be setup to track entities of type device_tracker, zone, and sensor. If an entity is placed in the origin or destination then every 5 minutes when the component updates it will use the latest location of that entity.</p>
<div class="highlighter-coderay"><div class="CodeRay">
<div class="code"><pre><span class="comment"># Example entry for configuration.yaml</span>
@ -147,17 +147,31 @@ Tracking can be setup to track entities of type device_tracker, zone, and sensor
</div>
</div>
<p>####Entity Tracking<br />
- <strong>device_tracker</strong><br />
- If state is a zone then the zone location will be used<br />
- If state is not a zone it will look for the longitude and latitude attributes<br />
- <strong>zone</strong><br />
- Uses the longitude and latitude attributes<br />
- Can also be referenced by just the zone’s friendly name found in the attributes.<br />
- <strong>sensor</strong><br />
- If state is a zone or zone friendly name then will use the zone location<br />
- All other states will be passed directly into the google API<br />
- This includes all valid locations listed in the <em>Configuration Variables</em></p>
<h4>Entity Tracking</h4>
<ul>
<li><strong>device_tracker</strong>
<ul>
<li>If state is a zone then the zone location will be used</li>
<li>If state is not a zone it will look for the longitude and latitude attributes</li>
</ul>
</li>
<li><strong>zone</strong>
<ul>
<li>Uses the longitude and latitude attributes</li>
<li>Can also be referenced by just the zone’s friendly name found in the attributes.</li>
</ul>
</li>
<li><strong>sensor</strong>
<ul>
<li>If state is a zone or zone friendly name then will use the zone location</li>
<li>All other states will be passed directly into the google API
<ul>
<li>This includes all valid locations listed in the <em>Configuration Variables</em></li>
</ul>
</li>
</ul>
</li>
</ul>
</article>