My concerns were mainly stemming from a few factors:
The confusing selection of apps, devices and bundles in your store, I wasn’t sure what to even buy and what functionality I’d be missing out on
The lack of screenshot examples of what the workflow would be like for accomplishing the different use cases. The wiki makes it seem as though I’m supposed to program things somewhere with text inputs?
Regardless, I think I’ll be holding off for now. My use case isn’t complicated enough to require this whole solution. Also, I think I’d prefer the learning experience of producing the behavior I need in webCoRE and keeping my money to buy another ecobee sensor at some point instead.
Just want to inform my contributors and all ecobee users that new version of MyEcobeeDevice(v5.9.9z7) & MyEcobeeInit (v4.2) can be downloaded at my e-commerce solution provider (sellfy) using the original download link.
Now that ecobee supports 2FA (2-factor authentication), the login page embedded in MyEcobeeInit now supports the code sent by Ecobee.
Minor icons change (UI in the ST classic mobile app).
My Ecobee thermostat (in the ST classic and new Samsung connect app)
You basically just need to install the DTHs once, and forget about it. The code will recover and resend any failed thermostat or switch command in the next hour window after a ST or ecobee outage. No other ecobee implementation (and especially the ST stock device) can match this level of resilience and reliability.
If you’re are a contributor to one of my support packages (and I have access to your ST account), the upgrade has already been done for you. You don’t need to do anything, everything has been taken care of.
On top of it, there are many complimentary smartapps designed for My ecobee DTH and are located at my github. All ecobee smartapps are explained at the ST community wiki (all ecobee* smartapps):
I am one of the contributors to your Ecobee SetZoneWithSchedule App. Could you please confirm if it will continue to work once I switch to the new smartthings App? Users of the Smartthings Classic App are getting notified through the app that they will no longer be getting updates. Customers are been asking to migrate.
Hi, if you have the latest version of My Ecobee bundle (including the ecobeeSetZoneWithSchedule smartapp), it should work under the new Samsung Connect app.
However, you need to keep the ST classic mobile app even after the migration as you need it for making change to the devices via MyEcobeeInit. All custom DTHs require the ST classic mobile app as long as SmartThings has not released the custom capabilities. This feature is not mature enough at this point.
The migration is mainly just for the routines and other automation.
You can still use both apps (ST classic mobile app and Samsung Connect app).
I’m using your smart app. It is working fine.
Today I got an email from ecobee saying they are moving EMS portal users to SmartBuildings and discontinuing EMS API in the near future. Should I need to worry about it?
Hello @yvesracine - Will you be hosting this smartapp on your own server or in the cloud when Samsung decommissions IDE? Just want to make sure I’m prepared as I use your code for both keen smart vents and ecobee.
I’m not planning to rewrite any code for the new Samsung platform at this point. The existing groovy code works at the moment under the new Samsung connect app (as per the screenshots above, see postings about the last version):