Nest Thermostat: What's your thoughts?

So why clutter-up this one?

4 Likes

Lol. Outdated. Seriously…
What’s so advanced about ecobee? It’s remote sensors? Integrated Alexa? At the end of the day a thermostat is always going to be a Thermostat.

Ecobee doesn’t have the Ecosystem that Nest has hand-down.
I have no problem saying there API needs to be much more advanced and open, but it works now and it is what it is.

My initial point was that he didn’t come here asking about whether he should get a Nest or Ecobee. In your usual fashion you are pushing Ecobee’s over Nest to try and drum up some business for your SmartApps and Devices.
That bugs me because that’s not what this community is about. I respect the fact that you want to make money for the time you spend on your developments but popping into every thermostat topics to push Ecobee is annoying.

2 Likes

And, aren’t you trying yourself to monetize your efforts by providing some real time event processing for the Nest devices (which you deserve btw) ??

I’m not trying here to sell my products, I’m trying to give better choices to non technical people who are looking into buying a really ā€œsmartā€ thermostat.

P.S. The initial thread was a question about the viability of the Nest… So, I’m providing another fair answer to this question.

I’m not here to have a debate i’m merely stating my opinion whether you agree with me or not is irrelevant. Obviously others do as well.

If you want to be helpful provide comparisons/facts based on your personal experiences if you’ve owned both.

I personally have zero experience with Ecobee so I can’t comment to how ā€˜Smart’ it is and I certainly don’t rely on tech journalists to provide me with decision making facts on whether one device is better than another. I like to review forums with real users opinions/issues to see if a product is right for me.

Well, obvsiously, I’m bias toward ecobee and, on top of it, I ask for a contribution for my code because of the extensive range of features I provide with my DTH and smartapps.

So, I’m not neutral, and that’s why I would not post my personal experience with any other thermostats…

I’d rather rely on several neutral reviewers from well established technical magazines who do reviews like that every day…

My thoughts are… if you are into smarthome technology and/or have a SmartThings, why waste money on a Nest, Ecobee, etc. Get the cheapest functional Zwave or other compatible thermo and use your smarthings / logic to control it. I bought CT100s. They work great.

It really depends on your needs (do you have a big house or a small appartment?) and your use cases.

Z-wave thermostats are fine (I have some at my house as secondary thermostats), but in a large house, they are not at par with ecobee or even the Nest. They lack many features and reliability.

And, the SmartThings’ scheduling is not as good as the ecobee scheduling (there are many threads about the ST scheduling failures), so I would not recommend Z-wave/Zigbee thermsotats in a house as the primary thermostat.

http://thingsthataresmart.wiki/index.php?title=My_Ecobee_Device#Why_ecobee_vs._other_connected_thermostats.3F

Regards.

I am not prepared to heat and cool my home solely based on ST logic. If I could do it all local, okay, but the cloud failures are too frequent in my mind.

The Nest user experience and network reliability is exceptional. Perfect? No but what is.

2 Likes

Too each their own.

Here’s the thing, despite the lack of reliability of ST - and you can easily see I have been one of the most vocal folks about ST’s failures… it has never impacted (meaningfully) my HVAC desires.

Why? Well, mainly because I am never going to be as sensitive to the timing and reliability of things related to HVAC as I am when it comes to things like lights, locks, etc… those need to work, work right away and every single time without fail.

HVAC, the logic doesn’t have to HIT right away, a few minutes delay is never noticed and between routines, and webcore watchdogs I have setup it always switches as I need it do so and if these logic engines are written in a robust fashion, they can back each other up and keep and eye out and cleanup any issues that result in a setting getting delayed or dropped. Be glad to share how if anyone is interested. Now if ST was down for 24 hours, I might have to hit the up down button on the temp on my Ct100s, but even that has never once happened.

As far as size of house - I have plenty of smart devices that pull in temp information and I could use that in my logic, but I don’t personally care to/need to do do, but one easily could do this to mirror what ecobee does in that regard.

I am not sure what supports that Zwave thermos are not reliable. Nor, at least when combined with smarthings, lack features. This is in response to the claim by others in this thread btw.

Just my 2 cents though…

2 Likes

:joy: oh the high and almighty. Such a dick! :joy:

1 Like

It also depends where you live… On the East Coast, scheduling failures are a big issue…

If the furnace or the AC doesn’t start in the middle of winter/summer, this could mean serious damages to your house: bursting pipes, mold, and so on…

You don’t want to rely solely on SmartThings to schedule your primary thermostat in your home…
For lights, that’s fine, but not for your primary thermostat.

Burp! Wait, what?! I have the best thermostat, period.

He he it’s so funny, I only see half the discussion but I can figure out what it is about - it’s THAT easy LOL

Laughing my webCoRE off :smiley:

3 Likes

Here’s another nice thermostat. It’s a cat! he he he

Still looking for the API documentation for it :smiley: :smiley: :smiley:

2 Likes