i don’t know if ecobee can relay this information as an entity, or not, but it would be very useful to be able to pull it into an automation as a trigger. ecobee thermostats with presence sensors should have an occupancy entity available when using the ecobee integration in home assistant. but my ecobee 3 has an occupancy entity in home assistant. but there may be some use cases where the ecobee presence sensors would be usable in automations. to my knowledge, if your ecobee 3 lite has one or more of those “motion + temp” remote sensor accessories, you would get those occupancy thing. not sure if this being a configuration thing, or it is not available in api to being with, or just not available via ha integration. if ecobee has it available to read in their api, that would be excellent to have in ha. it would be very useful to grab this sensor for intruder detection when the home isn’t occupied, and to trigger automations. (i have another one upstairs to control the central air, which is an entirely different system from my boiler) ecobee responded that the thermostats would never be able to read each other as room sensors do.
i intend to work around this in home assistant via automations or node-red. but from looking at the history of my ecobee sensors, the thermostat occupancy entity state appears to be independent of the remote sensors occupancy state. the top is the thermostat, and the rest are remote sensors. this also give you an idea as to how infrequently the ecobee occupancy state changes. what is your ecobee model – 3, 3 lite, 4, smartthermostat (aka 5th gen)? i was curious as to what exactly this data looks like from the ecobee api. running the api directly to get sensor information, shows that in addition to the remote sensor info, the thermostat info is returned… i found this remark back from 2017. ecobee occupancy sensors are gone? all my remote sensors show up as occupancy but it didn’t pick up any of my thermos. edit: so doing more research, the issue for me is i’m on an ecobee 3 lite. i was confused because the ecobee app actually says (unoccupied) making me believe it did.
i’m trying to set up an automation to change the ecobee hvac_mode, not the away mode, based on current external temperature. if you are currently testing this automation while the sensor is already above 32, the automation will not trigger. i see owm pulling metrics as expected, and i see the ecobee state updated as expected, but i’m guessing the actual automation trigger just took a while to fire off? it should be the precise moment when you manually triggered the automation. if you use the homekit_controller integration, commands between home assistant and the thermostat are local and instantaneous (i.e they don’t use ecobee’s cloud service). it is not a local api so relies on the web.
i didn’t even see that on the integration page, and that’s a great piece of info going forward. you buy a homekit accessory (like an ecobee thermostat) then use the iphone or ipad to scan the accessory’s homekit code (printed on the device itself and/or an accompanying sticker). that “pairs” the accessory to the iphone. to pair the accessory to home assistant, you have to manually enter its homekit code (i.e. if you have a homekit accessory that is already paired to an iphone or ipad, you first have to un-pair it before you can pair it with home assistant. all of my ecobee switch+ devices are paired to my home assistant instance via the homekit_controller integration. and if i’m following the logic and functionality, i should be able to parse the functions that need more immediate actions(hvac mode changes, thermostat temperature changes) via the homekit_controller integration, and use things that aren’t time-sensitive through the climate.
to get your ecobee notifications working with home assistant, you must first have the main ecobee integration loaded and running. once you have that configured, i walk by my ecobee thermostat all the time and its screen changes. i don’t know if ecobee can relay this information as an entity, or not, i’m trying to set up an automation to change the ecobee hvac_mode, not the away mode, based on current external temperature., ecobee thermostat, ecobee thermostat, ecobee local api home assistant, ecobee developer, home assistant ecobee homekit.
hello,i’m new to the ha platform, another refugee from the decommissioning of the smartthings v1 platform.while i could just put the actions directly how to configure ecobee thermostat in home assistant step 1: generate ecobee api key step 2: create api key step 3: add ecobee integration. home assistant configuration reboot home assistant you will see a new notification saying “click button to configure ecobee” click on that, ecobee integrations, home assistant ecobee resume schedule, ecobee developer login, ecobee.com api key, ecobee developer login not working, home assistant ecobee occupancy sensor, ecobee login, ecobee developer api, ecobee authorize app, ecobee disable 2fa.
When you try to get related information on home assistant ecobee automation, you may look for related areas. ecobee thermostat, ecobee local api home assistant, ecobee developer, home assistant ecobee homekit, ecobee integrations, home assistant ecobee resume schedule, ecobee developer login, ecobee.com api key, ecobee developer login not working, home assistant ecobee occupancy sensor, ecobee login, ecobee developer api, ecobee authorize app, ecobee disable 2fa.