Not on Hubitat. On the ecobee website. Is that where you did it?
I also removed the sensor from the thermostat and re paired it and still not showing up.
Did you go into âMy Appsâ in you Ecobee account and remove Hubitat from the list of authorized apps?
It doesnât work on mobile, you need to do it from computer.
Yes I did, and waiting another 5 minutes still only 2 sensors are showing up. I deleted the app inside hubitat also nothing is helping
Not sure why itâs not working for you. I notice in your screen shot that the sensor shows unoccupied. You might try removing the authorization on the Ecobee site, then walk in front of the sensor so it says âOccupiedâ and then re-authorize from the hub.
Itâs possible that the sensor may take a day or so to be added to the cloud API on there side before itâs available. But I really donât know that for sure. How the Ecobee API behaves is out of Hubitatâs control. Theyâre just hooking into it like any other manufacturer dose.
OK i will wait a day and try again, thanks for the tips and tricks, its much apricated
I don't know if they'll be of any help, but you could explain the situation to Ecobee if they're still not there tomorrow. They are very helpful on hardware install, but I have no experience with how well they support their API. The hub certainly can see the first two devices on your thermostat, so there's no question that the Hubitat team didn't do their job correctly. What the API is exposing is therefor a function of their cloud service.
I have an Ecobee 4 and was hoping to turn on lights when it detects motion.
Do Hubitat drivers support the scenario, if ecobee version gt 4 then expose motion sensor as virtual device?
I know there's Ecobee Suite but that's the only feature I need
Yes, the Hubitat Ecobee integration does create child devices for each Ecobee sensor device. However, the performance is not all that great, as Hubitat has to poll the Ecobee cloud for updates. Also, I have not found the Ecobee sensors to be all that robust in detecting motion. YMMV, of course.
If I recall correctly, they only report once every 30 minutes.
Yup.
Even using the local homekit protocol (separate from Hubitat) it can take a couple minutes for the SmartSensors to send a motion report. One quick test of the actual thermostat seemed faster. Maybe I'll try to test this out...
UPDATE: The motion sensor built into the thermostat acts mostly like a standard motion sensor. It's not very sensitive and therefore a bit slow to detect when entering the room. It also won't see small movements if you're sitting mostly unmoving (reading, etc.) in the field of view. This is likely to avoid false triggers from pets and the like. Reset time to inactive is fixed at roughly 5 minutes.
Thanks, hopefully a newer Ecobee version would implement Zigbee/Matter.