Waze travel time update

yes it is, just look for the card in hacs

Can you change the log level to warning or even info? if it is expected than it is not probably error. I can suppress the error but then I will not see real errors …

Hi, I’m staying in Asia and may i know what region should i put? It seems doesn’t have options for Asia region.

you can do that through logger.

The rest of the world for Waze works off “EU” for this api for some reason.

1 Like

Ok. I will try it out and report the result here. Thanks

If that doesn’t work, also try NA. The api is really limited. It’s clear that it wasn’t meant to be used this way.

Hi, the ‘EU’ region is working in Malaysia. Thanks alot.

@Mariusthvdb thank you for sharing your amazing card.
I do wonder if it is possible to change the fields to a friendly_name of a sort,
meaning zone.XXXX will show a zone name instead.
Origin - will show full address, instead of coordinates,
and under Travel time Name will be presented origin location and destination location?

I guess anything is possible… you need to create a few ‘mappers’, ie, template sensors that map the name to the state (for the zone), and maybe you can do the same for the frontend representation of the gps coordinates.

about the name: I only now notice that doesnt change indeed :wink: hmm. must have a look when I can find the opportunity…anytime soon. This is a Waze-card issue with the Waze sensor, so will have to go back to that (havent seen it in a while now). As I see it now, it show this sensor:

  - platform: waze_travel_time
    name: Select Origin Destination
    origin: sensor.origin_address
    destination: sensor.destination_address
    region: EU

which name you can set of course, to your liking. It won’t change given the gps coordinates. Quickly changed it to Route Planner for now:

1 Like

@Mariusthvdb Thank you for explaining, i did not know about the mappers option, so thank you for education me about it, though working a long while on making it work was unsuccessful.
could you please point me to where should i use mappers in this case?
changing sensor template using mapper return the name instead {{ lat }}, {{ lon }} and break the results of waze, as far as i know lovelace yaml cannot have template, there for i am a bit lost on the how to…
as for my config - it is basically similar to your implantation above.

Tried both NA and EU but keep getting status Unknown and I’m in Thailand.
Any suggestions?

You can give IL a try but I’m not sure it will work. Typically NA works for everyone (Not sure why). The API itself is very limited.

With NA I can get 1 min to destination, but nothing it is constant. I’ll give IL a try as well…

What are you providing for addresses? If you use lat/lon it should work everywhere.

Also, make sure your lat/lon are in the correct order if you’re using comma separated values

Like this.

image

And configuration.yaml

And you verified those lat/lon using google or something of the like? If you used the waze live map, it reverses the order of lat & lon.

Yeah. I used Google Maps to verify lat/lon. I checked them again and the shows right. Should I reverse the order in my secrets file?

No, don’t reverse them in the file. It expects lat/lon. Unfortunately, its been 3 years since I’ve looked at this integration. I can’t remember anything else that could be the problem.

Capture

This what I get at the most. :frowning: Thanks for the help anyways!