wait, are lat. and lon.xxx written in your file?
You should just have the number. Meaning
home_address: 43.234234, 23.4423452
work_address: 43.234234, 23.4423452
Yeah had lat.xxxxxx, lon.xxxxx in my secrets file.
Donât know where I saw that but thats the only way Iâve been able to get any kind of info showing instead of unknownâŚ
I changed it now and waiting for update!
Wohooo! After changing back to EU instead it finally seems alright! Thank you so much for the help!
1 Like
Does it still wait 5 minutes before updating after bootup? I donât use the sensor
For what I understand, yes. Takes around 5 mins after reboot for me to get info.
I have been looking in the Waze API to see if there is anything that could be done.
I noticed the API that the calculator uses returns three results but two is discarded.
Iâm thinking that all three could be displayed and how much delay you can expect on each route.
I made a sample in php, because I donât know python enough.
Here is first the dump of the array where you can see the route name, the time the route takes and the normal time (N).
So time - Normal time = delay on that route.
If you have all three results then you can see why the normal route is not suggested.
From the source I can see
Does that mean WazeRouteCalculator is not part of HA and is a external source? Because I canât find that code in HA.
Itâs an external library, also it doesnât always provide 3 results. Itâs a max of 3 results. Lastly, you wonât be able to change the attributes because they are common amungst all the travel time integrations
Has this stopped working for anyone else, or is it just me?
Iâve got entity is unavailable on my dashboard for both sensors I have, and various different errors relating to aiohttp in the logs.
I did seem to stop working around the same time as a local internet outage, which was the same time as the facebook/whatsapp etc. downtime.
1 Like
Hi, can this be updated manually? I did upgrade to the new release today (core-2021.10.0) and Waze started working again, but the update breaks my installation because of Tuya and i have numerous blinds which is not currently being supported
Tanks for input
Confirmation of fix by todayâs update. Works again.
Hello, thanks for your integration. I have some problem with it and I donât know how to investigate for the reason.
Origin is an entity with GPS. Destination I tried âzone.homeâ and it says âcannot connectâ. I tried with latitude,longitude and it again âcannot connectâ. Then I tried wist home only, and it accepted the configuration, but it returns a completly wrong number of minutes.
I am in Italy and the destination is in Portugal. Waze Travel Time 16 minutes.
Maybe is it something connected with the metric system (inverted use of dot and comma)? The route is also crazy⌠passing through Budapest.
With the Waze app on my mobile, the time and route is correct (23 hous through Spain).
Hi. I am trying waze for the first time and have created several sensors via the UI integration. The region I used is EU. It seems to be working, but in the log I see loads of these warnings pretty much after creating those sensors.
error:
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:661
First occurred: 4:40:44 PM (38 occurrences)
Last logged: 7:20:45 PM
Update of sensor.eri_to_work_waze is taking over 10 seconds
Update of sensor.duc_to_home_waze is taking over 10 seconds
Update of sensor.eri_to_home_waze is taking over 10 seconds
The api for waze is a web api, itâs a hack and it doesnât work very well. Youâre going to get issues like this all over the place. You can try switching to the NA servers which seem to be better than the EU servers. Also, if youâre using an address, just put in the lat/lon. It works better and skips a whole portion of their api.
ok. thanks. I will try the NA server.
Hello, Iâm noticing that the route is empty. Is this normal? If not, how can I fix it? Thanks!
post your configuration. The route can be empty if you over constrain it or have the latitude and longitude flipped. Also check for errors in the logs. The site sometimes doesnât work and you have to wait 5 minutes between each route calculation.
1 Like
I used to have it in my configuration but now it is configured in the UI. I have no constrains set. Everything seems to be working correctly, I just have an empty route attribute.
attribution: Powered by Waze
duration: 46.45
distance: 39.85456805469236
route: ''
origin: xx,xx
destination: xx,xx
unit_of_measurement: min
friendly_name: Codys commute
icon: mdi:car
This is the only error I see occurring occasionally in the logs.
Logger: homeassistant.components.waze_travel_time.sensor
Source: components/waze_travel_time/sensor.py:329
Integration: Waze Travel Time (documentation, issues)
First occurred: 1:23:31 AM (14 occurrences)
Last logged: 10:38:31 AM
Error on retrieving data: empty response
That means the API decided not to respond to the request.
Unfortunately I canât help with this configuration as I wrote the original waze integration and someone else must have added it to the UI. Sorry.
1 Like
I might try adding it back to my config and see if that fixes it.