Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Waze empty responses
See original GitHub issueThe problem
I have defined 2 sensors of Waze Travel Time, it throws at least 3 times an hour warning messages of empty response for one of the intergations (sensors)
today at 10:09:19 AM2022-02-08 10:09:19 DEBUG (SyncWorker_30) [homeassistant.components.waze_travel_time.sensor] Fetching Route for Waze Home to Payoneer
today at 10:09:19 AM2022-02-08 10:09:19 INFO (SyncWorker_30) [WazeRouteCalculator.WazeRouteCalculator] From: 32.28*************,34.91************ - to: 32.09*****,34.84************
today at 10:09:19 AM2022-02-08 10:09:19 DEBUG (SyncWorker_30) [WazeRouteCalculator.WazeRouteCalculator] Start coords: (32.28*************, 34.91************)
today at 10:09:19 AM2022-02-08 10:09:19 DEBUG (SyncWorker_30) [WazeRouteCalculator.WazeRouteCalculator] End coords: (32.09*****, 34.84************)
today at 10:09:19 AM2022-02-08 10:09:19 DEBUG (SyncWorker_17) [homeassistant.components.waze_travel_time.sensor] Fetching Route for Waze Payoneer to Home
today at 10:09:19 AM2022-02-08 10:09:19 INFO (SyncWorker_17) [WazeRouteCalculator.WazeRouteCalculator] From: 32.09*****,34.84************ - to: 32.28*************,34.91************
today at 10:09:19 AM2022-02-08 10:09:19 DEBUG (SyncWorker_17) [WazeRouteCalculator.WazeRouteCalculator] Start coords: (32.09*****, 34.84************)
today at 10:09:19 AM2022-02-08 10:09:19 DEBUG (SyncWorker_17) [WazeRouteCalculator.WazeRouteCalculator] End coords: (32.28*************, 34.91************)
today at 10:09:19 AM2022-02-08 10:09:19 WARNING (SyncWorker_30) [homeassistant.components.waze_travel_time.sensor] Error on retrieving data: empty response
today at 10:09:20 AM2022-02-08 10:09:20 INFO (SyncWorker_17) [WazeRouteCalculator.WazeRouteCalculator] Min Max
today at 10:09:20 AM27.40 46.65 minutes
today at 10:09:20 AM26.14 34.76 km
What version of Home Assistant Core has the issue?
core-2022.2.3
What was the last working version of Home Assistant Core?
core-2021.11.0
What type of installation are you running?
Home Assistant Container
Integration causing the issue
waze_travel_time
Link to integration documentation on our website
https://www.home-assistant.io/integrations/waze_travel_time
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:29 (1 by maintainers)
Top Results From Across the Web
Waze Travel Time - Configuration - Home Assistant Community
I have added the waze travel time and it seems to work well. I took a look at my log though, ... Error...
Read more >Blank Map - Page 18 - waze.com
Certain parts of my map are blank but show up when zoomed out very far. When driving into a blank area, Waze acts...
Read more >Blank maps? Failed starts? : r/waze - Reddit
Just a frozen screen of the map pin as though I was at home. The only way out of it would be to...
Read more >Fix a map issue - Waze Help - Google Support
Report an issue in the Waze app · Tap Reports · Tap Map Issue · Tap Map Issue again · Tap an issue...
Read more >Method: health | Waze Ads Management API
HTTP request; Query parameters; Request body; Response body; ServingStatus ... Request body. The request body must be empty.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same here 2022.4, 2022.4.1
rate limiting for all on the same time, most likely maintenance or less resources to support the load with the old API