Would like to add my 2 cents and context regarding PWS for you and others reading this.
Unless you have installed or know personally the PWS, I would not suggest opting into one through our app. We have viewed a lot of bad data coming from PWS.
Just for an example, we have one installed at the office. It was installed incorrectly under an awning and on any given day the temperature was 20F higher than what was being reported by the national weather station near us.
To be completely transparent, internally we only use PWS data for our weather intelligence (virtual rain sensor) and weather display on the client apps. We do not use PWS for water budgeting. I am not initially planning on using PWS data to calculate ET or precipitation values for flex schedules. Please understand that to mix and match this data is a large undertaking, and to start we are taking a more cautious approach. I will be looking at the best way to incorporate flex schedules using PWS (I’m thinking of using the PWS precipitation for schedule skip, just like we do weather intelligence (virtual rain sensor) ). This will happen after we have enough empirical data on how flex schedules are running. I don’t want to introduce too much, too soon.
Here is a bit more information on PWS.
Here is more information on how weather intelligence works, it is much more sophisticated than a physical rain sensor:
I expect sometime this year to research and implement a different weather service(s) that will allow us to get much, much, more accurate weather data and ET data. Stay tuned