Would you buy a Nest thermostat again based on those facts that I posted above?
The Nest is not smarter than a zwave/zigbee thermostat when connected to SmartThings as you need to totally rely on SmartThings for its scheduling, which is not reliable (look up for scheduler fail in the ST community forum, you’ll know what I mean). With the current Nest APIs, you don’t have access to the following (and you can testify about it as you know the APIs): The current program The current programmed setpoints Any way to resume your current scheduled program Your runtime data, for example: stats about your running time of your main HVAC components Your sensors’ motion data So, yes, the Nest is not really smarter than a zwave/zigbee thermostat when connected to ST. All this can be achieved with the ecobee APIs. So, is it crap or not? Who is credible?
What I’m saying here is that there are better options for the same price point. This thread is about explaining the ecobee option for new buyers, not trying to convince existing Nest users to switch.
For someone who already bought the Nest, well it’s mostly too late. It’s a good thermostat, but does it worth the extra money vs zigbee/z-wave thermostats given its lack of good APIs?
Using SmartThings to schedule is not alien to me, as I have almost everything running through webcore. In all honesty I would prefer to use webcore for ALL automations and scheduling. The native apps rarely have the functionality I desire, and it’s easier for me to have everything running through one thing.
I don’t need all the extra features you listed, but many of them are available through NST Manager.
In the future I might buy another Nest. Larger user base, support is always a call away, and I already know how to use it.
Or I might buy an ecobee to change things up. Since they are so very similar, and the features (the ones I use) can be achieved on both I’m afraid it might have to come down to cosmetics.
Did you have any DST issues with your Automations just recently?
I’m sorry but where I live, my family cannot wake up cold in the middle of the night when it’s - 20 degrees outside…
All I’m saying is that I’m glad I don’t rely on SmartThings for my main HVAC scheduling… The other ecobee benefits (good APIs, HomeIQ portal, etc) are icing on the cake.
I understand that for you the Amazon integration is not a strong point, but for others it also makes a difference…
Honestly you’ve got me on the defensive mostly because you called my Nest dumb.
I’m outside Philly. Gets cold here too.
The screenshots of the ecobee look pretty cool though. All that data right there, ready to go.
The Home IQ portal is really a strong benefit of the ecobee. All your data available for download in excel spreadsheet if needed.
And, now something new is coming into the Ecobee Ecosystem (in beta):
Getting “an unexpected error occurred” when trying to add the new ecobee4 to SmartThings.
Anyone seen this before? Any ideas?
I don’t believe that you’re a contributor to my code. If you want a reliable integration between ST and Ecobee, please contribute to My Ecobee device at my store:
[RELEASE] My Ecobee Device & ecosystem v5 - The smartest thermostat under ST with new "comfort tips" features and Unique Integration with Echo/Ask Alexa
If you’re indeed a contributor, please send your logs to
P.S. If you’re a contributor, I don’t have you as an active contributor, so you’d need to follow the update procedure I sent you in an email.
Actually, the code was not at all the issue. Thanks anyway… but the issue is resolved.
Ecobee is the best thermostat according to wired…
I told you so, Ecobee is the best thermostat, and you were wrong all along…What will you do with your Nest thermostats: paperweight??