google_travel_time sensor provides travel time from the Google Distance Matrix API.
You need to register for an API key by following the instructions here. You only need to turn on the Distance Matrix API.
Google now requires billing to be enabled (and a valid credit card loaded) to access Google Maps APIs. The Distance Matrix API is billed at US$10 per 1000 requests, however, a US$200 per month credit is applied (20,000 requests). By default, the sensor will update the travel time every 5 minutes, making approximately 288 calls per day. Note that at this rate, more than 2 sensors will likely exceed the free credit amount. If you need to run more than 2 sensors, consider changing the scan interval to something longer than 5 minutes to stay within the free credit limit or update the sensors on-demand using an automation (see example below).
A quota can be set against the API to avoid exceeding the free credit amount. Set the ‘Elements per day’ to a limit of 645 or less. Details on how to configure a quota can be found here
To enable the sensor, add the following lines to your
# Example entry for configuration.yaml sensor: - platform: google_travel_time api_key: XXXX_XXXXX_XXXXX origin: Trondheim, Norway destination: Paris, France
Your application’s API key (get one by following the instructions above). This key identifies your application for purposes of quota management.
The starting point for calculating travel distance and time. You can supply one or more locations separated by the pipe character, in the form of an address, latitude/longitude coordinates, or a Google place ID. When specifying the location using a Google place ID, the ID must be prefixed with
One or more locations to use as the finishing point for calculating travel distance and time. The options for the destinations parameter are the same as for the origins parameter, described above.
A name to display on the sensor. The default is “Google Travel Time - [Travel Mode]” where [Travel Mode] is the mode set in options for the sensor (see option “mode” below).
You can choose between:
transit. This method is now deprecated, use
A dictionary containing parameters to add to all requests to the Distance Matrix API. A full listing of available options can be found here.
The travel mode used to calculate the directions/time. Can be
You can choose from a lot of languages:
(time | string)(Exclusive)
now, a Unix timestamp, or a 24 hour time string like
08:00:00. If you provide a time string, it will be combined with the current date to get travel time for that moment.
(time | string)(Exclusive)
See notes above for
now, only a Unix timestamp or time string. You can not provide both
arrival_time. If you do provide both,
arrival_timewill be removed from the request.
Indicate what Google should avoid when calculating the travel time, you can choose from:
If you opted for
travel_mode, you can use this variable to specify which public transport you want to use:
for the travel time calculation for public transport you can also specify the preference for:
Set the unit for the sensor in metric or imperial, otherwise the default unit the same as the unit set in
Tracking can be setup to track entities of type
person. If an entity is placed in the origin or destination then every 5 minutes when the platform updates it will use the latest location of that entity.
# Example entry for configuration.yaml sensor: # Tracking entity to entity - platform: google_travel_time name: Phone To Home api_key: XXXX_XXXXX_XXXXX origin: device_tracker.mobile_phone destination: zone.home # Tracking entity to zone friendly name - platform: google_travel_time name: Home To Eddie's House api_key: XXXX_XXXXX_XXXXX origin: zone.home destination: Eddies House # Friendly name of a zone # Tracking entity in imperial unit - platform: google_travel_time api_key: XXXX_XXXXX_XXXXX destination: zone.home options: units: imperial # 'metric' for Metric, 'imperial' for Imperial
- If state is a zone then the zone location will be used
- If state is not a zone it will look for the longitude and latitude attributes
- Uses the longitude and latitude attributes
- Can also be referenced by just the zone’s friendly name found in the attributes.
- If state is a zone or zone friendly name then will use the zone location
- All other states will be passed directly into the Google API
- This includes all valid locations listed in the Configuration Variables
You can also use the
homeassistant.update_entity service to update the sensor on-demand. For example, if you want to update
sensor.morning_commute every 2 minutes on weekday mornings, you can use the following automation:
- id: update_morning_commute_sensor alias: "Commute - Update morning commute sensor" initial_state: 'on' trigger: - platform: time_pattern minutes: '/2' condition: - condition: time after: '08:00:00' before: '11:00:00' - condition: time weekday: - mon - tue - wed - thu - fri action: - service: homeassistant.update_entity entity_id: sensor.morning_commute