(Updated a little, on Mon., Nov. 13th).
Summary of observations when running one Flex Daily schedule:
-
When you connect a freeze sensor to Iro terminals S1 and SC and then configure sensor 1 as a Rain sensor (no choice of choosing freeze), nothing’s going to happen. No real time messages, no text messages, etc. No implementation of actual freeze sensing either. The key point here is you must cycle power to the Iro2 afterwards. (Maybe Rachio designers assumed every owner would turn off power to the Iro2 before connecting something to S1 and SC. I didn’t - it’s only 24 VAC.) It’s only the first power cycle that produces any diagnostic info.
-
Rachio cloud processing stops using remote weather station data (for freeze protection) when Sensor 1 is configured to be a Rain sensor.
-
Current Moisture Balance is being appropriately maintained.
-
The Iro2 checks at the time of start for every day’s FD schedule for a presence of a sensor and what mode it’s in. My open circuit simulation was picked up at the start of each day’s FD schedule.
Conclusions:
-
Absolute freeze protection does work if you’re willing to connect a freeze protection device to terminals S1 and SC. Some devices are set at 37 degrees, some at 39 degrees. (I’ll do this with my automation system, while monitoring outside temp). You must connect a freeze protection device (wired or wireless) to eliminate otherwise possible situations where you won’t have freeze protection but think you do.
-
There is no other means of absolute freeze protection .
-
Nothing works with respect to Iro2 options for emails, text messages. Status information via app.rach.io is kept up to date on existing / non-existence of freeze sensor after the power cycle (above) is done.
-
Connection of a freeze sensor doesn’t get activated without going through a power cycle.
Let me repeat: All of this is for Flex Daily schedules only, and where only one exists.
Best regards,
Bill