With the ecobee suite, I am using the thermostat as a motion sensor. Could that be integrated into Hubitat? It's not available. Is there a way to enable this enhancement so we can use it with the thermostat? I use the thermostat's motion sensor in some of my rules, and I'd prefer not to add another sensor. Would this be feasible?
I appreciate your help.
I'm confused. You say you use it in rules and then ask for it in hubitat. Can you clarify?
Today I use the Ecobee Suite, which lets you use the thermostat as a motion sensor too. Today, I use them as part of some of my rules with other sensors. I have decided to move to Ecobee Integration, but I noticed the Thermostats cannot also be used as motion sensors. Is it possible to change that? It is capable,
Are your referring to Hubitat’s built-in Cloud Ecobee Integration?
Or, are you referring to Hubitat’s built-in HomeKit Controller integration that allows for direct, local control of an Ecobee thermostat over the LAN?
I'm assuming that this is it. It required me to log in to Ecobee.
I'm not familiar with HomeKit Controller Integration.
I am not sure that the Hubitat team is focusing too many resources on that original Cloud Ecobee Thermostat integration. But who knows? ![]()
This is only available on the C8 Pro hubs. Hubitat’s first two major devices supported by the HomeKit Controller integration were the Ecobee thermostat and the Aqara FP2 sensor. But, I am not sure if it supports the thermostat’s internal motion sensor.
I don't believe it is exposed over Homekit. At least it's not exposed when the thermostat is directly paired to Apple Home, or when it is paired as a Homekit device to HA.
Definitely exposed to Homekit. And shows up in HA. I was looking at the wrong place.
How about Home Assistant (why not to add it to your setup)?
I am using HA + HADB for adding many devices to HE which aren't supported directly by HE. Ecobee tstat plus 5 sensors are working perfectly fine and integration is 100% local.
I use the community Ecobee suite by Sandood and it allows you to set up the thermostat as a motion sensor. It's only mildly useful as it has a long persistence time.
[Edit]after re-reading your post, I am confused as well. You say you use it in rules but then ask how you use it in Hubitat.
I have the thermostat today to detect motion in the locations where they resided. I'm looking to reduce overhead (as discussed in the EcbeeSuite thread and given that it isn't being developed) and move toward a lighter-weight approach with better platform support. However, since Ecobee integration doesn't detect motion, those rules will not work. With the included Suite functions, I can create rules for those.
It sounds like I'm stuck between a rock and a hard place.
Motion does not show up in current states for the built-in Hubitat Ecobee HK integration. Motion is available in the user Ecobee Suite integration.

Thanks for checking that out. At that point, it's in the suite and not in the built-in intuition. I like to move to something better, supported, and with potential firmware updates as needed. The only choice is use the ecobee suite, which no longer gets updates.
FWIW, I'm using the built-in HomeKit integration on my primary hub. On a second meshed C7 reserved for a few misbehaving children I'm running Ecobee Suite and sharing via hub mesh only Ecobee thermostat as a temperature sensor which is not available on either of the built-in standard and HomeKit integrations. I don't need motion but that would be available that way as well. Maybe with the end of Suite the @Hubitat_Staff will see their way clear to add a few more Ecobee attributes to the built-in apps.
Thanks! That is how I'm set up today. I put all/Most of my IP/Cloud-based stuff on my C7 (EcoBee Suite, OwnsTrack, Weather, Echo Speaks, etc.). I use my C8 (Not the Pro) for Rules, WebCore, Zigbee, Matter, Zwave and HomeKit (not much there). A clear path forward would be great. Those are some of the challenges I see in home automation today.
FYI, using the system provided HomeKit Integration, my Ecobee Smart Thermostat Enhanced creates three children, Thermostat, Motion, and Presence, for the main unit.
My Ecobee Smart Thermostat Essential (older/cheaper) ONLY has the thermostat device, no children.
Good to know. My five year old Smart Thermostat with Voice Control creates no children in the HomeKit integration.

