Good point… still a “skip due to rain.” Thread title updated.
I’d expect no notifications related to schedules or the skipping of them while in standby. If there was a “Winterized” option that mutes those notifications yet allows system level notifications (loss of connection, power loss, etc…) I’d use that. We’ve had other heavy rain storms this winter and I don’t remember V2 popping these during standby. Or I swiped them away too quick to remember. Always possible.
For the scenario you asked about though, I don’t see it as any different than if my schedule were going to be skipped due to current soil moisture levels, predicated rain, freeze skip, etc…
I think I’d expect something along the lines of the following;
- Operator changes the status of the controller to take it out of standby. Similar to your new “Updating devices…” screen in V3 you then get a “Checking conditions…” screen.
- While “Checking conditions” is happening the controller is checking weather forecasts for recent rainfall totals, predicted rainfall, temperatures, and updates current/predicated soil moisture. In parallel it checks the status of any connected rain sensor.
- “Checking conditions” then goes away and you may get some sort of “Controller is once again operational and your schedules will resume within the parameters you have configured.”
- Then, if necessary, you get a notification or perhaps it is part of the screen in #3, “While resuming operations your controller discovered your rain sensor became active at ##:## on MM/DD. All schedules will be skipped until the rain sensor is deactivated.”
- Then, also only if necessary, you’d get a toast stating the day’s schedule would be skipped due to “X” reason like it normally would whether it is predicted rainfall, freeze temp, etc… However, this may only be useful for users with a schedule set to run in the middle of the day. If you’re already past the schedule end-by time (e.g. by sunrise or by 5:45AM) I would expect the notifications system to sit dormant until the next watering event.