← All guides

Matter on Hubitat, Homey and openHAB: what each controller supports

All three platforms are Matter controllers according to their own documentation — Hubitat on model C-5 and newer, Homey on Homey Pro, Homey Pro mini and Homey Self-Hosted Server (but not Homey Cloud), and openHAB through its Matter binding. Thread support differs sharply: only Hubitat's C-8 Pro Thread Special Edition has a Thread radio, Homey Pro and Homey Pro mini are Thread border routers, and openHAB needs a Thread border router from another ecosystem. Homey's Matter Bridge app and openHAB's Matter bridge can share their own devices with Apple Home, Google Home, Alexa and others, while Hubitat's documentation says Hubitat is not a Matter bridge. See what Matter is and the hub and Thread border router guide for the wider picture.

Controllers, Thread border routers and Matter bridges

Hubitat's documentation draws a clear line between a Matter controller and a Matter bridge. A controller pairs and controls Matter devices, similar to how Hubitat pairs Zigbee or Z-Wave devices. A bridge "translates" Matter to and from devices that use another protocol — the Philips Hue Bridge is Hubitat's example, exposing a Matter interface while the underlying bulbs still use Zigbee. Hubitat says it is a controller and not a bridge: it won't create Matter-compatible devices out of the non-Matter devices you've added to it. Each controller creates its own Matter fabric, and Matter devices can belong to several fabrics at once — Hubitat says at least 3-5, possibly more depending on the device.

Homey's wiki makes the same controller-versus-border-router distinction from the networking side. A Thread border router handles routing IP traffic between the Thread mesh and your Wi-Fi or Ethernet network. A Matter hub — which Homey also calls a Matter controller — handles onboarding and control: adding devices to a fabric, sending commands, reading states and running automations. Homey's explainer puts it plainly: a border router alone cannot control devices, and a Matter controller without border-router functionality cannot reach Thread devices on its own. Homey Pro and Homey Pro mini combine both roles.

openHAB's Matter binding documentation describes two independent functions. The Matter client lets openHAB discover and control other Matter devices. The Matter bridge exposes openHAB Items and Groups as Matter devices to third-party clients like Apple Home, Amazon Alexa and Google Home. The two operate separately — adding or removing a controller Thing or node Thing has no effect on the bridge. For more on how Matter fits into a smart home, see Matter explained and the controller and border router comparison.

Hubitat, Homey and openHAB at a glance

Each row names its source, and the details follow in the sections below. MatterCheck doesn't check Hubitat, Homey or openHAB itself, so there are no MatterCheck results for these three controllers — the platform counts elsewhere on this site cover Apple Home, Google Home, Alexa, SmartThings and Home Assistant only.

Hubitat Elevation and Matter

Which Hubitat hubs support Matter

Hubitat's Matter documentation says Matter is available on hub model C-5 and newer only. It requires platform 2.3.8 on the C-5 and C-7, or 2.3.7 on the C-8 and C-8 Pro. As with any Hubitat device, an appropriate driver is required — the docs point to the built-in list of compatible devices. Hubitat's release notes for 2.4.4, posted 2026-02-12, say the platform "Updated Matter to v1.5 (beta)".

Matter over Wi-Fi and Thread on Hubitat

Matter-over-Wi-Fi devices can be commissioned directly on any Matter-capable Hubitat model, with no other controller needed. Hubitat's Add Device page notes that 2.4 GHz is required for most Matter-over-Wi-Fi devices, and the main Matter page recommends a wired hub connection whenever possible for reliability. Thread is different: only the C-8 Pro Thread Special Edition can commission Matter-over-Thread devices directly. On that model, the product page says the integrated Thread radio replaces the Zigbee radio found in the standard C-8 Pro, so it has no built-in Zigbee connectivity. It's a limited edition, available for shipment to the 48 contiguous United States only, and Hubitat's staff announcement says it's sold through Hubitat.com while supplies last.

Every other Matter-capable Hubitat model needs a Thread border router on the network — Hubitat's docs list Apple TV 4K (3rd generation with Wi-Fi and Ethernet, or 2nd generation), HomePod (2nd generation) or HomePod mini, Amazon Echo (4th generation), Google Nest Hub (2nd generation) and SmartThings Station as examples. The recommended path is to commission the Thread device with that other controller first, then share it to Hubitat using a pairing code. Hubitat's docs also note that the mobile app isn't recommended for Thread Special Edition users with Apple devices right now, because those devices may attempt to join an Apple Thread border router instead of Hubitat.

