jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-23 09:17:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update link to nmap_tracker (fixes #1570)

Browse Source
This commit is contained in:
Fabian Affolter 2016-12-10 23:53:21 +01:00
parent 59be089733
commit 102adee9e4
No known key found for this signature in database
GPG Key ID: DDF3D6F44AAB1336
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
source/_components/device_tracker.locative.markdown
View File

@ -34,4 +34,4 @@ To configure Locative, you must set up the app to send a `GET` request to your H
When you enter a geofence, your location name in Home Assistant will be set to the name of the geofence in Locative. When you exit a geofence, your location name in Home Assistant will be set to "not home".
To use Locative in combination with another device tracker, such as [nmap](/components/device_tracker.nmap_scanner/) or [Netgear](/components/device_tracker.netgear/), fill in the `mac` field to the Locative entry in `known_devices.yaml` with the MAC address of the device you want to track. The state of the device will be determined by the source that reported last.
To use Locative in combination with another device tracker, such as [nmap](/components/device_tracker.nmap_tracker/) or [Netgear](/components/device_tracker.netgear/), fill in the `mac` field to the Locative entry in `known_devices.yaml` with the MAC address of the device you want to track. The state of the device will be determined by the source that reported last.

2
source/_components/device_tracker.owntracks.markdown
View File

@ -30,7 +30,7 @@ Configuration variables:
- **max_gps_accuracy** (*Optional*): 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.
- **waypoints** (*Optional*): Owntracks users can define [waypoints](http://owntracks.org/booklet/features/waypoints/) (a.k.a regions) which are similar in spirit to Home Assistant zones. If this configuration variable is `True`, the Owntracks users who are in `waypoint_whitelist` can export waypoints from the device and Home Assistant will import them as zone definitions. Defaults to `True`.
- **waypoint_whitelist** (*Optional*): A list of user names (as defined for [Owntracks](https://home-assistant.io/components/device_tracker.owntracks/)) who can export their waypoints from Owntracks to Home Assistant. Defaults to all users who are connected to Home Assistant via Owntracks.
- **waypoint_whitelist** (*Optional*): A list of user names (as defined for [Owntracks](/components/device_tracker.owntracks/)) who can export their waypoints from Owntracks to Home Assistant. Defaults to all users who are connected to Home Assistant via Owntracks.
A full sample configuration for the `owntracks` platform is shown below:

2
source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown
View File

@ -147,7 +147,7 @@ The validation of the configuration is still on-going. Approximatly 80 % is done
[Temper]: /components/sensor.temper/
[mqtt-fan]: /components/fan.mqtt/
[Xbox]: /components/sensor.xbox_live/
[Nmap]: /components/device_tracker.nmap_scanner/
[Nmap]: /components/device_tracker.nmap_tracker/
[automatic]: /components/device_tracker.automatic/
[Owntracks]: /components/device_tracker.owntracks/
[OpenweatherMap]: /components/sensor.openweathermap/