I would like to bump this topic back up. We had a very very miniscule amount of rain yesterday (0.02in as reported by KNKX which is the NWS used by my Iro). To be honest, I would not even have bothered to set a rain delay had I been using an older timer.
Anyway, my IFTTT recipe for triggering a rain delay appears to have fired yesterday in the evening. I was not aware of this happening because that does not result in any push notification to the iOS app. However, when I looked at my history log this morning, it shows the rain delay coming from IFTTT. Thank you for implementing this suggestion, @franz. Could you also please consider implementing a push notification when any changes are made by external sources (such as IFTTT)? I would have actually liked to override the rain delay in this particular instance and let my normal schedule run today.
That being said, I would still like to complain about the messaging in the history. Even though yesterday’s log shows the rain delay being set, today’s log still says “zone was not skipped…”. The system did NOT run, so the zone was actually skipped (due to rain delay). I would say the existing verbiage is still confusing:
On a side note, even though we have water restrictions in Southern CA (which say no watering for 48 hours following any measurable rainfall), I’m beginning to wonder how useful IFTTT is - their weather station is at an unknown location and there is NO guarantee that my yard will be rained upon at the time they detect any rain. We’re already down to 2 allowed days a week and if such rain delays kick in and rob us of a valuable allowed watering opportunity, that’s not very good. What do other folks in this area do/think? Is it just better to let Iro manage everything based on the NWS (at least we know where it is and there is a slightly better chance of conditions being the same at our home)?