Adding a device that's already in Apple Home or Alexa

Hubitat's guidance is to commission a Matter device with another controller first — Apple Home, Amazon Alexa, Google Home, SmartThings or similar — then put it in pairing mode from that system. The Add Device page warns that the pairing code you get this way may not be the QR code or numbers printed on the device itself; use the code the existing system provides. For Apple Home, Hubitat writes: long-press the accessory in the Home app, choose Accessory Settings, select Turn On Pairing Mode, and use the setup code the Home app shows. For Alexa: go to Devices, find the device, select the settings gear, choose Other Assistants and Apps, select Add another, and wait for the setup code. You then enter that 11-digit code on Hubitat's Add Device page. The device stays usable in both systems, because Matter devices support multiple fabrics — Hubitat says at least 3-5, possibly more. See sharing one device with several platforms for the general pattern.

Matter bridges on Hubitat

Hubitat is not a Matter bridge itself, but it can add Matter bridges. Hubitat's October 2024 press release says platform 2.3.9.192 brought built-in support for Matter Bridge devices, including the Aqara Hub M3 and Philips Hue Bridge, without integration apps or custom code. The same release says Aqara Zigbee devices can be paired directly to the hub or used via the Aqara M3 as a Matter bridge, and Aqara Thread devices can be integrated via the M3 over Matter. For the broader picture on bridges that expose Zigbee devices over Matter, see Matter bridges for Zigbee devices.

Recent Hubitat Matter changes

Hubitat's release notes track the platform's Matter progress. Release 2.4.4 added a button to generate a Matter setup code for each connected device on the Matter details page, plus improvements to Matter events and subscriptions. Release 2.5.1, posted 2026-07-29, added Matter web UI QR scanning and manual setup code handling for Wi-Fi commissioning, plus network status and IP address attributes on Matter devices. Hubitat's docs add that as of platform 2.5.1 the hub web interface can also commission new Matter devices. Release 2.5.2, posted 2026-09-29, added Matter firmware updates through the drivers' updateFirmware command — excluding bridge devices — and switched Matter attestation to the CSA's DCL online database, which Hubitat says should fix devices that failed commissioning at the attestation phase.

Homey and Matter

Which Homey products support Matter

Homey's Matter device types article says Homey Pro, Homey Pro mini and Homey Self-Hosted Server are certified as Matter 1.5 controllers by the Connectivity Standards Alliance. The CSA listing for Homey shows a Software Component with specification version 1.5, firmware 13.3.0, certified 06/29/2026. Homey's product comparison page states that Homey Cloud does not support Matter, Thread or LAN devices. Homey's Connect article says there's no need to install apps for Matter devices — Homey Pro determines the device's capabilities without them. For how to check certification yourself, see checking Matter certification.

Thread on Homey Pro and Homey Pro mini

Homey Pro and Homey Pro mini both act as Thread border routers. When adding a Matter device, Homey Pro automatically decides whether to connect it over Wi-Fi or Thread. The Add a Matter device article describes two paths on Homey Pro: Connect via Homey Pro, which uses Homey Pro's own Thread network and Bluetooth for the initial connection, or Connect via Android/iOS, which uses your phone's Thread network and Bluetooth. Homey Pro mini skips that choice and always pairs through your phone.

There are real constraints. Homey's Thread article says Homey Pro currently can't join an existing Thread network — such as one created by Apple Home or Google Home — because Thread and Zigbee share the same hardware, and resetting the Zigbee network also resets Thread. Homey Pro's Thread network currently can't be added to iOS, so iPhone users pairing through the phone need a third-party Thread border router such as a HomePod. On Android, Homey Pro's Thread network is configured automatically only if no other Thread network was configured before; Android doesn't allow changing the Thread network configuration afterwards. For how Thread credentials move between systems, see Thread credentials and joining Thread networks.

Homey Self-Hosted Server and Thread

Homey Self-Hosted Server can add Matter-over-Thread devices, but it needs a Thread border router already on the network. Homey's Self-Hosted Server Thread article explains how credentials work: when you set up a Thread border router, the manufacturer's app — Apple Home, Google Home or Alexa — syncs the Thread network credentials to your phone, and Homey uses those credentials during setup to add devices to the existing Thread network. The article lists commonly used border routers including Homey Pro and Homey Pro mini, Apple HomePod mini and Apple TV 4K (2nd and 3rd generation), Google Nest Hub (2nd generation) and Nest Wifi Pro, Amazon Echo (4th generation) and Echo Hub, and Nanoleaf Shapes, Lines and Elements.

