Matter arrived with an unusually large promise: buy any device with the logo and it will work with whatever you already own. No bridges, no vendor apps, no checking compatibility lists.
It hasn't fully delivered that. It has delivered more than the sceptics expected. The truth sits in between, and it's worth knowing where.
What Matter actually is
Matter is a shared language, not a radio.
This is the most common misunderstanding about it, and it makes everything else confusing. Zigbee, Thread and WiFi are how a signal physically travels. Matter is what a device says once the signal arrives: how it announces "I am a dimmable light", what "set brightness to 40%" looks like, how it gets paired and secured.
So Matter runs over other things, namely WiFi, Ethernet or Thread. A Matter bulb is a WiFi or Thread bulb that speaks a standard vocabulary. Our protocol guide goes deeper into the layer distinction, which explains most of the confusion in this space.
The problem it was built for
Before Matter, every ecosystem had its own vocabulary. Manufacturers either implemented several of them badly or picked one and abandoned the rest. Buying a device meant checking whether it worked with your particular setup, and the answer was often "yes, via a bridge", which is a way of saying no.
Matter is backed jointly by Apple, Google, Amazon, Samsung and others, which is what makes it credible. Those companies had spent a decade competing on incompatibility and worked out that it was costing all of them more than it earned.
What works now
Pairing really is better. Scan a code and the device joins, and in the good cases it shows up across several ecosystems without a vendor app anywhere.
Basic control is reliable. Lights, plugs, switches, locks, thermostats. On, off, brightness, colour, setpoint. The everyday operations mostly just work.
It's local by default, which is a significant win that nobody talks about much. Matter is designed to operate on the local network, so Matter-over-Thread and Matter-over-WiFi devices can be controlled without a round trip through a vendor's cloud.
And multi-admin means one device can be controlled by several ecosystems at once, instead of being claimed by whichever app set it up first.
Curious whether Nexop fits your home?
Book a live demo, run by one of the founders rather than a salesperson. Or join the waitlist and hear from us the day it ships.
What still doesn't
Advanced features fall back to the vendor app. Matter standardises the common denominator, so a robot vacuum's start and stop may be standard while its mapping and zones aren't, and you end up keeping the manufacturer's app anyway.
Ecosystems sit at different versions. Matter reached 1.4 in late 2024 and has kept iterating, but platforms adopted it at very different speeds. It's entirely normal to find two Matter devices whose supported features don't quite line up, and the logo won't tell you which version anything implements.
"Matter" on the box doesn't tell you the transport. A Thread device needs a Thread border router. A WiFi Matter device doesn't. Both say Matter. This is the single most common cause of "why won't this pair".
And Matter doesn't reach backwards. Your existing Zigbee sensors are still Zigbee, and something still has to bridge them.
Should it change what you buy?
Prefer Matter when everything else is equal. More ecosystems will speak it, and it lowers the odds of a device being orphaned by a vendor's decision.
Don't pay a large premium for the logo, though, especially on devices whose interesting features live outside the standard anyway.
Check the transport before buying. If it's Thread, confirm you have a border router, and if you don't, that's a second purchase rather than a detail.
And don't replace working hardware for it. Perfectly good Zigbee kit doesn't need retiring because a newer standard exists. That's an expensive way to solve a problem you might not have.
Our side of it
Nexop supports Matter natively, alongside Zigbee, KNX and WiFi. Zigbee because it's what most existing sensors use, Matter because it's where new devices are heading. Supporting only one would strand you in one direction or the other.
One specific limitation, which is the advice above applied to us: our Matter support runs over WiFi and Ethernet, not Thread, at launch. A Thread-only Matter device would need a border router we don't currently provide. If your home is built around Thread devices, Homey Pro has a Thread radio and we don't.
Nexop is pre-launch. If you're working out what to buy right now, the FAQ covers compatibility plainly, and you can book a demo to ask about a specific device rather than a category.