Waze travel time route attribute empty

[Wetzel402]

The problem

When using the Waze travel time integration the route attribute is empty. This is configured through the UI. There appear to be no errors related to this in the logs.

What version of Home Assistant Core has the issue?

2021.11.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Waze travel time

Link to integration documentation on our website

https://www.home-assistant.io/integrations/waze_travel_time

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

attribution: Powered by Waze
duration: 46.45
distance: 39.85456805469236
route: ''
origin: xx,xx #lat,log obfuscated 
destination: xx,xx #lat,log obfuscated
unit_of_measurement: min
friendly_name: Commute time
icon: mdi:car

[probot-home-assistant]

waze_travel_time documentation
waze_travel_time source
_{^{(message by IssueLinks)}}

[bs42]

Confirming that I'm also seeing the same thing on the same version.

[dhavaldesai-HA]

Same issues since last 24 hours.
Location : Europe

[MarkRK]

Not sure if related to any api-changes which could cause this but it started happening at the same time... the traveltimes calculated by the integration are longer than calculated by waze on the app or website.
Integration calculates 60 minutes and the app/website 44 minutes. (different route?)

[mbrentini]

I also confirm this issue, happening since 1 week.

[bartdeweijer]

I can also confirm that the route attribute is empty for me too. Without this attribute filled the substring becomes useless as well. Also experiencing the same problem as @MarkRK, all my routes are the longest of the bunch (3 routes I assume, same as on the web version of Waze).

[kindersec]

Confirmed as well in Europe Zone, Route attribute is empty for more than a week

[Kuba15]

Also confirm that he route is empty, using the substring filter does not work (core-2021.11.5).
Plus since 7th of December, 9:00 CEST, the travel duration became longer than it was before and does not match the time on the Waze application.

[backslashV]

Also confirm that he route is empty, using the substring filter does not work (core-2021.11.5). Plus since 7th of December, 9:00 CEST, the travel duration became longer than it was before and does not match the time on the Waze application.

Exactly. Facing the same issue.

[fi-sch]

Also confirm that he route is empty, using the substring filter does not work (core-2021.11.5).
Plus since 7th of December, 9:00 CEST, the travel duration became longer than it was before and does not match the time on the Waze application.

Same here. Also, I did notice that the longer travel distance is, the higher "overestimation" becomes.
Maybe, as a temporary hack, it would be enough to figure out the % of overestimation and correct each WTT sensor using a template sensor.

[themajesticking]

I'm also experiencing the time calculation issue. After putting in the same destination on the Waze website I've concluded that it appears to be using the 2nd or 3rd route option which are often much longer than the first option.

[dhavaldesai-HA]

I've upgraded to 2021.12.2. Problem still persist. On Waze integration the travel time still comes up as "unknown" value.

Zone: Europe

[aegjoyce]

I'm recently having the same issue. Prior to 2021.11 (I think) it was working fine - accurate timings and route provided for my 50 minute commute. Now timings are all wrong and no route appears, even when switching from zones to coordinates as inputs.

[Midnitte]

I've been experiencing this issue since December 7th but since I don't upgrade immediately or consistently I'm not sure which version I had installed.
It's configured to realtime traffic, using a car, to avoid tolls, and there's no substring set.

System Health

version	core-2021.12.5
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.9.7
os_name	Linux
os_version	5.10.83
arch	aarch64
timezone	America/New_York

Home Assistant Community Store

GitHub API	ok
Github API Calls Remaining	5000
Installed Version	1.18.0
Stage	running
Available Repositories	921
Installed Repositories	8

Home Assistant Cloud

logged_in	true
subscription_expiration	January 18, 2022, 7:00 PM
relayer_connected	true
remote_enabled	true
remote_connected	true
alexa_enabled	true
google_enabled	true
remote_server	us-east-1-0.ui.nabu.casa
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 7.0
update_channel	stable
supervisor_version	supervisor-2021.12.2
docker_version	20.10.9
disk_total	113.9 GB
disk_used	5.6 GB
healthy	true
supported	true
board	odroid-n2
supervisor_api	ok
version_api	failed to load: timeout
installed_addons	Z-Wave JS (0.1.50), File editor (5.3.3), Git pull (7.13.1), Terminal & SSH (9.2.2), Node-RED (10.2.2), Glances (0.14.1), Home Assistant Google Drive Backup (0.105.2), Mosquitto broker (6.0.1)

