Waze Reisezeit Integration

sirector · 30. September 2026 um 22:24

Die Integration Waze zeigt nur noch 403 forbidden. Das Problem wurde bereits gemeldet

Waze Travel Time: routing requests return HTTP 403 Forbidden for coordinates too (all regions)

offen 06:13PM - 30 Sep 26 UTC

integration: waze_travel_time

### The problem Since 2026-09-30 ~17:30 UTC all my Waze Travel Time sensors (8 …config entries) became `unavailable` at the same time. The coordinator logs: ``` Error fetching waze_travel_time data: Error on retrieving data: <!doctype html><meta charset="utf-8"><meta name=viewport content="width=device-width, initial-scale=1"><title>403</title>403 Forbidden ``` All entries use **coordinates** for origin and destination (no addresses), so this is not the address lookup problem from #183673 / pywaze#105. The failing call is the routing request itself. The sensors had been working normally on 2026.9.4 until 17:26 UTC the same day (5-minute polling, valid durations), so this does not look like a regression in a Home Assistant release but a change on the Waze side. ### Reproduction outside Home Assistant Same result with pywaze 1.2.1 (the version with the fix from pywaze#105) run standalone: ```python import asyncio from pywaze.route_calculator import WazeRouteCalculator async def main(): c = WazeRouteCalculator(region="EU") try: print(await c.calc_routes("40.4169,-3.7035", "40.4065,-3.6895", vehicle_type="CAR", real_time=True)) finally: await c.close() asyncio.run(main()) # -> WRCError: <!doctype html>...<title>403</title>403 Forbidden ``` And with plain curl against the routing servers: ```bash P="from=x%3A-3.7035+y%3A40.4169&to=x%3A-3.6895+y%3A40.4065&at=0&returnJSON=true&returnGeometries=false&returnInstructions=false&timeout=60000&nPaths=1&options=AVOID_TRAILS%3At" curl -s -o /dev/null -w "%{http_code}\n" -A pywaze -H "referer: https://www.waze.com/" \ "https://routing-livemap-row.waze.com/RoutingManager/routingRequest?$P" # 403 ``` Findings: - `routing-livemap-row`, `routing-livemap-am` and `routing-livemap-il` all return **403** (also with a US route on `-am`). - Same 403 with a browser `User-Agent`, so it is not only a `User-Agent` filter on `pywaze`. - Same 403 from two different IPs: a residential ISP connection in Spain and a VPN exit in Germany. - `https://www.waze.com/` itself returns 200. ### What version of Home Assistant Core has the issue? core-2026.9.4 ### What was the last working version of Home Assistant Core? core-2026.9.4 (worked until 2026-09-30 ~17:26 UTC; the break is not tied to an update) ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Waze Travel Time ### Link to integration documentation on our website https://www.home-assistant.io/integrations/waze_travel_time/ ### Additional information - pywaze 1.2.0 (bundled with 2026.9.4) and 1.2.1 (standalone test) both fail. - Region EU, vehicle type car, realtime enabled. - Related: #183673, #183660, pywaze#105, pywaze#107.

MIB72 · 1. Oktober 2026 um 09:27

Bei mir das gleiche Problem

sirector · 1. Oktober 2026 um 15:24

Das werden ganz viele haben.

Guenter · 2. Oktober 2026 um 08:50

Waze Travel Time: Forbidden 403 error.

Sind auch schon mehrere issues gemeldet - bleibt leider nur abzuwarten.

sirector · 2. Oktober 2026 um 08:50

Ist gefixed und wird hoffentlich mit 2026.10 wieder laufen

sirector · 8. Oktober 2026 um 06:16

Der Fix wurde integriert aber funktioniert nicht. Es gibt noch ein anderes Problem. Abwarten…

maxe · 8. Oktober 2026 um 07:32

Soll jetzt mit 2026.10.1 gefixt werden.

Thema		Antworten	Aufrufe
Waze_travel_time: „403 Forbidden" beim Datenabruf – nur bei mir oder allgemein? Allgemein	18	125	15. Oktober 2026
Waze Integration - 410 Gone Allgemein	0	447	24. November 2025
Probleme mit Waze Reisezeit Integrationen	4	597	23. Oktober 2025
403 Forbidden bei homeassistant.local Allgemein	9	123	5. August 2026
Grohe Sence App funktioniert nach integration in HA nicht mehr Add-ons	3	308	7. März 2026

Waze Reisezeit Integration

Verwandte Themen