Homey Centralizes Firmware Updates for Matter, Zigbee, and Z-Wave Devices
According to Android Authority, Homey has rolled out a new "Device Updates" feature in app version 9.10.0 that pushes firmware to Matter, Zigbee, and Z-Wave devices from a single interface — finally…

According to Android Authority, Homey has rolled out a new "Device Updates" feature in app version 9.10.0 that pushes firmware to Matter, Zigbee, and Z-Wave devices from a single interface — finally putting a dent in the multi-app shuffle that plagues anyone running a genuinely mixed smart home.
One Pane of Glass, Three Protocols
The feature lives behind the three-dot menu (More → Settings → Device Updates, sitting right under System Updates), with a secondary entry point tucked into each device's Maintenance tab. Under the hood, the routing splits cleanly by protocol: Matter updates pull from the Connectivity Standards Alliance's Distributed Compliance Ledger, while Zigbee and Z-Wave updates are sourced from their respective vendor apps embedded within Homey itself.
For the user, it reads like a simple pending-updates queue. For the tinkerer, it's a clean abstraction layer — Homey becomes the orchestrator that negotiates with three different update transports on your behalf, sparing you the ritual of opening six manufacturer apps to chase a security patch. Coverage extends to Homey Cloud, Homey Pro (2023–2026), Homey Pro mini, and the Self-Hosted Server, so both cloud renters and self-hosters get the same single-update surface.
The Catch: Manufacturer Opt-In
Here is the part the marketing copy glosses over: Matter updates will arrive automatically because the DCL pipeline is open by design. Zigbee and Z-Wave updates, on the other hand, are gated by individual manufacturer participation. Homey names IKEA, Aeotec, Zooz, frient, and ThirdReality as already on board, with more reportedly in the pipeline — but if your favorite brand hasn't shipped an update-capable integration yet, you will still be hunting firmware the old-fashioned way.
Think of it as a webhook with conditional triggers: the pipeline is built, but the payload only fires when the upstream vendor exposes the right endpoint. Until then, that device is dead weight in the queue.
What to Watch
Homey has a separate product announcement slated for September 1 at 7 PM CEST, which suggests this Device Updates rollout is groundwork for a bigger play — possibly a hub refresh or a new bridge module aimed at the same fragmentation pain point. Keep an eye on whether the September reveal ties back to the update pipeline, and audit your current Zigbee/Z-Wave device list to see which vendors are already wired in. If half your mesh still relies on manufacturer apps, the practical win here is real but partial — exactly the kind of incremental plumbing that makes the whole stack less annoying without solving the walled-garden problem outright.