How can we help?


[BUG] Watering Program showing different runtimes for each display

Comments

8 comments

  • Official comment
    Avatar
    RainMachine Nicholas

    Hi,

    The difference between iOS and Web is because of the date/time issue that you observed on the Web UI. This has been fixed and there will be an available update on beta channel soon.

    As for device it will show an estimate, it's a simulation what it would need to water considering a daily program that waters zone 2 so it can differ. We have some improvements in this area under discussion too.

    Comment actions Permalink
  • Avatar
    Chris B. (Edited )

    It seems to me they all 3 show different estimates instead of the same. The Web UI and iOS are even showing different estimates, not just off on the dates.

     

    Also I noticed over the weekend my controller is watering on days I have turned off. I have watering turned off for the weekends, all my zones are still running for a few minutes even though I have it program set not to run. Plus on top of that, it was raining outside.......

     

    Sorry to say between all the confusing data, estimates and incorrect watering I am feeling I need to return this controller. Its a lot of money for inconsistency. 

    0
    Comment actions Permalink
  • Avatar
    RainMachine Nicholas (Edited )

    It won't water on the days that you didn't select. Maybe the watering log from web ui had mixed up date ?

    Same for Web UI vs iOS, they should show same values but the culprit here is Web UI which showed on Feb 28 the percentage from Mar 1. There can also be a small chance to differ if

    the weather had been updated between the time you refreshed the Web UI and the iOS app (as I've seen last update 1 minute ago on iOS) or a small rounding difference between the two.

    For watering when raining, this can happen, if the precipitation forecast amount from NOAA is less than the lost moisture from evapo-transpiration. 

     I've also created a support ticket to help you further.

    0
    Comment actions Permalink
  • Avatar
    Chris B.

    I have the "Program" set not to run on Saturday or Sunday. And it has been raining here most of the weekend so the system shows it would not water. I watched the system run myself Sunday morning even though the system showed it should not water due to rain and I had the program set not to run these days.

    0
    Comment actions Permalink
  • Avatar
    RainMachine Nicholas

    The software core won't even try to start a program that it's not scheduled for that day, no matter the moisture/precipitation deficit. This is indeed strange. Did it showed up on watering logs ? When a command to open the valves is sent is automatically logged into the database, it will say if it was scheduled or manual, but it will log as soon as valves are opened then later updated with the number of seconds that it was opened.

    0
    Comment actions Permalink
  • Avatar
    Chris B. (Edited )

    I thought it was strange myself. I see no logs at all.

     

    I have my schedule/program set to run at 3am, so I usually do not see it run. But we had a party this Saturday night and we where up past 3am, so we all saw my sprinklers going off. 

     

    The system is showing it was not suppose to run this morning due to rain, so I checked my cameras this morning and it does not look like it ran, as it should.

    0
    Comment actions Permalink
  • Avatar
    Chris B.

    I was trying to give this controller a chance. Even after notifying you of some issues, I still have plenty after the last update.

    Now, even after the last update

    • my scheduled run times are outrageous once a week for some reason (From 99 minutes scheduled to 297 minutes - I didn't change anything)
    • On top of the scheduled run time changing, the program decided 1 of my zones had too much water but the rest have not. Even though none of the zones have watered in 10 days.
    • the time on my push notifications is off since the time change (Program is set to run at 3am, my notifications tell me it ran at 1:58am)
    • and all the other issues I sent you still exists

    Sorry to say I am returning this controller.

    Good idea, but sorry to say, poor execution.

    0
    Comment actions Permalink
  • Avatar
    RainMachine Nicholas

    > my scheduled run times are outrageous once a week for some reason (From 99 minutes scheduled to 297 minutes - I didn't change anything)

    You can check which zones have watered more from Watering History.  Then check if you have a Minimum Watering Time setup that prevent some zones to water and keep postponing 

    the watering till next run. Also if the suggested time is too much, then it could be because of the choosen Sprinkler Head that has a much less Precipitation Rate than you actual sprinkler head. This could be also solved by defining a custom sprinkler head.

    > the program decided 1 of my zones had too much water but the rest have not. Even though none of the zones have watered in 10 days

    That could only happen if the Field Capacity from zones differ. Maybe that zone has a higher Field Capacity than the rest.

    > the time on my push notifications is off since the time change (Program is set to run at 3am, my notifications tell me it ran at 1:58am)

    We noticed this and it will be fixed.

    > and all the other issues I sent you still exists

    We haven't yet released the update but should be in beta channel next week.

    I will send you a private message so I can look over your controller, I think there might be some misconfigurations

     

    0
    Comment actions Permalink

Please sign in to leave a comment.