mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-19 07:17:14 +00:00
Update geofency, GPSLogger and owntracks docs
This commit is contained in:
Paulus Schoutsen
parent
0f89c201dc
commit
db243d7fb6
@ -16,15 +16,13 @@ redirect_from:
|
||||
- /components/device_tracker.geofency/
|
||||
---
|
||||
|
||||
This component sets up integration with [Geofency](http://www.geofency.com/). Geofency is a [paid app](https://itunes.apple.com/app/id615538630) for iOS that lets users to configure a request that will be sent when a geofence or iBeacon region is entered or exited. This can be configured with Home Assistant to update your location.
|
||||
|
||||
Enabling this component will automatically enable the Geofency Device Tracker.
|
||||
This component sets up integration with [Geofency](http://www.geofency.com/). Geofency is a paid app for iOS that lets users to configure a request that will be sent when a geofence or iBeacon region is entered or exited. This can be configured with Home Assistant to update your location.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
To configure Geofency, you must set it up via the integrations panel in the configuration screen. You must then configure the iOS app (via the Webhook feature) to send a POST request to your Home Assistant server at the webhook URL provided by the integration during setup. Use the default POST format. Make sure to enable the 'Update Geo-Position' functionality for mobile beacons.
|
||||
|
||||
Geofency will automatically generate the device tracker name used for geofences, and you will find it in `known_devices.yaml` after the first request. For beacons, the device name will be `beacon_<name from Geofency>`, e.g., `device_tracker.beacon_car`.
|
||||
Geofency will automatically generate the device tracker name used for geofences, and you will find it in the integrations section after the first request. For beacons, the device name will be `beacon_<name from Geofency>`, e.g., `device_tracker.beacon_car`.
|
||||
|
||||
When using mobile beacons (optional) an entry in `configuration.yaml` is still needed as this can't be added via the integrations panel.
|
||||
|
||||
|
||||
@ -16,9 +16,7 @@ redirect_from:
|
||||
- /components/device_tracker.gpslogger/
|
||||
---
|
||||
|
||||
This component sets up integration with [GPSLogger](http://code.mendhak.com/gpslogger/). GPSLogger is an open source app for [Android](https://play.google.com/store/apps/details?id=com.mendhak.gpslogger) that allows users to set up a `POST` request to update GPS coordinates. This can be configured with Home Assistant to update your location.
|
||||
|
||||
Enabling this component will automatically enable the GPSLogger Device Tracker.
|
||||
This component sets up integration with [GPSLogger](https://gpslogger.app/). GPSLogger is an open source app for Android that allows users to update your location in Home Assistant.
|
||||
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ redirect_from:
|
||||
---
|
||||
|
||||
<p class='note'>
|
||||
Locative is no longer under active development. <a href="https://blog.locative.io/bye-everyone-df01871fe949">Read more here</a>
|
||||
Locative is no longer under active development.
|
||||
</p>
|
||||
|
||||
This platform allows you to detect presence using [Locative](https://my.locative.io/). Locative is an open source app for [iOS](https://github.com/LocativeHQ/ios-app) and [Android](https://github.com/LocativeHQ/Locative-Android) that allows users to set up a `GET` or `POST` request when a geofence is entered or exited. This can be configured with Home Assistant to update your location.
|
||||
@ -34,5 +34,3 @@ To configure Locative, you must set it up via the integrations panel in the conf
|
||||
</p>
|
||||
|
||||
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_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.
|
||||
|
||||
@ -24,17 +24,9 @@ By default the integration will listen for incoming messages from OwnTracks via
|
||||
<iframe width="560" height="315" src="https://www.youtube.com/embed/UieAQ8sC6GY" frameborder="0" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
### {% linkable_title Configuring the component %}
|
||||
## {% linkable_title Configuration %}
|
||||
|
||||
1. Open the Home Assistant frontend
|
||||
1. Open Settings -> integrations
|
||||
1. If you see an Owntracks component under 'Configured', delete it.
|
||||
- Click on it.
|
||||
- Click on the trashcan icon in the upper right corner.
|
||||
1. Now, look for Owntracks in 'Setup new integration' and click on CONFIGURE.
|
||||
1. The login credentials and configuration for owntracks will be presented to you.
|
||||
in a popup window. You will need these in the configuration for the app as mentioned below.
|
||||
1. Save these credentials somewhere, as there is no way to get it back at a later point in time if it is lost, besides repeating step 1-5
|
||||
To configure OwnTracks, you must set it up via the integrations panel in the configuration screen. This will give you the webhook URL to use during mobile device configuration (below).
|
||||
|
||||
### {% linkable_title Configuring the app - Android %}
|
||||
|
||||
@ -43,7 +35,7 @@ By default the integration will listen for incoming messages from OwnTracks via
|
||||
In the OwnTracks app, open sidebar and click on preferences, then on connection. Change the following settings:
|
||||
|
||||
- Mode: Private HTTP
|
||||
- Host: `<URL given to you when setting up the integration above>`
|
||||
- Host: `<URL given to you when setting up the integration>`
|
||||
- Identification:
|
||||
- Username: `<Username>`
|
||||
- Password: Can be left blank.
|
||||
@ -167,19 +159,3 @@ By default, any Owntracks user connected to Home Assistant can export their wayp
|
||||
|
||||
1. The configuration variable `waypoints` can be set to `false` which will disable importing waypoints for all users.
|
||||
2. The configuration variable `waypoint_whitelist` can contain a list of users who are allowed to import waypoints.
|
||||
|
||||
## {% linkable_title Using Owntracks with other device trackers %}
|
||||
|
||||
Owntracks can also be used with other device trackers, such as [Nmap](/components/device_tracker.nmap_tracker/) or [Netgear](/components/device_tracker.netgear/). To do this, fill in the `mac` field to the Owntracks entry in `known_devices.yaml` with the MAC address of the device you want to track. This way the state of the device will be determined by the source that reported last. The naming convention for known device list is `<username>_<device-id>` and could be set in app configuration. More details about this config can found in [device tracker](/components/device_tracker/).
|
||||
|
||||
An example showing the inclusion of the `mac` field for multiple component tracking. The `mac` field will need to be added to the `owntracks` device and will enable tracking by all components that track via the `mac` address.
|
||||
|
||||
```yaml
|
||||
USERNAME_DEVICE_ID:
|
||||
name: Friendly Name
|
||||
mac: EA:AA:55:E7:C6:94
|
||||
picture: https://www.home-assistant.io/images/favicon-192x192.png
|
||||
gravatar: test@example.com
|
||||
track: true
|
||||
hide_if_away: false
|
||||
```
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user