Waze Travel Time

The Waze Travel Time integration集成将 Home Assistant 与您的设备、服务等连接和集成。 [Learn more] provides travel time from the Waze.

配置

要将 Waze Travel Time integration 添加到您的 Home Assistant 实例中，请使用此 My 按钮：

Notes:

• If a unit system is not specified, the integration集成将 Home Assistant 与您的设备、服务等连接和集成。 [Learn more] will use the unit system configured on your Home Assistant instance.
• Origin and Destination can be the address or the GPS coordinates of the location. For coordinates, use the following format: 52.5200, 13.4050. Make sure the coordinates are separated by a comma. They must not include letters. You can also enter an entity id which provides this information in its state, an entity id with latitude and longitude attributes, or zone friendly name (case sensitive).
• The incl_filter/excl_filter allow you to force the integration集成将 Home Assistant 与您的设备、服务等连接和集成。 [Learn more] to use a particular route or avoid a particular route in its time travel calculation. These inputs must be an exact match to the street name including casing, spaces, and special characters. Use the service waze_travel_time.get_travel_times to get the exact street names for each route.
• When using the Avoid Toll Roads?, Avoid Subscription Roads? and Avoid Ferries? options, be aware that Waze will sometimes still route you over toll roads or ferries if a valid vignette/subscription is assumed. Default behavior is that Waze will route you over roads having subscription options. It is therefor best is to set both Avoid Toll Roads? and Avoid Subscription Roads? or Avoid Ferries? if needed and experiment to ensure the desired outcome.

Action waze_travel_time.get_travel_times

This service populates response data with route alternatives and travel times between two locations.

action: waze_travel_time.get_travel_times
data:
  origin: "51.330436, 3.802043"
  destination: "51.445677, 3.749929"
  region: "eu"
response_variable: routes

waze_travel_time.get_travel_times:
  routes:
    - duration: 16.15
      distance: 13.942
      name: B455 - Boelckestraße Wiesbaden
      street_names:
        - Eleonorenstraße
        - Wiesbadener Straße
        - L3482 - Wiesbadener Straße
        - Otto-Suhr-Ring
        - Boelckestraße
        - B455 - Boelckestraße
        - A66 > Frankfurt am Main / Köln
        - A66
        - AS 8 Wallau
        - L3017
        - Diedenberger Straße
        - L3017 - Diedenberger Straße
        - K785 - Diedenberger Straße
        - Hessenstraße
        - Robert-Bosch-Straße
        - Nassaustraße
        - Johannes-Gutenberg-Straße
    - duration: 16.9
      distance: 15.319
      name: L3482 - Wiesbadener Landstraße Wiesbaden
      street_names:
        - Eleonorenstraße
        - Wiesbadener Straße
        - L3482 - Wiesbadener Straße
        - Wiesbadener Landstraße
        - L3482 - Wiesbadener Landstraße
        - Kasteler Straße
        - L3482 - Kasteler Straße
        - Mainzer Straße
        - K650 - Mainzer Straße
        - "> A66 / Wiesbaden-Stadtmitte"
        - A66 > Frankfurt / Hannover
        - A66
        - AS 8 Wallau
        - L3017
        - Diedenberger Straße
        - L3017 - Diedenberger Straße
        - K785 - Diedenberger Straße
        - Hessenstraße
        - Robert-Bosch-Straße
        - Nassaustraße
        - Johannes-Gutenberg-Straße

Defining a custom polling interval

如果您想要定义一个特定的间隔来轮询您的设备以获取数据，可以禁用默认的轮询间隔并创建自己的轮询自动化。

要添加自动化：

1. 转到 设置 > 设备与服务，并选择您的集成。
2. 在集成条目上，选择 。
   • 然后，选择 系统选项 并切换按钮以禁用轮询。
3. 要定义您的自定义轮询间隔，创建一个自动化。
   • 转到 设置 > 自动化与场景 并创建一个新的自动化。
   • 定义您喜欢的任何触发器和条件。
   • 选择 添加动作，然后选择 其他动作。
   • 选择 执行动作，然后从列表中选择 homeassistant.update_entity 动作。
4. 保存您的新自动化以轮询数据。

Example using dynamic destination

Using the flexible option to set a sensor value to the Destination, you can setup a single Waze integration集成将 Home Assistant 与您的设备、服务等连接和集成。 [Learn more] that will calculate travel time to multiple optional locations on demand.

In the following example, the Input Select is converted into an address which is used to modify the destination for the Waze route calculation from the 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:
    name: destination
    options:
      - Home
      - Work
      - Parents

template:
  - sensor:
     - name: "Destination address"
       state: >-
          {%- if is_state("input_select.destination", "Home")  -%}
            725 5th Ave, New York, NY 10022, USA
          {%- elif is_state("input_select.destination", "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 example, we use 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: “US”

Tracking entity to zone friendly name

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

• Name: “Home to Eddie’s 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: “imperial”
• Vehicle Type: “motorcycle”

Avoiding toll, subscription

• Name: “Westerscheldetunnel”
• Origin: “51.330436, 3.802043”
• Destination: “51.445677, 3.749929”
• Region: “EU”
• Avoid Toll Roads: True
• Avoid Subscription Roads: True

Using the live map in an iFrame

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