- watering events
- discrete rain events (METAR, NOAA, local sensor)
- failure activities
Watering events seem well handled.
Discrete rain events:
After upgrading to the most recent software, and taking advantage of NOAA forecast triggering coupled with METAR and a local sensor, I am no longer able to determine what input is causing the current rain delay.
- I have rain delay set at 4 hours, METAR set at 5, NOAA set at 2 days 60%, rain sensor is a RainBird WR2 rain/freeze
- A previous rain event is cleared shortly after 11:00pm
- Rain started shortly after 12:00am.
- HF picked up METAR precipitation of 0.00"
Mon 05-12-2014 23:00:01 - Rain Delay Time Expired - Watering Schedules Resumed
Mon 05-12-2014 23:20:02 - METAR Data updated.
Mon 05-12-2014 23:20:03 - NOAA Forecast Data updated.
Tue 05-13-2014 00:00:00 - Run Time was Increase by 14% due to NOAA Temperature option for the following scheduled stations.
Tue 05-13-2014 00:00:02 - Program 1 Start Time A - Station 6 Added to scheduler with a run time of 00:11:24 (11 minutes 24 seconds)
Tue 05-13-2014 00:00:02 - Program 1 Start Time A - Station 7 Added to scheduler with a run time of 00:11:24 (11 minutes 24 seconds)
Tue 05-13-2014 00:00:02 - Program 1 Start Time A - Station 8 Added to scheduler with a run time of 00:11:24 (11 minutes 24 seconds)
Tue 05-13-2014 00:00:02 - Program 1 Start Time A - Station 9 Added to scheduler with a run time of 00:11:24 (11 minutes 24 seconds)
Tue 05-13-2014 00:00:02 - Turned Station 6 ON (Back - North 40)
Tue 05-13-2014 00:00:02 - Insteon Device 'Front Yard Landscape Lighting' Commanded to OFF state
Tue 05-13-2014 00:00:02 - Email task failed with a 0.0.0.0 POP3 Address and a Not Assigned SMTP Address - Aborting.
Tue 05-13-2014 00:11:26 - Turned Station 6 OFF (Back - North 40)
Tue 05-13-2014 00:11:27 - Turned Station 7 ON (Back - North 20)
Tue 05-13-2014 00:20:02 - Detected Precipitation of 0.00 inches in Last Hour in METAR Data (24 Hr Running Total is 0.46 inches).
Tue 05-13-2014 00:20:02 - Rain Delay Time Active - All running programs canceled
Tue 05-13-2014 00:20:02 - Turned Station 7 OFF (Back - North 20)
Tue 05-13-2014 00:20:02 - Program 1 completed execution
I never see the local rain sensor event being logged after the rain delay kicked in for the METAR detection (the WR2 has not dried out and still shows the event). I never see the NOAA event logged (it was 70% chance of rain over the evening).
Failure Activites:
I would like the ability to squelch the local logging (and syslog when implemented); excluding non-negative admin/software events would be very helpful. Examples of events that don't need to be logged:
Tue 05-13-2014 00:20:03 - METAR Data updated.
Tue 05-13-2014 00:20:04 - NOAA Forecast Data updated.
Tue 05-13-2014 03:42:15 - RTC before Update - 05-13-114 08:42:15, RTC after Update - 05-13-114 08:42:15
Tue 05-13-2014 03:42:15 - SNTP Server Callback - Updated System Time Successfully
Wed 05-14-2014 08:00:00 - Email task failed with a 0.0.0.0 POP3 Address and a Not Assigned SMTP Address - Aborting.
The first four entries above aren't needed; if any of them failed, definitely log it. The final entry is a failed email send when email has not been setup; if it hasn't been setup, the user doesn't appear to want to receive email. Of course, logging the event of a failed email send when email has been setup does make sense.
Positive watering and insteon events should not be included in the non-negative list.