Clarity on how to use LLAT (#7002)

LLAT isn't obviously a long lived access token, and the intro leaves the reader hanging as if things are handled automatically. Adding some clarity.
This commit is contained in:
DubhAd 2018-10-22 22:30:21 +01:00 committed by Fabian Affolter
parent 920549e7e8
commit 08ca5a6574

View File

@ -15,7 +15,7 @@ The `gpslogger` device tracker platform allows you to detect presence using [GPS
## {% linkable_title Auth change release 0.77 and above %}
Since release 0.77, we now have long-lived access tokens. These are setup under your profile.
Since release 0.77, we now have long-lived access tokens. These are setup under your profile and configured in the GPSLogger application on your smartphone as explained below.
```yaml
# Example configuration.yaml entry
@ -80,7 +80,7 @@ Add the above URL after you modified it with your settings into the **URL** fiel
- Use the domain that Home Assistant is available on the internet (or the public IP address if you have a static IP address). This can be a local IP address if you are using an always on VPN from your mobile device to your home network.
- Only remove `PORT` if your Home Assistant instance is using port 443. Otherwise set it to the port you're using.
- For Home Assistant only the above URL, as written, will work - do not add, remove, or change the order of any of the parameters.
- **0.77+** If you are using Long-Lived access tokens, then add `Authentication: Bearer LLAT` to the HTTP Headers setting
- **0.77+** If you are using Long-Lived access tokens, then add `Authentication: Bearer LLAT` to the HTTP Headers setting (replace `LLAT` with your Long Lived Access Token).
- **<0.77** Make sure to include your [API password](/components/http/) if you have configured a password. Add `&api_password=YOUR_PASSWORD` to the end of the URL.
- You can change the name of your device name by replacing `&device=%SER` with `&device=DEVICE_NAME`.