Turn any electrical irrigation valve into a smart-valve.. or run your pumps on a smart schedule based on your climate! This homebridge plugin exposes a multi-zone irrigation sprinkler dummy control system to Apple's HomeKit. Although a dummy, it brings smarts of an evapotranspiration based climate and plant adaptive irrigation controller with the use of OpenWeatherMap API. The plugin can optionally email you, and/or send you push notifications through Pushover or Pushcut, with the watering schedule it has calculated, or when a watering run is completed, along with the next 7-day weather forecast. Added option to expose system controls to Homekit allowing a user to enable/disable irrigation, rechecks, push and email notifications from within the Home App. Associated WaterLevel Characteristic shows the % of watering cycle remaining.
MIT License
77
stars
3
forks
source link
[BUG] Not pulling sunrise data from API call, retrying every minute #56
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):