WTH is happening with the Waze Travel Time sensor?

ikifar2015 · August 18, 2020, 2:49pm

It has been broken for a very long time now just look at the GitHub issue https://github.com/home-assistant/core/issues/22022

stboch · August 18, 2020, 4:32pm

Strange it seems to be working fine for me…
There is one bug that is more of a waze/ha thing if the gps if the origin and destination are the same place there is a nonetype error.

happy to help figure what I am doing differently.
0.114.2

ikifar2015 · August 18, 2020, 5:34pm

The log displays this error

Error on retrieving data: empty response

petro · August 18, 2020, 5:41pm

We can suppress the error but the error is coming from them. Nothing can be done as we don’t own the api.

EDIT: To elaborate. We send a request. The request is ‘hey get me the drive time between here and there’. They respond with “I got nothing”. We log everytime they say “I got nothing”. The common causes of this is incorrect latitude and longitude. Every now and then the API sends this error even if the information is correct. And to clarify about the API, it’s 100% controlled by Waze, so we are unfortunately held to whatever they send us.

stboch · August 18, 2020, 6:25pm

Not sure how you are formating the Origin and destination, have you tried using a zone?

example:

- platform: waze_travel_time
    name: "Steven Commute - to work"
    origin: zone.home
    destination: zone.steven_work
    region: 'US'

ikifar2015 · August 18, 2020, 9:11pm

Yep it works the example in the docs still shows an address though and it did work with an address at some point

petro · August 18, 2020, 9:50pm

it still works with addresses, but the format has to be a good address format.

ikifar2015 · August 18, 2020, 11:17pm

It was working with the addresses I had until 0.89 thats why I thought it was broken, can you provide an example of proper format?