6 min read
For years, building a smart home around Apple Home meant accepting a frustrating constraint: if a device did not carry the HomeKit badge, it simply did not belong.
That limitation pushed many Apple users toward parallel ecosystems or complex workarounds just to use the hardware they already owned. Homebridge 2.0, released May 4, 2026, changes that calculation in a meaningful way.
By adding native Matter support to its already substantial plugin library, Homebridge now acts as a universal translator between Apple Home and thousands of devices that were never designed to work with it. Read on to find out how it works, what it supports, and whether it belongs in your setup.
Homebridge has existed for years as an open-source software bridge that allows non-HomeKit devices to appear inside the Apple Home app. It runs on low-cost hardware like a Raspberry Pi and connects to Apple Home through a software layer that mimics the HomeKit protocol.
Before version 2.0, that bridge only worked in one direction: devices could appear in Apple Home, but not in Google Home, Amazon Alexa, or any other platform simultaneously. Version 2.0 changes that by adding native Matter support, the open smart home standard backed by Apple, Google, Amazon, and Samsung.
Homebridge 2.0 can expose supported plugin accessories through Matter to Apple Home and other Matter-capable controllers, but support depends on plugin updates and setup. A Raspberry Pi 4 is one possible host, officially listed for $35. That is a significant leap from what the software could do even 12 months ago.

When a plugin connects a device to Homebridge, the software now translates that device’s capabilities into Matter clusters, which are the standardized building blocks that Matter-compatible platforms use to understand and control smart home hardware.
A Ring camera plugin, for example, translates Ring’s proprietary states into Matter-readable signals that any compatible platform can interpret. Matter communication between a controller and Homebridge can be local, but Homebridge plugins may still depend on manufacturer cloud APIs, depending on the device.
A single Homebridge instance supports up to 150 devices, and multiple instances can run in parallel on the same network for larger setups. The system uses Thread, Wi-Fi, or Ethernet connections depending on what the device and network support, with automatic fallback between connection types if one becomes unavailable.
The practical answer is a very long list. Homebridge supports more than 2,000 plugins for thousands of smart accessories, including popular integrations for brands and ecosystems such as Ring, Tuya, Nest, Govee, and Zigbee-connected devices, though compatibility depends on each plugin and device model.
Ring cameras, Tuya smart plugs, Zigbee sensors, Govee lights, and Sonoff devices are among the most popular integrations, covering a wide range of hardware that Apple Home would otherwise reject entirely.
Robot vacuums receive a particularly notable upgrade in this release. Prior versions of Homebridge represented robot vacuums as basic switches or lights inside Apple Home, which limited what automations could do with them.
Version 2.0 aligns with the Matter 1.2 specification, which introduced a dedicated vacuum device type with full traits, including dock status, zone mapping, and cleaning path control. Eufy robot vacuums, for example, can now be automated through the Apple Home app with proper vacuum-specific controls rather than a blunt on/off toggle.

Homebridge 2.0 occupies an interesting position in the smart home hub landscape. Home Assistant remains the most flexible option overall, with more than 2,000 integrations, full local control, and no device limit, though it carries a steeper learning curve.
Apple Home natively supports up to 250 devices, but it works only within the Apple ecosystem. SmartThings and Hubitat both offer local processing but have more limited cross-platform reach and smaller plugin communities.
Homebridge sits between those options in a useful way. It offers cross-platform exposure that native Apple Home cannot match, a plugin library approaching Home Assistant’s depth, and a setup process that is significantly more approachable for users who want Apple Home as their primary interface.
For the existing Homebridge community, the 2.0 update is largely seamless. The release includes a one-click migration tool that carries over existing plugin setups, and the more than 900 plugins in the ecosystem are flagged for compatibility in the updated plugin store.
Homebridge v2.0 release notes say Node.js v18 and v20 are no longer supported, and v2 requires Node.js v22 or v24. Hardware older than a Raspberry Pi 4 may struggle under heavier plugin loads, though the software runs comfortably on most modern mini PCs as well.
The Homebridge GitHub repository crossed 25,000 stars, far exceeding the 10,000 milestone shortly after the Homebridge 2.0 launch.
Homebridge 2.1 is tentatively tracking toward Q3 2026, aiming to build directly upon the major foundational updates laid down by the recent v2.0 release.
The strongest case for Homebridge 2.0 is a household that has invested in Apple Home but owns devices that fall outside the HomeKit ecosystem. Rather than replacing working hardware or buying duplicate devices with HomeKit certification, Homebridge bridges the gap at minimal cost.
A Raspberry Pi 4, a stable internet connection, and an afternoon of configuration are the primary requirements.
For households already running Home Assistant, Homebridge adds less incremental value since Home Assistant already handles cross-platform integration at a deeper level.
Little-known fact: Homebridge’s Matter implementation is not certified by the Connectivity Standards Alliance (CSA) and is not a commercial Matter-certified product.

This article was made with AI assistance and human editing.
If you liked this, you might also like:
We appreciate you taking the time to share your feedback about this page with us.
Whether it's praise for something good, or ideas to improve something that
isn't quite right, we're excited to hear from you.
Lucky you! This thread is empty,
which means you've got dibs on the first comment.
Go for it!