Was scratching my head this morning why my IFTTT rule didn’t make my thermostat budge. I have an HSM alert for low temps near my plumbing to push the thermostat higher in serious cold. Was 3 degrees in NJ this AM. I checked their twitter and sure enough they were getting flooded with questions. Hours later here is their email:
Our services will undergo planned maintenance over the next few weeks.
Start Date: January 22, 2019
We’re performing an update to our software and services to improve your experience and maintain your security. Our servers will undergo maintenance over the next few weeks, and you may experience brief intermittent connectivity. Our updates will begin taking place on January 22, and run throughout February. The downtime will be used to maintain the platform, perform upgrades, and help ensure the continued integrity and security of our services to our users.
During this time, your thermostat will continue to work, but you may temporarily experience an inability to remotely manage it via your app.
No action is required from you right now. Connectivity will re-establish itself automatically.
So in the bitter month of January we should expect that our thermostats will not respond. Oh and the solution is to just manually set them, how acceptable.
If not for my wireless furnace controller I’d be done with these idiots.
The scary thing is you have no way of knowing the message to the Thermostat made it or not, other than walking up to the unit to see. App will show that it is set per your request. Smh
I wouldn't complain too much, you could be using an Ecobee. They have daily unplanned/unannounced outages, which invalidates your tokens and everything stops automating. In fact, at this moment, I can't even refresh my token. I'm just saying, I don't feel real bad for you. j/k
Sounds like they have some major issues they are trying to fix, but they ought to provide more info as to why after. But maybe they don’t want worse PR then what they are about to get.
Any new CVEs for Honeywell stuff?
Even more of a reason to stay off the cloud as much as possible.
Maybe I've been hanging out here too much, but this is a real eye opener - I don't need their stinkin cloud with a platform as solid as HE. It's not like I'm relying on some advanced algorithms on their end - I just want to set the Thermostat.
I just purchased an ecobee with remote sensors. My need is really to operate with a remote sensor, I don't need any complex automation. Should I assume these thermostats work in some basic mode without the cloud connection?
I'll install the ecobee in a few days. BTW I'm not that worried because I purchased the ecobee from costco and they have a very liberal return policy. Good deal too, $170 for an ecobee light with 2 remote sensors
Also:
I just received an email from Zen, they verified the Zen does not support remote sensor(s).
That leaves the ecobee the only thermostat with native remote sensor capability.
Just to echo what JasonJoel said, Ecobee work great if you stick to their scheduling and automation. They do not integrate well with much of anything outside of IFTTT, and absolutely nothing locally.
Even so, without the cloud, the smartphone app doesn't work at all. So when I'm lazily laying in bed thinking it's too damned hot, I couldn't do anything about it, without getting my lazy butt up and walking to the thermostat, when my automation integration fails due to their persistent outages.
You bet. Full scheduling locally. You don't need to use the cloud connection any more than you want to. Although I think it is MUCH easier to program from a laptop web interface than the phone, but YMMV.
can add/remove the # of periods (sleep, home, away - an example day may look like night-home-away-home-night, etc )
can have different schedules and setpoints per day
Awesome thermostat. I like it WAY more than I did the nest, The remote sensors are great,
Anyone else seeing login error trying to access Honeywell TCC? Getting log errors on HE as well as unable to log in with the Honeywell TCC app on my phone. Thanks.
