I tried looking for global solutions. There is one, SoilGrids, but it's still in beta and not reliable. I tried it even though they said the service is “suspended.” The endpoints are up but don't always work or have valid data.
At least WET-IT has the right season for you. I did build that smarts in. 
Have installed the latest version with scheduling and set up all 6 zones on my B-Hyve controllers. It passes all the diagnostics, but gives a No valid API key error. How can I fix this?
Are you seeing that for any of the other wx providers or just Tempest? I tried to recreate it on my end, but I don't have access anymore.
Last API Test: 
TEMPEST API test failed: status code: 401, reason phrase: Unauthorized
Cutting me off is the right thing to do, it just makes it harder to make sure what I'm seeing is the issue.
The logs show you are definitely getting weather and connecting at the validation stage. Looking at the code, I think the issue is when the wx update occurs every two hours.
If you'd be so kind as to let me in, I'll validate the fix I just made and then push it.
What controller are you using to get this working, I am also in Aus and keen to get this setup.
As they say...
Upon further review from the booth...
It looks like Weatherflow broke this for everyone. I checked not only my code, I checked a couple of other drivers, and even their own “test” site:
WET-IT → 401 drdsnell WeatherFlow driver → 401 augoisms WeatherFlow Lite driver → 401 Swagger UI → 401 curl / Postman / browser → 401All of them:
https://swd.weatherflow.com/swd/rest/*token=Multiple independent codebases, all failing the same way, points to an upstream policy change.
I even hopped around to a couple of different public IPs to make sure it wasn't me being blocked.
The good, not great news is you can toggle on NOAA as a backup, and everything you've done will work, just not with your local data.
Is anyone else seeing 401 errors with either of the other two WeatherFlow drivers? I still need to do some digging, just wondering if they moved to 100% OAuth or changed the URI and not update the docs or ??? something, anything?
Bueller? Bueller? Bueller?
Ecowitt GW1101 / WS69
Sorry I was talking irrigation controller.
Oh sorry, I’m just using tuya Zigbee valves.
I’m so far from needing irrigation right now in the Pacific Northwest, but really looking forward to giving this a spin. Orbit B-hyve has been so unreliable with the forecasting that I just switched to time based last summer.
Would it be possible to just allow users to select weather station sensor data manually, and add separate forecasting from one of the existing sources you’re already using? There are already enough ways to get personal weather station data into Hubitat, so we should be able to just select the sensor data and put them into your app without you having accomdate a number of different weather station APIs.
Awesome thanks, just purchase the Tuya 8 zone from Ali, hopefully that plays nice.
Download the Hubitat app
