How To Set Coordinates In Waze

Waze Travel Time

The waze_travel_time sensor provides travel time from the Waze.

Configuration

Calculation Waze Travel Time to your Habitation Banana case can exist done via the user interface, by using this My push:

Manual configuration steps

Notes:

If a unit system is not specified, the integration volition apply the unit arrangement configured on your Habitation Assistant instance.
Origin and Destination can be the address or the GPS coordinates of the location (GPS coordinates have to be separated by a comma). You tin can also enter an entity id which provides this data in its state, an entity id with latitude and longitude attributes, or zone friendly name (case sensitive).
The string inputs for Substring * let you to force the integration to use a item route or avoid a particular route in its time travel calculation. These inputs are example insensitive matched against the description of the road.
When using the Avoid Toll Roads?, Avoid Subscription Roads? and Avoid Ferries? options exist aware that Waze will sometimes still route you over cost roads or ferries if a valid vignette/subscription is causeless. Default behavior is that Waze volition road y'all over roads having subscription options, then all-time is to ready both Avoid Toll Roads? and Avoid Subscription Roads? or Avoid Ferries? if needed and experiment to ensure the desired outcome.

Manual Polling

Some users will want to have more command over polling frequencies. To use more granular polling, disable automatic polling in your config entry'due south System Options. To manually trigger a polling request, call the homeassistant.update_entity service as needed, either manually or via automations.

Case using dynamic destination

Using the flexible option to set a sensor value to the Destination, you tin setup a unmarried Waze integration that will calculate travel time to multiple optional locations on demand.

In the post-obit case, the Input Select is converted into an accost which is used to modify the destination for Waze route calculation from device_tracker.myphone location (It takes a few minutes for the value to update due to the interval of Waze data fetching).

                              input_select                :                destination                :                proper noun                :                destination                options                :                -                Dwelling house                -                Work                -                Parents                template                :                -                sensor                :                -                name                :                "                Destination                                                address"                land                :                >-                {%- if is_state("input_select.destination", "Home")  -%}                725 5th Ave, New York, NY 10022, U.s.a.                {%- elif is_state("input_select.destination", "Piece of work")  -%}                767 5th Ave, New York, NY 10153, Usa                {%- elif is_state("input_select.destination", "Parents")  -%}                178 Broadway, Brooklyn, NY 11211, USA                {%- else -%}                Unknown                {%- endif %}

Various configurations that are supported

Tracking entity to entity

In this case we apply a device_tracker entity ID as the origin and the sensor created above as the destination.

Name: "Me to some destination"
Origin: device_tracker.myphone
Destination: sensor.dest_address
Region: "U.s.a."

Tracking entity to zone friendly name

In this example we are using the entity ID of a zone as the origin and the friendly proper name of a zone equally the destination.

Name: "Abode to Eddie'southward house"
Origin: zone.home
Destination: "Eddies House"
Region: "US"

Tracking entity in Imperial Units

Name: "Somewhere in New York"
Origin: person.paulus
Destination: "725 5th Ave, New York, NY 10022, USA"
Region: "US"
Units: "royal"
Vehicle Type: "motorbike"

Avoiding toll, subscription

Name: "Westerscheldetunnel"
Origin: "51.330436, three.802043"
Destination: "51.445677, 3.749929"
Region: "EU"
Avert Toll Roads: True
Avoid Subscription Roads: True

Using the live map in an iFrame

If you plan to use Waze'southward live map in a dashboard iframe then employ https://embed.waze.com/iframe and not the live map URL itself.

Assistance us to improve our documentation

Suggest an edit to this page, or provide/view feedback for this page.