From 845463ae272d42f2ae0a1e2be72f67eb56dc05b2 Mon Sep 17 00:00:00 2001 From: Kevin Stillhammer Date: Tue, 1 Mar 2022 16:57:46 +0100 Subject: [PATCH] Google Travel Time - Use same info for origin/destination sources (#21846) Co-authored-by: Franck Nijhof --- source/_integrations/google_travel_time.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_integrations/google_travel_time.markdown b/source/_integrations/google_travel_time.markdown index 2e567249ef8..b5d62703558 100644 --- a/source/_integrations/google_travel_time.markdown +++ b/source/_integrations/google_travel_time.markdown @@ -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.