Google Travel Time - Use same info for origin/destination sources (#21846)

Co-authored-by: Franck Nijhof <frenck@frenck.nl>
This commit is contained in:
Kevin Stillhammer 2022-03-01 16:57:46 +01:00 committed by GitHub
parent d7edea6be6
commit 845463ae27
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -23,6 +23,10 @@ A quota can be set against the API to avoid exceeding the free credit amount. Se
{% include integrations/config_flow.md %}
Notes:
- Origin and Destination can be the address or the GPS coordinates of the location (GPS coordinates have to be separated by a comma). You can also enter an entity ID that provides this information in its state, an entity ID with latitude and longitude attributes, or zone friendly name (case sensitive).
## Manual Polling
Using automatic polling can lead to calls that exceed your API limit, especially when you are tracking multiple travel times using the same API key. To use more granular polling, disable automated polling in your config entry's System Options. To manually trigger a polling request, call the [`homeassistant.update_entity` service](/integrations/homeassistant/#service-homeassistantupdate_entity) as needed, either manually or via automations.