I am struggling to understand why this code stopped working:

Temperature: 66 F
Thermostat: 68°F
Occupancy: On
Heater: Off
The Temperature (66) is less than the Thermostat setting (68) and the Occupancy Setting is ON and so the heater should turn on. But it remains off. (The T-Stat is just a virtual device, not an actual physical device.)
I created a simple test event that would send an email every time the temperature changed (every 15 minutes) and the temperature is consistently less than the T-Stat setting.
I created another test event that would only compare the Temperature with the T-Stat setting and it fails, too:

So it is the EastTrigger test that is failing.
I went into the Advanced tab for the temperature sensor and it reports the actual values as:

And for the T_Stat (which is just a virtual device) as:

So it sure seems that EasyTrigger is failing to perform correctly, although I understand it to be a very reliable and well maintained control.
I have stopped and restarted the EasyTrigger plugin and then later stopped and restarted HomeSeer. This did not correct the behavior.
I know that events are triggering when the temperature sensor changes, since I have built an event that sends me an email whenever the temperature is updated (every 15 minutes.) I am getting those.
One last comment: This all WAS working just a few days ago. I don't think I made any changes that would have cause it to fail, but I have done a lot in the last few days, so I may have been stupid in some way.
Any further thoughts?
Temperature: 66 F
Thermostat: 68°F
Occupancy: On
Heater: Off
The Temperature (66) is less than the Thermostat setting (68) and the Occupancy Setting is ON and so the heater should turn on. But it remains off. (The T-Stat is just a virtual device, not an actual physical device.)
I created a simple test event that would send an email every time the temperature changed (every 15 minutes) and the temperature is consistently less than the T-Stat setting.
I created another test event that would only compare the Temperature with the T-Stat setting and it fails, too:
So it is the EastTrigger test that is failing.
I went into the Advanced tab for the temperature sensor and it reports the actual values as:
And for the T_Stat (which is just a virtual device) as:
So it sure seems that EasyTrigger is failing to perform correctly, although I understand it to be a very reliable and well maintained control.
I have stopped and restarted the EasyTrigger plugin and then later stopped and restarted HomeSeer. This did not correct the behavior.
I know that events are triggering when the temperature sensor changes, since I have built an event that sends me an email whenever the temperature is updated (every 15 minutes.) I am getting those.
One last comment: This all WAS working just a few days ago. I don't think I made any changes that would have cause it to fail, but I have done a lot in the last few days, so I may have been stupid in some way.
Any further thoughts?
Comment