RFC: Irrigation Schedule File Format
1 post
• Page 1 of 1
RFC: Irrigation Schedule File Format
I am trying to come up with some config file format for the irrigation schedules.
Some back ground information, as you might know, I got a fancy internet based
irrigation controller, the irrigation caddy. I place the irrigation caddy behind an openwrt
based wireless router so I can use the home wireless network to access it.
The timer function provide by irrigation caddy itself is very limited. There are only 3
timers total. I can make up for that using the openwrt router. The router can send
command to irrigation caddy as if it was click "RunNow" from the Web UI. I want
to make this feature as some enhancement package for openwrt. It will be open sourced.
Before I get too fancy with the water data collection. I would like to have the some
kind of config file to describe the water schedule. Put it this way, if I can give you
the ultimate control of the water schedule, what will be the config file look like?
Here is some config file I have in mind:
Some consideration:
Some back ground information, as you might know, I got a fancy internet based
irrigation controller, the irrigation caddy. I place the irrigation caddy behind an openwrt
based wireless router so I can use the home wireless network to access it.
The timer function provide by irrigation caddy itself is very limited. There are only 3
timers total. I can make up for that using the openwrt router. The router can send
command to irrigation caddy as if it was click "RunNow" from the Web UI. I want
to make this feature as some enhancement package for openwrt. It will be open sourced.
Before I get too fancy with the water data collection. I would like to have the some
kind of config file to describe the water schedule. Put it this way, if I can give you
the ultimate control of the water schedule, what will be the config file look like?
Here is some config file I have in mind:
- Code: Select all
config 'controller' 'caddy'
option type 'irrigationcaddy'
option url 'http://caddy/'
option scale 100
config 'schedule' 'lawn'
# option disable 0
option controller 'caddy' #optional if there is only one controller
option zone1 20
option zone2 20
option days '1 5' # Mon & Fri
# option cycle '1 week'
option start '8:00 10:00'
config 'schedule' 'flower'
option zone5 10
option zone6 10
option days '2 4 6' # Tue, Thu, Sat
option start '8:00'
Some consideration:
- Can support more than one controller.
- No limit of number of schedules
- Easy to add start up time to existing schedule
- The cycle of days can be "1 week" , "2 week", "7 day", "1 month"
-

ssa - Posts: 256
- Joined: May 17th, 2010, 2:37 pm
- Location: San Jose, CA
- Grass Type: Front: TTTF Back: Random Vegetable
1 post
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 4 guests
