Last updated: 6 September 2026 · Originally published December 2025 · By SHUK Editorial
Last checked: 30 August 2026.
How we evaluated: This guide is based on official Connectivity Standards Alliance, Thread Group, manufacturer, certification and platform documentation recorded in the Smart Home UK source ledger. It was not hands-on tested by Smart Home UK. Outage statements below describe published behaviour and architecture limits, not an offline test performed by us.
UK verdict: Matter can reduce ecosystem lock-in for supported device classes, but it does not remove the need to check controllers, Thread border routers, bridges, platform versions and manufacturer-only features. Buy an exact certified product for a defined household task, not a Matter logo in isolation.
Matter is an application-layer interoperability standard. It can run over Ethernet, Wi-Fi or Thread. A Matter product still needs a compatible Matter controller. A Matter-over-Thread product also needs a Thread border router. A Matter bridge can represent supported non-Matter devices—such as Zigbee lights—to a Matter ecosystem. The bridged device does not become a native Matter or Thread end device.
Matter roles explained
| Role | What it does | What it is not |
|---|---|---|
| Matter controller | Commissions and controls supported Matter device classes | Not necessarily a Thread border router, bridge or Zigbee hub |
| Thread border router | Routes an IPv6 Thread mesh to the home IP network | Not by itself the user’s Matter app or controller |
| Matter bridge | Exposes supported devices from another protocol or ecosystem | Does not change the end device’s native radio |
| End device | The light, sensor, plug, thermostat or other controlled product | Does not automatically include a controller, bridge or border router |
Native versus bridged: a Matter-over-Wi-Fi or Matter-over-Thread light is a native Matter end device. A Hue Zigbee lamp exposed by a Hue Bridge remains a Zigbee end device on the lamp side and is represented through the bridge on the Matter side. This distinction affects required hardware, feature exposure and what fails if a bridge, controller or Thread border router is unavailable.
Current Matter releases
The Connectivity Standards Alliance’s official Matter 1.6 release notes are the specification reference used below. They also make an important adoption point: a published specification is available for manufacturers and platforms to implement, but support reaches products and ecosystems on their own schedules. The Thread Group lists Thread 1.4.1 as the current specification, but a product may still document Thread 1.3 or 1.4.
| Version | Release point | Relevant change | What buyers should know |
|---|---|---|---|
| Matter 1.2 | October 2023 | Robot-vacuum support and other device types | Robot vacuums are not a future 1.6 category |
| Matter 1.5 | November 2025 | Camera device type, closures and expanded energy management | Certification and ecosystem support still vary |
| Matter 1.5.1 | 31 March 2026 | Camera and doorbell streaming and media refinements | Does not make every current camera Matter-compatible |
| Matter 1.6 | 17 June 2026 | NFC commissioning, Joint Fabric administration, thermostat suggestions, status and security refinements | No new device categories; products and platforms adopt versions on different schedules |
Published platform versions checked 30 August 2026
| Platform or product | Published implementation evidence | Conflict or limit | Official source |
|---|---|---|---|
| Home Assistant | Home Assistant 2026.8.3; Matter Server 9.0 supports Matter 1.5.1; updated OTBR supports Thread 1.4. | The Thread integration remains marked work in progress. Do not report Matter 1.6 implementation. | Matter Server 9.0 |
| Homey Pro / Pro mini | Firmware 13.3.0; CSA-certified Matter 1.5. | Older Matter 1.3 wording is stale. Device-class and app support still need checking. | Homey certification |
| SmartThings hubs | Production hub firmware 0.61.6 adds Matter 1.5 device-type support. | 0.62.x was beta at the check date and is not used as the production version. | SmartThings 0.61.6 notes |
| Echo Dot Max | Alexa Matter support documents a Matter 1.5 subset and Thread 1.3 border-router role. | The exact device firmware build is not publicly listed. | Alexa Matter support |
| Google Home Speaker | Production firmware 3.78.540761; Matter controller and Thread 1.3 border router. | Google does not publish the exact implemented Matter specification. | Google specifications |
| Apple HomePod / Apple TV 4K | HomePod Software 26.6 and tvOS 26.6; supported models act as home hubs and Thread border routers. | Apple does not publish an exact Matter specification version. | Apple Thread border-router list |
| IKEA DIRIGERA | Controller component: Matter 1.4.2, firmware 26.4.0. Bridge end product: Matter 1.3, firmware listed as 4. | These are separate certified roles, not conflicting installed-firmware claims. | controller certificate; bridge certificate |
What the camera and energy updates mean in practice
Matter 1.5 added a camera device type and expanded energy-management capabilities. Matter 1.5.1 refined camera performance plus doorbell, chime and intercom behaviour. Matter 1.6, released 17 June 2026, is the current specification in this guide. A specification release is not proof that every Apple, Google, Amazon, SmartThings or other controller already implements every new feature.
The Aqara Camera Hub G350 is a concrete example: the Alliance’s product certificate records Matter 1.5 certification on 10 February 2026. It combines dual lenses, pan and tilt, local detection, microSD recording and optional cloud services. Before buying for Matter, verify that the intended controller version exposes the camera functions you need.
Check the Matter-certified Aqara G350 on Amazon UK
Matter cameras remain an early UK category. This research established one exact currently UK-buyable certified camera, not a broad enough market for a dependable best-buy roundup. Another CSA camera certificate exists, but its exact UK SKU and buyability were not established.
Important compatibility limits
- Hue lamps use Zigbee to a Hue Bridge; the bridge can expose supported Hue devices to Matter. The lamps remain bridged Zigbee end devices, not native Matter or Thread end devices.
- Eve Cam is not listed here as a native-Matter camera. Its documented integration remains Apple HomeKit Secure Video unless an official Matter certification is added.
- Certification establishes compliance for the listed version and configuration; each ecosystem still chooses supported device types, features and software versions.
- Local control can continue only where the complete route remains available: device, power, LAN, controller and—when applicable—Thread border router or bridge. Remote access, voice services, accounts and cloud-only features still need internet.
- Not every Matter device works without extra hardware: verify the controller, Thread border router where required, device-class support and platform version.
How to check a Matter purchase
- Identify the exact device, SKU/region and the task it must perform.
- Confirm the native transport: Ethernet, Wi-Fi, Thread or a non-Matter protocol such as Zigbee.
- Confirm whether the route is native Matter or bridged through a manufacturer hub.
- Confirm a compatible Matter controller in the intended ecosystem.
- For Thread, confirm a suitable Thread border router and its placement.
- Check the platform version, supported device class and functions you need.
- Record which settings remain only in the manufacturer app and which require cloud access.
- Check the exact UK model, seller, warranty and return route before ordering.
This sequence is more useful than asking whether a household “has Matter”. A controller may support a light but not every new camera function. A border router can provide network transport without being the app the household uses. A bridge may expose basic controls while retaining advanced settings in its own ecosystem.
Use the Smart Home UK checker toolkit to map the controller, bridge and Thread-border-router roles before choosing an end device.
Who should buy Matter products?
Matter is a good fit when the exact certified device is supported by the household’s controller, the required transport hardware is already present and multi-ecosystem access solves a real problem. It can also be useful when a household wants to add devices without committing every future purchase to one vendor.
Avoid replacing a reliable Zigbee or manufacturer-bridged network only to obtain a Matter label. Bridging may already provide the functions needed. Avoid newly announced device classes until the exact product, certification, UK availability and controller support are established.
Installation, reliability and privacy
Store commissioning codes securely and do not publish them in photographs. Add one device at a time, name it clearly and verify ordinary control before adding another ecosystem through multi-admin. Keep physical controls for essential lighting, heating and access.
| Device route | Published broadband-outage boundary | Additional failure point |
|---|---|---|
| Native Matter over Wi-Fi/Ethernet | Eligible basic control may continue if the LAN, controller, device and power remain available. | Remote, voice, vendor-cloud and app-only features may fail. |
| Native Matter over Thread | Eligible basic control may continue if the Thread mesh, border router, controller, LAN and power remain available. | Loss of the controller or required border router breaks that route. |
| Bridged Zigbee | Published local behaviour depends on the Zigbee device, bridge, controller, LAN and power. | Loss of the bridge removes Matter exposure; manufacturer-only features may never cross the bridge. |
| Direct or physical association | Can remain available only where the manufacturer explicitly documents it. | Direct control does not prove that app history, alerts or remote access remain available. |
Where a manufacturer does not publish recovery after broadband, cloud, controller, border-router or bridge loss, our status is not published—not tested by Smart Home UK. Review household permissions in every ecosystem to which the device is added, and remove former members.
Ownership cost
Include any controller or Thread border router the household does not already own, plus manufacturer bridges retained for fuller features. Do not call a product “hub-free” when it needs another controller device. Equally, do not count an existing compatible speaker, display or hub as a new purchase if it already serves the household.
For comparisons, use the same basis: hardware + required hub or storage + installation + 36-month subscription + mandatory consumables. Show a free/core route separately from optional paid services, date every price and leave unresolved battery replacement quantities visible rather than inventing them.
The maintenance cost includes software updates, account recovery, controller replacement and rebuilding automations. A slightly simpler device route can be better value than exposing the same accessory across several ecosystems no one uses.
Related UK guides
See the IKEA Matter range guide, smart-home hub guide, smart-lighting guide and Zigbee versus Matter decision guide.
SHUK Editorial — Research-led UK smart-home guidance using public manufacturer and authoritative sources. Editorial identity · Research method and corrections.