Do You Still Need Homebridge With Home Assistant?

Short answer: most Home Assistant homes do not need both

Home Assistant can replace the main job Homebridge performs for many Apple-first homes. Homebridge translates community plugin data into accessories that Apple Home understands. Home Assistant can connect those devices, run their automations, and send selected controls to Apple Home through its official HomeKit Bridge integration.

An entity is one control or reading in Home Assistant, such as a lamp, door lock, temperature, or motion state. HomeKit Bridge publishes chosen entities outward to Apple Home. That lets the family keep the Home app and Siri while Home Assistant becomes the place where devices and automations are managed.

The similarly named HomeKit Device integration goes in the opposite direction. It brings a HomeKit accessory into Home Assistant. Home Assistant's current documentation says a HomeKit accessory can be paired to only one controller at a time, so an accessory already paired to Apple Home may need to be removed or reset before Home Assistant can claim it. You can then publish it back to Apple Home with HomeKit Bridge.

Neither Homebridge nor Home Assistant's HomeKit Bridge is an Apple home hub. Apple says a HomePod or Apple TV home hub is what enables away-from-home control, household sharing, Apple Home automations, and adding Matter accessories. You can retire Homebridge and still keep that Apple hardware and interface.

Do not unplug Homebridge today just because the answer is “usually no.” First prove how every current plugin will be replaced. The safest end state may be no Homebridge, or it may be one small Homebridge exception alongside a much larger Home Assistant system.

Choose the right path for each device

Those connection labels are simpler than they sound: local means normal control stays inside the home network, while cloud means it passes through a vendor's internet service. Push means the device or service sends changes to Home Assistant; polling means Home Assistant checks for changes on a schedule.

When you can retire Homebridge

You can normally retire Homebridge when every device family it exposes passes four checks:

• Home Assistant has a working connection. Prefer a current native integration—the direct connector built for that product or service. Use HomeKit Device or Matter when that is the appropriate supported path.
• The features you actually use are present. A light that turns on is not a full replacement if dimming, color, button events, or power readings disappeared.
• Apple Home receives only the controls the household needs. A small HomeKit Bridge include list is easier to understand than sending thousands of entities into Apple Home.
• Scenes, Siri names, and automations have been tested after cutover. A device arriving through a new bridge may have a new Apple accessory identity, even when its visible name is the same.

Philips Hue Bridge v2 is a useful example. Home Assistant's official Hue integration is Local Push, imports Hue scenes, and receives state changes instantly over the local event stream. Home Assistant's Matter documentation also uses Hue to explain why the native integration can retain richer features than the generic Matter path. If a Homebridge plugin was only making Hue lights visible to Apple Home, the native Hue integration plus HomeKit Bridge is the cleaner route.

Repeat that check for each plugin rather than declaring the whole server replaceable at once. One weak device family should not force every other accessory to keep taking the longer path.

When keeping Homebridge still makes sense

• A specific maintained plugin exposes something Home Assistant cannot. Name the plugin, the missing feature, and whether it is local or cloud dependent. “We might need it” is not enough.
• You are still migrating. Homebridge is a useful temporary source while devices, automations, and household habits move in small batches.
• You intentionally use Homebridge 2's Matter output. This can serve other Matter-capable platforms, but only participating plugins gain that path, and Homebridge says its Matter implementation is not certified by the Connectivity Standards Alliance.
• A camera, television, or unusual accessory has a proven plugin path that the new stack does not match. Test it separately. Home Assistant's HomeKit Bridge handles some of these as individually paired accessories, and camera recording remains a separate decision.

Keeping one exception is not a failure. The goal is a system whose ownership is clear: Home Assistant handles the devices it supports well, Homebridge handles a short documented exception list, and each accessory appears in Apple Home only once.

Also check cloud dependence at the plugin level. Homebridge itself runs in the house, but a plugin may still sign in to a vendor's servers. Moving the same cloud account into Home Assistant does not automatically make the device local.

A safe Homebridge-to-Home-Assistant migration

1. Back up Homebridge. Use Homebridge UI's Backup & Restore page. Its current documentation says the archive includes the configuration, cached accessories, HomeKit pairings, plugin information, and UI accounts. Store that archive securely because configuration and account data can be sensitive.
2. Inventory the current plugins. For each plugin, record the device family, Apple Home name and room, must-keep features, account or hub it uses, whether control survives an internet outage, and any locks, doors, cameras, alarms, or heating controls involved.
3. Choose one new owner for each device. Mark it as native Home Assistant, HomeKit Device, Matter multi-admin, or “keep on Homebridge.” Do not use HomeKit Bridge as the incoming device connection; it sends Home Assistant entities out to Apple Home.
4. Add and test the device in Home Assistant first. Check state updates and every important command inside Home Assistant before changing what Apple Home sees. Run a simple test automation if the device will be used as a trigger.
5. Create a selective HomeKit Bridge. Include one small test group, such as a room or device family. The existing Tara guide to HomeKit Device versus HomeKit Bridge shows which direction each integration moves data.
6. Cut over one family. Disable the old Homebridge plugin or its separate child bridge for that group before exposing the replacement accessories from Home Assistant. This avoids two “Kitchen Lamp” tiles controlling the same light.
7. Repair the Apple side deliberately. Put the new accessories in the correct rooms, confirm names, and rebuild any Apple Home scenes or automations that referenced the old accessory identity. Test Siri from more than one household member's device.
8. Move critical devices last. Keep a physical key, wall control, thermostat control, or manual door release available. Do not make a lock, garage door, alarm, or heating system the first experiment.
9. Stop Homebridge before deleting it. Leave the old host and backup untouched through several ordinary days, an away-from-home test, and a restart of Home Assistant and the Apple home hub. Remove the old server only after nothing depends on it.

