Ecobee and HomeKit Device Integration

Hello,

I have 3 Ecobee thermostats and have been using the Ecobee integration. I wanted to convert to using the HomeKit Device Integration to keep things local. My Ecobee3 was discovered and I was able to connect it just fine.

However, my 2 Ecobee4’s are not being discovered. I do not have any other Homekit hubs, no Apple Hub or Apple TV.

Any tips or suggestions to get them to be discovered?

Thanks

2 Likes

I’m in the same boat. Ecobee’s developer feature is broken (I already have a developer account, but the “Create App” feature isn’t working). One of my four thermostats was discovered as a Homekit device. :expressionless:

Fortunately I’ve had all mine connected through Ecobee for a while. Was just trying to get it local. I haven’t found a way to get it recognized yet.

I finally got it to work. On my EcoBee 4’s I had to go through the menus and enable Homekit pairing.

Hit the hamburger menu on the main screen.
Hit the gear to enter the options
Scroll to the Settings option and press that
There will be a HomeKit entry hit that.
There is an option to Enable HomeKit pairing.

After that HomeAssistant discovered the devices.

4 Likes

Thank for posting this, I was able to quickly connect my new ecobees (swapping from Nest with a new HVAC system) thanks to this note.

How did you guys get this to work? Mine, upon going to the Homekit Pairing section, provides me with a QR code and says “scan this with your ios device” essentially. I have checked in HA while it’s waiting for the QR code to be scanned, but it never gets discovered.

I originally had the Ecobee integration set up and had ignored the Homekit discovery of the Ecobee. Could that be the case for you? Maybe check and see if you had ignored it.

Once I removed the Ecobee 3 from the ignore list it was discovered right away. For my Ecobee 4’s, once I enabled it as I outlined in a previous post, it was discovered in a matter of seconds. So not sure what’s going on in your case.

I’m seeing the same when trying to add it today. I see a pairing screen, and I’m checking in HA but the device is not being discovered. I also tried adding the HomeKit Device integration, which started the config wizard, but found no devices.

My ecobee is connected to my WiFi because I can access it via the ecobee app. But I’ve never paired it with HomeKit before.

And I haven’t previously “ignored” the ecobee either (it’s never been “discovered” by HA).

Mine is an Ecobee Thermostat Premium (this ecobee page helped me figure out my model). So maybe that’s part of it?

I am having the same issue with a new ecobee 3 just installed today.

I’m thinking of registering with my teenager’s iphone and then de-registering it to see if that works. I think there is also an ecobee app that we could try to register and then delete…

Just got it to work, via automatic detection. I have two access points on my wifi network (an Asus wireless router and an additional ubiquiti access point). Surprisingly connecting it to my main asus router didn’t work but connecting it to my additional access point did.

Leads me to believe it is some sort of routing issue (mdns?)

Hope it works for you…

I am also trying to get my ecobee 4 premium and my ecobee 3 into HA. Both are available in homekit for me. I added the homekit bridge but didnt find the thermostats.

Do I need to remove them from homekit and start over?

I do see ecobee in HA as discovered but I cant get an API key since ecobee broke it.

Oof, i could really use some help here. I added my Ecobee to Homekit but it is not discoverable by HA. It is not connected to any other apple device.

Try unpairing the ecobee from homekit. Make sure that the ecobee is on your wifi network, the same network as Home Assistant. Now enable homekit pairing on the ecobee. The Ecobee should now show up on the Home Assistant > Settings > Integrations Page as a new discovered Homekit device. Select the newly discovered device and you should see a prompt for entering the pairing code shown on the Ecobee display.

3 Likes

Did you end up removing from HomeKit so it would be discovered in HA? Mine was added to HomeKit first, but it’s not showing in HA.

I connected my Ecobee 3 thermostats to HA today and when I use HA to switch the mode to heat the thermostat display shows a version of the heat icon that I have never seen before (picture below). Anybody else have this? Is it an auxiliary heat mode or something similar? It doesn’t happen when I switch to heat from the Ecobee app. Thanks all!

I was experiencing the same issue of attempting to add the EcoBee (mine is an ecobee 3) via HomeKit integration, but the HomeKit integration failed to find the thermostat. I discovered what my issue was and wanted to share in case anyone else is bumping into the same under this setup:

I am running Home Assistant container in PodMan via systemd in Arch Linux, using a Quadlet file, as described in the Home Assistant → Podman section of the Arch wiki: Home Assistant - ArchWiki.

I had originally used the quadlet configuration as specified in the wiki, but on a later read-through, I noticed the NOTE: that mentioned HomeKit discovery and I had to update the Quadlet file as described:

#PublishPort=8123:8123
Network=host
PodmanArgs=--privileged

And then perform the operations systemctl daemon-reload and then systemctl restart homeassistant.

Hope this helps someone stuck in the same boat.

Hi!

New Essential owner here (great deal from my NatGas company). I have it online and paired to HA with HomeKit. Was curious, what all should I turn off on the Thermostat for HA to have full control via its automations and such… or is the general consensus to just allow the EcoBee to do that work?

Let me know!

Has anyone else noticed that the ability to trigger a specific schedule is now returning 500 server error. It only seems like setting Away schedule and resuming the current schedule are functional.

I’ve had a number of home automation connected thermostats in the past. Most of them were “high touch” from my home automation system in terms of getting advanced functionality to work… meaning they offered very basic controls… Modes, set temp, set humidity in one case… and fan.

The ecobee is the opposite of that. It does a lot on its own, at least for my purposes, and it does it well especially with the ecobee app

  • Can run the fan X minutes an hour on its own
  • Schedules work well and easy to do from the app
  • Can easily set a vacation away mode and when I’ll return
  • Uses averages between all used sensors to keep the whole house as close to setpoint as possible
  • My power utility has a staggered pricing schedule… I’ve told the ecobee what that is, and it manipulates A/C around that: Cool off a little extra before the period, let it get a little warmer during and then quickly back to normal afterwards

Now my only HA use is manual fan control (HA HomeKit hub) to back up room vent fan cycles when the humidity is high

Very much - save your self work and let it do its thing as much as possible