You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The plugin is throwing a warning message to the log, seemingly whenever it hits the OpenWeatherMap API:
WARNING Error getting weather data or Cannot read properties of undefined (reading 'sunrise')
After the error, the plugin waits a minute and then retries, with the same result. So it's hitting the API every minute, which is probably going to cause it to exceed the OpenWeatherMap usage limits.
The plugin shouldn't be throwing this warning, or it should at least wait longer than a minute to hit the API again. I'm assuming that, if it can't determine when "sunrise" is, then the "sunriseOffset" feature probably won't work, and if it hits the API too often, the OpenWeatherMap server will cut off access.
Yep, got an email from OpenWeather saying, "We have noticed that your account is currently using One Call API quite intensively and exceed the account limit of 1000 calls per day."
Describe the bug
The plugin is throwing a warning message to the log, seemingly whenever it hits the OpenWeatherMap API:
WARNING Error getting weather data or Cannot read properties of undefined (reading 'sunrise')
After the error, the plugin waits a minute and then retries, with the same result. So it's hitting the API every minute, which is probably going to cause it to exceed the OpenWeatherMap usage limits.
To Reproduce
Steps or config to reproduce the behaviour:
Expected behavior
The plugin shouldn't be throwing this warning, or it should at least wait longer than a minute to hit the API again. I'm assuming that, if it can't determine when "sunrise" is, then the "sunriseOffset" feature probably won't work, and if it hits the API too often, the OpenWeatherMap server will cut off access.
**Screenshots or logs **
This is repeating every minute:
Platform (please complete the following information):
The text was updated successfully, but these errors were encountered: