- This topic has 9 replies, 5 voices, and was last updated 5 years, 9 months ago by
.
-
Posts
-
I realize that bad things have been happening with the Wunderground API, but I am still able to use my API key to make Json calls for weather history that I keep in a spreadsheet. However, my OSPi, since its last re-boot, has not been able to pull weather data and I can’t even seem to find the place where I originally entered my still-working Wunderground API key. Did that API call feature somehow get automatically removed from my OSPi or have the working API keys ceased functioning with OSPi? I have not manually updated the firmware in close to a year on the RPI0W unit that runs my system. Do I need to do some sort of regression installation to get the Wunderground API key function back? The web page for my OSPi reports App Version 1.8.4, Firmware 2.1.8(1), and Hardware Version OSPi. Thanks!
We are no longer using WUnderground with OpenSprinkler. The current state does not allow much room for development/testing and is very inconsistent. We have decided to focus our efforts on OpenWeatherMaps.
The app is no longer exposing the key field as of 1.8.3. The weather service is also now ignoring the weather key. If you wish to go back to the prior state of things you could run your own local weather service based on a prior commit or possibly explore the solution written by @Peter. Details are here: https://opensprinkler.com/forums/topic/cutting-the-weather-underground-cord-homebrew-solution/
How do I clear out the old WU API key? The latest firmware has hidden it and unfortunately whatever is running at present is simply not working (no watering happening). When I look in my export config I can see that the WU API key is still present in the config but if I try and manually edit the config to set the API key to “” and upload the edited version it doesn’t seem to work.
The API key can be removed by following the steps here you can remove it: https://opensprinkler.com/forums/topic/no-more-free-wunderground-api-key/page/4/#post-54166
However, please note there is no reason to remove it really. The Weather Service API will ignore that key now and always use OpenWeatherMaps. Regarding the quality we are working to improve our data from OWM.
I’m sorry to be a bit confused – but, in my app, I’ve set my location in Main Menu > Edit Options > System. I’m now seeing a seemingly correct weather forecast on the main page in the upper left corner. However, I’m also not getting any watering – the “Water Level” has been stuck at “0%” for a while now. Also, in Prefs Menu > System Diagnostics, the “Last Weather Call” is reporting a recent (an hour ago) call, but the “Last Successful Weather Call” is blank.
Am I experiencing some kind of failure?
App Version 1.8.4
Firmware 2.1.5 (1)
Hardware 2.1 – ACSame issue here. In the end I have had to disable zimmerman and set a manual weather adjustment which is a real pain. If I use the automated then with the new weather source and code I get watering set to zero and the plants die.
We have made changes to our weather service which should fix some of these issues. Could you please let us know if you continue to have the issue now?
Thank you!
Seems to be working for me – “Last Weather Call” and “Last Successful Weather Call” are both current and matching and the Zimmerman adjustment is changing in what seems to be a weather-appropriate fashion.
The Zimmerman calculation is not working correctly, as evidenced that it changes throughout the day. Properly calculated, Zimmerman is based on the previous day’s average temperature and average humidity and the previous day’s total precipitation plus any rain today. If there’s no rain today, then the water level percentage should not change from midnight to 11:59 p.m. But it does, and it’s useless in a climate where night time temps drop significantly. There is no way that the current weather data source can work unless OpenSprinkler aggregates the hourly data calls and then computes the averages.
- You must be logged in to reply to this topic.