[RELEASE] Initial Setup for Ecobee3 & 4, Smart-SI, EMS, Smart-02 thermostats - My Ecobee Device

Done. Thank you.

Finally got a response from support:

"Chad Weirick (SmartThings)
Dec 7, 4:24 PM

Jarett,

Sorry for the delay in responding to you and that you’re having issues with Ecobee and SmartThings. I know that this is an issue that our developers are actively looking into at this time. I’m really sorry for the inconvenience, and can understand how frustrating this must be for you.

Just because our developers are looking into a solution doesn’t mean that we can’t try to improve your experience right now. Before we look at some potential solutions, was there a reason that you were using YRacine’s EcoBee device type over our own EcoBee implementation?

If there wasn’t a particular reason that you went with YRacine’s solution vs. our own implementation, I’d like you to use our try using our EcoBee device type. To do this you’ll need to remove your current EcoBee device from SmartThings and then follow the guide for your device:

EcoBee Smart Thermostat
EcoBee Smart Thermostat Si

I’d like to help you out further and gather some information on my end if that is OK with you. In the event that our troubleshooting does not resolve your issue, I have made sure that your email address has been attached to the issue at large. When that issue is resolved, you’ll be notified."

1 Like

@yvesracine Thanks for all the updates. I’ll give your beta branch a try today and report back later.

I too tried the beta code with our ecobee and less 6 hours later was encountering too many exception errors. What a drag. yvesracine’s Change Mode app is exactly what I was looking for.

1 Like

Hi,

Could you resync MyEcobee device at my main branch?

Just copy and paste, save & publish.

Now, I’m starting to believe that ST cloud backend is throwing some exceptions
for some users (like groovyx.net.http.HttpResponseException ) when it should not.

After checking in other forum threads, I found out that ST is also throwing groovyx.net.http.ResponseParseException for no reason as per this thread:

So the new code at my main branch will continue processing despite the exception.

Let’s give a try.

Regards.

Hi @slagle,

Now, I’m starting to believe that ST cloud backend is throwing some exceptions
for some users (like groovyx.net.http.HttpResponseException ) when it should not.

This affects MyEcobee device as my code is doing some exception handling in order
to avoid losing the access token (when I should probably not do anything in this case,
and just trap it).

After checking in other forum threads, I found out that ST is also throwing groovyx.net.http.ResponseParseException for no reason as per this thread (see the bottom of it):

My questions to ST (not to you specifically) are:

(1) Is it possible that some exceptions in DevConn are thrown for no reason?

(2) If yes, are there any platform updates planned to correct the situation?

Regards.

@yvesracine With your beta code and latest code I am able reinstall my Ecobee thermostat however when I go to add my remote sensor I get a blank screen during the part where you select the sensors.

I’ve also tried removing the thermostat and adding all from scratch and I still can’t add the remote sensors

Hi, @huydnguyen

Make sure to have the latest versions at the main branch (as the code has been promoted
from beta to main):

(1) Set My ecobee Device’s trace preferences to ‘true’

(a) go to https://graph.api.smartthings.com/device/list
(b) click on My ecobee device
© edit the preferences and set the trace parameter to ‘true’

You can remove this preference after doing debugging as this may impact performance.

(2) Activate Live logging at https://graph.api.smartthings.com/ide/logs

(3) Filter the logs for myEcobee Device & ecobee3RemoteSensorInit, and PM them to me if you have any exceptions/errors for the ecobeeRemoteSensorInit or My Ecobee Device.

Regards.

EDIT: This has been fixed now… The code is now working…

Hi @kruznby, @jarettp,

According to some feedback from several users, my code is now working with the
workaround that I implemented about the connection issues.

My Ecobee Device, MyEcobeeInit, Ecobee3RemoteSensorInit need to be resync first at the main branch (just save & publish the code in the IDE).

You may need to un-install and re-install the smartapps if some recurrent exceptions reappear.
Regards.

P.S. My code now ignores some exceptions that are thrown by the ST cloud backend (i.e. groovyx.net.http.HttpResponseException ) for some users.

Please support the developer :grinning:

I have the latest beta code and my account cannot stay connected for very long. Every time something should have triggered, I look and it shows I need to reauthorize the app. I am trying to determine how long it stays connected but there are so many exception entries in the activity feed that it is hard to determine. What can I provide to you to help determine where the issue is happening?

I will try deleting everything and starting from scratch again as in the post where you announced the latest fix, you indicated that was not necessary, but I just saw that in your last post you say it might be if the issues continue…

I have resync’ed as you directed. Also I turned on the toggle for proactive exception handling.

I ought to know by morning if this works for my particular configuration.

Thank you for your patience, persistence, and hard work!

No luck here. Looks like I would need to login every 4 hours.

refresh_tokens>>exception groovyx.net.http.HttpResponseException: Unauthorized for null

Ecobee verbose trace is doRequest>exception groovyx.net.http.HttpResponseException: Internal Server Error for https://api.ecobee.com/1/thermostatSummary?format=json&body={"selection"%3A{"selectionType"%3A"registered"%2C"selectionMatch"%3A""%2C"includeEquipmentStatus"%3A"true"}}

Yes, I had the same issue myself, I’m afraid that we have to wait for a platform update.

See below:

Continuing the discussion from Initial Setup for Ecobee3, Smart-SI, EMS, Smart-02 thermostats - My custom Ecobee Device:

Continuing the discussion from Initial Setup for Ecobee3, Smart-SI, EMS, Smart-02 thermostats - My custom Ecobee Device:

So I wonder how IFTTT stays connected without issues? Is it because IFTTT is an official Ecobee supported integration where ST is just trying to utilize their API? Or are we truly seeing a failure with the ST environment? IFTTT working sort of negates the “we can only control what we can control” pointing the finger line…

I’ve asked ecobee if they can add an indefinite hold to comfort profile mode changes. This would give me a great work around until ST fixes their integration. It hasn’t happened yet though. If we can get more people submitting this request maybe we can get it done quicker.

1 Like

Curious, would these exceptions issues affect routines not executing as they normally should? Thanks.

The excess exceptions appear to result in the ecobee init program becoming deauthorized from the ecobee web site, so yes?? However, I am not sure which is the symptom/cause of the occurrence…

Is there anyway for IFTTT to work based on presence of two phones (first arrive, last away) without using life360? I’ve used IFTTT to trigger based on connecting/disconecting to wifi at my house for my wife’s phone and then just override manually when I was home. I might have to switch back to this until ST and Ecobee work out their issues.

1 Like

You can use smartthings to trigger IFTTT using virtual switches.

I’ve got to be doing something silly here but I did as @yvesracine suggested and removed out all smartapps, devices, and republished the new code for the device type & myecobeeinit

When I execute the app from ‘my apps’ it take me to the first screen for paypal donation and info but after clicking next I come to a white screen that won’t load anything. Clicking ‘Done’ errors out and says contact the developer. I’ve removed and added back a few times now and still doing it. Any ideas? Thanks!