Ok well deleted that thing and re-added it. Also added back the thermostats. I did a network rediscovery too.
Great, all three show as learned in on AC power and an install date of today. You should be good to set up schedules.
Thanks Jason.
I’ll do that and watch what happens over the weekend. Hopefully it all “works as designed” after all this 
Well everything was good until it wasn’t.
This afternoon I check the downstairs thermostat and see the temp is set for a value that doesn’t exist at any point in my schedule and certainly doesn’t match the value that it should be at 1:31 pm local time.
I do have a sensor left open rule that kicked in this morning but I also see the “restoral” log item which should just return things back to the normal schedule.
So now what?
Can definitely confirm that the sensor left open rules are only working one way, when the sensor is left open, and do not restore the normal schedule when the sensor is closed despite the activity log showing the “restoral” trigger firing.
Can definitely confirm that the sensor left open rules are only working one way, when the sensor is left open, and do not restore the normal schedule when the sensor is closed despite the activity log showing the “restoral” trigger firing
Delete and recreate those left open rules. Still an issue?
Just so I can look back and verify, what was the temperature the downstairs stat was set to?
Jason,
The night time cool setting should be 78 and then the normal home setting should be 79. The away setting should be 81.
There were two sensor left open events this morning for the downstairs thermostat. One of them recovered as it should, the second one did not and caused the thermostat to be set too high and I manually had to change it back to what it should.
See attached:
That does seem to be the issue. Looking at your history I see the panel reports that the thermostat left open rule resolved the first time, but for the second left open event for the Front Door sensor, the restoral shows in ADC history as a standard sensor left open restoral. Not the thermostat rule.
First try deleting the left open overrides. Wait 10 minutes. Recreate them and save.
Either the rule seems to have a bug which is causing the failure or the panel Z-wave has an issue. All the Z-wave devices show as having good link quality and the thermostats are not in power save mode anymore so there should be no issue with signaling.
Jason, I don’t see a way to delete those rules. I can deactivate them or alter them but they’re built in rules that don’t show me a delete option that I can see. I toggled them to off and will wait a bit and then toggle them again. Short of that I’m not seeing anything else I can do with them.
Jason, I followed your suggestion from the other thread talking about sensor left open rules and thermostats.
I turned off all the sensor left open rules. I modified them as well. I let everything sit for about 45 mins then recreated those rules again. That was probably around 4 PM here, so plenty of time for them to propagate back down to the panel and thermostats.
At 6 PM, the downstairs thermostat is supposed to go from 81 to 79. Instead, it went to 82 degrees. This wasn’t due to a sensor left open, as that hasn’t happened since I recreated the rules, but this is exactly the behavior I’ve been seeing. It seems that the sensor left open rule not firing right is a symptom of a greater issue relating to thermostats and scheduling as I’m seeing these malfunctions in both scenarios.
As you said, and I looked as well, the Zwave network is reporting all connections as healthy and strong. Something else is going on here.
See attached for the rule and the log notification I got.
Same thing at 10 PM for the next scheduled change for the downstairs thermostat. The temp went to 81 instead of 78. The schedule is completely out the window at this point; temperature changes are happening at the scheduled times, but the temp is being set wrong. In both of these instances I had to set the desired temp either using the app or the website.
Thank you for the follow ups and additional details on testing. I am forwarding all of these details to Alarm.com and opened up a ticket with them to investigate.
I am assuming this is not the case, but just to confirm 100%, no one else at the home may have physically changed the thermostat at those times? A manual adjustment would override that section of the schedule.
Thanks Jason. To answer your question, I’m confident that no one manually changed the thermostat. I was in the same room as it is, and I had full view of the thermostat, my girlfriend, my dogs and my sneaky cats 
Same story this morning btw. Something is triggering a temp change at the time my schedule usually would, it’s just not being set to the expected temps.
Note that I haven’t seen this behavior on the other two thermostats in the house since they were all reset, but there also hasn’t been any “sensor left open” rules triggered in those parts of the house so if that’s the catalyst for things going awry, it’s only happened downstairs so far.
A quick update: I noticed that last night the schedule worked normally on all three thermostats. Also this morning, had the usual sensor left open event downstairs and when it recovered, the thermostat was set back to its normally expected values.
Curious what’s changed on the ADC side.
I haven’t been updated of anything yet but the ticket was submitted through our primary ADC rep
OK well maybe they’re working on stuff because today has been “working as designed.”
Aaaaaand this morning it was totally whacked out again with the downstairs thermostat set to 84 degrees…
Did you have one or more sensor left open overrides before that which may not have resolved?
Yes, same symptom as we discovered previously.
Here’s the activity log which confirms:
There was no subsequent restoral event.
Alright, I am updating ADC with the additional example
Any updates on this? It’s still malfunctioning.