Lovelace

dashboards	1
resources	3
views	2
mode	storage

[k-korn]

OK, looks like the issue is that Waze API changed.
This has been fixed in WazeRouteCalculator ( kovacsbalu/WazeRouteCalculator#64 ), relevant commit is
kovacsbalu/WazeRouteCalculator@a502c65

To manually make Waze integration work, one should replace $HASS_HOME/deps/lib/python3.9/site-packages/WazeRouteCalculator/WazeRouteCalculator.py (or whatever the path is at your side) with the content of https://raw.githubusercontent.com/kovacsbalu/WazeRouteCalculator/master/WazeRouteCalculator/WazeRouteCalculator.py

That's a pretty rough hack, but will work until updated version of WazeRouteCalculator is released and integrated here.

[fi-sch]

@k-korn
Is this a solution to the route attribute being empty, or should it also fix the time calculation issue?

[k-korn]

@k-korn Is this a solution to the route attribute being empty, or should it also fix the time calculation issue?

Looks like it fixes both issues.

[rgusick]

I'm also experiencing the time calculation issue. After putting in the same destination on the Waze website I've concluded that it appears to be using the 2nd or 3rd route option which are often much longer than the first option.

I'm glad I found this issue thread. I thought that I was crazy.

[fi-sch]

@k-korn Is this a solution to the route attribute being empty, or should it also fix the time calculation issue?

Looks like it fixes both issues.

Thanks a lot!

Does anyone know where can I find said directory/file (WazeRouteCalculator.py) on HAOS?

EDIT: Found it. I needed to access HA bash first:

docker exec -it homeassistant /bin/bash

[pilot1981]

where I can find $HASS_HOME/deps/lib/python3.9/site-packages/WazeRouteCalculator/WazeRouteCalculator.py in HASSOS installation?

[pilot1981]

var/deps and so on Il ven 31 dic 2021, 17:30 pilot1981 @.***> ha scritto:
…

It don’t exists …

[fi-sch]

where I can find $HASS_HOME/deps/lib/python3.9/site-packages/WazeRouteCalculator/WazeRouteCalculator.py in HASSOS installation?

Launch 'SSH & Web Terminal' add-on and use command that I provided to exec into the homeassistant container.

[kefran95]

Hello,
With the script "WazeRouteCalculator.py", can we retrieve the correct route and time information in the "Waze Travel Time" integration?
Thank you.

[fi-sch]

route yes, travel time no. I live in Italy, I have a HA in Portugal and waze says I need 5-6 minutes to arrive in Portugal. The street is in Hungary -_-

You seem to experience a different issue when it comes to time calculation (#61572). In my case solution provided above fixes all of 7 sensors that I have set up.

[fi-sch]

It is my issue. As I said, it doesn't solve the problem, but I get very funny behavious: if I set the friendly name of my zone.home as destination, I get a "not possible to connect" error while adding the integration, but if I swap destination with origin... et voilà, it works and it calculates something more correct.

And yet you are commenting here, in the thread that relates to different issue.

[kefran95]

Sorry, but I cannot retrieve the correct information. I find myself with a difference of 16 minutes.

[k-korn]

WazeRouteCalculator v0.14 contains the fix for this issue:
https://github.com/kovacsbalu/WazeRouteCalculator/releases/tag/0.14

It should now be trivial to update https://github.com/home-assistant/core/blob/dev/homeassistant/components/waze_travel_time/manifest.json to use 0.14 instead of 0.13 for someone with write access to HA repository to resolve this issue.

[fi-sch]

@Smandurlo You're once again commenting below a different issue. This issue was fixed with WazeRouteCalculator v0.14 and dependency can be updated.