@storageanarchy could you look at this thread. I cannot use the thermostat tile in a dashboard for my Ecobee thermostat. It does not function. I used the method mentioned here and I am now able to update in the dashboard. This seems to only effect dashboards in a browser as I never had an issue using the HE mobile app
According to @bravenel a driver update is required.
An exemplar of how to do this correctly can be found in the public repo Virtual Thermostat driver:
I have three Ecobee thermostats in my house. Today I upgraded one of them to the Ecobee Premium. Ecobee App and Homekit reflect the newer thermostat. I then went into the HE Ecobee Suite app and selected the new thermostat (had a slightly different name from the prior one), and the old one was no longer listed. I then re-selected the new sensors.
However, HE devices were NOT removed and created to reflect the configuration change. How can I sync the new Ecobee config with the HE device list? The github readme seemed to indicate that was managed automatically.
I have not tested Ecobee Suite with the Ecobee Premium, so I don't know if it works seamlessly or not.
Are the old sensor and thermostat devices still showing in Hubitat devices? If so, delete them manually. Then check to see if the Test devices still exist - delete them manually as well. Then try adding the new thermostat and sensors to ES again...
Thanks! I removed the lingering devices, then fiddled with the Ecobee Suite device list, and now everything is good. Picked up the Premium thermostats and sensors with no issues. Thanks!
Again my apologies for the silence. My wife & I have been travelling & RVing a lot this last 9 months or so, and I haven't had much time for my coding hobby.
Fixes & enhancements:
fanSpeed setting. Current value is reported in the attribute fanSpeed, and there is a new command setFanSpeed(speed) where 'speed' is one of ('low', 'medium', 'high', 'optimized'). Note that this only does anything if your HVAC and Ecobee both support changing the fan speed.supportedThermostatModes and supportedThermostatFanModes JSON_OBJECT attributes so that they work properly with Hubitat 2.3.3 and later dashboards & Rule Machine. This should also improve Apple HomeKit support if you expose the Ecobee Suite thermostat device to Homekit (instead of using native Ecobee integration with Homekit).Files Changed:
Because SmartThings has deprecated and terminated support for 3rd party Groovy-based apps and devices on their platform, as of today, Ecobee Suite's SmartThings support is suspended.
There will be no more verification of the code on the SmartThings platform (it isn't even possible) and I will begin removing all of the multi-platform code from Ecobee Suite so as to further optimize for the Hubitat-only environment.
This should not impact existing Hubitat users, and I will be taking some time to verify that I don't screw things up whilst "purifying" the code...
Update just released, thanks for raising the issue.
Thanks so much! Worth the wait.
I kinda don't care because I can do what I want (set stat to low and high)...but reporting for completeness. Again, I really appreciate you adding this functionality. My ecobee is set up with a 2 speed fan and I have Low, High and Optimized as my options in the thermostat.
If I use the setFanSpeed I end up with the following in thermostat:
low -> Low
medium -> High
high -> Optimized
optimized -> Optimized
Welcome back @storageanarchy! Do you have any plans to add flair vent support to ecobee suite? It seems they have an open api.
Half of my Keen vents stopped working with constant flashing red led’s saying they are jammed and they don’t seem to be available for replacement for the past year. The native flair app actually works quite well coupled with ecobee suite, but I miss the ability to 1) open the vents for fan operation and then retun them to temperature dependent state when the Heat/Air conditioning switches on and 2) set partially open states rather than fully open/closed.
Hi, I upgrade to Ecobee Suite Manager 1.8.56 and I am no longer able to control my Ecobee's thermostat modes.
It was working perfectly with previous versions
I also update to HE platform 2.3.4.119 today. Not sure if that is related to my problem.
I will look into it tomorrow…pretty sure I’m just passing the string to the API, as per the documentation.
No current plans, as I don’t have any way to test them… That said, the “dimmer” mode of the Smart Circulation Helper might work for you…
The code is correct as written - fanMinOnTime is the "fan minutes on per hour" setting on the thermostat that we are adjusting, and this fragment is checking whether it can be increased without exceeding the user-configured maximum for this app.
It appears that the Ecobee server is installing a different value than supplied, in pseudo-random fashion. However, I have found that if I set the parameter twice in a row, the second one appears to reliably be accepted.
As a test, could you try sending two setFanSpeed() requests back-to-back? If that works, I'll look into having the code send the request twice...
Hello... I have an item to report for your use during debugging. The "auto" function was fine during the summer and now that heating season is upon us, I just noticed that HE wasn't working. I'd prefer to just turn the Ecobee's to Auto or ON. Even changing to HEAT or COOL, returns the same error. See logs from just now.
Maybe there is a way within webCore to more explicitly direct the Ecobee to use Auto mode. If there is can you share tips on how to do that?
PS. I have updated the Ecobee suite and HE to latest versions.
You may have found a bug - give me a few minutes to do some digging...
Fix posted - get the 1.8.25 version of ecobee-suite-thermostat from the github repo...
Thanks for finding this...
Download the Hubitat app
