Hi,
410 Gone
The sensor is always “Unavailable”.
Thanks.
NathanCu
November 28, 2025, 8:06am
2
Known and apparently the fix is already in the next release…
opened 08:23PM - 24 Nov 25 UTC
closed 09:49AM - 25 Nov 25 UTC
Hey, @eifinger
First of all thanks a lot for this project.
I have a long-runni… ng script that has been using WazeRouteCalculator for a long time (for commute time estimations). It worked reliably for months, but recently all calls to Waze now fail with an HTML response 410 Gone instead of route JSON.
This happens consistently even when:
Using different proxy exits (several IPs)
Verifying that the proxies are alive and can reach other HTTPS sites (e.g., https://www.gstatic.com/generate_204, http://ifconfig.me/ip)
The net effect is that calc_route_info now always fails.
- Has Waze changed or deprecated the internal routing endpoint / URL that WazeRouteCalculator relies on?
- Is this library now effectively deprecated because the underlying endpoint is gone, or is there an updated endpoint / path that should be used instead?
- If there is any known workaround (different URL, headers, params, etc.) or a recommended successor library, I would really appreciate pointers.
Thanks!
Thank you! Good to know it’s a known issue and already fixed in the next release. Do you happen to know when the next release is expected? Thanks again!
This integration is part of Core, so if you update to Home Assistant Core 2025.12.0 that just released yesterday then it’ll be fixed.