I recently noticed that ST is showing a different temp reading than what my Ecobee 4 thermostat has. At times is just 1 or 2 degrees but like today it was 5 degrees difference. This doesn’t seem to be a delay in reporting to ST as I have watched for quite some time and refreshed the screen with no change in the ST reported temp. I am not having any other cloud to cloud interface issues with other devices in ST and I am able to control the thermostat in ST. So not sure if it’s on the Ecobee of ST side. Wondering if any others are having a similar experience?
Maybe the Ecobee app shows the set temperature, not the measured temperature. Change the cooling setpoint in the Ecobee app and see how it’s reflected in SmartThings.
I don’t have Ecobee so this may not be applicable.
My Honeywell VisionPro 8000 Wi-Fi thermostats use a cloud to cloud integration with the Honeywell/Resideo cloud. Even though the Resideo app always shows the current temp it was only getting updated in SmartThings every 12 hours. While there is a Refresh command it isn’t exposed in Routines.
I resorted to creating a loop in SharpTools to issue the Refresh command every 30 minutes. One of these days I’ll take the time to recreate that using the Rules capability.
@Andreas_Roedl Confirming it’s not the set point.
This was from earlier today. Note the variance was only 1 degree.
But later in the day it went up to 3 degrees.
@HalD You might be on to something. Looking at just the temp reporting history it seems to only report when the temp changes. This is also the same for humidity.
But it doesn’t explain why there is a variance throughout the day and why that variances changes.
2 Likes
If mine had behaved that way I’d have been ok with it. But before I built the workaround it only logged updates ever 12 hours.
Seems very strange it’s “drifting”. Does it look like there’s a lower limit on the refresh time?