This is getting so ridiculous from Sensi’s end that I sold both my thermostats…
Thanks for supporting us this far @Kirk_Brown
This is getting so ridiculous from Sensi’s end that I sold both my thermostats…
Thanks for supporting us this far @Kirk_Brown
Contemplating posting mine on ebay also and moving on… I’ll email their support first.
So I assume this is officially dead? Was nice while it lasted. Stupid me just bought another Sensi.
Well seems like it, Kirk said he’s out of luck trying to get through it since they need official login authorization page to enable integration.
I’m just going to setup an IFTTT recipe for my webCoRE automation …
Slightly related to the API change… this week my Sensi thermostat started running schedules I never created. I now see a schedule for Cool, Heat, and Auto which have checkmark indicators and I cannot uncheck them. I did try to change the Schedule Type in the app to No Schedules… but it didn’t seem to prevent the mystery schedule(s) from commandeering the temperature. I sent an email to Emerson for help. Anyone else seeing this issue?
Not having this problem right now. But just half a month ago my thermostat and app started to act unsteadily.
From time to time it disconnected from my WIFI which it hadn’t been for over a year. Then I could not update the temperature and on/off status form my app, it often jumped back to some kind of default setting such as 25 cooling with schedule running (I didn’t let schedule run).
Then I tried pulling out batteries at the back and tried reinstalling it (like setting it up for the first time) and boom it started working again.
So you can try reinstalling it, or even resetting it. I guess their change to the new API hinders existing thermostat settings, shame on them…
Yes. This very thing is happening with my Sensi schedules. It’s quite annoying. I wasnt too worried because I figured it wouldn’t follow “Hear” or “Auto” schedule unless it was set to it, but it’s not following my “cool” schedule either.
Did you get any feedback from Sensi?
I haven’t heard from them yet. It looks like setting mine to “no schedules” did eventually prevent the schedules from running. Mine was running the cool schedule that had been created without my knowledge.
SENSI Thermostat Recall
Just received notification via Amazon:
Emerson Thermostats Sensi Smart Thermostat, Wi-Fi, UP500W, Works With Alexa
More details, including how to determine if your purchase is impacted and what you should do next can be found in the following notification:
If you made this purchase for someone else, please notify the recipient immediately and provide them with the information concerning these issues.
UPC/SKU: B00HHE6CW2
Found this thread looking for compatibility for some friends who just bought a condo.
Kudos above for the recall notice. Did anyone follow along for the “Fix”
This is some serious B.S.
Ofcourse they totally left out the fact this must now run off batteries from now on, I assume. Wonder how long they last?
Thank you for finally adding integration with the Sensi thermostat!
I was able to add my two Sensi thermostats to my SmartThings (via the new app) but in about an hour later, I noticed it said they were offline. I went and deleted it, and now I’m unable to add them back.
When I try and add a new device and select Sensi, it says it’s connected but it doesn’t find my two thermostats anywhere.
Help!
I wonder if you can remove the integration and add it back. to remove, go to the three bars in the upper left of the screen, select settings (the cog), go to connected services and swipe left on sensi and delete. then go through the previous steps you used earlier to add it back.
Thank you, that did it!
From the main menu, I clicked in the hamburger.
Then click on the cog as you said.
Then click in connected services and Sensi was listed. Selected it, and it showed my two thermostats. I removed the Sensi service and re-added it which prompted me to login again to Sensi to establish the connection and that did it.
Has anyone had any luck with the Sensi integration and triggering automations?
I’ve got one set up to trigger based off humidity % + presence sensor + time of day, but it never triggers.
Is it a standard thing to “uninstall and reinstall” in ST?
I think it’s because of how often sensi sends its status of the thermostat to ST. When you go into thermostat view and check the history of your thermostat’s temperature and humidity, you can see it updates quite infrequently, basically around 6 hours each time.
I noticed recent 2 days there’s more frequent updates, but it’s only when thermostat being contorled i.e. set temperature, change mode, etc.
So in your case it might never get the actual humidity at the time because ST got the value many hours ago.
I gotcha, that makes sense.
Do you have the actual Sensi app still on your phone? Mine updated a few days ago, with the official announcement of ST integration. Since then, the automation has actually triggered once! I’m just not sure if that once is because the conditions were met only once, or if it’s just buggy still.
Just bought 2 sensi and noticed this very thing. It’s not updating ST very often. Anyone have any ideas to force an update on a schedule? Webcore has a ping function but not sure exactly what this function does. Also found it odd that there is no functions available to get current temp or humidity just a bunch of set functions.
Just of note, all other functions in ST works fine. If I change the set point in ST the stat changes and visa versa.
Not sure then, I noticed the sensi dth is not recognized by the ide, just showing place holder:
For anyone else that might have this issue my thermostat randomly stopped responding yesterday saying it was offline in SmartThings. I went to remove and re-add it in “connected services” again in the new app and when I tapped on Sensi it took me to the Sensi login page. Once I logged in, it instantly started working again without having to remove it.
If you don’t know where “connected services” is, open the new SmartThings app, pull out the left menu, tap the gear for settings, and it should be the third thing down.