ELK Rule List

slowmo

Member
Does anyone have a comprehensive list of creative Elk M1 Rules? I’m looking for something a little beyond what is on the Elk website. Their website offers good examples, but I’m looking for other creative ways to used Elk rules. Every now and then I'll come across a rule searching the forum but it would be nice to have a comprehensive list.

For example, with help from Elk’s support team, I am able to control my attic fan based on the actual attic temperature and the difference between the attic temperature and outside temperature. In this example, whenever the attic temperature is greater than 95 Deg and the outside is cooler by at least 10 Deg. then the attic fan is turned on for 10 minutes.

ATTIC FAN – STEP #1
WHENEVER EVERY 30 SECS
THEN SET Temp (Counter 1) TO TEMPERATURE OF Outside (Zn 10)
THEN TURN OUTPUT 200 ON FOR 2 SECS

ATTIC FAN – STEP #2
WHENEVER OUTPUT 200 STATE IS TURNED OFF
THEN ADD 10 TO Temp (Counter 1)
THEN TURN OUTPUT 201 ON FOR 2 SECS

ATTIC FAN – STEP #3
WHENEVER OUTPUT 201 STATE IS TURNED OFF
AND Attic (Zn 1) ACTUAL TEMPERATURE IS GREATER THAN Counter01 (Counter 1)
AND Attic (Zn 1) ACTUAL TEMPERATURE IS GREATER THAN 95 DEG. F. (35 DEG. C.)
THEN TURN Attic Fan (Out 3) ON FOR 10 MINS

Thanks,
Scott
 
Great question ! I have found writing intricate rules for the ELK M1 can be tricky . I also have looked at Elk's website and always look here and will make multiple attempts at implementing the rule but will still end up calling Elk's tech support. They have been very helpful, however many times that I want to work on my rules can be later at night or weekends. You guys know exactly what i'm referring to. Maybe instead of having a list of rules or a thread to one particular rule writing dilemma There could be a permanant location just for M1 Rules .
 
I missed the thread above... guess I'll need to include keywords "vibrator" and "bed" into my seach for Elk rules.
 
THIS thread was started, but it didn't generate a lot of response... :(

This is disappointing, and it might be worthwhile to consider some of the reasons.

- It's simply hard to remember, after you have struggled to find a solution, to take the next step and post it so that somebody else might benefit from your work.

- Sometimes, small breakthroughs (after you have achieved them) seem obvious and not worth posting.

- Rule solutions can sometimes be so specific that it is pointless to share (e.g. an oddball HVAC rule set).

- Do you suppose that some sort of organization or taxonomy for classifying rules would encourage contributions (e.g. "Keypad Functions" "Task Management")?

Based on this thread I contributed a "lesson learned" to the Rules Programming thread, but frankly I doubt it's of much value (see second point above).

Dave (Lagerhead formerly davidvind)
 
Spanky,
Can you ask Elk Tech Support to contribute as well... I know it is a pain, but I'm sure well worth the PR.

Thank, Scott
 
THIS thread was started, but it didn't generate a lot of response... :(

I can see where a thread asking for unique M1 Rule may not generate a lot of responses for various reasons as already cited; however, rather than asking for unique M1 rules may be the question is “how are you using M1 rules?” For example, my kids are forever leaving the garage door opened in the evening. “Maheda” as my kids fondly refer to our M1, reminds them to “Please close garage door.” I have another rule that alerts me when the deer are in the backyard, so I can chase them out. Additionally, I work late into the night so the M1 turns on/off key lights (upb) so I don't stumble through the house while going to bed.
 
Back
Top