Matter started as a promise to end the fragmentation of smart home ecosystems — a single standard that Apple, Google, Amazon, and Samsung could all support, so a thermostat or a light switch would work with any of them. The first versions of the specification focused on the most common device types: lights, plugs, thermostats, locks, and blinds. Matter 1.5, published in early 2026, moves into more technically demanding territory.
The additions in 1.5 are significant: energy management and monitoring, water and irrigation control, cameras, and a fleet of new sensor types including smoke and CO alarms. Of these, energy management is the one that changes the economic case for Matter most substantially.
The Edge Architecture Behind Matter
Before getting into 1.5 specifics, it’s worth understanding why Matter’s architecture is actually interesting from an edge computing perspective.
Matter is deliberately designed to work locally. A Matter network doesn’t require cloud connectivity for basic operation — devices communicate directly over Thread (a mesh IPv6 protocol designed for low-power IoT) or Wi-Fi, controlled by a Matter controller running on a local hub. Apple’s HomePod, Google’s Nest Hub, Amazon’s Echo, and Samsung’s SmartThings station all function as Matter controllers and Thread Border Routers.
The Thread Border Router is the edge node in this architecture. It bridges Thread’s 2.4 GHz mesh to the IP network, enabling devices to communicate with controllers and with each other without routing through the cloud. For automation and control, this means sub-100ms response times even when your internet connection is down — something that cloud-dependent platforms can’t match.
Multi-admin, another core Matter feature, means a single device can be controlled by multiple ecosystems simultaneously. Your lock can appear in both Apple Home and Google Home at the same time, and both see its state in real time. This is achieved by having each controller commission a separate set of credentials to the device, and the device maintains parallel connections to multiple controllers.
Matter 1.5: Energy Management
The Home Energy Management System (HEMS) cluster in Matter 1.5 is the most substantial new addition. It defines a standardised way for devices to report energy consumption, respond to grid signals, and participate in demand response programmes.
What this enables in practice: a solar inverter, a home battery, an EV charger, and a heat pump — from different manufacturers — can all communicate energy state and capacity to a central controller using the same protocol. The controller can implement energy dispatch logic locally: charge the battery when solar exceeds demand, shift the EV charge to off-peak hours, pre-heat the home before an evening peak tariff period.
Previously, achieving this kind of coordination required either buying everything from one vendor (who controlled the integration) or using a home automation platform like Home Assistant with custom integrations for each device. Matter 1.5’s energy clusters provide the data model and command set that manufacturers and automation platforms can implement once.
The device types defined in 1.5’s energy cluster include:
- EVSE (EV Supply Equipment): communicates charging state, available capacity, and accepts charge schedules
- Solar Panels: reports instantaneous and cumulative generation
- Battery Storage System: reports state of charge, available charge and discharge capacity
- Heat Pump: reports current power draw and accepts comfort targets
The energy management API also includes a time-of-use tariff input: devices can receive tariff schedules that inform their automated behaviour without that logic needing to be cloud-coordinated.
Cameras in Matter 1.5
Camera interoperability has been the most-requested addition to Matter since the specification launched. Matter 1.5 delivers it, though with a narrower scope than some expected.
The camera device type in 1.5 focuses on the core security camera use case: live stream access, motion and person detection events, and snapshot retrieval. The video streaming uses WebRTC with Matter’s end-to-end encrypted transport, which means streams are secured by the same trust model as other Matter devices rather than going through a vendor’s cloud relay.
What this means practically: a camera certified for Matter 1.5 should be accessible in Apple Home, Google Home, or any Matter controller that supports cameras, with live view, motion alerts, and snapshot retrieval working across ecosystems. Storage and more advanced AI features — package detection, face recognition — remain vendor-specific extensions and are not part of the base specification.
The camera implementation in practice is still catching up to the specification. As of mid-2026, camera support in the major ecosystems is present but uneven. Apple Home’s camera support for Matter 1.5 devices requires iOS 18.4 and later. Google Home supports Matter cameras in the Home app. The major camera brands — Aqara, Eve, Logitech — have committed to Matter 1.5 camera certification, with several models already certified.
Thread Mesh and Network Topology
One of Matter’s least-visible but most important features is how Thread handles the mesh network. Thread devices form a self-healing mesh — if one device loses power, routes around it automatically. Devices with consistent power (plugs, light switches) act as Routers and relay traffic for battery-powered devices (sensors, buttons) that operate as End Devices.
For edge computing purposes, the Thread Border Router is the critical piece of infrastructure. All the major controller hubs function as Thread Border Routers, but running multiple Border Routers on the same network improves resilience — if one hub loses power, the Thread Border Router function fails over to another.
The Apple HomePod mini and HomePod (2023) are particularly effective Thread Border Routers because they’re always-on, low-power devices. Google Nest Hub Max and Amazon Echo (4th gen and later) serve the same function. For a robust Thread mesh in a larger home, having at least two Border Routers from different manufacturers is recommended — they interoperate correctly under the Matter specification.
What’s Still Missing
Matter 1.5 is a substantial specification update, but the roadmap items still outstanding are worth noting.
Alarm systems are not yet in the specification. An intrusion alarm panel with sensors and sirens can’t be a Matter device as of 1.5. This is a significant gap for the security use case.
Appliances — washers, dryers, dishwashers, ovens — are not yet standardised beyond basic power monitoring. The HEMS cluster provides power draw data, but the appliance-specific control clusters aren’t defined.
Subscriptions and services tied to device capabilities remain vendor-specific. Cloud video recording, AI detection features, and similar value-add services are outside the specification scope deliberately — they’re vendor differentiation opportunities.
Interoperability in practice still requires testing. Matter certification verifies compliance with the specification, but the combination matrix of controller × device × network topology can surface edge cases that certification doesn’t catch. The standard has improved dramatically since 1.0, but complex multi-vendor setups still occasionally surface pairing or reliability issues.
Is It Worth Building On Now?
For home automation enthusiasts and developers building on Matter, 1.5 is a meaningful platform maturation point. The energy management additions are the most compelling for anyone building integrations with solar, EV, or battery storage systems — the protocol infrastructure for local HEMS coordination is now specified and implementable.
For consumers buying devices, the practical guidance is: look for Matter 1.5 certification on new purchases, particularly for cameras and energy devices. The interoperability is real, the local-first architecture is genuinely resilient, and the Thread mesh is reliable when set up correctly. The caveats are mainly at the edges — alarm systems, appliances, and advanced AI features remain outside what Matter covers.
The long-term trajectory is toward Matter as the baseline expectation for smart home interoperability, with vendor differentiation living above the protocol layer in cloud services and AI features. For the edge computing layer — local device control, automation, and data — Matter is becoming the credible foundation it was designed to be.