CasaSmart guide
Detailed comparison: mesh network, latency, ecosystem support, prices and availability in Moldova.
CasaSmart
Zigbee and Matter are the two names that come up most often when you choose smart devices in 2026, but they are not the same kind of thing and they do not cancel each other out. Zigbee is a mature radio protocol with its own mesh network on the 2.4 GHz band, used for years for bulbs, sensors, switches and plugs. Matter, by contrast, is not a new radio technology but an application and interoperability standard that runs over IP networks: Wi‑Fi, Ethernet and Thread. In short, Zigbee answers the question "how do devices physically talk to each other", while Matter answers "how do devices from different brands understand each other, regardless of the app you use".
The confusion appears because both are tied to the smart home, and Matter often leans on Thread, a mesh radio very similar to Zigbee at the physical layer. That is why many people think they must pick one over the other, or that Matter "replaces" Zigbee overnight. In reality, in 2026 the two coexist: you have a huge, inexpensive and well‑tested Zigbee catalogue, and a growing Matter layer that promises portability across ecosystems. The right call depends on which devices you want, which hub you run, and how much you value fully local control.
In this guide we compare the two honestly, with no invented numbers: what each one is, how mature it is, device availability, local versus cloud control, the Thread vs Zigbee difference, real‑world interoperability, and how Home Assistant supports both. The goal is not to crown a winner, but to help you understand when each makes sense for a home in Moldova.
TL;DR
Zigbee is a mature mesh radio with the largest device catalogue and solid local control; Matter is an interoperability standard over IP (Wi‑Fi/Thread) that links ecosystems. In 2026 you don't pick just one — Home Assistant runs both, and combining them is often the best answer.
Step 1
Zigbee is a low‑power 2.4 GHz radio protocol built on the IEEE 802.15.4 standard that forms a mesh network: a coordinator (usually a USB stick or gateway) runs the network, mains‑powered devices (bulbs, plugs, relays) act as routers and extend coverage, and battery sensors are "end devices". A message hops from node to node, so the more mains‑powered devices you have, the more stable the network. Its historical weak point was the application layer: the same "Zigbee" label did not guarantee that one brand's device would pair correctly with another's hub. That gave rise to open solutions like Zigbee2MQTT and ZHA that normalise behaviour.
Step 2
Matter is an application and connectivity standard, developed under the Connectivity Standards Alliance, that defines how devices are described and controlled over IP. It is not a radio: a Matter device can use Wi‑Fi, Ethernet or Thread as its transport. Its big advantage is "multi‑admin" — the same device can be added to several ecosystems at once (for example Apple Home, Google Home, SmartThings) by sharing a pairing code, without moving it exclusively to one. Commissioning is usually done by scanning a QR code. Importantly, Matter standardises device types, so a feature only exists in Matter if that type has been specified — at launch whole categories were missing and have been filled in gradually through successive versions.
Step 3
At the physical layer, Thread and Zigbee are close relatives: both use the same 802.15.4 radio on 2.4 GHz and form low‑power mesh networks. The key difference is that Thread is IP‑native — every node has its own address and can be routed directly, without being "translated" by a gateway, which fits the Matter model perfectly. Zigbee, by contrast, has its own stack and needs a coordinator that translates between the Zigbee network and your home network. For Thread you need a "border router" (present in many modern speakers and hubs) that links the Thread network to Wi‑Fi/Ethernet. In practice: the same physical propagation rules, but different network architectures.
Step 4
Here Zigbee has a clear lead in 2026: a vast, inexpensive catalogue proven over years — door, motion, temperature and humidity sensors, bulbs, in‑wall relays, switches, thermostatic heads, wireless buttons. Many are affordable and easy to source. Matter is growing fast, but coverage across device types is uneven: core categories (bulbs, plugs, sensors, locks) are well represented, while advanced features or specific niches may be missing or only partly exposed. On top of that, some "Matter" devices add extra features only through their own app. The honest verdict: for catalogue breadth, Zigbee; for guaranteed cross‑ecosystem portability on the basics, Matter.
Step 5
For a resilient home that keeps working without internet, local control matters. Zigbee, via Zigbee2MQTT or ZHA on Home Assistant, runs fully locally: pairing, automations and commands stay in the house, with no dependence on a manufacturer's servers. Matter is designed to be able to work locally over your IP network, and Thread does not require internet to operate — but in practice some commissioning steps or manufacturer‑app features may temporarily ask for an account or a cloud connection. With Home Assistant acting as the Matter controller, day‑to‑day control is local. The recommendation for Moldova, where internet outages are not rare: prioritise solutions that keep automation logic in the home, whatever the protocol.
Step 6
Here Matter's core mission shows: you can buy a device and add it to your preferred ecosystem (Apple, Google, SmartThings, Amazon) without being locked to one brand, with the option to share it across several at once. With Zigbee, real interoperability depends heavily on the hub: an open coordinator with Zigbee2MQTT/ZHA accepts devices from dozens of makers, while a closed brand gateway may only accept that brand's products. In short, Matter brings a promise of standardised portability "out of the box", while Zigbee offers broad interoperability provided you use an open platform. The two are not rivals: Home Assistant can unite them, exposing both Zigbee and Matter devices in the same interface.
Step 7
Home Assistant is where the comparison becomes moot, because it runs both at once. For Zigbee you have two routes: ZHA (native integration, no extra broker) or Zigbee2MQTT (a separate, very flexible layer with excellent support for new devices). For Matter, Home Assistant includes a Matter Controller and an OpenThread Border Router that can be powered by a compatible radio adapter. So a single radio coordinator with multiprotocol firmware can, in many scenarios, serve both Zigbee and Thread. The result: you pair cheap Zigbee sensors and Matter/Thread devices in the same home, write automations that combine them, and keep everything local. This is the approach we recommend in CasaSmart integrations.
Step 8
Simple rules, no absolutes. If you want the largest number of sensors and devices on a small budget with fully local control, start from a Zigbee base on Home Assistant. If you want to buy a device and use it in Apple Home and Google Home in parallel without hassle, Matter is the right bet for that device. For a new‑build, plan a Thread border router from the start and mix freely. For a renovation where you already have Zigbee bulbs and sensors, throw nothing away — add Matter where it brings portability. And don't forget wired relays/switches (for example Shelly, where we are an official distributor), which solve retrofit on the existing wiring regardless of the radio protocol you choose.
The most common mistake is to think Matter is a radio that "replaces" Zigbee and to throw away good gear. Matter is an interoperability layer over IP, not a physical substitute. Other traps: buying Matter‑over‑Thread devices without a border router; expecting features that simply aren't specified in Matter yet; and mixing in a closed brand gateway hoping it will accept any Zigbee device. Plan the architecture before you buy.
No. They are different things: Zigbee is a mesh radio, Matter is an interoperability standard over IP that can use Thread, Wi‑Fi or Ethernet. In 2026 they coexist. Zigbee still leads on catalogue breadth and device price, while Matter brings cross‑ecosystem portability. They work best together, under a shared controller like Home Assistant.
Not necessarily. Your existing Zigbee devices keep working through your coordinator (ZHA or Zigbee2MQTT) and can be exposed further to different interfaces. Add Matter devices only where they bring a concrete benefit, for example portability between Apple Home and Google Home. There is no point replacing good gear just for the Matter label.
Yes, and it is often the best solution. Home Assistant runs Zigbee (ZHA or Zigbee2MQTT) and Matter at the same time, with a Thread border router included. You can write automations that combine a cheap Zigbee sensor with a Matter device and keep everything local. In CasaSmart integrations we frequently design exactly this kind of hybrid architecture.
Day‑to‑day control can be local: Thread needs no internet, and with Home Assistant as the Matter Controller commands and automations run in the house. Note, however, that some commissioning steps or manufacturer‑app features may temporarily require an account or cloud. That is why we recommend platforms that keep automation logic local — helpful during the internet outages that are not rare here.
A Thread border router is the device that links the Thread mesh network to your IP network (Wi‑Fi/Ethernet). You only need one if you use Matter‑over‑Thread devices; many modern speakers and hubs include one, and Home Assistant can provide an OpenThread Border Router. If you stay on Zigbee or Matter‑over‑Wi‑Fi, you don't need a Thread border router.
● CasaSmart · Chișinău
CasaSmart can configure the Home Assistant automation and test it on real devices.