Okay. I should be able to add that without much of a problem. I just need to think through to make sure it is easily reverted upon transition to the next routine/sequence which may not be possible. Which would mean that you would have to make sure that the next routine takes care of that change.
I’ll look at it and report back once I’ve got something to test.
I just wanted to say thanks for all your hard work. I really appreciate your app it’s been amazing.
I have a question since my IDE had some issues and I’m not sure if it’s updating properly anymore.
Is 0.9.16 still the current version?
StrykerSKS/SmartThingsPublic (StrykerSKS-Ecobee3)
@StrykerSKS does the ecobee API allow for turning on/off the “free cooling” feature of a ventilator?
Yes, this is the latest version. I’m working on an update right now to add the ability to change the minimum fan runtime per a request. Found some backend bugs that are slowing me down on that to get it out.
Not at this time and unfortunately it seems that it may not even be supported by the APIs according to the Ecobee developer site. This has been requested by several developers but there is no response from Ecobee if/when it will be exposed.
Thanks for checking, I didn’t want to sign up for a developer account just to find out if it was in the API.
TL;DR is there any way around the new OAuth changes?
I just tried setting this up and it looks like I’m having an OAuth issue (“You are not authorized to perform the requested operation.”)
In the OAuth tab for the Ecobee Connect app, I see no “Enable OAuth in Smart App” option. In the list of SmartApps, the Ecobee Connect app has a value of “true” under the OAuth column.
A 4/29 update to this thread indicates SmartApps now need to be reviewed before OAuth is privileges are granted. I use a third party Android app, SharpTools, which recently pushed out an update, asked for reauthorization, and is now working again.
Thanks for any help
The OAuth changes should not have impacted us. Read the thread you linked me to. If you installed it in the IDE you can use it.
I am not seeing this error on my end and have been able to reauthenticate without a problem.
I’m traveling for today but will try to look at it some more this weekend to see if I can reproduce the issue.
Thanks for the response. Some more info I hope will be helpful:
I followed the instructions to the letter using github integration.
OAuth is in fact enabled in the Connect SmartApp in IDE (I was originally confused because there was no enable button but the client id, secret, etc settings are there so it must have been enabled). Generating new client IDs and secrets has not helped. Display name and link are blank.
When I run the Connect SmartApp on my phone (Android) I get the authorization error on a screen which is essentially blank not counting a remove button at the bottom (which does nothing) and a back button at the top.
Despite the error, each time I run it, an “Ecobee Thermostat:TestingForInstall” device is created. Deleting these devices removes the Connect SmartApp from my phone.
I tried deleting the Connect SmartApp from IDE inorder to reinstall but I keep getting a 500 Internal Server Error.
@kspace I’ve tried to reproduce this particular issue but have not been able to. I have been able to reauthorize and reinstall without problems on multiple devices (iOS and Android). I also know of others that have been able to install as well.
The “TestingForInstall” device is a dummy device that is created to test if the Device Handlers are properly installed. If they are not being automatically deleted then the app is crashing near that point. There was a platform issue that was causing such a crash that should be resolved now, but that still doesn’t explain the authentication issues you are seeing.
Is this still causing you a problem?
This has taken a LOT longer to implement than expected. This is for two reasons:
I’ve made some good progress in my development branch and am able to change the fanMinOnTime through tiles and a Routine change. Right now I’m working to get the resumeProgram functionality working properly.
Thanks for your patience.
Thank you for your hard work!
I updated the two SmartApps from the repo yesterday and tried again. Connect on my phone was no longer blank, had all the expected actions listed. Tried to authenticate to ecobee and got an error. I can’t remember what it said exactly but it sounded like a token issue so I reset the client ID and secret in IDE and now everything works just fine.
Not sure if it was the update that did it or a coincidence, but either way thank you.
Thanks Sean. I really appreciate you working on a solution
Am I the only one getting kicked out of authentication with the API several times a day?
Thanks for your work. I actually have an Ecobee Smart with 2 remote (wired) temp sensors, and a fresh air ventilator. I’ve grabbed your device and have it working with my setup. Obviously it says motion is not supported, but since the Ecobee API is consistent, everything else works.
I’ve skimmed the thread a little, but are others working with non-Ecobee3 setups? I’m interested in digging in and seeing if I can contribute.
Colin
Routines stopped firing for me, after a couple of days of the authentication getting kicked out several times. Now the smart app wont let me edit the preferences or the Helper Smart Apps. I tried to Remove ecobee (Connect) but i get “An unexpected error occurred.” message.
Mine keeps losing connection as well. I reconnected again yesterday through Ecobee(connect) and it has been good for the last day anyway.
I know of at least one other Ecobee Smart user. I made changes to accommodate their hard wired sensors. Some other tweeks that could probably be made depending on the configurations.
Happy to have more contributors!
Deleting should NOT be your first reaction to problems. In many cases the issues are being caused by a platform issue, so trying to delete the apps will often compound that problem if the system issues are still ongoing.
For those of you that are having disconnect issues, I need more data to pinpoint what is causing the issue! So please either grab the data from the live logs or set debugging to Level 5 in the SmartApp Preferences and when you get a disconnect please grab the information from the debug console in the SmartApp please.
Mine almost always recovers on it’s own. I can only recall having to reauthorize twice since I switched to this app.