MatterODM by Shenan YangguangWhy the 2.4 GHz band is crowded
Wireless coexistence is the set of design and planning measures that let multiple radios sharing the 2.4 GHz band — typically Wi-Fi, Thread and Bluetooth — operate in the same home without one drowning out the others. The band is popular precisely because it is license-free and travels reasonably through walls, which is also why it is crowded: a typical home has a router, phones, a laptop, a speaker and a growing pile of sensors all talking there at once. For a security sensor the consequence is direct — a transmission that collides with a Wi-Fi burst may need a retry, and a retry on a door-open event is a delay the system can ill afford.
The good news is that the radios are not identical. Wi-Fi carries high-throughput traffic in wide channels, while Thread and Bluetooth use narrower channels and lower data rates, so with sensible channel selection the technologies normally share the band without one crippling the other. The work is in making that "normally" into "reliably," which is where both chip behaviour and enclosure design come in.
Channel planning: the highest-leverage step
Thread operates on a set of 2.4 GHz channels that overlap only partially with the Wi-Fi channels in common use, so selecting a Thread channel that sits clear of the home's primary Wi-Fi channel is the single most effective coexistence measure a planner can make. In practice this means the installer or the setup software looks at where Wi-Fi energy is concentrated — often on channel 1, 6 or 11 in one region, or 1, 5, 9 and 13 in another — and steers the Thread mesh to a channel least overlapped. A factory cannot know the buyer's Wi-Fi layout in advance, so the right design is to support channel selection and to ship a sensible default that the setup experience can refine on-site.
Clear-channel assessment
Clear-channel assessment is the mechanism by which a radio listens before transmitting and waits for a quiet moment, so it is far less likely to fire into the middle of a Wi-Fi frame and force a collision and retry. This is a behaviour of the connectivity silicon, but whether it is enabled and tuned correctly is something a factory verifies rather than assumes. For a battery security sensor, clear-channel assessment also interacts with the sleep budget: listening costs energy, so the implementation balances politeness against battery life. We tune that trade explicitly rather than leaving it at a datasheet default.
The enclosure is part of the RF design
A sensor's enclosure is part of its RF design, not just its industrial design, because metal, conductive coatings, battery placement and wall thickness all change the antenna's effective range and its exposure to interference. A contact sensor that sits half behind a steel door frame, or a PIR in a metal-faced housing, can see its antenna detuned or shadowed in ways a bare-board test never reveals. This is why we treat the finished, cased, battery-installed unit as the thing we actually measure, and why we advise brands against last-minute enclosure changes that were never RF-validated.
The antenna and the enclosure together set the sensor's real-world range and its resilience to neighbouring transmitters, so range is an outcome of mechanical and RF co-design rather than a number printed on a module's datasheet. The connectivity module provides the radio, but how that radio performs once buried inside a small, often metal-adjacent, battery-powered shell is our engineering responsibility. The broader radio-certification picture — antenna, range and the product-level tests a brand must pass — is covered in our article on antenna, range and radio certification for Matter sensors.
Bluetooth's role at commissioning time
Bluetooth Low Energy is commonly used to carry the Matter setup information from a phone to a new device during commissioning, so it briefly shares the 2.4 GHz band at the exact moment a user is pairing a sensor. Coexistence planning therefore includes commissioning: the device must bring up BLE, exchange the credentials and hand off to Thread without the two radios fighting each other on the bench or in a Wi-Fi-busy living room. We validate the commissioning sequence under a live Wi-Fi environment rather than in a quiet lab, because that is the condition the customer actually experiences. The onboarding and multi-admin workflow that surrounds this is discussed in our article on Matter onboarding and multi-admin for security brands.
What the factory controls versus the installer
The factory controls the module integration, the antenna and enclosure RF performance, the default channel and power settings, and the validation of behaviour under a busy 2.4 GHz environment, while the installer controls on-site channel planning and where devices are physically placed. This split matters because neither side can fully own reliability alone. We hand over hardware that is well-behaved in a crowded spectrum and a sensible default channel; the installer (or the setup software we help design) makes the final on-site choices. A brand that understands this split avoids blaming the module for a placement problem, or the installer for a device that was never RF-validated.
Verifying coexistence before shipment
Coexistence is verified by testing the sensor's message delivery and latency while a busy Wi-Fi and Bluetooth environment runs alongside it, and by confirming the device uses clear-channel assessment and selects a clean channel — rather than testing the radio only in an empty anechoic chamber. An empty-chamber report proves the radio works in isolation; it does not prove the device behaves next to a streaming router. Our validation includes a stressed 2.4 GHz environment so that the "it worked in the lab" gap does not become a field support ticket. The factory-validation programme this sits inside — EMC pre-scan, environmental and life testing — is described in our article on how a factory validates a Matter security sensor before shipment.
Factory stance
Shenan Yangguang designs, prototypes, validates and mass-produces the Matter security hardware, and we treat coexistence as a first-class design requirement rather than a hope. We integrate a standard CSA-certified Matter connectivity module as the radio component, then own the antenna integration, enclosure RF performance, default channel and power tuning, and the stressed-environment validation that proves the sensor holds up next to real Wi-Fi and Bluetooth. We do not relabel a third party's RF design and present it as our own. Where a specific coexistence behaviour depends on the buyer's network — channel selection, placement, neighbouring transmitters — we state that openly and build the setup experience to handle it, because a security sensor that fails only in a busy home is the worst kind of failure to discover late.