I’m having an issue that started a day or two ago with this energy saver rule.
I had it set up to turn off my thermostat if any of my contact sensors were left open for over an hour. It has been working 100% fine up until this week, where now it won’t turn off the thermostat after the windows/doors have been left open for that long.
I tried all the troubleshooting tips in this post: Sensor Left Open Energy Saver Rule issue (so, restarting the panel, turning the rule off and editing the sensors included in the rule, leaving it off for more than 10 minutes, re-enabling the rule) and still it doesn’t work.
For troubleshooting purposes I changed the rule to turn off the thermostat if any of them are left open for 1 minute or longer. I also created a rule to notify me if any contact sensors were left open for 1 minute or longer, and those come through fine, so I know the panel is detecting the sensors being open for that long.
You can see in my Activity that there are plenty of those events occurring, it’s just not handling the thermostat rule for some reason.
Alright, it seems to be working now. It wasn’t at first, but after doing multiple updates to the rule it seems to be consistent. I’ll update tomorrow whether it’s still working or not.
So, the rule has started “malfunctioning” again today.
After everything we did the other day, I set up my rule for turning off the thermostat if any sensor is left open for 30+ minutes. It was working fine up until this morning.
I opened my windows for about 2 hours and realized I never got a notification about the thermostat being turned to “off.” I checked, and sure enough it hadn’t.
I tried disabling/changing the Energy Saver Rule to send an update to the panel on it, and the rule worked once after I did that. But now it’s not working again.
Also it did something pretty odd just now when I was testing it – I left a window open for a while (about 1.5 hours) and noticed the AC was on (so the rule didn’t work) and when I closed the window it gave the Thermostat Restoral notification even though the thermostat had never been turned off. You can see it in the activity for my panel.
Anyway, is there something else to do so we can try to fix this for good? I feel like I’m having technology problems with this system every week.
I tried disabling/changing the Energy Saver Rule to send an update to the panel on it, and the rule worked once after I did that. But now it’s not working again.
Do you recall the most recent time this rule worked as intended?
Well, as I said it was working since we last troubleshooted up until this morning. So in that sense, yesterday morning was the last time I had an event that would have turned the thermostat off per this rule, and it was working then.
The last time it was working week after week and not having any periodic issues was maybe 2 days before this entire post started. So like 7-8 days ago?
Its possible the TSTAT isnt getting the message. How far from the panel is the TSAT?
Have any changes been made to the environment? Adding/moving furniture appliances, mirrors etc. in the area? Were any Z-Wave devices removed from the network?
As a test, disarm the system then power cycle the panel. Leave it off for a couple minutes, then power it back up.
Once it has rebooted, wait about 5 minutes, then run a Z-Wave network rediscovery. Afterwards, test the rule for resolution.
Have any changes been made to the environment? Adding/moving furniture appliances, mirrors etc. in the area? Were any Z-Wave devices removed from the network?
No changes to the environment. I have one malfunctioning sensor that I’m working on getting a replacement for, which I unlearned from the Panel, but that was about 2 days ago. Otherwise, no Z-wave changes.
A counter to this idea that the thermostat is not getting the message is that I can send a thermostat mode/fan/temp change via the Alarm.com app and the thermostat takes the change immediately. So the Panel is definitely communicating fine with it.
I’ll try the turn off / reboot / network rediscovery and report back.
It worked yesterday after the troubleshooting, and it’s working this morning as well. Fingers crossed it continues to work. As always, I’ll keep you posted if anything changes.