Smart Home
Smart Home IoT Development
Raonebytes builds connected smart-home prototypes: sensors, controllers, automation devices, lighting and security hardware, and cloud-connected consumer IoT products. We design the board, the radio front end, the firmware, the commissioning flow and the backend together, because in consumer IoT the parts that generate returns are almost always the joins between them.
The short answer
Smart home IoT development covers the connected hardware, radio design, commissioning flow, secure firmware and ecosystem integration needed for a consumer device that a non-technical buyer can set up in a few minutes and forget about. A mid-complexity connected home device typically costs $8,000 to $20,000 to prototype and takes 8 to 14 weeks, with simpler enclosed devices starting from $5,000. Most of the engineering effort goes into radio and antenna behaviour, provisioning, device identity and update safety rather than the app screens.
Common builds
Smart sensors
Connected controllers
Matter and Thread devices
Home automation hardware
Consumer IoT prototypes
What Raonebytes delivers
Connected PCB design
Wi-Fi, BLE, 802.15.4 and sub-GHz radio design with antenna placement, matching network and keepout worked out during layout, plus relay, sensor, power and enclosure-aware engineering.
Firmware, provisioning and OTA
Commissioning flows, control logic, telemetry and signed over-the-air update with rollback protection, structured so a failed update leaves a working device rather than a returned one.
Cloud, app and dashboards
Device registration, APIs, control and telemetry paths, alerts and dashboards, validated against real hardware instead of a simulator.
Pre-compliance and production handoff
Radiated emissions pre-scans, antenna tuning, safety-aware creepage and clearance review, BOM, Gerbers, assembly files, DFM notes and test procedures for your manufacturing partner.
What makes this hard
The constraints that decide whether a design survives contact with the real world.
Setup is the product for most buyers
A consumer judges a connected device on the first five minutes, and commissioning is where the hardware, phone app, home router and cloud all have to agree at once. Provisioning has to survive a captive-portal router, a 5 GHz-only SSID, a mistyped password and a phone that drops off Wi-Fi mid-flow, which means the retry and recovery paths need as much design attention as the happy path.
A crowded and unpredictable 2.4 GHz band
Wi-Fi, Bluetooth LE, Thread and Zigbee all share 2.4 GHz, and a real home adds microwave ovens, neighbouring networks, metal appliances and plasterboard with foil backing. Combo silicon needs coexistence arbitration configured properly, Thread and Zigbee channels need selecting away from the dominant Wi-Fi channel, and range has to be measured in a house rather than on a bench.
Antenna performance decided by the enclosure
A chip or trace antenna is only as good as its ground plane, keepout and the plastic, metal and battery sitting next to it. Tuning has to be done in the final mechanical assembly, and a design that skips this usually discovers the problem at the compliance lab, where the fix is a board respin.
Devices that must stay secure for years without attention
A smart-home device is internet-reachable, physically accessible to an attacker and expected to run for a decade with no user maintenance. That requires per-device credentials provisioned at manufacture, secure boot, signed firmware and an update path that keeps working long after the original development team has moved on.
Standards and protocols that shape the design
Identifying these early is what keeps them from forcing a redesign later.
- Matter and Thread
- Matter is the application and interoperability layer from the Connectivity Standards Alliance: it defines device types, clusters, commissioning and the security model, and it runs over Thread, Wi-Fi or Ethernet. Thread is one of those transports, a low-power IPv6 mesh built on IEEE 802.15.4 that needs a border router in the home, so choosing Matter still leaves the transport decision open and that decision drives power budget, silicon and range.
- Matter commissioning and device attestation
- Matter devices are commissioned over Bluetooth LE using an onboarding payload carried in a QR code or manual pairing code, then issued operational credentials for each fabric they join. Each unit needs a Device Attestation Certificate provisioned during manufacture under the Alliance PKI, alongside a Vendor ID and Product ID, which makes secure key injection a production-line requirement rather than a firmware detail.
- Zigbee and Z-Wave
- Zigbee also uses 802.15.4 radios but is not IP-based and reaches other systems through a hub or bridge, while Z-Wave runs in regional sub-GHz bands (around 908 MHz in North America and 868 MHz in Europe) with better wall penetration and lower throughput. Both have large installed bases, so a new product often has to interoperate with them even when its own stack is Matter.
- Ecosystem programmes: Apple Home, Alexa and Google Home
- Works with Apple Home, Works with Amazon Alexa and Works with Google Home are separate programmes, each with its own membership, functional testing, artwork rules and listing process, and Matter certification alone does not automatically grant any of them. We design to their published behavioural requirements so the device is ready for submission, and the manufacturer of record holds the certification and the listing.
- FCC Part 15, CE RED and product safety
- Intentional radiators need FCC Part 15 Subpart C authorisation in the United States and conformity under the Radio Equipment Directive in Europe, with harmonised standards such as EN 300 328 for 2.4 GHz and EN 301 489 for EMC. Mains-powered consumer equipment is assessed to IEC and UL 62368-1, which replaced the older IEC 60950-1 information technology standard, and household appliance or control products may additionally fall under IEC 60335-1 or IEC 60730.
Typical technology stack
Radio silicon
ESP32-C6 and nRF5340 class parts where Wi-Fi, Bluetooth LE and 802.15.4 are needed in one device, nRF52840 or EFR32MG for Thread and Zigbee nodes, and dedicated sub-GHz transceivers where wall penetration matters more than bandwidth.
Firmware platform
Zephyr, ESP-IDF or a vendor SDK with the open-source Matter stack layered on top, chosen mainly by which combination the silicon vendor actually maintains and certifies rather than by developer preference.
Security
Secure boot and flash encryption on the MCU, or a discrete secure element such as an ATECC608 or SE050 where keys must be isolated from application firmware, with per-device credentials injected at end-of-line test.
Update path
Dual-bank or A/B firmware slots with signature verification and anti-rollback counters, plus staged rollout on the server side so a bad build reaches a hundred units rather than the whole field.
Power
Coin cell or AA sensor designs budgeted around measured sleep current and radio duty cycle, and mains-powered devices designed against off-mode and networked-standby limits from the EU ecodesign rules for standby power, which constrain how much an always-connected device may draw when idle.
Cloud and app
Device registry, mutual TLS or token-based authentication, MQTT or a vendor IoT core for telemetry and control, and a mobile provisioning flow built with the same team that writes the device firmware so the two sides of commissioning are debugged together.
Why this matters
Smart-home hardware fails in ways a spec sheet does not predict: a device that pairs on the bench but not through a plasterboard wall, an antenna detuned by its own enclosure, a commissioning flow that assumes a cooperative router, or an update mechanism that bricks units in the field. Raonebytes designs the electronics, firmware, radio front end, enclosure and backend as one system, so those interactions surface during the prototype instead of after launch. We work to fixed quotes under NDA, and design for pre-compliance so radio and safety testing is a submission rather than a redesign. Our AI kids toy build is directly relevant here: a consumer connected device with an enclosure, audio, cloud services and parental controls, where usability and safety constrained the engineering as much as the electronics did.
Frequently asked questions
What does a smart home device prototype cost?
A mid-complexity connected consumer device typically runs $8,000 to $20,000 for a working prototype, covering custom PCB design, firmware, provisioning, enclosure and a cloud link. A simple enclosed device starts from $5,000. The main cost drivers are the number of radios, whether the product is mains powered, and how much ecosystem integration is in scope.
How long does a smart home build take?
Most connected consumer prototypes take 8 to 14 weeks from kickoff to a tested unit. Schematic and layout usually take 3 to 4 weeks, fabrication and assembly 2 to 3 weeks, and firmware plus commissioning and cloud integration the remainder. Antenna tuning in the final enclosure and app-side provisioning are the two steps most often underestimated.
What is the difference between Matter and Thread?
Matter is the application layer that defines how devices describe themselves, get commissioned and interoperate across ecosystems. Thread is one of the network transports Matter can run over, a low-power IPv6 mesh on 802.15.4 that needs a border router in the home. Matter also runs over Wi-Fi and Ethernet, so picking Matter does not by itself decide your radio, power budget or bill of materials.
Can you get our product certified for Apple Home, Alexa or Google Home?
Each ecosystem runs its own programme with separate membership, testing and listing requirements, and the manufacturer of record holds the certification, not us. What we do is design and build to their published requirements, exercise the behaviour they test for, and prepare the technical material so your submission is a formality rather than a rework cycle.
Do you handle FCC and CE radio certification?
We design for pre-compliance, run pre-scans where useful, tune the antenna in the final mechanical assembly and prepare the documentation pack, then support the submission to an accredited test lab. Formal FCC Part 15 authorisation and CE conformity under the Radio Equipment Directive are issued through that lab and held by the product owner. Using a pre-certified radio module reduces the radio testing burden but does not remove the unintentional-radiator and safety testing.
How do you handle firmware updates and device security?
We build secure OTA in from the start: signed firmware images verified by a secure boot chain, dual-bank or A/B slots so a failed update falls back to a working image, and anti-rollback protection so old vulnerable builds cannot be replayed onto a device. Device identity uses per-unit credentials injected at manufacture, held in MCU secure storage or a discrete secure element rather than a shared key baked into the binary.
Related capabilities
Build with Raonebytes
Send your requirements and get a fixed quote, typically within 24 hours. NDA on every project.