#1) Yesterday my Mini 'hung' [I can't remember the number of years since that has happened, if ever] and of course it happened during a drip irrigation cycle. The only reason I noticed an issue was that my iPad screen went black, with the message "unable to connect to Indigo server", and my remote client disconnected and would not reconnect.
Thankfully I was at home, but by the time I figured out what was going on and rebooted the Mini my potted plants were aquariums. Had I not been home I would have water front property.
#2) Today I noticed that during a sprinkler cycle
- Code: Select all
Schedule _next_zone_1_Irrigation [sprinkler]
Sprinkler Turning "Irrigation [sprinkler]" zone 2 on for 28.00 minutes
Error "Irrigation [sprinkler] - [2] Pool Left" on; send failed (no acknowledgment)
The irrigation actually went to zone 2, but all interfaces displayed zone 1, even as zone 3 started. I corrected the issue by using the 'get valve status' button in the client.
I proceeded to create a CP element that I could press to correct the valve display. This is when I discovered that the sprinkler control action includes everything EXCEPT 'get valve status'.
So, who has some ideas? Off the top of my head I would like:
- A CP element to activate 'get valve status' manually.
- A trigger that on every zone change would 'get valve status' after ±15 seconds, healing itself if there were an error.
- A solution for rebooting your server manually and/or automatically remotely. It would be nice if the computer could just sense the problem and reboot itself. The biggest problem with a 'hang' is no alerts are sent so if you were away from home you would have no idea there was a problem like in a power failure.
Indigo 5.1.10
EZ Flora's