Author
Topic: Ecobee3 control from VeraEdge UI7 (Read 12498 times)

Thank you very much Watou for your efforts and contributions! I removed the original plugin after the polling issue you posted recently just to insure I was contributing to the Ecobee spamming issue. As such I am looking forward to getting it installed and actually being able to take advantage of my new Ecobee3 in conjunction with my Vera and new Econet vents.

Thank you very much Watou for your efforts and contributions! I removed the original plugin after the polling issue you posted recently just to insure I was contributing to the Ecobee spamming issue. As such I am looking forward to getting it installed and actually being able to take advantage of my new Ecobee3 in conjunction with my Vera and new Econet vents.

Thanks again for your hard work!

You're welcome! Please let me know if there are plugin problems once you have it installed and running.

Thank you very much Watou for your efforts and contributions! I removed the original plugin after the polling issue you posted recently just to insure I was contributing to the Ecobee spamming issue. As such I am looking forward to getting it installed and actually being able to take advantage of my new Ecobee3 in conjunction with my Vera and new Econet vents.

Thanks again for your hard work!

You're welcome! Please let me know if there are plugin problems once you have it installed and running.

Will do. I will be keeping an eye out on the App interface and here for news on the new Apps release. As soon as it's available, I will install it. Thanks again!

@watou - through trial and error, I've figured out (I think) that the plugin (or rather Ecobee) will only support one instance of the plugin for a single Ecobee account, meaning, in my case, I have two thermostats (two homes) that I have setup through a single Ecobee account, and when I authorize one Vera to control Ecobee by securing a PIN and putting it into the Ecobee interface, it knocks my other Vera off. So it seems that in order to control both thermostats through Vera, I would need to have both thermostat controls exist in only one of my Vera instances (i.e. primary home + vacation home both on my primary home's dashboard), because Ecobee is only maintaining one PIN code to allow Vera control. Not ideal, but doable.

Question: Have I reached the correct conclusion, or is something else going on and should I be able to control each thermostat in each of my two separate Vera instances? Extending that, do I need to decide if I want to control my Ecobee thermostats in a single Ecobee account, or a single Vera dashboard, but cannot do both?

Also, I'm now contemplating an upgrade to UI7. Is the plugin working in UI7 these days?

@watou - through trial and error, I've figured out (I think) that the plugin (or rather Ecobee) will only support one instance of the plugin for a single Ecobee account, meaning, in my case, I have two thermostats (two homes) that I have setup through a single Ecobee account, and when I authorize one Vera to control Ecobee by securing a PIN and putting it into the Ecobee interface, it knocks my other Vera off.

It's not supposed to work that way. The OAuth flow is confusing and hidden from users, but a PIN is "exchanged" for a unique auth token, from which are produced refresh and access tokens which are rotated once an hour. You don't want to copy any of those three tokens to other plugin instances, because one instance will rotate the tokens, pulling the rug out from the other instance. So pressing "Get PIN" on one Vera, entering the PIN at ecobee.com, and then doing those same steps on the other Vera, should not cause any conflict.

do I need to decide if I want to control my Ecobee thermostats in a single Ecobee account, or a single Vera dashboard, but cannot do both?

No; you should be able to use any number of Veras to control any number of Ecobee thermostats through any number of Ecobee accounts (subject to Ecobee's limits of registering a thermostat with only one ecobee.com account, and whatever limit they have for number of thermostats per account).

Also, I'm now contemplating an upgrade to UI7. Is the plugin working in UI7 these days?

It works, but the UI is wrong because of the incompatible change to setpoints in UI7, and a lack of documentation on how to update a working UI5 thermostat plugin for UI7 (unless it's quietly appeared in the meantime and I'm not going to go hunt for it).

Clearly I must have something else going on then. Right now, my weekend home Vera is successfully maintaining a connection to my Ecobee and has been for at least a couple months. Not the case for my primary home. And when I go in and get a new PIN for my primary home Vera, it seems to knock out the weekend home. Odd...

I will try one more time setting a PIN for my primary home and keep a close watch and report back.

I've installed the latest version (1.6), but when I attempt to create a scene, all options are grayed out. Also, I don't see any option to control the fan. I have added, removed, and re-added and authorized my Ecobee probably 20 times already, but no such like. Do I need to do a factory reset of of my Vera and Ecobee? What am I doing wrong? Are there any other Ecobee plug-ins that I should try?

Yes, there is an Ecobee plugin in the App store. It works. I use it. Install it, click the "Get PIN" button, and when the PIN returns, register that PIN as an authorized app in the app control settings in your Ecobee web interface.

The only issue I have with the plugin is that sometimes my thermostat will "un-register" from Vera (i.e. Vera no longer communicates with it) and I have to re-register using the above process. But I think (and this is just a guess) that this has something to do with the fact that I have two Ecobee thermostats in my Ecobee account (one in my primary home, one in my weekend home). One will occasionally de-register (seems to fluctuate between the two homes with no rhyme or reason) but the other will remain fine. This seems to happen every couple of months or so. I reported it to the app developer, but he hadn't heard of the issue with any other users, so again, there must be something unique about my setup/configuration. But generally speaking, it works.

I'm on UI7 and just purchased Nest Protect. I'm creating a scene using the Nest Protect as trigger and then change the state of the Ecobee to OFF. I can control the state of the Ecobee on the dashboard but whenever I tried using it on the scene, I cannot select the state of the Ecobee or even change the temperature on the scence.

I know it is working for me but I am using Lua code rather than the scene editor. I think it would be fairly easy for me to fix by adding the ecobee housemode device to be accessible by the scene editor but in the meantime try

luup.call_action("urn:ecobee-com:serviceId:Ecobee1","SetClimateHold", {HoldClimateRef = "mode"},ecobid)where ecobid is the device number of your ecobee house mode device"mode" is "home", "away", "night" or "smart1"

I was able to successfully add Ecobee Plugin on Veraplus (UI7). I tried creating scene for the motion detector in the thermostat and noticed that it only work intermittently (I am sending email notification and turning on a light upon motion detection). Has anyone tried using the thermostat's motion detector to trigger a scene?