Hurting2Ride

Just be cautious in your use of it that way since it would be shared between any programs that happen to trigger during the same time. Such as the one that runs a sprinkler valve to top off your pool for 5 minutes and the one that closes your garage after an hour.

Hook up a siren to it. Will probably take <24 hours before everyone remembers to walk around it... ...on a more serious but related note, what settings do you have set on the sensor and where is it located?

I purchased one of the new integrated 2491T7E thermostats and have had no issues. (But boy do I want to be able to read that remote sensor...)

I would use a similar approach as the above, with a couple of minor changes. 1) Have your "i.Alarm_is_Set" variable use 1/-1 as its on/off values. (I use "i." to specify an integer variable). This makes it simple to issue a "$i.Alarm_is_Set *= -1" which will flip back and forth between the off and on state. 2) Using the above, you can now have your IR command just run that 1 line program and you have your ability to use the key to flip back and forth between the states. If you want to do more than that, such as the suggestion to have the lamp in your bedroom blink to confirm which state you are in, change the variable to be a state variable. Add a program (or programs) that trigger on the value change to perform the actions you want. 3) Using the variable also makes it easy to do things like start the coffee machine up 15 min before your alarm is set to go off, or turn on the instant hot-water appliance to be ready for your shower.

I misread that as "SMNP" and nearly jumped out of my chair. This is what happens when you code at 3am...

I'd leave the schedule for every day and just add a "Last Run" IF statement that required more than 36 hours to have passed since last run.