I need help displaying the high and low values for temperature as measured at a ELK-M1KP keypad. I have logic that does this very reliably for zone temperatures measured with ELK-M1ZTS sensors but the keypad temperatures have been very quirky:
1) If the temperature is saved to a counter, the counter is the measured temperature plus 40 degrees
2) If the current temperature is compared to a counter, the results are erratic, with 1-2 degrees worth of instability.
Using the rules below, it is not unusual for the low value to wind up higher than the high value. The same logic (without the 40 degree offset for display) works perfectly with my ELK-M1ZTS zone temperatures.
Is there some trick I am missing? Thanks for any suggested solutions.
Nick
I use the following rules to update hi and lo values for the keypad sensor
WHENEVER EVERY 1 MINUTE
AND Dining Room (KP 1) ACTUAL TEMPERATURE IS LESS THAN DR Lo (Counter 6)
THEN SET DR Lo (Counter 6) TO TEMPERATURE OF Dining Room (KP 1)
WHENEVER EVERY 1 MINUTE
AND Dining Room (KP 1) ACTUAL TEMPERATURE IS GREATER THAN DR Hi (Counter 5)
THEN SET DR Hi (Counter 5) TO TEMPERATURE OF Dining Room (KP 1)
I use the following rules to display hi and lo values for that sensor
WHENEVER KEY F5 ON KEYPAD1 ACTIVATES
AND F5Context (Counter 64) IS EQUAL TO 1
THEN SUBTRACT 40 FROM DR Lo (Counter 6)
THEN DISPLAY "Local lo % CTR6 % F" IN House (Area 1) FOR 30 SECONDS, [*] CLEARS
THEN ADD 40 TO DR Lo (Counter 6)
THEN SET F5 Context (Counter 64) TO 2
WHENEVER KEY F5 ON KEYPAD1 ACTIVATES
AND F5Context (Counter 64) IS EQUAL TO 0
THEN SUBTRACT 40 FROM DR Hi (Counter 5)
THEN DISPLAY "Local hi % CTR5 % F" IN House (Area 1) FOR 30 SECONDS, [*] CLEARS
THEN ADD 40 TO DR Hi (Counter 5)
THEN SET F5 Context (Counter 64) TO 1
WHENEVER KEY F5 ON KEYPAD1 ACTIVATES
AND F5Context (Counter 64) IS EQUAL TO 2
THEN SET F5 Context (Counter 64) TO 0
Note: there are additional rules to reset the high and low and context counters at midnight and at system startup
1) If the temperature is saved to a counter, the counter is the measured temperature plus 40 degrees
2) If the current temperature is compared to a counter, the results are erratic, with 1-2 degrees worth of instability.
Using the rules below, it is not unusual for the low value to wind up higher than the high value. The same logic (without the 40 degree offset for display) works perfectly with my ELK-M1ZTS zone temperatures.
Is there some trick I am missing? Thanks for any suggested solutions.
Nick
I use the following rules to update hi and lo values for the keypad sensor
WHENEVER EVERY 1 MINUTE
AND Dining Room (KP 1) ACTUAL TEMPERATURE IS LESS THAN DR Lo (Counter 6)
THEN SET DR Lo (Counter 6) TO TEMPERATURE OF Dining Room (KP 1)
WHENEVER EVERY 1 MINUTE
AND Dining Room (KP 1) ACTUAL TEMPERATURE IS GREATER THAN DR Hi (Counter 5)
THEN SET DR Hi (Counter 5) TO TEMPERATURE OF Dining Room (KP 1)
I use the following rules to display hi and lo values for that sensor
WHENEVER KEY F5 ON KEYPAD1 ACTIVATES
AND F5Context (Counter 64) IS EQUAL TO 1
THEN SUBTRACT 40 FROM DR Lo (Counter 6)
THEN DISPLAY "Local lo % CTR6 % F" IN House (Area 1) FOR 30 SECONDS, [*] CLEARS
THEN ADD 40 TO DR Lo (Counter 6)
THEN SET F5 Context (Counter 64) TO 2
WHENEVER KEY F5 ON KEYPAD1 ACTIVATES
AND F5Context (Counter 64) IS EQUAL TO 0
THEN SUBTRACT 40 FROM DR Hi (Counter 5)
THEN DISPLAY "Local hi % CTR5 % F" IN House (Area 1) FOR 30 SECONDS, [*] CLEARS
THEN ADD 40 TO DR Hi (Counter 5)
THEN SET F5 Context (Counter 64) TO 1
WHENEVER KEY F5 ON KEYPAD1 ACTIVATES
AND F5Context (Counter 64) IS EQUAL TO 2
THEN SET F5 Context (Counter 64) TO 0
Note: there are additional rules to reset the high and low and context counters at midnight and at system startup