Homey Gains Matter 1.5 Certification to Streamline Energy Device Integration

The update widens the bridge's energy-device reach — EV chargers, heat pumps, solar panels, and major appliances — while continuing to translate Zigbee, Z-Wave, infrared, Bluetooth, 433 MHz, Wi-Fi, and a long tail of proprietary APIs into something Apple Home, Google Home, Alexa, SmartThings, and Home Assistant can actually parse. For automation engineers running multi-vendor stacks, this is one of the cleanest payload conversions currently on the market.

Beyond the badge: what Matter 1.5 actually unlocks

The version number matters more than usual here. Homey is reportedly one of the few smart-home controllers certified for Matter 1.5 right now — Amazon Alexa still sits on Matter 1.0, Apple and Google are on Matter 1.4, and Home Assistant trails on Matter 1.3. That delta translates directly into feature parity: the new energy clusters let the hub expose consumption data, control state, and report faults on devices that previously required a vendor app to do anything useful.

For the automation crowd, energy clusters are the payload type you've been waiting for. Instead of scraping inverter telemetry through a flaky REST endpoint or polling a vendor cloud every thirty seconds, your hub can treat solar output, grid draw, and EV charging as first-class entities — triggers, conditions, and logic gates that fire on real power measurements rather than approximations. Pair that with home battery state and you finally get orchestration logic that doesn't fold the moment the vendor API rate-limits you or the manufacturer's cloud has a quiet outage.

The bridge that actually earns its keep

Homey's multi-protocol stack already covers Zigbee, Z-Wave, infrared, Bluetooth, 433 MHz, Wi-Fi, and a grab bag of proprietary APIs. The Matter Bridge app then maps those endpoints into standard accessory representations — lights, sockets, thermostats, locks, window coverings, and sensors — and forwards them downstream to the platforms you actually use. Control stays local on the Homey side; the downstream systems just see the abstract accessory shape they expect to receive, which means latency stays low and automations don't collapse when someone else's cloud misbehaves.

Athom CEO Stefan Witkamp framed the design philosophy plainly: "Most people already own devices that will never speak Matter natively, and those should stay just as usable as anything they buy tomorrow." That's a stance most automation tinkerers wish the big three had internalized years ago — your existing gear shouldn't become e-waste just because the spec shipped without your protocol of choice.

What to verify before you re-pair everything

Energy clusters are notoriously uneven across vendors, and Matter 1.5 certification doesn't guarantee your specific inverter, heat pump, or EVSE actually publishes the attributes the bridge relies on. Before you start reassigning devices, check three things: whether your target hardware exposes the energy-reporting fields the bridge expects (read the device's Matter implementation details, not the marketing page), whether your downstream platform — Apple Home, Google Home, Alexa — consumes the new energy data rather than silently dropping it, and whether your fallback rules still fire correctly when the bridge momentarily loses connection. Run a staged migration, one device category at a time, so a bad firmware push can't black out your entire energy graph. And keep a pre-1.5 backup of your Homey flows; local-execution semantics can shift as new clusters get parsed, and you don't want to discover that during a heatwave with the AC in the wrong state.