Homebridge 2.0 adds Matter support

Homebridge is one of those glue tools smart-home people quietly depend on. It takes devices that were never meant to work with Apple Home and makes them show up anyway. Now Homebridge 2.0 is trying to do the same trick for Matter — the newer standard that is supposed to let Apple, Google, Amazon, and Samsung all speak the same smart-home language. The change landed on May 4, and it’s real, but it’s also early. (thechels.uk) ### What is Homebridge actually for? Homebridge is an open-source Node.js server that sits on your network and translates between smart-home devices and Apple’s HomeKit world. For years, that meant one thing: if a gadget didn’t support HomeKit, a Homebridge plugin could often fake the missing bridge and get it into Apple Home anyway. That made Homebridge useful, but also pretty Apple-centric. (developers.homebridg([thechels.uk)ml)) ### So what changed in 2.0? Version 2.0 adds what the project itself calls the “initial groundwork” for Matter support alongside HomeKit. Basically, Homebridge is no longer thinking only about how to expose devices to Apple’s older HomeKit model. It can now start exposing supported accessories as Matter devices too, which opens the door to Google Home, Alexa, SmartThings, and Apple Home through one shared standard. (thechels.uk) ### Why is Matter a big deal here? Matter is supposed to reduce the brand silos that made smart homes annoying in the first place. Instead of every platform needing its own custom integration, a device that speaks Matter can usually pair locally with multiple ecosystems. The catch is that a lot of existing gear does not speak Matter natively. Homebridge’s new role is to help older, plugin-supported devices cross th(thechels.uk) (github-wiki-see.page) ### Why are robot vacuums the headline example? Because robot vacuums have been a weird compatibility hole for a long time. Older HomeKit setups often had to pretend a vacuum was something else — like a fan — just to get basic controls into Apple’s Home app. With Homebridge 2.0’s Matter work, plugins can now expose a vacuum as an actual Matter robotic vacuum cleaner device. One Eufy RoboVac plugin already says it can do exactly that on Homebridge 2.0 beta. (github.com) ### Does this mean everything works today? No — and this is the important part. Homebridge says Matter support is early, experimental, and not everything will work out of the box on day one. Individual plugins need updates. So the upgrade does not magically convert Homebridge’s whole catalog overnight. What 2.0 really ships is the platform layer that plugin developers can now build on. (thechels.uk) ### Why does the plugin ecosystem matter so much? Because Homebridge already has scale. The project points to an ecosystem of more than 4,000 plugins. If even a modest chunk of those plugins gains Matter output over time, Homebridge could turn from a HomeKit workaround into a broader compatibility hub. That is the interesting part — not one release day feature, but the migration path it creates for a huge pile of existing integrations. (thechels.uk) ### Is this the same as Matterbridge? Not quite. Matterbridge is a separate project built specifically around Matter plugins. Homebridge 2.0 is Homebridge itself adding Matter capabilities without abandoning its older HomeKit identity. In other words, Homebridge users may not need to jump to a totally different tool if they want to start experimenting with Matter. (npmjs.com)eature than a foundation pour. But it’s a meaningful one. Homebridge spent years helping unsupported devices sneak into Apple’s world. Now it’s starting to help them speak the smart-home standard that was supposed to make all this glue code less necessary in the first place. (thechels.uk)