Moving from HomeKit YAML to HomeKit Integration

Is there a recommended way to move from the YAML configured HomeKit bridge to the configuration through the integrations page?

I would like to be able to manage my included domains and entities via the GUI (much like I do for the Alex and Google integrations) but I’m currently configured via YAML. When I click the “options” link in the integrations page I was getting a pop up indicating that the component is configured via YAML.

To try and get around this I removed the configuration from YAML and restarted and I had the same message so I followed the instructions in the docs to reset the component and I deleted the integration and then added it again.

After deleting and adding again I can select the included domains but I can’t get the GUI to filter down to the entity / domain level even though the pop up says this:

“You will be able to select which entities to exclude from this list on the next screen.”

I would like to start over with the integration. Is there a way to do this? I tried rebooting HA and the integration just kept showing up again.

I also have an issue with the entities showing as unavailable in HomeKit but I think that’s because things are in a bad state at the moment.

Maybe this will help:

If you need to use the entity_config , ip_address , or advertise_ip configuration options, HomeKit Bridge must be configured via your configuration.yaml file

Thanks for the reply. I read that but I’m not using those options and the GUI makes it clear that you should be able to select the entities to include:

image

1 Like

Personally I don’t think the current UI to manage domains and include/exclude entities for Homekit is up to the job especially if you have a LOT on entities you need to exclude. The layout of entities in a drop down does not lend itself to this task. They need to be laid out similar to how you choose entities to expose to Alexa (along with in page filters), this would also keep consistency.

Until changes are made to improve this I think I may have to switch back to yaml config.

2 Likes

I’ve done the same.

I have configured 2 HomeKit bridges. One basic version with all the domains that can be easily setup in the UI integration, this will make sure that any of these devices will automatically appear in HomeKit when they are added.

And an advanced version that only contains entities that needed a specific configuration in yaml. By doing this I am also way below the limit of 150 devices again for each bridge.

1 Like

Interesting, that’s a good way around it :slight_smile:

Do you happen to have a YAML sample of how you setup the dual Home bridges? Can’t get mine to work and read somewhere i may need to define them on two ports. Thank you!

I only have one setup in yaml, for the other one I use the UI.

I started with my HomeKit bridge in UI mode and would like to move at least some devices over to YAML. It looks like the includes and exclude options in YAML are much more comprehensive, especially with globbing. It would definitely help to take advantage of that for filtering in my setup.

Is it possible to move paired devices between the UI and YAML without having to unpair and repair in the Home app?

I’m trying to avoid having to set a bunch of other dependent things like automations up again.

Does anybody know if you setup a TV through the UI which features in feature_list are used if any?
I want to enable Menu, mute, etc. in the Remote app. For now I can only go back, get information and play/pause.