Matter device types Homey lists

Homey's supported device types page groups them into categories, each listing more types than named here: climate (air conditioners, air purifiers, fans, heat pumps, thermostats), kitchen and laundry (cooktops, dishwashers, ovens, washers, dryers), lighting, power and access (lights, sockets, buttons, locks), energy (EV chargers, solar panels, water heaters, water valves, pumps), sensors (motion, environment, safety and air quality types), and home and entertainment (bridges, robot vacuums, speakers, video players, window coverings). For bridges, only bridged devices of the listed types can be used in Homey. The Add a Matter device article lists the requirements: Homey Pro firmware v10.3.0 or newer for setup through the Homey Web App, Homey Mobile App v9.2.5 or newer, and iOS 18.5 or newer or Android 8 or newer with the latest Google Play Services. It also warns that the Matter API in Google Play Services can take up to 24 hours to update, so if pairing fails on Android, waiting a day may help.

Homey's Matter Bridge app

Homey's official Matter Bridge app exposes Homey devices to Apple Home, Google Home, Amazon Alexa, Samsung SmartThings and Home Assistant. It works with Homey Pro (2023 - 2026), Homey Pro mini and Homey Self-Hosted Server. The app page lists supported device types: on/off, dimmable, color and temperature lights, plug-in sockets, thermostats, locks, blinds, curtains and roller shutters, door/window sensors, temperature and humidity sensors, motion and occupancy sensors, air quality sensors, and CO2 and smoke alarms. Version 0.9.0 added connecting additional Matter platforms directly from the app settings, with each pairing attempt using a temporary code that can be cancelled without affecting existing connections.

Homey's Apple Home article walks through the setup: you need a Homey Pro, Homey Pro mini or Self-Hosted Server, an iPhone or iPad, a home hub such as a HomePod or Apple TV 4K for remote access and automations, and devices already working in Homey. Apple Home may show a warning about an uncertified accessory — Homey says to tap Add Anyway. Without a home hub, devices still work on your home network but remote control and automations won't.

Homey's Matter Bridge explainer sets expectations: only features defined by the Matter standard and supported by the receiving platform are exposed, so advanced Homey features like energy reporting or multi-channel devices may not appear externally. Homey's page on controlling devices via Matter adds that some action-based devices, such as IR or 433 MHz devices, may not report real-time state. Removing a device from Homey also removes it from the other platform, and if Homey loses access to a device, it becomes unavailable across all platforms until Homey is restored.

openHAB and Matter

The openHAB Matter client

openHAB's 5.0 release post, dated 21 July 2025, described a Matter 1.4.1 client that can communicate with more than 30 device types. The current Matter binding documentation now says it supports version 1.5.1 of the Matter specification and earlier. The binding uses the matter.js implementation and requires Node.js 22+; it will attempt to download and cache an appropriate version if one isn't installed. The quick start is to install the binding, add a Matter "Controller" Thing, use the Pair Matter Device action on that Thing, then add the discovered device as a "Node" Thing.

For a device already paired with another ecosystem, openHAB's docs say you must use that ecosystem to generate a new pairing code, and the code is only available for a limited time — typically 5-15 minutes, though the exact duration depends on the ecosystem. openHAB then talks directly to the device, not through the other vendor's stack. Bridged endpoints from Matter bridges become endpoint Things automatically once the parent node is added, and the 5.0 post says openHAB can talk Matter to bridges such as the Philips Hue hub and IKEA Dirigera. For firmware, openHAB queries the public Matter Distributed Compliance Ledger every 24 hours for updates.

Thread devices and IPv6 on openHAB

openHAB has no Thread border router integration yet. The binding docs recommend pairing Thread devices to a commercial router with Thread support first — Apple TV 4K, Google Nest Hub 2, Amazon Gen 4 Echo — then generating a Matter pairing code in that ecosystem and adding the device normally. openHAB still gets direct access to the device through the embedded border router. The docs say support for using an OpenThread Border Router has been verified to work and "will be coming soon" to openHAB, but no date is given.

Matter on openHAB requires IPv6 to be enabled and routable between openHAB and the device. The docs warn that Docker, VLANs, subnets and other configurations can stop Matter working if not set up correctly. For more on the network side, see Matter network settings.

