Hi nfrobertson,

Please see http://board.homeseer.com/showthread.php?p=1139908

The short of this is that I have an event that triggers when the setpoint temperature changes. It waits ten seconds, then sends me an email with the new setpoint in the body of the message using a replacement variable. Most often, it works, but on occasion, the setpoint parameter is invalid in the device (temporarily, at least), and the HS3 emailer chokes on it and goes into an infinite loop, clogging my log and bringing HS3 to its knees.

Can you check that there is code which validates that the variable loaded into the device (setpoint) is within bounds? I think this would solve this problem. Let me know if this doesn't make sense.