I'd like to be able to send my Ecobee remote sensors and other temperature sensors to Alexa so I can ask her for the temperature in my rooms. Alexa can also accept contact sensors as well.
Is not a direct integration from ecobee with alexa? I have google home and nest so i have HE integrated to google home but not the nest through HE, nest is integrated directly to google home. I think you can do the same.
Maybe I'm wrong, I didn't have an ecobee to test.
You're right. I need to add the sensors via the official Ecobee app for them to show up as temperature sensors in Alexa. Interestingly though, adding the Ecobee remote sensors to Alexa via the SmartThings integration adds them as motion sensors so somehow it does make sense to add the sensors to Alexa in both Ecobee and SmartThings. Would it be possible for Hubitat to also provide motion and contact sensors to Alexa or is this because SmartThings is a partnered integration?
I don't think so, but if they integrated with ST like that, temp and motion, then probably using HubConnect (community app) you can use the thermostat and those temps and motions in HE. Actually right now I have Nest and my Honeywell thermostats in ST and shared to HE with HubConnect and from there to the dashboard. Works great.
I also have HubConnect installed and have my HE and ST hubs linked. My goal is to entirely retire ST from my home automation so I'm trying to figure out how to replace all the pieces one by one.
I prefer leaving Nest and Honeywell handling to ST, it's all cloud based anyway so less load to HE, and believe me, moving both to ST from HE hub (I had Nest native integration and TCC driver for Honeywell) and sharing them with HubConnect are working better and the hub is noticeable faster, less errors. You no need the ST hub connected for this, their cloud does the hard work.
But I understand your goal. Good luck.
Good point about the Ecobee being cloud based anyway. I use @storageanarchy's Ecobee Suite Manager on ST and it works well so I might as well keep it on ST to keep the load off of the HE like you say, at least until it's ported to HE.
1 Like
Even if it's ported to HE I prefer it consuming ST cloud, that's is the same as nest manager for ST, it's ported to HE but I use it in ST and share the thermostat to HE with HubConnect, less stress to my local CPU. 
1 Like
I may look into making a custom HubConnect Driver for my Ecobee Suite, so that you have access to the full suite of attributes and commands/api's that the Suite offers. And maybe then porting over the Helper SmartApps to HE, so that the event decisions are local and only the Ecobee API commands traverse the cloud. I'm thinking this should be more efficient for those who have most of their sensors running on Hubitat...
Thoughts / comments anyone?
1 Like
That would be amazing! Let me know if you would like any help in your porting efforts.
It now appears that HubConnect is only able to reflect up to 8 attributes from SmartThings into Hubitat, and it is currently using 7 of those 8. This would seem to mean that I can't build a custom driver for my Ecobee Suite Thermostat that would reflect ALL the attributes it currently supports.
Thus, for now, this idea will be shelved.
I continue trying to get my full Suite ported over; currently I am still stuck on the OAuth code authorization logic...
User drivers can pass 18 attributes. It was expanded a release or two ago.
Thanks, @JasonJoel
My Ecobee Thermostat DTH on SmartThings currently exposes about 150 Attributes and about 45 commands. And there are another 50 or so attributes/settings that I have yet to expose. Several of the commands require 5 arguments; the current HubConnect support limit appears to be 4.
Of course, not all are required, but I can't squeeze down to just 18 attributes. A quick survey of my code appears to require at least 40 attributes, minimum.
