I’m a little at my wit’s end here. I had a few routines set up for controlling my Honeywell thermostat that I set up months ago. However, with my heat exchanger acting up, I needed to fine tune the routines to manage EM Heat and Cooling instead of Heat, EM Heat, and cooling. While using the app, I could set the outdoor temperature ranges in Fahrenheit, but the app outright refuses to set the thermostat temperature in anything but Celsius.
While having to do a conversion is certainly an inconvenience, it does seem like SmartThings can’t decide what to do with the mixed up standards. With the EM Heat set to 20C, the thermostat fluctuates my held heating temperature between 62F and 68F. I can’t get a steady hold whatsoever.
I’m also no convinced that the app is actually utilizing the outdoor temperature to trigger the routine. It was 41F outside this morning, and the EM Heat was supposed to kick on at any temperature at or below 55F. Needless to say, it did not. And no no matter what I set the routine at, it won’t hold a temp at 68F.
This was stable the last time I set this up months ago. I don’t know if an update down the line broke something, or if there is some conflict in the chain, but this is starting to cause an issue.
Thanks in advance.
I’ve have the same problem for months, and have opened several tickets because ST keeps closing them saying it will be resolved in the next app release, which of course never happens.
I suggest submitting your own ticket and reference my ticket in yours. It’s #1334103.
@SmartThings @brad_st I’ve sent screen shots, log files, and everything else except mail my phone to support. I keep being told it’s fixed in the next release, engineers know of the issue, etc. If so, why keep asking me for the same files and screenshots? Any help would be greatly appreciated.
Thanks for the reply, sorry you’re having the same issue. I’m really not pleased to hear that it’s seemingly being swept under the rug like this.
I don’t know if it’s a conflict between SmartThings and Honeywell, or if it’s because they’re gearing up for this switch to Matter, but I would’ve hoped they’d have fixed this by now.
I just looked at my thermostat history, and confirmed that the software doesn’t know what to do with my forced Celsius inputs. Where I’m forced to set it to 20C, the history lists my heating temp as 20F.
I’ve been on the fence about switching to something else due to lapses in SmartThings stability. Lapses in lighting is frustrating, but the heating and cooling of my house is another level entirely. If this doesn’t get fixed soon, I’ll likely have to swap over to something like Home Assistant.
I just got this reply from Smartthings support yesterday:
We would like to inform you that our Developing team is working on this issue.
We got an update from them that this behavior was resolved in a previous app version but appears to be back. We were able to reproduce this temperature behavior and re-escalate to developers.
We are continuing to work on a resolution for this behavior and will provide an update as soon as possible.
We apologize for the inconvenience caused.
Meanwhile, your patience is highly appreciated.
Please feel free to write back to us for any further queries and concerns.
Well that’s a good start at least.
In the meantime, I seem to have found a temporary workaround. I loaded up SmartThings on my Galaxy Tab instead of my S21 Ultra, and it didn’t have the same issue. In fact, the app even listed which standard it was using right in the menu. Instead of simply “68” it was “68F” or “20F” instead of “20”.
So far, it’s holding. I guess for the time being I’ll have to do all of my routines and fiddling on the Galaxy Tab instead of the phone.
Here’s hoping for both of us (and everyone else who’s having this issue)!
Hey that’s a good idea. I also have a Tab. I’ll give that a try when I get home today.