SAFETY 1: A temp sensor in true error will give either -196, >100, or something not repeating values. So, that error value should be the SAFETY determination of whether what it's reporting is any good.
SAFETY 2: Minutes can't work for latest update unless there's a workaround for the 60 min vs 0 min situation. Maybe need to use Unix time +/1 to achieve that.
SAFETY 3: Send notification and/or log (don't shut off) on a room long to change temperature. Need to identify which room it is!
!!! Alright... at the end of the day, I'm just trying to keep the HVAC from running too long at once, because that might be a sign of an error of any kind. I think cooling mode running for more than 60 minutes is a strange event. The "are temps changing" values are interesting for log-watching but there are just too many variables to allow them to shut off the air conditioner.
As to why LK's room is struggling... on the hottest days, maybe her vent needs to be opened wider.
A bit of a new way of thinking:
!!! Alright... at the end of the day, I'm just trying to keep the HVAC from running too long at once, because that might be a sign of an error of any kind. I think cooling mode running for more than 60 minutes is a strange event. The "are temps changing" values are interesting for log-watching but there are just too many variables to allow them to shut off the air conditioner.
As to why LK's room is struggling... on the hottest days, maybe her vent needs to be opened wider.