Hubitat Elevation offers support for Matter devices. This feature is available on hub model C-5 and newer only and requires platform 2.3.8 (model C-5/C-7) or 2.3.7 (model C-8/C-8 Pro) or later. Note that as with any device, an appropriate driver is required; see List of Compatible Devices for built-in options.
Hubitat Elevation is a Matter controller. This means you can pair devices that support Matter to your hub. This is similar to how you can pair/include Zigbee or Z-Wave devices. Hubitat is not a Matter bridge (see below for more on Matter bridges) — it will not create Matter-compatible devices out of non-Matter devices you have added to your hub.
Matter is a new smart home standard backed by several major manufacturers and supported by many more. It defines a standard interface for local control of devices, a sort of common "language" they can speak and understand. Matter per se does not define how the devices get on your network in the first place. To do this, Matter relies on additional technologies for connectivity, including:
- Wi-Fi: a common protocol that you are probably already familiar with, likely used by many existing devices on your home network. (Some devices may also use Ethernet; the idea is similar, that these are regular IP-accessible devices on your home network.)
- Not all Wi-Fi devices support Matter. Look for the Matter logo or the term "Matter over Wi-Fi."
- Thread: a low-power mesh network protocol. Most battery-powered devices will use this protocol since it consumes less power than Wi-Fi, but some mains-powered devices also use Thread.
- Not all Thread products support Matter; look for the Matter logo or the term "Matter over Thread." (The most common Thread devices you are likely to find that won't work use "HomeKit over Thread" rather than Matter. Some vendors may have firmware upgrades available if the hardware is capable, though not all will or can.)
Your hub does not have to be connected using Wi-Fi (i.e., in Network Setup) in order to use Matter over Wi-Fi devices. (In fact, we recommend a wired connection whenever possible for best reliability.) In nearly all home networks, your Wi-Fi and Ethernet/wired devices form a single network, and this is all that is needed.
You may also see another protocol related to Matter:
- Bluetooth: Most Matter devices devices use Bluetooth LE for initial setup; however, it is not used by Matter as a means to communicate with devices after this (and the use of Bluetooth during setup is generally not apparent to the user — you likely won't even know!).
- The hub does not have built-in Bluetooth, nor does the mobile app make use of Bluetooth that may be on-device. This is one reason Matter devices must be initially commissioned via another system before being paired as described in Add Device.
Another type of Matter device you may find is a:
- Matter bridge: "Translates" Matter to/from devices that communicate with the bridge using some other protocol (Zigbee, Z-Wave, Bluetooth, etc.). The Philips Hue Bridge is an example of a Matter bridge: it exposes a Matter interface for devices on the Hue system, though the underlying devices still use Zigbee.
Your hub creates a Matter Fabric, where "Fabric" is, more or less, the technical term for a particular "network" of Matter devices (regardless of lower level protocols). Your hub is a separate Fabric from other Matter Fabrics you may be using, such as Apple Home, Amazon Alexa, etc. Matter devices support being paired to multiple Fabrics at the same time (at least 3-5 but possibly more, depending on the device). This feature is sometimes referred to as "Multi-Admin" or "Multi-Fabric."
For any Matter device, the device must first be commissioned with another Matter controller (Apple Home, Amazon Alexa, Google Home, SmartThings, or similar). This controller can then put the device in "pairing mode" to use with another system, such as Hubitat.
Matter devices are ultimately added via the Add Device page, similar to most other devices.
As stated previously, Matter devices allow pairing with multiple controllers. This also means that if you commission a Matter device using Apple Home above, then also pair the device with Hubitat after using Apple Home to put it in pairing mode, it will be usable in both systems (no need to use the HomeKit Integration to make it usable in HomeKit from Hubitat, in this example).
Want to learn more about Thread? It is designed to be generally self-maintaining, but some terms and tips may be helpful to know.
- Mains-powered Thread devices may act as routers that can pass messages to and from other Thread devices, effectively extending the range of the network. (This is similar to Zigbee routers, sometimes informally called repeaters, for users who are familiar with that protocol.)
- Special routers on the network are called Thread border routers, which essentially bridge your Thread network to your regular LAN.
- You will need a Thread border router to use Thread devices with Hubitat Elevation. The hub itself does not contain a Thread radio and thus cannot function as a border router — but you may already have one (or more) in your home!
- Examples of Thread Border Routers include:
- Apple TV 4K (3rd generation with Wi-Fi and Ethernet; or 2nd generation)
- Apple HomePod (2nd generation) or HomePod Mini
- Amazon Echo (4th generation)
- Google Nest Hub (2nd generation), Next Hub Max, Nest Wifi Pro (6E), or Nest Wifi
- SmartThings Station
- A Thread network can have multiple border routers.
- While the latest version of the standard provides a way to make this possible, we are not aware of any case currently in which Thread border routers from different vendors (Apple, Amazon, Google, Samsung, etc.) can work together (technically, share keys) to form a single Thread network.
- You may operate multiple Thread networks.
- However, it may be best to pick the one that gives you the most possible border routers for best resilience (e.g., if you have an Apple TV and HomePod that both support Thread but only a single Thread-capable Echo device, using Apple Home may make the most sense).
- Like Zigbee (and Wi-Fi), Thread uses the 2.4 GHz spectrum. Keeping Thread devices, especially routers and border routers, away from strong 2.4 GHz signals may help create a better Thread network. For example, do not set one of these devices directly on top of your Wi-Fi router/access point or a Zigbee hub.