Ecobee Premium is not seeming to auto-detect with Apple Homekit

Third party integrations
1

Oh, I am sure I am not the only one who wishes ill on whoever at Ecobee decided to discontinue the API in March of 2024.

I added “zeroconf:” in my configuration.yaml and I know that my new HA VM is on the exact same subnet as the Ecobee thermostat but for some reason, it is not autodetecting. Am I doing something wrong in that configuration.yaml file? It detects my Rachio irrigation controller and all my Kasa/TP-Link surge protectors even though I used their integrations. I just do not see the thermostat and I have rebooted plenty of times in the last couple of days.

# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
device_tracker:
  - platform: cisco_ios
    host: x.x.x.x
    username: ********
    password: ********
  - platform: fortios
    host:  x.x.x.x
    token:  *******
zeroconf:
2

Nevermind. I figured it out. For those of you who are in need, go to your Ecobee thermostat, then get into the settings and you should see a setting that says Homekit. It will show up as unpaired. Click on getting the code. It will be your normal xxxx-xxxx home kit code format. Once you start that, assuming you have that “zeroconf:” line in your configuration.yaml, then it discover. You add it, and then put in that code on the thermostat screen, it will bring up the thermostat and any remote sensors you have to put them in the rooms you wish in HA.

Still mad they got rid of APIs as I am not really an Apple fan.