- This topic is empty.
September 3, 2014 at 1:55 pm #23145
Hi. I have Open Sprinkler v 2.1s with firmware 2.0.8. using App version 1.1.8 on Android tablet. When I edit stations for one of my programs (which I use for outdoor lighting control), I tick the box “Ignore rain” for this zone, S01. I submit this to save it, and check that it is saved, and it is. I then set a rain delay of 48 hours and if I go into program preview the block for this zone to run is now red (it was green), and the station does not run. This is repeatable, I made a second program using different zones, ticked ignore rain, but if rain delay is activated the zones that are supposed to ignore the rain do not. At least this is what I expected to happen. I need the watering stations to react to rain, either sensed or manualy entered delay, but any other use should ignore it.
I also set the rain sensor option on, and unticked the N.O. sensor option. With no sensor attached Open Sprinkler noted “rain detected” as expected. If I then look in program preview all stations, in all programs, remain set to run? This is with or without the “ignore rain” tick box checked, I tried both ways, checking carefully that changes were saved. Any insight you can give me would be appreciated, thanks, KeithSeptember 3, 2014 at 3:29 pm #28055
Well, I will first say you are right the program preview is not accounting for ignore rain delay on stations. I will fix this today but this is a purely visual issue and does not affect what the firmware does. Also, my program preview is only marking red for rain delay not sensor. I will also get this fixed today.
In regard to the actual station not running due to rain delay being set on an ignore rain station is a firmware issue. I will test this today and try to identify the cause.
Thanks for the feedback!
Update: If your stations have a space in them then no changes may be saved. This is a bug in 2.0.8 and might be preventing the ignore station setting from being saved properly.September 3, 2014 at 10:50 pm #28056
This has been fixed in the app and will be reflected in the next update.
- You must be logged in to reply to this topic.