The openHAB Matter bridge

openHAB can expose Items and Item groups as Matter devices to Google Home, Apple Home and Amazon Alexa, for local control; the docs say it can be used instead of cloud-based integrations for features like voice assistants. The 5.0 post notes that this bridge uses a Matter development certificate and is uncertified. The bridge is unrelated to the Matter controller Thing. When it starts with no paired clients, it opens a commissioning window automatically; after one client pairs, the window closes by default. To add more clients, you enable "Allow Commissioning" in the settings and pair within a 15 minute window using the QR code or manual pairing code. The docs list supported device types including on/off lights, dimmable lights, color lights, plug-in units, thermostats, window coverings, temperature and humidity sensors, occupancy and contact sensors, door locks, fans and mode selects.

Which products have Matter and Thread

The Thread column matters most if you already have an Apple, Google or Amazon Thread border router. openHAB, and Hubitat hubs without a Thread radio, use that border router through another controller first — you commission the device there, then share it with a pairing code. Homey Self-Hosted Server uses the border router's credentials synced to your phone. Homey's Thread page says Homey Pro can't currently join an existing Thread network. For the practical difference between the two transports, see Thread vs Wi-Fi.

Using them alongside Apple Home, Google Home, Alexa, SmartThings or Home Assistant

There are two directions here. The first is bringing a device from another platform into Hubitat or openHAB using a pairing code — the multi-admin route each page describes. Hubitat's docs walk through Apple Home's Turn On Pairing Mode and Alexa's Other Assistants and Apps flow, and openHAB's docs say Apple Home, Google Home, Amazon Alexa and openHAB all support generating pairing codes for existing devices. The second direction is sharing devices out: Homey's Matter Bridge app and openHAB's Matter bridge expose their own devices to other Matter controllers. Homey's app page names Apple Home, Google Home, Amazon Alexa, Samsung SmartThings and Home Assistant; openHAB's docs name Google Home, Apple Home and Amazon Alexa. Hubitat doesn't offer this direction — its docs say it is not a Matter bridge.

MatterCheck's own data covers the five receiving platforms. MatterCheck tracks 24 Matter device types across Apple Home, Google Home, Alexa, SmartThings and Home Assistant:

A device bridged from Homey or openHAB still has to be a Matter device type the receiving platform supports. Homey's Matter Bridge explainer makes the same point: each platform may interpret Matter features differently, and Google Home may display device types that Apple Home doesn't. See the five-platform comparison for the full breakdown.

Network settings these controllers ask for

Homey's Connect article lists several network tips: disable multicast enhancements, Access Point isolation, VLANs or mDNS forwarding features in your router; avoid Matter 1.0 device firmware and update if possible; ensure enough Thread routers (mains-powered devices generally are); move Wi-Fi to channel 1 and avoid channel 11; and prefer a single Ethernet Thread border router over multiple Wi-Fi border routers.

openHAB's docs say IPv6 must be enabled and routable, and that Docker, VLANs and subnets can prohibit Matter from working if not configured correctly. Hubitat's docs recommend a wired hub connection whenever possible, and its add-device page says 2.4 GHz is required for most Matter-over-Wi-Fi devices. For the full network checklist, see Matter network settings: IPv6, VLANs and mDNS.

Before you add Matter devices: what to check

1. Check your product is Matter-capable. Hubitat needs model C-5 or newer; Homey needs Homey Pro, Homey Pro mini or Self-Hosted Server — Homey's comparison page says Homey Cloud doesn't support Matter; openHAB needs the Matter binding and Node.js 22+.
2. Update first. Hubitat's docs list platform 2.3.8 (C-5 / C-7) or 2.3.7 (C-8 / C-8 Pro) or later, and release 2.4.4 moved Matter to v1.5 (beta). Homey's Add a Matter device article lists Homey Pro firmware v10.3.0 and Homey Mobile App v9.2.5 or newer.
3. Plan Thread. Work out which device acts as your Thread border router. openHAB, and Hubitat hubs other than the C-8 Pro Thread Special Edition, need one from another ecosystem; Homey Pro and Pro mini provide their own; Homey Self-Hosted Server needs one already on the network.
4. For a device already in another app, get a fresh pairing code from that app. Hubitat and openHAB both say to use the code the existing system generates, not the one printed on the device, and openHAB notes the code is typically valid for 5-15 minutes.
5. Check the device type is supported. Homey and openHAB publish supported device type lists; Hubitat requires an appropriate driver for any device.
6. Check network settings. IPv6 for openHAB, 2.4 GHz for most Wi-Fi devices on Hubitat, and Homey's advice to disable multicast enhancements and AP isolation.

