Will elapsed time be a valid trigger to make an alarm off?
dave
Originally posted by Bryan Mayland:
<BLOCKQUOTE class="ip-ubbcode-quote"><div class="ip-ubbcode-quote-title">quote:</div><div class="ip-ubbcode-quote-content">Originally posted by D Peart:
Hopefully these triggers will allow actions like changing the pit temperature as well. That is one thing I've wanted for a long time.
I'm holding back talking about the how the alarm works for a bit to see if any new ideas float out, but yeah you can change settings from the alarm trigger like:
<pre class="ip-ubbcode-code-pre">
# Lower SetPoint to 180F on alarm
lmclient LMST,sp,180
# Or do something more complicated such as lower the pit temperature by 20%
# and set another alarm to go off in 10 more degrees, until the new alarm
# temperature reaches 200 degrees, at which point send an email and lower setpoint
# with the current status
NEWSET=$((SETPOINT*4/5))
NEWALARM=$((PROBE1_TEMP+10)
if [ $NEWALARM -lt 200 ] ; then
lmclient LMST,sp,$NEWSET
lmclient LMST,al,,,,$NEWALARM
else
lmclient LMST,sp,50
mail -s "[HeaterMeater] Cook Over"
chunkylover53@aol.com << EOF
This message is to inform you that your HeaterMeter at $HOSTNAME
has completed cooking at $DATE $TIME.
$PROBE0_NAME: ${PROBE0_TEMP}F
$PROBE1_NAME: ${PROBE1_TEMP}F
Share and Enjoy!
EOF
fi
</pre> </div></BLOCKQUOTE>