Watering started with 0% scheduled and water surplus
I noticed a strange thing this morning.
We had rain expected for noon and it actually rained around noon.
My lawn program was scheduled to start at 7:00. I did not expect it to start due to the expected precipation.
I actually checked in the app and wondered why it showed me that the next cycle would start today at 7, but still it showed 0% watering.
At 7 the RM started the lawn and I manually had to stop it. The webinterface showed this:

As you can see, the watering is at 0%, there is no icon for adaptive skip though. The watering times are total garbage, runtime is always the same for both zones.
Any ideas why this happened?
-
What does the watering history say after it had watered ? Can you post a screenshot from the web interface for the event as shown in watering history ?
The only thing that I can think about is that before the program is started the weather is fetched again and maybe it has different from the previous forecast.
-
Hi Nicholas,
I'll attach a screenshot from the watering history. But I stopped the watering as soon as I saw that it was running.
I also still have the log I pulled from the machine when the event occured. Maybe that helps.
Baseline runtime for the zones would be 32:43.

In the log, something looks odd with the watering start/stop, this is what a "regular" watering looks like in the log:
2021-07-04 06:53:53,713 - INFO - rmParserManager:509 - ** Forcing parsers run because program 2 will start in 420 seconds
2021-07-04 06:54:05,576 - INFO - wunderground-parser:87 - WUnderground: station data retrieved for IERLEN55
2021-07-04 06:54:05,584 - INFO - wunderground-parser:95 - WUnderground: forecast data retrieved.
2021-07-04 07:00:02,310 - INFO - rmProgramScheduler:262 - Program 2 added to watering queue and/or watering history
2021-07-04 07:00:02,707 - INFO - rmProgramSchedulerWatering:250 - Watering - starting zone: (uid=None, pid=2, zid=2, ust='2021-07-04 07:00:01', rst='2021-07-04 07:00:02', ud=3926, md=0, rd=0, aw=-3.2956292034611732, flag=12, manual=False, running=True, flowClicksDelta=0)
2021-07-04 07:00:04,233 - INFO - rmProgramSchedulerWatering:295 - UpdateZone available water: -3.29562920346
2021-07-04 07:00:04,425 - INFO - rmProgramSchedulerWatering:150 - Watering - zone finished: (uid=None, pid=2, zid=2, ust='2021-07-04 07:00:01', rst='2021-07-04 07:00:02', ud=3926, md=0, rd=0, aw=-3.2956292034611732, flag=12, manual=False, running=False, flowClicksDelta=0)
2021-07-04 07:00:04,437 - INFO - rmProgramSchedulerWatering:250 - Watering - starting zone: (uid=None, pid=2, zid=3, ust='2021-07-04 07:00:01', rst='2021-07-04 07:00:04', ud=3926, md=0, rd=0, aw=-3.2956292034611732, flag=12, manual=False, running=True, flowClicksDelta=0)
2021-07-04 07:00:05,915 - INFO - rmProgramSchedulerWatering:295 - UpdateZone available water: -3.29562920346
2021-07-04 07:00:06,103 - INFO - rmProgramSchedulerWatering:150 - Watering - zone finished: (uid=None, pid=2, zid=3, ust='2021-07-04 07:00:01', rst='2021-07-04 07:00:04', ud=3926, md=0, rd=0, aw=-3.2956292034611732, flag=12, manual=False, running=False, flowClicksDelta=0)
2021-07-04 07:00:06,290 - INFO - rmProgramSchedulerWatering:160 - Watering - program finished: programId=2 flag=12
2021-07-04 07:30:02,769 - INFO - rmProgramScheduler:262 - Program 1 added to watering queue and/or watering history
2021-07-04 07:30:03,096 - INFO - rmProgramSchedulerWatering:250 - Watering - starting zone: (uid=None, pid=1, zid=4, ust='2021-07-04 07:30:01', rst='2021-07-04 07:30:03', ud=2003, md=0, rd=0, aw=0.3705325007459509, flag=6, manual=False, running=True, flowClicksDelta=0)
2021-07-04 07:30:04,683 - INFO - rmProgramSchedulerWatering:295 - UpdateZone available water: 0.370532500746
2021-07-04 07:30:05,098 - INFO - rmProgramSchedulerWatering:150 - Watering - zone finished: (uid=None, pid=1, zid=4, ust='2021-07-04 07:30:01', rst='2021-07-04 07:30:03', ud=2003, md=0, rd=0, aw=0.3705325007459509, flag=6, manual=False, running=False, flowClicksDelta=0)
2021-07-04 07:30:05,304 - INFO - rmProgramSchedulerWatering:160 - Watering - program finished: programId=1 flag=6And this is what happened when the issue occured:
2021-07-08 06:53:42,445 - INFO - rmParserManager:509 - ** Forcing parsers run because program 2 will start in 420 seconds
2021-07-08 06:53:42,762 - INFO - netatmo-parser:299 - Getting data from https://api.netatmo.com/api/getstationsdata
2021-07-08 06:53:43,003 - INFO - netatmo-parser:299 - Getting data from https://api.netatmo.com/api/getmeasure
2021-07-08 06:53:43,217 - INFO - netatmo-parser:299 - Getting data from https://api.netatmo.com/api/getmeasure
2021-07-08 06:53:57,714 - INFO - wunderground-parser:87 - WUnderground: station data retrieved for IERLEN55
2021-07-08 06:53:57,722 - INFO - wunderground-parser:95 - WUnderground: forecast data retrieved.
2021-07-08 07:00:00,615 - INFO - rmProgramScheduler:193 - Zone 1001 is not simulated won't carry available water
2021-07-08 07:00:00,628 - INFO - rmProgramScheduler:193 - Zone 1002 is not simulated won't carry available water
2021-07-08 07:00:00,921 - INFO - rmProgramScheduler:262 - Program 2 added to watering queue and/or watering history
2021-07-08 07:00:01,486 - INFO - rmProgramSchedulerWatering:250 - Watering - starting zone: (uid=None, pid=2, zid=1001, ust='2021-07-08 07:00:00', rst='2021-07-08 07:00:01', ud=5, md=5, rd=0, aw=0, flag=0, manual=False, running=True, flowClicksDelta=0)
2021-07-08 07:00:06,521 - INFO - rmProgramSchedulerWatering:150 - Watering - zone finished: (uid=None, pid=2, zid=1001, ust='2021-07-08 07:00:00', rst='2021-07-08 07:00:01', ud=5, md=5, rd=5, aw=0, flag=0, manual=False, running=False, flowClicksDelta=0)
2021-07-08 07:00:06,532 - INFO - rmProgramSchedulerWatering:250 - Watering - starting zone: (uid=None, pid=2, zid=2, ust='2021-07-08 07:00:01', rst='2021-07-08 07:00:06', ud=3926, md=2404, rd=0, aw=0, flag=0, manual=False, running=True, flowClicksDelta=0) -
The line next to 1001 (which is Master Valve Start) it says that machine calculated duration was 2404 (seconds). It can only mean that the forecast/observation changed and it has recomputed the duration, but the only times I've seen such big corrections were when RainMachine didn't water due to forecast saying lots of rain/precipitation and the next day observed data from NetAtmo/WUnderground said it didn't actually rain. Unsure if this is applicable here but please keep this thread update if this happens again, we will need to request an access token for your device and look into weather data.
Please sign in to leave a comment.
Comments
3 comments