What does not move automatically

A Homebridge backup is a rollback for Homebridge; it is not an import file for Home Assistant. Plugin settings, credentials, cached accessories, and HomeKit pairings do not turn into Home Assistant integrations or entities.

Apple Home also identifies the newly exposed accessory by its bridge and accessory information, not just the friendly name on the tile. Assume that room assignments, favorites, scenes, and Apple Home automations may need attention after a device changes bridge. Write down important routines before the cutover and test them from the family-facing app afterward.

Matter multi-admin is not an automation migration tool either. It gives another controller access to a supported Matter device. It does not copy room names, dashboards, scenes, or rules from Apple Home to Home Assistant.

This is why Tara recommends moving the device connection first and the automation owner second. The guide to choosing where smart-home automations should live helps separate routines that belong in Home Assistant from simple family controls that can remain in Apple Home.

Homebridge 2 and Matter do not change the basic decision

As of August 15, 2026, Homebridge's release page lists version 2.3.1 as current. Homebridge 2 can optionally publish supported plugin accessories through Matter as well as HomeKit. The project says this is enabled per bridge, plugins choose whether to publish Matter accessories, and the implementation is not certified by the Connectivity Standards Alliance. A controller may show an uncertified-accessory warning.

That is useful progress, but it does not mean every Homebridge plugin now has a complete Matter route. Check the current Matter-plugin list and the exact plugin's documentation before relying on it.

Home Assistant's Matter integration has a different job: it controls Matter devices and can join a device that was shared from another platform. Its documentation does not describe a general way to publish arbitrary Home Assistant entities as Matter accessories. When Apple Home is the destination for ordinary Home Assistant entities, HomeKit Bridge remains the direct supported path.

For a real Matter accessory already in Apple Home, multi-admin may be cleaner than removing and pairing it again. Follow Tara's Matter multi-admin guide and check whether the device keeps the features you need in both controllers.

Six mistakes that make this migration painful

• Exposing everything: start with an include list, not every entity Home Assistant knows.
• Running two Apple paths for one device: duplicates create ambiguous Siri names and fragile scenes.
• Assuming local software means local control: check whether the documentation says Local Push, Local Polling, Cloud Push, or Cloud Polling, and note any vendor login requirement.
• Confusing HomeKit Device with HomeKit Bridge: one brings an accessory into Home Assistant; the other sends an entity to Apple Home.
• Deleting before backing up: a rollback is useful only when the old configuration and host still exist.
• Starting with safety-sensitive devices: prove the process on a lamp or sensor before a lock, garage door, alarm, or thermostat.

Cameras deserve their own check because live view, motion events, two-way audio, and recording are separate features. Tara's guide to Home Assistant and HomeKit Secure Video explains why moving a camera tile does not automatically move its recording path.

Tara's practical recommendation

If Homebridge is mainly there to make devices visible in Apple Home, and Home Assistant now has stable connections for those devices, migrate them in small groups and retire Homebridge. Keep Apple Home as the household interface if the family likes it. Keep the Apple home hub for Apple remote access and sharing.

If one Homebridge plugin remains uniquely useful, keep that one bridge with a written reason and no duplicate accessories. Review it during normal maintenance instead of letting an old server become invisible infrastructure.

If you want the controller, bridge boundaries, local-versus-cloud paths, and Apple handoff planned as one system, Tara's configured Home Assistant setup is the closest service path.

Frequently asked questions

Can Home Assistant replace Homebridge?

Usually. Home Assistant can connect many devices through native integrations or HomeKit Device, then expose selected entities to Apple Home and Siri through HomeKit Bridge. Keep Homebridge only for a specific plugin or feature that your tested Home Assistant path cannot replace.

Can Home Assistant and Homebridge run at the same time?

Yes. They can coexist during migration or permanently. Give each accessory one owner and one route into Apple Home; exposing the same light, lock, or sensor through both systems creates duplicates and confusing automations.

Do I have to stop using the Apple Home app?

No. Home Assistant's HomeKit Bridge can send selected Home Assistant entities to Apple Home, so the family can keep the Home app and Siri while Home Assistant owns device connections and automations.

Must I remove a HomeKit device from Apple Home before adding it to Home Assistant?

Yes when you are pairing that accessory through Home Assistant's HomeKit Device integration, because a HomeKit accessory can have only one controller. A Matter device can instead be shared to another controller through Matter multi-admin when the device and platforms support it.

Does Homebridge 2 Matter support make Homebridge necessary?

No. Matter support is optional, plugins must support the path, and Homebridge says its Matter bridge is not certified by the Connectivity Standards Alliance. Keep it only when that exact bridge or plugin solves a tested need that Home Assistant does not.