Vera - Smarter Home Control Forum

General => Temperature Monitoring & HVAC Control => Topic started by: watou on February 26, 2013, 05:18:15 pm

Title: Plug-in for ecobee thermostats in development
Post by: watou on February 26, 2013, 05:18:15 pm
Hi all, just a note to say that I've done most of the development for a new plug-in for ecobee thermostats.  I'm not sure exactly when it will be available, but it will work with both their consumer- and commercial-level thermostats.

The current state of the plug-in is documented here: http://cocu.la/vera/ecobee/README.md (http://cocu.la/vera/ecobee/README.md).  One of the "fun" features of this thermostat (and the plug-in) is the ability to automate a text message from Vera that will go to the thermostat's display (or to all of your thermostats at once) in a simple UPnP SendMessage action.  So property managers can send "close the window" or "pay the rent" message to their rental properties! :)

If you have any thoughts, ideas or suggestions of what should be in the plug-in, please share!

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: Barlow on March 10, 2013, 05:45:29 pm
Hi Watou,

I just read your announcement and just wanted to let you know that I am really excited about your project. I use Ecobee thermostats in our house and summerhouse and the prospect of being able to integrate with Vera is great. It has been on my wish list for a long time. Keep up the good work. I look forward to work with the plugin when ready - or if ever you need testing done.

Kind regards,
Barry

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 10, 2013, 09:47:04 pm
I'm very glad to hear that, Barry!  I'm eager to release it to get some more testing with it, but it's looking good so far.  I will post here when it's ready for testing.

Thanks very much for the encouragement.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on April 03, 2013, 04:50:55 pm
Do any ecobee thermostat users out there have a "My Apps" widget in their ecobee web portals, like on the settings tab?  My plugin is working fine with the current state of the web API, but I would like to involve others to test the code before official release. 

Thanks for any assistance,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on May 08, 2013, 02:40:51 pm
Sorry for the late reply; very spotty Internet here.

I don't have better info regarding when My Apps will be generally available.  Hopefully soon.

The plugin ought to work with all of their thermostats, but it's only been tested against about 18 Smart Si thermostats so far.

Sorry I don't have better info. I tried to accommodate more testers but was rebuffed.

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: dmcstroud2 on May 08, 2013, 08:35:07 pm
I got a message saying need firmware 1.5.408 but my vera lite is on 1.5.262 and says it is the most current version??
Title: Re: Plug-in for ecobee thermostats in development
Post by: futzle on May 08, 2013, 08:57:05 pm
You have to update by visiting a special web page. Finding the announcement on the forum is left as an exercise.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Brientim on May 08, 2013, 10:36:24 pm

Try cp.mios.com/firmware and follow the instructions
Title: IMPORTANT NEWS for ecobee thermostat plugin users
Post by: watou on May 31, 2013, 02:41:32 pm
To anyone who has installed the ecobee plugin from the app store but who has not yet entered the PIN in the ecobee.com web portal (since it's still in beta and not generally available):

Please uninstall the plugin for now until ecobee has made their API publicly available to all ecobee customers, and version 0.7 of the plugin is avaible in the Apps store. 

To uninstall the plugin, log into your Vera UI5 web interface, go to the Apps tab, find "ecobee Thermostat" under the "My apps" sub-tab, and press Uninstall.  Follow the remaining instructions, and monitor this thread for exciting news about the upcoming GA release of ecobee.com's API!

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: Michele on June 07, 2013, 02:03:14 pm
I just installed the ecobee plugin on my new Vera 3 and I have to say I'm very impressed.  This is a great service - thanks so much.  Nice job!
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 07, 2013, 03:00:48 pm
I just installed the ecobee plugin on my new Vera 3 and I have to say I'm very impressed.  This is a great service - thanks so much.  Nice job!
You're very welcome!
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 07, 2013, 05:05:56 pm
How did you get PIN code login working?
Please report if the information in the README.md is insufficient.

http://cocu.la/vera/ecobee/README.md (http://cocu.la/vera/ecobee/README.md)
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 07, 2013, 06:25:57 pm
I don't see "My Apps" widget in my ecobee.com web portal.
So I wonder how others are logging in since Ecobee beta is closed.

Unfortunately I have no information about when the API was/will be generally available. If it's not already, it ought to be very soon. Make sure you check the settings tab in the web portal to be sure. Version 0.7 of the plugin is available because 1) I believe that My Apps will be GA soon if not already, and 2) it is the only viable path to make the beta plugin available to testers.

If you learn anything definitive,  please share it here!

Thanks,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: Michele on June 07, 2013, 08:28:42 pm
Michele,

How did you get PIN code login working?

I have no idea.  First I went to the apps tab on Vera and installed the ecobee app.  Then I saw an ecobee icon appear on my Dashboard with a button that said "get pin".  So I clicked that.  I got a four digit number but nothing else happened, so I went back and read the documentation that said I had to type that into ecobee's web interface.  So I opened that, went to the ecobee Apps tab, loaded the Vera app and typed the pin into the otherwise anonymous gray box I found there.

Once again, nothing happened.  I then went back to Vera and typed my thermostat's serial number into the "thermostats" section of the advanced tab of the ecobee icon.  And still nothing happened.

But a few minutes later, while I was searching the web for more information on how to get this mystery to work, suddenly my thermostat appeared in UI5.  Yippee!

I guess sometimes just stumbling around blindly can be a productive strategy.
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on June 14, 2013, 12:58:25 am
I got my API!

Thank you WATOU, your plug-in works beautifully!
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 14, 2013, 01:03:27 am
I got my API!

Thank you WATOU, your plug-in works beautifully!

Thanks for the positive feedback!  Very glad to hear.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on June 15, 2013, 11:36:21 am
watou,

thanks for your plug-in!

a couple questions after playing with Smart tstat & plag-in:
- Home/Away buttons gives 'Invalid Service' error
- Resume button works, but forces Programming for 10-15 minutes, i.e. during this period a temperature can't be changed to Hold; it snaps back to Programming setting
- my Hold Action is set to "Ask Me". What is a Hold timing default in "Ask Me" mode and is it user settable? Any thoughts on implementing Hold timing options?
It would be great to have
 - QuickSave/Economy button state
 - Wattage reporting working
 - Heat/AC/Fan ON/OFF state reporting

PS I'm a bit confused about your instructions for scope/selectionType/selectionMatch settings to enter smartWrite/thermostats/list of thermostat identifiers.
During the setup smartWrite was automatically set to 'registered' and both my thermostats seem to work. I did not enter tstats IDs as I was not really clear if I had to do it anyway and how/where to enter them.

Thanks again for great work!


Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 15, 2013, 12:07:44 pm
thanks for your plug-in!

You're welcome!

- Home/Away buttons gives 'Invalid Service' error

What are the specific models of your ecobee thermostats?  I have a single EB-SMARTSi-01 here that I've done testing against, and I've only ever gotten "view only" access to a collection of other ecobee thermostats.  There is code for "EMS" thermostats in the plugin which I've not yet been able to test.  I would appreciate part of your /var/log/cmh/LuaUPnP.log file around the time of the 'Invalid Service' error to see if it leads me in the direction of finding the cause.

When I press the Away button, it sets an indefinite hold event that changes the heat and cool setpoints to the quick-save setback and set forward increments.  The Home button issues a ResumeProgram function to clear the hold.  This is for non-EMS thermostats.  For EMS thermostats, setting Away performs a setOccupied(false) function (a special hold type).

- Resume button works, but forces Programming for 10-15 minutes, i.e. during this period a temperature can't be changed to Hold; it snaps back to Programming setting

I will have to research what "forces Programming for 10-15 minutes" means.  Could you elaborate or send me a doc link?

- my Hold Action is set to "Ask Me". What is a Hold timing default in "Ask Me" mode and is it user settable? Any thoughts on implementing Hold timing options?
It would be great to have

Currently all holds are set indefinitely because I don't know how to semantically match other hold times to Vera/UPnP service types.  I could possibly add a variable on the Advanced tab that let you choose a different hold time from indefinite, but I will have to know more about potential use cases to get it right.

- QuickSave/Economy button state

I asked for a way to implement QuickSave from the plugin, just as the user can do from the web portal, and I don't think that is in the current API.  However, the "Away" button when used with non-EMS thermostats attempts to detect/set a setback/forward hold event like QuickSave does.  I think that if we can figure out the 'Invalid Service' error that you get (but that I can't reproduce here), this might help address this point.

- Wattage reporting working

Like in the Nest plugin, the UserSuppliedWattage device variable is just a placeholder in the code for wattage reporting.  Do you have any implementation ideas for how to make this meaningful?

- Heat/AC/Fan ON/OFF state reporting

This was not in the ecobee API last time I checked, but I will look again after the API is officially public and report back.

PS I'm a bit confused about your instructions for scope/selectionType/selectionMatch settings to enter smartWrite/thermostats/list of thermostat identifiers.
During the setup smartWrite was automatically set to 'registered' and both my thermostats seem to work. I did not enter tstats IDs as I was not really clear if I had to do it anyway and how/where to enter them.

If you are a non-commercial customer, you can typically skip the entire section of the README regarding setting selectionType and selectionMatch.  Only larger infrastructure users would typically be concerned with viewing/controlling specific subsets of their managed thermostats.  If you have any suggestion on how to make the documentation less confusing, please pass it along!

Thanks very much for the report.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: Michele on June 15, 2013, 12:41:59 pm
Michele,

How did you get PIN code login working?
I just clicked the "Get PIN" button on the ecobee device in UI5.  Teen I logged in to Ecobee's own gateway, went to Settings -> My Apps, typed in the PIN in the gray box and clicked on "Install App".  I then added "Vera Home Controllers" and a few minutes later my thermostats appeared in UI5.

I am having a problem though of having to go through this process every three days or so.  I get a message in the Vera log that says

"ecobee : Not yet authorized. Press 'Get PIN' once; wait for PIN; enter at ecobee.com."

After going through the whole process again, it works - until the next time.  What's up with that?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 15, 2013, 01:02:48 pm
I am having a problem though of having to go through this process every three days or so.  I get a message in the Vera log that says

"ecobee : Not yet authorized. Press 'Get PIN' once; wait for PIN; enter at ecobee.com."

After going through the whole process again, it works - until the next time.  What's up with that?

Let's not forget that the API is still not officially available! :)

Edit: not to discourage you from reporting whatever oddities you see! 

(I just think the programmers at ecobee are probably busily readying for GA, might have to do cleaning out of old tokens or other pre-launch prep.)

Title: PLEASE install attached update file
Post by: watou on June 16, 2013, 12:15:32 pm
To anyone who has installed the 0.7 (app store) beta of the ecobee thermostat plugin:

Please install the attached file on your Vera as soon as possible.  I've discovered a strange bug in Vera (1.5.408 anyway) that can lead to over-polling of ecobee.com.  This file will close that potential.

To install the attached file:
If you want to verify that you correctly applied the fix, the plugin will now log that it is version 0.8 in your Vera's /var/log/cmh/LuaUPnP.log file.

Thanks,
watou

P.S. If you installed the ecobee thermostat plugin but you do not currently have access to "My Apps" in the ecobee web portal, please uninstall the plugin for the time being, until such time as you have My Apps access, and only install 0.8 of the plugin once it's available in the app store.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Michele on June 26, 2013, 01:27:42 pm

Let's not forget that the API is still not officially available! :)

Edit: not to discourage you from reporting whatever oddities you see! 

(I just think the programmers at ecobee are probably busily readying for GA, might have to do cleaning out of old tokens or other pre-launch prep.)
That's probably it - that problem has not happened again since then.  This app is actually better than Ecobee's official web interface.

I do have a suggestion for a feature that might not be too hard to do (I haven't checked the API docs).  How about adding an alert if you lose communication with the thermostat?  That could give you an early warning of trouble.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 26, 2013, 01:55:52 pm
This app is actually better than Ecobee's official web interface.

Wow!  That's great to hear.

I do have a suggestion for a feature that might not be too hard to do (I haven't checked the API docs).  How about adding an alert if you lose communication with the thermostat?  That could give you an early warning of trouble.

I would be happy to implement whatever is considered the "standard" way for doing this in Vera, but it might be achievable already without putting anything specific in the plugin.

There are two points of connectivity that could fail -- (1) from your Vera to ecobee.com, and (2) from ecobee.com to the thermostat. 

If the first happens, then the thermostat's LastUpdate variable (from the service ID urn:micasaverde-com:serviceId:HaDevice1) will not be updated.  If the current time (seconds since the Epoch) is too different from LastUpdate (say, 600 seconds or pick a number), then that would indicate that the plugin has not learned the thermostat's status in about that long.  I imagine some kind of automation could be kicked off.  In the second case, where ecobee.com can't communicate with the thermostat (by its own measure), then the CommFailure variable will be set to 1, another case where automation could be triggered.

Now this isn't as "user-friendly" as it could be, but I would be interested in implementing an enhancement as long as it's consistent with how other plugins well address the same issue.  Any thoughts on this are very welcome!

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: Michele on June 28, 2013, 01:10:50 pm
Good question.  I have no experience with other "cloud" type devices.  All my devices talk directly to Vera. 

Case 1 - loss of communication between Vera and ecobee.com.  If Vera itself has gone down, then you're already done - doing anything will be impossible.

Case 2 - loss of communication between ecobee.com and the thermostat.  That can happen a bunch of different ways: ecobee.com itself goes down (and that seems to happen about once a year), your router, modem, or ISP goes down, your wi-fi gets wedged (neighbor installs new router on your channel), or the thermostat itself fails.

If ecobee.com is up and Vera is still alive, odds are the thermostat itself has failed - that's what we want to know.

And while we're at it, is there a way to get ecobee alerts via the plugin?  One of my thermostat's dry contact inputs is connected to the A/C float switch.  If that trips, I get an email form ecobee but it's something you really want to know about right away.  For example, using VeraAlerts, I could get a notification right on my phone.  That would be cool.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 28, 2013, 01:21:10 pm
If ecobee.com is up and Vera is still alive, odds are the thermostat itself has failed - that's what we want to know.

I *think* the CommFailure variable will be set to 1 in the above case, but I can't say for certain because the specific logic that's behind the ecobee API for determining if a thermostat is "connected" is not visible to the API user.  I tested it here by simply removing power from my thermostat, saw that CommFailure went to 1, plugged it back in, and shortly thereafter saw it go back to 0.  I imagine that a sufficiently "dead" thermostat, aside from power loss, would show up in the API the same way, but I can't say for sure.

And while we're at it, is there a way to get ecobee alerts via the plugin?  One of my thermostat's dry contact inputs is connected to the A/C float switch.  If that trips, I get an email form ecobee but it's something you really want to know about right away.  For example, using VeraAlerts, I could get a notification right on my phone.  That would be cool.

I would very much like to know the "clean" way that a Vera plugin generates textual message notifications.  I believe the ecobee API would give me the ability to push alerts out, but I haven't investigated the proper way to surface these in the plugin.  Any ideas where I should look?  I can post in the Plugins and Plugin Development area here, but maybe someone reading this has ideas?  If not, I will start digging.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 05, 2013, 10:50:07 am
Just a note that I've (finally) updated the README online to reflect the current ecobee thermostat plugin release 0.8:

http://cocu.la/vera/ecobee/README.md (http://cocu.la/vera/ecobee/README.md).

The source code for the plugin (minus the API library) is also now published at GitHub:

https://github.com/watou/vera-ecobee-thermostat (https://github.com/watou/vera-ecobee-thermostat)

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: saratankard on August 02, 2013, 08:02:46 pm
Really curious about the SendMessage action call.  I tried using the below code I *think* this is correct, but I didn't see a message pop up on the TStat. Am I using the syntax in the way you intended?

dev_num=237
service_id="urn:ecobee-com:serviceId:Ecobee1"
action = "SendMessage"
arguements = {Direction="In", Parameter="MessageText",Value="Door 5 Open"}

luup.call_action(service_id,action, arguements, dev_num)
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 02, 2013, 11:59:07 pm
Really curious about the SendMessage action call.  I tried using the below code I *think* this is correct, but I didn't see a message pop up on the TStat. Am I using the syntax in the way you intended?

dev_num=237
service_id="urn:ecobee-com:serviceId:Ecobee1"
action = "SendMessage"
arguements = {Direction="In", Parameter="MessageText",Value="Door 5 Open"}

luup.call_action(service_id,action, arguements, dev_num)

I think the argument syntax in your call is incorrect (see http://wiki.micasaverde.com/index.php/Luup_Lua_extensions#function:_call_action (http://wiki.micasaverde.com/index.php/Luup_Lua_extensions#function:_call_action)).  Try something like this:

Code: [Select]
local service_id = "urn:ecobee-com:serviceId:Ecobee1"
local action = "SendMessage"
local args = { MessageText = "Door 5 Open" }
local dev_num = 237
luup.call_action(service_id, action, args, dev_num)

I can't test this myself at the moment, but I think if you change the args accordingly it should work.  Also note that 237 should be either the main "Ecobee" device, in which case the message text should appear on all controlled thermostats, or 237 should be a specific thermostat device.

Regards,
watou

Edit: I think I had quotes around "MessageText" above which would be incorrect syntax.  (I should always test my examples before sharing them.)
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 05, 2013, 04:52:58 am
Sara, my example had a syntax error in it -- sorry!  Please let us know if you get your code to send messages to the thermostat's display.  Thanks!
Title: Re: Plug-in for ecobee thermostats in development
Post by: saratankard on August 05, 2013, 11:11:15 am
Works! Thanks so much  :)
Title: Re: Plug-in for ecobee thermostats in development
Post by: saratankard on August 22, 2013, 11:04:53 am
One follow-up question and one observation:

Question: On the Ecobee TStat when a message pops up there is a ""View details" option as well which you can navigate to with the arrows on the TStat. I didn't see anything in the documentation, so just wanted to confirm that there currently does not exist a way to edit this text field (by choosing a different parameter for instance).

Observation: I noticed on my EcoBee TStat in Mios there is no ModeTarget service variable for the urn:upnp-org:serviceId:HVAC_UserOperatingMode1 service. This was causing a few errors in my LUUP code when I went to change the TStat from CoolOn to Off, etc because the service variable was reporting a nil value.  I went ahead and added the service, variable, and value manually in Mios in the advanced settings and all works fine now, but might be nice to have this feature added.

Thanks again for a great plugin!!

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 22, 2013, 01:30:20 pm
Question: On the Ecobee TStat when a message pops up there is a ""View details" option as well which you can navigate to with the arrows on the TStat. I didn't see anything in the documentation, so just wanted to confirm that there currently does not exist a way to edit this text field (by choosing a different parameter for instance).

Hi Sara,
I'm afraid I don't understand what you are looking for regarding messages on the thermostat.  Please elaborate and I will attempt to answer!

Observation: I noticed on my EcoBee TStat in Mios there is no ModeTarget service variable for the urn:upnp-org:serviceId:HVAC_UserOperatingMode1 service. This was causing a few errors in my LUUP code when I went to change the TStat from CoolOn to Off, etc because the service variable was reporting a nil value.  I went ahead and added the service, variable, and value manually in Mios in the advanced settings and all works fine now, but might be nice to have this feature added.

You are correct that there is no actual ModeTarget device variable, and after looking at the code I can see that a call to the GetModeTarget action will always return "AutoChangeOver" regardless of the actual setting (a definite bug).

Edit: I opened an issue to keep track of this bug here: https://github.com/watou/vera-ecobee-thermostat/issues/4 (https://github.com/watou/vera-ecobee-thermostat/issues/4)

But I wonder why you would query the ModeTarget variable or call the GetModeTarget action.  ModeTarget is the variable that (should) hold the mode to which you are trying to set the actual thermostat, while ModeStatus is the variable which holds the actual, current mode.  So normally you would want to be querying the ModeStatus variable (or calling GetModeStatus) to get the current HVAC mode.  The UPnP spec separated the Target and Status concepts, knowing that an attempt to change the mode (with SetModeTarget) might be delayed from actually effecting the change, which is then finally reflected in GetModeStatus.

Also note that the above is a completely different subject from the current running state (ModeState) -- whether the thermostat is currently calling for cooling, heating, is idle, etc.  The ecobee API doesn't report the current running state last I checked, so there is currently no way to know if the thermostat is currently calling for heating or cooling.

Please let me know if this makes sense.

Thanks again for a great plugin!!

You're very welcome!

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: saratankard on August 22, 2013, 04:49:50 pm
On the Ecobee thermostat when a message is received I see three things on the display screen: 1) Desired message displayed message in a large blue box and 2)"Ok" 3) "View Details". As a user, you can either click "Ok" to accept the message or click "ViewDetails". I am wondering if there is a way if there is a way to input text so when the user clicks "View Details" another sub-message appears. As of right now when you click View Details, the original message is just displayed. Let me know if this makes more sense.

So, I was using the SetModeTarget action to set the ModeTarget variable to Off or CoolOn and this is what caused the error as no such variable existed. I was not actually querying the ModeTarget variable or using the GetModeTarget action. So, what you are saying makes sense but I don't believe it applies to what I am doing.

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 23, 2013, 04:21:21 am
On the Ecobee thermostat when a message is received I see three things on the display screen: 1) Desired message displayed message in a large blue box and 2)"Ok" 3) "View Details". As a user, you can either click "Ok" to accept the message or click "ViewDetails". I am wondering if there is a way if there is a way to input text so when the user clicks "View Details" another sub-message appears. As of right now when you click View Details, the original message is just displayed. Let me know if this makes more sense.

My guess is that the "View Details" button, in the case of text messages, would display the entire message if it were a really long message, while what is initially shown might be truncated if it's too long for the blue box.  I can't test it at the moment but that would make sense.  The ecobee API only lets me send one message, up to 500 characters long.  No additional fields are offered.

So, I was using the SetModeTarget action to set the ModeTarget variable to Off or CoolOn and this is what caused the error as no such variable existed. I was not actually querying the ModeTarget variable or using the GetModeTarget action. So, what you are saying makes sense but I don't believe it applies to what I am doing.

Are you saying that you are seeing an error calling the SetModeTarget action?  The UI5 and mobile apps can use that action without complaint (unless there is something in the logs I've missed.  If you have any log output you would like me to look at, please send it along.)

To get the current HVAC mode, query the ModeStatus variable or call the GetModeStatus action.

I hope this helps!

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: hadiesper on September 11, 2013, 08:27:07 am
Hi Everyone, I have a quick question before purchasing the Ecobee Smart Thermostat.

I am going to buy 12 of them. Will this plugin be able to support all at once?

Has anyone tried to control the thermostat through SQ Remote.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on September 11, 2013, 08:41:17 am
Hi Everyone, I have a quick question before purchasing the Ecobee Smart Thermostat.

I am going to buy 12 of them. Will this plugin be able to support all at once?

Has anyone tried to control the thermostat through SQ Remote.

During development of the plugin I saw it managing 15 thermostats from the one plugin instance.  Each thermostat has a thermostat device, a humidity device and a home/away switch device, so in that case the one plugin instance created 45 devices.  The large number of devices can be managed using rooms, categories, etc.

I only saw the plugin work with the Smart Si model but I have no reason to believe that it would not work with ecobee's other thermostats.

All monitoring and control goes through ecobee's web services, but I've not seen any performance or reliability issues as long as you have a solid Internet connection (and good wi-fi co-located with the thermostats).

I have managed my own Smart Si via the AutHomation Android app with no issues.  I suspect SQ Remote will also work but I've not heard.

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: hadiesper on September 15, 2013, 04:34:11 am
Thanks Watou. Your response was very helpful :)

Title: Re: Plug-in for ecobee thermostats in development
Post by: saratankard on November 13, 2013, 09:55:21 am
2 questions :)

1) I have noticed a weirdness on the EcoBee plugin that seems to occur sometimes after a restart. It seems when the luup engine is overloaded (causing a restart) both the cool and the heat go to their respective temperature extremes (-400, +400). It does not occur after EVERY restart, so I am trying to re-create the error in order to solidify more specific events which will be more helpful for you in thinking about this problem. In the meantime, I was wondering if you had ever observed such behavior?

2) I also have noticed, rarely, but sometimes the plugin loses comms with the Ecobee server, requiring a re-entry of the PIN#. I know you have noted in your github notes that sometimes external events may cause this. Are there any events in particular you have noticed that we can be wary of in order to predict when a lost comm is more likely to occur? Or better yet, would it be possible to add a sent alert or notification when the ecobee loses comms?

Thanks again for all your hard work -- it is not under-appreciated! 8)
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on November 13, 2013, 10:27:13 am
1) I have noticed a weirdness on the EcoBee plugin that seems to occur sometimes after a restart. It seems when the luup engine is overloaded (causing a restart) both the cool and the heat go to their respective temperature extremes (-400, +400). It does not occur after EVERY restart, so I am trying to re-create the error in order to solidify more specific events which will be more helpful for you in thinking about this problem. In the meantime, I was wondering if you had ever observed such behavior?

I have not seen anything like you are describing, but when you say "go to their respective temperature extremes" do you mean that the UI is showing that the setpoints are at these extremes but checking at ecobee.com verifies that the UI is wrong, or that the plugin sets the setpoints as such to the thermostat, or what exactly?  There is nothing in the plugin that will set these values to those extremes.  Make sure you have debug logging (LogLevels must include 35 in the list) so if you are able to re-create this situation, we can have logs to examine.  Sorry nothing comes to mind on this one, but maybe if you have more detail, it would help me think of something to try or inspect.

2) I also have noticed, rarely, but sometimes the plugin loses comms with the Ecobee server, requiring a re-entry of the PIN#. I know you have noted in your github notes that sometimes external events may cause this. Are there any events in particular you have noticed that we can be wary of in order to predict when a lost comm is more likely to occur? Or better yet, would it be possible to add a sent alert or notification when the ecobee loses comms?

I too have noticed this rare occurrence, requiring me to press "Get PIN" and then enter the new PIN in the ecobee.com portal.  It might be weeks and weeks before this happens, and I have no idea what is causing it.  I have always assumed that it was the consequence of some required maintenance going on at Ecobee with their API, where existing tokens need to be flushed, but that is just a wild guess.  I can't think of anything in the plugin that would be falsely reporting the need for a new PIN.  Look in your logs for "Encountered authorization error; forgetting tokens." and look for messages immediately preceding it to see what is being reported as to the cause.  The set of errors that would tell the plugin to forget its auth_token are:

Code: [Select]
  invalid_request = "The request is malformed. Check parameters.",
  invalid_client = "Authentication error, invalid authentication method, lack of credentials, etc.",
  invalid_grant = "The authorization grant, token or credentails are expired or invalid.",
  unauthorized_client = "The authenticated client is not authorized to use this authorization grant type.",
  unsupported_grant_type = "The authorization grant type is not supported by the authorization server.",
  invalid_scope = "The requested scope is invalid, unknown, malformed, or exceeds the scope granted by the resource owner.",
  not_supported = "HTTP method not supported for this request.",
  account_locked = "Account is temporarely locked.",
  account_disabled = "Account is disabled.",
  authorization_pending = "Waiting for user to authorize application.",
  authorization_expired = "The authorization has expired waiting for user to authorize.",
  slow_down = "Slow down polling to the requested interval."

If the ecobee API returns any of these except "authorization_pending," then the plugin will throw away its auth_token and require you to request a new PIN.  Perhaps check with your contact at Ecobee to determine if this list of API error returns is too long, and that some of these returns would not suggest that the session needs to be discarded.

On the subject of knowing when this happens, it is relatively straightforward for one to set up an automated notification when the plugin enters the state where it needs the user to request a new PIN.  It is also easy to use the GetPIN UPnP action to perform the request for a new PIN, but much trickier (and outside the scope of the plugin) to automate the entering of that PIN  in the ecobee.com web portal.  So the process of knowing when authorization has been lost and then re-establishing authorization is nearly fully automatable (but that last step would be pretty tricky unless you had a web page automated testing tool, for example).

Thanks again for all your hard work -- it is not under-appreciated! 8)

My pleasure.  Please report back here what you can so other plugin users can benefit, and thanks!

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: saratankard on November 21, 2013, 10:19:07 am
Quote
do you mean that the UI is showing that the setpoints are at these extremes but checking at ecobee.com verifies that the UI is wrong, or that the plugin sets the setpoints as such to the thermostat, or what exactly?

What I observed was the setpoints in the UI at these extremes. Perhaps a bit stupidly, I did not check in ecobee portal or the thermostat itself. I have not been able to re-create the error, but once I do I will post on here.

Quote
Look in your logs for "Encountered authorization error; forgetting tokens." and look for messages immediately preceding it to see what is being reported as to the cause.The set of errors that would tell the plugin to forget its auth_token are:  (.....) If the ecobee API returns any of these except "authorization_pending," then the plugin will throw away its auth_token and require you to request a new PIN.  Perhaps check with your contact at Ecobee to determine if this list of API error returns is too long, and that some of these returns would not suggest that the session needs to be discarded.

Thanks for all the valuable information on error codes for the logs. I should have enough to go on to investigate myself and report back. Also, I will follow-up with an ecobee rep to see if all really are necessary to discard the session.

Quote
On the subject of knowing when this happens, it is relatively straightforward for one to set up an automated notification when the plugin enters the state where it needs the user to request a new PIN. 

It would be quite valuable for us to have a notification when the plugin enters this state. Is this something relatively straightforward that I could implement, or do you mean easy for you to add to the plugin? I would love to make that happen! If you could tell me a bit more about how to simply add alerts when the EcoBee has lost comms (but not re-enter a new pin like you discuss), that would be very helpful.

Thanks again, as usual, for everything!
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on December 05, 2013, 02:18:43 pm
Watou,

I have been using your plug-in for few month and it works great!
Thank you!

Any plans to implement Energy (Watts) reporting?

It would be very helpful to monitor as HVAC is the biggest energy hog  :'(

Thanks
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on December 05, 2013, 03:05:21 pm
I have been using your plug-in for few month and it works great!
Thank you!

You're very welcome, and thanks for speaking up.  I was really wondering who out there was using it.  I've gotten very little feedback, which is either good or bad. :)

Any plans to implement Energy (Watts) reporting?

It would be very helpful to monitor as HVAC is the biggest energy hog  :'(

I would love to get ideas on what would be desired and any ideas on approaches.  All I know is a UserSuppliedWattage device variable, but what code does with it is still a mystery to me.  There might be other standard approaches for tracking HVAC energy consumption in Vera that I just don't know about.  Thoughts?

Also, have you ever had the plugin prompt you to request a new PIN seemingly out of the blue?   If so, did that event seem to correlate to anything else?  I don't have much user feedback about the plugin, and it would really help track down this oddity.

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on December 05, 2013, 05:28:21 pm
I think low feedback is a good thing - its working!
(btw, I don't see ecobee plug-in in Vera's Apps interface)

I have a very little experience with luup programming.
From what I read, it should be UserSuppliedWattage as described in http://wiki.micasaverde.com/index.php/Luup_UPnP_Variables_and_Actions#EnergyMetering1.
I'm not sure why Vera does not report energy consumption since dashboard displays correct wattage.
Perhaps you can test with luup.variable_get("urn:micasaverde-com:serviceId:EnergyMetering1", "KWH", <deviceID>).

Related to energy, I was planing to implement a work around for my HVAC split system to correctly report wattage as suggested in this post http://forum.micasaverde.com/index.php?topic=13301.0.
However, I noticed that HVAC actual State ('HVAC_OperatingState1' and 'FanStatus') are missing in thermostat Notification setup.
Would it be possible to add them?

Since July I think I had to reset PIN three times.
I don't think it correlated with local setup; most likely something on Ecobee server.

Thanks again for great plug-in
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on December 05, 2013, 11:35:03 pm
I think low feedback is a good thing - its working!
(btw, I don't see ecobee plug-in in Vera's Apps interface)

I hope that's it!  I do see the entry here: http://apps.mios.com/plugin.php?id=3586 (http://apps.mios.com/plugin.php?id=3586)  or do you mean something else?

I have a very little experience with luup programming.
From what I read, it should be UserSuppliedWattage as described in http://wiki.micasaverde.com/index.php/Luup_UPnP_Variables_and_Actions#EnergyMetering1.
I'm not sure why Vera does not report energy consumption since dashboard displays correct wattage.

Perhaps you can test with luup.variable_get("urn:micasaverde-com:serviceId:EnergyMetering1", "KWH", <deviceID>).

Related to energy, I was planing to implement a work around for my HVAC split system to correctly report wattage as suggested in this post http://forum.micasaverde.com/index.php?topic=13301.0.
However, I noticed that HVAC actual State ('HVAC_OperatingState1' and 'FanStatus') are missing in thermostat Notification setup.
Would it be possible to add them?

I suspect that the issue is that the Ecobee API, last I checked, has no way to report the current operating state, such as Heating, Cooling or Idle, or the current FanStatus (which is always reported as Off).  And so the plugin can't either.  Lacking that information, there would be no way to count energy consumption based on the UserSuppliedWattage setting, even though you may have supplied the values.  I suppose my adding UserSuppliedWattage was misleading if there is no way with the present Ecobee API to know when the system was heating or cooling or if the fan was currently running.

If you could lobby Ecobee to add the current running HVAC and fan states to their API, then maybe enough customers asking for this API feature could tip the scales.  Then I would update the plugin to make use of it and UserSuppliedWattage settings would most likely start being of value (plus there would be new automation trigger possibilities).

Since July I think I had to reset PIN three times.
I don't think it correlated with local setup; most likely something on Ecobee server.

I believe that the next plugin release will remove this rare need to request and register a new PIN.  0.8 of the plugin is overly aggressive in throwing away authentication information on certain errors, and I was recently informed that this isn't needed.

Thanks again for great plug-in

You are very welcome, and thank you for the feedback!

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on December 06, 2013, 02:12:40 am
Quote
I do see the entry here: http://apps.mios.com/plugin.php?id=3586  or do you mean something else?
I meant in Vera's interface Apps->Install Apps.

Quote
I suspect that the issue is that the Ecobee API, last I checked, has no way to report the current operating state, such as Heating, Cooling or Idle, or the current FanStatus (which is always reported as Off).  And so the plugin can't either.  Lacking that information, there would be no way to count energy consumption based on the UserSuppliedWattage setting, even though you may have supplied the values.  I suppose my adding UserSuppliedWattage was misleading if there is no way with the present Ecobee API to know when the system was heating or cooling or if the fan was currently running.

If you could lobby Ecobee to add the current running HVAC and fan states to their API, then maybe enough customers asking for this API feature could tip the scales.  Then I would update the plugin to make use of it and UserSuppliedWattage settings would most likely start being of value (plus there would be new automation trigger possibilities).

I do see Wattage reported when the Heat is On (first number from UserSuppliedWattage variable).
What triggers this Wattage display? Is there any way to see/used this trigger/status?

From your post I understand that Ecobee's API does not report weather On status is Heating or Cooling, however you can derive that if thermostat is in non-Auto mode state.
Alternately, one can adjust wattage seasonally.

I will send Ecobee a request to to add running status in API.
Btw, I did see API documentation on Runtime stage reporting for heat and cooling https://www.ecobee.com/home/developer/api/documentation/v1/objects/ExtendedRuntime.shtml
Is it usable?

Thanks again
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on December 06, 2013, 02:32:29 am
Quote
I do see the entry here: http://apps.mios.com/plugin.php?id=3586  or do you mean something else?
I meant in Vera's interface Apps->Install Apps.

Could it be that plugins you already have installed are filtered out of that search view?  I don't see it (or the Nest plugin) either when I search that way, and I have both installed.  Not sure about why that is (and not willing to uninstall any plugin in order to test my theory :) ).

Quote
I suspect that the issue is that the Ecobee API, last I checked, has no way to report the current operating state, such as Heating, Cooling or Idle, or the current FanStatus (which is always reported as Off).  And so the plugin can't either.  Lacking that information, there would be no way to count energy consumption based on the UserSuppliedWattage setting, even though you may have supplied the values.  I suppose my adding UserSuppliedWattage was misleading if there is no way with the present Ecobee API to know when the system was heating or cooling or if the fan was currently running.

If you could lobby Ecobee to add the current running HVAC and fan states to their API, then maybe enough customers asking for this API feature could tip the scales.  Then I would update the plugin to make use of it and UserSuppliedWattage settings would most likely start being of value (plus there would be new automation trigger possibilities).

I do see Wattage reported when the Heat is On (first number from UserSuppliedWattage variable).
What triggers this Wattage display? Is there any way to see/used this trigger/status?

From your post I understand that Ecobee's API does not report weather On status is Heating or Cooling, however you can derive that if thermostat is in non-Auto mode state.
Alternately, one can adjust wattage seasonally.

I have no idea what code uses UserSuppliedWattage or the inner workings of it.  I know that there is no HVAC running state possible with the Ecobee API as it's currently published.

Note that the running state (Idle, Heating, Cooling, FanOnly) refers to what relays have been engaged in the thermostat to turn your equipment on or off, while the HVAC mode of Heat, Cool, AutoChangeOver, etc. refer to what equipment will be engaged when the thermostat setpoints haven't been reached (or whatever other logic exists in the thermostat).  There is nothing that can be learned about what equipment is currently drawing energy from the mode, unless some piece of code in Vera is using a very crude guesstimate that, say, we're in Heat mode, and the current temperature is below the heat setpoint temperature.  I would imagine such a guesstimate would be extremely rough and not very dependable, but in any case, it's completely outside the realm of the plugin.

I will send Ecobee a request to to add running status in API.
Btw, I did see API documentation on Runtime stage reporting for heat and cooling https://www.ecobee.com/home/developer/api/documentation/v1/objects/ExtendedRuntime.shtml
Is it usable?

The ExtendedRuntime information isn't usable because it only reflects the state of things 5, 10 and 15 minutes ago, not currently, and plus polling that payload on each polling cycle would be very burdensome on the plugin and probably Ecobee's servers.

Please let us know if Ecobee responds favorably to your enhancement request to add current running state information to the API.

Thanks a lot for your help and feedback.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on December 06, 2013, 01:31:20 pm
Watou, thanks for clarification.

I got this reply from Ecobee on runtime status API:
Quote
We will try to have it implemented for the next major release which is slated March 2014 or so.

let's keep our fingers crossed
Title: Re: Plug-in for ecobee thermostats
Post by: watou on January 16, 2014, 02:29:49 pm
Hi all,

I've submitted v0.9 of the Ecobee plugin for Vera to apps.mios.com, and it addresses these three issues in v0.8:

- GetModeTarget always returns AutoChangeOver (https://github.com/watou/vera-ecobee-thermostat/issues/4 (https://github.com/watou/vera-ecobee-thermostat/issues/4))

I forget when this came up, but the device now holds a ModeTarget variable, so any attempt to GetModeTarget will return the ModeTarget.

- Remove all code/doc for multiple app instance restrictions (https://github.com/watou/vera-ecobee-thermostat/issues/5 (http://(https://github.com/watou/vera-ecobee-thermostat/issues/5))

Very early on, there was an API issue with multiple instances to the same app from the same user.  Since those issues are long resolved, I removed the special case code for dealing with it.

- Do not forget tokens on API "auth" errors, only on refresh request (https://github.com/watou/vera-ecobee-thermostat/issues/6 (https://github.com/watou/vera-ecobee-thermostat/issues/6))

Occasionally there is some error using the API, and the v0.8 plugin would eagerly throw away your tokens, forcing you to have to request a new PIN and reenter it at ecobee.com.  This change should stop that irritating process.

If accepted, v0.9 of the plugin should be available in the next few days.  Please let me know if you see anything strange with this update.


Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: redneckTech on January 16, 2014, 03:22:13 pm
Watou,

This is awesome!.  I'm in the final stages of our new house and this plugin swayed me from the Honeywell 8320zw to ecobee.

As if anyone cares, I installed a two-stage heat pump (with dehum) and a single stage upstairs all by myself.  Today I'm ordering one ecobee smart and one smartSI.  Can't wait to throw the switch and start tinkering with this plugin (pray for no smoke).

I can tell you've put a lot of work into this already. I'm a pretty decent coder with no luup experience yet; given I can find the time I'd like to contribute to improving this plugin. Not likely, so I may have to revert the the paypal button. 

Thanks again Watou!
Title: Re: Plug-in for ecobee thermostats in development
Post by: di33266 on January 20, 2014, 05:34:53 pm
Hi guys
You know by any chance if Ecobee Remote Sensor Module (RSM) would report its sensors' reading to the plugin?
Thank you
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 26, 2014, 07:03:29 am
This is awesome!.  I'm in the final stages of our new house and this plugin swayed me from the Honeywell 8320zw to ecobee.

As if anyone cares, I installed a two-stage heat pump (with dehum) and a single stage upstairs all by myself.  Today I'm ordering one ecobee smart and one smartSI.  Can't wait to throw the switch and start tinkering with this plugin (pray for no smoke).

I can tell you've put a lot of work into this already. I'm a pretty decent coder with no luup experience yet; given I can find the time I'd like to contribute to improving this plugin. Not likely, so I may have to revert the the paypal button. 

Thanks very much for the kind words.  Your contributions (ideas, code suggestions or dollars) would be appreciated in any measure!  The ecobee thermostats are high quality, especially for the price, and are generally very well respected among contractors as getting the job done right.  My goal is to have the plugin be a solid and capable performer as well.  I hope it works well for you.

You know by any chance if Ecobee Remote Sensor Module (RSM) would report its sensors' reading to the plugin?

I don't know, but I think that if the thermostat is using the RSM instead of the internal sensor, then that would be the data reported over the API to the plugin.  There is no special path in the API to get data from the RSM, so my guess (and it's only a guess) is that this is opaque to API users, and the remote sensor is just used in place of the internal sensor.

I know you can find this answer from the ecobee technical support people fairly quickly.

watou

P.S. Now that I've turned notify back on for this subject, I expect to reply more quickly in future. (Not sure why it was turned off!)


Title: Re: Plug-in for ecobee thermostats in development
Post by: ttmetro on February 21, 2014, 07:03:35 pm
(Apologies if this question has already been answered somewhere.)

The Ecobee has an optional Zigbee module that in my area can monitor electricity usage reported by my smartmeter.
Question: is this information available in the Vera plugin?

Thanks.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 24, 2014, 07:15:26 am
The Ecobee has an optional Zigbee module that in my area can monitor electricity usage reported by my smartmeter.
Question: is this information available in the Vera plugin?

That information is not currently exposed in the ecobee plugin. I don't know if that information is exposed in the API (away from the computer) but if there were a clean way to pass it along to a device in Vera I would consider adding it.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: AEBogdan on June 02, 2014, 09:51:08 am
Our house wake-up times can be 5am, 6:30am, 8:00am, or 8:30am depending on shifting schedules. I would like to automatically schedule our HVAC morning-on time based on our Google Calender entries by using the Google Calendar Vera plug-in.

I'm now shopping for a Vera compatible thermostat.

Does the Ecobee plug-in have the functionality to easily add, remove, or change set-points, or are automated temperature changes implemented only using timed temperature holds and Away/Home mode toggles?

Is the Ecobee SI thermostat good for this task or do other thermostats (like Nest) have features that might work better for this?

Thanks for your expertise.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 02, 2014, 10:05:52 am
Our house wake-up times can be 5am, 6:30am, 8:00am, or 8:30am depending on shifting schedules. I would like to automatically schedule our HVAC morning-on time based on our Google Calender entries by using the Google Calendar Vera plug-in.

I'm now shopping for a Vera compatible thermostat.

Does the Ecobee plug-in have the functionality to easily add, remove, or change set-points, or are automated temperature changes implemented only using timed temperature holds and Away/Home mode toggles?

Is the Ecobee SI thermostat good for this task or do other thermostats (like Nest) have features that might work better for this?

Thanks for your expertise.

The two main paths for Ecobee are 1) the "Ecobee way" using their native web interface, or 2) the "Vera" way that involves setting the current setpoints when a schedule (or the Google calendar plugin or PLEG or...) dictates. Setting setpoints with the Ecobee plugin sets an indefinite hold from the current program which can be resumed or you can set the setpoint again. 
Both native Ecobee and Vera approaches have many good features. I think native Ecobee might be more obvious than native Nest, while Vera opens more possibilities, but that's all pretty subjective.
Let us know how it goes.
Regards,


watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: integlikewhoa on June 02, 2014, 10:56:21 am
Our house wake-up times can be 5am, 6:30am, 8:00am, or 8:30am depending on shifting schedules. I would like to automatically schedule our HVAC morning-on time based on our Google Calender entries by using the Google Calendar Vera plug-in.

I'm now shopping for a Vera compatible thermostat.

Does the Ecobee plug-in have the functionality to easily add, remove, or change set-points, or are automated temperature changes implemented only using timed temperature holds and Away/Home mode toggles?

Is the Ecobee SI thermostat good for this task or do other thermostats (like Nest) have features that might work better for this?

Thanks for your expertise.

I would stick with a zwave thermostat as thats the easiest way to add a thermostat in vera since natively it is zwave. Any zwave thermostat can do this with PLEG and or calender plugin.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 02, 2014, 02:12:42 pm
I would stick with a zwave thermostat as thats the easiest way to add a thermostat in vera since natively it is zwave. Any zwave thermostat can do this with PLEG and or calender plugin.

A Z-Wave thermostat may be a good match for AEBogdan's purposes, but is there anything about a Z-Wave thermostat compared to a third-party plugin thermostat that makes it easier to automate?  I was unaware of there being those kinds of differences, but I would love to hear about any.

The Nest plugin has a few more automation triggers than a standard Z-Wave thermostat, while the Ecobee plugin allows access to Ecobee-specific functionality.  Another advantage to an Ecobee or Nest is that there is an independent path (web, apps) to monitor and control it from the vendor (as long as local Wi-Fi is on the Internet), whereas a Z-Wave thermostat is only accessible remotely with Vera.  Of course there are theoretical negatives, such as needing working Internet connectivity to a vendor-supplied web service.  It's complicated. :)

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: integlikewhoa on June 02, 2014, 03:32:53 pm
I would stick with a zwave thermostat as thats the easiest way to add a thermostat in vera since natively it is zwave. Any zwave thermostat can do this with PLEG and or calender plugin.

A Z-Wave thermostat may be a good match for AEBogdan's purposes, but is there anything about a Z-Wave thermostat compared to a third-party plugin thermostat that makes it easier to automate?  I was unaware of there being those kinds of differences, but I would love to hear about any.

The Nest plugin has a few more automation triggers than a standard Z-Wave thermostat, while the Ecobee plugin allows access to Ecobee-specific functionality.  Another advantage to an Ecobee or Nest is that there is an independent path (web, apps) to monitor and control it from the vendor (as long as local Wi-Fi is on the Internet), whereas a Z-Wave thermostat is only accessible remotely with Vera.  Of course there are theoretical negatives, such as needing working Internet connectivity to a vendor-supplied web service.  It's complicated. :)

watou

I'm unaware of any more or less that can be done with most of the thermostats. It turns on your a/c or heat and turns it off. (most will handle your multiple stages too but make sure you get the right one for your app)

Now ease of use is where I'm assuming the biggest difference would be. I use PLEG for most if not all my actual automation. When I get home and its night do this this and this and such. The thermostat is only as smart as its sensors and unless the ecobee has more then a humidity and temp sensor (which I havent seen) probley not going to help anyone any more then the rest.
We will take Nest for example. Nest is great for someone without home automation. It doesn't have any more sensors to know if your home or not but it guesses (Vera doesn't guess) if you are depending on previous history. Works great until the day you don't leave the same time you normally do. And if you leave earlier it also doesn't know and runs more then it needs too. It also has schedules just like a z-wave does (which many don't use on the thermostat) but since Vera is controlling it, it's pointless.
So when you get back down to it if Vera is controlling it (which maybe you don't want that, but why need a plugin then) just let vera and its power of multiple temp sensors, motion sensors, outdoor weather plugins, geofencing, google calander, or whatever control it?
As far as backup control, yes a nest or other wifi stat if Vera is down can be controlled over the net threw the manufactures website.
The Net being down is mute as neither option would be able to function, but locally both would function as normal.

I think your point is ease of programming. A nest you pay twice as much or more, hang it on the wall and its does an OK job (guessing) at taking care of it's self. A z-wave you hang it on the wall, but then it does a Great Job but only after you setup PLEG or the like which for some can be difficult.
Title: Re: Plug-in for ecobee thermostats in development
Post by: pmnb on June 02, 2014, 10:13:25 pm
I would stick with a zwave thermostat as thats the easiest way to add a thermostat in vera since natively it is zwave. Any zwave thermostat can do this with PLEG and or calender plugin.

A Z-Wave thermostat may be a good match for AEBogdan's purposes, but is there anything about a Z-Wave thermostat compared to a third-party plugin thermostat that makes it easier to automate?  I was unaware of there being those kinds of differences, but I would love to hear about any.

The Nest plugin has a few more automation triggers than a standard Z-Wave thermostat, while the Ecobee plugin allows access to Ecobee-specific functionality.  Another advantage to an Ecobee or Nest is that there is an independent path (web, apps) to monitor and control it from the vendor (as long as local Wi-Fi is on the Internet), whereas a Z-Wave thermostat is only accessible remotely with Vera.  Of course there are theoretical negatives, such as needing working Internet connectivity to a vendor-supplied web service.  It's complicated. :)

watou

IMHO, the hybrid (Vera Plugin + vendor app/portal) is a great combination.  You get the benefit of using the Vera to orchestrate multi-device automation, but can also leverage additional analytics and visualization features, such as Nest's energy history UI, through their mobile or web app (although I do wish they would provide us with a way of downloading the history, or accessing it through an API).   A quick look at the Ecobee web site shows similar value-added reporting, etc.
Title: Re: Plug-in for ecobee thermostats in development
Post by: AEBogdan on June 09, 2014, 09:28:00 am
Had everything working, but after a reset and restore of Vera (another plug-in locked it up) the Ecobee device lost all communication with the thermostat.

Pressing any button gives an error message like "ecobee: failed to set new hvacMode to off". Tested the thermostat from the Ecobee website and everything works from there, so the thermostat is accessible and working. The "VERA HOME CONTROLLERS" app is still listed as installed. I tried doing the Get PIN process again, but that did not correct the issue.

Is the API interface up and running? If so, is there a way to force a reset of the Ecobee device without deleting and recreating the device or plug-in?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 09, 2014, 09:35:09 pm
Had everything working, but after a reset and restore of Vera (another plug-in locked it up) the Ecobee device lost all communication with the thermostat.

Pressing any button gives an error message like "ecobee: failed to set new hvacMode to off". Tested the thermostat from the Ecobee website and everything works from there, so the thermostat is accessible and working. The "VERA HOME CONTROLLERS" app is still listed as installed. I tried doing the Get PIN process again, but that did not correct the issue.

Is the API interface up and running? If so, is there a way to force a reset of the Ecobee device without deleting and recreating the device or plug-in?

I don't know what state things are in after the reset and restore of Vera, but I do know that a Vera that is occasionally crashing can negatively affect the Ecobee plugin, in this way: The Ecobee API frequently requires its authorization tokens to be refreshed, and the plugin saves them in state variables.  But since Vera does not write state variables to flash memory when requested, but instead every few minutes, it's possible that your Vera crashed before the latest tokens were written.  So when your Vera restarts, the Ecobee plugin attempts to use expired tokens.

I have always been able to recover from this condition by pressing the Get PIN button and then entering that new PIN in the ecobee.com portal.

If your Vera's Luup process is routinely crashing for whatever reason, this situation will probably recur and you will have to both press the Get PIN button, and then enter that new PIN into your ecobee.com portal account, per the README.

Please let us know if this clears up the issue for you.

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: AEBogdan on June 10, 2014, 10:01:05 am
I tried the pin update this morning and Vera became stuck in an infinite loop when I pressed Reload. Of course, without some sort of debugging information I can't be sure what caused the lockup.

I did a Vera reset, loaded a backup from yesterday, and immediately reset the Ecobee pin. This time everything, including the thermostat, is fully functional again. I'll remember to immediately redo the pin if I need to restore from a backup in the future.

Is there any way for the plug-in to determine when a new pin is necessary and display a LUUP status message or send out a notification? Does the API send back an error code, or does it simply stop responding?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2014, 10:13:01 am
Is there any way for the plug-in to determine when a new pin is necessary and display a LUUP status message or send out a notification? Does the API send back an error code, or does it simply stop responding?

I am unable to fully test a code change at the moment, but if you were to download the file I_Ecobee1.xml from your Vera (or from here: https://raw.githubusercontent.com/watou/vera-ecobee-thermostat/master/src/I_Ecobee1.xml  (https://raw.githubusercontent.com/watou/vera-ecobee-thermostat/master/src/I_Ecobee1.xml)) and change line 506 from:

Code: [Select]
         log("Unable to getThermostatSummary; skipping status update.")

to

Code: [Select]
         task("Unable to getThermostatSummary; skipping status update.")

and then upload the changed file and restart the Vera, you ought to see the problem in Vera's web UI when it occurs.  Please let me know if this works for you.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 13, 2014, 08:54:14 pm
I've just submitted v1.0 of the Ecobee plugin for approval. 
Please see the full README at http://cocu.la/vera/ecobee/README.md (http://cocu.la/vera/ecobee/README.md).

I expect the new version will be made available some time next week.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: gkotak on June 14, 2014, 07:38:44 pm
Hello watou, thank you for posting this. Based on this plug-in I am about to purchase the ecobee thermostat. I wanted to confirm, does this work with any of the WIFI thermostats? I am thinking of purchasing the Smart Si thermostat that you can find here - http://www.amazon.com/ecobee-Thermostat-Heat-2-NON-Touch-Screen/dp/B008F40R4C/ref=cm_cd_al_qh_dp_i

Regards,
Gaurav
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 16, 2014, 06:21:00 am


does this work with any of the WIFI thermostats? I am thinking of purchasing the Smart Si thermostat

Hello!
The plugin ought to work with any Ecobee wifi thermostat, but I did all development and test with a Smart Si thermostat so I know empirically that it works. 

Regards,

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on June 19, 2014, 11:32:30 pm
I've just submitted v1.0 of the Ecobee plugin for approval. 

Made possible by a recent update to the Ecobee API, the thermostat device now reports the current running state ...

I expect the new version will be made available some time next week.


Thank you Watou!
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on June 27, 2014, 11:55:30 am
Watou,

I just upgraded to v.1 and noticed that variables on advanced tab seems not to be updating until Vera's reload.

For example, I changed thermostat to Off but variables still display old status after 30 minutes.

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 27, 2014, 01:50:50 pm
I just upgraded to v.1 and noticed that variables on advanced tab seems not to be updating until Vera's reload.

For example, I changed thermostat to Off but variables still display old status after 30 minutes.

I just performed the same steps here, and what I saw was the standard Vera behavior where the variables on the Advanced tab do not refresh automatically.  You have to refresh your browser (Ctrl+R or Command+R for example), and then check the Advanced tab again, and then you will see the correct values.

Please reply to make sure I understood your report correctly, and that my advice worked/didn't work.  Thanks!

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on June 27, 2014, 02:48:05 pm
..the standard Vera behavior where the variables on the Advanced tab do not refresh automatically.

You are correct.
I was not aware that Vera's web script does not refresh Advance tab variables automatically, like it does with widgets display values.

Separately, does MessageText function sets an alarm?
I want to set an thermostat alarm if AC is on and a door/window is open for more then several minutes.
Any suggestions how to use MessageText with PLEG to achieve this?

Thanks
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 27, 2014, 05:01:01 pm
Separately, does MessageText function sets an alarm?
I want to set an thermostat alarm if AC is on and a door/window is open for more then several minutes.
Any suggestions how to use MessageText with PLEG to achieve this?

I haven't used PLEG, but if you want to make a message appear on your Ecobee's screen and you can perform a luup.call_action from PLEG, then check this example:
http://forum.micasaverde.com/index.php/topic,13836.msg121293.html#msg121293 (http://forum.micasaverde.com/index.php/topic,13836.msg121293.html#msg121293)
Title: Re: Plug-in for ecobee thermostats in development
Post by: Envirogreen on June 29, 2014, 05:43:50 pm
Couple of questions

Has anyone used this plugin with the irule mi Casa module?  Does it work the same as if it was a zwave tstat?

When buying the ecobee any extra module needed to make this work?

Also does it work with Veralite as well as Vera 3?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 30, 2014, 05:48:23 pm
Has anyone used this plugin with the irule mi Casa module?  Does it work the same as if it was a zwave tstat?

I don't know anything about irule, but I do know that the plugin creates thermostat devices with the same device and service types as Z-Wave thermostats, so it "should work."  It adds new device and service types for non-thermostat devices, but that shouldn't be relevant.

When buying the ecobee any extra module needed to make this work?

Aside from working Internet access and whatever the basic thermostat needs to get onto the Internet, I don't think it needs anything else.

Also does it work with Veralite as well as Vera 3?

Yes, but if your Veralite is on the verge of using up its precious memory, this plugin, like most, would create problems.  I've not heard of an out-of-memory situation with the plugin, but the Veralite can become memory constrained, depending on what you're doing.  Otherwise the plugin ought to work the same on Veralite and Vera 3.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 08, 2014, 11:58:59 pm
For anyone attempting to use the Ecobee plugin on UI7, attached is a file that ought to fix the problem in v1.0 of the plugin, where the plugin does a bad job of detecting its required minimum Vera version, and gives up.

Based on a system with the v1.0 plugin installed, please download the attached file, go to Apps -> Develop Apps -> Luup files, check the Restart after upload box, and upload this file.  (Or if this is different in UI7, the equivalent steps there.)

Please report if this proposed fix resolves the mistaken message that 1.5.408 or later is required to run.  I will submit a v1.1 of the plugin to the app store if this fix works.

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: jasperpants on September 15, 2014, 08:35:13 pm
Hey, it appears to fix the error relating to the software version.

However, unlike other devices, I cannot select which room to put it in once it's installed.  I've tried the 4 devices it created, ecobee, Temperature, Humidity, and EventClimate but it's not showing up.

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on September 17, 2014, 07:52:45 pm
However, unlike other devices, I cannot select which room to put it in once it's installed.  I've tried the 4 devices it created, ecobee, Temperature, Humidity, and EventClimate but it's not showing up.

I am still waiting for some official documentation on what changes UI5 plugins need in order to work correctly in UI7, so I don't know why this is happening.  But I did read that you can manually change the device's room_num property on the Advanced tab and after a reload/refresh, the devices should end up in the proper rooms.  I haven't tried this myself as I don't have a UI7 system to test with and I cannot switch to UI7 on my Vera.  Sorry I can't be more help.

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: AEBogdan on September 21, 2014, 11:57:19 am
Tip on using the Ecobee plug-in 1.0 with UI7 (1.7.318):

The main device in the dashboard has a [Get PIN] button. This button does not work. It will give you a "Can't Detect Device" error.

To get a PIN you need to instead press the Settings button [>], choose the CONTROL option, and use the [Get PIN] button that displays here. This button works.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on September 21, 2014, 12:21:49 pm
Thank you very much for sharing that info, Al.  I hope there will be official information available soon on how to make third-party plugins work correctly on UI7.  The Nest and Ecobee plugins both have issues on UI7, but I am totally blind as to what to do about it.

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: laaf2005 on November 04, 2014, 11:59:53 pm
Pin support was added to ecobee 3

Sent from my SHIELD Tablet using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: jswnhart on November 23, 2014, 05:16:11 pm
Even though I have auto update enabled, still at version 0.7 (on UI5) and cannot see a newer version when I search the install apps page. Any ideas how to get past this?  Thanks.
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on December 03, 2014, 11:16:07 am
Watou,

Thanks again for your great plugin.

I'm using your plugin to automate many custom features not available in ecobee directly.
For example, I'm keeping my vacation home temp 40F (tstat min temp is limited to 45F).
But this can be dangerous if tstat looses communication with Vera in OFF position.
What would be a good test to notify if this occurs?
To check ecobee device status for valid token and CommFailure?

Thanks,
Theal

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on December 03, 2014, 12:50:23 pm
I'm using your plugin to automate many custom features not available in ecobee directly.
For example, I'm keeping my vacation home temp 40F (tstat min temp is limited to 45F).
But this can be dangerous if tstat looses communication with Vera in OFF position.
What would be a good test to notify if this occurs?
To check ecobee device status for valid token and CommFailure?

On every poll, the main plugin device will have its "status" variable (using service ID urn:ecobee-com:serviceId:Ecobee1) set to "0" if there is a communication problem (plugin to API) or "1" if there isn't.  It will only set the variable if it changes from its existing value.  For good measure, you may also want to check the thermostat device's "LastUpdate" variable (service ID urn:micasaverde-com:serviceId:HaDevice1) to be sure that it represents a timestamp that is not different from the current timestamp by too many seconds (your choice).  Lastly, "CommFailure" will be set to "1" if the API reports that it cannot communicate with the thermostat itself, or "0" if it reports that the thermostat is connected.  Together, these ought to give you a high level of confidence that you are getting a reliable status.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on December 03, 2014, 01:14:47 pm
Thank you watou,

Adding "LastUpdate" check to API status and  CommFailure is a great idea.
Just need to figure out how to compare Epoch GMT time with Vera's time.
Title: Re: Plug-in for ecobee thermostats in development
Post by: djrakso on December 05, 2014, 12:12:53 pm
A few question on ecobee3:
- If the internet is down for awhile (lets say 2-3 weeks) will the ecobee3 unit still know its tasks and continue without interruptions?
- Could I connect the ecobee3 device to VeraEdge without needing a internet connect, if so how?
Title: Re: Plug-in for ecobee thermostats in development
Post by: Sig on December 06, 2014, 06:23:36 pm
The Ecobee plugin is working great for both of my thermostats (primary & weekend home).  I have a question (and wasn't able to find the answer via search)...

I have a "Leaving" scene I use when I leave my weekend home (basically shuts everything down and sets thermostat to more extreme setpoints since the home will be unoccupied for an extended period).  When I use the plugin to set those temperature setpoints, that is working fine.  And my Ecobee thermostat shows "62-85 and Holding" as you would expect.  My question...what mode is that hold?  Right now, my Ecobee is configured to ask me what kind of hold should be used whenever I override the temperature (i.e. "Until I'm home", "Until next schedule Event", "Until I change it.").  Which of these types of hold is the Plugin temperature set using (I'm hoping it's the "Until I Change It" which is essentially a true hold).  Unfortunately, the Ecobee display doesn't tell you that - it only tells you its holding, but not until _something_ happens, if that makes sense.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on December 07, 2014, 03:08:20 am
The Ecobee plugin is working great for both of my thermostats (primary & weekend home).  I have a question (and wasn't able to find the answer via search)...

I have a "Leaving" scene I use when I leave my weekend home (basically shuts everything down and sets thermostat to more extreme setpoints since the home will be unoccupied for an extended period).  When I use the plugin to set those temperature setpoints, that is working fine.  And my Ecobee thermostat shows "62-85 and Holding" as you would expect.  My question...what mode is that hold?  Right now, my Ecobee is configured to ask me what kind of hold should be used whenever I override the temperature (i.e. "Until I'm home", "Until next schedule Event", "Until I change it.").  Which of these types of hold is the Plugin temperature set using (I'm hoping it's the "Until I Change It" which is essentially a true hold).  Unfortunately, the Ecobee display doesn't tell you that - it only tells you its holding, but not until _something_ happens, if that makes sense.

Hi @Sig,

The plugin uses the "indefinite" ("Until I change it.") hold type when changing setpoints, fan mode, etc., meaning it won't change until you Resume the program or override it with a new hold.  Using "indefinite" is hard-coded into the plugin, as opposed to the other hold types of "holdHours", "nextTransition", or "dateTime".  Someone who wanted the opposite of what you want, for example to have the hold expire when the schedule transitions to a new climate/comfort setting, would currently have to replace a few "indefinite" strings in I_Ecobee1.xml with "nextTransition" strings.

The configuration to say "always ask" is local to the thermostat itself, and of course the plugin has no way to ask you anyway. :)

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: Sig on December 07, 2014, 02:51:17 pm
Thanks @watou.  That makes complete sense and is what I was hoping for. 
Title: Re: Plug-in for ecobee thermostats in development
Post by: lavoyka on December 09, 2014, 04:24:34 pm
Anyone else install the Ecobee3 and have temperature change control?  It gives the correct temp and humidity, but I cannot change the temperature in the vera. When I click the up or down arrows, it does nothing. Anyone else have this problem??
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on December 09, 2014, 06:15:32 pm
Anyone else install the Ecobee3 and have temperature change control?  It gives the correct temp and humidity, but I cannot change the temperature in the vera. When I click the up or down arrows, it does nothing. Anyone else have this problem??

I just tried to change the heat setpoint up one degree on my ecobee3 via the plugin and it worked.  I verified in the new web portal at ecobee.com.  I then cleared the hold and it reverted to the schedule as expected.  This was on Vera UI5 1.5.622. 

Is the main ecobee device showing a grey or green "bee" logo?  A grey one means that your tokens have expired and need to request and enter a new PIN.

I believe that there are remaining issues with UI7.  I was given instructions on how to change the icons and make the one plugin work against UI5 or UI7 (by duplicating a number of JSON and XML files and selectively using one set or the other), but none of those instructions dealt with non-working setpoint controls in the UI.  I am still awaiting instructions (or a pointer to documentation) that will help me understand how to change the plugin to work in UI7, but I was also told that there are outstanding UI bugs in the firmware for thermostat plugins.  I don't have an ETA.

If you are using and must use UI7, I suggest a mobile app like AutHomation (Android) or many other third-party solutions as a means of interacting with the plugin devices.

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: lavoyka on December 10, 2014, 03:42:36 pm
I don't see any 'bee logo' on the vera.
see attachment.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on December 10, 2014, 03:53:09 pm
I don't see any 'bee logo' on the vera.
see attachment.
You are on UI7, and I've been told that it has UI problems by Vera personnel, and that there will be fixes and further UI7 plugin developer documentation.  I interpret all I've been told that fixing the setpoint UI problems is not in my control.  I've been shown how to fix icon display, but I'm holding off on that cosmetic change until I can target a firmware that I know will be acceptable.  If anyone has a better set of facts, please let me know. Thanks.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on December 12, 2014, 11:25:48 am

On every poll, the main plugin device will have its "status" variable (using service ID urn:ecobee-com:serviceId:Ecobee1) set to "0" if there is a communication problem (plugin to API) or "1" if there isn't.  It will only set the variable if it changes from its existing value.  For good measure, you may also want to check the thermostat device's "LastUpdate" variable (service ID urn:micasaverde-com:serviceId:HaDevice1) to be sure that it represents a timestamp that is not different from the current timestamp by too many seconds (your choice).  Lastly, "CommFailure" will be set to "1" if the API reports that it cannot communicate with the thermostat itself, or "0" if it reports that the thermostat is connected.  Together, these ought to give you a high level of confidence that you are getting a reliable status.

watou

watou,

I implemented your suggestions into a custom alarm to monitor Ecobee on-line status and it worked well.
Yesterday my alarm notified me that API was down for a couple hours.  Vera status box did not show any errors but urn:ecobee-com:serviceId:Ecobee1 Status was 0 and Vera/Ecobee communication was down.  I manually re-registered the plugin with a new PIN and Ecobee was back on-line.
However, today API is down again for 10 hours, also with no error on Vera web interface.
Any insight on what is going wrong?

Thank you,
theal
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on December 12, 2014, 11:49:40 am

On every poll, the main plugin device will have its "status" variable (using service ID urn:ecobee-com:serviceId:Ecobee1) set to "0" if there is a communication problem (plugin to API) or "1" if there isn't.  It will only set the variable if it changes from its existing value.  For good measure, you may also want to check the thermostat device's "LastUpdate" variable (service ID urn:micasaverde-com:serviceId:HaDevice1) to be sure that it represents a timestamp that is not different from the current timestamp by too many seconds (your choice).  Lastly, "CommFailure" will be set to "1" if the API reports that it cannot communicate with the thermostat itself, or "0" if it reports that the thermostat is connected.  Together, these ought to give you a high level of confidence that you are getting a reliable status.

watou

watou,

I implemented your suggestions into a custom alarm to monitor Ecobee on-line status and it worked well.
Yesterday my alarm notified me that API was down for a couple hours.  Vera status box did not show any errors but urn:ecobee-com:serviceId:Ecobee1 Status was 0 and Vera/Ecobee communication was down.  I manually re-registered the plugin with a new PIN and Ecobee was back on-line.
However, today API is down again for 10 hours, also with no error on Vera web interface.
Any insight on what is going wrong?

Thank you,
theal
My two instances of the plugin seem to be running fine on firmware 1.5.622. I know of one ugly problem that shows if your LuaUPnP process is often crashing: when the plugin gets refreshed auth tokens, it saves them to device variables, but they aren't written to disk except every few minutes (I believe so as to avoid wearing out the flash memory). If the process crashes (due to some other issue outside the plugin), then when it restarts, the plugin will try to use the old tokens. On a Vera that doesn't have a crashing problem, the fresh tokens are written to disk properly and so it will use the correct tokens on restart.  Could anything like this be happening in your case?

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on December 12, 2014, 12:27:42 pm
Quote
My two instances of the plugin seem to be running fine on firmware 1.5.622. I know of one ugly problem that shows if your LuaUPnP process is often crashing: when the plugin gets refreshed auth tokens, it saves them to device variables, but they aren't written to disk except every few minutes (I believe so as to avoid wearing out the flash memory). If the process crashes (due to some other issue outside the plugin), then when it restarts, the plugin will try to use the old tokens. On a Vera that doesn't have a crashing problem, the fresh tokens are written to disk properly and so it will use the correct tokens on restart.  Could anything like this be happening in your case?

watou

I'm running firmware 1.5.622 on VeraLight.
How can I check for LuaUPnP crash?
I did a couple soft reboot and "reload" but that did not help. I'm currently away so I can't do hard reboot.
I did noticed that during a "reload" there is no notification that Ecobee plugin being initialized.  Could this be a problem and how I can troubleshoot this?

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on December 12, 2014, 01:57:32 pm



I'm running firmware 1.5.622 on VeraLight.
How can I check for LuaUPnP crash?
I did a couple soft reboot and "reload" but that did not help. I'm currently away so I can't do hard reboot.
I did noticed that during a "reload" there is no notification that Ecobee plugin being initialized.  Could this be a problem and how I can troubleshoot this?

If the problem was like the one I described, it can be corrected each time by getting and entering a new PIN, which can be done remotely. This would suggest the crashing problem if the token keeps failing. 

I think the best thing is to look at the logs to see what is going on, when you are able to collect one right after startup (and scrub any private information). If you add LogLevel 35 to the list in cmh.conf, you will get debug output as well.

There are some tools that can help determine internal metrics like memory, CPU, etc., but there are forum participants who know a lot more than I about them.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on January 02, 2015, 03:04:26 pm
@watou, have they exposed the sensors yet, now that they are in their dashboard?  Looking forward to taking advantage of those in vera! 
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 03, 2015, 08:14:43 am
@watou, have they exposed the sensors yet, now that they are in their dashboard?  Looking forward to taking advantage of those in vera!

I  am also looking forward to seeing those exposed in the API, but I don't believe they are there yet.  I follow this thread on their support forum:

http://developer.ecobee.com/api/topics/access-to-ecobee3-sensor-data-via-api (http://developer.ecobee.com/api/topics/access-to-ecobee3-sensor-data-via-api)

Please ping me if you hear of a positive change in status.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on January 03, 2015, 12:43:21 pm
@watou, have they exposed the sensors yet, now that they are in their dashboard?  Looking forward to taking advantage of those in vera!

I  am also looking forward to seeing those exposed in the API, but I don't believe they are there yet.  I follow this thread on their support forum:

http://developer.ecobee.com/api/topics/access-to-ecobee3-sensor-data-via-api (http://developer.ecobee.com/api/topics/access-to-ecobee3-sensor-data-via-api)

Please ping me if you hear of a positive change in status.

watou

Cool... will do!
Title: Re: Plug-in for ecobee thermostats in development
Post by: mcvflorin on January 05, 2015, 11:08:59 am
One possible workaround for variables losing their value because of a LuaUPnP crash is to save the value in 2 places: in the state variable, and in a file in /tmp (which is in the RAM), as backup. And, when the plugin starts, check if the value from the variable is different than the one in the file. If it is, load the value from the file, and update the state variable. Since the files will be saved in the RAM, they will disappear when the Vera reboots, but that happens a lot less often than a LuaUPnP crash.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 05, 2015, 11:14:01 am
One possible workaround for variables losing their value because of a LuaUPnP crash is to save the value in 2 places: in the state variable, and in a file in /tmp (which is in the RAM), as backup. And, when the plugin starts, check if the value from the variable is different than the one in the file. If it is, load the value from the file, and update the state variable. Since the files will be saved in the RAM, they will disappear when the Vera reboots, but that happens a lot less often than a LuaUPnP crash.
Good suggestion; thanks for that idea.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: djbisme on January 07, 2015, 10:32:05 pm
Hello-
I'm new to Vera, and also have a new EcoBee3 installed.  The Ecobee app in Vera lists ver 1.0, and I can't figure out how to update to 1.1.  I have the update box checked, but it has been sitting at 1.0 for a week.
Thanks.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 09, 2015, 09:26:35 am
Hello-
I'm new to Vera, and also have a new EcoBee3 installed.  The Ecobee app in Vera lists ver 1.0, and I can't figure out how to update to 1.1.  I have the update box checked, but it has been sitting at 1.0 for a week.
Thanks.
Sorry I'm on my phone with limited bandwidth, but there is a URL you can enter that will force an update. It's *like* what's described here: http://forum.micasaverde.com/index.php?topic=18818.msg142272#msg142272 but would apply to the Ecobee plugin's ID. Sorry I'm out of position to give better advice atm.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: Sig on January 12, 2015, 07:49:15 pm
I'm continuing to have a problem changing setpoints via the Ecobee plugin.  I really only control the thermostat through Vera for a couple of scenes I setup for when I travel, which is often.  I have a scene that shuts down various electronic components, turns off my standard evening lighting schedule, etc. and also changes the cooling & heating setpoints to a wider range, similar to what you'd set when leaving on vacation.  I have a converse scene that resets everything to normal that I typically fire off before I get home.  My problem is with the "Away" scene.  It always seems to only change ONE of the setpoints (typically the heat) even though I've selected a different setpoint for both heating & cooling.  I've tried using a delay, thinking the other activities in the scene were somehow kluging up the thermostat action, but that hasn't helped either.

Strangely, if I instead have my "Away" scene simply change to "Away" mode using the plugin, the setpoints change, but they change to lower/higher values than the Away mode I have set on the thermostat.  In other words, my standard Away settings on the thermostat are 62/82 for cooling/heating.  When I click the "Away" button in Vera (or have my scene do that), the setpoints change to 58/86.  It seems to be getting those values from somewhere other than the thermostat configuration.  Ultimately, that's OK, this achieves my desired result.  But I am curious about it, because I initially didn't use this setting thinking it would only use my standard Away setpoints, which aren't wide enough for when I travel for extended periods.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 13, 2015, 12:33:04 am
I'm continuing to have a problem changing setpoints via the Ecobee plugin.  I really only control the thermostat through Vera for a couple of scenes I setup for when I travel, which is often.  I have a scene that shuts down various electronic components, turns off my standard evening lighting schedule, etc. and also changes the cooling & heating setpoints to a wider range, similar to what you'd set when leaving on vacation.  I have a converse scene that resets everything to normal that I typically fire off before I get home.  My problem is with the "Away" scene.  It always seems to only change ONE of the setpoints (typically the heat) even though I've selected a different setpoint for both heating & cooling.  I've tried using a delay, thinking the other activities in the scene were somehow kluging up the thermostat action, but that hasn't helped either.

I can think of two possibilities.  One possibility is that you are using UI7, which I last knew to have strangely "re-wired" setting setpoints to ignore which setpoint you are asking to change, but instead changes only the setpoint of the current HVAC mode.  I and others view this as a fatal bug.

The other possibility is a timing issue in the plugin, regardless of UI5 or UI7.  When setting a hold via the Ecobee API, it needs to know both the desired heat and cool setpoint on the API call, but since the thermostat device sets each individually, it queries the Vera device for the current state of the other setpoint's value when calling the Ecobee API.  If you don't wait long enough for the local value of the last setpoint change to get updated in the Vera device (maybe more than 5 seconds), the next hold change will send the old setpoint value with the new hold request, effectively losing the first change request.  So it might work better if your automation can wait long enough for the first setpoint change request to be reflected back in Vera, before making the second setpoint change request.

Strangely, if I instead have my "Away" scene simply change to "Away" mode using the plugin, the setpoints change, but they change to lower/higher values than the Away mode I have set on the thermostat.  In other words, my standard Away settings on the thermostat are 62/82 for cooling/heating.  When I click the "Away" button in Vera (or have my scene do that), the setpoints change to 58/86.  It seems to be getting those values from somewhere other than the thermostat configuration.  Ultimately, that's OK, this achieves my desired result.  But I am curious about it, because I initially didn't use this setting thinking it would only use my standard Away setpoints, which aren't wide enough for when I travel for extended periods.

The "Away" setpoint values are controlled via the "QuickSave" setback and setforward relative values in the Ecobee web UI.  So "Away" mode lowers the heat setpoint and increases the cool setpoint values by the deltas you control in the native web UI, and sets an indefinite hold for both setpoints, each offset by their QuickSave deltas.  "Home" simply cancels the hold.  If you can increase these relative values in the Ecobee web UI to a wider range to meet your "away" scene needs, then it's probably the more reliable approach than working around the issues I described for setting individual setpoints.

Hope this helps,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on January 13, 2015, 10:06:17 am
One possible workaround for variables losing their value because of a LuaUPnP crash is to save the value in 2 places: in the state variable, and in a file in /tmp (which is in the RAM), as backup. And, when the plugin starts, check if the value from the variable is different than the one in the file. If it is, load the value from the file, and update the state variable. Since the files will be saved in the RAM, they will disappear when the Vera reboots, but that happens a lot less often than a LuaUPnP crash.
Good suggestion; thanks for that idea.

watou

+1
Title: Re: Plug-in for ecobee thermostats in development
Post by: crimsondr on January 14, 2015, 03:31:16 pm
I have a Ecobee Smart SI from my hydro provider.  Can this plugin allow me to control the thermostat from my VeraEdge?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 14, 2015, 03:43:42 pm
I have a Ecobee Smart SI from my hydro provider.  Can this plugin allow me to control the thermostat from my VeraEdge?

If you can see the thermostat from your own personal login at ecobee.com, you can use the Vera plugin for Ecobee to control it.  There are unpleasant issues with UI7, but it will work, and look better from one of the mobile apps, like AutHomation HD for instance.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: crimsondr on January 14, 2015, 03:47:19 pm
Thanks, yes I can see my thermostat from ecobee.com. Does it matter which mobile app I use? I was thinking of using autovera.

Thanks.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 14, 2015, 03:56:44 pm
Thanks, yes I can see my thermostat from ecobee.com. Does it matter which mobile app I use? I was thinking of using autovera.

You can try different mobile apps until you find the one you like -- I only know what the plugin's devices look from HomeWave against UI5 and AutHomation HD against UI5 and UI7.  It might look fine from AutoVera!

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: crimsondr on January 15, 2015, 10:02:50 am
I successfully added the ecobee plugin to my UI7 dashboard.  However, the Thermostat does not show the programmed temperature.  It's blank.  Is this normal?

Attached is a screenshot.

Thanks.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 15, 2015, 10:38:43 am
I successfully added the ecobee plugin to my UI7 dashboard.  However, the Thermostat does not show the programmed temperature.  It's blank.  Is this normal?

I believe that this is one of the "unpleasant" aspects of UI7 as it currently stands.  I was given explanations that plugins cannot make thermostat devices that look like the built-in devices, as they used to be able to in UI5.  I would quote what I was told, but it would be too difficult to capture the context of my email dialogues.  And as to why this is the case in UI7, I definitely do not understand.

Mobile apps are more likely to properly depict the important values than the native UI7 web interface.  I know things look pretty good in AutHomation HD on Android, for instance, and probably on other mobile apps, too.

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: crimsondr on January 15, 2015, 10:45:59 am
Thanks for the quick responses.  I'll have to try out AutHomatioHD.  Currently I've only installed AutoVera.
Title: Re: Plug-in for ecobee thermostats in development
Post by: ohecht on February 15, 2015, 12:43:19 am
Never mind...I figured it out once I finally found the "My Apps" section of the Ecobee portal...I was trying to use it as if I was registering another thermostat.

I just installed an Ecobee 3 and downloaded this plug-in, but the ecobee.com site will not accept any of the 4-digit PINs...I've tried many of them.  Am I missing something?

I get an error message of "the registration code you have entered is incorrect" each time.

Thanks in advance,

Olivier
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 15, 2015, 12:57:41 am
Ecobee has different kinds of PINs, and you are possibly trying to enter the PIN into the wrong place.  In the ecobee.com web interface, you have to slide in the menu on the right edge of the screen and choose the MY APPS section.  There you can enter the PIN that the plugin generates to authorize the plugin to access your account.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: ohecht on February 15, 2015, 01:07:07 am
Thanks watou...I just noticed that when I went back to the Ecobee portal...I'll try the plugin now...
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on March 24, 2015, 10:36:27 am
Ecobee has different kinds of PINs, and you are possibly trying to enter the PIN into the wrong place.  In the ecobee.com web interface, you have to slide in the menu on the right edge of the screen and choose the MY APPS section.  There you can enter the PIN that the plugin generates to authorize the plugin to access your account.

watou

Hey Watou...

this has happened twice in the last couple of weeks... no idea why.  On the Ecobee site, it still shows the app listed .. but the icon on Vera is greyed out.  Getting a new PIN always works, but i have to keep checking the icon color to ensure it's running properly.

two questions.  One, any idea why this is happening?  And two, if there isn't an easy fix, is there a way to send an alert that would say when the connection is lost?

thanks!
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 24, 2015, 01:09:32 pm
this has happened twice in the last couple of weeks... no idea why.  On the Ecobee site, it still shows the app listed .. but the icon on Vera is greyed out.  Getting a new PIN always works, but i have to keep checking the icon color to ensure it's running properly.

two questions.  One, any idea why this is happening?  And two, if there isn't an easy fix, is there a way to send an alert that would say when the connection is lost?

I've been noticing this new issue lately myself but haven't been checking the logs to see why it's been happening. The main Ecobee device has a "status" variable that is either 0 or 1; you could automate off of that -- it's what makes the icon go grey or green. I will check my logs once I'm in a position to and let you know if I can spot anything.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on March 24, 2015, 07:34:00 pm
this has happened twice in the last couple of weeks... no idea why.  On the Ecobee site, it still shows the app listed .. but the icon on Vera is greyed out.  Getting a new PIN always works, but i have to keep checking the icon color to ensure it's running properly.

two questions.  One, any idea why this is happening?  And two, if there isn't an easy fix, is there a way to send an alert that would say when the connection is lost?

I've been noticing this new issue lately myself but haven't been checking the logs to see why it's been happening. The main Ecobee device has a "status" variable that is either 0 or 1; you could automate off of that -- it's what makes the icon go grey or green. I will check my logs once I'm in a position to and let you know if I can spot anything.

watou

ok... thanks. 

No idea how to capture and automate off that variable.  :)
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 25, 2015, 12:56:24 am
No idea how to capture and automate off that variable.  :)

You could create a schedule that runs every x minutes, and runs this luup code as a test:

Code: [Select]
local status = luup.variable_get("urn:ecobee-com:serviceId:Ecobee1", "status", 43);
return 0 == tonumber(status);

(replace 43 which your main ecobee device ID), and then choose an automation trigger action.  Also consider PLEG as an alternative to automate with this device variable.

Title: Re: Plug-in for ecobee thermostats in development
Post by: Sig on April 25, 2015, 08:25:52 pm
I'm consistently losing the connection between Vera and my Ecobee, and have to request a new PIN and re-register the app in the Ecobee Web UI every time.  It appears this is happening to others as well.  Any thoughts on what might be causing this?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on April 25, 2015, 09:03:06 pm
I'm consistently losing the connection between Vera and my Ecobee, and have to request a new PIN and re-register the app in the Ecobee Web UI every time.  It appears this is happening to others as well.  Any thoughts on what might be causing this?

The two possible reasons I'm aware of for this class of problem are 1) your LuaUPnP process is frequently crashing, and the frequently updated auth tokens are getting lost before being saved permanently to flash memory, so when the process restarts it tries to use expired tokens, or 2) there is a service problem at ecobee.com.  If your LuaUPnP.log file is showing frequent crashes and restarts, it's more likely to be the first possibility.

From here, I have two plugin instances on one UI5 Vera, and two instances of the OpenHAB binding on another system, and I've not seen any connectivity/token problems recently.

Hope this helps,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on April 27, 2015, 04:55:48 pm
this has happened twice in the last couple of weeks... no idea why.  On the Ecobee site, it still shows the app listed .. but the icon on Vera is greyed out.  Getting a new PIN always works, but i have to keep checking the icon color to ensure it's running properly.

two questions.  One, any idea why this is happening?  And two, if there isn't an easy fix, is there a way to send an alert that would say when the connection is lost?

I've been noticing this new issue lately myself but haven't been checking the logs to see why it's been happening. The main Ecobee device has a "status" variable that is either 0 or 1; you could automate off of that -- it's what makes the icon go grey or green. I will check my logs once I'm in a position to and let you know if I can spot anything.

watou

I asked in another thread but I figured I would inquire here. When do you anticipate releasing the new Ecobee Plugin? I am considering an Ecobee3 and would likely want to take advantage of the additional Ecobee temp sensors that should be usable with the latest Ecobee firmware release. I am hoping those sensor will be useful in Vera so I can create zones that control Z-Wave Dampers for upstairs and downstairs. Also would like to know that Ecobee 3 is good and stable on VeraEdge before  I make the Ecobee purchase.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on April 27, 2015, 07:08:53 pm
this has happened twice in the last couple of weeks... no idea why.  On the Ecobee site, it still shows the app listed .. but the icon on Vera is greyed out.  Getting a new PIN always works, but i have to keep checking the icon color to ensure it's running properly.

two questions.  One, any idea why this is happening?  And two, if there isn't an easy fix, is there a way to send an alert that would say when the connection is lost?

I've been noticing this new issue lately myself but haven't been checking the logs to see why it's been happening. The main Ecobee device has a "status" variable that is either 0 or 1; you could automate off of that -- it's what makes the icon go grey or green. I will check my logs once I'm in a position to and let you know if I can spot anything.

watou

I asked in another thread but I figured I would inquire here. When do you anticipate releasing the new Ecobee Plugin? I am considering an Ecobee3 and would likely want to take advantage of the additional Ecobee temp sensors that should be usable with the latest Ecobee firmware release. I am hoping those sensor will be useful in Vera so I can create zones that control Z-Wave Dampers for upstairs and downstairs. Also would like to know that Ecobee 3 is good and stable on VeraEdge before  I make the Ecobee purchase.

Sorry I've been remiss in replying.  Now that the OpenHAB integration works with ecobee3's remote sensors, I will be upgrading the Vera plugin as well.  I will either be able to finish it before the 4th of May, or failing that it will be closer to the end of May.  Sorry for the delay.  I know it's in demand and I want to contribute it.  The ecobee3 is an excellent thermostat and I think it's worth the money (if you are one to appreciate this sort of thing).

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on April 27, 2015, 07:56:22 pm
Sorry I've been remiss in replying.  Now that the OpenHAB integration works with ecobee3's remote sensors, I will be upgrading the Vera plugin as well.  I will either be able to finish it before the 4th of May, or failing that it will be closer to the end of May.  Sorry for the delay.  I know it's in demand and I want to contribute it.  The ecobee3 is an excellent thermostat and I think it's worth the money (if you are one to appreciate this sort of thing).

Regards,
watou

No apologies necessary  :-)
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on April 27, 2015, 09:05:24 pm
this has happened twice in the last couple of weeks... no idea why.  On the Ecobee site, it still shows the app listed .. but the icon on Vera is greyed out.  Getting a new PIN always works, but i have to keep checking the icon color to ensure it's running properly.

two questions.  One, any idea why this is happening?  And two, if there isn't an easy fix, is there a way to send an alert that would say when the connection is lost?

I've been noticing this new issue lately myself but haven't been checking the logs to see why it's been happening. The main Ecobee device has a "status" variable that is either 0 or 1; you could automate off of that -- it's what makes the icon go grey or green. I will check my logs once I'm in a position to and let you know if I can spot anything.

watou

I asked in another thread but I figured I would inquire here. When do you anticipate releasing the new Ecobee Plugin? I am considering an Ecobee3 and would likely want to take advantage of the additional Ecobee temp sensors that should be usable with the latest Ecobee firmware release. I am hoping those sensor will be useful in Vera so I can create zones that control Z-Wave Dampers for upstairs and downstairs. Also would like to know that Ecobee 3 is good and stable on VeraEdge before  I make the Ecobee purchase.

Sorry I've been remiss in replying.  Now that the OpenHAB integration works with ecobee3's remote sensors, I will be upgrading the Vera plugin as well.  I will either be able to finish it before the 4th of May, or failing that it will be closer to the end of May.  Sorry for the delay.  I know it's in demand and I want to contribute it.  The ecobee3 is an excellent thermostat and I think it's worth the money (if you are one to appreciate this sort of thing).

Regards,
watou

Thank you very much for the reply! It is very much appreciated. Ecobee3 certainly looks like a nice thermostat. I don't usally use built in programming for thermostats as I only use heat and AC when I need to. I would however like to control it from my mobile device and in particular Vera so that I can create a scene to heat just the upstairs or just down stairs. Same goes with cooling. I have a single zone AC in a two story home and it's proven very inefficient which is something I am hoping I can change with some Z-Wave vents and and some programming in Vera. Hopefully this thermostat is all it's cracked up to be and hopefully with the updated plugin, I can take advantage of the additional temp sensors for Ecobee. My only reluctance with Ecobee3 is purchasing the additional sensors if it turns out Vera won't be able to support them in the near term. I'd hate to buy those sensors only to find out I need to purchase additional Z-Wave temp sensors to make this work.

My goal is to have a scene that I manually activate. For example: "Heat Upstairs". When activated, the downstairs vents shut and the heat will shut off when the upstairs bedroom temp sensor hits 75*. A similar scene for downstairs would shut the upstairs vents and use the downstairs temp sensor and shut off at a predetermined temp. Same scenario would be used for cooling the upstairs or downstairs.

Any thoughts on using Ecobee for this would be greatly appreciated as I have yet to buy the thermostat and sensors and am itching to do so.

Thanks again!
Scott
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on April 27, 2015, 09:34:17 pm
The ecobee3 remote sensors will appear like any temperature sensor and you will be able to automate off their temps.  They will update frequently enough to be usable for vent control.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on April 27, 2015, 10:40:31 pm
The ecobee3 remote sensors will appear like any temperature sensor and you will be able to automate off their temps.  They will update frequently enough to be usable for vent control.

watou

That is very reasurring.  I guess that will be the way I will be going then. Thanks again for your reponse and contributions here!
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on April 28, 2015, 03:05:52 pm
The ecobee3 remote sensors will appear like any temperature sensor and you will be able to automate off their temps.  They will update frequently enough to be usable for vent control.

watou

That is very reasurring.  I guess that will be the way I will be going then. Thanks again for your response and contributions here!

I bit the bullet and ordered the Ecobee 3 with the extra sensors. Should have it later this week. Hopefully the install/setup goes smooth. Looking forward to your plugin update as well. Next thing to figure out will be Roomie Integration which could be an issue unless I do that through the Roomie Vera interface. 
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on April 28, 2015, 03:13:23 pm
i'll be interested to hear how you like the zwave vents.  they are pretty pricey, and i'm worried about backflow issues to the furnace.  But i have a very similar situation as you.

One other thing to consider is a vent with a register/fan built in to push more air into a room.  I have one of these, and will automate it to turn on in our bedroom when the AC comes on.  I may use just 1-3 of the Ecovents to see if that also helps get the cold air there better.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on April 28, 2015, 08:48:48 pm
i'll be interested to hear how you like the zwave vents.  they are pretty pricey, and i'm worried about backflow issues to the furnace.  But i have a very similar situation as you.

One other thing to consider is a vent with a register/fan built in to push more air into a room.  I have one of these, and will automate it to turn on in our bedroom when the AC comes on.  I may use just 1-3 of the Ecovents to see if that also helps get the cold air there better.

Curious as to what register vents you are talking about with built in fans. I don't think I will need those as I think the Z-Wave vents will increase the flow to the rooms that need it most by closing or restricting vents that aren't needed. I will certainly update this thread or start a new thread with a review on the vents once I decide to bit the bulllet on those. I need a lot of vents so it will certainly be an expendature but I'm pretty certain I can work something amicable with the manufacturer since I know him from his computer business as he and I are in the same industry. With summer fast approaching, my plan is to get at least a handful of the vents before long. I still need to do a count on my vents here though.
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on April 28, 2015, 10:43:20 pm
i'll be interested to hear how you like the zwave vents.  they are pretty pricey, and i'm worried about backflow issues to the furnace.  But i have a very similar situation as you.

One other thing to consider is a vent with a register/fan built in to push more air into a room.  I have one of these, and will automate it to turn on in our bedroom when the AC comes on.  I may use just 1-3 of the Ecovents to see if that also helps get the cold air there better.

Curious as to what register vents you are talking about with built in fans. I don't think I will need those as I think the Z-Wave vents will increase the flow to the rooms that need it most by closing or restricting vents that aren't needed. I will certainly update this thread or start a new thread with a review on the vents once I decide to bit the bulllet on those. I need a lot of vents so it will certainly be an expendature but I'm pretty certain I can work something amicable with the manufacturer since I know him from his computer business as he and I are in the same industry. With summer fast approaching, my plan is to get at least a handful of the vents before long. I still need to do a count on my vents here though.

Well, do share any deals you can work :-).  I assume you are talking about these vents?  http://econetcontrols.com/EV100.php  or the Ecovent?

What I was talking about was this to boost airflow:  http://www.amazon.com/Tjernlund-RB10-Register-Booster-Fits/dp/B005FNL0OW/ref=pd_sim_indust_5?ie=UTF8&refRID=1114PW6W76GAJ9S64JR5  (or something similar)
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on April 29, 2015, 11:22:58 am
i'll be interested to hear how you like the zwave vents.  they are pretty pricey, and i'm worried about backflow issues to the furnace.  But i have a very similar situation as you.

One other thing to consider is a vent with a register/fan built in to push more air into a room.  I have one of these, and will automate it to turn on in our bedroom when the AC comes on.  I may use just 1-3 of the Ecovents to see if that also helps get the cold air there better.

Curious as to what register vents you are talking about with built in fans. I don't think I will need those as I think the Z-Wave vents will increase the flow to the rooms that need it most by closing or restricting vents that aren't needed. I will certainly update this thread or start a new thread with a review on the vents once I decide to bit the bulllet on those. I need a lot of vents so it will certainly be an expendature but I'm pretty certain I can work something amicable with the manufacturer since I know him from his computer business as he and I are in the same industry. With summer fast approaching, my plan is to get at least a handful of the vents before long. I still need to do a count on my vents here though.

Well, do share any deals you can work :-).  I assume you are talking about these vents?  http://econetcontrols.com/EV100.php  or the Ecovent?

What I was talking about was this to boost airflow:  http://www.amazon.com/Tjernlund-RB10-Register-Booster-Fits/dp/B005FNL0OW/ref=pd_sim_indust_5?ie=UTF8&refRID=1114PW6W76GAJ9S64JR5  (or something similar)

Those are the vents I'm talking about. I will talk to him and see if something can be done price wise. It's possible that I might be able to put together a group buy but we would likely need to get some other members together for it to happen. I will keep you posted and possibly start a group buy thread if I can make that happen.

That boost vent is interesting although I am not sure it would work for me due to the power requirements.

Edit.. I spoke with the Z-Wave Vent MFG and they are amicable to doing a group buy discount for Vera users. I will post details in a separate thread in this forum section.

Edit again: Group buy is on and the thread can be found here:
http://forum.micasaverde.com/index.php/topic,32011.0.html
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on May 02, 2015, 12:10:54 pm
I just wanted to post an update here. I installed my Ecobee3 yesterday.. Install was very straight forward other than having to climb into the attic to verify if I had the common wire and what color it was connected to in the harness as my previous t-stats didn't need the common. Ecobee support was fantastic and answered every call and every question. They also updated my Bee to the latest version once I had it online.

I also installed the existing plugin to my VeraEdge which is obviously running UI7. Vera see's the Ecobee but it doesn't appear to be able to control it. I can see the temp as well humidty via the Vera web interface. I can also see them through the Homewave app that is pulling the info from Vera but I can't seem to toggle the modes to adjust the temp. When I have the AC on and running while in hold mode, I cannot increase or decrease the temp via Vera. The Ecobee doesn't seem to respond to the temp adjustment. Also when pushing the temp button up or down in the Vera browser interface to increase or decrease the temp setting, there is a huge lag (several seconds) between each increment or degree change and the setting displayed on Vera doesn't reflect the setting on the Eco when those manual changes are made.

Having said that, I still need to play with the Ecobee some more. I am keeping the bee in Hold Mode. I don't want my AC running continuously or automatically. We try not to run it often and only turn it on when we need to. As such, I likely won't be taking advantage of the Ecobee's automatic features very often and will likely too to add the automation from the Vera side once I get my Z-Wave vents.

Bottom line.. I am not sure if my lack of Vera/Ecobee control is a result of the fact that I have Ecobee in hold mode or if it's the plugin. I've read through the various Ecobee threads here and I guess I need to read them again as I don't recall the issues that other UI7 users experienced with this plugin.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Sig on May 02, 2015, 07:21:14 pm
I'm consistently losing the connection between Vera and my Ecobee, and have to request a new PIN and re-register the app in the Ecobee Web UI every time.  It appears this is happening to others as well.  Any thoughts on what might be causing this?

The two possible reasons I'm aware of for this class of problem are 1) your LuaUPnP process is frequently crashing, and the frequently updated auth tokens are getting lost before being saved permanently to flash memory, so when the process restarts it tries to use expired tokens, or 2) there is a service problem at ecobee.com.  If your LuaUPnP.log file is showing frequent crashes and restarts, it's more likely to be the first possibility.

From here, I have two plugin instances on one UI5 Vera, and two instances of the OpenHAB binding on another system, and I've not seen any connectivity/token problems recently.

Hope this helps,
watou

Still losing my connection.  I doubt there's a service problem with Ecobee, because this isn't happening in my vacation home, only my primary home.  So maybe there is an issue with my LuaUPnP process.  Forgive my ignorance,  but where do I find the LuaUPnP.log file to see if there's a problem and, more importantly, if this is the problem, how do I fix it?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on May 02, 2015, 08:32:22 pm
Still losing my connection.  I doubt there's a service problem with Ecobee, because this isn't happening in my vacation home, only my primary home.  So maybe there is an issue with my LuaUPnP process.  Forgive my ignorance,  but where do I find the LuaUPnP.log file to see if there's a problem and, more importantly, if this is the problem, how do I fix it?

I am seeing a possibly similar problem on my UI5, where my Ecobee plugin tokens are staying solid to one account that has an ecobee3, but the tokens have failed to a separate account with a Smart Si thermostat, requiring me to get a new PIN and register it at ecobee.com.  I am trying to see what the possible cause could be, and if there is anything on the plugin side that can be done about it.

On UI5, you can see part of the log in the browser if you navigate to http://<VERA-IP>/cgi-bin/cmh/log.sh?Device=LuaUPnP . Or better yet, if you can ssh into your unit, the log file is in /var/log/cmh/LuaUPnP.log .  My log file has rotated since the time when the tokens became invalid, so at present I don't have anything to report.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on May 02, 2015, 08:42:05 pm
I just wanted to post an update here. I installed my Ecobee3 yesterday.. Install was very straight forward other than having to climb into the attic to verify if I had the common wire and what color it was connected to in the harness as my previous t-stats didn't need the common. Ecobee support was fantastic and answered every call and every question. They also updated my Bee to the latest version once I had it online.

I also installed the existing plugin to my VeraEdge which is obviously running UI7. Vera see's the Ecobee but it doesn't appear to be able to control it. I can see the temp as well humidty via the Vera web interface. I can also see them through the Homewave app that is pulling the info from Vera but I can't seem to toggle the modes to adjust the temp. When I have the AC on and running while in hold mode, I cannot increase or decrease the temp via Vera. The Ecobee doesn't seem to respond to the temp adjustment. Also when pushing the temp button up or down in the Vera browser interface to increase or decrease the temp setting, there is a huge lag (several seconds) between each increment or degree change and the setting displayed on Vera doesn't reflect the setting on the Eco when those manual changes are made.

Having said that, I still need to play with the Ecobee some more. I am keeping the bee in Hold Mode. I don't want my AC running continuously or automatically. We try not to run it often and only turn it on when we need to. As such, I likely won't be taking advantage of the Ecobee's automatic features very often and will likely too to add the automation from the Vera side once I get my Z-Wave vents.

Bottom line.. I am not sure if my lack of Vera/Ecobee control is a result of the fact that I have Ecobee in hold mode or if it's the plugin. I've read through the various Ecobee threads here and I guess I need to read them again as I don't recall the issues that other UI7 users experienced with this plugin.

I won't be able to test the plugin on UI7 until next week at the earliest.  I know there have been many issues with thermostat plugin device setpoints on UI7, confusion over heat/cool/auto setpoints, and each UI7 firmware update for Vera seems to change something about how well thermostat plugins work.  Keeping up with how close UI7 gets to UI5 functionality for these devices is something I'm just not going to devote time to (sorry).  If you could ask the people at Vera to make existing UI5 thermostat plugins work on UI7 as well as they did on UI5, hopefully they will offer you something helpful.  For many months after UI7 was released into the wild, one of their engineers told me it simply wasn't possible (i.e., they broke thermostat plugins and were not going to fix what they broke), but hopefully they've since improved matters for themselves and their customers.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on May 03, 2015, 10:47:25 am
I just wanted to post an update here. I installed my Ecobee3 yesterday.. Install was very straight forward other than having to climb into the attic to verify if I had the common wire and what color it was connected to in the harness as my previous t-stats didn't need the common. Ecobee support was fantastic and answered every call and every question. They also updated my Bee to the latest version once I had it online.

I also installed the existing plugin to my VeraEdge which is obviously running UI7. Vera see's the Ecobee but it doesn't appear to be able to control it. I can see the temp as well humidty via the Vera web interface. I can also see them through the Homewave app that is pulling the info from Vera but I can't seem to toggle the modes to adjust the temp. When I have the AC on and running while in hold mode, I cannot increase or decrease the temp via Vera. The Ecobee doesn't seem to respond to the temp adjustment. Also when pushing the temp button up or down in the Vera browser interface to increase or decrease the temp setting, there is a huge lag (several seconds) between each increment or degree change and the setting displayed on Vera doesn't reflect the setting on the Eco when those manual changes are made.

Having said that, I still need to play with the Ecobee some more. I am keeping the bee in Hold Mode. I don't want my AC running continuously or automatically. We try not to run it often and only turn it on when we need to. As such, I likely won't be taking advantage of the Ecobee's automatic features very often and will likely too to add the automation from the Vera side once I get my Z-Wave vents.

Bottom line.. I am not sure if my lack of Vera/Ecobee control is a result of the fact that I have Ecobee in hold mode or if it's the plugin. I've read through the various Ecobee threads here and I guess I need to read them again as I don't recall the issues that other UI7 users experienced with this plugin.

I won't be able to test the plugin on UI7 until next week at the earliest.  I know there have been many issues with thermostat plugin device setpoints on UI7, confusion over heat/cool/auto setpoints, and each UI7 firmware update for Vera seems to change something about how well thermostat plugins work.  Keeping up with how close UI7 gets to UI5 functionality for these devices is something I'm just not going to devote time to (sorry).  If you could ask the people at Vera to make existing UI5 thermostat plugins work on UI7 as well as they did on UI5, hopefully they will offer you something helpful.  For many months after UI7 was released into the wild, one of their engineers told me it simply wasn't possible (i.e., they broke thermostat plugins and were not going to fix what they broke), but hopefully they've since improved matters for themselves and their customers.

watou

Yikes. That's kind of discouraging as far as the Ecobee3 and UI7 is concerned. My ultimate goal for purchasing this thermostat was Vera integration and since I am on the VeraEdge, UI7 is a given for me. Hopfully I didn't jump the gun on this thermostat. As nice as it's own app is, I'd like to be able to create my Z-Wave vent scenes and have the AC or heating functionality as part of that interface. Come Monday I will certainly be contacting Vera support to request the UI5 to UI7 plugin conversion although I suspect that will fall on deaf ears.

Do you anticipate making a new plug that willl improve UI7 functionality? I know you mentioned releasing a new plugin but I'm not sure if that is going to be targeted for UI5 or UI7. If nothing else, I will look forward to your comments after you do some testing with UI7.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on May 03, 2015, 11:09:11 am
I intend to update the Ecobee plugin in the following ways, as soon as I have time:

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on May 03, 2015, 12:09:23 pm
I intend to update the Ecobee plugin in the following ways, as soon as I have time:
  • For each ecobee3 remote sensor, create a Vera temperature sensor device and a motion sensor device.  They will be named using the names you gave the devices in Ecobee.  You can then change the Vera room in which the remote sensor devices actually exist.
  • Have separate JSON files for UI5 vs. UI7 installations, so the Ecobee icons appear on UI7 as they do on UI5. I don't expect to be trying to track changes in UI7's compatibility with thermostat plugins with updates to the plugin, but I hope my efforts leave it in a usable state on UI7.
  • Change the home/away button so it sets an indefinite hold for the either the "home" or "away" climate/comfort setting, and the Vera device reports "1" if the current climate/comfort setting is "home", and "0" in all other cases (like "away", "sleep" or any other climate/comfort setting).  This will undo the existing behavior where "away" uses the quickSave setback and setforward offsets of the current setpoints, thereby giving users more control and consistency.
  • Test on both UI5 and UI7 best I can, and publish the update on apps.mios.com.

watou

Thanks for the informative post Watou. With a bit of luck, this will make Ecobee more usable through Vera for us UI7 users.  I've been in the computer and data storage manufacturing business for many many years and have had my share of programmers on payroll. Knowing that programming and development can be quite an undertaking, especially where the only return is a gracious thank you, I for one (and I am sure many others here do as well) really appreciate your efforts and contributions. While no product is ever perfect, it's people like yourself that can really make a difference. Again, thank you for your efforts.
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on May 03, 2015, 01:08:54 pm
+1 to that sentiment!
Title: Plug-in for ecobee thermostats in development
Post by: mda on May 03, 2015, 10:25:08 pm
@watou

I have 2 Nests right now but am considering replacing them with the ecobee3 if I can do a couple more things with the plugin. Do you expect to be able to:

1. show and (in a scene or Luup) set all 4 modes on the ecobee3?

2. Select which temp sensors to use in a scene or Luup ? (In UI 5).

Thanks !
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on May 03, 2015, 10:43:50 pm
1. show and (in a scene or Luup) set all 4 modes on the ecobee3?

2. Select which temp sensors to use in a scene or Luup ? (In UI 5).

I could add a Luup Action to the thermostat device that accepts "raw" JSON to the API.  If you can build the proper JSON string in your code, you will be able to reach the API. 

The temperature sensors have standard triggers for things like temperature going above and going below.

For selecting which temp sensors, you should be able to average across whichever sensors you want in Lua code, since you will have all the "CurrentTemperature" variables.

Title: Plug-in for ecobee thermostats in development
Post by: mda on May 03, 2015, 10:59:25 pm
Thanks.

I am not sure how I would figure out the raw json to send to change modes. I was hoping the plugin would natively support the 4 modes so we can read and activate them the same way we do with the Nest plugin home/away.

I am not looking to average temps directly with Vera, just want to instruct the thermostat which sensors to pay attention to so the thermostat can do the work.

If these are not feasible, I think I will have to stick with the Nests (with your UI5 nest plugin). Thanks.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on May 14, 2015, 09:32:57 pm
Just wanted to follow up on the Ecobee plugin and see if any progress has been made on the updated version.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on May 15, 2015, 01:59:39 am
Just wanted to follow up on the Ecobee plugin and see if any progress has been made on the updated version.

Yes, there's progress!  Please see this list for what is currently being considered/worked on for the next plugin release:

https://github.com/watou/vera-ecobee/milestones/v1.2

Please let me know if something you need is missing.  Thanks, watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on May 15, 2015, 10:12:07 am
Perfect.
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on May 18, 2015, 01:12:42 am


Yes, there's progress!  Please see this list for what is currently being considered/worked on for the next plugin release:

https://github.com/watou/vera-ecobee/milestones/v1.2

Please let me know if something you need is missing.  Thanks, watou

watou,
to add to your list:
- multistage reporting/energy/controls.
- EB-RSM-01 remote sensor module reporting
- implement mcvflorin's earlier suggestion to avoid losing registration during LuaUPnP crash by storing token in 2 places: in the state variable, and in a file in /tmp

Thanks again for awesome work
theal

 
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on May 18, 2015, 04:20:07 pm
Just wanted to follow up on the Ecobee plugin and see if any progress has been made on the updated version.

Yes, there's progress!  Please see this list for what is currently being considered/worked on for the next plugin release:

https://github.com/watou/vera-ecobee/milestones/v1.2

Please let me know if something you need is missing.  Thanks, watou

That's great news! Thanks for the update. From what I can see, you have everything I could imagine covered for my needs.
Title: Re: Plug-in for ecobee thermostats in development
Post by: mda on May 18, 2015, 04:43:35 pm
@watou - Is there any chance of adding the ability to instruct the thermostat whether or not to follow the remote temp sensor?
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on May 31, 2015, 12:08:27 pm
@Watou...

not sure if this is due to the recent update, or something I've just never noticed before.  I'm running U15, and one of the devices your plugin creates is the home/away control. 

I realized this morning that the colored state of the buttons never change, no matter if you are in either home or away.  In my case... the away button is always colored, as if it is in that state.  But the tstat is "home". 

I can actually trigger the tstat for either home or away from the plugin fine... so it is functionally working.  the button state just never changes.  any ideas?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on May 31, 2015, 01:10:44 pm
@Watou...

not sure if this is due to the recent update, or something I've just never noticed before.  I'm running U15, and one of the devices your plugin creates is the home/away control. 

I realized this morning that the colored state of the buttons never change, no matter if you are in either home or away.  In my case... the away button is always colored, as if it is in that state.  But the tstat is "home". 

I can actually trigger the tstat for either home or away from the plugin fine... so it is functionally working.  the button state just never changes.  any ideas?

Hi @tomgru,

I don't know why that would be, but the v1.2 version of the plugin is going to change the meaning and function of these buttons entirely, from the current use of quicksave offsets, to this:

Please let me know if this spells disaster for you, and why, and thanks!

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 01, 2015, 10:11:25 am
@Watou...

not sure if this is due to the recent update, or something I've just never noticed before.  I'm running U15, and one of the devices your plugin creates is the home/away control. 

I realized this morning that the colored state of the buttons never change, no matter if you are in either home or away.  In my case... the away button is always colored, as if it is in that state.  But the tstat is "home". 

I can actually trigger the tstat for either home or away from the plugin fine... so it is functionally working.  the button state just never changes.  any ideas?

Hi @tomgru,

I don't know why that would be, but the v1.2 version of the plugin is going to change the meaning and function of these buttons entirely, from the current use of quicksave offsets, to this:
  • if the current comfort setting (aka "climate") is "home," the Home button will be highlighted and the switch device will be ON.
  • if the current comfort setting is "away," the Away button will be highlighted and the switch will be OFF.
  • if the current comfort setting is anything else, the switch will be OFF and neither button will be highlighted.
  • I will add a new Action to set an indefinite hold by climate reference (like "away","wake","sleep","home" or others you might have defined).  There is already a device variable called currentClimateRef to read what it is currently.
  • setting the switch to ON (also clicking Home) will set an indefinite hold to the "home" comfort settings.
  • setting the switch to OFF (also clicking Away) will set an indefinite hold to the "away" comfort settings.
  • You can continue to clear any current hold (like changing the setpoints, Home or Away, etc.) but pressing the Resume button on the thermostat device.

Please let me know if this spells disaster for you, and why, and thanks!

watou

Sounds perfect.
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on June 02, 2015, 08:54:33 am
watou,
I got a reply from Ecobee development team that their RemoteSensor API fully supports Ecobee's RSM EB-RSM-01 board (http://developer.ecobee.com/api/topics/remote-sensor-module-api).
Would you please make sure your implementation supports all sensor capabilities (adc, co2, dryContact, humidity, temperature, occupancy)?

Thanks in advance
theal
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 02, 2015, 01:49:00 pm
watou,
I got a reply from Ecobee development team that their RemoteSensor API fully supports Ecobee's RSM EB-RSM-01 board (http://developer.ecobee.com/api/topics/remote-sensor-module-api).
Would you please make sure your implementation supports all sensor capabilities (adc, co2, dryContact, humidity, temperature, occupancy)?

If the RSM EB-RSM-01 board's sensor information is conveyed in the RemoteSensor object like ecobee3's wireless remote sensors are, then they will appear no differently (see https://www.ecobee.com/home/developer/api/documentation/v1/objects/RemoteSensor.shtml).  Despite that, I don't have the same equipment you do, and the API documentation does not say how values for the capabilities adc, co2 and dryContact are presented, so I can only guess for them, and I'm quite possibly going to guess incorrectly (see https://www.ecobee.com/home/developer/api/documentation/v1/objects/RemoteSensorCapability.shtml).

Do you know what the values mean and how they are formatted for the capabilities adc, co2 and dryContact?  I can only guess that adc means "analog to digital converter," but converting what into what, in what format?  Is co2 a numeric value of parts per million?  Is dryContact a simple contact switch that is reported as "true" or "false", or "1" or "0", etc.?  Which UPnP service and device types would most accurately map to these sensor capabilities?  Can you run any sample API code to produce a full JSON dump for your equipment?  (Your answers may help me produce better outcomes, but I can make no guarantees.)

My ability to dig deeply into this is very limited, as I'm doing this work completely pro bono, and have no use myself for the outcome.

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on June 03, 2015, 12:59:13 am

If the RSM EB-RSM-01 board's sensor information is conveyed in the RemoteSensor object like ecobee3's wireless remote sensors are, then they will appear no differently (see https://www.ecobee.com/home/developer/api/documentation/v1/objects/RemoteSensor.shtml).  Despite that, I don't have the same equipment you do, and the API documentation does not say how values for the capabilities adc, co2 and dryContact are presented, so I can only guess for them, and I'm quite possibly going to guess incorrectly (see https://www.ecobee.com/home/developer/api/documentation/v1/objects/RemoteSensorCapability.shtml).

Do you know what the values mean and how they are formatted for the capabilities adc, co2 and dryContact?  I can only guess that adc means "analog to digital converter," but converting what into what, in what format?  Is co2 a numeric value of parts per million?  Is dryContact a simple contact switch that is reported as "true" or "false", or "1" or "0", etc.?  Which UPnP service and device types would most accurately map to these sensor capabilities?  Can you run any sample API code to produce a full JSON dump for your equipment?  (Your answers may help me produce better outcomes, but I can make no guarantees.)

My ability to dig deeply into this is very limited, as I'm doing this work completely pro bono, and have no use myself for the outcome.

Regards,
watou

watou,

I'm planing a major revamping of my HVAC system by the end of the month and while I'm doing it, I want to install temperature sensors in coil, return and supply ducts for delta-T monitoring/control blower variable speed & AC staging.
I was looking for a device to connect these sensor to Vera and could not find a reasonable solution.  Fibaro Universal Sensor looked promising but it is not sold in US.
Then I saw that Ecobee added a Remote Sensor API capabilities, so I'm planning to install RSM EB-RSM-01 board during my upgrade to run it with supported 10k ohm ntc temperature sensors.
According to RSM documentation, my Smart tstat won't support CO2 sensors, so I don't know if CO2 would be exposed to API (I would like to use CO2 sensor for outside ventilation control).
I'm not planning to run any dryContacts through RSM for now as they (water and freeze sensors) already handled by my DSC/Vera alarm.  I suspect dryContact would be reported as a contact switch in API.
As per UPnP device types, I would use basic TemperatureSensor, HumiditySensor, GenericSensor (CO2), DoorSensor  (dryContact).
I'll be happy to test/debug API once my board is running.
Meanwhile I posted on development's forum to see if we can get clarification on your format questions.

I completely understand your position and I hope a RSM board implementation will be in line with Ecobee3 remote sensors implementation with very little extra coding.

Thanks again for all your work
theal

Thanks again,
theal
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 02:50:46 am
v1.2 of the plugin is currently in the approval queue at apps.mios.com.  The updated documentation is here:

http://watou.github.io/vera-ecobee/

Please let me know if it works with your RSM EB-RSM-01.  Thanks!

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: Wekurtz74 on June 10, 2015, 06:30:18 am
v1.2 of the plugin is currently in the approval queue at apps.mios.com.  The updated documentation is here:

http://watou.github.io/vera-ecobee/

Please let me know if it works with your RSM EB-RSM-01.  Thanks!

watou

Looks great!  Can't wait to try it out.   Thank you for your work to produce this.   

Sent from my GT-N5110 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 10, 2015, 10:16:20 am
v1.2 of the plugin is currently in the approval queue at apps.mios.com.  The updated documentation is here:

http://watou.github.io/vera-ecobee/

Please let me know if it works with your RSM EB-RSM-01.  Thanks!

watou

Drumroll................
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 10, 2015, 11:43:27 am
It got approved!! available NOW!
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 10, 2015, 12:16:35 pm
It got approved!! available NOW!

I don't see it yet in the "install apps" section within U15, but it is at the MiOS Marketplace.  However, when i try to install from there... nothing happens. 

@watou, make sure you chance the author name for to get some well deserved credit :-)
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 12:22:40 pm
It got approved!! available NOW!

I don't see it yet in the "install apps" section within U15, but it is at the MiOS Marketplace.  However, when i try to install from there... nothing happens. 

@watou, make sure you chance the author name for to get some well deserved credit :-)

Thanks, Tom, good thought.  :) I was just able to successfully update to v1.2 on my VeraEdge running 1.7.1181.  I haven't tried the official update on the Vera 3 running 1.5.622, but I will do so later.

Let me know how it goes, when it goes!
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 10, 2015, 12:28:20 pm
It got approved!! available NOW!

I don't see it yet in the "install apps" section within U15, but it is at the MiOS Marketplace.  However, when i try to install from there... nothing happens. 

@watou, make sure you chance the author name for to get some well deserved credit :-)

Thanks, Tom, good thought.  :) I was just able to successfully update to v1.2 on my VeraEdge running 1.7.1181.  I haven't tried the official update on the Vera 3 running 1.5.622, but I will do so later.

Let me know how it goes, when it goes!

it is funny... when from the MiOS Marketplace, it says installing plugin... but when i go back to my U15 screen... nada.  Should I uninstall the older version first?  (I do have auto update on... but i am too impatient to wait :-))
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 10, 2015, 12:31:21 pm
Hmm Mine installed just fine...
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 10, 2015, 12:32:16 pm
Hmm Mine installed just fine...

Did you have the old one installed?  And what version of Vera are you on?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 12:32:44 pm
If you could search around and find the local URL that forces the update -- it's in one of these Ecobee threads somewhere....
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 12:35:59 pm
It got approved!! available NOW!

I just installed it.. Lots of new devices as a result. Motion, temp, humidity etc. Now I just need to figure out how to use it. I guess I will need to figure out Luup or Pleg to take advantage of this. I suspect my head will start to spin when I go down that path.

Thanks again Watou for your efforts.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 12:40:08 pm
I just installed it.. Lots of new devices as a result. Motion, temp, humidity etc. Now I just need to figure out how to use it. I guess I will need to figure out Luup or Pleg to take advantage of this. I suspect my head will start to spin when I go down that path.

You ought to be able to use the new devices in scenes or use PLEG if you prefer, like when there is motion in a room open the cooling vent in that room, close vents in no-longer-occupied rooms, etc.  You can also call the new SetClimateHold action to send the thermostat into one of its comfort settings (formerly called "climates") from Luup code.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 10, 2015, 12:51:54 pm
If you could search around and find the local URL that forces the update -- it's in one of these Ecobee threads somewhere....

Found it... for others just in case:
http://<your vera ip>:3480/data_request?id=update_plugin&Plugin=3586

updating now.

EDIT.  LOOK AT THAT.  it's like a new toy at Christmas!!!!
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 01:00:18 pm
I added the Ecobee to my Homewave app. This is probably a Homewave issue so I will post it there but when I added the Thermostat settings button only gives me Auto, On % Cycle instead of Off, Auto, Cool & Heat. In Vera, I do see Off, Auto, Cool & Heat so it does appear to be working on the Vera side. I will post this over in the Homewave section to see what the developer has to say. I attached an image of the Homewave screen shot.
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 10, 2015, 01:05:30 pm
i see two humidity panels for the main tstat... both reading correctly.  Assume one came over from the old version?

@sleif - i see the correct controls in Imperihome, and it is functioning so far as i can tell!
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 01:08:41 pm
i see two humidity panels for the main tstat... both reading correctly.  Assume one came over from the old version?

@sleif - i see the correct controls in Imperihome, and it is functioning so far as i can tell!
Good to know. I posted this in the Homewave forum here so I will be interested to see what they say. As for two humidity sensors, I have two as well along with two temp sensors.  I think the reason for that is that the thermostat has a built in sensor for temp and humidity. Then you have the remote sensor with temp and humidity as well.  What I am curious about is if we add additional sensors, will the plugin automatically create the devices for those? I have two additional Ecobee sensors sitting in their box and at some point I will add those provided I can set a temp for a specific room like my master bedroom or living and be able to use that sensor for the temperature control instead of an average between them which I think is the default way the Ecobee functions. 
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 01:14:57 pm
i see two humidity panels for the main tstat... both reading correctly.  Assume one came over from the old version?

The reason you see two humidity devices is this: the plugin has to work for tstats with no remote sensors as before v1.2, so the old "humidistat" device remains (which still lacks humidity setpoints for various reasons, so it's not much of a humidistat).  Then, the Ecobee remote sensor API lists all sensors including the ecobee3's internal sensors, including its humidity sensor.  So instead of special-casing the code (and likely making a bad assumption), I give you all of the temperature, humidity and occupancy sensors the API delivers.  So in the end, for ecobee3 users with remote sensors (or maybe all ecobee3 users, I can't test that), you get two humidity-reporting devices instead of one.  Think of it as a free bonus!

Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 10, 2015, 01:16:00 pm
@watou - one question (so far :-)).  All my motion sensors show up as set to "bypass".  Wouldn't they reflect if i have them armed for the different settings/modes in my tstat?

OR... is this a 'separate' ability to arm for other scenes, which is what i'm now guessing as i type this?  :-)
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 01:21:54 pm
What I am curious about is if we add additional sensors, will the plugin automatically create the devices for those?

Yes it will create new devices when you add new remote sensors.  However, if you remove a remote sensor from the thermostat, Vera may show dead devices which you will have to manually delete from Vera.  The plugin has to deal with two different device discovery techniques, and this seemed the simplest, least error-prone approach.

I have two additional Ecobee sensors sitting in their box and at some point I will add those provided I can set a temp for a specific room like my master bedroom or living and be able to use that sensor for the temperature control instead of an average between them which I think is the default way the Ecobee functions.

I don't know how you could use one ecobee3 and multiple remote sensors to achieve a multi-zoned system, or maybe I'm not following you.  The ecobee3 will average one or more temperature sensors to achieve a sense of what the current ambient temperature is, and command the HVAC equipment to try to reach its setpoint against that averaged ambient temperature.  The follow-me comfort is constantly changing which sensors participate in the average based on occupancy (unless you turn off follow-me comfort or explicitly exclude specific sensors).
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 01:26:05 pm
@watou - one question (so far :-)).  All my motion sensors show up as set to "bypass".  Wouldn't they reflect if i have them armed for the different settings/modes in my tstat?

OR... is this a 'separate' ability to arm for other scenes, which is what i'm now guessing as i type this?  :-)

Vera's security sensors have the concept of Armed (being "0" -- bypass, or "1" -- armed).  The concept is not related to Ecobee at all.  It is only to give you the option to ignore bypassed sensors in scenes in Vera (or for whatever other purpose you would want to use the concept).

Separately, the plugin does not toggle the "inUse" flag for whether a temperature sensor participates in the follow-me comfort averaging -- you have to do that through the ecobee portal, or on the physical tstat itself.

Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 02:16:25 pm
What I am curious about is if we add additional sensors, will the plugin automatically create the devices for those?

Yes it will create new devices when you add new remote sensors.  However, if you remove a remote sensor from the thermostat, Vera may show dead devices which you will have to manually delete from Vera.  The plugin has to deal with two different device discovery techniques, and this seemed the simplest, least error-prone approach.

I have two additional Ecobee sensors sitting in their box and at some point I will add those provided I can set a temp for a specific room like my master bedroom or living and be able to use that sensor for the temperature control instead of an average between them which I think is the default way the Ecobee functions.

I don't know how you could use one ecobee3 and multiple remote sensors to achieve a multi-zoned system, or maybe I'm not following you.  The ecobee3 will average one or more temperature sensors to achieve a sense of what the current ambient temperature is, and command the HVAC equipment to try to reach its setpoint against that averaged ambient temperature.  The follow-me comfort is constantly changing which sensors participate in the average based on occupancy (unless you turn off follow-me comfort or explicitly exclude specific sensors).

Presently I have the main thermostat sensor disabled and am using one remote sensor for my temp control. As such, I guess follow me comfort is disabled. I don't keep my AC on normally and only turn it on when it gets too hot or too cold in the house. As such, I really don't take advantage of any of the advanced Ecobee features.

My hope was that I could place a sensor in my master bedroom and another in my living room. Both are the most common areas of my house that I am likely to be in.

In Vera I would like to be able to create a couple scenes or activities that essentially works as follows.

Cool or Heat Living room to 77*. When I select that activity or scene, Vera would only use the temp sensor for that area and turn the air or heat on to auto or manual mode. Once the the temp sensor in that room reads the set temperate, Vera would turn the Ecobee off. As part of this, my Z-Wave vents upstairs would close and the downstairs ones would open. I already have a scene for the vent function.

I would have a similar scene for Cool or Heat Upstairs which Vera would use the temp sensor upstairs as the temp reference and turn the air or heat on until it reaches the target temperature for the sensor associated with that location. It would also close the vents downstairs and open the vents upstairs.

That is the idea anyway.  Not sure if it's doable or not using multiple sensors that Vera uses to control the Ecobee manually. Worst case, I use the single sensor as I am now doing and just carry it upstairs or downstairs. Of course that isn't ideal though.

Do you think this would be doable using Vera to control the Ecobee3 manually like that?

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 02:59:25 pm
...

Presently I have the main thermostat sensor disabled and am using one remote sensor for my temp control. As such, I guess follow me comfort is disabled. I don't keep my AC on normally and only turn it on when it gets too hot or too cold in the house. As such, I really don't take advantage of any of the advanced Ecobee features.

My hope was that I could place a sensor in my master bedroom and another in my living room. Both are the most common areas of my house that I am likely to be in.

In Vera I would like to be able to create a couple scenes or activities that essentially works as follows.

Cool or Heat Living room to 77*. When I select that activity or scene, Vera would only use the temp sensor for that area and turn the air or heat on to auto or manual mode. Once the the temp sensor in that room reads the set temperate, Vera would turn the Ecobee off. As part of this, my Z-Wave vents upstairs would close and the downstairs ones would open. I already have a scene for the vent function.

I would have a similar scene for Cool or Heat Upstairs which Vera would use the temp sensor upstairs as the temp reference and turn the air or heat on until it reaches the target temperature for the sensor associated with that location. It would also close the vents downstairs and open the vents upstairs.

That is the idea anyway.  Not sure if it's doable or not using multiple sensors that Vera uses to control the Ecobee manually. Worst case, I use the single sensor as I am now doing and just carry it upstairs or downstairs. Of course that isn't ideal though.

Do you think this would be doable using Vera to control the Ecobee3 manually like that?

Would it be equivalent to have two remote sensors, one in the living room and one upstairs, and your living room scene would 1) switch to cooling mode, 2) set the cool setpoint to 77, 3) disable the upstairs sensor for the current comfort setting, 4) enable to living room sensor for the current comfort setting, and the upstairs scene would be the mirror image? 

The plugin currently can't do steps 3 or 4, and frankly it would be very mucky to create a custom JSON payload to send through the plugin to the API to achieve this outcome (the facility to send custom JSON payloads is not yet present in the plugin and I'm waiting for a extremely good reason to add it).  This would require a deep understanding of the Ecobee API (docs are here: https://www.ecobee.com/home/developer/api/documentation/v1/objects/Climate.shtml).

Or to simplify it further, you would have two active remote sensors, disable the one at the tstat, and your scene would be to switch the thermostat between Off, HeatOn or CoolOn.  Let the thermostat follow you and do all the rest.

It would be really worthwhile to exhaustive study the myriad options built into the thermostat already, to see if there is a way to achieve close to what you want with the facilities already present in it.  I wouldn't be surprised if there wasn't some way to approximate your goal with existing thermostat functionality.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 03:33:29 pm

Would it be equivalent to have two remote sensors, one in the living room and one upstairs, and your living room scene would 1) switch to cooling mode, 2) set the cool setpoint to 77, 3) disable the upstairs sensor for the current comfort setting, 4) enable to living room sensor for the current comfort setting, and the upstairs scene would be the mirror image? 

The plugin currently can't do steps 3 or 4, and frankly it would be very mucky to create a custom JSON payload to send through the plugin to the API to achieve this outcome (the facility to send custom JSON payloads is not yet present in the plugin and I'm waiting for a extremely good reason to add it).  This would require a deep understanding of the Ecobee API (docs are here: https://www.ecobee.com/home/developer/api/documentation/v1/objects/Climate.shtml).

Or to simplify it further, you would have two active remote sensors, disable the one at the tstat, and your scene would be to switch the thermostat between Off, HeatOn or CoolOn.  Let the thermostat follow you and do all the rest.

It would be really worthwhile to exhaustive study the myriad options built into the thermostat already, to see if there is a way to achieve close to what you want with the facilities already present in it.  I wouldn't be surprised if there wasn't some way to approximate your goal with existing thermostat functionality.

watou

To answer your first question, the answer is yes with the exception being that Vera would be using a selected temperature sensor to manually control the Ecobee3. Whether that is possible I don't know. There would be separate heat or cool programs for both upstairs and downstairs.

With regards to this:
"Or to simplify it further, you would have two active remote sensors, disable the one at the tstat, and your scene would be to switch the thermostat between Off, HeatOn or CoolOn.  Let the thermostat follow you and do all the rest.", that is kind of what I am after but ideally only  using a selected temp sensor and having Vera manage the Ecobee manually via the scene.

I can't help but wonder if a simpler Z-Wave based thermostat may be have been a better choice for my application. Having said that, I do like the Ecobee interface and it's functionality.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 04:13:34 pm
...Vera would be using a selected temperature sensor to manually control the Ecobee3.

Is the issue that you want to control the temperature in possibly unoccupied rooms?  In other words, is it that occupancy is not the condition you want to use to cause a specific room's temperature sensor to be used as the temperature to bring to the setpoint?  What condition should trigger this outcome?

"Or to simplify it further, you would have two active remote sensors, disable the one at the tstat, and your scene would be to switch the thermostat between Off, HeatOn or CoolOn.  Let the thermostat follow you and do all the rest.", that is kind of what I am after but ideally only  using a selected temp sensor and having Vera manage the Ecobee manually via the scene.

Out of curiosity, what is your purpose in having Vera perform this logic via a scene?
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 04:29:10 pm
...Vera would be using a selected temperature sensor to manually control the Ecobee3.

Is the issue that you want to control the temperature in possibly unoccupied rooms?  In other words, is it that occupancy is not the condition you want to use to cause a specific room's temperature sensor to be used as the temperature to bring to the setpoint?  What condition should trigger this outcome?

"Or to simplify it further, you would have two active remote sensors, disable the one at the tstat, and your scene would be to switch the thermostat between Off, HeatOn or CoolOn.  Let the thermostat follow you and do all the rest.", that is kind of what I am after but ideally only  using a selected temp sensor and having Vera manage the Ecobee manually via the scene.

Out of curiosity, what is your purpose in having Vera perform this logic via a scene?

For the most part the temp will be adjusted for the room I am in. If I am upstairs in bed, then I may have the temp set for upstairs. If I am downstairs watching TV or cooking than i would want to control the downstairs temp. In essences, I am creating a poor mans zoned system. As to why I want to control via Vera. I already have the Z-Wave vents setup. At the moment I have 3 scenes to control those vents.

Heat/Cool Downstairs: Opens the downstairs vents and closes the upstairs vents.
Heat/Cool Upstairs: Opens the upstairs vents and closes the down stairs vent.
Heat/Cool Upstairs Downstairs: Opens both upstairs and downstairs.

Presently I trigger a scene on Vera via one of my apps and then go into the Ecobee app and turn the air on. Since I use Homewave and Roomie Remote as my go to apps/remotes for AV and home automation control and both have my Vera outlets and scenes programmed in, the idea of having one scene to heat or cool down stairs and another to heat or cool upstairs is much more convenient than using vera to toggle the vents and Ecobee to turn on the air or heat. Especially if I am using Roomie or Homewave for my home automation control. Just a simple press of the button to cool off the downstairs to 78 or heat it to 78. Same for the upstairs. Press one button to trigger a scene that does it all (set temp and toggle vents).

My idea was to create a program or scene that would set the upstairs or downstairs temp to 77* with a push of a button at which point the vents would open or close accordingly, the AC or heat would turn on and the logic would use the appropriate temp sensor for that zone to control the temps.  If Ecobee uses an average between the two and I want to increase the temp downstairs, the upstairs will become an oven before the downstairs reaches it's target. While I do have the Z-Wave vents, they don't make them in every size I needed so I purchased what they had that I could use which was a total of 5 vents out of about 15 vents in my house. As such, it would be much more efficient to use separate temp sensors for each of the two zones. 
 
Title: Re: Plug-in for ecobee thermostats in development
Post by: mda on June 10, 2015, 05:01:43 pm
Out of curiosity, what is your purpose in having Vera perform this logic via a scene?


In case it helps, my use case for Vera telling ecobee which sensors to care about would be:

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 05:20:35 pm
Out of curiosity, what is your purpose in having Vera perform this logic via a scene?


In case it helps, my use case for Vera telling ecobee which sensors to care about would be:

  • We have a 2 storey home, each story has its own HVAC unit. Our child's bedroom is on the first floor of the house and our master bedroom is on the 2nd floor.
  • We tell vera when our child goes to sleep and wakes up, and we tell vera when we go to sleep and wake up (so blinds and lights are lowered, raised etc)
  • It would be great if as soon as vera knows that both our child and we have gone to sleep it could tell the ecobee on the first floor to care only about our daughter's bedroom temp, then tell it to go back to using its main sensor in the morning.

You have just described the functionality that's built into the ecobee3.  It comes with comfort settings called wakeup, away, home, and sleep, that you can customize.  Each comfort setting has its own setpoints and fan mode, and each also has its own list of which sensors to average (even just one sensor).  The comfort settings are run on a weekly schedule that you define through the web portal (or define vacations).  Separately, you can immediate effect a hold to a specific comfort setting from the Ecobee plugin in Vera, via a scene, PLEG or Luup code.  So when your scene runs from your mobile Vera client, it puts the thermostat into the defined comfort setting, which has all the outcome effects you are after.  So all of the thermostat functions of controlling different zones would be configured in each comfort setting.  And lastly, you can define your own named comfort settings outside of the provided wakeup, away, home, sleep set provided, in case you want to represent different scenes to control.

So, I think the ecobee3 was really the right thermostat for this project!

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 05:29:12 pm
...Vera would be using a selected temperature sensor to manually control the Ecobee3.

Is the issue that you want to control the temperature in possibly unoccupied rooms?  In other words, is it that occupancy is not the condition you want to use to cause a specific room's temperature sensor to be used as the temperature to bring to the setpoint?  What condition should trigger this outcome?

"Or to simplify it further, you would have two active remote sensors, disable the one at the tstat, and your scene would be to switch the thermostat between Off, HeatOn or CoolOn.  Let the thermostat follow you and do all the rest.", that is kind of what I am after but ideally only  using a selected temp sensor and having Vera manage the Ecobee manually via the scene.

Out of curiosity, what is your purpose in having Vera perform this logic via a scene?

For the most part the temp will be adjusted for the room I am in. If I am upstairs in bed, then I may have the temp set for upstairs. If I am downstairs watching TV or cooking than i would want to control the downstairs temp. In essences, I am creating a poor mans zoned system. As to why I want to control via Vera. I already have the Z-Wave vents setup. At the moment I have 3 scenes to control those vents.

Heat/Cool Downstairs: Opens the downstairs vents and closes the upstairs vents.
Heat/Cool Upstairs: Opens the upstairs vents and closes the down stairs vent.
Heat/Cool Upstairs Downstairs: Opens both upstairs and downstairs.

Presently I trigger a scene on Vera via one of my apps and then go into the Ecobee app and turn the air on. Since I use Homewave and Roomie Remote as my go to apps/remotes for AV and home automation control and both have my Vera outlets and scenes programmed in, the idea of having one scene to heat or cool down stairs and another to heat or cool upstairs is much more convenient than using vera to toggle the vents and Ecobee to turn on the air or heat. Especially if I am using Roomie or Homewave for my home automation control. Just a simple press of the button to cool off the downstairs to 78 or heat it to 78. Same for the upstairs. Press one button to trigger a scene that does it all (set temp and toggle vents).

My idea was to create a program or scene that would set the upstairs or downstairs temp to 77* with a push of a button at which point the vents would open or close accordingly, the AC or heat would turn on and the logic would use the appropriate temp sensor for that zone to control the temps.  If Ecobee uses an average between the two and I want to increase the temp downstairs, the upstairs will become an oven before the downstairs reaches it's target. While I do have the Z-Wave vents, they don't make them in every size I needed so I purchased what they had that I could use which was a total of 5 vents out of about 15 vents in my house. As such, it would be much more efficient to use separate temp sensors for each of the two zones.

This is also a case where you would match your scenes in Vera to comfort settings in ecobee3, and when you run your scene, from a mobile app for example, it puts the thermostat into that comfort setting to effect all the heating/cooling behaviors you're after.  All of the other actions in that scene, like controlling vents, would continue as usual.  Problem solved! (I think)
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 10, 2015, 05:35:31 pm
@sleif and @mda...

I think you need to use more of the Ecobee logic first.  You can assign sensors to modes you create in the tstat.  So, for example, I have three modes in Ecobee (separate from Vera).  Home, Away, and sleep.  For home and away, i use the "follow me" feature, that sets the temp based on a blended average of the sensors i have selected.  (in this case, all sensors selected - i have 5 today).  This way,  wherever i am, the temp is adjusted accordingly.  If I'm only in one room, it will set the temp based on the sensor in that room.  My wife in another room... blends the two.

Now sleep mode is the great new feature in Ecobee, where it will set the temp based on a sensor you create, and doesn't rely on motion (as it may not pick it up while you are sleeping - unless of course you sleep like my 14 yearold :-), moving constantly floppy around).  I currently only have this using my master bedroom sensor, on the second floor. 

This all works today.. that's the good news.  The bad news is that to get my Master to 68 degrees, my first floor ends up being even lower - AC i'm wasting. 

That's where i'm hoping the vents come in.  Today, prior to Watou's version change, i just had a scene that ran at 10pm that closed several vents downstairs (or that was the plan... as I've only installed two vents so far).  My thinking would be that not only would that allow possibly more airflow upstairs cooling my Master, but also mitigate the large delta between first and second floor temps by minimizing the cooling downstairs.

NOW.. with the ability to use the Ecobee sensors, i can automate this better than just creating the 10pm scene.  So.. without having done any thinking around how to actually do this ... here's what i'm planning on doing:

1. for Home and Away, let Ecobee and "follow me" do the heavy lifting.  (note, i do have a trigger than when i arm my alarm, it automatically sets the Ecobee to Away).
2. Since this is mostly a night time sleep issue.. when "Sleep" is started on the Ecobee, i want Vera to look at the temps in the rooms (all sensors) - but specifically i want to compare the downstairs temp to the master bedroom temp.  If it is, which occurs more in the hot summer, say a more than 4 degree delta, then close the vents downstairs to get the two floors to equal out, while still letting Ecobee manage getting my Master bedroom temp to the right setting.
3. Ultimately, i may try to do #2 all the time, effectively load balancing around my house - but i think that might get too complicated in conjunction with "follow me". 

Anyhoo... that's my plan.  what am i missing?

EDIT.  i see our posts crossed Watou... clearly on the same page i believe.  :-)
Title: Re: Plug-in for ecobee thermostats in development
Post by: mda on June 10, 2015, 05:39:22 pm
...So, I think the ecobee3 was really the right thermostat for this project!

watou

Perfect, thank !
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 05:44:23 pm
EDIT.  i see our posts crossed Watou... clearly on the same page i believe.  :-)

Spot on! :-)
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 06:30:47 pm
I am home now and doing some testing and I am not sure if I have an issue or if I am not understanding how the app works. I included a screen shot below from vera. On the right side I have the temp setting, off, auto, heat and cool. If I change the temp to 77* and select cool, it doesn't seem to change the Ecobee temperature setting. It does however seem to change modes. If I select cool in Vera or Off, Ecobee changes it's mode but it doesn't seem like I can change the termperature set point from Vera. I also noticed that the Vera app doesn't seem to reflect the mode that Ecobee is in. If for example Ecobee is in Cool mode, the App was showing it to be in OFF mode and the temp doesn't seem to reflect the correct set point that I have on the Ecobee. I tried refreshing the page and it still didn't seem to reflec the correct temperature.

I will mess with it a bit later after a beer or two and verify my results. I will also review your reply above.
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 10, 2015, 06:33:35 pm
I tend to agree with the folks here. I would use the plugin to add some additional controls to the built in Ecobee and would also use it to sync my soon to be installed econet vents. I would not want the Vera to run the entire Thermostat logic. Ecobee is already very good at it and I believe will keep on improving. It adds the access to all the ecobee sensors which helps the vera automate other things based on these sensors too.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 06:42:24 pm
@sleif and @mda...

I think you need to use more of the Ecobee logic first.  You can assign sensors to modes you create in the tstat.  So, for example, I have three modes in Ecobee (separate from Vera).  Home, Away, and sleep.  For home and away, i use the "follow me" feature, that sets the temp based on a blended average of the sensors i have selected.  (in this case, all sensors selected - i have 5 today).  This way,  wherever i am, the temp is adjusted accordingly.  If I'm only in one room, it will set the temp based on the sensor in that room.  My wife in another room... blends the two.

Now sleep mode is the great new feature in Ecobee, where it will set the temp based on a sensor you create, and doesn't rely on motion (as it may not pick it up while you are sleeping - unless of course you sleep like my 14 yearold :-), moving constantly floppy around).  I currently only have this using my master bedroom sensor, on the second floor. 

This all works today.. that's the good news.  The bad news is that to get my Master to 68 degrees, my first floor ends up being even lower - AC i'm wasting. 

That's where i'm hoping the vents come in.  Today, prior to Watou's version change, i just had a scene that ran at 10pm that closed several vents downstairs (or that was the plan... as I've only installed two vents so far).  My thinking would be that not only would that allow possibly more airflow upstairs cooling my Master, but also mitigate the large delta between first and second floor temps by minimizing the cooling downstairs.

NOW.. with the ability to use the Ecobee sensors, i can automate this better than just creating the 10pm scene.  So.. without having done any thinking around how to actually do this ... here's what i'm planning on doing:

1. for Home and Away, let Ecobee and "follow me" do the heavy lifting.  (note, i do have a trigger than when i arm my alarm, it automatically sets the Ecobee to Away).
2. Since this is mostly a night time sleep issue.. when "Sleep" is started on the Ecobee, i want Vera to look at the temps in the rooms (all sensors) - but specifically i want to compare the downstairs temp to the master bedroom temp.  If it is, which occurs more in the hot summer, say a more than 4 degree delta, then close the vents downstairs to get the two floors to equal out, while still letting Ecobee manage getting my Master bedroom temp to the right setting.
3. Ultimately, i may try to do #2 all the time, effectively load balancing around my house - but i think that might get too complicated in conjunction with "follow me". 

Anyhoo... that's my plan.  what am i missing?

EDIT.  i see our posts crossed Watou... clearly on the same page i believe.  :-)

Interesting. I was under the impression from my conversations with Ecobee that if I had more than one remote temp sensor, Ecobee would automaticly use an average between those sensors. Are you saying that I could have "Home" mode use my downstairs temp sensor and Sleep Mode use the upstairs one?
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 10, 2015, 06:47:17 pm
@sleif and @mda...

I think you need to use more of the Ecobee logic first.  You can assign sensors to modes you create in the tstat.  So, for example, I have three modes in Ecobee (separate from Vera).  Home, Away, and sleep.  For home and away, i use the "follow me" feature, that sets the temp based on a blended average of the sensors i have selected.  (in this case, all sensors selected - i have 5 today).  This way,  wherever i am, the temp is adjusted accordingly.  If I'm only in one room, it will set the temp based on the sensor in that room.  My wife in another room... blends the two.

Now sleep mode is the great new feature in Ecobee, where it will set the temp based on a sensor you create, and doesn't rely on motion (as it may not pick it up while you are sleeping - unless of course you sleep like my 14 yearold :-), moving constantly floppy around).  I currently only have this using my master bedroom sensor, on the second floor. 

This all works today.. that's the good news.  The bad news is that to get my Master to 68 degrees, my first floor ends up being even lower - AC i'm wasting. 

That's where i'm hoping the vents come in.  Today, prior to Watou's version change, i just had a scene that ran at 10pm that closed several vents downstairs (or that was the plan... as I've only installed two vents so far).  My thinking would be that not only would that allow possibly more airflow upstairs cooling my Master, but also mitigate the large delta between first and second floor temps by minimizing the cooling downstairs.

NOW.. with the ability to use the Ecobee sensors, i can automate this better than just creating the 10pm scene.  So.. without having done any thinking around how to actually do this ... here's what i'm planning on doing:

1. for Home and Away, let Ecobee and "follow me" do the heavy lifting.  (note, i do have a trigger than when i arm my alarm, it automatically sets the Ecobee to Away).
2. Since this is mostly a night time sleep issue.. when "Sleep" is started on the Ecobee, i want Vera to look at the temps in the rooms (all sensors) - but specifically i want to compare the downstairs temp to the master bedroom temp.  If it is, which occurs more in the hot summer, say a more than 4 degree delta, then close the vents downstairs to get the two floors to equal out, while still letting Ecobee manage getting my Master bedroom temp to the right setting.
3. Ultimately, i may try to do #2 all the time, effectively load balancing around my house - but i think that might get too complicated in conjunction with "follow me". 

Anyhoo... that's my plan.  what am i missing?

EDIT.  i see our posts crossed Watou... clearly on the same page i believe.  :-)

Interesting. I was under the impression from my conversations with Ecobee that if I had more than one remote temp sensor, Ecobee would automaticly use an average between those sensors. Are you saying that I could have "Home" mode use my downstairs temp sensor and Sleep Mode use the upstairs one?

Yep.  go into the web portal and look select your modes tile (sorry, i'm at work and don't have the exact verbiage).  From there, you can edit each mode individually... so for example, select Home.  then you should see an option for sensors.  Click on that, and select the sensors you want to use in that mode. 

As Watou said, you can create as many modes as you want.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 06:53:01 pm
I am home now and doing some testing and I am not sure if I have an issue or if I am not understanding how the app works. I included a screen shot below from vera. On the right side I have the temp setting, off, auto, heat and cool. If I change the temp to 77* and select cool, it doesn't seem to change the Ecobee temperature setting. It does however seem to change modes. If I select cool in Vera or Off, Ecobee changes it's mode but it doesn't seem like I can change the termperature set point from Vera. I also noticed that the Vera app doesn't seem to reflect the mode that Ecobee is in. If for example Ecobee is in Cool mode, the App was showing it to be in OFF mode and the temp doesn't seem to reflect the correct set point that I have on the Ecobee. I tried refreshing the page and it still didn't seem to reflec the correct temperature.

I will mess with it a bit later after a beer or two and verify my results. I will also review your reply above.

I see in the screenshot that the main Ecobee device shows that you pressed the Get PIN button, but had not, within the ten minute window, entered that PIN at Ecobee.  That means that Vera cannot communicate with the API until those steps are completed per the document at : http://watou.github.io/vera-ecobee/

Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 10, 2015, 06:58:49 pm
I am home now and doing some testing and I am not sure if I have an issue or if I am not understanding how the app works. I included a screen shot below from vera. On the right side I have the temp setting, off, auto, heat and cool. If I change the temp to 77* and select cool, it doesn't seem to change the Ecobee temperature setting. It does however seem to change modes. If I select cool in Vera or Off, Ecobee changes it's mode but it doesn't seem like I can change the termperature set point from Vera. I also noticed that the Vera app doesn't seem to reflect the mode that Ecobee is in. If for example Ecobee is in Cool mode, the App was showing it to be in OFF mode and the temp doesn't seem to reflect the correct set point that I have on the Ecobee. I tried refreshing the page and it still didn't seem to reflec the correct temperature.

I will mess with it a bit later after a beer or two and verify my results. I will also review your reply above.

I see in the screenshot that the main Ecobee device shows that you pressed the Get PIN button, but had not, within the ten minute window, entered that PIN at Ecobee.  That means that Vera cannot communicate with the API until those steps are completed per the document at : http://watou.github.io/vera-ecobee/

Too many beers?  :-)
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 07:13:38 pm
I am home now and doing some testing and I am not sure if I have an issue or if I am not understanding how the app works. I included a screen shot below from vera. On the right side I have the temp setting, off, auto, heat and cool. If I change the temp to 77* and select cool, it doesn't seem to change the Ecobee temperature setting. It does however seem to change modes. If I select cool in Vera or Off, Ecobee changes it's mode but it doesn't seem like I can change the termperature set point from Vera. I also noticed that the Vera app doesn't seem to reflect the mode that Ecobee is in. If for example Ecobee is in Cool mode, the App was showing it to be in OFF mode and the temp doesn't seem to reflect the correct set point that I have on the Ecobee. I tried refreshing the page and it still didn't seem to reflec the correct temperature.

I will mess with it a bit later after a beer or two and verify my results. I will also review your reply above.

I see in the screenshot that the main Ecobee device shows that you pressed the Get PIN button, but had not, within the ten minute window, entered that PIN at Ecobee.  That means that Vera cannot communicate with the API until those steps are completed per the document at : http://watou.github.io/vera-ecobee/

I guess I didn't go into the vera device and select save after adding the pin code to Ecobee. Ecobee shows 1 device as it did before. The Vera screen is different now and shows one theremostat in that device. So I do have that correct now or at least I think I do. Vera still doesn't seem to change the set temp in Ecobee. Below is screen shot of the Vera page. You can see the temp is set to 80 and in Cool mode. The Ecobee is still showing a set temp of 76.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 07:14:38 pm
Here is the Ecobee screen shot. As I said, I can change from Off to heat, cool and auto. Just not change the temp.

Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 07:18:51 pm
@sleif and @mda...

I think you need to use more of the Ecobee logic first.  You can assign sensors to modes you create in the tstat.  So, for example, I have three modes in Ecobee (separate from Vera).  Home, Away, and sleep.  For home and away, i use the "follow me" feature, that sets the temp based on a blended average of the sensors i have selected.  (in this case, all sensors selected - i have 5 today).  This way,  wherever i am, the temp is adjusted accordingly.  If I'm only in one room, it will set the temp based on the sensor in that room.  My wife in another room... blends the two.

Now sleep mode is the great new feature in Ecobee, where it will set the temp based on a sensor you create, and doesn't rely on motion (as it may not pick it up while you are sleeping - unless of course you sleep like my 14 yearold :-), moving constantly floppy around).  I currently only have this using my master bedroom sensor, on the second floor. 

This all works today.. that's the good news.  The bad news is that to get my Master to 68 degrees, my first floor ends up being even lower - AC i'm wasting. 

That's where i'm hoping the vents come in.  Today, prior to Watou's version change, i just had a scene that ran at 10pm that closed several vents downstairs (or that was the plan... as I've only installed two vents so far).  My thinking would be that not only would that allow possibly more airflow upstairs cooling my Master, but also mitigate the large delta between first and second floor temps by minimizing the cooling downstairs.

NOW.. with the ability to use the Ecobee sensors, i can automate this better than just creating the 10pm scene.  So.. without having done any thinking around how to actually do this ... here's what i'm planning on doing:

1. for Home and Away, let Ecobee and "follow me" do the heavy lifting.  (note, i do have a trigger than when i arm my alarm, it automatically sets the Ecobee to Away).
2. Since this is mostly a night time sleep issue.. when "Sleep" is started on the Ecobee, i want Vera to look at the temps in the rooms (all sensors) - but specifically i want to compare the downstairs temp to the master bedroom temp.  If it is, which occurs more in the hot summer, say a more than 4 degree delta, then close the vents downstairs to get the two floors to equal out, while still letting Ecobee manage getting my Master bedroom temp to the right setting.
3. Ultimately, i may try to do #2 all the time, effectively load balancing around my house - but i think that might get too complicated in conjunction with "follow me". 

Anyhoo... that's my plan.  what am i missing?

EDIT.  i see our posts crossed Watou... clearly on the same page i believe.  :-)

Interesting. I was under the impression from my conversations with Ecobee that if I had more than one remote temp sensor, Ecobee would automaticly use an average between those sensors. Are you saying that I could have "Home" mode use my downstairs temp sensor and Sleep Mode use the upstairs one?

Yep.  go into the web portal and look select your modes tile (sorry, i'm at work and don't have the exact verbiage).  From there, you can edit each mode individually... so for example, select Home.  then you should see an option for sensors.  Click on that, and select the sensors you want to use in that mode. 

As Watou said, you can create as many modes as you want.

I now see where you can add modes and associate them with particular sensors which is great. It seems that the modes are tied directly to schedules. Can I manually change modes via Vera as part of my scenes? I poked around in the Vera Devices and I didn't see anywhere in that that I can select Sleep, Downstairs (I created a new mode), etc. There is one device in Vera that shows Home and Away but not any of the other modes. Because I rarely use my AC and heating, my goal is to trigger the modes manually on an as needed basis and not automatically based on schedules.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 07:20:28 pm
I am home now and doing some testing and I am not sure if I have an issue or if I am not understanding how the app works. I included a screen shot below from vera. On the right side I have the temp setting, off, auto, heat and cool. If I change the temp to 77* and select cool, it doesn't seem to change the Ecobee temperature setting. It does however seem to change modes. If I select cool in Vera or Off, Ecobee changes it's mode but it doesn't seem like I can change the termperature set point from Vera. I also noticed that the Vera app doesn't seem to reflect the mode that Ecobee is in. If for example Ecobee is in Cool mode, the App was showing it to be in OFF mode and the temp doesn't seem to reflect the correct set point that I have on the Ecobee. I tried refreshing the page and it still didn't seem to reflec the correct temperature.

I will mess with it a bit later after a beer or two and verify my results. I will also review your reply above.

I see in the screenshot that the main Ecobee device shows that you pressed the Get PIN button, but had not, within the ten minute window, entered that PIN at Ecobee.  That means that Vera cannot communicate with the API until those steps are completed per the document at : http://watou.github.io/vera-ecobee/

Too many beers?  :-)

Or not enough beer!   ;D
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 07:21:23 pm
You can see the temp is set to 80 and in Cool mode. The Ecobee is still showing a set temp of 76.

The screenshot also still shows that the plugin has not yet been authorized by ecobee.com, so the devices in Vera are going to be out of sync with the web portal and real thermostat.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 07:23:06 pm
... Are you saying that I could have "Home" mode use my downstairs temp sensor and Sleep Mode use the upstairs one?

Yes.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 07:26:08 pm
You can see the temp is set to 80 and in Cool mode. The Ecobee is still showing a set temp of 76.

The screenshot also still shows that the plugin has not yet been authorized by ecobee.com, so the devices in Vera are going to be out of sync with the web portal and real thermostat.

So authorization takes time after adding the pin code? How long should I expect it to take?
By the way, I hope my questions aren't dumb. I did go back to your github documents and didn't see anything there about authorization time.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 07:33:27 pm
Can I manually change modes via Vera as part of my scenes?

I poked around in the Vera Devices and I didn't see anywhere in that that I can select Sleep, Downstairs (I created a new mode), etc. There is one device in Vera that shows Home and Away but not any of the other modes. Because I rarely use my AC and heating, my goal is to trigger the modes manually on an as needed basis and not automatically based on schedules.

Yes, by calling the SetClimateHold action on the "home" device.  You can do this via a scene action advanced editor (see attached as an example), via PLEG if you use it, or in custom Luup code (search on how to call Luup actions and use the spec in the plugin doc).  The plugin calls this action itself when you press the Home and Away buttons, but you can specify any climateRef string you create as well as wakeup, away, home, and sleep when invoked as described above.

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 07:36:53 pm
So authorization takes time after adding the pin code? How long should I expect it to take?
By the way, I hope my questions aren't dumb. I did go back to your github documents and didn't see anything there about authorization time.

You are quite right to ask how long PIN authorization should take, as it's not in the documentation.  It should take about three minutes or so.  This is probably an area I could speed up.  Note that you have to enter the PIN in the ecobee.com web portal with every PIN code you generate, within about 9 minutes of pressing the Get PIN button, and then wait three minutes or more.  You may need to refresh the browser once after that, but I'm not sure.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 07:43:50 pm
I also noticed in screenshots that the Vera device's name for the thermostat is the long decimal ID number, which means you didn't name your thermostat at ecobee.com.  This is not a problem, and you can rename the devices in Vera if you wanted, or instead rename at ecobee.com and delete the Vera devices, which will get re-created on the next poll, with the new names.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 07:47:17 pm
So authorization takes time after adding the pin code? How long should I expect it to take?
By the way, I hope my questions aren't dumb. I did go back to your github documents and didn't see anything there about authorization time.

You are quite right to ask how long PIN authorization should take, as it's not in the documentation.  It should take about three minutes or so.  This is probably an area I could speed up.  Note that you have to enter the PIN in the ecobee.com web portal with every PIN code you generate, within about 9 minutes of pressing the Get PIN button, and then wait three minutes or more.  You may need to refresh the browser once after that, but I'm not sure.

Ok.. It's been about an hour since I added the pin and Vera still doesn't appear to reflect the current set temp and the Vera screen doesn't appear any different. Vera shows 68 and Ecobee shows  a set temp of 78.

Edit: I changed the names in Vera.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 10, 2015, 07:51:51 pm
Ok.. It's been about an hour since I added the pin and Vera still doesn't appear to reflect the current set temp and the Vera screen doesn't appear any different. Vera shows 68 and Ecobee shows  a set temp of 78.

Look at the details for the thermostat device (right arrow) and find the Control pane.  See the two vertical setpoint sliders, and see if either agrees with the value it should be.  If so, this is possibly a UI7 display issue dealing with setpoints.  Do other changes get reflected in Vera, like the current operating mode (Cool, Heat, Auto, Off)?
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 10, 2015, 08:01:32 pm
Ok.. It's been about an hour since I added the pin and Vera still doesn't appear to reflect the current set temp and the Vera screen doesn't appear any different. Vera shows 68 and Ecobee shows  a set temp of 78.

Look at the details for the thermostat device (right arrow) and find the Control pane.  See the two vertical setpoint sliders, and see if either agrees with the value it should be.  If so, this is possibly a UI7 display issue dealing with setpoints.  Do other changes get reflected in Vera, like the current operating mode (Cool, Heat, Auto, Off)?

Using the vertical sliders in the Control screen, I can change the set temp and switch from Off to Cool, Heat or Auto but it still doesn't appear to reflect the correct set point in the main device page as shown in the photos above. What I think is displaying in the main device page is my heating setpoint despite being in cool mode.

I have my heat set really low so Ecobee doesn't turn the heat on and by setting the heat to 68, there is no liklihood of the heat turning on as my house is never below 68. I have my cooling mode set to 84 so the ac doesn't turn on automatically as well. If I need to use the heat or AC, I just set the temp and select heat or cool so it's in manual hold mode.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 11, 2015, 05:38:36 am
If you are running the Ecobee plugin v1.2 on UI7, the attached .zip file contains 4 .json files that will give you non-default icons for the ecobee, thermostat, humidistat and house devices.  Do not apply these files unless you are running plugin v1.2 on UI7. 

You would apply these by extracting the four files from the .zip, going to Apps -> Develop Apps -> Luup files, and then dragging/dropping the four .json files to the drop target.  You would then wait a minute and then refresh your browser.

The icons are currently static -- they won't grey/un-grey based on state.  This should be added in v1.3, which is intended to have UI7 fixes.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 11, 2015, 09:59:38 am
@watou, total nit, but no joy for updating the ecobee tstat icon with a new version?  😉
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 11, 2015, 10:10:42 am
@watou, total nit, but no joy for updating the ecobee tstat icon with a new version?  😉

I haven't gotten around to it.  It would be an ecobee3, 50x50 PNG, ideally with a shadow fading to a transparent background like the current (http://watou.github.io/vera-ecobee/icons/thermostat.png), but not showing a temperature or mode that could mislead.  I was thinking that it would look too much like a black square with rounded corners -- too boring.

But if your image creating skills are up to it and you can improve on the old SmartSI icon, I will update the source with it at github, and voil?!
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 11, 2015, 10:15:22 am
@watou, total nit, but no joy for updating the ecobee tstat icon with a new version?  😉

I haven't gotten around to it.  It would be an ecobee3, 50x50 PNG, ideally with a shadow fading to a transparent background like the current (http://watou.github.io/vera-ecobee/icons/thermostat.png), but not showing a temperature or mode that could mislead.  I was thinking that it would look too much like a black square with rounded corners -- too boring.

But if your image creating skills are up to it and you can improve on the old SmartSI icon, I will update the source with it at github, and voil?!

Lol... in knew that was coming 😃

I have a Bud that might be able to do this. Lemme ask!
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 11, 2015, 04:15:26 pm
@watou, total nit, but no joy for updating the ecobee tstat icon with a new version?  😉

I haven't gotten around to it.  It would be an ecobee3, 50x50 PNG, ideally with a shadow fading to a transparent background like the current (http://watou.github.io/vera-ecobee/icons/thermostat.png), but not showing a temperature or mode that could mislead.  I was thinking that it would look too much like a black square with rounded corners -- too boring.

But if your image creating skills are up to it and you can improve on the old SmartSI icon, I will update the source with it at github, and voil?!

Lol... in knew that was coming 😃

I have a Bud that might be able to do this. Lemme ask!

Can you make this work?
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 11, 2015, 08:14:01 pm
Can I manually change modes via Vera as part of my scenes?

I poked around in the Vera Devices and I didn't see anywhere in that that I can select Sleep, Downstairs (I created a new mode), etc. There is one device in Vera that shows Home and Away but not any of the other modes. Because I rarely use my AC and heating, my goal is to trigger the modes manually on an as needed basis and not automatically based on schedules.

Yes, by calling the SetClimateHold action on the "home" device.  You can do this via a scene action advanced editor (see attached as an example), via PLEG if you use it, or in custom Luup code (search on how to call Luup actions and use the spec in the plugin doc).  The plugin calls this action itself when you press the Home and Away buttons, but you can specify any climateRef string you create as well as wakeup, away, home, and sleep when invoked as described above.

Question for you. I created a new scene called "Cool Downstairs". It closes upstairs vents and opens downstairs vents. I created a new comfort mode in my Ecobee3 called "Downstairs" that sets a desired temp range for that mode. The idea is to add force that mode (Downstairs) when I activate the scene "Cool Downstairs".
 
I used the advanced editor in Vera's scene creation and went through my Ecobee devices and found "SetClimateHold" but unlike you screen shot, I don't get an option to add the mode "Downstairs". That is to say that there is no field for "Hold Climate Reference" as there is in your screen shot. I did find an option in the advanced scene editor called SetModeTarget and that gives me a NewModetarget" field and I tried putting "Downstairs" in there to call out my newly created comfort mode but that did nothing.

As such, I am not sure how to trigger a comfort mode in a Vera scene. Any help would be greatfully appreciated.
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 12, 2015, 12:12:06 am
Are you able to pull the default modes? I managed to create some scenes but using the ecobee plug in as the trigger.
For example changing my Vera house mode to "night" when the ecobee goes into sleep mode and set it back to "home" when the ecobee goes into "wake up" mode.
I have not created any new mode on the ecobee to check but I suppose if you could pull that mode, you would see it using that one device.

By the way I had no idea the ecobee had a wakeup mode...
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 12, 2015, 06:55:48 am
Can I manually change modes via Vera as part of my scenes?

I poked around in the Vera Devices and I didn't see anywhere in that that I can select Sleep, Downstairs (I created a new mode), etc. There is one device in Vera that shows Home and Away but not any of the other modes. Because I rarely use my AC and heating, my goal is to trigger the modes manually on an as needed basis and not automatically based on schedules.

Yes, by calling the SetClimateHold action on the "home" device.  You can do this via a scene action advanced editor (see attached as an example), via PLEG if you use it, or in custom Luup code (search on how to call Luup actions and use the spec in the plugin doc).  The plugin calls this action itself when you press the Home and Away buttons, but you can specify any climateRef string you create as well as wakeup, away, home, and sleep when invoked as described above.

Question for you. I created a new scene called "Cool Downstairs". It closes upstairs vents and opens downstairs vents. I created a new comfort mode in my Ecobee3 called "Downstairs" that sets a desired temp range for that mode. The idea is to add force that mode (Downstairs) when I activate the scene "Cool Downstairs".
 
I used the advanced editor in Vera's scene creation and went through my Ecobee devices and found "SetClimateHold" but unlike you screen shot, I don't get an option to add the mode "Downstairs". That is to say that there is no field for "Hold Climate Reference" as there is in your screen shot. I did find an option in the advanced scene editor called SetModeTarget and that gives me a NewModetarget" field and I tried putting "Downstairs" in there to call out my newly created comfort mode but that did nothing.

As such, I am not sure how to trigger a comfort mode in a Vera scene. Any help would be greatfully appreciated.

If you are using UI5, you might see a problem defining an action where the parameters don't show up.  Not sure.  Anyway, you can call SetClimateHold from Luup code similarly to what is shown here: http://forum.micasaverde.com/index.php/topic,13836.msg121293.html#msg121293

Also, when you create your own Ecobee climate/comfort setting, you will need what's called a "climate ref."  I think you can find out what the one you're interested in using is by looking at the URL when you're editing the climate in the portal:

https://www.ecobee.com/consumerportal/index.html#/thermostats/3125555665555/climate/away/edit/name

Where you see "away" in the URL above would be the HoldClimateRef for the "Away" climate/comfort setting. (What others have been calling mode in this thread.)

Hope this helps.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 12, 2015, 09:58:13 am
@watou, will that graphic work?
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 12, 2015, 10:53:57 am
Are you able to pull the default modes? I managed to create some scenes but using the ecobee plug in as the trigger.
For example changing my Vera house mode to "night" when the ecobee goes into sleep mode and set it back to "home" when the ecobee goes into "wake up" mode.
I have not created any new mode on the ecobee to check but I suppose if you could pull that mode, you would see it using that one device.

By the way I had no idea the ecobee had a wakeup mode...

I have not tried creating a scene using the default modes. I will have to try that.



If you are using UI5, you might see a problem defining an action where the parameters don't show up.  Not sure.  Anyway, you can call SetClimateHold from Luup code similarly to what is shown here: http://forum.micasaverde.com/index.php/topic,13836.msg121293.html#msg121293

Also, when you create your own Ecobee climate/comfort setting, you will need what's called a "climate ref."  I think you can find out what the one you're interested in using is by looking at the URL when you're editing the climate in the portal:

https://www.ecobee.com/consumerportal/index.html#/thermostats/3125555665555/climate/away/edit/name

Where you see "away" in the URL above would be the HoldClimateRef for the "Away" climate/comfort setting. (What others have been calling mode in this thread.)

Hope this helps.

watou

Thanks again for the help and support Watau! I really appreciate it. I hate asking questions and am usually able to figure this kind of stuff out on my own by dumb thumbing my way through things.

I'm on the latest UI7 build. I don't as of yet understand luup code and going there will only confuse me more at this point. I looked at the example in your link and it made my head spin just as did the other luup examples I have seen. I'm very proficient with my aquarium controller programming which is now simple and intuitive to me but I've also been use that type of coding for many years. I'm going to have to study the luup and Pleg coding to see if I can understand it better but I'm just not there yet and it would open a can of worms for me that would be followed by countless questions. 

Here is my url for my sleep mode.
https://www.ecobee.com/consumerportal/index.html#/thermostats/317423358848/climate/sleep/edit/name

I am assuming the "climate ref" would be "sleep" and that I don't need to include anything else from the URL in the climate ref field? 

One thing I noticed in Ecobee that was driving me nuts and has nothing to do with the plugin is the scheduling of the modes. I started playing with the schedules thinking I may need to apply a schedule to force a mode. Creating schedules seemed kind of wonky to me. It would be nice if the Ecobee schedule creator had a start point and an end point for each mode you use. Instead, you create one start point and the end point is set by the next mode. Or at least that is how I thought it worked until I added the next mode for a different time of day. I pretty much gave up on schedules since I won't be using my Ecobee that way. It did however get me thinking.. Do I need to have the mode (Upstairs as an example) part of a schedule to force the mode change through the Ecobee plugin? That is to say if I have a new mode that I created and it's not part of the Ecobee schedule, can I still force that mode?

I'm at work now so I won't be able to test any of this until later today but I plan on trying to get it figured out over the weekend. Hopefully there is light at the end of the tunnel. If I can get this scene to function properly, I will be able to use it in my both my Roomie Remote and Homewave which would be pretty cool. I use Roomie Remote for my home theater and bedroom TV universal remote. I've managed to program in all my Vera lights and some of my scenes. if I can turn the air on or off and set the zone via one scene, it would be great to be able to trigger that from Roomie which would be simple. Roomie is however worthless for Ecobee but Vera will bridge that gap through the use of scenes. 
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 12, 2015, 11:17:51 am
Using a mode change from the ecobee as a trigger did not work apparently... The "My ecobee is set to sleep" was never detected. Any idea why?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 12, 2015, 01:31:06 pm
@watou, will that graphic work?

I added it, but forgot that on the latest UI7, it's putting the temperature over top of the icon (odd).  So the little green bee in the middle is actually in the way a little.  I personally don't care, but ideally it would look correct for both UI5 and UI7 users.  Every v1.2+ ecobee plugin user is now getting the new logo though.
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 12, 2015, 01:37:19 pm
@watou, will that graphic work?

I added it, but forgot that on the latest UI7, it's putting the temperature over top of the icon (odd).  So the little green bee in the middle is actually in the way a little.  I personally don't care, but ideally it would look correct for both UI5 and UI7 users.  Every v1.2+ ecobee plugin user is now getting the new logo though.

Do I need to reinstall fur it to show up in u15?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 12, 2015, 01:40:27 pm
Here is my url for my sleep mode.
https://www.ecobee.com/consumerportal/index.html#/thermostats/317423358848/climate/sleep/edit/name

I am assuming the "climate ref" would be "sleep" and that I don't need to include anything else from the URL in the climate ref field? 

Correct.

That is to say if I have a new mode that I created and it's not part of the Ecobee schedule, can I still force that mode?

Yes.

I'm at work now so I won't be able to test any of this until later today but I plan on trying to get it figured out over the weekend. Hopefully there is light at the end of the tunnel. If I can get this scene to function properly, I will be able to use it in my both my Roomie Remote and Homewave which would be pretty cool. I use Roomie Remote for my home theater and bedroom TV universal remote. I've managed to program in all my Vera lights and some of my scenes. if I can turn the air on or off and set the zone via one scene, it would be great to be able to trigger that from Roomie which would be simple. Roomie is however worthless for Ecobee but Vera will bridge that gap through the use of scenes.

Sound great!
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 12, 2015, 01:41:57 pm
Using a mode change from the ecobee as a trigger did not work apparently... The "My ecobee is set to sleep" was never detected. Any idea why?

No, but if you tell me which firmware version number you are using, I can try it here and see if there is a bug in the plugin.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 12, 2015, 01:43:08 pm
Do I need to reinstall fur it to show up in u15?

No, but you might need to clear your browser cache.  It's just a regular image loaded over HTTP.
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 12, 2015, 01:52:57 pm
Using a mode change from the ecobee as a trigger did not work apparently... The "My ecobee is set to sleep" was never detected. Any idea why?

No, but if you tell me which firmware version number you are using, I can try it here and see if there is a bug in the plugin.

My firmware is 3.6.0.877
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on June 12, 2015, 01:56:19 pm
Do I need to reinstall fur it to show up in u15?

No, but you might need to clear your browser cache.  It's just a regular image loaded over HTTP.

Awesome .. looks good!  I did ask my buddy to do a blank one as well just in case.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 12, 2015, 02:01:00 pm
My firmware is 3.6.0.877

Sorry; I should have been more specific.  The Vera firmware will tell me which of my Veras to test the trigger against.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 12, 2015, 02:03:14 pm
Awesome .. looks good!  I did ask my buddy to do a blank one as well just in case.

Great!  I would like to credit your buddy in the documentation as having contributed the icon, if he doesn't mind that he is named (or aliased if he prefers).  Could you send along the blank one as well, just in case I can't rid the temperature text from the plugin on UI7 (it's redundant).
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 12, 2015, 02:18:14 pm
Here is my url for my sleep mode.
https://www.ecobee.com/consumerportal/index.html#/thermostats/317423358848/climate/sleep/edit/name

I am assuming the "climate ref" would be "sleep" and that I don't need to include anything else from the URL in the climate ref field? 

Correct.




Interesting. I just checked the url for the mode that I created and interestingly enough, it doesn't use the new mode name as part of the URL like the default modes. Instead, the new mode I created called "downstairs" is using "smart1" instead of "downstairs" in the url.
https://www.ecobee.com/consumerportal/index.html#/thermostats/317423358848/climate/smart1/edit/name

As such, my Climate Ref would not have been correct.
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 12, 2015, 02:26:36 pm
My firmware is 3.6.0.877

Sorry; I should have been more specific.  The Vera firmware will tell me which of my Veras to test the trigger against.

oops, should have guessed what you meant.
7.0.8 on a vera lite. (1.7.599)

I am able to trigger off of heating and cooling from the ecobee but not off of mode changes... They are different virtual devices but wondering if there is a workaround.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 12, 2015, 02:41:59 pm
My firmware is 3.6.0.877

Sorry; I should have been more specific.  The Vera firmware will tell me which of my Veras to test the trigger against.

oops, should have guessed what you meant.
7.0.8 on a vera lite. (1.7.599)

I am able to trigger off of heating and cooling from the ecobee but not off of mode changes... They are different virtual devices but wondering if there is a workaround.

Your reply triggered my memory of a small detail in the service description files.  I just added the detail to the attached S_Ecobee1.xml file.   I toggled my climate between home and away with a notification trigger for each, and Vera sent me the two emails I was hoping for.

Please download the attached S_Ecobee1.xml file, and go to App->Develop Apps->Luup files, check to box to reload after upload, and upload the file, replacing the one there now.  Then try to see if you start getting scenes/notifications triggered.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 12, 2015, 05:40:42 pm
Installed. I will test when it goes to sleep mode tonight.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 12, 2015, 06:17:02 pm
This is driving me nuts.  I have my Ecobee set to OFF.  I can't seem to toggle any modes on my Ecobee via scenes.  I also tried to just turn the AC on througha  scene without any success. I tried it through devices under scene create by selecting my Ecobee device, setting the temp to 77 and trying to select "cool" via the gui (see screen shot below). On the other hand, If I go into my Ecobee mode device in Veras devices, I can manually change the mode in Vera from OFF to Heat or Cool and change the temp by pushing the up or down arrows.

I also tried using the advanced editor feature in the scene creator without any success. I don't see any option to force the system in cool mode. I also tried to force comfort settings such as sleep or home without success too. In the advanced editor device pull down, there are obviously a few Ecobee devices to choose from. I am choosing the device I called Ecobee Mode shown in the image I attached. From there, there are dozens of command options to choose from. I am choosing ones that seem to be associated with the ServiceID:Ecobee1 as opposed to Vera related Ecobee commands if that makes sense. I know I must be doing something wrong. I assume that I have the plugin setup right because I can toggle from OFF, to Heat to Cool manually from the Vera Ecobee device.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 12, 2015, 06:23:39 pm
These are just some of the options under my Ecobee device in the scene creator advanced editor.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 12, 2015, 06:39:09 pm
I think you want the "house" device for setting climate holds.
I'm on my phone so sorry for brief reply.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 12, 2015, 06:59:08 pm
I think you want the "house" device for setting climate holds.
I'm on my phone so sorry for brief reply.

Which one would be the house device? As you can see in the photos above, the device details are cut short in the pull downs under the advanced scene editior.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 12, 2015, 08:12:33 pm
I think you want the "house" device for setting climate holds.
I'm on my phone so sorry for brief reply.
Which one would be the house device? As you can see in the photos above, the device details are cut short in the pull downs under the advanced scene editior.

Your #56 device looks to be the thermostat device.  Some other numbered device, maybe #57 or #58, might be the one with the house icon on it.  From that device, you can trigger when the climate changes.
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 12, 2015, 08:14:48 pm
This is driving me nuts.  I have my Ecobee set to OFF.  I can't seem to toggle any modes on my Ecobee via scenes.  I also tried to just turn the AC on througha  scene without any success. I tried it through devices under scene create by selecting my Ecobee device, setting the temp to 77 and trying to select "cool" via the gui (see screen shot below). On the other hand, If I go into my Ecobee mode device in Veras devices, I can manually change the mode in Vera from OFF to Heat or Cool and change the temp by pushing the up or down arrows.

I also tried using the advanced editor feature in the scene creator without any success. I don't see any option to force the system in cool mode. I also tried to force comfort settings such as sleep or home without success too. In the advanced editor device pull down, there are obviously a few Ecobee devices to choose from. I am choosing the device I called Ecobee Mode shown in the image I attached. From there, there are dozens of command options to choose from. I am choosing ones that seem to be associated with the ServiceID:Ecobee1 as opposed to Vera related Ecobee commands if that makes sense. I know I must be doing something wrong. I assume that I have the plugin setup right because I can toggle from OFF, to Heat to Cool manually from the Vera Ecobee device.

This is odd. I have tested two things related to what you are doing: I created a scene to set the ecobee in away mode triggered by my phone geofence and it went to away hold (Not very good because it lasts at least 2 hours and the ecobee does not remove it when you come back by triggering the sensors). I also tested the opposite with a scene to trigger a hold home and it worked...
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 12, 2015, 08:24:23 pm
I think you want the "house" device for setting climate holds.
I'm on my phone so sorry for brief reply.
Which one would be the house device? As you can see in the photos above, the device details are cut short in the pull downs under the advanced scene editior.

Your #56 device looks to be the thermostat device.  Some other numbered device, maybe #57 or #58, might be the one with the house icon on it.  From that device, you can trigger when the climate changes.

#56 is the device I call Ecobee Mode and that was the one I was trying to change the modes from. It works if I change the modes directly from the device but when I try to via a scene, it doesn't work. Having said that,  I don't have any device with a house on it that I can see. Below is a screen shot of my Ecobee devices excluding the motion sensors. There is one device that says get pin. I have generated a pin and added it to ecobee apps and I do show a Vera device listed under the Ecobee "My Apps" page.

My guess is my issue is related to my lack of understanding with the plugin and Ecobee coupled with my lack of understanding when it comes to using the advanced scene editior.

Edit.. I think you are talking about device 58 which says Home/Away..

Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 12, 2015, 08:38:46 pm
Assuming Device 58 is the correct device, when I select that in the advanced scene editor I have the following options (see image) available to me in the pulldown. Which would I select to Change the system from OFF to Cool or OFF to one of the comfort modes?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 12, 2015, 08:42:29 pm
Edit.. I think you are talking about device 58 which says Home/Away..

Yes; try that one to trigger based on the current climate changing.

Assuming Device 58 is the correct device, when I select that in the advanced scene editor I have the following options (see image) available to me in the pulldown. Which would I select to Change the system from OFF to Cool or OFF to one of the comfort modes?

Switching the thermostat between Off, Cool, Heat and Auto is a different concept from switching the house device to different comfort settings (formerly called climates and what has confusingly been called modes in this thread).  I recommend studying those concepts in the native web portal for a bit to see how they mean different things, and then return to the plugin to see how you can use them in automation.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 12, 2015, 08:59:13 pm
Edit.. I think you are talking about device 58 which says Home/Away..

Yes; try that one to trigger based on the current climate changing.

Assuming Device 58 is the correct device, when I select that in the advanced scene editor I have the following options (see image) available to me in the pulldown. Which would I select to Change the system from OFF to Cool or OFF to one of the comfort modes?

Switching the thermostat between Off, Cool, Heat and Auto is a different concept from switching the house device to different comfort settings (formerly called climates and what has confusingly been called modes in this thread).  I recommend studying those concepts in the native web portal for a bit to see how they mean different things, and then return to the plugin to see how you can use them in automation.

Is it even possible to toggle between Off, Cool, Heat and Auto via scenes using the plugin? That is the easiest method I can imagine for my purpose since I rarely use my AC and generally only use it via manual intervention on an "as needed" basis. I really don't want to keep my system in Auto mode because it inevitably will turn on when I don't need it or don't want it to. I will however spend some time studying the comfort settings to better understand them and see if I can put them to use but I see myself keeping the system in the Off mode except when I need to cool things down.

I was digging around in the adanced scene editor options for device 58 and don't have an option for "SetClimateHold" that provides me the "HoldClimateRef" field as show in the screen shot you posted earlier in this thread. See image below of your screen shot and a screen shot of SetClimateHold on my device 58.


Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 13, 2015, 04:20:35 am
I was digging around in the adanced scene editor options for device 58 and don't have an option for "SetClimateHold" that provides me the "HoldClimateRef" field as show in the screen shot you posted earlier in this thread. See image below of your screen shot and a screen shot of SetClimateHold on my device 58.

I think this is in the area of UI7 user interface "intuitiveness," which, as they say, is above my pay grade.  I think that, with enough poking around, you should be able to get to the point of the screenshot I provided, but I can't say that with authority.  Good luck!

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 13, 2015, 11:32:30 am
My firmware is 3.6.0.877

Sorry; I should have been more specific.  The Vera firmware will tell me which of my Veras to test the trigger against.

oops, should have guessed what you meant.



7.0.8 on a vera lite. (1.7.599)

I am able to trigger off of heating and cooling from the ecobee but not off of mode changes... They are different virtual devices but wondering if there is a workaround.

Your reply triggered my memory of a small detail in the service description files.  I just added the detail to the attached S_Ecobee1.xml file.   I toggled my climate between home and away with a notification trigger for each, and Vera sent me the two emails I was hoping for.

Please download the attached S_Ecobee1.xml file, and go to App->Develop Apps->Luup files, check to box to reload after upload, and upload the file, replacing the one there now.  Then try to see if you start getting scenes/notifications triggered.

watou

Watou,

It did not work. At least not for the wakeup and sleep modes: When the ecobee switched to them, it failed to trigger the vera. I have not tested home and away but I have the reverse logic for these where I have the vera trigger a "resume" mode instead. Any other idea as to how I can get the ecobee to trigger when it changes mode to sleep?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 13, 2015, 01:25:23 pm
It did not work. At least not for the wakeup and sleep modes: When the ecobee switched to them, it failed to trigger the vera. I have not tested home and away but I have the reverse logic for these where I have the vera trigger a "resume" mode instead. Any other idea as to how I can get the ecobee to trigger when it changes mode to sleep?

I saw the triggers for changing currentClimateRef work on UI5 1.5.622 with the new S_Ecobee1.xml in place.  (To either home or sleep, the two climates I tested.) I will try it on my UI7 1.7.1181 (VeraEdge) and let you know what I see.

EDIT: I just saw the trigger work on my UI7 1.7.1811 VeraEdge with the v1.2 plugin + updated S_Ecobee.1xml file, as it does on UI5 1.5.622 Vera 3.  Vera sent me an email notification when I switched the device to "away" as expected.  Make sure you properly replaced the S_Ecobee1.xml file on your Vera and had it restart after upload.  Also review your automation to make sure it triggers off of this change.
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 13, 2015, 01:55:34 pm
I will try again. I have a sudden doubt about having messed around my config yesterday and having recovered from a backup which may have overwritten the xml file.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 13, 2015, 02:03:44 pm
The plugin is definitely working.. I was able to add controls to my Homewave interface to change the set temp and toggle between OFF, Auto, Cool and Heat using device 56. So I can control my Ecobee with Homewave which is great. Below is a screen shot of my Homewave AC control screen which is a bit of a work in progress.

Now I need to figure out how to toggle between OFF and Cool, Heat or Auto using a scene. I played around with it more this morning but can't figure it out. I've tried SetModeTarget and entered "Auto" in the new target mode field and that didn't work. I am assuming that Auto would be the correct string unless that is where I could enter comfort modes?? I know I have to be missing something. Am I correct that SetModeTarget should be the interface to switch between OFF, Auto Cool and Heat?  I assume I should be able to switch between OFF, Auto, Cool and Heat using the advanced scene editor or will I need to use pleg or luup code?
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 13, 2015, 02:27:46 pm
Could it be that I need an additional action before the mode change action? Below is a screen shot of what I tested this morning to try to get my Ecobee to change to Auto mode.
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 13, 2015, 03:58:23 pm
Just an idea here and I am wondering too. When you have a schedule set up on the ecobee, it seems like setting up hold away and hold home works. You can also run a resume. I am doing these with a scene. It sounds like you are trying to change the mode of the ecobee in spite of the scheduled mode. For they ecobee they are really different status. Have you tried triggering a hold?
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 13, 2015, 04:12:55 pm
Just an idea here and I am wondering too. When you have a schedule set up on the ecobee, it seems like setting up hold away and hold home works. You can also run a resume. I am doing these with a scene. It sounds like you are trying to change the mode of the ecobee in spite of the scheduled mode. For they ecobee they are really different status. Have you tried triggering a hold?

At this point I am not using any schedules. Just manually turning my AC on and off. I see an option the advanced scene editor for SetClimateHold but not Hold Home or Hold Away. How are you setting those?
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 13, 2015, 06:58:17 pm
I did not have to write any luup code. One of the devices created by the plug in shows up with a generic zwave logo and has 2 buttons "home and away". It is under the category "interfaces and Misc Devices" toggling this device sets it to hold home or hold away. When you use this device and go in the advanced editor you will see

Code: [Select]
Service: urn:ecobee-com:serviceId:Ecobee1
SetClimateHold

with the argument:
Code: [Select]
HoldClimateRef: home
I used this device to test the climate hold and I am using it now to set "resume program"

Look around the different devices the app created. The Thermostat device itself may not have everything you need.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 13, 2015, 08:17:57 pm
I did not have to write any luup code. One of the devices created by the plug in shows up with a generic zwave logo and has 2 buttons "home and away". It is under the category "interfaces and Misc Devices" toggling this device sets it to hold home or hold away. When you use this device and go in the advanced editor you will see

Code: [Select]
Service: urn:ecobee-com:serviceId:Ecobee1
SetClimateHold

with the argument:
Code: [Select]
HoldClimateRef: home
I used this device to test the climate hold and I am using it now to set "resume program"

Look around the different devices the app created. The Thermostat device itself may not have everything you need.

That would be my device 58. My issue seems to be getting the system out of OFF mode. If I am in OFF mode, toggling the state does nothing. Near as I can tell, I need to keep the system in Auto mode to toggle to different comfort settings. At that point, I could probably use the modes to accomplish what I'm after. I just hate leaving my AC in auto mode. I have to believe (since I can do this manually via the device itself) that there is a way through the use of a scene to switch from OFF to Cool or from OFF to Heat. It may be that I have to use code to do it. I wish I knew more about Luup code or Pleg.

Tomorrow or possibly later today I'll play with my comfort settings and try changing the modes again through the scenes only this time I will do it with the Ecobee in Auto mode and see if that makes a difference. The only thing that has be scratching my head is the lack of a HoldClimateRef field when I select SetClimateRef (for device 58) in the advanced scene editior. 

That said, I'm very happy that I can now control my AC from Homewave and don't need to use the Ecobee app for that. That adds a new level of convenience.  There was a point that I was wondering if I made the right choice with the Ecobee. Now that I can control it from my main automation app and have the use of multiple temp sensors, I'm very happy with my purchase decision. As such I'm really stoked on that and greatful to Watau for putting this app together.

Now if I could just get the scene to work, then I could control it from Roomie as well. For some odd reason, I can't control the Ecobee from Roomie as it doesn't see the Ecobee device in Vera. I can however control all my other Vera devices from it as well as any scenes. As such, I just need to figure out the scene thing so I can use the vents and cooling/heating control with a single button and also add that to Roomie.   
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 13, 2015, 10:10:58 pm
I put my AC in in Auto mode and didn't have any success changing the comfort states. Or at least not that I could tell. I think my issue is that I don't have the HoldClimateRef field when I select SetClimateHold. That has me a bit miffed. I'm tempted to uninstall the Ecobee App in Vera and reinstall it but now that I've got my Homewave app setup to control the Ecobee, I'm a little reluctant to do so if it's going to be an effort in futility.

Watau, I assume you were also testing in UI7? You mentioned earlier that this could be a Vera issue..

Anhman,
You're on UI7, right?
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 13, 2015, 10:18:46 pm
I did not have to write any luup code. One of the devices created by the plug in shows up with a generic zwave logo and has 2 buttons "home and away". It is under the category "interfaces and Misc Devices" toggling this device sets it to hold home or hold away. When you use this device and go in the advanced editor you will see

Code: [Select]
Service: urn:ecobee-com:serviceId:Ecobee1
SetClimateHold

with the argument:
Code: [Select]
HoldClimateRef: home
I used this device to test the climate hold and I am using it now to set "resume program"

Look around the different devices the app created. The Thermostat device itself may not have everything you need.

OK.. That was helpful. I went into my scene and included the device (#58) with home in it and set the state to Home. Then when I went into the advanced editor, low and behold, SetClimateRef field was there with "Home" in it as the state value. I assume I can now change that value to smart1 or smart2 to reflect my custom comfort modes. 

Thank you very much for that info.. I will do some more testing and report back. 
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 13, 2015, 10:32:02 pm
I did not have to write any luup code. One of the devices created by the plug in shows up with a generic zwave logo and has 2 buttons "home and away". It is under the category "interfaces and Misc Devices" toggling this device sets it to hold home or hold away. When you use this device and go in the advanced editor you will see

Code: [Select]
Service: urn:ecobee-com:serviceId:Ecobee1
SetClimateHold

with the argument:
Code: [Select]
HoldClimateRef: home
I used this device to test the climate hold and I am using it now to set "resume program"

Look around the different devices the app created. The Thermostat device itself may not have everything you need.

OK.. That was helpful. I went into my scene and included the device (#58) with home in it and set the state to Home. Then when I went into the advanced editor, low and behold, SetClimateRef field was there with "Home" in it as the state value. I assume I can now change that value to smart1 or smart2 to reflect my custom comfort modes. 

Thank you very much for that info.. I will do some more testing and report back.


Wooohooo!!! Or should I say waaaaatouuuuu!!! That worked! I was able to toggle from Away & Hold to Home & Hold. Thank you anhman and watou!!! Next I will try to edit that SetClimateRef to reflect my new climate states and see if that works which I suspect it will.

Worst case, I have my temp setpoints for home set to acceptable numbers and I will use the set points in Away such that my AC or Heat won't turn on. Then I will create a scene to toggle the state from Home to Away that will effectively shut my AC Off.

Edit.. I was able to modify the Ref value and change it to smart1 which reflects one of the new comfort modes I created and the scene changed the Ecobee state and my AC came on.. Now I know what I'm doing and have to put thought into the comfort settings but the great news is that I have it working now.

Thank you guys for putting up with my countless posts in this thead. I'm active on a number of forums and people like me that post repetitively because they don't understand what they are doing tend to drive me crazy sometimes. As such, I greatly appreciate your patience with me and your help!
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 13, 2015, 10:55:35 pm
Edit.. I just got through modifying my scenes and adding the needed Comfort modes and Settings.

I'm pretty damn excited now. Best of all, I didn't pull all my hair out trying to figure this out. Thanks to Watou for the great plugin and the help. Thanks to Anhman for getting me on the right path with the HoldClimateRef. Thanks to Tomgru for the idea of using custom Comfort settings and your help. The answer was to add the Thermostat device to the scene first and let it select the default "home". Then go to the advanced scene editior and change the ClimateRef to reflect the appropirate Comfort Mode. Oh yea, speaking of which, I never would have figured out the correct climate ref without Watou's advice of looking at the url from the Ecobee web portal. The new comfort modes I added came up as "Smart1, Smart2 and Smart3 instead of the names I gave them. Counter intuitive when the default ones are Home, Away, etc. That's is an Ecobee thing.

Here's a rundown.

I have two external temperature sensors that I'm using. I am not using the one on the thermostat.  One snesor in my living room which is where most of my downstairs time is spent. The second temp sensor is upstairs in my master bedroom. I have a 3rd temp sensor which I am not presently using but may put it in one of the kids rooms and use an average between the upstairs temp sensors.

I use two different apps to control my Vera. First is Homewave and the second is Roomie Remote. Roomie is my universal remote for my home theater and my bedroom AV system. It also works great with Vera and allows control over any Vera switch and scene. Homewave is my go to app for Vera control but we use Roomie very frequently since it's our go to home theater remote. As such, having Vera control in it is all too convenient.

I have 5 Econet vents setup in my home. Two are downstairs with one being in my office and the 2nd being in the kitchen. The other 3 Econet vents are upstairs with one being in my master bathroom, one in my daughters room and one in my sons room.

I created 3 scenes related to the zones and a 4th scene that toggles my AC to a mode that essentially shuts the AC system off.

The modes are as follows:
Heat Cool Downstairs: This opens the downstairs vents, closes the upstairs vents and sets the AC to 77* and heat to 72*. This scene uses the downstairs temp sensor via a dedicated comfort setting. 

Heat Cool Upstairs: Closes downstairs vents, opens the master bath vent 100% and opens the 2 kids rooms vents 30%  and sets the AC to 77* and heat to 72*. This scene uses the upstairs temp sensor via a dedicated comfort setting. 

Heat Cool Up & Down: Opens downstairs vents, Opens master bath 100% and opens the kids vents 50% and sets the AC to 77* and heat to 72*. This scene uses an average between the upstairs and downstairs temp sensors via a dedicated comfort setting. 

AC Off: toggle the AC to a mode that neither the heat or air will come on. 

In my Homewave app, I have each of the scenes programmed in as well as the rest of my AC controls for manual AC control. I also have each of the vents included in that screen so I can manually control each vent if I choose to. I also have my upstairs and downstairs temps displayed.

In my Roomie app, I have a dedicated Vera screen which now has my 4 AC related scenes.

I have to say that I am really stoked on this setup. My downstairs and upstairs cool so much faster now. Despite only have a handfull of Econet vents out of nearly 20 vents in my house and only a few closing at any given time, my system is much more efficient and my AC runs much less as a result to cool off any given zone. The Ecobee plugin took me some time to figure out and I owe it to a couple forum members for their help and guidance in figuring out how to set and use comfort modes within my Ecobee and the Vera plugin but now that I have it working, I'm really excited. These vents will make using my AC much less painful this summer and the Vera integration is seemless. Especially with the use of the Apps.

Here are a couple screen shots. These are from my iPad. We have these same apps on all of our ipads, iphones as well as the iPad we have mounted on the wall in our kitchen. The first is my Homewave AC control screen and the second is my Roomie Remote Vera screen. I will likely create another remote screen in Roomie that will be dedicated to the AC but there really isn't much need for that as I'm creating AC related activities on the other Roomie Remote screen that are used to control things like DirecTV, Bluray, Netflix etc which in turn will execute any of these AC related scenes from any of the Roomie Remote screens.
Title: Re: Plug-in for ecobee thermostats in development
Post by: slief on June 14, 2015, 01:20:32 am
Also for reference, here is a screen shot of my Comfort Settings Page. You can see I created 3 new Comfort Modes that set the cooling and Heating range as well as select the correct temp sensor for that zone. Ecobee uses smart1, smart2, smart3 for those 3 new Comfort modes. That is what needs to be entered as the Climate ref value instead of Home, Away or Night. If I added a 4th, it would be smart4.
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 14, 2015, 02:44:41 am
It did not work. At least not for the wakeup and sleep modes: When the ecobee switched to them, it failed to trigger the vera. I have not tested home and away but I have the reverse logic for these where I have the vera trigger a "resume" mode instead. Any other idea as to how I can get the ecobee to trigger when it changes mode to sleep?

I saw the triggers for changing currentClimateRef work on UI5 1.5.622 with the new S_Ecobee1.xml in place.  (To either home or sleep, the two climates I tested.) I will try it on my UI7 1.7.1181 (VeraEdge) and let you know what I see.

EDIT: I just saw the trigger work on my UI7 1.7.1811 VeraEdge with the v1.2 plugin + updated S_Ecobee.1xml file, as it does on UI5 1.5.622 Vera 3.  Vera sent me an email notification when I switched the device to "away" as expected.  Make sure you properly replaced the S_Ecobee1.xml file on your Vera and had it restart after upload.  Also review your automation to make sure it triggers off of this change.

Watou,

I just tested again and indeed, it does not work. The thermostat goes to sleep schedule and nothing happens on the vera side. No notification, no scene run. I am suspecting you tested the mode change by triggering a hold but a scheduled mode change does not trigger. Could you check? I am also able to trigger scene if I trigger a hold home or away but I am not able to trigger from a scheduled sleep.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 14, 2015, 02:53:11 am
I just tested again and indeed, it does not work. The thermostat goes to sleep schedule and nothing happens on the vera side. No notification, no scene run.

If you have plugin v1.2 installed, then the newer S_Ecobee1.xml installed (via Apps->Develop Apps->Luup files) (I've attached it again here), restarted Luup (for certain), set up a proper trigger when the device goes to sleep climate, and if you see "sleep" under the Climate: label when it had been a different value previously, it ought to work.  I saw it work here on 1.5.622 and 1.7.1181.  I don't know what else to suggest!

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 14, 2015, 02:59:03 am
I do not see sleep under the climate. Actually when the climate is a scheduled climate, it shows nothing. If the ecobee is on hold home or away then I see the status change.

I checked the CurrentClimateRef and currentEventType variable under the different conditions:
With a short lag when I trigger a hold on the ecobee I get:
currentEventType: Hold
currentClimateRef: Home or Away (correctly)

If I resume schedule on the ecobee I get:
currentEventType: Template
currentClimateRef: (Empty no matter what mode I am in)


Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 14, 2015, 03:51:23 am
I do not see sleep under the climate. Actually when the climate is a scheduled climate, it shows nothing. If the ecobee is on hold home or away then I see the status change.

I checked the CurrentClimateRef and currentEventType variable under the different conditions:
With a short lag when I trigger a hold on the ecobee I get:
currentEventType: Hold
currentClimateRef: Home or Away (correctly)

If I resume schedule on the ecobee I get:
currentEventType: Template
currentClimateRef: (Empty no matter what mode I am in)

OK, interesting.  I have not seen this with my Smart Si or ecobee3.  I'm guessing you have a different model thermostat?

EDIT: I see reference to a "template" event type in the API documentation here:

https://www.ecobee.com/home/developer/api/documentation/v1/objects/Event.shtml

But I've never seen that event active before, and the API docs say it is never active, but only used to hold vacation settings.  Is your thermostat currently on vacation? :)
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 14, 2015, 09:34:33 am
Hmm, this is strange. No my setting is not on vacation. It is following a schedule (home, away, night) and it is an ecobee 3...
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 14, 2015, 12:59:20 pm
Hmm, this is strange. No my setting is not on vacation. It is following a schedule (home, away, night) and it is an ecobee 3...

I would suggest touring through the web portal and physical thermostat, looking for and clearing any hold or non-default, unwanted settings, and if that doesn't clear the "template" hold, inquire with Ecobee's support about it.  It is indeed weird to me, too.
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on June 14, 2015, 11:58:24 pm
I sent them an enquiry. Now that I think about it, I think it has always shown "template" when following schedule even with 1.0 and under the previous 2 ecobee firmware.

Also another idea for 1.2: Could one of the virtual devices report the current functioning mode? (ie variable ModeState?). I found myself looking at the ecobee interface to see what it is doing while I was setting up some scenes. Would have been nice to be able to just look it up.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 15, 2015, 02:23:56 am
Also another idea for 1.2

Do you mean 1.3?

Could one of the virtual devices report the current functioning mode? (ie variable ModeState?). I found myself looking at the ecobee interface to see what it is doing while I was setting up some scenes. Would have been nice to be able to just look it up.

The ModeState variable (that shows if equipment is running, like Cooling, Heating, Idle, FanOnly, Off) looks great on UI5 (see the UI5 screenshots in the documentation).  You could watch the thermostat device on the dashboard and see this value change.  UI7 took this away, but it's still on the Control pane when you look at device details.  Since Vera took it away, you could ask them to put it back!

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on June 25, 2015, 02:42:20 pm
v1.2 of the plugin is currently in the approval queue at apps.mios.com.  The updated documentation is here:

http://watou.github.io/vera-ecobee/

Please let me know if it works with your RSM EB-RSM-01.  Thanks!

watou

watou,

I added RSM EB-RSM-01 board and it looks good!
All four configured board's temperature sensor appeared in Vera's interface as separate temperature devices (v.5).
Thank you!

PS I see you have multi-staging reporting in your roadmap.
Is there anyway to persuade you to move it up the list?

Thanks again for your work!

theal
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 25, 2015, 02:53:14 pm
I added RSM EB-RSM-01 board and it looks good!
All four configured board's temperature sensor appeared in Vera's interface as separate temperature devices (v.5).
Thank you!

That's really great news.  The Ecobee developer support and API people are to be commended for fitting the sensor board's information in the same way they expose ecobee3 sensors, and for answering your question on their forum.  I love it when a plan comes together.

PS I see you have multi-staging reporting in your roadmap.
Is there anyway to persuade you to move it up the list?

I lack a good sense of the requirements and how it would fit logically into Vera.  I want to avoid replicating any reporting that Ecobee already does in their web portal.  An OpenHAB user has already asked about extended reporting, but I need to understand the objectives better.

Thanks very much for reporting the good news.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Don Diego on June 26, 2015, 07:48:34 am
Also another idea for 1.2

Do you mean 1.3?

Could one of the virtual devices report the current functioning mode? (ie variable ModeState?). I found myself looking at the ecobee interface to see what it is doing while I was setting up some scenes. Would have been nice to be able to just look it up.

The ModeState variable (that shows if equipment is running, like Cooling, Heating, Idle, FanOnly, Off) looks great on UI5 (see the UI5 screenshots in the documentation).  You could watch the thermostat device on the dashboard and see this value change.  UI7 took this away, but it's still on the Control pane when you look at device details.  Since Vera took it away, you could ask them to put it back!

watou

watou--

   Does Version 1.2 of the plug-in run on UI5?

     Don
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 26, 2015, 08:16:12 am
   Does Version 1.2 of the plug-in run on UI5?

It should run on firmware 1.5.488 or later, so yes.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Don Diego on June 26, 2015, 05:08:12 pm
   Does Version 1.2 of the plug-in run on UI5?

It should run on firmware 1.5.488 or later, so yes.

Watou

  Great thanks

   
Title: Re: Plug-in for ecobee thermostats in development
Post by: xiper on July 02, 2015, 01:31:27 pm
Love your plugin and running version 1.2.  I'm wondering about Vera's ability to detect motion on the remote sensors.  Each sensor is properly detected by Vera as a Temperature and Motion sensor.  Temp works great.  But the motion sensors never trip (nor does motion on the thermostat) and under the advanced tab for the sensor, lasttrip is always zero.  Is motion detection not fully supported by the plugin at this time?
Title: Re: Plug-in for ecobee thermostats in development
Post by: JMack89427 on July 06, 2015, 08:42:02 am
I've been running into a weird issue since I upgraded to v1.2 of this app that I didn't see listed.  I used my ecobee3 to manage my schedule, rather than Vera, and have been seeing random holds of temperature ranges that match my schedule but then aren't cleared when the schedule is supposed to change.  This is most frustrating at night when I drop my temperatures for sleeping. 

I should add that I've just started using the HomeWave app around the same time and just this morning updated the xml file that was attached.

Has anyone else seen this?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 06, 2015, 08:55:25 am
Love your plugin and running version 1.2.  I'm wondering about Vera's ability to detect motion on the remote sensors.  Each sensor is properly detected by Vera as a Temperature and Motion sensor.  Temp works great.  But the motion sensors never trip (nor does motion on the thermostat) and under the advanced tab for the sensor, lasttrip is always zero.  Is motion detection not fully supported by the plugin at this time?

Sorry; just now saw your message.  I have the v1.2 plugin running on both UI5 (1.5.622 on a Vera 3) and UI7 (1.7.1248 on a VeraEdge) and I watch the occupancy sensors trip and clear properly on both Veras.  The LastTrip values are updated in both as expected.  This is against an ecobee3 running firmware 3.6.0.877.  Your ecobee3 has to have firmware 3.6 minimum for remote sensors to show up properly in the API.

Hopefully the issue is just a firmware upgrade not having been applied.  If your LuaUPnP.log has odd messages in it, I can take a look.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 06, 2015, 09:00:03 am
I've been running into a weird issue since I upgraded to v1.2 of this app that I didn't see listed.  I used my ecobee3 to manage my schedule, rather than Vera, and have been seeing random holds of temperature ranges that match my schedule but then aren't cleared when the schedule is supposed to change.  This is most frustrating at night when I drop my temperatures for sleeping. 

I should add that I've just started using the HomeWave app around the same time and just this morning updated the xml file that was attached.

Hi, I don't understand how you are using the ecobee3 to manage your schedule; perhaps if you describe that in great detail I can think of ways in which the plugin may have changed that affect it.  With the updated XML after v1.2, the built-in triggers for changing the standard climates (aka comfort settings) should trip.  I had an email notification hitting me 3/4 times a day as the currentClimateRef variable was changing value.  It's certainly possible that a mobile app has interacted in some way that affects the function, but I have no idea how that might be.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: JMack89427 on July 06, 2015, 12:27:12 pm
Basically, my comfort settings appear to be overridden by a specific temperature hold.  For example, my Sleep comfort setting is set for 9 pm and when I went to bed at 10:30, I noticed it was still pretty warm. I looked and my ecobee3 was showing a 67-72 degree hold. When I dismissed it, my normal sleep temperatures took over.  I haven't noticed this every time, but I don't remember ever seeing it in v1.1.

Let me know if you need more specific information.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 06, 2015, 01:21:41 pm
Basically, my comfort settings appear to be overridden by a specific temperature hold.  For example, my Sleep comfort setting is set for 9 pm and when I went to bed at 10:30, I noticed it was still pretty warm. I looked and my ecobee3 was showing a 67-72 degree hold. When I dismissed it, my normal sleep temperatures took over.  I haven't noticed this every time, but I don't remember ever seeing it in v1.1.

Let me know if you need more specific information.

It seems at least conceivable that HomeWave is setting a cool or heat setpoint, possibly accidentally, thereby setting an indefinite temperature hold.  The v1.2 plugin slightly changed the meaning of "currentClimateRef" to include when there is a hold based on a climate/comfort setting (holdClimateRef), but now exclude when a hold is set based on just changing the setpoints.  I found it important to do it that way, because there is a new UPnP action called SetClimateHold, that, after it's called from Luup code or in a scene, the plugin needs to report that the current climate is the one you just set it to.

So if using HomeWave is creating a hold event by setting heat or cool setpoints, even to the same values as those in the current comfort setting, it is still creating a simple setpoint hold, meaning that the current comfort settings are not actually in use.  Worse than that, it's an indefinite hold, meaning that your schedule won't run thereafter.

If that's the case, the ideal thing would be to ask the HomeWave author to not change the setpoints with explicit user interaction.  Then, the "currentClimateRef" would be accurate all the time.  That would be fixing a bug at its source (if that's what's happening).  Beyond that, if there is a better, more universally meaningful way to honestly and accurately report that a specific comfort setting is currently in effect, I'm open to adjusting it in a v1.3 of the plugin.

The current logic for determining the currentClimateRef value is here:

https://github.com/watou/vera-ecobee/blob/master/src/I_Ecobee1.xml#L195

I hope this makes sense!

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: JMack89427 on July 06, 2015, 09:56:09 pm
Thanks for the insight!  I tested it quickly and even switching the fan from auto to on from either the Vera web portal or Homewave sets the hold so I don't think it's Homewave.  Let me know if I can provide any data that may be helpful in diagnosing this. Thanks!
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 07, 2015, 12:17:39 am
I tested it quickly and even switching the fan from auto to on from either the Vera web portal or Homewave sets the hold so I don't think it's Homewave.
I'm sorry; I don't understand what your test is telling you about what I described above.
Title: Re: Plug-in for ecobee thermostats in development
Post by: JMack89427 on July 07, 2015, 08:09:22 am
I'm new to Vera and home automation in general so maybe I'm not understanding what it is your plugin is attempting to do and how it's intended to interact with the ecobee3 thermostat.  I have my thermostat programmed with Comfort Settings that suit my needs and really don't NEED Vera to control anything.  I have the thermostat added to Vera so that I can leverage the data and remote sensors for smart vents in the future and so that I can get the view I want using Homewave.  That being said, any change made to the thermostat, regardless of whether it's temperature setpoints, cooling mode, or fan mode, causes a temperature hold to be placed on the thermostat at whatever the current temperature setpoints are ... and maybe this is the intended behavior.  That would be fine if they cleared at the next scheduled Comfort Setting change but they don't. 

At the end of the day I want the thermostat to function on its own and only want the data to act upon so I guess my questions are:
1. Is this the intended behavior and if so, can it be disabled without losing access to the sensors?
2. If it can't be disabled, is it possible to create a scene that would clear this type of hold on a regular or scheduled basis?

I appreciate all of the work that you've put into making this work and hope that this is a little clearer.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 07, 2015, 08:25:40 am
I have my thermostat programmed with Comfort Settings that suit my needs and really don't NEED Vera to control anything.

That's probably the best way to look at the ecobee3 -- let it do its thing!

I have the thermostat added to Vera so that I can leverage the data and remote sensors for smart vents in the future and so that I can get the view I want using Homewave.  That being said, any change made to the thermostat, regardless of whether it's temperature setpoints, cooling mode, or fan mode, causes a temperature hold to be placed on the thermostat at whatever the current temperature setpoints are ... and maybe this is the intended behavior.  That would be fine if they cleared at the next scheduled Comfort Setting change but they don't. 

A user interaction of changing the mode (heat, cool, auto, off) should definitely not result in a hold event being created that overrides the current program.  I would call that a likely client bug of some kind.  Explicitly changing a setpoint with a slider or up/down arrows in the UI, however, should create a temperature hold.  Similarly, it would seem like a client bug for a temperature hold to be set for what the current setpoints currently are.  Vera's standard devices don't have the concepts that Ecobee does of hold durations like "indefinite", "nextTransition," etc.  so the plugin uses indefinite holds.

At the end of the day I want the thermostat to function on its own and only want the data to act upon so I guess my questions are:
1. Is this the intended behavior and if so, can it be disabled without losing access to the sensors?

It seems like something about your mobile client is creating a temperature hold when you didn't ask it to.  Only using the native Vera web UI, I've never seen a temperature hold appear without explicitly setting it with up/down arrows or the setpoint slider.

2. If it can't be disabled, is it possible to create a scene that would clear this type of hold on a regular or scheduled basis?

Absolutely.  You would call the ResumeProgram UPnP action against the thermostat device, in order to clear all hold, returning you to the program.  This might be a workaround for the cases where a current client bug is unintentionally creating a temperature hold.  For example:

Code: [Select]
local service_id = "urn:ecobee-com:serviceId:Ecobee1"
local action = "ResumeProgram"
local args = { }
local dev_num = 237
luup.call_action(service_id, action, args, dev_num)

I appreciate all of the work that you've put into making this work and hope that this is a little clearer.

No worries; hopefully the above is helpful.

Regards,
watou

...adding, if you can ssh into your Vera and "tail -f /var/log/cmh/LuaUPnP.log", then open HomeWave and see if setpoints are being set without you explicitly changing sliders or clicking up/down arrows, that would probably be useful info for the HomeWave author.  Or instead of watching the log, watch the native Vera web UI and see if these holds appear around the time you are using the HomeWave app.
Title: Re: Plug-in for ecobee thermostats in development
Post by: JMack89427 on July 07, 2015, 09:48:15 am
Following up on this, I did some additional tests and here's what I'm seeing:

From the Vera Web Portal:
1. Changes to temperature set points do nothing.  No holds set and no changes visible on the thermostat.
2. Changes to Heating/Cooling mode act normally and no holds are set.
3. Changes to fan mode act normally and a hold is set.

I think the second to last line might be the culprit although I admit I'm not sure what 99.9% of this is doing :)
Code: [Select]
07/07/15 8:18:56.652    mg_callback from IP:127.0.0.1:46168 /port_3480/data_request id=lu_action&output_format=json&DeviceNum=4&serviceId=urn:upnp-org:serviceId:HVAC_FanOperatingMode1&action=SetMode&NewMode=Auto&rand=0.41747144516557455 start id: 1749 <0x74a64520>
12      07/07/15 8:18:56.652    luvd_get_info_data_request starting /data_request?id=lu_action&output_format=json&DeviceNum=4&serviceId=urn:upnp-org:serviceId:HVAC_FanOperatingMode1&action=SetMode&NewMode=Auto&rand=0.41747144516557455 pMem 0x1358000/20283392 diff: 6434816 <0x74a64520>
10      07/07/15 8:18:56.653    JobHandler_LuaUPnP::HandleRequest id lu_action request pMem 0x1358000/20283392 diff: 6434816 <0x74a64520>
10      07/07/15 8:18:56.654    sbrk JobHandler_LuaUPnP::HandleActionRequest from IP:228.105.85.119 pMem 0x1358000/20283392 diff: 6434816 <0x74a64520>
08      07/07/15 8:18:56.654    JobHandler_LuaUPnP::HandleActionRequest device: 4 service: urn:upnp-org:serviceId:HVAC_FanOperatingMode1 action: SetMode <0x74a64520>
08      07/07/15 8:18:56.655    JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=4 <0x74a64520>
08      07/07/15 8:18:56.656    JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:HVAC_FanOperatingMode1 <0x74a64520>
08      07/07/15 8:18:56.656    JobHandler_LuaUPnP::HandleActionRequest argument action=SetMode <0x74a64520>
08      07/07/15 8:18:56.656    JobHandler_LuaUPnP::HandleActionRequest argument NewMode=Auto <0x74a64520>
08      07/07/15 8:18:56.657    JobHandler_LuaUPnP::HandleActionRequest argument rand=0.41747144516557455 <0x74a64520>
35      07/07/15 8:18:56.658    luup_log:3: ecobee: debug: in setHold() <0x74a64520>
35      07/07/15 8:18:57.135    luup_log:3: ecobee: debug: Scheduling status poll in 5 seconds. <0x74a64520>

From Homewave App:
1. Changes to temperature set points act normally.  Holds are set and changes visible on the thermostat.
2. Changes to Heating/Cooling mode act normally and no holds are set.
3. Changes to fan mode act normally and a hold is set.

Same bit of the log from Homewave change
Code: [Select]
10      07/07/15 8:16:13.321    mg_callback from IP:192.168.1.166:49489 /data_request output_format=json&id=lu_action&DeviceNum=4&serviceId=urn:upnp-org:serviceId:HVAC_FanOperatingMode1&action=SetMode&NewMode=ContinuousOn start id: 1721 <0x74a64520>
12      07/07/15 8:16:13.321    luvd_get_info_data_request starting /data_request?output_format=json&id=lu_action&DeviceNum=4&serviceId=urn:upnp-org:serviceId:HVAC_FanOperatingMode1&action=SetMode&NewMode=ContinuousOn pMem 0x1358000/20283392 diff: 6434816 <0x74a64520>
10      07/07/15 8:16:13.322    JobHandler_LuaUPnP::HandleRequest id lu_action request pMem 0x1358000/20283392 diff: 6434816 <0x74a64520>
10      07/07/15 8:16:13.323    sbrk JobHandler_LuaUPnP::HandleActionRequest from IP:228.105.85.119 pMem 0x1358000/20283392 diff: 6434816 <0x74a64520>
08      07/07/15 8:16:13.323    JobHandler_LuaUPnP::HandleActionRequest device: 4 service: urn:upnp-org:serviceId:HVAC_FanOperatingMode1 action: SetMode <0x74a64520>
08      07/07/15 8:16:13.324    JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=4 <0x74a64520>
08      07/07/15 8:16:13.324    JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:HVAC_FanOperatingMode1 <0x74a64520>
08      07/07/15 8:16:13.325    JobHandler_LuaUPnP::HandleActionRequest argument action=SetMode <0x74a64520>
08      07/07/15 8:16:13.325    JobHandler_LuaUPnP::HandleActionRequest argument NewMode=ContinuousOn <0x74a64520>
35      07/07/15 8:16:13.326    luup_log:3: ecobee: debug: in setHold() <0x74a64520>
35      07/07/15 8:16:14.190    luup_log:3: ecobee: debug: Scheduling status poll in 5 seconds. <0x74a64520>
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 07, 2015, 09:57:52 am
From the Vera Web Portal:
1. Changes to temperature set points do nothing.  No holds set and no changes visible on the thermostat.
2. Changes to Heating/Cooling mode act normally and no holds are set.
3. Changes to fan mode act normally and a hold is set.

1. This might be a UI7 bug.  I've repeatedly asked for information on how thermostat plugins that work perfectly in UI5 should be altered so their setpoints also work correctly in UI7, but I've gotten no answers.
2. This is correct.
3. The only way to only change the fan mode is to set a hold event, so this is also correct.

From Homewave App:
1. Changes to temperature set points act normally.  Holds are set and changes visible on the thermostat.
2. Changes to Heating/Cooling mode act normally and no holds are set.
3. Changes to fan mode act normally and a hold is set.

This looks good then.  But the question remains, what is sending indefinite holds to your thermostat?  In the case of simply browsing around your clients, have you determined that no press, swipe, reload, close, reopen, etc., do not accidentally send a setpoint or fan mode change?  I am asking the right question here?

Title: Re: Plug-in for ecobee thermostats in development
Post by: JMack89427 on July 07, 2015, 10:24:55 am
3. The only way to only change the fan mode is to set a hold event, so this is also correct.

So changing the fan mode is intended to set an indefinite hold for the current temperature set points?  If that's the case, it shouldn't be a real issue as I don't really intend to leverage that functionality.

It's distinctly possible that the erroneous holds were from accidentally tapping something while configuring Homewave.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 07, 2015, 10:30:58 am
3. The only way to only change the fan mode is to set a hold event, so this is also correct.

So changing the fan mode is intended to set an indefinite hold for the current temperature set points?

Correct -- this is the only way to only change the current fan mode in the Ecobee API.

It's distinctly possible that the erroneous holds were from accidentally tapping something while configuring Homewave.

That would be a relief, instead of having some unknown gremlin setting holds.
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on July 07, 2015, 04:59:43 pm
Is there a way to read/set/remove 'quickSave" event?
I would like to auto-control quickSave based on occupancy and doors/windows sensors.

Also, are 'urn:upnp-org:serviceId:TemperatureSetpoint1_Heat/Cool' fields read-only or programmable?

Thanks
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 07, 2015, 06:00:42 pm
Is there a way to read/set/remove 'quickSave" event?
I would like to auto-control quickSave based on occupancy and doors/windows sensors.

I begged Ecobee for the ability in the API to set a quickSave event when it was in beta, but they eventually said that was not going to be available.  But if you set a quickSave event through the thermostat or portal, you can see it in the currentEventType device variable as "quickSave" on the "home/away" device.  (See "type" under Properties on this page: https://www.ecobee.com/home/developer/api/documentation/v1/objects/Event.shtml (https://www.ecobee.com/home/developer/api/documentation/v1/objects/Event.shtml).)

The plugin used to simulate a quickSave event when the home/away switch was turned off, by creating a normal temperature hold, but by negatively offsetting the current heat setpoint by the quickSaveSetBack variable's value (which is Fahrenheit times 10), and by positively offsetting the current cool setpoint by the quickSaveSetForward variable's value (also F*10).  You could do something similar in Luup.  Or better...

Could you instead create a/use an existing "climate" (more recently being called a comfort setting), and use the new SetClimateHold UPnP action in your scenes?  If there's no occupancy or doors/windows are open (as an example), you could call SetClimateHold with "away" or the climate ref to your custom climate, and the thermostat would switch to the heat and cool setpoints defined in that climate.  When you want to reverse the action, call the ResumeProgram UPnP action to return to whatever the thermostat should be doing on that day/time.

Also, are 'urn:upnp-org:serviceId:TemperatureSetpoint1_Heat/Cool' fields read-only or programmable?

To change a setpoint you would call SetCurrentSetpoint action like this:

Code: [Select]
local service_id = "urn:upnp-org:serviceId:TemperatureSetpoint1_Cool"
local action = "SetCurrentSetpoint"
local coolSetpoint = "78"  -- your desired temperature in Vera's current temperature scale
local args = { NewCurrentSetpoint = coolSetpoint }
local dev_num = 237 -- thermostat device ID
luup.call_action(service_id, action, args, dev_num)

After the call is performed and after the poll about 5-6 seconds later, the device variable CurrentSetpoint under the service ID should contain the new value.

Code: [Select]
luup.variable_get("urn:upnp-org:serviceId:TemperatureSetpoint1_Cool", "CurrentSetpoint", 237)
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on July 08, 2015, 11:10:58 am
...
If there's no occupancy or doors/windows are open (as an example), you could call SetClimateHold with "away" or the climate ref to your custom climate, and the thermostat would switch to the heat and cool setpoints defined in that climate.  When you want to reverse the action, call the ResumeProgram UPnP action to return to whatever the thermostat should be doing on that day/time.

To change a setpoint you would call SetCurrentSetpoint action like this:
...

Thank you watou, this is a good workaround and code example.
It should work well.
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on July 08, 2015, 11:35:30 am
I added RSM EB-RSM-01 board and it looks good!
All four configured board's temperature sensor appeared in Vera's interface as separate temperature devices (v.5).
Thank you!

That's really great news.  The Ecobee developer support and API people are to be commended for fitting the sensor board's information in the same way they expose ecobee3 sensors, and for answering your question on their forum.  I love it when a plan comes together.

Thanks very much for reporting the good news.

Attached are snapshots of my SMART/RSM EB-RSM-01 four temperature sensors (listed on the bottom of the graph).
I placed one temperature sensor in AC evaporator coil and another in return duct before a fan so I can monitor delta-T of my HVAC.
Other two are placed in the basement and outside. (You can see that my outside temperature differentiate significantly from Ecobee's reported NOAA weather station 20 miles away).
RSM sensors data is also included in CSV download file.
I plan to add an outside humidity sensor, especially that Ecobee's outside humidity data is not included in CSV download, despite my numerous requests.
CO2 sensor is not officially supported by SMART/RSM but it has the same spec as Humidity sensor, so it may work with a conversion formula.

Watou, thanks again for your implementation!
theal
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 08, 2015, 11:55:50 am
Attached are snapshots of my SMART/RSM EB-RSM-01 four temperature sensors (listed on the bottom of the graph).
I placed one temperature sensor in AC evaporator coil and another in return duct before a fan so I can monitor delta-T of my HVAC.
Other two are placed in the basement and outside. (You can see that my outside temperature differentiate significantly from Ecobee's reported NOAA weather station 20 miles away).
RSM sensors data is also included in CSV download file.
I plan to add an outside humidity sensor, especially that Ecobee's outside humidity data is not included in CSV download, despite my numerous requests.
CO2 sensor is not officially supported by SMART/RSM but it has the same spec as Humidity sensor, so it may work with a conversion formula.
Watou, thanks again for your implementation!

Cool! You're very welcome.  Please report if you get the CO2 sensor connected and what it reports.  I too have been confused by the weather reports coming from Ecobee, but I've not looked into why it seems to differ so much from other reports.

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on July 08, 2015, 01:07:23 pm

Please report if you get the CO2 sensor connected and what it reports. 

I'm looking for an inexpensive CO2 sensor with a display that matches RSM spec of 0-10 or 0-5 Vdc.
If anyone sees one, please let me know.


I too have been confused by the weather reports coming from Ecobee, but I've not looked into why it seems to differ so much from other reports.

It is my understanding that Ecobee uses NOAA services and auto-selects nearest reporting station, but you can request to change to another station through support.
http://www.weather.gov/
Here in Long Island NY 20 miles makes a huge difference in weather and at times I see a difference up to 10F.
I found a closer proximity Weather Underground stations are a better match, although some are less reliable.
In my case, I can't rely on NOAA reporting for precise control, like freeze protection, so I need to use my own sensors.
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on July 08, 2015, 02:29:03 pm
PS I see you have multi-staging reporting in your roadmap.
Is there anyway to persuade you to move it up the list?

I lack a good sense of the requirements and how it would fit logically into Vera.  I want to avoid replicating any reporting that Ecobee already does in their web portal.  An OpenHAB user has already asked about extended reporting, but I need to understand the objectives better.

After using 2-stage AC for a couple weeks, I can see a big benefit to have all HVAC info including staging on one custom Vara-control page, especially on a mobile device, without going into Ecobee site/app, especially that Ecobee mobile app is not ergonomic in providing all info on one page.

Also, it would be great to access a stage status programmatically.  For example, I have a split two zone system and my AC 2nd stage/fan speed sized for the whole house.  I would like to have a logic that if one of the zone tstat activates 2nd stage, it would open a second zone as well.

I hope this helps.
theal
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 08, 2015, 05:18:26 pm
After using 2-stage AC for a couple weeks, I can see a big benefit to have all HVAC info including staging on one custom Vara-control page, especially on a mobile device, without going into Ecobee site/app, especially that Ecobee mobile app is not ergonomic in providing all info on one page.

Also, it would be great to access a stage status programmatically.  For example, I have a split two zone system and my AC 2nd stage/fan speed sized for the whole house.  I would like to have a logic that if one of the zone tstat activates 2nd stage, it would open a second zone as well.

It's going to be tough to accommodate those requirements on Vera, because plugins have poor control over what is shown in the UI, and almost no control of UI when it comes to mobile clients.   You may have extra tools that overcome this, but plugins are focused on device and service types, where the developer has already imagined what information you want, and fits it into a standard-ish model.

If you were an OpenHAB user, however, the tools already exist to put whatever numbers, text, buttons, sliders, etc., containing whatever data from Ecobee (and Z-Wave, Insteon and well over 100 other systems) in either the classic web or mobile clients.  Take a look at the (subset) of information my OpenHAB binding (like a plugin) for Ecobee already provides here: https://github.com/openhab/openhab/wiki/Ecobee-Binding#examples (https://github.com/openhab/openhab/wiki/Ecobee-Binding#examples).  You can specify what is shown and how it is shown, and have buttons, sliders, etc., that let you control it all.  And if you add in rules, you can automate just about anything.

I'm not saying Vera *can't* do your custom UI, but it's a longer, tougher path to get there (and plus I can't engage in any platform flame wars, for anyone who might want to go there!).
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on July 09, 2015, 04:18:07 pm

It's going to be tough to accommodate those requirements on Vera, because plugins have poor control over what is shown in the UI, and almost no control of UI when it comes to mobile clients.   You may have extra tools that overcome this, but plugins are focused on device and service types, where the developer has already imagined what information you want, and fits it into a standard-ish model.

If you were an OpenHAB user, however, the tools already exist to put whatever numbers, text, buttons, sliders, etc...

I fully concur on Vera's UI limitation and it is my understanding v.7 UI is not much of an improvement.
Perhaps at some point you would consider to expose relays status via tstat custom variables (type/activeClosed https://www.ecobee.com/home/developer/api/documentation/v1/objects/Output.shtml) so one can use it programmatically or to create a custom UI.
Alternatively, would it be possible to make direct Ecobee API calls through LUUP/plugin?

OpenHAB looks very interesting and deserves a closer look.

Thank you
theal
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 10, 2015, 02:23:43 am

It's going to be tough to accommodate those requirements on Vera, because plugins have poor control over what is shown in the UI, and almost no control of UI when it comes to mobile clients.   You may have extra tools that overcome this, but plugins are focused on device and service types, where the developer has already imagined what information you want, and fits it into a standard-ish model.

If you were an OpenHAB user, however, the tools already exist to put whatever numbers, text, buttons, sliders, etc...

I fully concur on Vera's UI limitation and it is my understanding v.7 UI is not much of an improvement.
Perhaps at some point you would consider to expose relays status via tstat custom variables (type/activeClosed https://www.ecobee.com/home/developer/api/documentation/v1/objects/Output.shtml) so one can use it programmatically or to create a custom UI.
Alternatively, would it be possible to make direct Ecobee API calls through LUUP/plugin?

OpenHAB looks very interesting and deserves a closer look.

Thank you
theal

I would be very happy if users would fork a copy of the public source code at https://github.com/watou/vera-ecobee (https://github.com/watou/vera-ecobee), make compatible and tested enhancements (or bug fixes) and submit pull requests for those changes that other users are very likely to want (without breaking anything, of course :) ). I would review the pull requests and fold the non-breaking ones into the official, installable plugin.  I no longer rely on the plugin myself, even though I currently have a UI5 and a UI7 Vera each running a copy against two different thermostats.  I don't want to leave users stranded, but I am doubtful that I can dedicate very much time and attention going forward.  Lua is a great programming language and there is a lot of learning by example in the existing plugin source code and elsewhere.  I'm not saying the Ecobee plugin has reached end of life, but I can't commit to major additions to it right now.

Or, if you look further into OpenHAB, all of the API objects are available in the OpenHAB binding to be bound to items, so this could be done on OpenHAB already (including the Device, Sensor, Output objects, everything).  If you had OpenHAB on a tiny computer like a Raspberry Pi 2 and the Ecobee binding, you could add Mark Clark's MiOS binding to expose the rest of your Vera devices and scenes into OpenHAB. The OpenHAB project just added free integration with IFTTT, which opens up a lot of possibilities for wider integration outside the local ecosystem.  Just some thoughts...

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on July 14, 2015, 07:39:50 pm
Watou,

Is there anyway to make the plugin maintain the ecobee access through a backup restore?
Every time I run a restore I am having to get a new pin and re-register...
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 14, 2015, 08:26:49 pm
Is there anyway to make the plugin maintain the ecobee access through a backup restore?
Every time I run a restore I am having to get a new pin and re-register...

I haven't tried the following, but it ought to work.  You will have to perform the following 3 steps, either by hand (after a browser refresh to make sure the UI isn't showing stale values) or with some Lua code.

1. Before you restore; copy these device variable values from the ecobee (bee logo) device:
2. Perform the restore.
3. Copy those saved variables back into the device. 

The auth_token is created after the PIN is entered and is valid for a year, so it ought to be the same.  If it's not, then there will be no point copying the other two tokens, since the older auth_token won't be valid and neither will the access or refresh tokens. 

The refresh_token is also good for a year, but only if it hasn't been replaced, which happens every hour while the plugin is running.

The access_token is only valid for an hour, but if it has expired, the plugin will fetch a new, valid one if the auth and refresh tokens are still valid.

OAuth relies on expiring tokens after some period of time and there is no way around it, by design.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on July 15, 2015, 10:11:33 am
Thanks! Will test it next time I need to do a restore from backup.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Wekurtz74 on July 18, 2015, 10:44:02 am
Xiper,  did you resolve you issues concerning this?  I have seen mine tripping and untripping, but it is not consistent.

Of note, i have seen my ecobee reporting a room as occupied,  but vera not recognizing the sensor as being tripped.  Then substantially later, vera reports it as tripped.  I have also seen trouble in simply tripping the occupancy sensor for purposes of ecobee 3 recognizing a room as occupied.

My ecobee firmware is the 3.6.1.xxxx, running veralite UI5.   

I am trying to determine if these sensors are suitable for use in turning on lights.  So far my conclusion is they are not.   I read on another thread that the reset time is 30 minutes and tripping can take up to 3 minutes,  but am unclear if we can change that.

Love your plugin and running version 1.2.  I'm wondering about Vera's ability to detect motion on the remote sensors.  Each sensor is properly detected by Vera as a Temperature and Motion sensor.  Temp works great.  But the motion sensors never trip (nor does motion on the thermostat) and under the advanced tab for the sensor, lasttrip is always zero.  Is motion detection not fully supported by the plugin at this time?

Sent from my GT-N5110 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 18, 2015, 11:18:04 am
Xiper,  did you resolve you issues concerning this?  I have seen mine tripping and untripping, but it is not consistent.

Of note, i have seen my ecobee reporting a room as occupied,  but vera not recognizing the sensor as being tripped.  Then substantially later, vera reports it as tripped.  I have also seen trouble in simply tripping the occupancy sensor for purposes of ecobee 3 recognizing a room as occupied.

My ecobee firmware is the 3.6.1.xxxx, running veralite UI5.   

I am trying to determine if these sensors are suitable for use in turning on lights.  So far my conclusion is they are not.   I read on another thread that the reset time is 30 minutes and tripping can take up to 3 minutes,  but am unclear if we can change that.

Love your plugin and running version 1.2.  I'm wondering about Vera's ability to detect motion on the remote sensors.  Each sensor is properly detected by Vera as a Temperature and Motion sensor.  Temp works great.  But the motion sensors never trip (nor does motion on the thermostat) and under the advanced tab for the sensor, lasttrip is always zero.  Is motion detection not fully supported by the plugin at this time?

Sent from my GT-N5110 using Tapatalk
A Z-Wave motion sensor would be much more responsive to trigger lights on. The Ecobee API can take up to 3 minutes (or so) to report occupancy, and should stay tripped until about 30 minutes after the last detected motion.  I'm not aware of how that can be changed.  The ecobee3 sensor could suit HVAC purposes better than an immediate need for light, for example.


watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: Wekurtz74 on July 18, 2015, 12:00:25 pm
Xiper,  did you resolve you issues concerning this?  I have seen mine tripping and untripping, but it is not consistent.

Of note, i have seen my ecobee reporting a room as occupied,  but vera not recognizing the sensor as being tripped.  Then substantially later, vera reports it as tripped.  I have also seen trouble in simply tripping the occupancy sensor for purposes of ecobee 3 recognizing a room as occupied.

My ecobee firmware is the 3.6.1.xxxx, running veralite UI5.   

I am trying to determine if these sensors are suitable for use in turning on lights.  So far my conclusion is they are not.   I read on another thread that the reset time is 30 minutes and tripping can take up to 3 minutes,  but am unclear if we can change that.

Love your plugin and running version 1.2.  I'm wondering about Vera's ability to detect motion on the remote sensors.  Each sensor is properly detected by Vera as a Temperature and Motion sensor.  Temp works great.  But the motion sensors never trip (nor does motion on the thermostat) and under the advanced tab for the sensor, lasttrip is always zero.  Is motion detection not fully supported by the plugin at this time?

Sent from my GT-N5110 using Tapatalk
A Z-Wave motion sensor would be much more responsive to trigger lights on. The Ecobee API can take up to 3 minutes (or so) to report occupancy, and should stay tripped until about 30 minutes after the last detected motion.  I'm not aware of how that can be changed.  The ecobee3 sensor could suit HVAC purposes better than an immediate need for light, for example.


watou
Watou,

Thanks for confirming what I believed.   That is unfortunate, but not really unexpected.  In practice, it often takes longer  than 3 minutes to trigger motion/occupancy in my house, although sometimes it is very fast.  Given this fact, I am attempting to find a good use for these sensors that are now populated in Vera.  I will probably use PLEG and the temperature aspect of these sensors to trigger activation of ceiling fans. Beyond that, vent control(which I do not plan on implementing), and general monitoring, I am not sure what else to do with them, although I am not particularly creative. 

In any event, thank you for your tremendous efforts in making this fantastic integration into Vera.

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 18, 2015, 01:39:34 pm
Xiper,  did you resolve you issues concerning this?  I have seen mine tripping and untripping, but it is not consistent.

Of note, i have seen my ecobee reporting a room as occupied,  but vera not recognizing the sensor as being tripped.  Then substantially later, vera reports it as tripped.  I have also seen trouble in simply tripping the occupancy sensor for purposes of ecobee 3 recognizing a room as occupied.

My ecobee firmware is the 3.6.1.xxxx, running veralite UI5.   

I am trying to determine if these sensors are suitable for use in turning on lights.  So far my conclusion is they are not.   I read on another thread that the reset time is 30 minutes and tripping can take up to 3 minutes,  but am unclear if we can change that.

Love your plugin and running version 1.2.  I'm wondering about Vera's ability to detect motion on the remote sensors.  Each sensor is properly detected by Vera as a Temperature and Motion sensor.  Temp works great.  But the motion sensors never trip (nor does motion on the thermostat) and under the advanced tab for the sensor, lasttrip is always zero.  Is motion detection not fully supported by the plugin at this time?

Sent from my GT-N5110 using Tapatalk
A Z-Wave motion sensor would be much more responsive to trigger lights on. The Ecobee API can take up to 3 minutes (or so) to report occupancy, and should stay tripped until about 30 minutes after the last detected motion.  I'm not aware of how that can be changed.  The ecobee3 sensor could suit HVAC purposes better than an immediate need for light, for example.


watou
Watou,

Thanks for confirming what I believed.   That is unfortunate, but not really unexpected.  In practice, it often takes longer  than 3 minutes to trigger motion/occupancy in my house, although sometimes it is very fast.  Given this fact, I am attempting to find a good use for these sensors that are now populated in Vera.  I will probably use PLEG and the temperature aspect of these sensors to trigger activation of ceiling fans. Beyond that, vent control(which I do not plan on implementing), and general monitoring, I am not sure what else to do with them, although I am not particularly creative. 

In any event, thank you for your tremendous efforts in making this fantastic integration into Vera.

You're welcome!  And hopefully the sensors are at least giving you the follow-me comfort function that's native to the ecobee3, which for a lot of people can really make a difference to give the most comfort for the least energy consumed.

All the best,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: Wekurtz74 on July 18, 2015, 02:00:23 pm
Oh absolutely!  The native function is fantastic and I am a huge advocate of the product, in large part because of remote sensors.    Please don't misunderstand my comments as being negative.  In fact, part of my interest in trying to get the most extra uses out of the remote sensors is to try to be able to explain to others the benefits of this system over others.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 18, 2015, 02:09:11 pm
Oh absolutely!  The native function is fantastic and I am a huge advocate of the product, in large part because of remote sensors.    Please don't misunderstand my comments as being negative.  In fact, part of my interest in trying to get the most extra uses out of the remote sensors is to try to be able to explain to others the benefits of this system over others.

Not taken negatively at all -- it's best to take these gadgets for what they are.  Z-Wave motion sensors are simply better for near-instance response.  The thermostat itself is excellent, and hopefully you find good, additional uses for the remote sensors.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Wekurtz74 on July 18, 2015, 03:46:20 pm
Oh absolutely!  The native function is fantastic and I am a huge advocate of the product, in large part because of remote sensors.    Please don't misunderstand my comments as being negative.  In fact, part of my interest in trying to get the most extra uses out of the remote sensors is to try to be able to explain to others the benefits of this system over others.

Not taken negatively at all -- it's best to take these gadgets for what they are.  Z-Wave motion sensors are simply better for near-instance response.  The thermostat itself is excellent, and hopefully you find good, additional uses for the remote sensors.

I think I am going to start a separate discussion thread for this topic.  I have been going back and forth on whether to do it here or on the ecobee boards, or both.  After thinking about it a bit today, I am sure there are some creative ideas out there that will save people money who dont need a high level rapid response from their occupancy or temperature sensors forwhich the ecobee sensor can provide value at no additional cost.  An idea that occurred to me just a short time ago is doing the opposite of I was thinking about in my first post earlier today:  instead of turning the light on upon entry, turn them off after leaving the room unoccupied for a while.  this would be great as children tend to leave rooms without shutting lights, and a rapid response time is not needed.

Sent from my GT-N5110 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 18, 2015, 03:52:39 pm
Oh absolutely!  The native function is fantastic and I am a huge advocate of the product, in large part because of remote sensors.    Please don't misunderstand my comments as being negative.  In fact, part of my interest in trying to get the most extra uses out of the remote sensors is to try to be able to explain to others the benefits of this system over others.

Not taken negatively at all -- it's best to take these gadgets for what they are.  Z-Wave motion sensors are simply better for near-instance response.  The thermostat itself is excellent, and hopefully you find good, additional uses for the remote sensors.

I think I am going to start a separate discussion thread for this topic.  I have been going back and forth on whether to do it here or on the ecobee boards, or both.  After thinking about it a bit today, I am sure there are some creative ideas out there that will save people money who dont need a high level rapid response from their occupancy or temperature sensors forwhich the ecobee sensor can provide value at no additional cost.  An idea that occurred to me just a short time ago is doing the opposite of I was thinking about in my first post earlier today:  instead of turning the light on upon entry, turn them off after leaving the room unoccupied for a while.  this would be great as children tend to leave rooms without shutting lights, and a rapid response time is not needed.

Sent from my GT-N5110 using Tapatalk
Great idea. Another way Ecobee can save you some energy costs.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on July 26, 2015, 01:44:04 am
Is there anyway to make the plugin maintain the ecobee access through a backup restore?
Every time I run a restore I am having to get a new pin and re-register...

I haven't tried the following, but it ought to work.  You will have to perform the following 3 steps, either by hand (after a browser refresh to make sure the UI isn't showing stale values) or with some Lua code.

1. Before you restore; copy these device variable values from the ecobee (bee logo) device:
  • auth_token
  • access_token
  • refresh_token
2. Perform the restore.
3. Copy those saved variables back into the device. 

The auth_token is created after the PIN is entered and is valid for a year, so it ought to be the same.  If it's not, then there will be no point copying the other two tokens, since the older auth_token won't be valid and neither will the access or refresh tokens. 

The refresh_token is also good for a year, but only if it hasn't been replaced, which happens every hour while the plugin is running.

The access_token is only valid for an hour, but if it has expired, the plugin will fetch a new, valid one if the auth and refresh tokens are still valid.

OAuth relies on expiring tokens after some period of time and there is no way around it, by design.

watou

I tried this but it did not work.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 26, 2015, 02:32:37 am
The only reason I can think it wouldn't work is if the plugin was running after restore and was working against your replacing its tokens.  As long as you could do the steps without being worked against, it ought to have worked.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on August 01, 2015, 01:56:32 am
Yup, tried it again and it worked. Somehow I think the font matters. Need to paste without any font change. I pasted them into a word file which messed it up the first time.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 01, 2015, 03:08:58 am
Ah yes, pasting into Word could result in possible "smart" changes to what you pasted, turning the tokens into garbage.  It's better to use a simple plain text-only editor as a holding point for the tokens.  Glad it worked on another try!
Title: Re: Plug-in for ecobee thermostats in development
Post by: Wekurtz74 on August 09, 2015, 11:27:44 am
I have been experiencing an issue for at least the last couple of days (maybe more) when every day I log into Vera I am getting a msg to request a new pin, which I must then go and enter at ecobee.com in order to go from "grey" back to "green" on the Vera UI5.  I tried uninstalling and reinstalling the ecobee.com app, but that didnt seem to have effect.

For reference,  have two ecobee3, one is the original type, and the other is the new homekit enabled one.   Plugin ver is 1.2.  Ecobee firmware is the 3.6XXXXX.  Anyone have similar experience or ideas for resolution?  Thanks in advance. 
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 09, 2015, 11:34:08 am
I think there is an issue with the API where it will rarely report "authorization_error" mistakenly, so the plugin discards the tokens. I will make a change where the plugin will give the API three times to report this before discarding the auth token, which will then precipitate the need for a new PIN.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 10, 2015, 07:44:50 am
I've made a change to the Ecobee plugin, which if my testing works out (over the next couple of days), will be v1.3 of the plugin.  The changes from v1.2 are:
Please let me know if you see any issues with this approach before I submit the update to apps.mios.com.

Thanks,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 12, 2015, 06:07:54 am
v1.3 of the Ecobee plugin is now available at apps.mios.com.  It differs from v1.2 in these two ways:
Please report here or at github if the "less eager" discarding of the auth token is not sufficiently improving the case where you are being asked for a new PIN.  The logic in v1.3 now tries five times to refresh the tokens, spanning over at least 15 minutes, before finally giving up and requiring a new PIN.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: scotstern on August 16, 2015, 05:48:58 pm
This app simply does not work and it will hang up your system with a LUUP loading error.  Stay away until it gets repaired.  I was using it with 1248 and it was not reliable and actually did nothing and I tried to upgrade it to version 1.3.  DO NOT DO THIS as it simply does not work!
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 16, 2015, 07:53:12 pm
Thanks for spreading the word that there is a problem with v1.3.  I tried installing it again on 1.5.622 and it was a disaster.  I do not know what the problem is -- my steps to publish were no different from every version previous to it.

I have requested to Vera that v1.3 is unpublished in the meantime, and I will see if anything about this issue is under my control (I'm doubtful).

Unless there is a major improvement in plugin development and deployment features for Vera, I suspect that v1.3 is, if even possible, the last version I will be able to publish.

Title: Re: Plug-in for ecobee thermostats in development
Post by: Wekurtz74 on August 18, 2015, 06:05:16 pm
I am sure exactly what is going on, but I want to thank you for your hard work on getting this working.  An Ecobee3 limited to itself or just Apple homekit is still a great device, but not ideal if it doesn't work with a more advance system.  If Vera doesn't support you, I hope at least Ecobee provides you will support and assistance
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 18, 2015, 06:14:30 pm
I am sure exactly what is going on, but I want to thank you for your hard work on getting this working.  An Ecobee3 limited to itself or just Apple homekit is still a great device, but not ideal if it doesn't work with a more advance system.  If Vera doesn't support you, I hope at least Ecobee provides you will support and assistance
Thanks very much. I tried another v1.3 release today, bit it too won't install correctly so I pulled it as well.  Reverting to v1.2 seems to work on both 1.5.622 (Vera3) and 1.7.1320 (VeraEdge).  I have another message in to @mcvflorin who seems to be responsible for plugin delivery. He's been responsive so far, so I hope this gets figured out soon.

Thanks for the kind words and patience.

BTW, Ecobee has been having trouble delivering sensor occupancy and equipment status since last week (I suspect a key person is hiking in Tibet or something).

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on August 18, 2015, 07:41:25 pm
total FYI... and not even sure where to post this... but think it's interesting.

Logitech Remotes now support Ecobee. 
http://blog.logitech.com/2015/08/13/harmony-announces-4-new-smart-home-integrations/?utm_source=cta

Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on August 19, 2015, 08:06:27 pm
@watou.....

i'm still on 1.2, and seeing and odd problem.  I'm using PLEG to turn on a vent fan in my master bedroom when the AC comes on, with the input being:

Thermostat device state change
Device is cooling

Doing the opposite to turn it off.

For some reason, it stopped working the other day.  But my token still looks good, and I can still control the tstat from your plugin on the dashboard. 

Any ideas, before I bug Richard?
Title: Re: Plug-in for ecobee thermostats in development
Post by: ando1 on August 19, 2015, 09:05:12 pm
Hi Watou,

I am having some issues with this plugin (v1.2). I seem to be losing my token every day and I also cannot reliably control the cooling temp on my ecobee. I have deleted the plugin and re-installed many times and still get the same results. Every day or so, I will log into my Vera Edge and I will see the blue banner at the top of the page telling me to register a new PIN. Any suggestions you could provide would be much appreciated.


Thanks,

Andy
Title: Re: Plug-in for ecobee thermostats in development
Post by: Wekurtz74 on August 19, 2015, 09:25:59 pm
Hi Watou,

I am having some issues with this plugin (v1.2). I seem to be losing my token every day and I also cannot reliably control the cooling temp on my ecobee. I have deleted the plugin and re-installed many times and still get the same results. Every day or so, I will log into my Vera Edge and I will see the blue banner at the top of the page telling me to register a new PIN. Any suggestions you could provide would be much appreciated.


Thanks,

Andy
Andy,

Please read post 307 onward RE this issue
Title: Re: Plug-in for ecobee thermostats in development
Post by: ando1 on August 19, 2015, 09:32:36 pm
Thanks Wekurtz74,

I had read those posts before but I guess I missed the issue about the tokens getting lost. I guess since v1.3 is having issues will have to wait until Watou can fix it.

Thanks,
Andy
Title: Re: Plug-in for ecobee thermostats in development
Post by: Wekurtz74 on August 19, 2015, 09:33:41 pm
Thanks Wekurtz74,

I had read those posts before but I guess I missed the issue about the tokens getting lost. I guess since v1.3 is having issues will have to wait until Watou can fix it.

Thanks,
Andy
Forgive me if my comment gave the appearance of being "snarky" (as I Re read it, it does look that way).  It was not my intent. It does sound like you and I had [have) the same issue.  Hopefully the issue can be resolved.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 19, 2015, 11:26:08 pm
Thanks Wekurtz74,

I had read those posts before but I guess I missed the issue about the tokens getting lost. I guess since v1.3 is having issues will have to wait until Watou can fix it.

Thanks,
Andy
Forgive me if my comment gave the appearance of being "snarky" (as I Re read it, it does look that way).  It was not my intent. It does sound like you and I had [have) the same issue.  Hopefully the issue can be resolved.
There are two issues right now:

1. Ecobee's service is partially broken since last week, where equipment status and remote sensor occupancy aren't updating. I am wondering why this outage has lasted this long but I suspect that a key person is on vacation (and hopefully not left the company!)

2. I've uploaded two attempts at v1.3 of the plugin but both didn't install properly so I pulled them. I await insight from @mcvflorin as to why v1.2 installs properly but not my later attempts. V1.3 attempts to solve the sometimes frequent need for a new PIN (once I can get it to you).

I really hope these two issues are fixed soon.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: ando1 on August 20, 2015, 06:05:57 am
Thanks Wekurtz74,

I had read those posts before but I guess I missed the issue about the tokens getting lost. I guess since v1.3 is having issues will have to wait until Watou can fix it.

Thanks,
Andy
Forgive me if my comment gave the appearance of being "snarky" (as I Re read it, it does look that way).  It was not my intent. It does sound like you and I had [have) the same issue.  Hopefully the issue can be resolved.

Oh I didn't take you comments as being snarky at all, but thanks for being conscientious about it  :) It does seem as if we have the same issue and reading Watou's last post below it seems like there is a fix for it in 1.3.

@Watou: Thank you for the quick responses and being so active in trying to resolve the issues. I will wait patiently for the 1.3 update!


Andy
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on August 20, 2015, 11:09:41 am
Thanks Wekurtz74,

I had read those posts before but I guess I missed the issue about the tokens getting lost. I guess since v1.3 is having issues will have to wait until Watou can fix it.

Thanks,
Andy
Forgive me if my comment gave the appearance of being "snarky" (as I Re read it, it does look that way).  It was not my intent. It does sound like you and I had [have) the same issue.  Hopefully the issue can be resolved.
There are two issues right now:

1. Ecobee's service is partially broken since last week, where equipment status and remote sensor occupancy aren't updating. I am wondering why this outage has lasted this long but I suspect that a key person is on vacation (and hopefully not left the company!)

2. I've uploaded two attempts at v1.3 of the plugin but both didn't install properly so I pulled them. I await insight from @mcvflorin as to why v1.2 installs properly but not my later attempts. V1.3 attempts to solve the sometimes frequent need for a new PIN (once I can get it to you).

I really hope these two issues are fixed soon.

watou

Do you think this is what's causing my problems as well?  I figured your plugin went directly to the tstat for status changes, but now that I think about it (using a token), you are going to their website to see the changes, as well as the sensor data?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 20, 2015, 11:26:24 am
Thanks Wekurtz74,

I had read those posts before but I guess I missed the issue about the tokens getting lost. I guess since v1.3 is having issues will have to wait until Watou can fix it.

Thanks,
Andy
Forgive me if my comment gave the appearance of being "snarky" (as I Re read it, it does look that way).  It was not my intent. It does sound like you and I had [have) the same issue.  Hopefully the issue can be resolved.
There are two issues right now:

1. Ecobee's service is partially broken since last week, where equipment status and remote sensor occupancy aren't updating. I am wondering why this outage has lasted this long but I suspect that a key person is on vacation (and hopefully not left the company!)

2. I've uploaded two attempts at v1.3 of the plugin but both didn't install properly so I pulled them. I await insight from @mcvflorin as to why v1.2 installs properly but not my later attempts. V1.3 attempts to solve the sometimes frequent need for a new PIN (once I can get it to you).

I really hope these two issues are fixed soon.

watou

Do you think this is what's causing my problems as well?  I figured your plugin went directly to the tstat for status changes, but now that I think about it (using a token), you are going to their website to see the changes, as well as the sensor data?
Tom, that is almost certainly the source of your automation not working.  Heating, Cooling, Idle, FanOnly, Off are stuck because of service problems at ecobee.com, now for about a week or more.

There is no "local API" and no plans to offer one; it's all cloud-based.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on August 20, 2015, 11:34:55 am
Awesome.... thanks!
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 27, 2015, 11:45:33 am
@mcvflorin has approved v1.3 of the Ecobee plugin again, and it appears that the third time is a charm.  I was able to upgrade my VeraEdge (1.7.1320) from v1.2 to v1.3 without a problem, and I was also able to force an upgrade on my Vera 3 (1.5.622) without a problem.  Both installed the new version and carried on, as they always used to do.

If you need to force an upgrade to v1.3, this URL usually works:

http://<your_vera_IP_address>:3480/data_request?id=update_plugin&Plugin=3586

Or just choose the Update App button in UI7.

As usual, the full information, including change log, is here: http://watou.github.io/vera-ecobee/

Thanks to @mcvflorin for his assistance in getting past whatever the issue was.  If your results differ and you can't get v1.3 installed properly, please post here.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on August 31, 2015, 10:42:26 am
upgraded yesterday.... all fine.
woke up to my PIN needing to be redone.  Trying it now, but it doesn't seem to take.  worked on the Ecobee side (approved PIN), but on the Vera3 (U15) side... just still shows the pin in the device and won't turn green. 

Trying it again..by first removing it from the Ecobee apps list... hangs on the Ecobee side.  Finally approved a new one, but still doesn't work on Vera side.

I'm pretty sure this is a webserver issue on the Ecobee side... but just putting it here in case others see the same problem.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 31, 2015, 10:45:30 am
upgraded yesterday.... all fine.
woke up to my PIN needing to be redone.  Trying it now, but it doesn't seem to take.  worked on the Ecobee side (approved PIN), but on the Vera3 (U15) side... just still shows the pin in the device and won't turn green. 

Trying it again..by first removing it from the Ecobee apps list... hangs on the Ecobee side.  Finally approved a new one, but still doesn't work on Vera side.

I'm pretty sure this is a webserver issue on the Ecobee side... but just putting it here in case others see the same problem.
Make sure you give it 3-6 minutes to take.  The API says not to poll more often than 3 minutes, so the plugin won't. Could take longer than it used to (possibly).

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on August 31, 2015, 11:14:52 am
upgraded yesterday.... all fine.
woke up to my PIN needing to be redone.  Trying it now, but it doesn't seem to take.  worked on the Ecobee side (approved PIN), but on the Vera3 (U15) side... just still shows the pin in the device and won't turn green. 

Trying it again..by first removing it from the Ecobee apps list... hangs on the Ecobee side.  Finally approved a new one, but still doesn't work on Vera side.

I'm pretty sure this is a webserver issue on the Ecobee side... but just putting it here in case others see the same problem.
Make sure you give it 3-6 minutes to take.  The API says not to poll more often than 3 minutes, so the plugin won't. Could take longer than it used to (possibly).

watou

oh... i'll bet that's it.  working now.  That said.... they still appear to be having some web difficulties.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 25, 2015, 07:42:16 pm
@ watou

thank you for this great plugin
the ecobee is far better than the nest

would it be possible to add "precision scale" like you did for your nest plugin
to add a reading of decimal places
this is very useful for celcius

if i remember correctly the settings were 1/5/10
ex.
1  - 23
5  - 23.5
10- 23.8

thanks
hope its possible



Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on September 26, 2015, 05:03:32 am
@ watou

thank you for this great plugin
the ecobee is far better than the nest

would it be possible to add "precision scale" like you did for your nest plugin
to add a reading of decimal places
this is very useful for celcius

if i remember correctly the settings were 1/5/10
ex.
1  - 23
5  - 23.5
10- 23.8

thanks
hope its possible
I will add that feature next week.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 28, 2015, 06:18:16 pm
thank you
look forward to seeing this

i have an additional question

how can i go about setting the ecobee to home without holding
it would appear that regardless of hold settings (2hours,next event, etc..)
if the ecobee is set to home or away it never moves on unless unselected
according to ecobee hold settings are for specific temp and not home/away
home/away must be manually unselected

this is not the same as "smart home" or "smart away"
when in smart home or away the button is not actually checked in quick settings
the next event actually takes over

finding a way to trigger the smart home/away would resolve my issue
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on September 28, 2015, 06:45:12 pm
The SetClimateHold action sets an indefinite hold (file I_Ecobee1.xml, line 833), which can only be cleared by resuming the normal schedule or setting a new hold.  The plugin doesn't expose the different hold types possible in the API. [1]

Separately, I don't think there is a way through the API to put the thermostat in "smart home" or "smart away" state.

[1]: https://www.ecobee.com/home/developer/api/documentation/v1/functions/SetHold.shtml
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 28, 2015, 07:44:00 pm
thanks for your reply

that will make things difficult
the smart home function is not always working properly
i had the same issue with nest
however with nest, issuing a home command was not indefinite
anything could override it

i do understand that this is not an issue with your plugin
and that it lies solely with the api and how it functions
its just unfortunate
as i have no way of telling the stat that i am home without setting a hold

can you think of any workarounds


***edit
i was just reading the API link
what if the homeandhold was set with a nextTransition hold type
can that be done?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on September 28, 2015, 10:18:09 pm
what if the homeandhold was set with a nextTransition hold type
can that be done?

You could download the file I_Ecobee1.xml from your Vera, edit line 833 (or near there, depending on your file) to read "nextTransition" instead of "indefinite", and upload the changed file.  That way, whenever you set a climate hold, it will automatically expire when the program changes. 
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 29, 2015, 08:15:16 am
thanks i will try that

have you had any issues with the remote sensors interfering with the zwave network
since installing the ecobee
my zwave network has gotten slow and unreliable
i know they run the same frequency

i logged a call with vera as some devices now dont work at all
they are asking me to deactivate anything that is 900mhz
have you experienced anything like this

EDIT**
this issue has been extreemly noticeable since last night's ecobee firmware update
3.6.1.323
i think they are related
since this update my remote sensors never drop but now my zwave network is almost inoperable
will check with ecobee and add comment here
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on September 29, 2015, 01:57:18 pm
If they transmit in the same band, they could conflict, but they each only rarely transmit so the odds of crosstalk seem remote to me in theory. Have you run a network heal on your Z-Wave network lately?  I don't have both ecobee3 and Z-Wave in the same structure so I can't experiment here.



watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 29, 2015, 06:26:15 pm
ui7 no longer does heal
it was removed about 3 updates ago
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on September 30, 2015, 07:37:52 am
ui7 no longer does heal
it was removed about 3 updates ago
How does the Z-Wave network rebalance the mesh now? I switched to openHAB for Z-Wave some time ago so my question is just curiosity.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 30, 2015, 08:11:24 am
mcv claims that it heals overnight but
it does not look like it is
some of my devices had neighbour nodes that have been gone for a long time
that was part of the issue

im going too look in at openhab
i can see that the vera is a supported device
am i better off using vera as the zwave communication on my ui5 hub
or should i just get a zwave sick
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on September 30, 2015, 02:36:58 pm


im going too look in at openhab
i can see that the vera is a supported device
am i better off using vera as the zwave communication on my ui5 hub
or should i just get a zwave sick

Both will work, but a Z-Stick and a Raspberry Pi 2 will manage a Z-Wave network nicely (but no lock support currently). Or you could use @guessed's MiOS binding to your Vera and migrate the network later.



watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 04, 2015, 08:18:47 am
@ watou

thank you for this great plugin
the ecobee is far better than the nest

would it be possible to add "precision scale" like you did for your nest plugin
to add a reading of decimal places
this is very useful for celcius

if i remember correctly the settings were 1/5/10
ex.
1  - 23
5  - 23.5
10- 23.8

thanks
hope its possible

Hi @charettepa,

Please upload the attached I_Ecobee1.xml file to your Vera unit, allow LuaUPnP to reload, refresh your browser, and then look at the device variable for the main (bee) ecobee device (it might also say "Thermostat(s) 1" on it ).  You should now have a variable called TemperaturePrecision with a value of 1.  If you change it to 2, it should round temps to half a degree.  If you change it to 10, it should round temps to tenths of degrees.  See the plugin documentation here: http://watou.github.io/vera-ecobee/#controlling-the-precision-of-reported-temperatures (http://watou.github.io/vera-ecobee/#controlling-the-precision-of-reported-temperatures)

Please report if this change achieves what you wanted, and if so, I will commit it and add this change to the v1.4 version of the plugin.  Thanks!

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 05, 2015, 09:33:36 am
Applied it 5 minutes ago
working great
thank you so much
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 05, 2015, 12:00:48 pm
what if the homeandhold was set with a nextTransition hold type
can that be done?

You could download the file I_Ecobee1.xml from your Vera, edit line 833 (or near there, depending on your file) to read "nextTransition" instead of "indefinite", and upload the changed file.  That way, whenever you set a climate hold, it will automatically expire when the program changes.

I have found 6 areas total, that may need to be changed depending on my needs
can you please advise if below I have interpreted it correctly


835
local function setClimateHold
for local function (mode(heat/cool/auto))

859
local func = ecobee.setHoldFunction
home away hold for si stat

871
setOccupiedFunction
home away hold for ems stat

1055
local heatHoldTemp
for current setpoint heat

1081
local coolHoldTemp
for current setpoint cool

1130
local func = ecobee.setHoldFunction
for fan operation
 

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 05, 2015, 12:10:58 pm
Code: [Select]
    local function setClimateHold(session, selection, lul_device, holdClimateRef)
      local func = ecobee.setHoldFunction(nil, nil, "indefinite")
      func.params.holdClimateRef = holdClimateRef
      return setHold(session, selection, lul_device, func)
    end

Changing indefinite to nextTransition in the code above (line 835 now as you mentioned) will mean that all climate holds performed by the plugin will expire on the next transition in the weekly schedule, instead of holding indefinitely until resuming the program.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 05, 2015, 02:09:08 pm
even without changing the other lines?
what if I change heat or cool setpoint @ lines 1055 and 1081
or fan state @ line 1130

line 835 appears to be for mode change only

I could be reading the code wrong
but it seems to imply that their hold duration is independently controlled
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 05, 2015, 02:57:29 pm
even without changing the other lines?
what if I change heat or cool setpoint @ lines 1055 and 1081

If you made those "indefinite"s to "nextTransition"s, then your setpoint changes would expire when the program changed to the next confort setting/climate.  If that's what you want, change those lines as well.

or fan state @ line 1130

The same expiration on setting the fan to auto or on would apply if you changed this line.  Feel free to do so if that's what you want!
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 05, 2015, 04:06:01 pm
thanks @watou

yes, thats exactly what I want
any change i make in vera to not be permanent
I want my schedule to continue as normal

I am modifying the file now

thanks for clarifying that I did read it correctly

also

1-the API supports calling a specific comfort setting, even custom ones
do you have any plans of adding this to the vera plugin
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 05, 2015, 05:31:30 pm
1-the API supports calling a specific comfort setting, even custom ones
do you have any plans of adding this to the vera plugin

You can currently call the SetClimateHold action on the "house" device and pass it the name of climateRef.  A custom climateRef can be determined from the URL in the Ecobee web UI whiled editing the comfort setting; they are automatically generated and might look like "smart1" or "smart6", etc.  See SetClimateHold in http://watou.github.io/vera-ecobee/ for how to call it.  Example:

Code: [Select]
local service_id = "urn:ecobee-com:serviceId:Ecobee1"
local action = "SetClimateHold"
local args = { HoldClimateRef = "smart6" } -- the climateRef you want to switch to
local dev_num = 237 -- device number of the "house" device
luup.call_action(service_id, action, args, dev_num)
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 07, 2015, 09:37:26 pm
thanks for this
it is working

I would like to also do a conditional scene
using loop to look at the current state
the scene continues if its true and stops if its false
I already have a few of thees
one of which turns on the porch lite on scene trigger but only if its night time

what i would like to do with the ecobee is have a scene that sets the ecobee to home
only if the current state is "away"
can I read the current home/away state and will it reflect current schedule or smart home/away

this is what i currently have
local chold = luup.variable_get("urn:schemas-ecobee-com:device:EcobeeHouse:1","currentClimateRef",176)
return (chold == "away")

basically the condition is to continue if the hold condition is away
i thought it was working but its not
i know i am not too far off

also
is there a variable i can refference for current scheduled item instead of current hold
as it seems that ecobee leaves currentclimateref blank if its scheduled and not held

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 08, 2015, 05:36:30 am
what i would like to do with the ecobee is have a scene that sets the ecobee to home
only if the current state is "away"
can I read the current home/away state and will it reflect current schedule or smart home/away

this is what i currently have
local chold = luup.variable_get("urn:schemas-ecobee-com:device:EcobeeHouse:1","currentClimateRef",176)
return (chold == "away")

basically the condition is to continue if the hold condition is away
i thought it was working but its not
i know i am not too far off

also
is there a variable i can refference for current scheduled item instead of current hold
as it seems that ecobee leaves currentclimateref blank if its scheduled and not held

The device variable currentClimateRef gets its value this way (see #1 for the code):
So that variable does not let you know if the current climateRef is the result of the program running normally, or if it is the result of a hold that's based on a climateRef (aka comfort setting).  Also, I've noticed that some users have a hold type of "template" which I think has something to do with vacations, so the currentClimateRef variable is reporting an empty string, per the description above.  I do not know why this "template" hold is in place for those users, and you may be seeing this as the explanation for why currentClimateRef is empty when it ought to be showing the currently running program.  Perhaps clearing out any vacation settings might help.  It's not documented extensively in the API docs.

If you're up for it, you might want to fork the https://github.com/watou/vera-ecobee repository and make coding changes in the plugin for your private use (or just edit the I_Ecobee1.xml file and maintain it yourself).  I don't expect that I will have much more time to dedicate to this plugin, as I don't rely on it any more (switched to openHAB for my own HA needs, but still run a few Veras for side purposes).

In your code above, you are passing the device id urn:schemas-ecobee-com:device:EcobeeHouse:1, but I think you should be using the service ID urn:ecobee-com:serviceId:Ecobee1.

#1. https://github.com/watou/vera-ecobee/blob/master/src/I_Ecobee1.xml#L197
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 08, 2015, 10:58:22 am
thank you, that works

however
from what you posted
as per the ecobee api

     The device variable currentClimateRef gets its value this way (see #1 for the code):
      1- If there is currently a hold event and it's based on a climateRef, currentClimateRef is set to the climate ref for the current hold.
      2- If there is currently a hold event and it's not based on a climateRef, currentClimateRef is set to the empty string "".
      3- Otherwise, currentClimateRef's value is set to the current climateRef for the running program (schedule).

3 is not functioning as it should
scheduled events are not showing up in currentclimareref
unless a hold has been set currentclimateref is always blank "" and currenteventtype is "vacation" but this is incorrect
when a hold is set it works as described

i can confirm that there is currently no hold event so #2 should be bypassed and 3 should kick in
is this a bug in the ecobee stat, the api or the plugin
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 08, 2015, 12:14:15 pm


currentclimateref is always blank "" and currenteventtype is "vacation" but this is incorrect ...
i can confirm that there is currently no hold event ...
The problem is that there *is* a hold event, this "vacation" event that shouldn't be there, according to the API docs (well, the docs don't explain why it's there).

Any way to clear vacation info from the Ecobee web portal and see if that helps?


watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 08, 2015, 12:36:58 pm
i dont have a vacation hold though
i am running on normal schedule

i do have a scheduled vacation in much later in 2016
i will delete the vacation and see what happens
if that works, then i am guessing there is a bug in the ecobee stat that reports vacation as long as a scheduled one exists
if thats the case i will report it to them and here to advise everyone

****update
since I deleted the vacation that is scheduled far in the future
the event is now saying template instead of vacation
but the currentclimatereref is still blank
instead of reading what is currently scheduled

im guessing this should get reported to ecobee?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 08, 2015, 01:18:33 pm
i dont have a vacation hold though
i am running on normal schedule

i do have a scheduled vacation in much later in 2016
i will delete the vacation and see what happens
if that works, then i am guessing there is a bug in the ecobee stat that reports vacation as long as a scheduled one exists
if thats the case i will report it to them and here to advise everyone

****update
since I deleted the vacation that is scheduled far in the future
the event is now saying template instead of vacation
but the currentclimatereref is still blank
instead of reading what is currently scheduled

im guessing this should get reported to ecobee?
Let me first look for a durable workaround before telling Ecobee; I doubt that they would change their firmware over it.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 08, 2015, 01:21:27 pm
ok thanks for looking
but it does look like a bug on their end right?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 08, 2015, 02:12:34 pm
ok thanks for looking
but it does look like a bug on their end right?
It seems to disagree with the API docs, but it's probably more of the "not well documented behavior" sort.  I am thinking I can loop through the hold events and find the first one marked running.  Let me get back to you soon.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 08, 2015, 03:10:32 pm
thanks you

let me know if I can test anything
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 08, 2015, 04:47:22 pm
let me know if I can test anything

Please try the attached I_Ecobee1.xml and let me know if you see "vacation" or "template" any more.  You ought to now only see the currently running event type or "none" if there is no currently running event, and currentClimateRef should either be the current climate ref for the running program, or if there is a currently running event, the climate ref it's based on or the empty string if the currently running event is not based on a climate ref.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 08, 2015, 05:12:09 pm
you are the man!

that is now 3 things that you have edited, corrected, updated in the last 2 weeks
and you do it all almost instantly

thank you so much

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 08, 2015, 05:18:45 pm
you are the man!

that is now 3 things that you have edited, corrected, updated in the last 2 weeks
and you do it all almost instantly

thank you so much

You're welcome!  Please confirm, just to be certain, that this last file gives you what you think is the most sensible values for currentClimateRef and currentEventType in the various scenarios you can picture.  (Normal running program (no events), temperature or fan hold event, climate/comfort setting hold event, vacation running/scheduled/not scheduled, anything else you can think of.)

I just want to be able to close this out and queue it for the v1.4 release.  Thanks for testing my changes!

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 08, 2015, 11:48:43 pm
it seems to return normal running schedule and hold event override it
please keep in mind that smart home and smart away seem to count as normal hold
so if your schedule is away but you are currently smart home
the parameter reports a hold of home

this seems to match the description provided by ecobee
i added my vacation back and it continues to function properly since the new file
smart home/away shows up as normal holds
i would rather see the actual schedule event as smart home/away can be canceled by a resume schedule
that being said, what is now happening with your mod seems logical and does match what is documented for the api

unless you have a way of detecting if it is in smart home/away versus normal home/away vs schedule
i'd say what you are doing now is perfect

ill come home early tomorrow before home mode kicks in and see if the event type is different on a smart home

thanks again
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 09, 2015, 03:50:25 am
I will queue this change for v1.4

Ecobee's developer support said: "it is also possible to check that type field for values of autoAway and autoHome" [1].

So you ought to be able to tell from the currentEventType variable if it says autoAway or autoHome.

[1] http://developer.ecobee.com/api/topics/where-are-the-settings-and-values-for-smart-home-away#reply_15666267
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 09, 2015, 07:25:42 am
if thats correct
and the event type can show autohome and autoaway
i would think that the climateref should continue showing the schedeuled climate rather than the held home/away
i will be able to confirm by around 4pm 
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 09, 2015, 04:29:47 pm
i just came home early which activated an autohome
the even does show autohome and the climate hold shows home
so it is now working exactly as documented by ecobee
i have attached a screenshot

if i want to read the contents of the event from luup like i did for climate
below is what i am using

local chold = luup.variable_get("urn:ecobee-com:serviceId:Ecobee1","currentevent",176)
return (chold == "autoHome")

**confirmed working


I now have access to and control of everything i need
Thank you
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 09, 2015, 06:46:52 pm
Thanks for verifying.  Your code looks correct, except the device variable name is currentEventType.

Code: [Select]
return "autoHome" == luup.variable_get("urn:ecobee-com:serviceId:Ecobee1","currentEventType",176)
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 09, 2015, 07:06:29 pm
thanks, you are correct
i did type it correctly in the luup box
i just didnt type it right here as it was not a copy paste and i missed that part

it is working great
i now perform several checks and actions based on different criteria

4 examples are
- when unlock deadbolt from outside if event is smart away then resume normal program and turn on hallway light if its nighttime
- when unlock deadbolt from outside if event is smart home then stay smarthome  and turn on hallway light if its nighttime
- when unlock deadbolt from outside if climate is away then hold home with nextTransition and turn on hallway light if its nighttime
- if vera house mode plugin shows that home is away then set ecobee to away with nextTransition and turn off all lights and lock deadbolt
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 09, 2015, 07:19:09 pm
i have a question about the 3 wattage values

i am assuming it is for stage 1 fan, stage 2 fan, ac compressor
can you please tell me in which order and if i got the items correct
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 09, 2015, 07:33:10 pm
Those are great example use cases, and I'm glad to have helped make it happen!

The three wattage values are documented here:

http://wiki.micasaverde.com/index.php/Luup_UPnP_Variables_and_Actions#EnergyMetering1

How Vera uses those values is unknown to me.  I assume some code would compute energy consumption based on heat/cool/fan operating time using operating state (Heating/Cooling/FanOnly/Idle).  If that happens, the value will be approximate at best because the 3-minute polling does not change operating state exactly when it really changes, but at some time up to around 3 minutes later.

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 13, 2015, 02:29:08 pm
on the heat/cool/fan subject

if your furnace is gas
the heat  would be 0 right?

 
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 13, 2015, 02:39:03 pm
if your furnace is gas
the heat  would be 0 right?
It depends how you want to use the data.  If your gas furnace runs a blower fan or a circulating pump when it's called for heat, then those take watts to operate, but the real cost is in the gas volume you consume.  Unless you have clamps or some other way of measuring electricity usage, it would be hard to guess a useful number.  The plugin doesn't do anything with the three numbers other than provide a device variable in which to record them.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 14, 2015, 12:25:23 pm
the only fan i have is the one in the furnace which has its own value
i assume that when heating the device counts the fan value as well?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 14, 2015, 01:28:27 pm
the only fan i have is the one in the furnace which has its own value
i assume that when heating the device counts the fan value as well?
I don't know what uses those values, so I don't know any more than the wiki doc link I sent.  There may be others who chime in on a different thread who do power management with Vera.  Sorry I can't help!
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on October 14, 2015, 02:41:53 pm
actually, you have been a tremendous help
thank you so much for all the changes and updates
with every question you had quick answers and turn-around

I truly appreciate all you have done
 
Thank You
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on October 14, 2015, 02:45:37 pm
actually, you have been a tremendous help
thank you so much for all the changes and updates
with every question you had quick answers and turn-around

I truly appreciate all you have done
 
Thank You
You're very welcome!

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: rbrockman on November 07, 2015, 12:35:11 pm
I'm looking for a method to use this plugin to control the minimum fan run time.    Ideally luup code I could place into a scene would be perfect.

Looks like in the ecobee API there is a Settings object ( https://beta.ecobee.com/home/developer/api/documentation/v1/objects/Settings.shtml)  which has a fanMinOnTime property.

Is this possible?



Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on November 08, 2015, 03:03:56 am
I'm looking for a method to use this plugin to control the minimum fan run time.    Ideally luup code I could place into a scene would be perfect.

Looks like in the ecobee API there is a Settings object ( https://beta.ecobee.com/home/developer/api/documentation/v1/objects/Settings.shtml)  which has a fanMinOnTime property.

Is this possible?

The plugin doesn't currently offer this functionality and I'm not able to add it at the moment, but if you look at this code here:

https://github.com/watou/vera-ecobee/blob/master/src/I_Ecobee1.xml#L1118

You can see where the plugin is constructing Lua tables that will be sent to the API to change the hvacMode:

Code: [Select]
{ settings = { hvacMode = hvacMode } }
If you were to edit your I_Ecobee1.xml and S_Ecobee1.xml files to add a new Luup action that does similar steps, you could change any thermostat settings you want (of course, subject to the API rules that you linked earlier).  Sorry I'm not able to work on it at present, but above would be the rough roadmap for adding the functionality you're after.

I've written a "binding" for openHAB (https://github.com/openhab/openhab/wiki/Ecobee-Binding), sort of similar to a Vera plugin, and it gives you complete access to all information and function in the Ecobee API.  Of course you are a Vera user so this may not be helpful, but I know of at least one openHAB user who succeeded in controlling fanMinOnTime in openHAB.
Title: Re: Plug-in for ecobee thermostats in development
Post by: mda on December 03, 2015, 11:24:20 pm
@watou I installed 2 Ecobees to replace my nests this week and wanted to say thanks for the ecobee plugin !

Also, if I may ask, is there any way to get to the weather forecast that i believe the ecobee api exposes? Thanks !


Sent from my iPhone using Tapatalk
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on December 04, 2015, 02:26:50 am
@watou I installed 2 Ecobees to replace my nests this week and wanted to say thanks for the ecobee plugin !

Also, if I may ask, is there any way to get to the weather forecast that i believe the ecobee api exposes? Thanks !

You're welcome!  You're right that the Ecobee API provides a weather forecast (and it's available in the openHAB binding for Ecobee), but it would be a big job to find a good way to expose that in Vera.  I wish a Vera plugin developer would clone the github repo and submit pull requests for this feature, because I know I won't be able to get to it soon.  So sorry.
Title: Plug-in for ecobee thermostats in development
Post by: mda on December 04, 2015, 02:37:40 am
I wish I had the skills to help with the code :(

Any chance the data could just be put into device variables on the home or temp device? That would not display nicely but it would be usable to watch the variables and act on changes.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on December 05, 2015, 08:08:31 pm
Just installed this Plugin (thank you Watou!)

Questions...

Does sensors' Arm/Bypass do something to the Ecobee system?
I have 2 devices showing Humidity?  (all other devices are singular)
urn:schemas-ecobee-com:device:EcobeeHumidistat:1
... humid.316579708532
urn:schemas-micasaverde-com:device:HumiditySensor:1
... sensor.316579708532_ei:0_2
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on December 06, 2015, 02:43:29 am
Just installed this Plugin (thank you Watou!)

You're very welcome!

Does sensors' Arm/Bypass do something to the Ecobee system?

No; the Armed/Bypass switch is only useful on the Vera, should you want to use it to ignore occupancy sensors in your own automation.  All motion sensors on the Vera have an Armed/Bypass switch.

I have 2 devices showing Humidity?  (all other devices are singular)
urn:schemas-ecobee-com:device:EcobeeHumidistat:1
... humid.316579708532
urn:schemas-micasaverde-com:device:HumiditySensor:1
... sensor.316579708532_ei:0_2

This was intentional, because I added the ecobee3 remote sensor support based on what the API reports, and it reports the thermostat itself as a remote sensor that reports temperature, occupancy and humidity (whereas actual remote sensors report occupancy and temperature).  I have a to-do for the plugin to add feedback to the humidistat device that shows if it's currently humidifying, dehumidifying or is idle, like the "ModeState" of the thermostat device that shows Heating, Cooling, Idle, etc.  Ideally, the humidistat device would have setpoints you could control for acceptable humidity levels, analogous to the thermostat.

Hope this makes sense!
Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on December 06, 2015, 04:44:47 pm
OT... anyone having, or had, issues with Remote Sensors showing Unoccupied when that is not true? All my sensors ALWAYS show unoccupied... even when I walk around, pick them up, etc.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on December 06, 2015, 04:55:37 pm
OT... anyone having, or had, issues with Remote Sensors showing Unoccupied when that is not true? All my sensors ALWAYS show unoccupied... even when I walk around, pick them up, etc.
I only knew this to be a problem with an old firmware version, but I think everyone's been upgraded. I don't have the numbers offhand, but is there any chance you're using outdated ecobee3 firmware?

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on December 06, 2015, 04:56:52 pm
I thought ecobee updated itself when it is installed? I just installed it 2 days ago
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on December 06, 2015, 05:00:34 pm
I thought ecobee updated itself when it is installed? I just installed it 2 days ago
Well it's unlikely to be the problem in that case.  Could you press the Get PIN button and register the new 4-letter value at ecobee.com, just in case?

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on December 06, 2015, 05:01:42 pm
the issue is not with the Plugin, the issue is with the Ecobee not showing Occupancy
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on December 09, 2015, 10:10:44 am
For those of you on UI7 and with the ecobee3. I modified a few files from the plugin and branched off of watou's git repo.

It incorporates the latest files watou provided on the forum, fixes to all the UI7 icons, ads the ability to set all 4 modes (home, away, sleep, vacation) from the UI using the house device. assuming you created an extra mode named "vacation" on the ecobee as well.

Download all the files from here
https://github.com/rafale77/vera-ecobee/tree/rafale77-patch-1/src

and upload to the vera using from the apps/develop apps/ luup file menu.
Title: Re: Plug-in for ecobee thermostats in development
Post by: jcolter on December 09, 2015, 07:49:19 pm
Hi Anhman,

I tried uploading your files from your last post to upgrade my already working Ecobee plugin but am getting the following after the LUUP restarts.  To fix it I just have to go into the Ecobee plugin in install apps and click update and it corrects the errors but I assume that also wiped the new files.

GET_LANG(system_error,System error) : Device: 183. Fail to load implementation file D_Ecobee1.xml
GET_LANG(system_error,System error) : Device: 184. Fail to load implementation file D_EcobeeThermostat1.xml
GET_LANG(system_error,System error) : Device: 185. Fail to load implementation file D_EcobeeHumidistat1.xml
GET_LANG(system_error,System error) : Device: 186. Fail to load implementation file D_EcobeeHouse1.xml

any ideas?
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on December 09, 2015, 09:10:07 pm
Let me go back and look at the code tonight. These are the exact files I am running now but I may have implemented some customization I failed to remove. Will get back to you.
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on December 10, 2015, 03:19:46 am
ok I think I figured it out. Please do not upload all the files. Only the json files should be uploaded to the vera.
There is a compression issue when loading the xml this way which makes them unreadable. I actually only modified the json files so they are the only ones needed.
Please try it that way and let me know if it fixes the issue.


Let me go back and look at the code tonight. These are the exact files I am running now but I may have implemented some customization I failed to remove. Will get back to you.
Title: Re: Plug-in for ecobee thermostats in development
Post by: jcolter on December 10, 2015, 12:17:12 pm
Hey anhman,

That fixed the error but when Luup reloaded this time I lost control of anything.  The only devices left were:
Ecobee-Home5  (motion)
Ecobee-Home3 ( Temp)
Ecobee-Home4 (humidity)

I updated the app again from installed apps and got back  :
Ecobee Is the one with the pin listed
Ecobee-home  (my name of my unit)  this one displays the temp controls in the main device icon
Ecobee-home1  Another humidity one
Ecobee-home2 has the hold climate controls in the control tab for the device

The main reason I was trying your updated files was that the hold controls were not working in the current 1.3 verison I have installed.   Any thoughts/help would be greatly appreciated.

Cheers,
Jeff
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on December 10, 2015, 01:15:27 pm
This is very strange. The fact that the devices do not show up would indicate that the json file is invalid. What version of vera firmware are you running?

I found a syntax error on the Ecobee json (the one with the pin) but somehow it never bothered my vera. I corrected it on github. For some reason the json simulator says this json is invalid but it loads just fine.
for the other 3 (home, humidistat and thermostat), can you do a copy of content (text) of any of the json and paste in in the device json simulator under apps/develop apps to see what it says to you? If it is valid, you should be able to see the device item at the bottom. Mine shows this:

Edit: I found a syntax error in the original D_Ecobee1.json and corrected it in my branch of github. It now shows correctly in the simulator.
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on December 10, 2015, 01:49:39 pm

The main reason I was trying your updated files was that the hold controls were not working in the current 1.3 verison I have installed.   Any thoughts/help would be greatly appreciated.


Do you mean that clicking on one of the house device buttons of the plugin does not trigger a hold on the ecobee side?

This sounds more like a communication problem between the plugin and the ecobee API. Does it report the ecobee mode in the plugin correctly? I have never encountered this problem. I only added the ability to access more than 2 modes from the UI.
Title: Re: Plug-in for ecobee thermostats in development
Post by: jcolter on December 11, 2015, 05:56:17 pm
Ya clicking the buttons was not working.  I ended up uninstalling the ecobee plugin reinstalling it then loading your files and then recreating the pin and connecting vera to the ecobee website.  However as soon as I did that I lost the device with the pin and was left with only the 3 devices I mentioned before.  I tried loading one of the json files text into the debugger and got invalid Json. 

At this point I used the upgrade button in the install apps and got things back to where I started except the button on the devices now seem to be working. I guess I needed to remove the device completely and repair it to the vera.  Anyhow I am heading off on a trip so I won't have time to test with your updated version till next week.  Thank for your time.

Jeff
Title: Re: Plug-in for ecobee thermostats in development
Post by: Glen Koenig on January 02, 2016, 10:44:53 am
OT... anyone having, or had, issues with Remote Sensors showing Unoccupied when that is not true?

The remote sensor cover is clocked wrong, so that the motion sensor is behind the hard plastic instead of the opaque window.

Quote
We?re sorry.
Your room sensor may not be reading occupancy.

We?ve recently learned that the covers on some sensors were assembled improperly. As a result, your sensor might read ?unoccupied? when the room is ?occupied', but it can still measure temperature and connect with your ecobee. It appears that your sensor(s) identified by IDs JF8S, L276, L36Q are affected. Fortunately, you can fix it (in 60 seconds), or get it replaced.

Link to fix from ecobee... https://www.ecobee.com/sensor/replacement?d=37E2502486026EAE38019996C6266081006C030F7839EB8D6E4A98AEB57B1D851A78F50A2810153B488DF365EAD6E6B3#fix (https://www.ecobee.com/sensor/replacement?d=37E2502486026EAE38019996C6266081006C030F7839EB8D6E4A98AEB57B1D851A78F50A2810153B488DF365EAD6E6B3#fix)
Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on January 02, 2016, 11:06:06 am
OT... anyone having, or had, issues with Remote Sensors showing Unoccupied when that is not true?

The remote sensor cover is clocked wrong, so that the motion sensor is behind the hard plastic instead of the opaque window.

Quote
We?re sorry.
Your room sensor may not be reading occupancy.

We?ve recently learned that the covers on some sensors were assembled improperly. As a result, your sensor might read ?unoccupied? when the room is ?occupied', but it can still measure temperature and connect with your ecobee. It appears that your sensor(s) identified by IDs JF8S, L276, L36Q are affected. Fortunately, you can fix it (in 60 seconds), or get it replaced.

Link to fix from ecobee... https://www.ecobee.com/sensor/replacement?d=37E2502486026EAE38019996C6266081006C030F7839EB8D6E4A98AEB57B1D851A78F50A2810153B488DF365EAD6E6B3#fix (https://www.ecobee.com/sensor/replacement?d=37E2502486026EAE38019996C6266081006C030F7839EB8D6E4A98AEB57B1D851A78F50A2810153B488DF365EAD6E6B3#fix)
Right, would have been nice for them to send emails immediately, not almost two months after the issue was found

Sent from my A1-840FHD using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on January 02, 2016, 10:36:11 pm
I keep having a problem where I get a message on the Vera...
"ecobee : Not yet authorized. Press 'Get PIN' once; wait for PIN; enter at ecobee.com."

The first time this happened I re-did the pin and that lasted fr almost a week until this message popped up again.

anyone have this issue, or know how to fix?

thx
Title: Re: Plug-in for ecobee thermostats in development
Post by: Glen Koenig on January 04, 2016, 03:15:05 pm
I keep having a problem where I get a message on the Vera...
"ecobee : Not yet authorized. Press 'Get PIN' once; wait for PIN; enter at ecobee.com."

The first time this happened I re-did the pin and that lasted fr almost a week until this message popped up again.

anyone have this issue, or know how to fix?

thx

Yes, and I just did it (get pin) again this morning. I'm running plug-in version 1.3.

Could it be due to the new calendar year?

http://watou.github.io/vera-ecobee/ (http://watou.github.io/vera-ecobee/)
Quote
Also, you may want to mark your calendar for next year because this authorization expires after one year. External events may also invalidate the authorization sooner

I didn't see it mentioned in the instructions, but I entered the Ip address of the ecobee 3 in the Advance tab of the plug-in.
Title: Re: Plug-in for ecobee thermostats in development
Post by: klamath on January 14, 2016, 01:51:20 am
I've been getting "ecobee : Not yet authorized. Press 'Get PIN' once; wait for PIN; enter at ecobee.com. " twice a day now, is there a fix?



I keep having a problem where I get a message on the Vera...
"ecobee : Not yet authorized. Press 'Get PIN' once; wait for PIN; enter at ecobee.com."

The first time this happened I re-did the pin and that lasted fr almost a week until this message popped up again.

anyone have this issue, or know how to fix?

thx
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 14, 2016, 02:30:01 am
I will try to find a more permanent solution for prematurely discarded tokens in a 1.4 plugin release, hopefully by the end of the weekend.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 17, 2016, 01:13:24 pm
I submitted v1.4 of the Ecobee plugin to apps.mios.com.  By past experience, it will take a small number of days for it to be approved.

Fixes and enhancements:


Full documentation and release notes here: https://watou.github.io/vera-ecobee/

Please report any regressions or not working as advertised here or at https://github.com/watou/vera-ecobee/issues

Thanks!
Title: Re: Plug-in for ecobee thermostats in development
Post by: mesa on January 17, 2016, 09:25:41 pm
Set-up a new Vera edge for the first time today. I installed the Ecobee plugin flawlessly, but on the dashboard it was showing the thermostat device as a temperature setting of 0.0, even though it was reading the current temperature as 68. When I went over to the actual thermostat, it was indicating "45 and holding", which is obviously not the temperature it should be.

As of right now I uninstall the the app(s) because I didnt have time to de-bug it tonight. Any ideas what caused this? Anything I should have done differently?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 19, 2016, 08:46:47 am
Set-up a new Vera edge for the first time today. I installed the Ecobee plugin flawlessly, but on the dashboard it was showing the thermostat device as a temperature setting of 0.0, even though it was reading the current temperature as 68. When I went over to the actual thermostat, it was indicating "45 and holding", which is obviously not the temperature it should be.

As of right now I uninstall the the app(s) because I didnt have time to de-bug it tonight. Any ideas what caused this? Anything I should have done differently?

The Ecobee plugin was designed for Vera's UI5 which supports a heat setpoint and a cool setpoint.  UI7 broke that, with the thinking "In UI7 heat and cool setpoints are replaced by only one generic setpoint like the real thermostat devices have."  While it's true from a UI standpoint that many thermostats show a single setpoint, in the underlying protocols they may have many setpoints, and which to show the user is a UI problem, not a plugin problem.  This is especially true when a thermostat is in "auto" or "heat-cool" mode, where the user can set a range of temperatures.

I had asked for documentation on how to allow the Ecobee plugin to work correctly in both UI5 and UI7, but it never appeared.  If it does appear, I will update the plugin so it works properly on both UI5 and UI7.  I own 3 Veras, one staying at UI5, even though I no longer rely on them.

I hope this sufficiently explains what you observed.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 19, 2016, 08:47:58 am
I submitted v1.4 of the Ecobee plugin to apps.mios.com.  By past experience, it will take a small number of days for it to be approved.

Fixes and enhancements:

  • Let user choose precision of reported temperatures enhancement (#19)
  • Recognize only the currently running event for currentClimateRef/currentEventType bug (#20)
  • Token issue with ecobee API bug (#21)
  • Added humidity mode state to humidistat device enhancement (#22)

Full documentation and release notes here: https://watou.github.io/vera-ecobee/

Please report any regressions or not working as advertised here or at https://github.com/watou/vera-ecobee/issues

Thanks!

MCV has published v1.4 of the Ecobee plugin!  Please install it and report any issues, and thank you!
Title: Re: Plug-in for ecobee thermostats in development
Post by: klamath on January 19, 2016, 09:27:19 am
My vera is now in a infinite loop of reboots after v1.4 upgrade.  contacting vera for help
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 19, 2016, 10:06:12 am
My vera is now in a infinite loop of reboots after v1.4 upgrade.  contacting vera for help

I wonder if this is similar to what happened last August.  Everyone please heed @klamath's warning until this is resolved.  Ugh.

@mcvflorin, any advice?
Title: Re: Plug-in for ecobee thermostats in development
Post by: mesa on January 19, 2016, 12:04:35 pm

The Ecobee plugin was designed for Vera's UI5 which supports a heat setpoint and a cool setpoint.  UI7 broke that...

Thanks for the feedback! After I had done a little more digging I was pretty sure it was a UI 5 vs. 7 thing. I guess I should roll it back.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 22, 2016, 07:23:53 am
I have since heard that a user had installed v1.4 of the Ecobee plugin without issues, so perhaps it was a temporary issue that caused the update to wreak havoc earlier.  Please give v1.4 of the plugin a try.  It should fix the prematurely expiring tokens problem, and a few other bells and whistles.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: klamath on January 22, 2016, 11:35:26 am
I just tried an upgrade failed, restored from backup, uninstalled, fresh install same issue.

LuaUPnP keeps cycling non stop

01   01/22/16 10:33:34.586   Device_LuaUPnP::LoadDeviceDoc can't load /etc/cmh-lu//D_Ecobee1.xml <0x77dfd320>
02   01/22/16 10:33:34.586   JobHandler_LuaUPnP::m_sMissingFile_set /etc/cmh-lu//D_Ecobee1.xml <0x77dfd320>
02   01/22/16 10:33:34.587   JobHandler_LuaUPnP::CreateDevice_LuaUPnP failed to load 102/D_Ecobee1.xml so device 102 is offline while waiting for download the file <0x77dfd320>
09   01/22/16 10:33:37.751   JobHandler_LuaUPnP::Run device 102  room 0 type urn:schemas-ecobee-com:device:Ecobee:1 cat 0:-1 id  parent 0/0x85f1e0 upnp: 0 plugin:3586 pnp:0 mac: ip: <0x77dfd320>
03   01/22/16 10:33:37.774   JobHandler_LuaUPnP::Run ready 33 devices oem:1 skin:1-mios installation 45011571 missing /etc/cmh-lu//D_Ecobee1.xml version *1.7.1707*  allow_evt: 1 allow_ud: 1 upnp 0 netpnp: 1 reprovision: 0 secure: 0 tz:21600 tnow:1453480417 dst: 0 gmt:-21600 tz:CST / CDT fahr:1 changed: 0 pMem 0xe1b000 start 7897088 diff: 6893568 <0x77dfd320>


Did a git clone and copied /src into /etc/cmh-lu, no errors but lua :

2016-01-22 10:47:22 - LuaUPnP Terminated with Exit Code: 0



2016-01-22 10:47:22 - LuaUPnP crash


I have since heard that a user had installed v1.4 of the Ecobee plugin without issues, so perhaps it was a temporary issue that caused the update to wreak havoc earlier.  Please give v1.4 of the plugin a try.  It should fix the prematurely expiring tokens problem, and a few other bells and whistles.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: mda on January 22, 2016, 12:15:56 pm
... Please give v1.4 of the plugin a try...

watou

Updating to 1.4 worked fine for me (Vera 3, UI5)
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 22, 2016, 02:02:38 pm
I just tried an upgrade failed, restored from backup, uninstalled, fresh install same issue.

LuaUPnP keeps cycling non stop

01   01/22/16 10:33:34.586   Device_LuaUPnP::LoadDeviceDoc can't load /etc/cmh-lu//D_Ecobee1.xml <0x77dfd320>
02   01/22/16 10:33:34.586   JobHandler_LuaUPnP::m_sMissingFile_set /etc/cmh-lu//D_Ecobee1.xml <0x77dfd320>
02   01/22/16 10:33:34.587   JobHandler_LuaUPnP::CreateDevice_LuaUPnP failed to load 102/D_Ecobee1.xml so device 102 is offline while waiting for download the file <0x77dfd320>
09   01/22/16 10:33:37.751   JobHandler_LuaUPnP::Run device 102  room 0 type urn:schemas-ecobee-com:device:Ecobee:1 cat 0:-1 id  parent 0/0x85f1e0 upnp: 0 plugin:3586 pnp:0 mac: ip: <0x77dfd320>
03   01/22/16 10:33:37.774   JobHandler_LuaUPnP::Run ready 33 devices oem:1 skin:1-mios installation 45011571 missing /etc/cmh-lu//D_Ecobee1.xml version *1.7.1707*  allow_evt: 1 allow_ud: 1 upnp 0 netpnp: 1 reprovision: 0 secure: 0 tz:21600 tnow:1453480417 dst: 0 gmt:-21600 tz:CST / CDT fahr:1 changed: 0 pMem 0xe1b000 start 7897088 diff: 6893568 <0x77dfd320>


Did a git clone and copied /src into /etc/cmh-lu, no errors but lua :

2016-01-22 10:47:22 - LuaUPnP Terminated with Exit Code: 0



2016-01-22 10:47:22 - LuaUPnP crash


I have since heard that a user had installed v1.4 of the Ecobee plugin without issues, so perhaps it was a temporary issue that caused the update to wreak havoc earlier.  Please give v1.4 of the plugin a try.  It should fix the prematurely expiring tokens problem, and a few other bells and whistles.

watou

I looked through my own forum private messages from last August when I submitted v1.3, and your log looks nearly identical to what I had reported to MCV at the time.  I received this report back from the MCV person at the time:

Quote
I found that there were 2 servers behind the apps.mios.com domain, and one of them had some issues.
Now the server with the issues was removed, so apps.mios.com points only to the good server.
The problems you were experiencing with the plugin installation could be related to that.

So my suspicion, having no internal visibility to MCV's operations, is that the problem from last August is once again showing itself.  I have had no communication with MCV personnel since August, so I can't offer any more advice, other than maybe try again and hope you get the "good" server and not the "bad" server (assuming that was the root cause)?  And yes, I very much understand any frustration you may have about this.

Regards,
watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: klamath on January 22, 2016, 02:10:35 pm
Can I manually patch the files affecting the API token issue?  That is the only thing im really after with the 1.4 upgrade.


Please advise.

Tim



I just tried an upgrade failed, restored from backup, uninstalled, fresh install same issue.

LuaUPnP keeps cycling non stop

01   01/22/16 10:33:34.586   Device_LuaUPnP::LoadDeviceDoc can't load /etc/cmh-lu//D_Ecobee1.xml <0x77dfd320>
02   01/22/16 10:33:34.586   JobHandler_LuaUPnP::m_sMissingFile_set /etc/cmh-lu//D_Ecobee1.xml <0x77dfd320>
02   01/22/16 10:33:34.587   JobHandler_LuaUPnP::CreateDevice_LuaUPnP failed to load 102/D_Ecobee1.xml so device 102 is offline while waiting for download the file <0x77dfd320>
09   01/22/16 10:33:37.751   JobHandler_LuaUPnP::Run device 102  room 0 type urn:schemas-ecobee-com:device:Ecobee:1 cat 0:-1 id  parent 0/0x85f1e0 upnp: 0 plugin:3586 pnp:0 mac: ip: <0x77dfd320>
03   01/22/16 10:33:37.774   JobHandler_LuaUPnP::Run ready 33 devices oem:1 skin:1-mios installation 45011571 missing /etc/cmh-lu//D_Ecobee1.xml version *1.7.1707*  allow_evt: 1 allow_ud: 1 upnp 0 netpnp: 1 reprovision: 0 secure: 0 tz:21600 tnow:1453480417 dst: 0 gmt:-21600 tz:CST / CDT fahr:1 changed: 0 pMem 0xe1b000 start 7897088 diff: 6893568 <0x77dfd320>


Did a git clone and copied /src into /etc/cmh-lu, no errors but lua :

2016-01-22 10:47:22 - LuaUPnP Terminated with Exit Code: 0



2016-01-22 10:47:22 - LuaUPnP crash


I have since heard that a user had installed v1.4 of the Ecobee plugin without issues, so perhaps it was a temporary issue that caused the update to wreak havoc earlier.  Please give v1.4 of the plugin a try.  It should fix the prematurely expiring tokens problem, and a few other bells and whistles.

watou

I looked through my own forum private messages from last August when I submitted v1.3, and your log looks nearly identical to what I had reported to MCV at the time.  I received this report back from the MCV person at the time:

Quote
I found that there were 2 servers behind the apps.mios.com domain, and one of them had some issues.
Now the server with the issues was removed, so apps.mios.com points only to the good server.
The problems you were experiencing with the plugin installation could be related to that.

So my suspicion, having no internal visibility to MCV's operations, is that the problem from last August is once again showing itself.  I have had no communication with MCV personnel since August, so I can't offer any more advice, other than maybe try again and hope you get the "good" server and not the "bad" server (assuming that was the root cause)?  And yes, I very much understand any frustration you may have about this.

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 22, 2016, 02:20:09 pm
Can I manually patch the files affecting the API token issue?  That is the only thing im really after with the 1.4 upgrade.

I really don't know if it's possible to successfully replace L_ecobee.lua.lzoenc from a patch.  The other files that differ from v1.3 are D_EcobeeHumidistat1.json, I_Ecobee1.xml, and S_Ecobee1.xml.  I would be happy if you could exert whatever pressure on the Vera folks to sort out their issue, so their app update system works for their customers.  Thanks for your understanding.
Title: Re: Plug-in for ecobee thermostats in development
Post by: klamath on January 22, 2016, 03:08:14 pm
Understood, unleashing irate customer email in 3,2,1. Sent.


Tim



Can I manually patch the files affecting the API token issue?  That is the only thing im really after with the 1.4 upgrade.

I really don't know if it's possible to successfully replace L_ecobee.lua.lzoenc from a patch.  The other files that differ from v1.3 are D_EcobeeHumidistat1.json, I_Ecobee1.xml, and S_Ecobee1.xml.  I would be happy if you could exert whatever pressure on the Vera folks to sort out their issue, so their app update system works for their customers.  Thanks for your understanding.
Title: Re: Plug-in for ecobee thermostats in development
Post by: mda on January 23, 2016, 01:48:30 pm
Updating to 1.4 worked fine for me (Vera 3, UI5)

I spoke too soon. My vera has been rebooting 2-3 times in a row then luup restarting 2-3 times in a row every few hours. I had to restore to a backup with 1.3 and i will see if that is more stable.
Title: Re: Plug-in for ecobee thermostats in development
Post by: klamath on January 23, 2016, 01:50:40 pm
If you email support you should have them link the issues, my ticket number is #155348.

Updating to 1.4 worked fine for me (Vera 3, UI5)

I spoke too soon. My vera has been rebooting 2-3 times in a row then luup restarting 2-3 times in a row every few hours. I had to restore to a backup with 1.3 and i will see if that is more stable.
Title: Re: Plug-in for ecobee thermostats in development
Post by: jcolter on January 24, 2016, 06:34:45 pm
Hi,  I updated to the 1.4 plugin after the latest Vera firmware update and keep getting a message "download Luup plugin" at the top of the vera web page.  The vera seems to hang and might be rebooting as I have a hard time getting a response from the web page.  After a few attempts I can get to the plugins page and uninstall the plugin and then the vera begins operating properly again. 

Anyone else have this problem/find a fix?  I tried reinstalling the plugin a few times but had the same thing happen.  Is it possible to reinstall the 1.3 plugin manually?

Cheers, Jeff
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 24, 2016, 11:40:57 pm
Anyone else have this problem/find a fix?  I tried reinstalling the plugin a few times but had the same thing happen.  Is it possible to reinstall the 1.3 plugin manually?

Please read a number of messages immediately previous to yours that discusses this issue.  Very unfortunate that this issue with apps.mios.com is still not resolved.

I don't know if it will work for you, but if you went to http://apps.mios.com/plugin.php?id=3586 and pressed the Login button, you should be able to choose an older version of the plugin to install from there.
Title: Re: Plug-in for ecobee thermostats in development
Post by: tad on January 26, 2016, 08:14:04 am
So I have same problem with Luup reloading. Think there will be a fix? I really like my ecobee's
Title: Re: Plug-in for ecobee thermostats in development
Post by: catalystpt on January 26, 2016, 03:51:10 pm
I decided to try out the plug in today and I think I ran into the reloading loop issue mentioned above. Was about to give up when I noticed that the under the 'my apps' tab, when I selected additional information for the ecobee Thermostat app, that it said "Current Version 1.4" and "Latest Version 1.3"... "Auto Update" was also checked. I unchecked the "Auto update button" and the plug in started working for me and the loop stopped.

I haven't had a chance to to test further yet, but thought I'd post incase the info might be useful.

UI7 - Vera Lite

M
Title: Re: Plug-in for ecobee thermostats in development
Post by: klamath on January 26, 2016, 05:23:33 pm
I called on 1/25/16 and spoke to a customer care rep.  Gave him the ticket number listed in my email and was told "Devs are looking into the issue"  When asked if the ticket was assigned to anyone the answer was "unsure".  This might take a while.
Title: Re: Plug-in for ecobee thermostats in development
Post by: mda on January 26, 2016, 05:37:59 pm
If you email support you should have them link the issues, my ticket number is #155348.

Updating to 1.4 worked fine for me (Vera 3, UI5)

I spoke too soon. My vera has been rebooting 2-3 times in a row then luup restarting 2-3 times in a row every few hours. I had to restore to a backup with 1.3 and i will see if that is more stable.

It turns out my issue was unrelated (as i kept crashing after restoring a backup from prior to 1.4 installation). /sigh/
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 27, 2016, 04:11:47 am
It turns out my issue was unrelated (as i kept crashing after restoring a backup from prior to 1.4 installation). /sigh/

Does this mean that, with persistence, you were able to get past the problem installing 1.4?  I suspect the root cause is the same as it was last August with 1.3.  According to @mcvflorin (not sure he still works there?), there are two servers behind apps.mios.com, one had a problem, and it may be random chance that you get the "good" one or the "bad" one.  This is all only a guess, because I have zero visibility into their operations, but possibly repeated attempts to install 1.4 could work?
Title: Re: Plug-in for ecobee thermostats in development
Post by: mda on January 27, 2016, 11:27:55 am

Does this mean that, with persistence, you were able to get past the problem installing 1.4?

I think luck had more to do with it than persistence :)

On a second Vera 3 I was able to install 1.4 (I have not tried on my production Vera 3 again since reverting to backup... I need to get it stable first).

On the new Vera 3 (also ui5) I had the problem with installing 1.4 from the "install apps" function in ui5, but I was able to restore a backup and then I installed 1.4 from apps.mios.com and it worked.
Title: Re: Plug-in for ecobee thermostats in development
Post by: mda on January 31, 2016, 08:54:54 pm
If you email support you should have them link the issues, my ticket number is #155348.

I tried today to update my other Vera3 with v 1.3 of the ecobee plugin on it to v 1.4 and ran into this same luup restarting problem. I opened ticket #110171 with vera and cross-referenced you ticket # in mine. (i backed up user_data before trying so was able to revert back quickly).
Title: Re: Plug-in for ecobee thermostats in development
Post by: awesomo on February 01, 2016, 10:06:44 am
I've always marveled in fascination at the state of this vendor....  "Support after the sale," and all that....

I'd agree with support lacking. I really wish there was a paid priority option. I'm sure most of us would pay it happily.

BUT, at least the developers documentation is somewhat usable. SmartThings was a nightmare. First off, Groovy?! WHY?! Getting past that... I wanted one simple app to do a few simple things. Read through the documentation a few times, and not once did I come across the function I actually needed. I found it in a damn year old forum post. Vera is so much easier to develop things on so I am continuing to stick it through with them.
Title: Re: Plug-in for ecobee thermostats in development
Post by: meathead88 on February 02, 2016, 02:36:27 pm
I just got my ecobee3 installed and installed the ecobee plugin fresh and ran into this pluguin download loop issue.
v1.4 is what installed but the plugin page stated that v1.3 was the most recent.

I simply kept trying to uncheck automatic updates till it finally took now all is well on v1.4 with no looping.
Title: Re: Plug-in for ecobee thermostats in development
Post by: ando1 on February 03, 2016, 05:47:13 am
I was able to upgrade by unchecking the Auto Update setting like the others on this thread and everything seemed to be working fine last night. This morning I logged into my Vera and got the "Get PIN" message again.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 03, 2016, 06:28:42 am
I was able to upgrade by unchecking the Auto Update setting like the others on this thread and everything seemed to be working fine last night. This morning I logged into my Vera and got the "Get PIN" message again.

If you are really running v1.4 of the plugin, then either of two things has happened:

1) You encountered a bug in Vera, where the LuaUPnP process crashed before saving the most recent tokens.  Upon restart, since the Vera didn't really save the tokens persistently, the plugin was instead handed the stale tokens from persistent storage, which produced the "invalid_client" response from the Ecobee API.
2) There is a bug in the Ecobee API which occasionally returns "invalid_client" when it's not true.  I doubt this possibility.

If it's possibility #1 above, you will either have to find a way to stop the LuaUPnP process from crashing before it's saved device variables, or tell the Vera folks to save device variables in an exit hook before bombing out the LuaUPnP process.  Somewhere way back on this very long forum topic, there is discussion of this Vera issue.

I don't have the time or patience to find some wildly creative workaround for the situation where a saved device variable isn't always a saved device variable, but I do sympathize with any frustration you may have about it.  (OpenHAB doesn't have this issue, for what it's worth.)
Title: Re: Plug-in for ecobee thermostats in development
Post by: meathead88 on February 03, 2016, 08:26:17 am
watou, I just wanted to say "thank you" for the time you've spent on this plug in.

I'd have to say this plug in is extremely important to me as I'm a Windows uses exclusively and ecobee does not have a native app for Windows 10 PC/tablets or Phones.

You plug in lets me control my ecobee through the Windows 10 native Vera app.

Thank you so much!
Title: Re: Plug-in for ecobee thermostats in development
Post by: ando1 on February 03, 2016, 08:32:58 am
Thanks Watou,

At this point I am just ready to give up on the ecobee plugin and possibly the T-stats and just get some Z-Wave enabled T-stats and call it a day. Pretty much everything else on my Vera is solid and I had the FW locked down for a while. I just decided to upgrade a few days ago because I heard that the UI was more responsive. Don't get me wrong I am not frustrated at you, just the complexity of eveything which takes up valuable troubleshooting cycles trying to get the issues fixed.

I had looked at OpenHAB last year, but it very much seemed like an Alpha release product and it seems like much more of a learning curve for non-developer types. I am a hardware engineer by trade, not really skilled in programming but I know enough to get myself into trouble :-)

Thanks for all of your hard work on the plugin.

Andy
Title: Re: Plug-in for ecobee thermostats in development
Post by: meathead88 on February 03, 2016, 10:12:42 am
Set-up a new Vera edge for the first time today. I installed the Ecobee plugin flawlessly, but on the dashboard it was showing the thermostat device as a temperature setting of 0.0, even though it was reading the current temperature as 68. When I went over to the actual thermostat, it was indicating "45 and holding", which is obviously not the temperature it should be.

As of right now I uninstall the the app(s) because I didnt have time to de-bug it tonight. Any ideas what caused this? Anything I should have done differently?

The Ecobee plugin was designed for Vera's UI5 which supports a heat setpoint and a cool setpoint.  UI7 broke that, with the thinking "In UI7 heat and cool setpoints are replaced by only one generic setpoint like the real thermostat devices have."  While it's true from a UI standpoint that many thermostats show a single setpoint, in the underlying protocols they may have many setpoints, and which to show the user is a UI problem, not a plugin problem.  This is especially true when a thermostat is in "auto" or "heat-cool" mode, where the user can set a range of temperatures.

I had asked for documentation on how to allow the Ecobee plugin to work correctly in both UI5 and UI7, but it never appeared.  If it does appear, I will update the plugin so it works properly on both UI5 and UI7.  I own 3 Veras, one staying at UI5, even though I no longer rely on them.

I hope this sufficiently explains what you observed.

watou

I think this explains why my temp is not showing up where is should be in web page or apps.  Its a shame they won't get you that info.  I seemed to have developed a good relationship with a Vera support person.  I would be happy to query them for what you need.  If you describe what information you need, I will ask them for us.

Title: Re: Plug-in for ecobee thermostats in development
Post by: Sorin on February 04, 2016, 09:57:42 am
Hey Guys,

Upgrading from 1.3 to 1.4 and clean install of 1.4 from the store should not crash anymore.

There where some files that where not in sync with the apps servers that should be resolved now.

Don't hesitate to let us know if you still encounter any issues related to this topic.
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on February 04, 2016, 10:08:40 am
watou, I just wanted to say "thank you" for the time you've spent on this plug in.

I'd have to say this plug in is extremely important to me as I'm a Windows uses exclusively and ecobee does not have a native app for Windows 10 PC/tablets or Phones.

You plug in lets me control my ecobee through the Windows 10 native Vera app.

Thank you so much!

I love this plugin... but am still on UI5.

That said, there is a great modern Windows 10 app for the ecobee if you haven't tried it.
Title: Re: Plug-in for ecobee thermostats in development
Post by: klamath on February 05, 2016, 10:22:06 am
Turns out me trying to fix the problem many posts back prevented the 1.4 install, git clone src and copy into /etc/cmh-lu broke it, deleted the files in /etc/cmh-lu and works perfect now.

Tim

After working with mcv.johnm today this is the cause:

"01      02/05/16 9:09:53.136    LuaInterface::CallFunction_Startup-1 device 113 function init failed [string "..."]:117: attempt to index upvalue 'json' (a nil value) <0x76e31520>
01      02/05/16 9:09:53.137    LuImplementation::StartLua running startup code for 113 I_Ecobee1.xml failed <0x76e31520>


Note, that this is using of shelf files provided by this developer.

The previous which was crashing the engine was indeed related to our side, while this looks like something the developer of this plugin would be able to sort out.

You may want to take this to the developer."




Installs OK, but getting "ecobee[113] : Startup Lua Failed" now.




Hey Guys,

Upgrading from 1.3 to 1.4 and clean install of 1.4 from the store should not crash anymore.

There where some files that where not in sync with the apps servers that should be resolved now.

Don't hesitate to let us know if you still encounter any issues related to this topic.
[/s]
Title: Re: Plug-in for ecobee thermostats in development
Post by: jcolter on February 18, 2016, 02:09:02 pm
I had issues with the Ecobee pugin restarting a while back and uninstalled it.  I just reinstalled it yesterday after seeing there might be a fix.  However I am constantly getting  "ecobee : Not yet authorized. Press 'Get PIN' once; wait for PIN; enter at ecobee.com."  I have reauthorized twice already and it keeps coming back.  Any ideas?

Cheers,
Jeff
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 18, 2016, 02:18:34 pm
I also noticed today that both of my instances of the plugin had lost their tokens, which means that either 1) my Vera LuaUPnP process crashed and did not save the refreshed tokens, or 2) Ecobee is reporting invalid_client when it's not true.

Since there is a possibility that #2 above is true, I will make a v1.5 of the plugin that only differs from v1.4, in that it will take several consecutive reports of invalid_client before the plugin throws away the tokens.

v1.3 threw away tokens after repeated failures of any kind (like network problems).
v1.4 instead only throws away tokens if the Ecobee API explicitly reports invalid_client even once.
v1.5 will throw away tokens after repeated consecutive reports of invalid_client.

If that doesn't fix it, then the only remaining possibility is #1 above, which is not something I can fix.  If the Vera folks would persist device variables before the LuaUPnP process exits, then it can keep crashing but still not lose refreshed tokens.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 19, 2016, 09:48:55 am
I have just submitted v1.5 for approval.  It only differs from v1.4 in that it will take 5 consecutive "invalid_client" responses (once per poll attempt) before ultimately discarding the auth token, thereby requiring you to retrieve and enter a new PIN.  The only possible reasons for an "invalid_client" response to be returned 5 times consecutively are 1) there is a bug in the Ecobee API that falsely reports an invalid client repeatedly (this is extremely unlikely in my opinion), or 2) your LuaUPnP process crashed before it saved refreshed tokens persistently to the flash storage, so when it restarted, it tried to carry on with expired tokens. 

If you see this issue again, in my opinion it is much more likely to be #2 above, which can be corrected by either 1) find and fix the cause of your LuaUPnP process exiting abnormally, or 2) have Vera fix the case where a plugin saves a device variable (but really it wasn't written to disk in order to not wear out the flash memory), the LuaUPnP process crashes without first saving the device variables, and upon restart it tries to use the last saved tokens, which have already expired.  There is nothing I can do about #2 -- it's all on the Vera folks to provide reliable persistent storage to 3rd-party plugins' device variables, and I'm not going to move heaven and earth to work around it.

Please report if you see problems with v1.5.  If attempting to install it results in a similar freakout as mentioned earlier in this topic regarding v1.4, which was caused by server problems at the Vera end, please tell them!

All the best,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: kyb2012 on February 20, 2016, 01:43:25 pm
Hey Watou,
Given your extensive experience with both the Nest thermostat and the Ecobee (thanks for both the plugins), do you still prefer the Ecobee over the Nest?  Do the remote temp sensors work as well as you hoped?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 21, 2016, 09:11:08 am
Hey Watou,
Given your extensive experience with both the Nest thermostat and the Ecobee (thanks for both the plugins), do you still prefer the Ecobee over the Nest?  Do the remote temp sensors work as well as you hoped?

In my experience both are good products, but I prefer the capabilities of the ecobee3 over the Nest.  The remote sensors are a brilliant solution to uneven heating situations, where if the thermostat only knew the temperature of occupied rooms, not just where you had to mount the thermostat, its setpoint would have true meaning.  The ecobee3 solved this problem in a very clean and easy package.  It's also better if you use Apple mobile devices, since all but the initial batch of ecobee3's natively support HomeKit.  This is something that Nest is probably much less interested in ever doing, due to its parent company.  The API also gives temperatures to a tenth of a degree Fahrenheit and relative humidity to whole percentages, whereas Nest's official API only gives whole degrees Fahrenheit, and relative humidity rounded to 5%.  Lastly, Ecobee's entire business is thermostats, while Nest and parent company have many other priorities that may not result in the best thermostat. 

I don't mean to knock the Nest, but overall a fair comparison between them has the ecobee3 coming out ahead.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Vanlon on February 21, 2016, 01:41:10 pm
Just to add to that, I have a 3 Zone system and just changed out all my Nests for Ecobees.  The reason is that i installed a steam humidifier, makes no difference if it was bypass I guess.  The Nest does not adjust your humidity in relation to outside temperature for you, and the setting is buried 4 menu's deep, x 3 thermostats every time the outdoor temperature swings equals wet windows and frustration.  The Ecobee even factors in the efficiency of your windows when deciding your RH.  So if you want a thermostat to control your humidifier go with the Ecobee.

Thanks Watau for the awesome app.
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on February 22, 2016, 11:38:09 am
@watou,

I woke up this morning to my token needing to be refreshed.  I have auto-update on... I wonder if this happens after an update?

Although, if I look in the apps list, I does still show i'm on 1.4. 
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 22, 2016, 11:42:10 am
@watou,

I woke up this morning to my token needing to be refreshed.  I have auto-update on... I wonder if this happens after an update?

Although, if I look in the apps list, I does still show i'm on 1.4.

Thanks for the report. Tom.  Please upgrade to 1.5 after it's available and please report if it requires a new PIN unprompted after that.  Thanks, watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on February 22, 2016, 11:43:23 am
@watou,

I woke up this morning to my token needing to be refreshed.  I have auto-update on... I wonder if this happens after an update?

Although, if I look in the apps list, I does still show i'm on 1.4.

Thanks for the report. Tom.  Please upgrade to 1.5 after it's available and please report if it requires a new PIN unprompted after that.  Thanks, watou

Will do. can you remind me how to force the upgrade?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 23, 2016, 12:59:49 am
Will do. can you remind me how to force the upgrade?

I see that v1.5 is not yet approved.  After it is, you should be able to go to http://<your vera ip>:3480/data_request?id=update_plugin&Plugin=3586 (http://<your vera ip>:3480/data_request?id=update_plugin&Plugin=3586) to force an upgrade if needed.
Title: Re: Plug-in for ecobee thermostats in development
Post by: klamath on February 23, 2016, 08:26:09 am
1.5 is out, no upgrade issues.
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on February 23, 2016, 10:39:11 am
Same!  Thanks!!!!
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on February 23, 2016, 10:34:45 pm
Watou, I purchased a Vera edge pretty much based on the existence of your plugin :-)

As a newby, I also managed to navigate an EVL4 install and installation of alarm integration.  We have a larger install of 9 ecobee3 stats and am attempting to both increase efficiency, automate night cooling etc.

It would be about perfect if I could change the stat mode to sleep, or away when an alarm partition is armed.  I can't seem to be able to do it.  Am I missing a step?

Cheers, and thanks for your great work!
Dennis.
Title: Re: Plug-in for ecobee thermostats in development
Post by: klamath on February 24, 2016, 09:28:59 am
Asking for PIN this AM :(

1.5 is out, no upgrade issues.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 24, 2016, 09:59:26 am
It would be about perfect if I could change the stat mode to sleep, or away when an alarm partition is armed.  I can't seem to be able to do it.  Am I missing a step?

Hi Dennis,

Thanks for the kind words.  Do these instructions linked below not work?

http://forum.micasaverde.com/index.php/topic,13836.msg251114/topicseen.html#msg251114

So you have to be able to trigger on an alarm partition being armed, and then you have to call the Lua snippet referenced in the message above.  Instead of "smart6" (which is an example of a non-standard climate reference), you can use "sleep", "home", "away", or "wakeup", depending on your model's default set of climates.
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on February 24, 2016, 08:47:50 pm
Thanks Watou.  I have some reading to do on Lua snippets, but this gets me pointed in the right direction :-) I've got a Smartthings hub as well (different location) and I must say the ability to get under the hood if required, and local processing makes the Vera Edge my preference.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 26, 2016, 05:34:30 am
Further support to the notion that Vera can lose device variables from Richard:

This is Vera saving it's state in case it restarts because of a failure ...
In general Vera tries to save the current state before it restarts. Depending on the failure it might not be able to.

When vera reloads, it reverts to the last save point (within 6 min of the current time)

Failing to save new tokens is of course "fatal" to the Ecobee plugin, because once the process restarts and tries to use the now expired tokens, it has no option other than to give up and require a new PIN authorization.  If Vera were fixed to save device variables from memory to the flash disk in these situations, requiring a new PIN would go away as an issue.  The Ecobee API cycles tokens about once an hour, so if in the window between cycling tokens and the LuaUPnP process bombing out without having saved device variables, it's game over.

Title: Re: Plug-in for ecobee thermostats in development
Post by: klamath on February 26, 2016, 11:19:51 am
watou,

Would it be possible to expose a config param to write token data to USB or to onboard memory?  Assume the user understands the risk of wearing out device, would that help in this case?


Thanks,

Tim

Further support to the notion that Vera can lose device variables from Richard:

This is Vera saving it's state in case it restarts because of a failure ...
In general Vera tries to save the current state before it restarts. Depending on the failure it might not be able to.

When vera reloads, it reverts to the last save point (within 6 min of the current time)

Failing to save new tokens is of course "fatal" to the Ecobee plugin, because once the process restarts and tries to use the now expired tokens, it has no option other than to give up and require a new PIN authorization.  If Vera were fixed to save device variables from memory to the flash disk in these situations, requiring a new PIN would go away as an issue.  The Ecobee API cycles tokens about once an hour, so if in the window between cycling tokens and the LuaUPnP process bombing out without having saved device variables, it's game over.
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on February 26, 2016, 12:45:27 pm
1-the API supports calling a specific comfort setting, even custom ones
do you have any plans of adding this to the vera plugin

You can currently call the SetClimateHold action on the "house" device and pass it the name of climateRef.  A custom climateRef can be determined from the URL in the Ecobee web UI whiled editing the comfort setting; they are automatically generated and might look like "smart1" or "smart6", etc.  See SetClimateHold in http://watou.github.io/vera-ecobee/ for how to call it.  Example:

Code: [Select]
local service_id = "urn:ecobee-com:serviceId:Ecobee1"
local action = "SetClimateHold"
local args = { HoldClimateRef = "smart6" } -- the climateRef you want to switch to
local dev_num = 237 -- device number of the "house" device
luup.call_action(service_id, action, args, dev_num)

Watou, so I did manage to get scenes working in terms of setting "Away and Hold" in the Vera Edge GUI, and using the Ecobee ON/OFF devices for individual stats.  I ideally I would like to address particular stats (there are nine of them) and several partitions that may be armed/disarmed.  Given that the code above applies to the "House" device, does this mean I can still individually control the stats?  I'm not sure what the "House" device refers to.  Nothing shows up in the GUI as a House device...but I'm guessing this is a code reference?  Forgive the question as I'm a code newby...but I'm good if pointed in the right direction :-)  It's taken a bit as I'm starting from zero, however the alarm integration and stat setup is all working, and I've got working scenes :-)  We're planning more HVAC control with summer cooling etc, so I'll need to learn a fair bit yet.

I'm assuming that whatever is set in the code or otherwise is a "hold" action on the stats, and therefore the hold behaviour will be controlled by the stat preferences (2, 4 hours, until I change it, etc).  Correct?

Thanks again for your patience and assistance :-)  Dennis.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 26, 2016, 06:04:36 pm
Given that the code above applies to the "House" device, does this mean I can still individually control the stats?

For each Ecobee thermostat, the plugin creates a thermostat, humidistat and house device.  The 2nd, 3rd and 4th devices in the screen grab here: https://watou.github.io/vera-ecobee/ show them in UI5.  The look different in UI7, of course, but they are there.  So for each of your actual 9 thermostats, each has a "house" device which you can address via its numeric device ID (like 237 in the example above).

I'm assuming that whatever is set in the code or otherwise is a "hold" action on the stats, and therefore the hold behaviour will be controlled by the stat preferences (2, 4 hours, until I change it, etc).  Correct?

No; those holds are set indefinitely, but you can change it.  This line in the source code for I_Ecobee1.xml:

https://github.com/watou/vera-ecobee/blob/master/src/I_Ecobee1.xml#L855

is set to create an indefinite climate hold.  You could change the source to any of the other hold types, as described here:

https://www.ecobee.com/home/developer/api/documentation/v1/functions/SetHold.shtml

You would then upload your changed I_Ecobee1.xml back to your Vera for it to take effect.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 26, 2016, 06:10:41 pm
Would it be possible to expose a config param to write token data to USB or to onboard memory?  Assume the user understands the risk of wearing out device, would that help in this case?

Yes, it's possible, but I'm going to wait for Vera to fix their device variable storage problem.  You could implement your own workaround if you wanted by changing the loadSession and saveSession local functions in the code here:

https://github.com/watou/vera-ecobee/blob/master/src/I_Ecobee1.xml#L410

Apparently the device variable storage problem is affecting PLEG and other plugins as well, so Vera had really better fix it.  And writing the tokens "manually" to any location, built-in flash or external USB, is unlikely to contribute to wearing out the media, as it only happens about once an hour.
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on February 27, 2016, 03:04:34 pm
Thanks Watou.  I did a bit of googling and figured out to download/edit and upload a plugin xml file :-)  Setting it to "nextTransition" worked exactly as desired.
Your links to the line of code and to the allowable parameters made it about as easy as pie.

Cheers,
Dennis
Title: Re: Plug-in for ecobee thermostats in development
Post by: Smoochies Boss on February 28, 2016, 04:48:36 pm
Watou, have you gotten any feedback from Vera about UI7 and them fixing the issues with it so your plugins work?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 29, 2016, 01:16:04 pm
Watou, have you gotten any feedback from Vera about UI7 and them fixing the issues with it so your plugins work?
No, but I'm not personally pursuing the answers.  I had invested a lot of effort into that some 1 1/2 years ago, but the Vera person disengaged and I moved on.
Title: Re: Plug-in for ecobee thermostats in development
Post by: MLeBaugh on February 29, 2016, 02:39:58 pm

No; those holds are set indefinitely, but you can change it.  This line in the source code for I_Ecobee1.xml:

https://github.com/watou/vera-ecobee/blob/master/src/I_Ecobee1.xml#L855

is set to create an indefinite climate hold.  You could change the source to any of the other hold types, as described here:

https://www.ecobee.com/home/developer/api/documentation/v1/functions/SetHold.shtml

You would then upload your changed I_Ecobee1.xml back to your Vera for it to take effect.

Watou,
This question has come up a few times in this forum on how to change this. Perhaps you can add a selection/variable for it on the default device. Default Home/Away: indefinite/nextTransition/holdHours. Set that as a variable and such and get it in the setClimateHold fuction.

Thanks so much for this plugin btw it's great!
Title: Re: Plug-in for ecobee thermostats in development
Post by: dzmiller on February 29, 2016, 02:48:18 pm

No, but I'm not personally pursuing the answers.  I had invested a lot of effort into that some 1 1/2 years ago, but the Vera person disengaged and I moved on.

Thanks for trying. I bought a veraplus and upgrade to UI7 just assuming that OF COURSE Ecobee would work. I'm disappointed that VEra has not supported your effort.
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on February 29, 2016, 11:26:00 pm
Watou, I've read through this entire thread before asking any more questions :-)   I'm trying to figure out two more control items:

1.  Resuming the program

I've created a scene using one of the thermostats, and added in this code:

Code: [Select]
local service_id = "urn:ecobee-com:serviceId:Ecobee1"
local action = "ResumeProgram"
local args = { }
local dev_num = 237
luup.call_action(service_id, action, args, dev_num)

The Ecobee API adds: "If resumeAll parameter set to true, the function resumes all events and returns the thermostat to its program. "  Rather than resuming the program on this stat, it creates a hold using the lowest  heat temp set in preferences, in this case 7C.  It's entirely possible I've got the code wrong..just not sure.  Can the resumeAll parameter be added to the above code?

2.  Is there code I can use to execute a fan hold?  I just want to turn on fans on the 5 air handlers when managing night cooling via the building ventilator.  The building HRV will feed the air handlers cool night air, so I'd like to turn their fans on and off when Vera is running night cooling scenes.
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on March 01, 2016, 05:08:28 pm
I also tried this code, but it does not resume the program..again it puts the stat into a hold with the lowest temp set in Heat preferences.

Code: [Select]
local service_id = "urn:ecobee-com:serviceId:Ecobee1"
local action = "ResumeProgram"
local args = {resumeAll="true"}
local dev_num = 237
luup.call_action(service_id, action, args, dev_num)
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 01, 2016, 05:21:25 pm
I also tried this code, but it does not resume the program..again it puts the stat into a hold with the lowest temp set in Heat preferences.

Code: [Select]
local service_id = "urn:ecobee-com:serviceId:Ecobee1"
local action = "ResumeProgram"
local args = {resumeAll="true"}
local dev_num = 237
luup.call_action(service_id, action, args, dev_num)

Calling the action ought to invoke this code:

https://github.com/watou/vera-ecobee/blob/master/src/I_Ecobee1.xml#L1169

The Ecobee API docs used to say that sending the "resumeProgram" function 3 times clears all holds, but they changed the doc to instead take the resumeAll parameter.  I don't know if they changed it, but you could test by pressing the Resume button in the UI, which invokes the same action. 

https://github.com/watou/vera-ecobee/blob/master/src/D_EcobeeThermostat1.json#L406

Does pressing the Resume button lead to the same strange heat setpoint setting?
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on March 01, 2016, 11:05:53 pm
Thanks again for your help Watou...it's very much appreciated.

Yes, selecting "Resume" as well as toggling Fan mode on/off work exactly in the GUI as I'd like to have them work in the scenes.  Can you provide a code example of where and how I would call these actions? 

Edit: Ok, I figured out how to call the action by adding the thermostat object to the scene, accessing the advanced editor, and adding the resume program action.   Works perfectly :-)

So that leaves one final question..how would I toggle fan mode between Auto/on in a scene?

Cheers,
Dennis.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 02, 2016, 04:22:46 am
So that leaves one final question..how would I toggle fan mode between Auto/on in a scene?

Try something like:

Code: [Select]
local service_id = "urn:upnp-org:serviceId:HVAC_FanOperatingMode1"
local action = "SetMode"
local args = {NewMode="ContinuousOn"} -- or "Auto"
local dev_num = 237 -- your thermostat device ID
luup.call_action(service_id, action, args, dev_num)

This sets an indefinite hold with the fan mode set to auto or on.
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on March 02, 2016, 11:34:57 am
Watou, thanks so much.  My problem was a rookie error as I assumed in the previous sample code that ID 237 was an Ecobee identifier...which in fact is your own Ecobee device stat.  Here's a summary of the changes/code I used for anyone else with similar questions.   First, I used this prodecure to list all the Vera device IDs, and save them for future reference/upgrades/disaster recovery.

http://www.vesternet.com/resources/application-notes/apnt-43#.VtcUZ5wrIuU

Then I confirmed that the code below works correctly :-)

This resumes the thermostat to whatever was scheduled:

Code: [Select]
local service_id = "urn:ecobee-com:serviceId:Ecobee1"
local action = "ResumeProgram"
local args = {resumeAll="true"}
local dev_num = 68 -- Our Ecobee R&D Thermostat Device ID
luup.call_action(service_id, action, args, dev_num)

And this code toggles the fan mode.  I was trying to use "on" instead of "ContinuousOn"

Code: [Select]
local service_id = "urn:upnp-org:serviceId:HVAC_FanOperatingMode1"
local action = "SetMode"
local args = {NewMode="ContinuousOn"} -- or "Auto"
local dev_num = 060 -- Our Ecobee R&D Thermostat Device ID
luup.call_action(service_id, action, args, dev_num)

This code will set whatever climate hold type is desired

Code: [Select]
local service_id = "urn:ecobee-com:serviceId:Ecobee1"
local action = "SetClimateHold"
local args = { HoldClimateRef = "Away" } -- the climateRef you want to switch to
local dev_num = 060 -- Our Ecobee R&D Thermostat Device ID
luup.call_action(service_id, action, args, dev_num)


I also used the VERA control panel APPS -> Develop Apps -> Luup Files to download, modify and upload I_Ecobee1.xml with two changes:

This line as you linked: https://github.com/watou/vera-ecobee/blob/master/src/I_Ecobee1.xml#L855 so that "indefinite" is changed to "nextTransition" so any climate holds are only in effect until the next scheduled event.

And this line: https://github.com/watou/vera-ecobee/blob/master/src/I_Ecobee1.xml#L1148 so that "indefinite" is changed to "nextTransition" so any fan holds are only in effect until the next scheduled event.

I also learned that to switch climate modes on the Ecobee3 in a Scene, you can add the thermostat On/Off switches to the Device list in a scene, than in "Step 3: Finish the Scene" click on the Avanced Editor and manually enter home or away or sleep.  Any custom climates could be entered here as well, providing you edit them from Ecobee's web interface and note their name (smart1 or similar) from the URL.

Watou, this is exactly why I decided to go with the Vera Edge after setting up the Ecobee stats.  Community support and the ability to get under the hood a bit :-)  I probably learned a bit more than intended about the Ecobee API and LUA code, but this is a good thing.

Cheers,
Dennis.

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on March 07, 2016, 04:03:45 pm

No; those holds are set indefinitely, but you can change it.  This line in the source code for I_Ecobee1.xml:

https://github.com/watou/vera-ecobee/blob/master/src/I_Ecobee1.xml#L855

is set to create an indefinite climate hold.  You could change the source to any of the other hold types, as described here:

https://www.ecobee.com/home/developer/api/documentation/v1/functions/SetHold.shtml

You would then upload your changed I_Ecobee1.xml back to your Vera for it to take effect.

Watou,
This question has come up a few times in this forum on how to change this. Perhaps you can add a selection/variable for it on the default device. Default Home/Away: indefinite/nextTransition/holdHours. Set that as a variable and such and get it in the setClimateHold fuction.

Thanks so much for this plugin btw it's great!

i would also like this
as i need to modify the file everytime there is a new app update
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on March 07, 2016, 04:10:16 pm

No, but I'm not personally pursuing the answers.  I had invested a lot of effort into that some 1 1/2 years ago, but the Vera person disengaged and I moved on.

Thanks for trying. I bought a veraplus and upgrade to UI7 just assuming that OF COURSE Ecobee would work. I'm disappointed that VEra has not supported your effort.

i have been using the plugin succesfully on ui7 on my veralite, and now on veraplus
the only issue is the display of the set temp as there is only one and not a heat and a cool in ui7

otherwise it works perfectly
it can still be controlled
you can still set it
it can be set in scenes


i also use it with wdsc (window door and sensor controller)
if outside doors or windows are open the hvac is shut off
when all are closed hvac is put back on in auto
if outside temp is above X i set to cool only
if outside temp is below X i set to heat only

Title: Re: Plug-in for ecobee thermostats in development
Post by: djrobx on March 10, 2016, 12:03:22 am
Just want to throw in a "me too" with the "Get PIN" issue.  I'm on UI5.   

I switched from a Nest to the Ecobee and this thing keeps letting me down.   The remote sensors have crap for range, the occupancy sensors suck (they regularly miss me walking 1 foot in front of them, including the built in one!), the build quality isn't as good.   And now my Vera integration is flaky despite a proper third party API.   
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on March 10, 2016, 12:54:43 am
Just want to throw in a "me too" with the "Get PIN" issue.  I'm on UI5.   

I switched from a Nest to the Ecobee and this thing keeps letting me down.   The remote sensors have crap for range, the occupancy sensors suck (they regularly miss me walking 1 foot in front of them, including the built in one!), the build quality isn't as good.   And now my Vera integration is flaky despite a proper third party API.

Hey there.... I don't know if it will help, but this is a great forum specifically for the Ecobee
http://www.smarthomehub.net/forums/categories/ecobee

I've had mine for a year, and am pretty happy with it.  No issues with build quality.  I will say the sensors sometimes have problems - often with firmware updates (sometimes good, sometimes bad).  That said, I have 5 in my house (3800 square feet) and all are working perfectly right now. 

Also, see on that forum they had some build issues on the sensors were the front cover was put on upside down from manufacturing, and the window was not over the sensor.  Something to check - easy to fix.

As for not seeing you... you might read up on how they work in case you haven't. They are not supposed to register motion right away (I think), but over time to decide if to use the temp from that sensor as an average in your settings.  So, for example, if you have "follow me" on, and you just happen to walk into a room for a minute, you don't necessarily want it to use that sensor right away.  I'm probably not describing it really well... but that's the gist.  That's why you wouldn't want to try to use them for motion activated scenes in Vera.

Anyway... hope that helps!
Title: Re: Plug-in for ecobee thermostats in development
Post by: ShawnParr on March 10, 2016, 07:58:20 am
Watou,
This question has come up a few times in this forum on how to change this. Perhaps you can add a selection/variable for it on the default device. Default Home/Away: indefinite/nextTransition/holdHours. Set that as a variable and such and get it in the setClimateHold fuction.

Thanks so much for this plugin btw it's great!

i would also like this
as i need to modify the file everytime there is a new app update

I'd like to add a me too! I added the plugin but haven't started automating with it yet. I'm glad a ran across this as I'd want to use "nextTransition" for most of my scenes. Most of what I want out of integration with the Ecobee is to make the "smart away" function more responsive, so it behaves more like my old Nest and goes "away" after maybe 1/2 hour instead of the 2 hours Ecobee uses.

Thanks for the plugin!
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 10, 2016, 08:50:27 am
If I added a holdType variable to the thermostat device, you could set it to either indefinite (the default) or nextTransition.  To support the other hold types, dateTime or holdHours, I would have to add 1-5 more variables, which is a little unwieldy.  Would just adding the ability to hold until nextTransition be enough to solve actual needs?

Title: Re: Plug-in for ecobee thermostats in development
Post by: ShawnParr on March 10, 2016, 09:01:10 am
If I added a holdType variable to the thermostat device, you could set it to either indefinite (the default) or nextTransition.  To support the other hold types, dateTime or holdHours, I would have to add 1-5 more variables, which is a little unwieldy.  Would just adding the ability to hold until nextTransition be enough to solve actual needs?

I can't speak for others, but nextTransition is what would currently be most useful for me. Taking a quick look at the API documentation it looks like if you also added holdHours it should use the number of hours specified in the EcoBee preferences for the parameter.

So IMHO it would be nice to add a variable with the ability to choose between indefinite, nextTransition, and holdHours in the next update or so. I'm sure eventually someone will come along that would appreciate the dateTime feature, but since that requires the extra parameters it can be back burnered for a while.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 10, 2016, 09:26:51 am
if you also added holdHours it should use the number of hours specified in the EcoBee preferences for the parameter.

My reading of the API docs says that the holdHours parameter is "required if holdType='holdHours'," so that would require a parameter.  So if adding the ability to specify nextTransition for a new holdType device variable is sufficient, I can provide an updated I_Ecobee1.xml file here to test, and if it works, I will include it v1.6.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 10, 2016, 10:06:31 am
The attached replacement file for I_Ecobee1.xml ought to create a new device variable for each Ecobee thermostat device shortly after installation of this file.  It will probably restart the Luup engine at that point, after which you should refresh your browser.  You can then change its default value indefinite to nextTransition.  Every hold performed against that thermostat going forward would then be resumed automatically on the next schedule transition.

Please report if this test file works or doesn't work to fulfill the actual need.  If it's all clear, I will include in v1.6.

UPDATE: new file attached.
Title: Re: Plug-in for ecobee thermostats in development
Post by: ShawnParr on March 10, 2016, 11:37:48 am
I installed, restarted LUUP, and refreshed browser. Regular function of plugin doesn't work now.

I think there may be an issue:

Code: [Select]
08 03/10/16 10:35:49.134 JobHandler_LuaUPnP::HandleActionRequest device: 48 service: urn:ecobee-com:serviceId:Ecobee1 action: SetClimateHold <0x7412a520>
08 03/10/16 10:35:49.134 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=48 <0x7412a520>
08 03/10/16 10:35:49.134 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:ecobee-com:serviceId:Ecobee1 <0x7412a520>
08 03/10/16 10:35:49.135 JobHandler_LuaUPnP::HandleActionRequest argument action=SetClimateHold <0x7412a520>
08 03/10/16 10:35:49.135 JobHandler_LuaUPnP::HandleActionRequest argument HoldClimateRef=away <0x7412a520>
01 03/10/16 10:35:49.136 LuaInterface::CallFunction_Job device 48 function SEcobee1_Ecobee1_SetClimateHold_run failed [string "..."]:805: attempt to index global 'funs' (a nil value) <0x7412a520>
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 10, 2016, 01:27:20 pm
Geez, sorry about that.  I've replaced the I_Ecobee1.xml file attached to my previous message.
Title: Re: Plug-in for ecobee thermostats in development
Post by: ShawnParr on March 10, 2016, 02:09:31 pm
Geez, sorry about that.  I've replaced the I_Ecobee1.xml file attached to my previous message.

That one seems to work. For some reason it took me a few refreshes before I saw the variable, but it is there now.

I did the following:


For me it is perfect. Thanks!
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 10, 2016, 02:24:24 pm
Thanks, Shawn!  This will be in v1.6.
Title: Ecobee setpoint on UI7 (please test)
Post by: watou on March 12, 2016, 08:58:50 am
Hi, I've made an attempt at having the current thermostat mode's setpoint appear and function in UI7.  In Auto mode, the single UI7 setpoint is the average of the heat and cool setpoints.

Please help me test this change (to make sure it doesn't break UI5, and that it works as well as possible on UI7).  Just replace the attached files, restart Luup and refresh the browser.
Title: Re: Ecobee setpoint on UI7 (please test)
Post by: ShawnParr on March 12, 2016, 01:21:44 pm
Hi, I've made an attempt at having the current thermostat mode's setpoint appear and function in UI7.  In Auto mode, the single UI7 setpoint is the average of the heat and cool setpoints.

Please help me test this change (to make sure it doesn't break UI5, and that it works as well as possible on UI7).  Just replace the attached files, restart Luup and refresh the browser.

So far so good under UI7. Instead of showing 0 all the time it shows my set point properly.

I'll mention that it throws me off a bit, as the set point is large and centered, with the current temperature off to the side smaller. I realize that is probably consistent with other HVAC systems and/or plugins. However, in the Ecobee interface on the site and on the thermostat itself they are the opposite, at least on the Ecobee 3. The large central number is the current temperature, and the smaller side number is the set point.

I'm not saying to change it or anything, just that it isn't immediately intuitive to me since it is different from the Ecobee interface.
Title: Re: Ecobee setpoint on UI7 (please test)
Post by: watou on March 13, 2016, 04:00:06 am
I'll mention that it throws me off a bit, as the set point is large and centered, with the current temperature off to the side smaller. I realize that is probably consistent with other HVAC systems and/or plugins. However, in the Ecobee interface on the site and on the thermostat itself they are the opposite, at least on the Ecobee 3. The large central number is the current temperature, and the smaller side number is the set point.

I'm not saying to change it or anything, just that it isn't immediately intuitive to me since it is different from the Ecobee interface.

Thanks for mentioning this, even though it's not something that's under the control of the plugin developer.  A small list of UI things was possible under UI5, and an even smaller list under UI7 (not complaining, just observing).

Please report any problems you see.  I hope to submit v1.6 in about a week, after there is a good chance for more feedback.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on March 14, 2016, 03:44:27 pm
i have tried these new files to test 1.6
followed the steps required
my app kept displaying as 1.4
however was not set up to auto update
changed to autoupdate and clicked update
app updated top 1.5

uploaded the 1.6 files
still shows only 1.5
even after luup reload and a reboot

downloaded the i_ecobee1.xml file that is on the vera
open up the file
it clearly is the 1.6 file as per version info and holdtype variable in the file

re-uploaded the file
still only showing 1.5 and parameter not found

also should the new variable be present on the main device where you get the token
or the thermostat control device
i have looked in both and still do not see the variable
i had a similar issue when you added the precision scale
the variable had to be added manually

i have now restored yesterdays backup
manually upgraded to 1.5
rebooted
re-applied the 2 new files
i can confirm that even though it says 1.5
it is running 1.6 as the auto temp is averaged as you mentioned
however i still dont have the new "holdType" variable parameter

can you assist with what i should try next?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 16, 2016, 03:56:15 am
uploaded the 1.6 files
still shows only 1.5
even after luup reload and a reboot

downloaded the i_ecobee1.xml file that is on the vera
open up the file
it clearly is the 1.6 file as per version info and holdtype variable in the file

re-uploaded the file
still only showing 1.5 and parameter not found

also should the new variable be present on the main device where you get the token
or the thermostat control device
i have looked in both and still do not see the variable
i had a similar issue when you added the precision scale
the variable had to be added manually

i have now restored yesterdays backup
manually upgraded to 1.5
rebooted
re-applied the 2 new files
i can confirm that even though it says 1.5
it is running 1.6 as the auto temp is averaged as you mentioned
however i still dont have the new "holdType" variable parameter

can you assist with what i should try next?

The plugin will still be listed as v1.5 as that was installed from apps.mios.com.  However the log should say plugin 1.6 is started after applying the patch files.  The holdType device variable is on the thermostat device, so you can set it differently for different thermostats.  You might need to refresh your browser and look under the thermostat device's Advanced tab for variables.  The default value indefinite should appear there, and you can replace it with nextTransition.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on March 16, 2016, 12:10:37 pm
i have refreshed the page f5
force refreshed the page ctrl + f5
reloaded luup
and rebooted the vera

this has happened to me before
with plugins that were uploaded manually
where some new variable are not getting added

the new variable parameter "holdtype" is still not there
how can i add it manually in that device under new service

i know the variable is "holdType"
and the value for me would be "nextTransition"
but what is the service?
urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1
would this be correct

also not sure if it matters
but i have the new vera plus
but have had similar issues on vera lite in the past
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 18, 2016, 02:22:00 am
The holdType variable ought to appear in the list of variables for the thermostat device (see screen capture attached).  Its service ID is urn:ecobee-com:serviceId:Ecobee1.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on March 18, 2016, 08:50:36 am
my thermostat display device is
urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1

the main device device is
urn:schemas-ecobee-com:device:Ecobee:1

the home/away device is
urn:schemas-ecobee-com:device:EcobeeHouse:1

none of them contain the new variable
i know it appears to be in the thermostat device in your screen shot
i can assure you i dont have it
i have attach a screenshot


i can also assure you i have the new files in place
the temp averaging is working in auto mode

as i said before
this has happened to me before on manual loading of files/ manual update of app
new variables just dont show up
i need to add them manually by clicking on add service on the correct device and specify the correct service


can you please confirm that the below is correct?

on thermostat display device
urn:schemas-upnp-org:device:HVAC_ZoneThermostat:1
go to advanced, new service

there are 3 fields
new service, new variable, new value

service: ecobee-com:serviceId:Ecobee1
variable: holdType
value: nextTransition

i want to make sure its correct before i add it as there is no option to remove variable
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 18, 2016, 09:20:32 am
The service/variable/value you give should work on the Ecobee thermostat device.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on March 18, 2016, 10:59:16 am
i have tried creating this variable
unfortunately it is not observed by the app
it still runs indefinite

so what i did was open up the i_ecobee1.xml file
and i changed the default value in the 3 locations from indefinite to nexttransition
i then uploaded the file and reloaded luup
thinking that even though i wont see it
at least the value will be correct

what ended up happening
is that it created a second variable called holdType
but the value in it was indefinite instead of the nextTransition that i put inthe file
from this it was still running indefinite
i set it to nextTransition
its now working as expected
but i have 2 of the same variable and dont know which is which
so i resored backup from yesterday
and re uploaded the modified xml
still no variable
however it is running with next transition

it only seems to creates the variable after a manual one is created but leaves me with a duplicate and only one working
this is very weird

so for now i have no variable but runing next transition as i modified the default value in the xml
and confirmed that it is running with next transition parameter

any thought?
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on March 18, 2016, 11:26:21 am
***update***

it occured to me that the simple action of creting a variable seems to make it show up
so I created a fake variable called zztest
immediatly the holdType variable showed up and its working

as a test I plugged in my veralite
uploaded the original 1.6 files you provided
it worked right away

this must be a "display" bug in the new vera firmware for the vera plus

it may be worth noting that people with a vera plus wont see the new variable until they create a "dummy" variable
or until the bug is resolved by vera
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on March 22, 2016, 03:03:22 pm
Watou, does the indefinite to nexttransition variable just affect temperature/climate changes?  I've changed the value in  i_ecobee1.xml file to also make fan mode changes until "nexttransition".  My assumption is that I'd still need that tweak?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 22, 2016, 07:14:11 pm
Watou, does the indefinite to nexttransition variable just affect temperature/climate changes?  I've changed the value in  i_ecobee1.xml file to also make fan mode changes until "nexttransition".  My assumption is that I'd still need that tweak?

All holds that the plugin requests go through the same code path, so each thermostat's own holdType device variable governs all holds to it -- temperature, climate or fan.

An aside: It's important to spell the holdType variable's content exactly as either immediate or nextTransition to agree with the API documentation.
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on March 27, 2016, 01:05:23 pm
Thanks Watou..this is good news.  I'll give the code a try.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Zoro on March 27, 2016, 02:02:36 pm
Thanks Watou..this is good news.  I'll give the code a try.

Denwood

   Please let us know howit goes. Thnks

Z
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on March 27, 2016, 02:33:48 pm
I had a very similar experience to charettepa .  I had to add the variable manually as indicated by charettepa, but it was not being parsed by the code as the stat was still using "indefinite" holds.  I figured I'd try editing the new I_ecobee file and changed "indefinite" to "nextTransition" as below:

Line 236 ["holdType"] = function(t) return "nextTransition" end,

Line 843 func.params.holdType = readVariableOrInit(lul_device, ECOBEE_SID, "holdType", "nextTransition")

After saving/reloading LUUP, I had an extra (duplicate) HoldType variable appear on the one Ecobee3 stat I was testing.  I changed that duplicate variable to nextTransition and everything worked as expected on that particular  thermostat.  This is good.

Unfortunately, the same behaviour was not evident on the other 8 Ecobee3 stats I have installed in Vera and there was no way I could get these stats to work with "nextTransition", or even force a duplicate variable to appear.  I restarted Luup and refreshed my browser after each change.  I also tried a different browser to make sure it wasn't a weird GUI issue.

Because I have several scenes/virtual switches etc. working with the nine stats, I had to restore the Vera from backup and grab a new PIN so the stats would work with the scenes etc. I have created.

On the plus side, all nine stats correctly displayed actual and set temps as expected.  The one working Ecobee3 instance correctly changed temps/climate and fan mode using the nextTransition behaviour after the duplicate variable was edited to "nextTransition".

Thanks again Watou for your efforts :-)
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 28, 2016, 06:06:09 am
The latest I_Ecobee1.xml before this message had the problem that, for thermostat devices that had already been discovered and created in the Vera, the "holdType" device variable was not being created until you actually went to perform a hold.  At that point, the device variable would be created with its default value of "indefinite".

With the attached version of the file, the plugin should create the "holdType" variable for each discovered thermostat device on the next poll of the device where the thermostat has reported some change.  This can take up to 15 minutes, but may happen after the next poll, which is usually only 3 minutes or less away.

Please replace your I_Ecobee1.xml file with the one attached, and please let me know if it does or doesn't perform as described.

Thanks,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: PromptCritical on March 28, 2016, 02:06:17 pm
This may be a dumb question, but I'm considering an Ecobee 3 to replace my Honeywell stat because my house has pretty uneven heating and I thought it might help.  I'll read the whole thread if I get one.

Does this plugin directly communicate with the Ecobee over my network or is everything routed through Ecobee servers? 
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on March 28, 2016, 04:57:03 pm
Prompt, all communication with Ecobee stats is via their web api.  So this plugin talks to the Ecobee web server, which talks to your stats.  It's quite transparent.

Watou, do I need both the D_EcobeeThermostat1.xml you posted on March 12th, as well as the updated I_Ecobee1.xml ?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 28, 2016, 04:59:28 pm
Watou, do I need both the D_EcobeeThermostat1.xml you posted on March 12th, as well as the updated I_Ecobee1.xml ?

Yes, you would need both the latest I_Ecobee1.xml and the earlier D_EcobeeThermostat1.xml files.
Title: Re: Plug-in for ecobee thermostats in development
Post by: PromptCritical on March 28, 2016, 05:07:53 pm
Prompt, all communication with Ecobee stats is via their web api.  So this plugin talks to the Ecobee web server, which talks to your stats.  It's quite transparent.

Watou, do I need both the D_EcobeeThermostat1.xml you posted on March 12th, as well as the updated I_Ecobee1.xml ?

Thanks for clarifying.  I am now reconsidering my purchase because I see zero justification that data and commands should have to travel to a distant server and back so two boxes located within the same building can talk to one another.  I find it to be technologically equivalent to calling my mom and asking if I can eat a cookie.  This trend where everything is being required to use a web API boggles my mind. 
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 28, 2016, 05:30:48 pm
Thanks for clarifying.  I am now reconsidering my purchase because I see zero justification that data and commands should have to travel to a distant server and back so two boxes located within the same building can talk to one another.  I find it to be technologically equivalent to calling my mom and asking if I can eat a cookie.  This trend where everything is being required to use a web API boggles my mind.
Reasons I can think of for not wanting a thermostat that uses a cloud API for remote control:
- Your Internet connection is historically unreliable and you can't fix it.
- You believe that the specific company that is providing the cloud API has an unacceptable reputation for API reliability.
- You believe that the specific company that is providing the cloud API will use your telemetry or private data in unapproved ways.

In years of remotely controlling my Nest and Ecobee, none of the above has applied to me.

Reasons I can think of for wanting a thermostat that uses a cloud API for remote control:
- You want remote access outside your private network and don't want to set up and maintain a secure path into it.
- You want additional information and features that can not be completely onboarded onto the thermostat device or one of your local servers.
- You want the API provider to dedicate resources to constant availability, instead of having to maintain operational oversight yourself.

In my experience, I have found all of the above useful.
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on March 28, 2016, 05:50:16 pm
Prompt, keep in mind that the stat does not require a web connection at all to run its schedules etc. so if web is down, no worries.  I also have our the stats programmed with the Home/Away and Follow options, so even if Vera fails completely, the stats will go into Home, Away and Sleep modes just fine with no web connection. I think it's the best of both worlds as the web API makes remote monitoring a lot simpler  Your smartphone doesn't need to traverse your home router connection.  We do use a VPN, but most consumers would have issues with this.  One of the reasons I specifically chose Vera is because it does all of it's processing locally, so yes it would nice if the stats could be managed this way too.  You can also get a "dumb" zwave stat like the 2Gig, but most of these stats don't work correctly if the hub fails or loses connection for some reason.

Watou, the files worked perfectly.  Here's what I did:

1. Uploaded the two files and bumped each of the nine stats to prompt a poll..waited about 5 minutes.
2. Cleared Browser cache and checked for the HoldType variable.  It was there.
3. Changed each variable to "nextTransition", hit Back button, Save Changes button, reloaded LUUP.

Vera UI7 is pretty flakey when it comes to changing variables so I went back and checked each stat and redid a few.

All nine stats display correctly, and I tested a few Scenes etc. to make sure fan, temp and climate holds were working with "nextTransition".  All good.

Thanks so much for the help :-)
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 29, 2016, 07:43:37 am
@denwood, that's great news!  I will submit v1.6 to the app store in a few days with these latest changes.
Title: Re: Plug-in for ecobee thermostats in development
Post by: PromptCritical on March 29, 2016, 12:57:06 pm
Reasons I can think of for not wanting a thermostat that uses a cloud API for remote control:
- Your Internet connection is historically unreliable and you can't fix it.
- You believe that the specific company that is providing the cloud API has an unacceptable reputation for API reliability.
- You believe that the specific company that is providing the cloud API will use your telemetry or private data in unapproved ways.

In years of remotely controlling my Nest and Ecobee, none of the above has applied to me

I don't have any issues with any of that.

Quote

Reasons I can think of for wanting a thermostat that uses a cloud API for remote control:
- You want remote access outside your private network and don't want to set up and maintain a secure path into it.
- You want additional information and features that can not be completely onboarded onto the thermostat device or one of your local servers.
- You want the API provider to dedicate resources to constant availability, instead of having to maintain operational oversight yourself.

In my experience, I have found all of the above useful.

I get that remote access and outside data require internet access.  My problem is that the API treats any device connected to the stat as "remote access", even if the device is fixed to the same network.  Vera seems to work alright: If I connect via my computer at home, it redirects me to a direct IP connection to the box, but if I'm away, it connects through the web API.  Unless I look at the address in my browser, I don't know the difference.  Maybe I'm just making a huge stink about nothing.  It's not like it's the garage door opener where every open/shut command appears to go through the GoControl server.

What is the point of all the different modes?  I feel like I'm missing something.  The basic gist of the system is that it has "Follow Me" and Smart Home/Away modes.  Shouldn't that be all I want?  But is also has a home/away schedule.  Why is that needed?  I can exclude sensors from Follow Me.  Why would I want to do that?

Finally, can the smart home/away mode be used to trigger the home and away modes on Vera?  That would be nice.
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on April 01, 2016, 12:57:50 pm
There is a lot of product specific information here...and you'll get better answers if you ask questions there  :-)

http://www.smarthomehub.net/forums/categories/ecobee

Smart Home/Away: if enabled, Ecobee stat uses motion detection on the stat and all remote sensors to put the stat in home mode, or turn it down a few degrees (not the same as Away!). It delays "Away" mode as much as two hours after last motion detected if in "Home" mode.

Follow me: if enabled, the stat biases temperature to occupied room, assuming that room's sensor is included in the comfort setting.  If you exclude that room's sensor from say your "Home" settings, temps from that sensor will be ignored.  Motion however cannot be disabled on sensors. If you need that, cover the sensor window with tape.

Ecobee3 detection of motion is always active in "occupied modes", on all sensors regardless of inclusion.  It's use of specific sensors for Sleep/Home/Away temperatures is by your choice.  "Sleep" mode specifically turns off motion detection on all sensors.  This keeps a restless sleeper by toggling smart home mode, when you actually want the stat set back.  If you define your own modes, you toggle if they reflect normally occupied, or not occupied modes.  It's best to just use the default modes IMHO.

The best way to program is to set up the stat to work without any external automation.  This way a web or API meltdown will not be an issue.  Use Vera to toggle modes, or trigger actions say based on temps from any of the Ecobee3 sensors.  I use alarm "arm" events to put tenant's HvAC into "Away" modes, and disarm to toggle Home modes.  I also use Ecobee3 sensor data to turn off and on our two building HRVs based on occupancy and temp (for "free" cooling). Works very reliably.

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on April 01, 2016, 01:05:42 pm
"Sleep" mode specifically turns off motion detection on all sensors.  This keeps a restless sleeper by toggling smart home mode, when you actually want the stat set back.

True, but to be more specific: the API will still report motion, even though triggering smart home mode doesn't happen.

The best way to program is to set up the stat to work without any external automation.  This way a web or API meltdown will not be an issue.  Use Vera to toggle modes, or trigger actions say based on temps from any of the Ecobee3 sensors.

Exactly!  Don't turn a "smart" thermostat into a "less smart" one by overriding its operating logic and making it dependent on external direction.  At least not *too* much...  ;)
Title: Re: Plug-in for ecobee thermostats in development
Post by: PromptCritical on April 01, 2016, 01:28:02 pm
Ok, so Vera can get motion data directly from the sensors to trigger "Home" mode.  But does that require a separate scene for every sensor or some PLEG stuff?  I haven't really tried automating the mode settings.  What I was hoping for was a direct call through the API to sync the Vera mode to the Ecobee mode.  Seems simpler that way.  I can use the smartness of the thermostat to make Vera smarter without having to do the extra work that Ecobee has already done.  "Don't reinvent the wheel" is a phrase I like to use frequently.

Also, is Minimum Fan Runtime basically the term they use for cycling the furnace blower without actually running the heat?  I'd like that feature.
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on April 02, 2016, 12:53:21 am
I've experimented with PLEG and got basic functions working.  The "Combination Switch" app was the simplest I've used so far...you can use this switch (with multiple inputs) to trigger a scene.

Yes, minimum fan runtime looks at the time running heat or cool and compares to the value you have set for minimum fan runtime, running the fan only if required. So if you set 20min/hr and the system called for heat 5 min, it would run fan only for 15min.
Title: Re: Plug-in for ecobee thermostats in development
Post by: PromptCritical on April 04, 2016, 11:46:30 am
Alright.  I'm convinced.  When funds allow, I'll buy one and a few sensors.
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on April 13, 2016, 08:12:44 pm
Watou, just an update on your updated code..zero issues.  I've got a fair bit going on with Ecobee 3 sensors triggering combination switches, security system arm/disarm scenes using PLEG and everything has worked perfectly.  Thanks as always for your efforts.

I've been looking over power and gas (heat) usage since we started with the "efficiency" program.  The Ecobee/Vera combination has reduced our gas use by nearly 25%, and hydro use about 18%.  Your plugin made much of this possible :-)

Cheers,
Dennis. 
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on April 14, 2016, 01:26:48 am
Watou, just an update on your updated code..zero issues.  I've got a fair bit going on with Ecobee 3 sensors triggering combination switches, security system arm/disarm scenes using PLEG and everything has worked perfectly.  Thanks as always for your efforts.

I've been looking over power and gas (heat) usage since we started with the "efficiency" program.  The Ecobee/Vera combination has reduced our gas use by nearly 25%, and hydro use about 18%.  Your plugin made much of this possible :-)

Cheers,
Dennis.

Thank you, Dennis, for the report and the kind thoughts.  I'm very happy it's working for you.

I submitted v1.6 of the plugin yesterday to apps.mios.com, it includes what I had uploaded here earlier, plus a hopefully defensive change to work with an Ecobee API change that is coming up in May.  Release notes here: https://watou.github.io/vera-ecobee/#history

All the best!

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: lingerba on April 14, 2016, 06:13:44 am
I just started using this plugin this past weekend.  I love it.  I love the Ecobee3.  I was previously a Honeywell Wifi thermostat user and I can't fully express how much better setup the Ecobee3 is and how much better it integrates with Vera using this app.  Thank you so much!
Title: Re: Plug-in for ecobee thermostats in development
Post by: lingerba on April 15, 2016, 07:56:36 am
I have a question, and I am going to be honest, I have not read every word on the 35 pages of this thread, so I may have missed this if already discussed.

I first installed this app 6 days ago.  I did the "get pin" process and registered that on Ecobee's website and everything worked great.  On Wednesday my Vera had a message saying that my Ecobee app wasn't registered and I needed to do the "get pin" process again.  However, Ecobee's website showed that the Vera app was still authorized.  So I ended up following the "get pin" process again, re-registered it on Ecobee's website and it all worked as expected.  I didn't think this once instance of this issue was a big deal and I figured that I had just done something wrong the first time.  However now on Friday (6 days after initial installation), I had the same issue again.  And just like before, I reregistered it on Ecobee's site and everything is working fine again.   Any thoughts/advice?
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on April 15, 2016, 08:19:14 am
the only time this has happened to me was when restoring a backup
im guessing its because the token is different

Title: Re: Plug-in for ecobee thermostats in development
Post by: lingerba on April 15, 2016, 08:23:13 am
Ok, the first time would be related to me restoring a backup.  That make sense.  I am not sure about this second time, other than if this pin process is a day or two behind the restoration.
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on April 15, 2016, 04:17:40 pm
Because Ecobee uses OAuth, there are situations where the token will expire.  I've had zero issues with this so far, but I'm guessing web connections down etc. could cause this.

Watou, the update to 1.6 went with zero issues :-)
Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on April 15, 2016, 04:39:30 pm
Watou, just an update on your updated code..zero issues.  I've got a fair bit going on with Ecobee 3 sensors triggering combination switches, security system arm/disarm scenes using PLEG and everything has worked perfectly.  Thanks as always for your efforts.

I've been looking over power and gas (heat) usage since we started with the "efficiency" program.  The Ecobee/Vera combination has reduced our gas use by nearly 25%, and hydro use about 18%.  Your plugin made much of this possible :-)

Cheers,
Dennis.
How did you lower your usage? Mine has increased since it now uses remote sensors.. Home is more comfortable but heater staying on more now
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on April 15, 2016, 05:15:25 pm
Aaron, we're using 9 stats, but in a commercial setting.  Keep in mind too, that winter temps here can hit -35C, so the potential for savings can be higher.  The 25% savings in gas usage I'd attribute to the following:

1. Lowering temps in entry ways and loading bay.  Remote sensors let us monitor these areas at 8C, to avoid freezing the in-floor radiant.

2.  Smart Recovery - the Ecobee stats are weather aware and adjust temp set up based on learned building behavior.  In most zones, we're using Smart Recovery.

3.  Aggressive "AWAY" mode toggling.  When tenants for example are away, the system is also in AWAY mode.  Vera integration with the security system combined with the Watou's Ecobee plugin also toggles AWAY modes, as well as computer peripheral power cuts etc.

Other than that, we did nothing. Workday temps are at 20.5 to 21C.  Research makes it pretty clear that the lower your delta between inside/outside temps, the more you'll save.  One of the best studies I came across was done by the NRC here in Canada using two "twin" homes.  They saw as much as 21% savings using just aggressive setbacks on the coldest days:  http://www.healthyheating.com/downloads/Thermostats/nrcc48361.pdf
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on April 26, 2016, 10:29:06 am
Because Ecobee uses OAuth, there are situations where the token will expire.  I've had zero issues with this so far, but I'm guessing web connections down etc. could cause this.

Watou, the update to 1.6 went with zero issues :-)
I had this happen as well to me.  Been months since I've seen this. 

I had a LUUP restart yesterday... could have been related to that... but it doesn't usually occur.  Maybe something on Ecobee's end....
Title: Re: Plug-in for ecobee thermostats in development
Post by: zscholz on May 13, 2016, 10:47:37 pm
Hi Watou - Maybe you can help.  I have a whole house (attic) fan that I run in the spring and in the fall.  The attic fan is on a z-wave switch so Vera knows the status of the attic fan (i.e. on/off).  I'd like to use that status to toggle on/off my ecobee.  I have successfully implemented a technique to do simple "urn:upnp-org:serviceId:HVAC_UserOperatingMode1" set to "Off" and that works when I turn on my attic fan.  Similarly, I can reset the the operating mode to "Cool" or "Heat" as well when I turn off my attic fan.  Because vera doesn't know whether I'd like to set it back to "Cool" or "Heat", as I have to currently hard code that value in the scene, I'd like a way to read the urn:upnp-org:serviceId:HVAC_UserOperatingMode1 mode and store that as a variable, then when I turn my attic fan off, write that variable back to the operating mode.  Something like:

Attic fan Off, Ecobee in "Heat" (starting state)
Turn Attic Fan On
  (Trigger) Read Ecobee UserOperatingMode1 value - write that to "mycurrentstatus" variable (in this case "Heat")
  (Trigger) Set Ecobee UserOperatingMode1 value to "Off"

Turn Attic Fan Off
  (Trigger) Set Ecobee UserOperatingMode1 value to "mycurrentstatus" (again - Heat)
  (Trigger) Send ResumeProgram Command (Maybe not necessary?)

The above scenario is perfect for "spring" - when it's still cool outside overnight, but during the day perhaps the attic fan is sufficient to keep the house cool.

The opposite (i.e. OperatingMode = Cool) might be useful in the summer, when you want to use the attic fan in the morning to cool down the house before the heat of the day, and then set the house back to Cool for the rest of the day.

Is this possible to do in Luup code?  Have any suggestions on how to implement something like this?

Thanks in advance!  LOVE your plugin!!
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on May 14, 2016, 11:39:51 pm
Are you asking if there is some device variable where you can stash the current operating mode instead of hardcoding it in the script?  Maybe you could just store it with the thermostat device, under the service ID urn:ecobee-com:serviceId:Ecobee1 ?

What might be possible instead of your scenario is to have the Ecobee control the attic fan -- the other way around from your scenario.  Ecobee has so many features for controlling equipment to achieve comfort, that there may be a way to have it turn off and on a ventilator based on its own logic (see https://www.ecobee.com/home/developer/api/documentation/v1/objects/Settings.shtml for ventilator settings).

The fact that the attic fan is controlled via Z-Wave might be a detail you could work around by monitoring the equipmentStatus reported back (see https://www.ecobee.com/home/developer/api/documentation/v1/objects/Thermostat.shtml).  Or, you could find the low-voltage relay on the thermostat to control the ventilator, run a wire up to a high-power relay on the attic fan, and re-use your Z-Wave relay for some other purpose.  This way, all comfort control logic remains with the Ecobee, with no dependencies on the Vera or Z-Wave network.  It would seem a shame to try to duplicate comfort control logic that already exists in the Ecobee by using complex external components like Vera and Z-Wave, just because of the current wiring arrangement.

Sorry this is all fuzzy, but I'm not a hardcore HVAC guy.  But the overall point is to try to leave Ecobee in charge of your equipment as much as possible, and not shift the center of control away from it, just because the fan is currently controlled via Z-Wave.  I hope this is food for thought anyway.

Good luck!
Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on May 15, 2016, 10:18:46 pm
The Ecobee 3 has an option to connect a ventilator and control via an extra set of dry contacts, normally used for an HRV.  If you do this, the stat can run the fan in lieu of AC given specific parameters.  It will only do this if the outside temp is low enough, and I seem to recall a humidity threshold you can set.  It's quite intelligent, and if you have only one stat, I'd consider using it.  You can use a Mimolite with signal input connected to the ecobee3 dry contacts to automate this without running much wire :-)

Read this: https://www.ecobee.com/2015/06/feature-friday-free-cooling/
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on May 16, 2016, 12:55:38 am
Very well put, @denwood!

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: zscholz on May 16, 2016, 11:19:35 pm
Very well put, @denwood!

watou

@watou and @denwood -  Thank you both for your reply! 

The term "attic fan" is one that's perhaps kind of misleading.  The fan that I have is a "whole house" attic fan (similar to what is shown here:  http://atticfan.com/).  This fan requires that, before use, several windows/doors are opened throughout the house to pull in fresh air from outside and through the house and out through the attic.  All that to say, the fan is 110vac powered (i.e. not dry contact closure - though I'm sure I could use a relay to close the high current lines) and (more importantly), it's located in the attic - where the ecobee control interface is in the basement.  It's really best to have the initiation of the attic fan "on" to be manual - since so much must be done in preparation of it turning on - but the ability to turn off the ecobee while it's running (so i'm not attempting to heat/cool the whole world - as the windows are open) is really all I'm after - well - that and restoring the program when I turn off the attic fan. 

I actually DO have available wires that run from the ecobee to the attic that I could use on the dry contacts, but since it's not really a typical "ventilator" (and also - I don't have an ecobee3 - I have the Ecobee Smart) - I'm not sure it's the right implementation.

@watou - I am interested in the option of storing the state of the thermostat (urn:ecobee-com:serviceId:Ecobee1) - can you give me an idea of how that might be accomplished...be gentile - I'm a hardware guy - not a software guy! 

Thanks again to both of you - I TRULY wish I had a traditional HRV/ERV - and could take advantage of the ventilator functionality...
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on May 17, 2016, 01:02:53 am
OK, now I understand. Thanks for the clear explanation.

So, back to your question: if you trigger on the attic fan turning on, check the thermostat mode. If it's in heat mode, set a hold to a much lower heat setpoint. If it's in cool mode, set a hold to a much higher cool setpoint. If it's off, do nothing.

When you trigger on the attic fan turning off, call resumeProgram so the hold you set, if any, is removed.  This way, you can have the Ecobee store state, not the Vera.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on May 17, 2016, 02:21:12 pm
Just as an aside, I'm doing a passive/active night cooling project like yours, just on a slightly larger scale.  In our case, we need windows to open, and a building exhaust fan to operate when conditions are correct.  You might find this thread helpful, detailing the project: http://www.garagejournal.com/forum/showthread.php?t=329010

We're using the Ecobee stats with Watou's plugin to monitor temps and manage AC, Leviton Zwave switch for the fan, Solar Smart window openers (no wiring required), and a few Mimolite relays to operate the windows.  The LFM20 is an isolated Zwave relay that we used to manage the two buildng HRV units via dry contacts..but it can mange up to 220V at 20 amps, perhaps ideal for your fan control.

The automations use Watou's Ecobee plugin, Combination switch plugin, DSC plugin, and Weather plugin.  The Vera box just puts the Ecobee stats in Sleep mode, or Away mode when the night cooling is going on, then resumes them when the automation is off.  I find this much easier to manage.  Opening any of the mainfloor windows (all have security sensors) turns off main floor AC by putting the stats in AWAY mode.  The window sensors are tied into Vera using an EVL4 interface.  All we do with Vera is put the stats into HOME, AWAY modes, or RESUME them.  This way, an automation or web connectivity issue will not affect the thermostat operation.

Might give you a few ideas :-)

Cheers,
Dennis.

Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on May 23, 2016, 10:13:03 pm
Anyone know a fix... this happens like once a month and is super problematic... makes it unreliable for scenes :(

ecobee : Not yet authorized. Press 'Get PIN' once; wait for PIN; enter at ecobee.com
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on May 24, 2016, 08:48:37 am
Anyone know a fix... this happens like once a month and is super problematic... makes it unreliable for scenes :(

ecobee : Not yet authorized. Press 'Get PIN' once; wait for PIN; enter at ecobee.com

previously this only happened to me after restoring a previous backup
but since version 1.5 or 1.6 not sure which one
it happens periodically for no reason
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on May 24, 2016, 09:05:17 am
previously this only happened to me after restoring a previous backup
but since version 1.5 or 1.6 not sure which one
it happens periodically for no reason

The reason, as far as I can tell, is that Vera does not reliably save device variables to disk in all cases.The Ecobee API rotates access and refresh tokens about once an hour, and if an attempt to save them to disk doesn't happen, it's game over.    If the LuaUPnP process exits abnormally (crashes, whatever reasons), the device variables are probably lost.  Since Vera tries to delay disk writes, there is no feedback possible to the plugin when it writes the variables, because they are only being saved in memory at that point.

If someone were to write a pull request to change the loadSession and saveSession functions here:

https://github.com/watou/vera-ecobee/blob/master/src/I_Ecobee1.xml#L427

so they did not use device variables, but instead used disk writes in some simple properties format for the specific device for which they are being saved (like, oh, /tmp/ecobee.49.tokens, whatever, didn't introduce some fancy external module just to do disk reads/writes, and only wrote to disk when something has changed), then I would strongly consider merging it into the next release.

All that said, I haven't lost my tokens in a very, very long time, even before the last point release of the plugin.  But my LuaUPnP process isn't doing much these days, so it's not crashing.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on May 24, 2016, 09:09:28 am
thanks watou

makes sense, good explanation
however on 1.4 and older this never happened unless I restored an older backup
which makes sense as you are restoring an old token
Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on May 24, 2016, 10:36:51 am
I haven't restored a backup in over a year. My Vera reboots daily, using a Vera scene. I wonder if a power failure can cause this? I did have a problem with Vera locking up yesterday and had to pull the plug
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on May 24, 2016, 10:39:07 am
i suppose if it rebooted at the time the token was changing
or right before it
then that could happen
Title: Re: Plug-in for ecobee thermostats in development
Post by: djrobx on June 08, 2016, 05:58:46 pm
I haven't had a token incident in a long while, but now the plugin seems to "fall asleep" at times.   The thermostat will show an old temperature, and attempts to adjust the temperature fail. 

If I restart LUUP it works again.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 09, 2016, 05:20:16 am
I haven't had a token incident in a long while, but now the plugin seems to "fall asleep" at times.   The thermostat will show an old temperature, and attempts to adjust the temperature fail. 

If I restart LUUP it works again.

I've seen the web browser "fall asleep," where the browser connection to the Vera no longer updates the UI, but after a browser refresh it hooks itself up again properly.  That sounds similar to your description.  But I've not seen a situation that required restarting Luup.  Anything interesting in the logs?
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on June 13, 2016, 10:19:47 am
we have experienced a few power outages in my area in the last month
i have found a pattern that is affecting the ecobee plugin
every time there is a power outage
afterwards the plugin does not work and reports that the token must be registered

earlier in the year we had a few power outages and this was not the case
I have noticed some token issues like this since version 1.5 and 1.6 of the plugin
on 1.4 i never had token issues which is strange as others did
and 1.5,1.6 were to resolve token issues
i have had the opposite effect
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 13, 2016, 12:40:16 pm
we have experienced a few power outages in my area in the last month
i have found a pattern that is affecting the ecobee plugin
every time there is a power outage
afterwards the plugin does not work and reports that the token must be registered

earlier in the year we had a few power outages and this was not the case
I have noticed some token issues like this since version 1.5 and 1.6 of the plugin
on 1.4 i never had token issues which is strange as others did
and 1.5,1.6 were to resolve token issues
i have had the opposite effect
If someone could do as I suggested here:

http://forum.micasaverde.com/index.php?topic=13836.msg282652.msg#282652

or if there is a hidden Lua function to sync device variables to disk as needed, then the newly rotated refresh token will be saved properly to disk. I don't know what else to suggest at the moment.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on June 13, 2016, 01:51:15 pm
i will search to see if i can find anything about syncing variables to disk using lua

would it be possible to force a token refresh at startup?
or would that not work as its already out of sync
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 13, 2016, 03:03:10 pm
When the plugin refreshes its tokens, it writes them as variables (which is only to memory at first). But they're supposed to be written to disk reliably thereafter. If they aren't and the plugin restarts, it then only knows the prior saved tokens, but they are now invalid, and the only solution is a new PIN process. So reliable token persistence is the only solution. Telling Vera to persist its variables immediately after refresh would help, since it's only once an hour, or my earlier suggestion to sidestep device variables completely.

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on June 13, 2016, 03:06:46 pm
Is there anything you can do to send a notification or trigger of some sort, that as soon as it realized it's token is no good, we can be notified.

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on June 13, 2016, 03:23:32 pm
The main Ecobee device has a status variable that goes from 1 to 0. If you could write automation to monitor that, it ought to tell you. But of course better is to fix Vera so writing variables is reliable, or find a way to workaround the issue like I described, or buy a Raspberry Pi and switch to openHAB. :-P



watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on June 13, 2016, 04:57:00 pm
The main Ecobee device has a status variable that goes from 1 to 0. If you could write automation to monitor that, it ought to tell you. But of course better is to fix Vera so writing variables is reliable, or find a way to workaround the issue like I described, or buy a Raspberry Pi and switch to openHAB. :-P



watou
Thanks, for now I will monitor that variable.  I do have 2 extra Pi's. I have started testing openhab. But have yet to fully understand it. It is much more complicated. I'm still not sure how to use it.

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: Vanlon on June 26, 2016, 03:14:48 am
I'm trying to return a home, away variable from my ecobee.  Seem to be doing something wrong somewhere  I wonder if someone could help, here's what I got so far.
Code: [Select]
local mainTherm = 91
local CkAway = luup.variable_get("urn:ecobee-com:serviceId:Ecobee1", "currentClimateRef", mainTherm)

if (CkAway == "away")  then
luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = "1"}, 12)
end
Title: Re: Plug-in for ecobee thermostats in development
Post by: lingerba on June 28, 2016, 08:48:39 am
First off, I love this plugin.

I have a scenario that I need some help with.  I use geofencing and PLEG to determine home/away status with my Vera.  I use that for several thing such a locking doors, turning off lights and setting the thermostats.  Before switching to Ecobee, I was using Honeywell thermostats which did not have the "smarts" built into it that the Ecobee does.

What I am looking to do is to still use my home/away logic in Vera, but also use the "smarts" and scheduling in Ecobee.  There is a setting for the Ecobee called "hold action" and one of the options is "until the next schedule activity".  This works great when making a setpoint change locally or via the app / web interface.  However, when Vera commands the setpoint change, it is a permanent hold.  Is there anyway to make it so when Vera commands the change that it follows the option of holding until the next schedule activity?  I know there is the option for "resume schedule", but that does not give me the same outcome as compared to holding until the next scheduled activity.

Also, am I just overthinking all of this?  Should I just let Ecobee do its own thing and leave it alone? 
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on June 28, 2016, 08:59:55 am
on the thermostat device with the controls, in vera
go to the advanced settings
then variables

look for holdType
change it to nextTransition

Title: Re: Plug-in for ecobee thermostats in development
Post by: lingerba on June 28, 2016, 09:06:43 am
That worked perfectly!  Thank you so much for your help @charettepa!

I would still appreciate any feedback that anyone has regarding how they use there Vera in conjunction with Ecobee.
Title: Re: Plug-in for ecobee thermostats in development
Post by: supernovae on July 01, 2016, 11:55:23 am
just wanted to say i love this module and i love my vera. The ecobee has been one of my best purchases yet and having it tie in so nicely to vera controller is icing on the cake.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on July 01, 2016, 11:56:28 am
just wanted to say i love this module and i love my vera. The ecobee has been one of my best purchases yet and having it tie in so nicely to vera controller is icing on the cake.
That's great to hear!

watou

Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on July 01, 2016, 03:34:08 pm
That worked perfectly!  Thank you so much for your help @charettepa!

I would still appreciate any feedback that anyone has regarding how they use there Vera in conjunction with Ecobee.

I really mostly on the ecobee for managing the various temp states using the little sensors.  That said. I do have it set to away mode if I leave the house and turn the alarm on.  Ecobee takes too long to realize someone is gone... and we usually only turn on the alarm if we are going to be gone for several hours or more.

Same alarm integration - when I come home and turn the alarm off... the SONOS app tells me the time of   day and what the temp is in the house.

I have several of the ecovents... and plan on doing something via plug and Ecobee to introduce some minimal zoning, but haven't really felt like diving into that yet.
Title: Re: Plug-in for ecobee thermostats in development
Post by: supernovae on July 08, 2016, 09:55:53 am
For the remote sensors, how reliable are they at triggering scenes? I have one that says to turn on ceiling fan if the sensor in living room detects someone, but i'd say its about a 50% chance of working. When i view it in the app, i see "occupied".  Not sure if my shutdown scene for unoccupied is trumping the occupied scene somehow but figured i would ask and see what others have experienced.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on July 08, 2016, 10:14:26 am
they are working perfectly for me


please remember
these sensors are NOT motion sensors
they are occupancy sensors
a certain amount of motion is required for a certain amount of time
this charges up a capacitor
then it reports occupancy

the opposite is true for unoccupied
after a certain amount of time
the capacitor discharges
then it reports unoccupied

Title: Re: Plug-in for ecobee thermostats in development
Post by: denwood on July 09, 2016, 08:32:30 pm
That worked perfectly!  Thank you so much for your help @charettepa!

I would still appreciate any feedback that anyone has regarding how they use their Vera in conjunction with Ecobee.

We use our nine Ecobee3 in various ways with Vera.  One is to use the Ecobee3 set point, operating mode, forecast high temp (via Underground Weather plugin) and actual inside temp vs outside temp to manage window automation and night pre-cooling of the building.  I also use the DSC plugin and an EVL4 interface to monitor windows opened or closed on the main floor.  The security sensors report a window is open, and Vera then tells the Ecobee3 main floor stats to turn off, then resume program when the windows are closed.

We capture tenant security zone arm/disarm events which toggle their Ecobee3 stats to/from HOME/AWAY.  The attached PLEG status report shows a bit of the logic to manage windows and night cooling.  All of the automations are focused around energy saving and efficiency.

Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on August 12, 2016, 09:13:14 pm
How much data can you get from the remote sensors into Vera? I've read you can get the occupancy data but I'm assuming that they report temp and possibly humidity. Do the sensors show up as separate Vera devices?
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on August 12, 2016, 09:15:00 pm
How much data can you get from the remote sensors into Vera? I've read you can get the occupancy data but I'm assuming that they report temp and possibly humidity. Do the sensors show up as separate Vera devices?
Every remote is a separate device

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on August 13, 2016, 04:22:33 am
How much data can you get from the remote sensors into Vera? I've read you can get the occupancy data but I'm assuming that they report temp and possibly humidity. Do the sensors show up as separate Vera devices?

charettepa is right, but more specifically, each ecobee3 wireless remote sensor appears as one occupancy sensor device and one temperature sensor device (the remote sensors do not sense humidity).  The main ecobee3 unit is also listed by the API as a sensor, except it also senses humidity, so for the main ecobee3 a humidity sensor device is also created.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on August 13, 2016, 11:02:48 am
That works for me. The occupancy sensors, from what I've read elsewhere, seem to be a much better option than monitoring motion detectors all over the place and with them being handled by the Ecobee itself, are less work on the Vera (or any other HA device for that matter). I was looking into the option of quite a few motion sensors and eventually a Z-Wave thermostat. The motion detectors would be used, obviously, to try to keep track of whether someone is home or not (along with other measures). Seems I can probably get away with one or two motion detectors (for security purposes) and just use the occupancy detectors for the bulk of the work...
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on August 13, 2016, 11:07:31 am
That works for me. The occupancy sensors, from what I've read elsewhere, seem to be a much better option than monitoring motion detectors all over the place and with them being handled by the Ecobee itself, are less work on the Vera (or any other HA device for that matter). I was looking into the option of quite a few motion sensors and eventually a Z-Wave thermostat. The motion detectors would be used, obviously, to try to keep track of whether someone is home or not (along with other measures). Seems I can probably get away with one or two motion detectors (for security purposes) and just use the occupancy detectors for the bulk of the work...
I am using mine the same way.  I have incorporated a few virtual sensors and scenes to determine home occupancy and away.  I track geo location and ip ping to our phones with occupancy sensors. When geo, ip, occupancy is all off then the home is away. As soon as one is present home mode is active. Works very well to control other scenes .

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on August 13, 2016, 11:12:16 am
How does one create a virtual sensor on Vera? I'd like a virtual temperature sensor that I can update with an http command or whatever is best to use. I have a separate automation system that runs my pool and a few other things that operates on Arduinos and ZigBee radios and a Raspberry Pi. It's easy enough to get information from Vera to the web interface on the Pi, I don't figure it's too difficult to go the other way...
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on August 13, 2016, 11:18:59 am
How does one create a virtual sensor on Vera? I'd like a virtual temperature sensor that I can update with an http command or whatever is best to use. I have a separate automation system that runs my pool and a few other things that operates on Arduinos and ZigBee radios and a Raspberry Pi. It's easy enough to get information from Vera to the web interface on the Pi, I don't figure it's too difficult to go the other way...
You can get virtual on/off and motion in the Vera app store, then use scenes to achieve your goal.

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on August 13, 2016, 11:33:24 am
I use virtual switches for several things now. I'm wondering how to do a virtual temperature sensor.  :-)
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 06, 2016, 12:04:36 pm
@watou

are you aware of any changes to the ecobee api

recently i need to re-authorize the ecobee to vera daily, sometimes 2x
i do not have excessive luup reloads
my controller has not crashed or restarted
i have not restored old backups

i did have issues periodically before but now its every day
any ideas?
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 06, 2016, 05:09:27 pm
Mine is working perfectly. Certainly hope your issue isn't a sign of things to come....
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 06, 2016, 05:12:03 pm
The only other thing that is different is I now have 2 more remote sensors. A total of 7. I have also noticed that the issue Is usually not long after a sensor connection loss/reconnection

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 06, 2016, 05:21:28 pm
Hmmm...Sounds like a support request to Ecobee....
Title: Re: Plug-in for ecobee thermostats in development
Post by: Wekurtz74 on September 06, 2016, 05:35:40 pm
I have also had to frequently reauthorize vera to ecobee.  I feel it has been more frequent recently

Sent from my VS986 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 06, 2016, 05:38:45 pm
I also just realized that the thermostat version is now a newer one.  3.7.0.910

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on September 07, 2016, 10:03:56 am
Mine is still working, but my firmware is 3.6.1.602
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 07, 2016, 10:32:21 am
 It would be so nice if we could connect to it locally, via ip. That would resolve all connection issues.

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 07, 2016, 11:14:25 am
i just read part of the ecobee API
not sure if I understood correctly
but it seems that the more remote sensors you have
the more interaction there will be

is it possible since i now have 7 remote sensors that the increased traffic"polling" is causing an issue
do they poll individually or as 1 unit?

i see that they dont want you to poll more often than 3 minutes
but what if they are actively blocking for X time when you go over
could that be causing it

also i am now on the newest vera firmware
it seems to luup refresh more often
could that force a poll before its time?
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 07, 2016, 11:52:41 am
When you add new sensors, how long does it take for them to show up in Vera?
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 07, 2016, 11:54:18 am
almost right away
if they are not there
just force a luup refresh and you will see it right away
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on September 07, 2016, 11:58:31 am
is it possible since i now have 7 remote sensors that the increased traffic"polling" is causing an issue
do they poll individually or as 1 unit?

That behavior is completely black-box from the perspective of the API and plugin, so only Ecobee Support could reliably answer that question.  The plugin itself requests all needed information in one API query per polling cycle and account, so there is no plugin code change that would stress the API less.

i see that they dont want you to poll more often than 3 minutes
but what if they are actively blocking for X time when you go over
could that be causing it

I've not heard of any rate limiting having been implemented, but I know Ecobee API people were talking about adding rate limiting at some point.   I would not recommend polling more often than 3 minutes, as you could hit a rate limit if they've implemented one, and I have no idea what would happen if you exceeded it.  Invalidating your tokens would seem to be a pretty harsh response from the API side, but like I said, I don't know.

also i am now on the newest vera firmware
it seems to luup refresh more often
could that force a poll before its time?

The only known cause I'm aware of having tokens become invalid is a bug/feature of Vera, where device variables are not saved to flash disk under some circumstances, and so when the plugin restarts, it retrieves stale tokens.  At that point, you need a new PIN.

The openHAB binding I wrote for Ecobee has never once ended up with invalid tokens, that I'm aware of.  I believe this is because the openHAB binding writes them disk when they are updated, so any later restart will pull in the latest tokens, not a stale set.  If you installed openHAB 1.8.3 (or possibly the 2.0 beta) and the Ecobee binding on some computer, you could at least compare behaviors against the same thermostat, remote sensors, Internet connection, etc.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on September 07, 2016, 12:05:51 pm
The ecobee vera app asks for verification at least once a week now... Very annoying.
I don't know where the problem is but I'm getting tired of all the vera issues.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 07, 2016, 12:15:52 pm

The only known cause I'm aware of having tokens become invalid is a bug/feature of Vera, where device variables are not saved to flash disk under some circumstances, and so when the plugin restarts, it retrieves stale tokens.  At that point, you need a new PIN.

The openHAB binding I wrote for Ecobee has never once ended up with invalid tokens, that I'm aware of.  I believe this is because the openHAB binding writes them disk when they are updated, so any later restart will pull in the latest tokens, not a stale set.  If you installed openHAB 1.8.3 (or possibly the 2.0 beta) and the Ecobee binding on some computer, you could at least compare behaviors against the same thermostat, remote sensors, Internet connection, etc.

watou

i did try a temp setup of openHAB about 6 months ago
i had a very hard time with it
though i must admit i did not try for very long, as i have many projects on the go
i would like to eventually try again

any tips on making a proper setup
i had an installation on an RPI2, still have the SDcard
had the windows designer installed
the demo on as well as all add ins
I could not seem to get any bindings installed/configured


i would like to move to openHAB as it sure seems more flexible
any help you can give would be greatly appreciated
i also realize this is off topic so if you want i can move this offline

Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 07, 2016, 12:54:42 pm
Added two sensors, have two more to add. Showed up after a minute or two on their own. Should have waited a little longer before I asked I suppose. I'm just used to things showing up when they are added.   ;D   Anyhow, anyone have any idea what the timeout is on the motion detection of the remote sensors?
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 07, 2016, 12:59:15 pm
they are actually occupancy sensors
slightly different than motion

the occupancy gets triggered almost right away
for it go back to a "non tripped" not occupied state
it takes about 30 minutes of no activity
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 07, 2016, 01:37:10 pm
That's what I was looking for. I knew they were actually occupancy sensors, it's part of the reason I went with the Ecobee3. Now that I have the rest of my sensors, I'm working on my logic to determine Home/Away and a few other things. Looks like I'm going to be wall mounting a few of these sensors. Anyone else have theirs mounted on the wall??
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 07, 2016, 01:46:08 pm
have all 7 wall mounted
doing exactly what you are planning
i have several scenes with logic to determine home away

1 combo switch that looks at all occupancy sensors + doors and windows
1 combo switch per/person (4 total) in the house that looks at (virtual switch triggered by geolocaton + ip ping sensor)
1 "master" combo switch that looks at all 5
     if anything is triggered house is home, once all are not-triggered (usually 20-30minutes after leaving) house is away

doing it this way instead of built in home/away prevents false alarms on triggers after away
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 07, 2016, 01:56:11 pm
Did you do anything to make them easier to remove from the mount for battery changes or are you simply hoping that they don't pull the anchor out of the wall when you try to take them off?

I'm using GeoLocation (Tasker for Android) along with the Ping Sensor plugin for my wife's phone and mine to update a multiswitch. Using the occupancy sensors to set another switch on the multiswitch to account for kids or guests. Could have used the comboswitch plugin but didn't know about it at the time. This way seem to work but I can change it later if I need to.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 07, 2016, 01:59:56 pm
i can confirm
in my case at least, that pulling them off, does not rip the plate out of the wall
i tested all of them
just make sure that you are either A) in a wall stud or B) have a good drywall anchor ie. the big white ones that screw in to the drywall

i have all mine in anchors, the good white screw in ones
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 08, 2016, 10:55:37 am
Good to hear.

How do you manage different states on your thermostat? Do you manage the home/away from Vera or do you let the thermostat do it? I'm wondering because I'd like to do a little of both but not sure how the thermostat handles itself under certain situations. I know how the smart home/away works. When Vera goes into Away mode, I flip the Ecobee home/away to away, bypassing the 2 hour timeout on the Ecobee. When I return, the thermostat (using it's sensors) will know I'm back and go back into home mode. What I need to figure out is if I can somehow control the set and hold options including the option of how long to hold, from Vera. If I'm going away for the weekend and trigger Vera's vacation mode, it should set and hold the thermostat at whatever level until I return, not just until the next schedule change. But I don't want away to do the same. In other words, I want to modify the logic of the thermostat, not replace it completely.... Any ideas???
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 08, 2016, 10:59:42 am
the plugin lets you chose between
indefinite, until next hold

but that in all cases, not selectable

to do what you want you will need to add lua/luup to your scenes
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 08, 2016, 11:05:13 am
The plugin allows me to select the hold time like that? I haven't seen any indication of that but I'll look again. I'm not a LUUP programmer by any means yet so if you wouldn't mind putting some examples of how and why, I'm sure others would appreciate it as much as I would.  :D
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 09, 2016, 08:28:46 am
The main thermostat device with the controls has a variable called holdType, the default is indefinite you can changes it to nextTransition. Those are the only 2 options. For advanced lua luup, I'm not sure, I have an idea but don't know what device service id to address, that will need help from watou.

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 09, 2016, 08:32:12 am
@watou you had mentioned that the main service device has a status variable, set to 1 when connected. It can be verified to confirm connection to ecobee service.  Unfortunately the value is not addressable via Vera scenes. My 2 questions are, 1- can you make it addressable via Vera scenes. 2- what urn device would I need to address in luup code to verify its state?

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 12, 2016, 01:55:50 pm
Hopefully Watou will see this. I'm wondering how to get the thermostat to do several things. One is hold and set the hold until mode. The other is to return to it's normal schedule. I'm certain that this is going to be Luup code...
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 14, 2016, 10:29:30 am
@watou

i have made a discovery today when it comes to re-authorizing

in the last 3 days i had a sensor lose and regain connection to the thermostat
2 times
in both cases it was at that moment that vera lost connection and needed to be re-authorised

hopefully this info helps in keeping/not loosing connection



Also

any thought on my previous question about 
what urn device would need to be address in luup code to verify its state

would this be correct

local ecobeestatus = luup.variable_get("urn:schemas-ecobee-com:device:Ecobee:1","status",173)
return (ecobeestatus == "0")

in this scenario
173 is my device id
and the luup code is "true" if status is 0
therefore my scene that notifies me, will run

or

the possibility of making addressable/visible by vera scene
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 14, 2016, 03:53:39 pm
ok so i have it working
to anyone who needs to monitor this value
here goes

install virtual switch from app store call it ecobee status (or something like that)
in this device I added 2 notifications
"Connected" that notifies of a re-connection when switch is on
"Disconnected" that notifies of a disconnection when switch is off

create 2 scenes that have a trigger of "every 5 minutes"
with the following luup code
ecobeeid value is the device# of the ecobee service device with the status, make sure to enter your value
vecobeeid value is the devexe# of the virtual switch you created, make sure to enter your value


1 that changes the switch to off "0" if the status is 0 and switch is on
luupcode below
local ecobeeid = 173
local vecobeeid = 328
local ecobeestatus = luup.variable_get("urn:ecobee-com:serviceId:Ecobee1","status",ecobeeid)
local vecobeestatus = luup.variable_get("urn:upnp-org:serviceId:SwitchPower1","Status",vecobeeid)
return (ecobeestatus == "0") and (vecobeestatus == "1")
set the action of the scene is to set the virtual switch to off

1 that changes the switch to on "1" if the status is 1 and switch is off
luupcode below
local ecobeeid = 173
local vecobeeid = 328
local ecobeestatus = luup.variable_get("urn:ecobee-com:serviceId:Ecobee1","status",ecobeeid)
local vecobeestatus = luup.variable_get("urn:upnp-org:serviceId:SwitchPower1","Status",vecobeeid)
return (ecobeestatus == "1") and (vecobeestatus == "0")
set the action of the scene is to set the virtual switch to on

you now have 2 scenes that toggle a virtual switch
and notification on status changes of that swirch
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 14, 2016, 04:02:10 pm
Hopefully Watou will see this. I'm wondering how to get the thermostat to do several things. One is hold and set the hold until mode. The other is to return to it's normal schedule. I'm certain that this is going to be Luup code...

hi Mike
for setting hold for a predefined amount of time or resume
you are correct
that is through luup

for setting the default hold type
that is done via a variable in the thermostat device with the controls
the variable is holdType
the values are nextTransition or indefinite
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 14, 2016, 05:10:13 pm
I knew it would be, I was hoping he'd come along and give some examples...
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 14, 2016, 05:13:57 pm
Yeah he must be away. I hope he chimes in on it needing a token reset when remote sensors disconnect. Also i would love to start using openhab as he his indicated several times we should try. but need a bit of help.  I have it setup but can't get ecobee or Vera to connect to their bindings.

Sent from my ONE A2005 using Tapatalk
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on September 14, 2016, 06:50:01 pm
Regarding the more frequent loss of tokens you are seeing, if there were log files that show anything interesting, I could take a look.  I still think it's a bug that device variables aren't saved when they should be, which I think is a Vera bug.  A log could still possibly show something helpful.

I don't have a collection of example Luup code, sorry.  I know openHAB can be difficult to work with at first.  There is a new openHAB 2.0 beta 4 just released, and it has usability improvements over openHAB 1.8.3 that might make it quicker to get something going.

Sorry I don't have much time these days...
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 14, 2016, 08:08:41 pm
Regarding the more frequent loss of tokens you are seeing, if there were log files that show anything interesting, I could take a look.  I still think it's a bug that device variables aren't saved when they should be, which I think is a Vera bug.  A log could still possibly show something helpful.

I don't have a collection of example Luup code, sorry.  I know openHAB can be difficult to work with at first.  There is a new openHAB 2.0 beta 4 just released, and it has usability improvements over openHAB 1.8.3 that might make it quicker to get something going.

Sorry I don't have much time these days...
Thanks for your reply I tried openhab 2.0b3 last week. Hopefully b4 will be better. I will try to get it now.

For Vera. Which log would you need to see and what is the best way to get it.  I have pin pointed it to every time the ecobee losses/regarding connection to a Remote sensor.

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 14, 2016, 09:00:27 pm
I get the lack of time. If you happen to get an extra minute and don't mind, could you try to enlighten us on how to return to the scheduled program? No hurry, I can live without it if I must. Thanks a million.....
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 15, 2016, 07:53:38 am
i had another disconnection this morning

but this one was like no other

i got the notification that the connection was lost
i did not have time and thought i'll fix it when i get to work
when i got to work i logged in and sure enough, it was disconnected
but then i had to get something

on my way back to my desk i got another notification that it was re-connected
and sure enough it was

this is good
but...
how, without a new token, did it correct itself?
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on September 15, 2016, 11:35:31 am
I get the lack of time. If you happen to get an extra minute and don't mind, could you try to enlighten us on how to return to the scheduled program? No hurry, I can live without it if I must. Thanks a million.....

Mike... not sure if this is what you are looking for.... but I do this when I turn the alarm off (return ecobee to 'home' state)

from within a scene... you should be able to go into the devices tab (i'm on UI5) and find the box with the home and away options.  this will add that action fro the scene.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 15, 2016, 01:11:12 pm
The thermostat will return itself to 'home' mode as soon as I walk in and the sensors detect I'm home. What I'm trying to do is figure out how to hold the temperature at a certain point indefinitely while I'm away on vacation, or any extended absence, but have it return to normal programming as the result of conditional logic such as a geofence that says I'm an hour or so away again. Last few nights, the thermostat hasn't gone into the night schedule at all. I'm going to turn off the "follow me" feature and see if it doesn't fix it. I have a feeling since there are people still moving around after the night schedule begins, it stays in "home and holding"...
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on September 15, 2016, 01:23:24 pm
The thermostat will return itself to 'home' mode as soon as I walk in and the sensors detect I'm home. What I'm trying to do is figure out how to hold the temperature at a certain point indefinitely while I'm away on vacation, or any extended absence, but have it return to normal programming as the result of conditional logic such as a geofence that says I'm an hour or so away again. Last few nights, the thermostat hasn't gone into the night schedule at all. I'm going to turn off the "follow me" feature and see if it doesn't fix it. I have a feeling since there are people still moving around after the night schedule begins, it stays in "home and holding"...

ah... ok.  so... here are my thoughts for what it's worth.  most of what you can do is done directly in the ecobee app...

for extended periods... you can actually go into the ecobee app and set that up with when you are leaving and returning.  I think it's called vacation mode.  not as sophisticated as using a geofence, but I find that when i'm away for an extended time, i'm usually pretty sure when i'm going to get home within a few hours... so it's close enough.

If you really wanted to do the return home bit using a geofence, you'd have to write some logic that when you crossed the fence, it would check the setting and switch it.  Should be able to do this in PLEG.

for the night mode... trying to recall, but I don't think moving around has anything to do with night mode....you are still "home"... so it's going to keep your temp setting at whatever you have it set for during night mode. "follow me" will just ensure that the temp in the rooms where there are people will be what you want it to be during night mode. If you all left... it would then go to away mode after some time. So, night mode is based on a time setting, not motion. 

that aside... one issue we have is that our master is the hottest room in the night (faces sun all day), so I have night mode set to ONLY see our master bedroom sensor to set the temp.  if it let it use all of them... the downstairs will be much cooler than the upstairs and the thermos will stop.

Make sense?
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 15, 2016, 01:36:35 pm
Well, that's my understanding of how it's supposed to work. For some reason, the past few days, the sleep schedule has never run. I'm going to watch it tonight to see what's going on.
Title: Re: Plug-in for ecobee thermostats in development
Post by: tomgru on September 15, 2016, 01:55:16 pm
Well, that's my understanding of how it's supposed to work. For some reason, the past few days, the sleep schedule has never run. I'm going to watch it tonight to see what's going on.

If you don't already have this.... it's a great forum for ecobee issues.
http://www.smarthomehub.net/forums/categories/ecobee

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 15, 2016, 02:25:38 pm
Well, that's my understanding of how it's supposed to work. For some reason, the past few days, the sleep schedule has never run. I'm going to watch it tonight to see what's going on.

i had a similar issue a few months ago
it was a problem with the remote sensors thinking there was occupancy when there was not
both my kids rooms had activity 24/7 even when not home
you can verify this in the home iq > system monitor > follow me

i removed both sensors
then
re-added them
then put them into the comfort zones/modes
then disable and re-enable follow me

dont ask me why it works but it does




Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 15, 2016, 07:10:10 pm
Not having problems with the sensors. They're working just fine....
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on September 16, 2016, 12:10:23 pm
Not having problems with the sensors. They're working just fine....
OK, it's good you checked though. Mine were fine too, but kept reporting motion at night. The process mentioned corrected the issue.

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: lingerba on September 16, 2016, 12:17:23 pm
I get the lack of time. If you happen to get an extra minute and don't mind, could you try to enlighten us on how to return to the scheduled program? No hurry, I can live without it if I must. Thanks a million.....

I used PLEG for this.  When you set your 'Action', choose the Ecobee device which shows the home/away mode.  From there you set the 'Device Action' to "Resume Program" which is under the "urn:ecobee-com:serviceID:Ecobee1" heading.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 16, 2016, 01:57:31 pm
I used PLEG for this.  When you set your 'Action', choose the Ecobee device which shows the home/away mode.  From there you set the 'Device Action' to "Resume Program" which is under the "urn:ecobee-com:serviceID:Ecobee1" heading.

That's what I was looking for, just didn't know where to look! I'll give it a run and see what happens.... Thanks!!!
Title: Re: Plug-in for ecobee thermostats in development
Post by: wfscot on September 16, 2016, 04:00:03 pm
Hello!

I'm new to MCV and Ecobee.  I just set up my VeraPlus, installed this app, and am trying to follow the instructions from the github site.

When I click "Get PIN", though, it just says "ERROR: Device not ready".  I do have the Ecobee app open to My Apps in another tab as instructed.  I've tried resetting the Vera and same result.

Any ideas what's going on?

Thanks!
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 18, 2016, 01:31:30 pm
Is the Ecobee3 completely set up and visible to the web UI?
Title: Re: Plug-in for ecobee thermostats in development
Post by: wfscot on September 18, 2016, 03:29:51 pm
Thanks for getting back to me :).

I assume you mean the ecobee web UI?  If so, then yes, I can access and control the thermostat via ecobee.com.

Thanks again!

Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on September 18, 2016, 08:28:33 pm
Delete the Vera app in the ecobee ui, refresh the page, reboot Vera, then select get pin. If that doesn't work,  remove and reinstall the plug in and try again. Mine loaded right up and ran....
Title: Re: Plug-in for ecobee thermostats in development
Post by: wfscot on September 25, 2016, 06:34:59 pm
Finally got back to the place to try this.  There was no app in the Ecobee (didn't make it that far), so I just removed the app in the Vera, restarted the Vera (for good measure), and re-added the app.  Everything is working like a charm.  Thanks!
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on November 15, 2016, 11:17:52 am
Is there a way to change a sensor participation via plugin or LUUP?

Typically I disable a sensor participation in guest rooms so only master bedroom sensor drives thermostat.
I would like to automatically enable a guest room participation if prolonged motion activity is detected and conversely, disable if no prolonged activity (probably using PLEG).

Also, it would be a great option to change a sensor participation based on alarm mode.

Btw, 'Follow Me' will average all participating sensors during inactivity, so it does not work for my scenario.

Thanks
Title: Re: Plug-in for ecobee thermostats in development
Post by: lingerba on November 15, 2016, 11:27:29 am
Is there a way to change a sensor participation via plugin or LUUP?

Typically I disable a sensor participation in guest rooms so only master bedroom sensor drives thermostat.
I would like to automatically enable a guest room participation if prolonged motion activity is detected and conversely, disable if no prolonged activity (probably using PLEG).

Also, it would be a great option to change a sensor participation based on alarm mode.

Thanks

Sensor participation is setup in your Ecobee settings (not Vera).  You can set specific sensor participation per "comfort setting" (i.e. home/night/away/etc.).  If you want Vera to control which sensors are used, you would have to set Vera up to specify which comfort setting is used and then create various comfort settings which match your needs.
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on November 15, 2016, 12:26:56 pm
Is there a way to change a sensor participation via plugin or LUUP?


Sensor participation is setup in your Ecobee settings (not Vera).  You can set specific sensor participation per "comfort setting" (i.e. home/night/away/etc.).  If you want Vera to control which sensors are used, you would have to set Vera up to specify which comfort setting is used and then create various comfort settings which match your needs.

Thanks lingerba,
Although a custom "comfort setting" with specific sensors participation is an interesting idea, it does not work with a regular schedule.
I want to keep one schedule and just change what rooms are participating within this schedule.

I still hope there is a way to change a sensor participation via Vera.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on November 15, 2016, 03:12:11 pm
Is there a way to change a sensor participation via plugin or LUUP?


Sensor participation is setup in your Ecobee settings (not Vera).  You can set specific sensor participation per "comfort setting" (i.e. home/night/away/etc.).  If you want Vera to control which sensors are used, you would have to set Vera up to specify which comfort setting is used and then create various comfort settings which match your needs.

Thanks lingerba,
Although a custom "comfort setting" with specific sensors participation is an interesting idea, it does not work with a regular schedule.
I want to keep one schedule and just change what rooms are participating within this schedule.

I still hope there is a way to change a sensor participation via Vera.
When a sensor is part of a comfort setting. It's readings do not count if it's "not occupied" for instance my basement is in the mix for "evening" but Is not factored into the average temp when it's "unoccupied"

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on November 15, 2016, 04:32:57 pm

When a sensor is part of a comfort setting. It's readings do not count if it's "not occupied" for instance my basement is in the mix for "evening" but Is not factored into the average temp when it's "unoccupied"


This is only true when another sensor is occupied.
However when all unoccupied, it's averaging all.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on November 15, 2016, 04:38:25 pm
If they are all unoccupied, it should switch to away mode. Just don't put that sensor in away mode comfort setting.

Sent from my ONE A2005 using Tapatalk
Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on November 16, 2016, 10:35:58 am
If they are all unoccupied, it should switch to away mode. Just don't put that sensor in away mode comfort setting.


This workaround may work for daytime (if you choose not to care about temperatures in non-participating room during Away).

But it does not work during Sleep setting.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on November 16, 2016, 10:39:01 am
If they are all unoccupied, it should switch to away mode. Just don't put that sensor in away mode comfort setting.


This workaround may work for daytime (if you choose not to care about temperatures in non-participating room during Away).

But it does not work during Sleep setting.
Same goes with sleep. Do not add that sensor to the sleep comfort setting.

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on November 16, 2016, 10:53:48 am
If they are all unoccupied, it should switch to away mode. Just don't put that sensor in away mode comfort setting.


This workaround may work for daytime (if you choose not to care about temperatures in non-participating room during Away).

But it does not work during Sleep setting.
Same goes with sleep. Do not add that sensor to the sleep comfort setting.


Then it defeats the purpose.
I do want bedrooms averaging during Sleep when they are used. 

If I can't control sensor's participation from Vera, I guess I can make a workaround using Fan control.
I can make a virtual 'Guest Bedroom Occupied' switch and when it's On, run a tstat Fan until delta-t between bedrooms are equalized.



Sent from my iPhone using Tapatalk
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on November 16, 2016, 10:57:33 am
If they are all unoccupied, it should switch to away mode. Just don't put that sensor in away mode comfort setting.


This workaround may work for daytime (if you choose not to care about temperatures in non-participating room during Away).

But it does not work during Sleep setting.
Same goes with sleep. Do not add that sensor to the sleep comfort setting.


Then it defeats the purpose.
I do want bedrooms averaging during Sleep when they are used. 

If I can't control sensor's participation from Vera, I guess I can make a workaround using Fan control.
I can make a virtual 'Guest Bedroom Occupied' switch and when it's On, run a tstat Fan until delta-t between bedrooms are equalized.



Sent from my iPhone using Tapatalk
I'm confused, I thought this was for your guest room. If so do not add guest room to sleep setting. But when you have a guest. Add it temporarily to the sleep setting. I agree your case is a bit different than my basement as that does not matter at sleep, but all you need to do is add the guest sensor to the sleep setting when someone is there.

Sent from my ONE A2005 using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: theal on November 16, 2016, 11:22:28 am
charettepa, I'm trying to avoid manual settings on t-stat in case I forget or I'm away.
I can program to detect an occupancy through motion/alarm settings.
My original question was if it is possible to change sensor's participation programmatically via Vera.

But thanks to this discussion, I'm leaning towards using Fan to equalize temperatures via PLEG.
It can solve participation issue and I wanted to implement fan temperature equalization anyway as it is way better than averaging (especially in my house where temperature difference can be as high as 5F).
I was very surprised that a fan temperature equalization function is not in Ecobee3; it should be no-brainer for Ecobee to have it as a standard feature.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on November 16, 2016, 11:30:45 am
charettepa, I'm trying to avoid manual settings on t-stat in case I forget or I'm away.
I can program to detect an occupancy through motion/alarm settings.
My original question was if it is possible to change sensor's participation programmatically via Vera.

But thanks to this discussion, I'm leaning towards using Fan to equalize temperatures via PLEG.
It can solve participation issue and I wanted to implement fan temperature equalization anyway as it is way better than averaging (especially in my house where temperature difference can be as high as 5F).
I was very surprised that a fan temperature equalization function is not in Ecobee3; it should be no-brainer for Ecobee to have it as a standard feature.
From a fully automated perspective that's not possible yet.  It would be nice if there were an option in ecobee settings to cooperator ignore a sensor if it has no occupancy. Ex. Name for option exclude this sensor when all unoccupied.

Sent from my ONE A2005 using Tapatalk

Title: Plug in for ecobee thermostats in development
Post by: LindsiWains on November 16, 2016, 07:07:46 pm
Is it possible to control 2 ecobee thermostats from the same ISY? using relay server  - I have ordered a 2nd for my house down stairs but not installed it yet.  I assume the ecobee app can handle this, but can EcoLink / relay server ?
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on November 21, 2016, 10:48:33 am
Any possibility of being able to modify the fan run time per hour from this plugin? I have a condition that set the setpoint high if a door or window is open longer than a period of time and it works just fine, but the fan still cycles. When everything is closed again, it resumes the current program. It does it when the mode is actually set to off as well so it may just be something I have to live with...
Title: Re: Plug-in for ecobee thermostats in development
Post by: PromptCritical on November 23, 2016, 04:39:38 pm
Well, finally got my Ecobee3 and three sensors.  Hopefully I'll get it installed soon.

Looks like the best idea is to remove my Honeywell from Vera and disconnect it, wire in the Ecobee and fully set it up before even thinking about installing the Vera plugin.  Then go for the plugin and see what happens.

From this thread, it looks like Watou isn't really able to work on this anymore since he hasn't posted in a couple months.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on November 23, 2016, 05:33:16 pm
Well, finally got my Ecobee3 and three sensors.  Hopefully I'll get it installed soon.

Looks like the best idea is to remove my Honeywell from Vera and disconnect it, wire in the Ecobee and fully set it up before even thinking about installing the Vera plugin.  Then go for the plugin and see what happens.

Very sound.  First get the hardware and native apps all working, and then move on to the plugin.

From this thread, it looks like Watou isn't really able to work on this anymore since he hasn't posted in a couple months.

It's true I have very little time to devote to it these days.  I've moved over to openHAB on a Raspberry Pi for my own purposes.  But I try not to leave anyone stranded with the Vera plugin.

watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: PromptCritical on November 25, 2016, 01:05:43 pm
Well, finally got my Ecobee3 and three sensors.  Hopefully I'll get it installed soon.

Looks like the best idea is to remove my Honeywell from Vera and disconnect it, wire in the Ecobee and fully set it up before even thinking about installing the Vera plugin.  Then go for the plugin and see what happens.

Very sound.  First get the hardware and native apps all working, and then move on to the plugin.

From this thread, it looks like Watou isn't really able to work on this anymore since he hasn't posted in a couple months.

It's true I have very little time to devote to it these days.  I've moved over to openHAB on a Raspberry Pi for my own purposes.  But I try not to leave anyone stranded with the Vera plugin.

watou

Good to know.  I'm glad we have developers like you doing this stuff and staying around to help others.  Sometimes it seems the support from you guys is better than what we've come to expect from people who actually get paid to do it.
Title: Re: Plug-in for ecobee thermostats in development
Post by: mpclimber on December 20, 2016, 06:15:26 pm
I am trying to use ecobee's "SmartAway" function as a trigger to switch my house mode to "Away".
I think this would be a great solution for presence detection in my house.  Geofencing, device IP detection or keyfob presence sensors won't work for me because I have young kids and sometimes the babysitter or someone else would be home with them and I don't want the house to switch into away just because my wife and I are not home.
 
I know I can use "Away" mode as a trigger, but it appears to only work when the ecobee is manually switched into away mode.

Does anyone know how I can accomplish this?
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on December 21, 2016, 02:58:04 pm
Do you have extra sensors spread around the house or just the thermostat and the one sensor? If you have multiple sensors, use them as the triggers instead of the actual thermostat mode. The more sensors you have, the better this will work. I monitor doors opening as well so that if all the sensors go quiet but no doors have been opened in the last 30 minutes, it doesn't switch modes. Google "wasp in a box" for a better understanding of the concept.
Title: Re: Plug-in for ecobee thermostats in development
Post by: mpclimber on December 21, 2016, 11:46:17 pm
I do have multiple sensors 4 for the ecobee and 2 other go control motion detectors, but I was hoping for simplicity without cooking up a complicated PLEG setup.  I'm imagining SmartAway has to be a readable state.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on December 22, 2016, 04:05:50 pm
I understand. I don't know if it's a readable state but urn:ecobee-com:serviceId:Ecobee1 references the variable currentEventType that may be of help. I looked for a reliable method for a while before I went the route that I went. Simple is good, but you may find that you'll still wind up a lot of false away statuses. I did...
Title: Re: Plug-in for ecobee thermostats in development
Post by: mpclimber on December 22, 2016, 06:41:37 pm
Thanks!  Given the sheer number of sensors, I've never had the ecobee go into a false smartaway mode on me.  I'll look into the setting you referenced.
Title: Re: Plug-in for ecobee thermostats in development
Post by: TinCup on January 05, 2017, 09:18:58 am
Love this plugin, @watou!  I replaced my CT100 with an ecobee and this plugin is the bee's knees.  I'm able to pull all kinds of goodness out of the plugin devices for some graphs I have setup.

Quick question:  is there a way to pull the humidity setpoint?  I didn't see it listed as a variable so it may not be exposed, but just wanted to ask.

Thanks!
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 05, 2017, 09:41:24 am
Thanks for the praise, TinCup! 

Unfortunately I never implemented a full humidistat function in the plugin.  The Humidistat device documented here https://watou.github.io/vera-ecobee/  only implements the humidity sensor service.  There doesn't seem to be (last I looked) a UPnP or Vera service definition for humidistats and I didn't need the feature myself.  No idea how UI7 would choose to display a humidity setpoint; might not work...

If you can improve the humidistat device to include setpoint control, such that it doesn't negatively impact existing users, I would gladly accept a pull request here:

https://github.com/watou/vera-ecobee/pulls

Regards,
watou
Title: Re: Plug-in for ecobee thermostats in development
Post by: TinCup on January 05, 2017, 09:47:10 am
Awesome!  I've already been playing around with ecobee's API so I'll give it a look!
Title: Re: Plug-in for ecobee thermostats in development
Post by: Freddy99 on January 31, 2017, 04:35:40 am
I have added my Ecobee thermostats to my Vera Plus using the Ecobee plugin. I am in Europe and so my Vera setting are set to Celsius. However the thermostat temperatures showing on my Vera are in Fahrenheit.....Not just that, but they are not converted to their equivalent.
So if the actual temp is 15 degrees C, it is showing up as 59 degrees C ( should be 59 degrees F to be correct)
I have contacted Vera support and they have told me that the Ecobee plugin ignores the weather and location settings in Vera.
Is there any way to get the Vera to use Celsius settings for my Ecobee?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on January 31, 2017, 04:50:03 am
I have contacted Vera support and they have told me that the Ecobee plugin ignores the weather and location settings in Vera.
Is there any way to get the Vera to use Celsius settings for my Ecobee?

The plugin has not changed since it was able to correctly determine C or F, as shown here: https://github.com/watou/vera-ecobee/blob/master/src/I_Ecobee1.xml#L141

So Vera support apparently did not share that they either broke this capability in a firmware update, or they simply gave you incorrect information.

In your web browser on the same local network as your Vera, do you receive a "temperature" value in the reply to this URL?

http://<VERAIPADDRESS>:3480/data_request?id=lu_sdata

There at least used to be a setting under Location in the web UI to choose the temperature scale to C, and in the data returned from the above URL, you would see "temperature": "C".

Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on January 31, 2017, 08:29:05 am
i have a vera plus and its working fine in celcius
i even use the .10 decimal display

i have had this happen before
just reload the engine and it should correct

if it does not
change vera to farenheit, reload engine, change back to celcius, reload engine

you should then be fine
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on January 31, 2017, 01:33:11 pm
Same here, I am in the US but have everything set in metric. Plug-in always shown in Celsius fine. No relation to the location...
Title: Re: Plug-in for ecobee thermostats in development
Post by: Freddy99 on January 31, 2017, 02:31:56 pm
Thank you. I will try this tonight and report back.
Freddy
Title: Re: Plug-in for ecobee thermostats in development
Post by: Freddy99 on February 03, 2017, 01:12:50 pm
OK, I figured this out after a lot of hair pulling and an unsuccessful factory reset.
I am also using the Nest plugin to monitor my Nest Protect smoke detectors, and they have released a new version of the plugin.
If the Nest plugin is loaded first and then the Ecobee plugin is loaded, then the Ecobee readings change to Fahrenheit regardless of any Vera settings or resets.
If the Ecobee plugin is loaded first and registered with Ecobee portal then all is good and you can load the Nest plugin after that.
This may help someone else.
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on February 03, 2017, 01:38:52 pm
Wow, thanks. I have both too and never seen this. I did have the ecobee plugin long before the nest. How do you make sure one loads before the other at startup?
Title: Re: Plug-in for ecobee thermostats in development
Post by: Freddy99 on February 03, 2017, 01:51:23 pm
My problem was the initial setup. I installed the Nest plugin first and that caused the problem.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on February 09, 2017, 10:28:56 pm
@watou

Just the past 3-4 days I've had major problems with the plugin constantly (~1x every day) complaining "ecobee : Not yet authorized. Press 'Get PIN' once; wait for PIN; enter at ecobee.com."

Is there an issue with an API change or something?

thx
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 10, 2017, 02:35:42 am
I follow Eceboee's Twitter feed, where they reported server maintenance activities in the last few days.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on February 10, 2017, 10:15:18 am
I'm not clear on what the issue is?

1. If there is maintenance on the server side, it forgets the API connection - even though their system still shows the Vera app in my config?
or
2. the Vera plugin fails to communicate and thinks we need to re-do the PIN -- but we really don't and the plugin will reconnect just fine, eventually?
or
3. the Vera plugin fails to communicate and then forces us to re-do the pin and won't try to reconnect even if the API starts working again?

thx

Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on February 10, 2017, 11:08:57 am
Just want to report, I am not seeing any disconnection over the past week...
Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on February 12, 2017, 10:34:35 am
@watou
Did it again yesterday. I reboot twice and waiting until this morning... I had to re-do the pin for it to work again :(

how can e troubleshoot this?

thx

Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 12, 2017, 10:40:10 am
@watou
Did it again yesterday. I reboot twice and waiting until this morning... I had to re-do the pin for it to work again :(

how can e troubleshoot this?

thx

I'm afraid that I don't have more advice than what had been said earlier on this thread: find why the LuaUPnP process is exiting abnormally, and/or get the Vera people to properly save device variables when written.
Title: Re: Plug-in for ecobee thermostats in development
Post by: NewfD90 on February 15, 2017, 03:50:01 pm
So mine has disconnected a handful of times since I installed it last fall.  I sigh and login to the ecobee website, delete the vera auth and re-add.  Things are good for a while.

However, short of deleting the device (which I don't want to do as it'll mess up my PLEGs), I'm not sure how to fix the latest disconnect.

The UI5 status box gives me the oh so familiar:

ecobee : Not yet authorized. Press 'Get PIN' once; wait for PIN; enter at ecobee.com.

However, when I go to the device, there is no Get PIN.  Status wise, it looks like it's still connected, yet I know it's not (none of the controls work).

Any advice as to how to make the device go into Get PIN mode?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 15, 2017, 04:01:17 pm
So mine has disconnected a handful of times since I installed it last fall.  I sigh and login to the ecobee website, delete the vera auth and re-add.  Things are good for a while.

However, short of deleting the device (which I don't want to do as it'll mess up my PLEGs), I'm not sure how to fix the latest disconnect.

The UI5 status box gives me the oh so familiar:

ecobee : Not yet authorized. Press 'Get PIN' once; wait for PIN; enter at ecobee.com.

However, when I go to the device, there is no Get PIN.  Status wise, it looks like it's still connected, yet I know it's not (none of the controls work).

Any advice as to how to make the device go into Get PIN mode?

On UI5, I get the Get PIN button.  Try fully refreshing your browser in case there is some connection issue.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on February 15, 2017, 04:05:52 pm
I've gotten the error again several time this week... I'll see if I can find the issue documented in the Lua log

Sent from my SM-G935U using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: jcolter on February 15, 2017, 06:43:57 pm
I've had a couple disconnects over the last few weeks as well and had to resync via the ecobee website.
Title: Re: Plug-in for ecobee thermostats in development
Post by: NewfD90 on February 16, 2017, 10:21:04 am
So mine has disconnected a handful of times since I installed it last fall.  I sigh and login to the ecobee website, delete the vera auth and re-add.  Things are good for a while.

However, short of deleting the device (which I don't want to do as it'll mess up my PLEGs), I'm not sure how to fix the latest disconnect.

The UI5 status box gives me the oh so familiar:

ecobee : Not yet authorized. Press 'Get PIN' once; wait for PIN; enter at ecobee.com.

However, when I go to the device, there is no Get PIN.  Status wise, it looks like it's still connected, yet I know it's not (none of the controls work).

Any advice as to how to make the device go into Get PIN mode?

On UI5, I get the Get PIN button.  Try fully refreshing your browser in case there is some connection issue.

Like I said, I normally do.  But in this disconnect case I don't.  I've restarted Vera and refreshed lots of times.

So short of deleting and re-adding, is there anyway to kick the device into re-auth mode?
Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on February 16, 2017, 08:36:35 pm
@watou
Log attached, I didnt see anything that pointed me to why the ecobee auth needs to be redone almost daily... but I'm sure you will have better luck.

thx for the help!
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on February 17, 2017, 10:47:55 am
I'm not sure what the issue is lately, but I've had to reauthorize mine a few times over the last two weeks. Is there a variable we can monitor to alert as to when contact is lost? It would be great if there was a way to automatically reauthorize the unit, but I doubt Ecobee would allow that...
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 17, 2017, 10:59:06 am
If users of the Ecobee plugin could convince the Vera folks to make sure that device variables written by Luup code are stored to disk reliably, I strongly believe that these issues will stop.  The plugin just writes device variables with new access and refresh tokens every hour, but sometimes the writes are not saved permanently but instead revert to the old tokens.  This is a long-running bug in the Vera firmware.  What do you do when you can't rely on persistent storage of device variables?  Vera should fix this firmware bug, which was reported a very, very long time ago.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on February 17, 2017, 11:02:00 am
If I were to install the plugin on my OpenLuup box, I wouldn't have the issue? I could then simply mirror it to the Vera, correct?
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on February 17, 2017, 11:13:22 am
If I were to install the plugin on my OpenLuup box, I wouldn't have the issue? I could then simply mirror it to the Vera, correct?

If the people who implemented OpenLuup made it so luup.variable_set(...) can be counted on to write the variable so future reads will read the correct result, and if OpenLuup supports encrypted source files like is required in this plugin's case, then it's certainly possible!

Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on February 17, 2017, 06:45:35 pm
Ah. I don't believe it supports encrypted source files. Oh well, I guess we just have to hope that MCV will get on the ball and fix the issue then...  :)
Title: Re: Plug-in for ecobee thermostats in development
Post by: Aaron on February 18, 2017, 11:14:47 am
Ah. I don't believe it supports encrypted source files. Oh well, I guess we just have to hope that MCV will get on the ball and fix the issue then...  :)
You need to open a ticket.  hope is not a strategy for success

They need users to open tons of tickets, vera says they fixed this... I've told them (three open tickets) this bug is not fixed. They only listen to open tickets

Sent from my SM-G935U using Tapatalk

Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on February 18, 2017, 09:30:30 pm
Ok. How does one open a ticket? If we have to bust balls to get a problem resolved, lets do it....
Title: Re: Plug-in for ecobee thermostats in development
Post by: Zoro on February 28, 2017, 12:36:16 pm
Ok. How does one open a ticket? If we have to bust balls to get a problem resolved, lets do it....

Hi Mike--

  See http://getvera.com/support/

Z
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on March 03, 2017, 09:52:28 am
Does this look familiar to anyone? This is the response I got back from support...

Type your response ABOVE THIS LINE to reply
 
Mike Yeager
Subject: Ecobee issues...
 
MAR 03, 2017  |  04:22AM PST
Ionut Sinatovici replied:
Hello Mike,
EcoBee is a third party plugin, we do not have access to it so we cannot modify or change its structure/functions. If a firmware upgrade from our side requires a plugin update, that is up to the manufacturer of the plugin. We did not change anything drastically, the plugin has to get an update from its manufacturer otherwise we cannot guarantee that a future update from us would ?fix? this issue.
Let me know if you have any questions and I will get back to you asap.
Thank you.
Regards,

Ionut ▾ Customer Care Advocate
Vera Control, Ltd. ▾ Smarter Home Control
www.getvera.com ▾ support@getvera.com ▾ +1 (866) 966-2272

How am I doing? Please email my manager, Daniel Stefan (daniel_stefan@getvera.com), with your feedback.

HOURS OF OPERATION (Pacific Time Zone, UTC−8)
Monday - Friday 12:00 am ? 06:00 pm
Saturday - Sunday 04:00 am ? 06:00 pm

HELPFUL LINKS
Web Portal: https://home.getvera.com
Platform Status: https://status.getvera.com
Order Tracking: https://shop.getvera.com/orders.asp
Customer Care Website: http://support.getvera.com
YouTube Channel: https://www.youtube.com/user/veratraining
 
FEB 28, 2017  |  02:10PM PST
Original message
Mike wrote:
I am using the Ecobee plugin and have been having issues with being forced to reauthorize the plugin. I'm told this is due to a bug that caused by the authorization token not being immediately written to storage. This has been reported several times according to the forum. Please fix. I need reliability here and other than a few minor issues, I'm fairly happy.
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 03, 2017, 10:44:39 am
Ha! My reading of the reply is that it is in no way responsive to your query.  Oh boy....
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on March 03, 2017, 11:08:25 am
My experience (I may be repeating myself) with the loss of token from the plugin is that it is related to either random luup reload and vera restart happening right at the time of the token renewal.
It is extremely annoying. The same customer support person has been trying to blame these restarts on other plugins. However true it is, it is primarily a problem with the vera firmware. The luup reload are relatively short but the vera restarts are unacceptable no matter what causes them. The response is a way to ask us to go pound sand.

If you would, install the status monitor app and you will see the last restart events. Since the last firmware update, luup reloads have occured about once every 24-36 hrs and vera restart every 48-56 hrs. I had reloads before but not restarts.

Homeseer is looking better and better by the day...
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on March 03, 2017, 01:31:06 pm
Ha! My reading of the reply is that it is in no way responsive to your query.  Oh boy....

Not in the least. They're trying to push it off as though it's the fault of the plugin. I replied that the author of the plugin was a frequent poster to the forum and that the plugin worked just fine. I also mentioned that the fault was Vera's delay in writing data to storage and that they've been made aware of this before. I told him that the author has encouraged others having this issue to contact them as "the squeaky wheel gets the grease"....

I will add the status monitor app....
Title: Re: Plug-in for ecobee thermostats in development
Post by: Juppers on March 04, 2017, 12:17:29 am
Since I fixed the errors in my config, I haven't had this problem for the last several weeks. Mine was being caused by gibberish luup in some scenes and/or the broken WAPIRZ-1 sensors in the prior firmware. I'd suggest checking all your scenes are correct with valid luup, correct modes applied, etc. My scenes didn't like the upgrade/import from UI5 and some got scrambled with the encoding changes in the newer firmware.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on March 04, 2017, 01:58:23 pm
I've already checked my scenes and all that. I install the systems monitor plugin a few days ago and so far, all I've had is a few Luup restarts. No Vera reboots as of yet...
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on March 04, 2017, 04:42:09 pm
Having a few Luup restart is pretty common though not sure it is acceptable since it basically disables the system during the restart process. It seems like my system is stabilizing a little and I can go few days without luup reload. I added a USB drive to the vera and have my logs now written on it. Totally forgot to do this when I went from the edge to the plus.
What you may notice if your problem is like mine is that every ecobee token corresponds to a vera restart. Not every vera restarts causes a token drop. The vera restart needs to be long enough and happen to coincide with a token renewal event. We are basically exposed to lose the token every time we upgrade firmware, reboot the vera or if very unlucky, when we install a plugin or save a scene because they all cause luup reloads.
On my previous firmware it was occurring once every couple of weeks. Initially after the upgrade, I saw it twice in 3 days... I am keeping my finger crossed... it seems like each zwave heal is helping for some reason. Something might have been changed in the zwave network handling on this last firmware.

Edit: Sure enough, I got a luup reload as I was writing this post...  :'(
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on March 07, 2017, 12:42:50 pm
At some point last night the plugin lost connection and I am not able to reconnect. Trying to reauthorize with a new code goes on to adding the app on the ecobee site but then the vera never seems to connect. Anybody else seeing this?

nevermind, tried again after a luup reload and it worked. After 24hrs of not reloading luup, the vera seems to be very good at corrupting itself...
Title: Re: Plug-in for ecobee thermostats in development
Post by: Kalapa on March 07, 2017, 09:04:47 pm

"Vera Mobile" app displays "Inside Temp" and UP / Down arrows temp settings with current temperature, but not showing any temp mode  ( off / auto /cool /Heat ) options. These options displaying correctly on when I access via web page in UI7..

Is this a known issue with Vera Mobile app? or am I missing any settings here?

Note : Veramate app shows all these options in mobile app,,
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on March 10, 2017, 12:45:49 am
Ok I think I am getting something consistent now. After 18hrs of absence of random luup reload, I lose connection to the ecobee server and am unable to reestablish connection until I manually reload the luup engine. If I am reloading the luup engine at some point in between then the connection appears to be able to hold another 18hrs. @Watou. Any idea what could cause this?
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on March 10, 2017, 01:57:23 pm
Mem Available  174828kilo bytes
CPU Load (1 minute)  0.16
CPU Load (5 minute)  0.2
CPU Load (15 minute)  0.17
Last CMH Reboot  07:26:58 Wed 22 Feb 2017
Last Vera Restart
Last Luup Restart  10:48:31 Fri 10 Mar 2017

This is where I stand after installing the system monitor. It's been about two weeks according to my previous post. No Vera reboots, but the Luup restarts are there. Would be great to know what's causing them and how to eliminate it. There was nothing going on this morning to cause this...
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on March 11, 2017, 11:28:01 am
Mem Available  174828kilo bytes
CPU Load (1 minute)  0.16
CPU Load (5 minute)  0.2
CPU Load (15 minute)  0.17
Last CMH Reboot  07:26:58 Wed 22 Feb 2017
Last Vera Restart
Last Luup Restart  10:48:31 Fri 10 Mar 2017

This is where I stand after installing the system monitor. It's been about two weeks according to my previous post. No Vera reboots, but the Luup restarts are there. Would be great to know what's causing them and how to eliminate it. There was nothing going on this morning to cause this...

I contacted support about it. Not sure if it is because they did something on my unit but now I am having to force the luup reloads otherwise my ecobee plugin disconnects and can't reconnect.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on March 11, 2017, 12:47:48 pm
Ok. Luup restarted at exactly the same time this morning. Not sure if that a good thing or a bad thing, but it's consistent...
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 11, 2017, 12:53:20 pm
Ok. Luup restarted at exactly the same time this morning. Not sure if that a good thing or a bad thing, but it's consistent...

It's possible that there are valid and sensible reasons for Luup to restart (don't know), but not at the expense of losing device variables written by plugins, which I believe is the root cause of losing tokens and needing to re-register a new PIN.  Hopefully someone reporting the issue gets or has gotten a responsive (instead of a nonsensical) response from support.
Title: Re: Plug-in for ecobee thermostats in development
Post by: SpecialSwell on March 18, 2017, 08:01:41 am
I'm sorry if I missed it in the thread, but didn't see anything regarding my issue....

Everything is up and running fine except mobile app. I can control the ecobee3 via desktop version but the app only shows my status. It doesn't allow me to make changes (eg: increase or decrease temperature).

I'm using ui7 latest update and I have a Vera plus.  I am using android OS.   Thanks in advance!
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on March 24, 2017, 02:59:14 pm
The mobile app unfortunately is pretty restrictive in terms what it can show or not show. I would recommend not using it and move to something else. For iOS I use Homewave.
Title: Re: Plug-in for ecobee thermostats in development
Post by: SpecialSwell on March 26, 2017, 10:32:52 pm
ah, ok.  Thanks.  Your advice worked.  I downloaded ImperiHome for android.  Great app.  Definitely needs to be customized and setup properly, but if you put the time into it .  . . . . It's really a pretty and useful app.  Already bought the paid version.  Ecobee (as well as everything else) is easily accessible and controllable.  Thanks again for the reply.   
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on March 30, 2017, 12:21:54 am
I've asked for support to look at my mysterious luup reloads and lately why a lack of luup reload can cause the plugin to disconnect and to fail to reconnect even with a new token. In the meantime v1.8 is out in the app store.   ;D
Title: Re: Plug-in for ecobee thermostats in development
Post by: ojovilla on April 20, 2017, 11:09:54 am
The ecobee vera app asks for verification at least once a week now... Very annoying.
I don't know where the problem is but I'm getting tired of all the vera issues.

Mine does this as well, did you find a solution ?
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on April 20, 2017, 02:34:59 pm
The answer, at least for me, was a plugin that I never loaded. Look and make sure you don't have the Ergy plugin. If you do, uninstall it and never look back...
Title: Re: Plug-in for ecobee thermostats in development
Post by: bohemian on May 24, 2017, 03:13:14 pm
Just a minor observation when using PLEG actions to control the Ecobee3.

The SendMessage call does not spawn a corresponding blank parameter field in the PLEG action interface. So you can't actually input any text to send.

Not sure if this is due to a PLEG limitation or something specific to the Ecobee plug-in. For now, I'm going to try just adding some appropriate LUA code (an example was shown much earlier in this thread) to the action and see if that is a possible workaround.
Title: Re: Plug-in for ecobee thermostats in development
Post by: phantomfsoc on December 14, 2017, 08:48:00 pm
I've had this working but 2 of my sensors only have Temperature and not humidity. I have another 2 that have both Humidity and Temp.
Is there a way to make the Humidity reading show up?
Title: Re: Plug-in for ecobee thermostats in development
Post by: Mike Yeager on December 15, 2017, 07:49:23 am
Unpair the sensor from Ecobee, wait 15 minutes and re-pair it. Worked for the one I had that did the same thing.
Title: Re: Plug-in for ecobee thermostats in development
Post by: prplrhd on December 18, 2017, 06:47:58 pm
New issue: anyone having problems with Ecobee plugin losing connection with the thermostat device? Have done multiple pin generation and connections, that doesn't appear to be at issue. The Ecobee site lists the Vera app connection, and Vera shows the plugin as connected.

I have a scene that runs testing CommFailure = luup.variable_get("urn:micasaverde-com:serviceId:HaDevice1", "CommFailure", 232) and alerting me if CommFailure code is returned as "1". Runs clean as well.

However, the info in Vera is not what's on the Ecobee device. It seems like the connection breaks but the Vera plugin doesn't know it and doesn't report it. The Ecobee website and app have no problems accessing the thermostat and remaining current.

Anyone else seeing this behavior?


Title: Re: Plug-in for ecobee thermostats in development
Post by: prplrhd on December 18, 2017, 10:30:03 pm
Noted that the variable "access_token" from urn:ecobee_com:serviceId:Ecobee1 is somehow getting dropped. Going in and requesting new pin, back to ecobee site to register, etc solves the problem. This was an issue some time ago... variables in the device and plugin show "registered" status, only field that seems to get reset is access_token.

01      12/18/17 19:17:52.335   LuaInterface::CallFunction_Job device 234 function SEcobee1_Ecobee1_SetClimateHold_run failed [string "module("L_ecobee",package.seeall)..."]:416: attempt to concatenate field 'access_token' (a nil value) <0x739af520>
06      12/18/17 19:19:41.713   Device_Variable::m_szValue_set device: 231 service: urn:ecobee-com:serviceId:Ecobee1 variable: access_token was:  now: 1vO09cIzWb40NEMYVmuNl7M1CGDBsDoo #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x751f0520>

Best I can do for now is set scene to monitor status of access_token and if it gets reset, send me a push notice. Hopefully Watou or others with some experience with the plugin have some ideas. I am not running the Ergy plugin so uncertain if there may be some other conflict. Running this on a VeraPlus with no other known issues.

Thanks
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on December 22, 2017, 01:20:01 pm
Noted that the variable "access_token" from urn:ecobee_com:serviceId:Ecobee1 is somehow getting dropped. Going in and requesting new pin, back to ecobee site to register, etc solves the problem. This was an issue some time ago... variables in the device and plugin show "registered" status, only field that seems to get reset is access_token.

01      12/18/17 19:17:52.335   LuaInterface::CallFunction_Job device 234 function SEcobee1_Ecobee1_SetClimateHold_run failed [string "module("L_ecobee",package.seeall)..."]:416: attempt to concatenate field 'access_token' (a nil value) <0x739af520>
06      12/18/17 19:19:41.713   Device_Variable::m_szValue_set device: 231 service: urn:ecobee-com:serviceId:Ecobee1 variable: access_token was:  now: 1vO09cIzWb40NEMYVmuNl7M1CGDBsDoo #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x751f0520>

Best I can do for now is set scene to monitor status of access_token and if it gets reset, send me a push notice. Hopefully Watou or others with some experience with the plugin have some ideas. I am not running the Ergy plugin so uncertain if there may be some other conflict. Running this on a VeraPlus with no other known issues.

Thanks

I just looked at mine and I think the token changes about twice a day yet I have not seen mine get disconnected in the past week
Title: Re: Plug-in for ecobee thermostats in development
Post by: LibraSun on March 05, 2018, 09:43:57 am
I know (both from this thread and from @watou's docs at http://watou.github.io/vera-ecobee/#SendMessage) that the ecobee plug-in was originally intended to allow users to send a text message (up to 500 characters) to the thermostat.

While I'm seeing that "SendMessage" action in the Scene > Advanced Editor > Device > Actions drop-down list, choosing it does not offer an input field for entering the text of the intended message. Nor do I see any kind of "MessageText" variable under the Thermostat device > Advanced, either.

Is it expected that users should use Luup coding exclusively to send messages this way? (i.e. with MessageText declared explicitly within the parameters of a Luup action call to the urn:ecobee-com:serviceId:Ecobee1 service?) Or can casual users like me get away with doing SendMessage a simpler way?

Thanks! - Libra

UPDATE #1:

Back to answer this question, in part: Yes, using Luup is one good way to send a message to your ecobee thermostat.

SAMPLE CODE

local deviceUrn = "urn:ecobee-com:serviceId:Ecobee1"
local deviceId = 95
local message = "This is a test"
luup.call_action(deviceUrn, "SendMessage", {MessageText=message}, deviceId)

NOTE: Replace '95' with your actual Thermostat device ID, and the message= text with your desired message text.

RESULT

The specified text message will appear both on the ecobee thermostat's display as well as a pop-up ? attributed to 'utility' (I don't know if this pseudo-sender name can be altered) ? on the ecobee.com website (and presumably the mobile app, as well?) until dismissed. NOTE: Thereafter, no record is kept of the message for later review.

UPDATE #2:
Seems these messages ("Alerts" as ecobee calls them) get posted to your ecobee account/device with a timestamp that is offset X hours from your local time zone. In my case, living in Central (U.S.), I observed the Alerts were marked exactly 5 hours earlier relative to my actual clock time, suggesting "GMT-11" or "US/American Somoa".
It's not immediately clear whether this can be adjusted by the user, as I see no corresponding Variable or setting within the ecobee plug-in. Neither is this issue in any way a show stopper, just something to be aware of when using. ;-)

UPDATE #3:
When more than one Message is broadcast via the Luup code shown above, they appear on the ecobee Web UI, in the ecobee mobile app, and on the ecobee thermostat screen itself. However, the moment you "OK" (dismiss) any Message on one platform, it will promptly disappear from the others. So, if you wish other users to see the Alerts, be sure not to click "OK". NOTE: This scenario, although rare, would also mean leaving your thermostat screen obscured by the displayed Alert(s), a potential usability obstacle!
Title: Re: Plug-in for ecobee thermostats in development
Post by: fullmoonguru on March 22, 2018, 02:33:37 pm
I'm trying to create a scene that changes from Heat mode to Cool mode depending on the outdoor temp, but I can't change that setting as part of the scene. It works fine when I'm in devices and just click on it. Anybody know what's going on with this?
Title: Re: Plug-in for ecobee thermostats in development
Post by: Don Phillips on March 22, 2018, 08:34:12 pm
I use PLEG to accomplish this.  Status report attached. I used to use a scene but it sometimes failed during a LUUP restart.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on March 25, 2018, 04:20:20 pm
@watou

will you be adding support for the switch+
it would be great to be able to turn on/off and use the temp/occupancy sensor in vera
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 26, 2018, 06:06:57 am
will you be adding support for the switch+
it would be great to be able to turn on/off and use the temp/occupancy sensor in vera

I don't see any API update since June, 2017*, and the polling nature of the ecobee "cloud" API doesn't lend itself well to supporting the switch, but if API support for the switch fits sensibly in the plugin, it should definitely be added as switch devices.  I haven't used a Vera in a long time though, so any plugin updates should be tested well by others!

* https://www.ecobee.com/home/developer/api/documentation/v1/change-log.shtml
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on March 26, 2018, 01:00:19 pm
they must have an unpublished change somewhere
as IFTTT and Alexa can both control my switch+

i would love to try and get these api changes to you
any idea who i would need to get a hold of to get the api changes?
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on March 26, 2018, 01:04:25 pm
-------------
unfortunately ifttt in vera only supports vera actions from external triggers and not the other way around
as i had considered adding a virtual switch and then making 2 scenes triggered by the switch to control an ifttt "do button"
for switch on and for switch off

apparently this can be achieved with ifttt maker triggering an external action on ifttt from a condition in vera
if anyone knows how please let me know
Title: Re: Plug-in for ecobee thermostats in development
Post by: watou on March 26, 2018, 02:14:56 pm
any idea who i would need to get a hold of to get the api changes?

Someone on their developer forum asked about it a week or two ago:

https://getsatisfaction.com/api/topics/ecobee-switch-api-plans

That seems like a good place to have asked about it, and I've followed the topic to see if/when it's answered.  I wouldn't be surprised if it doesn't fit properly into the current v1 API, and might require a server push mechanism that is not currently published.  Just guessing though.
Title: Re: Plug-in for ecobee thermostats in development
Post by: charettepa on March 26, 2018, 03:13:21 pm
i have contacted ecobee support
RE: missing updated api changes that are not published but IFTTT and Amazon seem to have

they advised they will get back to me

i will forward anything i get from them
Title: Re: Plug-in for ecobee thermostats in development
Post by: Freddy99 on May 13, 2018, 06:21:07 pm
I am having problems whereby my Ecobee thermostat temperatures are being displayed incorrectly on Vera. If the room temp is 15degrees Celsius, it is being displayed as 59degrees Celsius. I had this problem about a year ago, but fixed it by uninstalling my Nest app.
Now the problem is back and I cannot get rid of it. Is anybody else having this experience?
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on May 13, 2018, 08:39:19 pm
I am having problems whereby my Ecobee thermostat temperatures are being displayed incorrectly on Vera. If the room temp is 15degrees Celsius, it is being displayed as 59degrees Celsius. I had this problem about a year ago, but fixed it by uninstalling my Nest app.
Now the problem is back and I cannot get rid of it. Is anybody else having this experience?

This has been intermittent on the vera and has been completely eliminated when I moved the app to openLuup. From my reading of the app, it is not so much a problem with the app itself but with the vera luup reload timing not being consistent. I believe you will see it come and go each time you do a luup reload and you will see it get worse as your system gets larger. There is a function in the plugin to check your vera default temperature setting. If it runs too late in the process, it will default to F mode even though your display wlll be in celsius. The version I posted on AltAppStore defaults to C units if I remember correctly.
Title: Re: Plug-in for ecobee thermostats in development
Post by: Freddy99 on May 14, 2018, 05:35:36 am
Thank you Rafale. I was not aware of theAltAppStore. I have just googled it and loaded the altappstore_install.lua. This shows as a device. How do I now get the Ecobee plugin to load from there?
Thanks again.
Title: Re: Plug-in for ecobee thermostats in development
Post by: rafale77 on May 14, 2018, 10:04:02 am
The version on the alt app store requires you to create a dev account to get an API key. See the instructions I posted on Github: https://github.com/rafale77/vera-ecobee
Title: Re: Plug-in for ecobee thermostats in development
Post by: Freddy99 on May 15, 2018, 12:38:57 pm
Thank you. I have had a look and it looks a bit complicated. I will have another look next week and see if I can do it. Thanks again