The Real homeOS Risk Is Not Homebridge. It Is What Apple Does With HAP.

After looking into Apple’s rumored homeOS, I had a question that matters considerably more to me than what the new display looks like.

What happens to Homebridge?

A large part of what makes Apple Home useful is everything Apple never officially supported. Homebridge lets perfectly good hardware participate in Apple Home through plugins, local APIs, reverse-engineered protocols and community integrations.

If homeOS represents a new smart-home architecture rather than simply another Apple device, it would be easy for tools like Homebridge to get stranded.

So I went looking for evidence that this is happening.

I found almost the opposite.

HomeKit, HAP and Apple Home are not the same thing

This distinction is important.

Apple Home is the ecosystem and user-facing experience.

HomeKit is the framework and data model applications use to interact with homes, rooms, accessories, services, scenes and automations.

HAP, the HomeKit Accessory Protocol, is one way devices communicate with that system.

Matter is now another.

Apple explicitly designed Matter this way. When Apple introduced its Matter architecture, it described Matter as a parallel protocol underneath the existing HomeKit framework. The idea was that applications could continue using the HomeKit APIs regardless of whether the accessory underneath was speaking HAP or Matter.

That architecture is still present today.

Apple’s developer documentation, updated in 2026, still has separate sections for developing HomeKit accessories and Matter accessories. It still documents the HomeKit framework, HAP accessories and third-party bridges.

That changes how I interpret homeOS.

homeOS does not currently look like a replacement for HomeKit.

It looks like another operating system that consumes Apple Home.

The homeOS reporting actually mentions HomeKit

None of homeOS has been officially announced, so there is an important line between evidence and rumor here.

What we know from Apple’s software is that identifiers associated with the rumored home hub, including J490 and J491, are appearing in macOS 26.7. Apple’s code also references Pebble, which has previously been associated with the homeOS project.

The reporting around the device says one of its primary functions will be HomeKit accessory management.

That is a significant detail.

If Apple were building an entirely new incompatible smart-home stack, I would expect to start seeing a corresponding replacement framework, migration APIs or developer documentation.

I cannot find any of that.

Instead, Apple’s current documentation continues to invest in HomeKit, Matter and bridges while the rumored homeOS device is described as another controller for those accessories.

My current read is that homeOS sits roughly where tvOS does today.

It is another operating system capable of participating in the home, probably with a much more ambitious interface and a much larger role for Siri.

The protocol transition is happening underneath it.

That transition is from HAP toward Matter.

Homebridge saw this coming

This is where the investigation became much more reassuring.

Homebridge 2.0 shipped on May 4.

Matter is now built directly into Homebridge.

A Homebridge installation can continue exposing accessories through traditional HAP, expose them through Matter, or operate with both transports.

Homebridge’s current Matter documentation goes even further.

Plugins can explicitly implement native Matter accessories, and the Homebridge UI now identifies plugins that support Matter directly.

But a plugin does not necessarily have to be rewritten for Matter just to survive.

The Homebridge documentation says ordinary plugins that produce HAP accessories can be bridged into Matter by Homebridge itself. Plugins implementing Matter directly are doing something more specialized.

That is enormous.

It means Homebridge is becoming a translation layer rather than merely a HomeKit emulator.

Today the path can be:

device → Homebridge plugin → HAP → Apple Home

But Homebridge is building another path:

device → Homebridge plugin → Homebridge → Matter → Apple Home

And plugins designed specifically for Matter can skip the intermediate HAP model entirely.

That is exactly the architecture I would want Homebridge to have going into homeOS.

Apple still officially supports bridges

There is another encouraging piece of evidence.

Apple’s current HomeKit documentation explicitly describes bridges as a supported accessory type.

Apple defines a bridge as something that provides HomeKit access to devices that cannot communicate with HomeKit directly. Accessories behind that bridge are added to the home and otherwise behave like ordinary accessories.

Matter supports bridges too.

That matters because Homebridge isn’t exploiting some accidental loophole in Apple’s architecture. Bridging incompatible device ecosystems is an intentional part of both models.