For the general process, see how to add a Matter device.

Frequently asked questions

Does Hubitat support Matter?

Yes. Hubitat's documentation says Matter is available on hub model C-5 and newer, requiring platform 2.3.8 on the C-5/C-7 or 2.3.7 on the C-8/C-8 Pro. Hubitat is a Matter controller, and release 2.4.4 updated Matter to v1.5 (beta).

Does Hubitat support Matter over Thread?

Only the C-8 Pro Thread Special Edition can commission Matter-over-Thread devices directly, because it's the only Hubitat model with a built-in Thread radio. Other Matter-capable models can use Thread devices by commissioning them with another controller that has a Thread border router, then sharing the device to Hubitat with a pairing code.

Is Hubitat a Matter bridge?

No. Hubitat's documentation says Hubitat is a Matter controller and not a Matter bridge — it won't create Matter-compatible devices out of non-Matter devices you've added. Hubitat can add Matter bridges such as the Philips Hue Bridge and Aqara Hub M3, but it doesn't expose its own devices to other platforms over Matter.

Does Homey support Matter?

Yes, on three of its products. Homey's Knowledge Base says Homey Pro, Homey Pro mini and Homey Self-Hosted Server are certified as Matter 1.5 controllers by the CSA, and the CSA's listing for Homey shows a certified date of 06/29/2026. Homey's comparison page says Homey Cloud does not support Matter, Thread or LAN devices.

Is Homey Pro a Thread border router?

Yes. Homey Pro and Homey Pro mini both act as Thread border routers and Matter controllers. However, Homey Pro currently can't join an existing Thread network, and its Thread network can't be added to iOS — iPhone users pairing through the phone need a third-party border router such as a HomePod.

Does Homey Bridge or Homey Cloud support Matter?

Homey Cloud does not support Matter, Thread or LAN devices. No Homey page here says Homey Bridge supports Matter on its own. For the Matter Bridge feature, Homey's page on controlling devices via Matter lists "A Homey Pro or Homey Bridge in combination with a Homey Pro mini or Homey Self-Hosted Server".

Does openHAB support Matter?

Yes. openHAB's Matter binding supports Matter specification 1.5.1 and earlier, and the 5.0 release post described a Matter 1.4.1 client with more than 30 device types. The binding needs Node.js 22+, and openHAB can act as both a Matter client and a Matter bridge.

More MatterCheck guides

• Matter hubs and Thread border routers — how the two roles differ across brands.
• Sharing one device with several platforms — multi-admin and pairing codes in practice.
• Matter bridges for Zigbee devices — how bridges like the Hue Bridge expose non-Matter devices.
• Thread credentials and joining Thread networks — how credentials move between phone apps and controllers.
• Matter network settings — IPv6, VLANs, mDNS and multicast requirements.
• Matter firmware updates — how updates reach devices through the DCL.
• Matter versions — what 1.4, 1.5 and earlier versions mean for devices.
• Matter on Home Assistant — the fifth platform MatterCheck tracks.
• Five-platform Matter comparison — MatterCheck's device-type counts for Apple Home, Google Home, Alexa, SmartThings and Home Assistant.

How we checked

Pages fetched 2026-10-20 — Hubitat's Matter and Add Device documentation, its C-8 Pro Thread product page, its October 2024 press release, its 2.4.4 / 2.5.1 / 2.5.2 release notes and its Thread edition announcement; Homey's Knowledge Base articles on Matter device types, adding Matter devices, Thread on Homey Pro and Self-Hosted Server and the Matter Bridge app with Apple Home, Homey's wiki pages on products, Thread border routers and the Matter Bridge, and the Matter Bridge app listing; the CSA's certified-product listing for Homey; openHAB's Matter binding docs and 5.0 release post. Hubitat's and Homey's script-rendered pages were read from the same content through their public page data. The platform counts come from MatterCheck's own data; MatterCheck doesn't test these three controllers. Makers change Matter support with updates, so check your hub's own release notes. See our methodology.

Last reviewed 2026-10-20. If your hub maker's own documentation says something different, follow the maker's instructions.