Firmware for smart home, wearables and consumer IoT
Consumer devices get updated by people who never asked for an update, over a phone that may leave the room halfway through. The firmware has to cope, and the rules now expect it to.
Key characteristics
- Typical radios
- Bluetooth LE, Wi-Fi, Thread and Matter
- Update routes
- Phone app, home hub, or Wi-Fi to your cloud
- Rules to plan for
- UK PSTI, EU CRA, US Cyber Trust Mark
- Not offered
- Certification or legal advice
Smart locks, sensors, lights and wearables share a hard environment. They sit on home networks nobody set up with them in mind. They depend on a phone app that the phone’s operating system can pause at any moment. Their owners do not read release notes, and a device that stops working after an update usually comes back as a return or a one-star review.
Consumer devices now also face security rules of their own. The UK has enforceable rules, the EU has a regulation whose reporting duties already apply, and the US has a voluntary label that is still being set up. Each one asks you to say how long you will keep fixing the device, and then to keep doing it.
Updates through a phone app
Many wearables and Bluetooth LE devices have no internet connection of their own. The phone app carries the update: it downloads the new image from your server and passes it to the device over Bluetooth LE. That design works well if the firmware treats the phone as an unreliable courier.
- The device checks the signature, not the app. The bootloader verifies the image with your public key before running it, so a modified app or a compromised phone cannot install firmware you did not sign.
- Transfers resume. Apps get backgrounded and phones walk out of range. The device keeps the partly received image and the app picks up where it stopped.
- The old image stays until the new one proves itself. The new image boots in a test state and confirms itself only after its self-test passes. If it never confirms, the device goes back to the version that worked.
- Battery comes first. A wearable checks its charge before accepting an update and refuses one it cannot finish.
Transfer time depends on your radio settings and on the phone. Per the Bluetooth SIG, the largest LE data payload grew from 27 octets in Bluetooth 4.0 and 4.1 to 251 octets in 4.2, and Bluetooth 5 added an optional 2M PHY that in theory gives about 1.7 times the bandwidth of 4.2. Phones do not all support the same options. Model your own numbers with the Bluetooth LE update time calculator.
Matter and Thread
Matter is a smart home standard whose open-source SDK, guided by the Connectivity Standards Alliance, works over Thread and Wi-Fi network transports. The SDK includes over-the-air update roles: an OTA Requestor on the device asks an OTA Provider whether newer software exists, downloads it, and in the SDK’s reference app refuses any image whose version is not newer than the one running. Matter decides how the image is found and delivered. Your bootloader, flash layout and signing still decide whether it is safe to run. We work with the Matter SDK and Thread on the connectivity side; we do not certify products.
Security rules for consumer devices, as of November 22, 2026
This summary follows the regulators’ own pages as checked on November 22, 2026. It is not legal advice; confirm how each rule applies to your product with a qualified adviser.
| Rule | Status | What it asks for |
|---|---|---|
| UK Product Security and Telecommunications Infrastructure (PSTI) regime | In effect since April 29, 2024 | Passwords unique per product or set by the user; published information on how to report security issues; a published minimum security update period with an end date |
| EU Cyber Resilience Act, Regulation (EU) 2024/2847 | Reporting duties have applied since September 11, 2026; main obligations apply from December 11, 2027 | Report actively exploited vulnerabilities and severe incidents (early warning within 24 hours, notification within 72 hours); security updates free of charge over a support period of at least five years, unless the product is expected to be in use for less; automatic security updates on by default where applicable, with an opt-out; an SBOM covering at least top-level dependencies |
| EU Radio Equipment Directive cybersecurity act, (EU) 2022/30 | Applied since August 2025; repealed with effect from December 11, 2027, when the CRA takes over | Cybersecurity requirements for radio equipment until the CRA applies |
| U.S. Cyber Trust Mark (FCC) | Voluntary label for wireless consumer IoT; not yet open to product applications | When it opens, the registry behind the label’s QR code will show whether updates are automatic and the product’s minimum support period end date |
The U.S. program has moved several times. UL Solutions withdrew as Lead Administrator effective December 19, 2025, and ioXt Alliance took the role effective April 13, 2026. In 2026 the FCC opened a filing window for label administrators (August 11), recognized accreditation bodies (September 28) and sought comment on label design and post-market surveillance (October 27). It will announce when the program can accept products; until then, nobody can apply for the label.
What we build toward
Taken together, these rules point at the same work: a way to ship security fixes, a way to take in vulnerability reports, a record of the software in each release, and a support period you can keep. We produce that evidence as part of the work:
- A signed update path with tested rollback (over-the-air updates).
- An SBOM generated for every release, and a vulnerability intake and triage process.
- A written support-period statement agreed with you, and a release plan that can keep it, through sustaining releases.
- A runbook for the CRA’s 24-hour and 72-hour reporting clocks if you sell in the EU.
We help you prepare; we do not certify products or declare them compliant. More detail is on firmware security and in the security and regulation section of Field Update.
Where to start
If your device is heading for retail shelves or an app store listing, request a firmware review. We read your schematics, code, flash layout and update plan, including the app’s side of the update, and send a written plan with the risks and the order of work.
Send us your board and your plan.
A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.
Or email sales@fumbar.com, or call (720) 675-4202.