Homebridge is essentially the software realization of exactly that idea.

Matter is not ready to replace everything yet

This is where I would not start converting an entire house just because Matter is newer.

Homebridge’s Matter implementation is still developing rapidly.

Its current documentation explicitly describes the implementation as uncertified, which means controllers may display warnings or limit features that require certification.

There are also semantic differences between HAP and Matter.

HAP has accumulated years of accessory types, characteristics and vendor-specific extensions. Matter’s device model is still expanding. Translating something into Matter does not guarantee that every obscure characteristic or plugin-specific capability has an equivalent representation.

The Homebridge project is actively working through exactly these problems.

Recent releases have been adding and fixing Matter support for power measurement, batteries, water valves, robotic vacuums, switches, thermostats and composed accessories.

So I would consider Homebridge’s Matter path a very important insurance policy.

I would not yet consider it a reason to turn off HAP everywhere.

Home Assistant has a different problem

I also looked at Home Assistant because it provides another useful test of where the open smart-home ecosystem is heading.

Home Assistant is investing heavily in Matter. Its new Matter server is built on matter.js, the same open-source implementation used by Homebridge, and the Open Home Foundation now stewards that project. Matter is already running in 38 percent of Home Assistant installations.

But there is an important difference.

Home Assistant’s core Matter integration is currently a Matter controller, not a Matter bridge.

Home Assistant explicitly says it cannot currently take arbitrary devices already represented inside Home Assistant and expose them outward as Matter devices.

Its built-in way of sending Home Assistant entities into Apple Home is still the HomeKit Bridge, which speaks HAP. That integration remains actively documented and is used by 17.2 percent of active Home Assistant installations.

So if Apple eventually eliminates HAP completely, Homebridge may actually be better positioned today for that particular transition than Home Assistant’s built-in Apple bridge.

I expect that gap would close long before HAP disappeared, especially now that both projects are working around the same matter.js foundation.

But it is something worth watching.

Apple has shown that it will retire old Home architecture

There is one reason I am not willing to say none of this can break.

Apple ended support for the previous Apple Home architecture on February 10, 2026.

Users who had not migrated could lose access to their home until they upgraded.

So the argument that Apple would never force a smart-home migration because it might break people’s existing setups is demonstrably false.

They will.

But that migration is also useful evidence.

Apple changed the underlying Apple Home architecture without eliminating HAP accessories or third-party bridges. Current Apple documentation published after that cutoff still supports both HAP and Matter.

That is the pattern I suspect we will continue to see.

The Home architecture changes.

The controllers change.

The HomePod and Apple TV evolve.

homeOS gets added.

Matter becomes increasingly important.

HAP slowly becomes the compatibility layer for the enormous amount of existing HomeKit hardware already installed in people’s houses.

I think Homebridge survives homeOS

There is no evidence right now that homeOS is designed to lock Homebridge out.

There is substantial evidence pointing the other direction.

Apple is still maintaining HomeKit.

Apple deliberately placed Matter underneath the HomeKit framework.

Apple still documents third-party bridges.

Matter itself supports bridging.

And Homebridge has spent 2026 turning itself into a dual HAP/Matter platform capable of translating existing accessories into the newer protocol.

That makes me much less worried about losing Homebridge.

The thing I want to watch now is HAP.

If Apple begins removing HAP language from developer documentation, stops accepting HAP accessories in new versions of Apple Home, removes HAP support from future home hubs, or starts exposing new device categories exclusively through Matter, those will be the signals that the real migration has begun.

Some of that last part is already happening. Matter is increasingly where new device types are appearing.

That is not necessarily bad.

If an open protocol eventually replaces Apple’s proprietary accessory protocol while projects like Homebridge remain free to bridge old hardware into it, that could actually leave us with a more open smart home than the one we started with.

But I don’t want Apple deciding which perfectly functional devices in my house get to survive the transition.

Homebridge is one of the tools that keeps that decision in my hands.

Right now, it looks like its developers understand exactly what is coming.