[DEPRECATED] Free Ecobee Suite, Version 1.2.*

I can’t reproduce it, but can you tell me what you where configuring (switch or contact, etc.)?

also, if you move line 379 to be before line 378, you should get the actual error logged in Live Logging for the device - that might help understand what’s going on…

Are you perchance trying to create this directly from the ST MarketPlace/SmartApps?

All of the Helper SmartApps in this suite MUST be created from within Ecobee (Connect), because they operate as children to that app. You can’t create them outside of Ecobee (Connect).

Thanks!
Barry

@storageanarchy,

I moved from using a nest to an ecobee… I am having a bit of a hard time trying to do some things that I use to do easily with the nest… IE: How can I just turn on the Fan for 2hrs? Or how can I tell the ecobee that if is over 82F in my house to turn on and keep the AC at 78 even when away…?

TIA!

Using my Ecobee Suite, set the default hold time to 2 Hours (in Ecobee (Connect) or in the Device Handler). Then click the fan button to “On”. This will create a 2-hour hold with the fan on.

Not sure what you want here - why don’t you just set the Away program to 78?

Or if you want to wait until the temperature hits 82 before cooling to 78, you can set the Cooling Delta to 4+ degrees (you have to set this on the thermostat preferences), and the cooling temperature to 78. This will wait until the temp hits 82, then cool to 78, and turn off again, until the temp hits 82 again.

1 Like

Mine did the same, so I manually copied/pasted all of the code in. Let me know if support helps you out!

@chevyman142000 Will do!

@chevyman142000 not looking very promising…

Hello Tim,

Thank you for reaching out to us here at SmartThings. Sorry you are having some trouble on your end.

One of my Leads checked into this as we don’t usually provide support on Custom Integrations & Custom Device Handlers and I apologize.

That said, they checked both shards and it worked.

You could try deleting/unlinking Repo and you may have luck that way.

Also, I am sure you are familiar with it but perhaps check our Community for a lot of great help and tips on Custom things.

Please do reach back out if you have other questions or concerns and we will do our best to assist.

Kindest regards

So it would seem they are punting here. Bummer, because I can’t manage copy and pasting code especially with fresh development that is getting frequent updates <(sigh)>.

  1. bogus answer, since works for me on 1 shard, and not in the other.

  2. code updates are slowing, so you shouldn’t have much hassle. Especially since it is only the 2 devices and not the 8 SmartApps.

My apologies…I wish I could do something to fix it.

Thanks!
Barry

Exactly why I didn’t open a support ticket. Thanks for trying!

I can’t seem to remove my current ecobee sensor and smart app. Any help would be appreciated.

This should be done from the Ecobee (Connect), basically reversing the order that you created them. Rome all the Helper SmartApps, deselect the sensors, then deselect the thermostats, exit Ecobee (Connect). Then go back into E© and scroll down to find the Remove button…

If this doesn’t work, try deleting in the IDE.

If that doesn’t work, contact support…

Thanks!
Barry

Turns out I had to give it over night to let me remove the devices. It was quite the battle. The problem I have right now is I can’t seem to add the thermostat as a device. It shows in the new smartapp but not as a tangible device for me to use. This is important as I did the switch mostly for more advanced webcore use.

Michael-

Fret not. You do not create the devices through the IDE. Please follow the install directions in the documentation:

Go to the Marketplace on your mobile device, select SmartApps/My Apps, and run Ecobee (Connect). From there, sign in to your Ecobee account, exit Ecobee (Connect). Then restart it from Automations/SmartApps, select your thermostat and sensors, and set any desired preferences. When you exit Ecobee (Connect) the devices will be created for you.

Thanks!
Barry

@storageanarchy and @chevyman142000 I sent a response to theirs and they dug a little deeper:

Currently, the system thinks those two device type handlers already exist in your repository. So what needs to be done is removing those in order to get them pulled in the other correct repository.

Which makes sense because I have the StrykerSKS-Ecobee3 repo even though I no longer use those device handlers. However, apparently I am still using the StrykerSKS-Ecobee3 repo’s ecobee connect smart app so I have to remove the ecobee devices from all my smart apps so I can remove the StrykerSKS-Ecobee3 smart app/repo so I can get back to stock ecobee smartapp, so I can use Barry’s shiny new stuff…

Sounds like a weekend project :slight_smile:
Thanks

1 Like

You should be able to manually install my Device drivers on top of Stryker’s, THEN delete Stryker’s repository from your IDE and add mine. It should work then…

Thanks!
Barry

1 Like

Turns out I figured out what the issue was playing around with things. Thank you for the prompt reply and I will let you know how things work out later down the road.

Thanks Barry I was able to get your repo added and get both the smart apps and the SH. I caused myself all kinds of fits by not doing a nice methodical “uninstall” of everything first.
I had ecobee connect installed already and made a mess of trying to install this without performing all of the “uninstall” steps first. Just in case someone else has (self-created) issues like I did, this is the order I should have followed:

In SmartThings App on device:

  1. Remove thermostat and remote sensor(s) from all smart apps (ActionTiles, Google, webCoRE, IFTTT, etc.)
  2. Uninstall remote sensor from “Things”
  3. Uninstall thermostat from “Things”
  4. Uninstall ecobee connect smart app
    On Web:
  5. Remove SmartThings integration from ecobee account (on ecobee’s site)
    In IDE:
  6. Install ecobee connect (and all child) smart app from repo (do not publish)
  7. Enable OAuth in ecobee connect smart app
  8. Publish ecobee connect smart app
  9. Publish device handlers from repo
    In SmartThings App on device:
  10. Go under “SmartApps > + Add a SmartApp > My Apps > Ecobee (Connect)”
  11. Logged into Ecobee account
  12. Chose Thermostat and remote sensro(s)
  13. Under “Things” renamed thermostat and sensor(s)
  14. Re-added thermostat and sensor(s) to appropriate smart apps (ActionTiles, Google, webCoRE, IFTTT, etc.)

I am sorry if this is a dumb post, but I was a dumb user and caused myself headaches… I am trying to help others avoid that. Now that everything is up and running… time to play! Thanks for this work @storageanarchy !

1 Like

Tim - Glad you made it through it all finally! And thanks for the documentation!

But for others using the @StrykerSKS version, you should be able to Manually install my suite in-place on top of that version. Things may get a little wonky for a few minutes, but if you run through Ecobee (Connect) to log in to your Ecobee account after you have saved/published everything in the IDE, you should not have to delete everything in order to make the switch.

You should then be able to delete the StrykerSKS repo from your IDE and add my repo instead, and from there you should be all set when updates are released.

Thanks again, Tim!
Barry

2 Likes

@storageanarchy Is there any way to customize the Notification messages? I have a notification when a window is open that I would like to just mention which window is open but instead it looks like the format for the messages is “Contact/Switch Handler name: All Doors and Windows are open, turning HVAC on”. What I want is to have it say either whatever I want, or “AC is on and [Contact Name] is open”.
Thanks

Would it suffice if the Notification for when the SmartApp turns the HVAC off included the name(s) of the contacts/switches that are causing us to turn it off? I could also include the thermostat name in this, as in

Contact/Switch Handler Name: [Front Door Sensor] left open for 5 minutes, turning [Ecobee Upstairs, Ecobee Downstairs] off.

This is relatively easy to accomplish.

However, telling you which specific contact sensor or switch was the last one to be closed is really difficult (nothing is impossible). Personally, I should think knowing which ones caused us to turn off the HVAC is much more important, while knowing the last one to be closed really isn’t useful information.

Thoughts?