What makes a sensor harder to build than it looks
Door and window contacts, motion detectors, leak sensors and temperature sensors share one architecture: a low-power radio, a single sensing element, a battery and a small plastic enclosure. The electronics are modest. The difficulty is that each unit typically has to sleep at a few microamps for most of its life, join a network reliably, and leave the factory carrying unique identifiers and, for Matter products, security credentials that match the QR code printed on its label.
Most manufacturing risk therefore sits in three places: the radio and antenna, sleep current, and per-unit provisioning on the production line. A proven ODM platform can settle the first two. The third depends on how the factory’s programming and test stations are built, and it is the part most often left until pilot production.
Sensor types and what drives each one
| Sensor | Sensing element | What to watch in production |
|---|---|---|
| Door and window contact | Reed switch or Hall-effect sensor, plus a separate magnet | Magnet strength and the switching gap across tolerances; mounting on doors that do not close flush |
| Motion (PIR) | Pyroelectric sensor behind a Fresnel lens | Lens material and alignment set the detection pattern; false triggers near heaters and windows |
| Water leak | Exposed probe contacts | Contact plating and corrosion; sealing around the probes |
| Temperature and humidity | Digital sensor IC | Placement away from the battery and radio; venting; whether the IC’s factory calibration supports your accuracy claim |
| Air quality | Gas or particle sensor | Sensor lifetime and drift; power needs that often exceed what a coin cell can supply |
Combined products, such as a contact sensor with temperature, are common, and the extra hardware often costs little. Each added function still needs its own line test and its own claim on the packaging, so add them deliberately.
Choosing the radio and the module
Zigbee and Thread both run on IEEE 802.15.4 and suit coin-cell devices. Bluetooth Low Energy is used for direct phone connection and, in Matter, for commissioning. Wi-Fi sensors exist, but joining and transmitting on Wi-Fi costs more energy, so they usually need bigger batteries or accept slower reporting. The choice should follow the ecosystem your customers use: a Thread device needs a border router in the home, and a Zigbee device needs a compatible hub.
The second decision is whether to use a pre-certified radio module or design the radio onto your own board (“chip-down”):
- Module. Higher unit cost, less RF engineering, and in the US a module with its own grant can reduce the intentional-radiator testing needed for the finished product. The product still needs its own emissions testing and, in the EU, its own conformity assessment under the Radio Equipment Directive.
- Chip-down. Lower bill of materials at volume, but the antenna must be tuned inside the final enclosure, the product needs full radio testing, and some chipsets need per-unit RF calibration, such as crystal trimming, on the line.
The crossover point depends on your volume, the module premium and certification costs, so work it out with real quotes rather than a rule of thumb. The quote comparison calculator helps put one-off costs and unit prices on the same basis.
Many ODM sensors ship on the supplier’s own app and cloud. If you need your own app, Matter support or a specific ecosystem, confirm early who owns the firmware source, which SDK and license it depends on, who signs over-the-air updates and who holds the provisioning keys.
Battery life is decided on the production line too
Battery life depends on sleep current, reporting interval, event count, radio retries and battery behavior at low temperature. Specify it as a scenario, for example a number of door openings per day and a reporting interval at a stated temperature, rather than as a single number of years.
Design sets the expected sleep current; production decides whether every unit achieves it. A unit can pass every functional test and still draw far more current asleep than it should because of a leakage path from flux residue, a wrong resistor value, a damaged component or a firmware build that leaves a peripheral powered. Those units fail in the field months later, long after the lot has shipped.
The practical defense is to measure sleep current on every unit at end of line, with a limit derived from your power budget. That requires a fixture with precise low-current measurement and enough settling time, which adds seconds to the test cycle. Budget for it in the line design.
Two battery points are often missed. If batteries ship installed, an isolating pull tab or a firmware shipping mode protects them in the warehouse. And lithium coin cells shipped inside or with the device fall under dangerous-goods transport rules, so agree packing and documentation with the factory and the forwarder before the first shipment.
Provisioning and labeling
Every sensor leaves the line with a firmware image and a set of unique identifiers: a serial number, a radio address and, for Matter products, a device attestation certificate with its private key plus an onboarding code printed as a QR label on the device and packaging. The attestation certificate identifies your vendor and product and has to match the certified product, so the programming station must inject credentials securely and log what went into each unit.
A mismatch between what is stored in the device and what is printed on its label produces a sensor that cannot be set up, which is one of the costliest defects a connected product can ship with. Before pilot production, settle:
- Where credentials come from, who holds the keys and how they reach the factory
- How the station injects them and what it records
- How each label is printed and then scanned back against the device’s stored data
- What happens to the credentials of scrapped or reworked units
- How the production record links serial number, radio address, credential and firmware version
What to test on every unit
A sensor’s functional test can be short, but it should cover:
- Firmware programmed and version read back
- Radio performance, for example a packet test against a reference radio inside a shielded box
- The sensing element with a controlled stimulus: a magnet moved in and out, a heat source for PIR, a shorted probe for leak, a reference reading for temperature
- LED, button and tamper switch
- Sleep current against the limit
- Label scan-back against stored identifiers
Certification and market access
Typical requirements include FCC and ISED radio rules for North America, the Radio Equipment Directive for the EU and the UK’s radio equipment regulations for Great Britain (which currently still accept CE marking), plus RoHS and REACH declarations. Using the Matter or Zigbee name or logo requires certification through the Connectivity Standards Alliance, and voice assistant and platform programs have their own requirements. Certification samples should carry production-intent firmware and enclosures, so plan the sequence with the build schedule; product certification planning covers the order of work.
Questions to ask an OEM/ODM about its sensor platform
- Which products on this platform are shipping now, on which radio stack and SDK version?
- Can you share sleep current measurements from a recent production lot, not only a datasheet value?
- Who owns the firmware source, and who signs over-the-air updates?
- Can your line provision Matter credentials, and how are the keys protected?
- Which certifications exist for this platform, and in whose name are they held?
- Which battery supplier do you use, and what is your date-code policy for cells packed with the product?
Where Zefinity helps
The weak point in most sensor programs is the distance between an ODM’s demonstration unit and a line that provisions and tests every unit. Ask for production evidence on sleep current, credential handling and certification before a supplier is chosen; Zefinity’s supplier qualification work is built around collecting that evidence, and its NPI and launch support follows the provisioning and test stations through pilot production.
Frequently asked questions
Should a battery-powered sensor use Zigbee, Thread or Wi-Fi?
Zigbee and Thread were designed for low-power mesh networks and suit coin-cell sensors; Thread is the main low-power transport for Matter. Wi-Fi works when the product has larger batteries or mains power and can accept slower wake-ups. The right choice also depends on which hubs, border routers and ecosystems your customers already own.
Does a Matter sensor need its own certification?
Yes. A product sold under the Matter name or logo has to be certified through the Connectivity Standards Alliance, which involves membership and testing. Building on an already certified platform can reduce the testing needed, but the finished product still needs its own certification and must leave the factory with valid attestation credentials.
How long should a coin-cell sensor battery last?
There is no single figure. Battery life depends on sleep current, how often the device reports, how many events it sees, radio retries and temperature. Write the requirement as a usage scenario, then ask the supplier for current measurements taken on production units rather than an estimate built from datasheet values.