thanks for your plug-in!
- 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.