AccuWeather data not updating in the morning for a few hours

I’ve noticed a weird situation where the AccuWx integration data is not being updated each morning (local time) for a few hours. The graph below shows the stats from AccuWx API website (between 09:00 and 12:00 UTC) supposedly showing that either HA is not making these requests or they are not receiving them.

I don’t see any errors in the general log, and just turned on the debug for the specific module to see if there is anything useful there.

The integration doesn’t have any open issues, and I can’t imagine I would be the only one seeing this is if it’s truly happening for many. Plus I’m only using about 44 or so of my allowed 50 API calls per day according to their stats.

Anyone else have any ideas or seeing something similar?

You are probably using all allowed requests. Integration consumes 40 requests per day. If you use more of them, you either use some automation that forces data to be downloaded or you restart HA/reload config entry too often.

That’s not the issue as I mentioned above. I’m only using 44 max requests a day based on how the integration is designed.

You can’t be sure without analyzing the whole day debug log.

As I mentioned above, the log shows clearly each time it sends a message to the API how many requests remain. This was the last message of the day right before it rolled over to start at 50 again.

Do you have any other suggestions?

Without the log? No.

Did you ever get this resolved? Same happening to me.

@Bieniu I noticed the same issue this morning. However, I do see the REQUESTS_EXCEEDED error in my logs. It failed yesterday (Aug 4), the day before (Aug 3) and July 30th. It probably correlates to me updating my software causing a reboot. Is there a plan to ensure that those 50 requests get partitioned equally during the day so they don’t end up getting consumed needlessly by reboots?

Integration consumes 42 requests per day so there are 8 left for HA/system restarts. This allows HA/system restarts 4 times per day. In my opinion this is enough and there is no reason to change the logic that works.

OK. Thanks. I must have an unusual use case then.

I reverted back to the Meteorologisk integration and I think I’m all set. This article helped me pick an alternative.

Forcing you to give your creditcard information is not a good reason to change?

Correction: this is now OpenWeatherMap :disappointed:

I don’t quite understand your comment. Who am I forcing to use a credit card?

Had it confused with OpenWeatherMap. Durp
/me hides in shame

No worries

1 Like

Hello,
I solved this problem by changing location in accuweather cloud api. https://developer.accuweather.com/
By default it is set to International. I change it to France, my location, and there is no more delay.

I’m seeing this same issue as well, where in the morning at 7:30 AM it will not have updated for around 8 hours and thus shows stale data (including current condition as something like “Clear, night” and the previous day as the left most day in the 5 day forecast).

For my AccuWeather app at the developer site, I do see it shows “Country: United States” in the Details tab and my profile has the “America / New York” time zone as expected. Is there any other setting here that could be relevant?

What’s the easiest way to see if somehow I’m exceeding API requests? I would have thought that would reset at midnight, so a 7-8 hr gap of no updates after midnight seems suspicious.

So another quick update on this after I figured out how to turn on debug logging for the AccuWeather integration. I turned it on to track what happened from Feb 1 evening/night to Feb 2 morning.

For Feb 2, my Message Count graph in the AccuWeather App Analytics tab looks very much like the OP, showing regular activity each hour but then a gap of zero activity from 7:00 UTC to 12:00 UTC. This should correspond to 2:00 AM EST to 7:00 AM EST (my local time zone).

From the debug logs, I can that see the transition when the number of requests goes back up to 50 between the 8:35 PM and 9:15 PM requests. This seems odd as it is neither midnight in my local time zone nor midnight UTC, which would be 7:00 PM EST. Also note there is no indication that I’ve ever run out of requests or had a failed request.

2025-02-01 20:35:00.491 DEBUG (MainThread) [accuweather] Data retrieved from https://dataservice.accuweather.com/currentconditions/v1/2126120?apikey=xxx&details=true&language=en-us, status: 200
2025-02-01 20:35:00.492 DEBUG (MainThread) [homeassistant.components.accuweather.coordinator] Requests remaining: 10
2025-02-01 20:35:00.493 DEBUG (MainThread) [homeassistant.components.accuweather.coordinator] Finished fetching Forecast AccuWeather Katonah (observation) data in 0.127 seconds (success: True)
2025-02-01 21:15:00.487 DEBUG (MainThread) [accuweather] Data retrieved from https://dataservice.accuweather.com/currentconditions/v1/2126120?apikey=xxx&details=true&language=en-us, status: 200
2025-02-01 21:15:00.488 DEBUG (MainThread) [homeassistant.components.accuweather.coordinator] Requests remaining: 49
2025-02-01 21:15:00.489 DEBUG (MainThread) [homeassistant.components.accuweather.coordinator] Finished fetching Forecast AccuWeather Katonah (observation) data in 0.124 seconds (success: True)

What’s even stranger is that I actually never see a lull in the debug log during that 2 AM EST to 7 AM EST period in which the AccuWeather analytics graph shows zero activity. For example, here is a successful update at 3:55 AM:

2025-02-02 03:55:00.491 DEBUG (MainThread) [accuweather] Data retrieved from https://dataservice.accuweather.com/currentconditions/v1/2126120?apikey=xxx&details=true&language=en-us, status: 200
2025-02-02 03:55:00.492 DEBUG (MainThread) [homeassistant.components.accuweather.coordinator] Requests remaining: 38
2025-02-02 03:55:00.492 DEBUG (MainThread) [homeassistant.components.accuweather.coordinator] Finished fetching Forecast AccuWeather Katonah (observation) data in 0.127 seconds (success: True)

Also looking at the Home Assistant logbook for the AccuWeather entity, I see updates at 3:15 AM (Partly Cloudy), 3:55 AM (Clear, night), 6:35 AM (Cloudy), and 7:15 AM (Partly Cloudy).

So to be clear, Feb 2 morning was not one of the problematic mornings I’ve mentioned I’ve had, where I wake up at 7:30 AM and see stale current conditions and forecasts, but there’s still something quirky going on here. Maybe all tied to local time zone vs UTC? Will keep an eye on this and see if I can capture debug for a morning with the stale data.

Any insights on this would be appreciated - thanks!

I found the setting tied to the AccuWeather API key that I believe @Fredzxda was referring to, and it does appear that that has fixed my issues.

For others who are interested, navigate to the AccuWeather APIs website, login, go to My Apps, and click into the app you previously created. Then click the Edit button and under “Is this Worldwide or Country specific use?” select “Country”. That should then make a select box appear below where you can select your country.

I’d still love to know exactly what this setting does, but it seems like now my current conditions and forecast are rolling over before when I wake up. I would have thought this setting would need more specific details than country (e.g. time zone) if it’s relevant for that rollover time.

EDIT: Argh, spoke too soon. Woke up today (Wednesday) at 7:30 AM and see the five day forecast still starts with yesterday (Tuesday). It also says the forecast was updated 17 minutes ago. Nobody else seeing these kinds of issues??

I’m in the process of migrating from Hubitat to HomeAssistant. While setting things up, adding HACS, Add Ons, and Integrations, required restarts are causing me to routinely exceed the 50 API limit. I’m hoping this will be less of an issue when the system is built out and stable, however, I also know that this is a ways off.

@Bieniu
Is there anyway to throttle the API calls or maybe make them only trigger from an automation that runs once a day regardless of HA reboots?

Yes, you can disable automatic updates and get data yourself via automation and homeassistant.update_entity action.

1 Like