8000 Waze Travel Time · Issue #61572 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Waze Travel Time #61572

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Smandurlo opened this issue Dec 12, 2021 · 24 comments
Closed

Waze Travel Time #61572

Smandurlo opened this issue Dec 12, 2021 · 24 comments
Labels
integration: waze_travel_time stale

Comments

@Smandurlo
Copy link
Smandurlo commented Dec 12, 2021 •
edited
Loading

The problem

I am in Italy and my destination is "home", a Home Assistant server in Portual.
zone.home has the correct gps coordinates as well as my location in the map.
Waze Travel Time is totally wrong:
Duration 5.683333333333334
Distance 1.027
(metric).

ETA is 6 minutes (I really wish it was true LOL)

What version of Home Assistant Core has the issue?

2021.11

What was the last working version of Home Assistant Core?

I don't know

What type of installation are you running?

Home Assistant Supervised

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 errors in the log

Additional information

I had a previous working installation, but I don't remember the core version. I just realized the problem after many version upgrade.
@probot-home-assistant
Copy link

waze_travel_time documentation
waze_travel_time source
(message by IssueLinks)

@Kuba15
Copy link
Kuba15 commented Dec 14, 2021

May be related to #61251 (comment)

@Smandurlo
Copy link
Author

well, I have this problem too. Now the travel route is empy, but it was completly wrong in the past. It said I had to pass in Hungary and the travel time was less than 10 minutes as well.

@fi-sch
Copy link
fi-sch commented Dec 26, 2021 •
edited
Loading

Just FYI. There seem to be a temporary solution to this issue: #61251 (comment) (if it is indeed related).

@Smandurlo
Copy link
Author

Thanks :-) I will wait for the official fix!

@Smandurlo
8000 Copy link
Author

I tried the fix. Replaced the file, but it didn't solve my problem. I have back the route: Best-Székely Mihály utca Budapest VI. Exactly on the other side of Europe. And still 5 minutes from Italy, passing through Hungary and arriving in Portugal.

@fi-sch fi-sch mentioned this issue Jan 3, 2022
Closed
@Smandurlo
Copy link
Author
Smandurlo commented Jan 3, 2022 •
edited
Loading

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.

This one is 8 min. Italy to Portugal.

attribution: Powered by Waze
duration: 8.166666666666666
distance: 1.027
route: Best-Székely Mihály utca Budapest VI.
origin: *** my gps origin in Italy
destination: home
unit_of_measurement: min

This one is, almost correct, Portugal to Italy

attribution: Powered by Waze
duration: 1602.4833333333333
distance: 3077.977
route: Natural-A-4
origin: *** my GPS from friendly name
destination: *** my address in Italy from my GPS tracking device
unit_of_measurement: min

Now I really got stuck because sometimes it doesn't create the integration (impossible to connect) and it depends how you enter the origin/destination fields and sometimes it create a not correct time in one direction, but the opposite is fine.

@Smandurlo Smandurlo mentioned this issue Jan 3, 2022
Closed
@fi-sch
Copy link
fi-sch commented Jan 4, 2022 •
edited
Loading

Distance says it's 1 km, so the 8 mins duration seems fine.

Are you sure that you provide proper friendly name of zone.home?
Did you try referring to entity instead of it's friendly name?
Are you sure that your zone.home has proper coordinates?
Did you try using those coordinates instead of a friendly name?

@Smandurlo
Copy link
Author
Smandurlo commented Jan 4, 2022 via email

@fi-sch
Copy link
fi-sch commented Jan 4, 2022 •
edited
Loading

Can you provide me both pairs of coordinates and exact settings for both routes? I will test both directions on my side. (HA Core 2021.12.6, applied fix for 'WazeRouteCalculator.py')

@Smandurlo
Copy link
Author
Smandurlo commented Jan 4, 2022 •
edited
Loading

latitude: 42.6688309
longitude: 13.6820182

latitude: 37.138199
longitude: -7.5953

No particular settings, everything is "as is" while you create the integration.

For the reference, using both coordinates as origin and destination it says "impossible to connect" in both directions and it doesn't create the integration
8000

@fi-sch
Copy link
fi-sch commented Jan 4, 2022 •
edited
Loading

No particular settings, everything is "as is" while you create the integration.

You should select region 'EU'. "As is" is 'US', at least on my side.

For the reference, using both coordinates as origin and destination it says "impossible to connect" in both directions and it doesn't create the integration

This is what I get with those coordinates. It is strange indeed, however looks like a another issue that should be investigated.
What I tried:
Origin: 42.6688, 13.6820
Dest: 37.1381, -7.5953
Region: EU

@Smandurlo
Copy link
Author

yes, Europe. I thought it was clear since I spoke of Italy and Portugal. I selected EU. What do you get?

@fi-sch
Copy link
fi-sch commented Jan 4, 2022

yes, Europe. I thought it was clear since I spoke of Italy and Portugal. I selected EU. What do you get?

"Impossible to connect" message.

@Smandurlo
Copy link
Author
Smandurlo commented Jan 4, 2022 via email

@fi-sch
Copy link
fi-sch commented Jan 5, 2022 •
edited
Loading

Will be fixed in version 0.15 of WazeRouteCalculator. It should be released soon, according to kovacsbalu/WazeRouteCalculator#65 (comment).

@JayOne73
Copy link
JayOne73 commented Jan 6, 2022 •
edited
Loading

Nevermind, meant 0.14

@Kuba15
Copy link
Kuba15 commented Jan 11, 2022

I have just updated to the HA 2021.12.9, the waze travel time looks correct now

@Smandurlo
Copy link
Author

It needs another fix that will be added in 0.15

@kovacsbalu
Copy link

kovacsbalu/WazeRouteCalculator/0.15

@Smandurlo
Copy link
Author

it fixes the problem, now it needs to be updated to HA

@fi-sch
Copy link
fi-sch commented Jan 17, 2022

it fixes the problem, now it needs to be updated to HA

Is proper PR already approved? If not, then you can reopen this issue as it is not fixed yet.

@Smandurlo
Copy link
Author

Sorry, I don't know how it works.

@Smandurlo Smandurlo reopened this Jan 17, 2022
@github-actions
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Apr 17, 2022
@github-actions github-actions bot locked and limited conversation to collaborators May 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
integration: waze_travel_time stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@kovacsbalu @Kuba15 @Smandurlo @JayOne73 @fi-sch
0