top of page

Key Considerations in Smart Home Product Development: Design, Connectivity and Integration

Writer: M Gopinaga Bharath
M Gopinaga Bharath
Nov 6
12 min read

Understanding the technologies behind smart home connectivity, their differences, and the key factors involved in choosing the right solution for reliable product integration.


Smart home devices including a smart lock, thermostat, sensors and speaker connected to a smartphone app

Consider a customer setting up a smart thermostat. It connects to the home network and works as expected. A few days later, it goes offline or does not reconnect properly after the router is restarted. The customer is unlikely to know whether the problem is with the device, the router or the setup process. For the manufacturer, this can lead to support requests, returns and time spent investigating issues that could have been avoided during development.


This is why connectivity needs to be considered early in smart home product development. The choice of wireless technology affects battery life, range, data transfer, setup, security and how the product works with other devices.


There are several options available, including Wi-Fi, Bluetooth Low Energy (BLE), Zigbee and Thread. Matter adds a common application layer that helps supported products work with different smart home platforms. These technologies are not interchangeable. The right choice depends on what the product needs to do and where it will be used.


What Is Smart Home Product Development?


Smart home product development involves designing and building connected products for use in homes. Depending on the product, this can include electronics, embedded firmware, wireless connectivity, mobile apps, cloud services, user interfaces, security and product testing. Regulatory requirements also need to be considered based on the product and the markets where it will be sold.


These products can include lighting controls, thermostats, door locks, cameras, motion sensors, smoke and gas detectors, smart plugs and connected appliances. Their requirements are quite different. A camera needs enough bandwidth to transfer video, while a door or window sensor may only send a status update when it is opened or closed. The sensor may also need to run for a long time on a small battery.


There is no single wireless technology that suits every product. Before deciding, the team needs to look at range, data rate, power consumption, response time, network setup, compatibility requirements and the markets in which the product will be sold.


Choosing a protocol is only one part of the decision. The hardware, firmware, app and network setup also need to work together and meet the product's requirements.

Where Does Zigbee Fit in Smart Home Products?


Zigbee is a low-power wireless technology used in smart lighting, sensors, switches and other connected devices. Most products use IEEE 802.15.4 radios in the 2.4 GHz band. The wider IEEE 802.15.4 standard also supports other frequency bands in some regions and applications.


Zigbee supports mesh networking. In a typical setup, powered devices that support router functionality can pass messages between devices and help extend network coverage. Battery-powered devices usually connect through another device and do not forward messages for the rest of the network. Actual coverage depends on the layout of the building, device placement, interference and the number of powered routing devices.


Zigbee has been used in smart home products for many years and has an established device ecosystem. The Zigbee Cluster Library defines common device functions and commands. However, using Zigbee does not automatically mean that every product will work with every hub or platform. Compatibility depends on the device type, supported clusters, certification and the way each product has been implemented. The Connectivity Standards Alliance released Zigbee 4.0 in November 2025, including the Suzi sub-GHz feature for supported use cases. The available frequency band and certification route should be checked for the intended market and product.


Zigbee operates in the 2.4 GHz band alongside Wi-Fi and Bluetooth, so interference and channel selection need to be considered during design and testing. Zigbee also has its own networking framework rather than using IP directly at the device network layer. A hub or gateway is commonly used to connect the Zigbee network to an app or other IP-based services.


Zigbee can be a practical choice when a product needs to work with an established Zigbee ecosystem or when the target application and installed base make it a suitable option. It should be evaluated alongside Thread, BLE and Wi-Fi rather than treated as a default for every low-power product.


What Is Matter?


Matter is a smart home application-layer standard developed by the Connectivity Standards Alliance (CSA). It aims to make it easier for products to work with different supported smart home platforms. For manufacturers, this can reduce the amount of separate integration work needed for each ecosystem, although it does not remove all platform-specific work.


Matter works over IP networks such as Wi-Fi, Thread and Ethernet. Bluetooth Low Energy is commonly used during setup, for example when a phone discovers and commissions a new device. It is not the only commissioning option: Matter 1.4.2 added Wi-Fi-only commissioning support for compatible implementations, and Matter 1.6 added NFC-based commissioning. Once setup is complete, the device uses its selected operational network, such as Thread, Wi-Fi or Ethernet.


Matter support does not mean every feature will be available on every platform. It varies with the device type, the features implemented and what each ecosystem supports. Manufacturers still need to test setup, device control, status updates, firmware updates and the overall user experience on the platforms they plan to support.


Matter continues to develop, with new device types and features being added through later releases. Matter 1.5 introduced support for cameras, closures, soil sensors and additional energy-management features. Matter 1.5.1 followed with improvements to camera streaming and related device types. Matter 1.6, released in June 2026, focused on setup, multi-ecosystem experiences and device status and control improvements. When planning a new product, check the latest specification and the support available in the chipsets, SDKs and ecosystems you intend to use.


Matter is worth considering for a new product when compatibility with multiple smart home platforms is an important requirement. However, it is still necessary to check the supported device type, available chipsets and software, memory requirements, power consumption, certification process and target markets before making the decision.


Where Does Thread Fit?


Thread is a low-power wireless mesh networking protocol based on IPv6 and IEEE 802.15.4. It uses 6LoWPAN to support IPv6 communication over the low-power wireless network. It is mainly used for connected products such as sensors, switches, locks and lighting controls.


Thread devices have different roles in the network. Powered devices with router capability can forward messages and help extend the mesh. Battery-powered devices can operate as sleepy end devices. They communicate through a parent router and do not route messages for other devices. This is important when planning network coverage and estimating battery life.


A Thread Border Router connects the Thread network to another IP network, such as Wi-Fi or Ethernet. This function can be built into a compatible home hub, router or other device, so it does not always need to be a separate product. The Thread network can continue to operate locally without an internet connection, but remote access and cloud services need an internet connection.


Thread and Matter are related, but they are not the same thing. Thread provides the low-power IP mesh network. Matter defines how supported devices communicate at the application level and how compatible platforms control them.


What Is the Difference Between Zigbee, Thread, Matter and Wi-Fi?


These technologies don't all do the same job. Matter is an application-layer standard, while Wi-Fi, Thread, Zigbee and BLE provide different ways for devices to communicate. The comparison below is a starting point.


Technology

Role

Network approach

Typical strengths

Common applications

Zigbee

Wireless networking and application framework

Low-power mesh

Mature device ecosystem and low-power operation

Lighting, switches and sensors

Thread

IP-based wireless networking

Low-power IPv6 mesh

IP connectivity, mesh routing and support for sleepy end devices

Matter-enabled sensors, locks and lighting controls

Matter

Application-layer interoperability standard

Uses IP networks such as Thread, Wi-Fi and Ethernet

Common device behaviour across supported ecosystems

Compatible smart home devices across supported platforms

Wi-Fi

Wireless local-area networking

Typically infrastructure-based through an access point

Higher data throughput and direct IP network connectivity

Cameras, media devices and connected appliances

Bluetooth Low Energy

Short-range wireless communication

Direct links and supported Bluetooth network modes

Low-power nearby communication and phone connectivity

Commissioning, provisioning, accessories and nearby control


Where Does Bluetooth Low Energy Fit?


Bluetooth Low Energy is useful when a product needs to communicate with a nearby phone or accessory without using much power. In smart home products, it is often used for initial setup, provisioning and nearby control.


BLE can also be the main connection for products that only need short-range communication. However, it is not a replacement for Thread or Zigbee where devices need to pass messages across a larger area using a mesh network.


When Should a Smart Home Product Use Wi-Fi?


Wi-Fi is often a good option for products that need to transfer more data or connect directly to the home network. Cameras, video doorbells, media devices and some appliances are examples.


A Wi-Fi product can connect directly to the home router, so it may not need a separate Zigbee hub or Thread Border Router. This can keep the product setup simple. However, the customer still needs good Wi-Fi coverage and a reliable setup process.


Power consumption is one of the main things to consider. A Wi-Fi device that needs to stay connected all the time can be difficult to run from a small battery. The design needs to account for transmit and receive current, sleep modes, connection intervals, signal strength and how often data is sent. Wi-Fi 6 includes Target Wake Time, which can help with power management when it is supported by both the device and the network.


Check how the product behaves on different routers and access points. Network performance depends on the router's capacity, signal strength, interference and the type of traffic on the network. It is not simply a question of how many devices are connected.


Planning a connected product? Implantaire works across embedded hardware, firmware, wireless connectivity, applications and product engineering. Talk to our team about your product requirements and connectivity architecture.


Choosing the Right Connectivity for Your Product


Before selecting a protocol, it is better to understand the product requirements. Some of the main points to consider are:


  • Power budget: Define the expected battery life, battery capacity, charging approach, sleep behaviour and communication frequency.

  • Range and environment: Consider the building layout, walls, installation location, interference and whether the product needs to communicate through a mesh.

  • Data and response requirements: Estimate message size, update frequency, latency and whether the product needs audio or video streaming.

  • Network and ecosystem: Identify whether the product must work with an existing hub, a particular smart home platform, a phone or a cloud service.

  • Setup and support: Plan commissioning, recovery after a router or hub change, firmware updates and diagnostics.

  • Security and product lifetime: Define secure provisioning, identity and credentials, encrypted communication, update mechanisms and the expected security support period.

  • Target markets: Identify radio, electrical safety, cybersecurity and protocol certification requirements before design freeze.


What Approvals and Certifications Might Be Needed?


There is no common certification list for all smart home products. The requirements depend on the product, the radio technologies used and the countries where it will be sold. Radio approvals, electrical safety and protocol certifications are separate items and need to be checked individually.


Radio regulatory requirements


Products with radio transmitters may need to meet the applicable requirements in each target market. Examples include FCC equipment authorisation requirements in the United States, ISED requirements in Canada, and the Radio Equipment Directive (RED) in the European Union. In India, Wireless Planning and Coordination (WPC) Equipment Type Approval may apply to equipment operating in de-licensed frequency bands. The exact route and documentation depend on the device and its radio configuration.


CE is a conformity marking used for products covered by applicable EU legislation; it should not be described as a single standalone radio certification. Manufacturers must identify the legislation and conformity assessment route that applies to the product.


Electrical safety and product-specific standards


Electrical safety requirements depend on the product category, power source, installation and intended use. Standards such as IEC 62368-1, IEC 60730 and UL 916 apply to particular categories of equipment and should not be treated as universal requirements for all smart home devices. A product-specific compliance assessment is needed to identify the relevant standards and tests.


In India, BIS registration or certification is required only where the product falls within an applicable compulsory certification or registration scheme. It should be checked separately from WPC radio approval.


Protocol and ecosystem certification


Matter and Zigbee have product certification programmes, while Thread has its own certification programme for Thread components and products. Which certifications are required or appropriate depends on the product architecture, the claims the manufacturer intends to make and the target ecosystems. These programmes assess conformance to the relevant specifications; they are not substitutes for regulatory approvals such as radio conformity or electrical safety assessment. Platform-specific programmes may also apply when a manufacturer wants to use a particular ecosystem's compatibility badge or make claims beyond the relevant standard.


Cybersecurity requirements


Cybersecurity requirements are increasingly part of connected-product compliance. In the UK, the consumer connectable product security regime under the Product Security and Telecommunications Infrastructure (PSTI) framework came into force on 29 April 2024. For products within scope, requirements include avoiding universal default passwords, publishing a route for reporting security issues and specifying a minimum security update period.


In the EU, the cybersecurity requirements introduced through the Radio Equipment Directive's Delegated Regulation (EU) 2022/30 have applied to in-scope radio equipment since 1 August 2025. The European Commission has since adopted Delegated Regulation (EU) 2026/339 to repeal that delegated regulation, with the repeal scheduled to take effect on 11 December 2027, when the main obligations of the Cyber Resilience Act are also due to apply. Manufacturers should check the current legal position and product scope when planning market entry.


This is a general overview, not a complete compliance assessment. Requirements can change, so the applicable standards and approval route should be confirmed for the specific product and target market before starting certification testing or planning a launch.


Common Issues to Consider During Development


Testing only in a controlled environment


A device may work well on the development bench but behave differently in a customer's home. Router models, network settings, wireless interference, walls and phone operating systems can all affect the setup and operation. Testing should cover a reasonable range of routers, phones and network conditions.


Leaving the mobile application until late in development


The mobile application is often a major part of the customer's experience. Pairing, onboarding, permissions, account management, device status, error messages and recovery flows need to be considered alongside hardware and firmware development. Developing the app in parallel with the embedded system can expose interface and integration issues earlier.


Underestimating the power budget


Battery life is not decided by the radio alone. Firmware wake-up intervals, retries, signal strength, sensor readings, LEDs and the battery itself all affect the final result. Battery-life estimates should be based on realistic usage and checked through actual measurements.


Designing security as a later feature


Security should be considered from the beginning of the project, not added at the end. Depending on the product, this can include device identity, secure provisioning, encrypted communication, secure boot, signed firmware updates and a clear process for handling security issues and updates.


Using the same protocol does not guarantee compatibility


Using the same wireless protocol does not automatically mean that two products will work together. Compatibility also depends on the supported device types, application-level features, protocol versions, firmware and the ecosystem being used. The setup and commissioning process can also affect whether devices work together as expected. Any compatibility claim should be based on the specific combination of products and features that has actually been implemented and tested.


Connectivity needs to be tested as part of the complete product. The antenna, electronics, firmware, power management, app and cloud services all have a role in how the product performs.

Smart Home Product Development in Practice


At Implantaire, we look at wireless connectivity as part of the complete product. We choose the technology based on the application, operating environment, power requirements, range and how the product needs to connect with other systems.


Our work covers embedded hardware, firmware, wireless connectivity, application development and product integration. We can therefore look at the electronics, embedded software and application together, rather than treating each part as a separate activity.


You can see examples of our product design and engineering work in the Our Works section of our website. Not every product shown uses Matter, Thread or Zigbee or holds a protocol certification; each new product is assessed on its own requirements.


Have a smart home or connected product idea? Discuss your hardware, firmware, connectivity and application requirements with the Implantaire team. Get in touch.


By M Gopinaga Bharath, Technical Director at Implantaire



Frequently Asked Questions


What is smart home product development?

Smart home product development is the process of designing and engineering connected products for residential use. It can include electronics, embedded firmware, wireless connectivity, mobile applications, cloud services, security, testing and regulatory compliance.

Matter is an application-layer smart home connectivity standard developed by the Connectivity Standards Alliance. It runs over IP networks using Wi-Fi, Thread or Ethernet, and Bluetooth Low Energy is commonly used during commissioning, although Matter also supports other commissioning methods in compatible implementations. Compatibility depends on the device type, supported features and ecosystem implementation.

Both commonly use IEEE 802.15.4 radios and support low-power mesh networking. Zigbee uses its own networking and application framework, while Thread is an IPv6-based network protocol. Matter can use Thread as a network transport, but Thread and Matter are not the same thing.

Wi-Fi is often suitable when a product needs higher data throughput or direct connection to a home network, such as cameras and media devices. Power consumption, coverage, access point capacity and the product's operating pattern should be assessed before choosing it.

Bluetooth Low Energy can support nearby device control, provisioning, commissioning and communication with phones or accessories. It is useful for low-power and short-range use cases, but it is not a direct substitute for a Thread or Zigbee mesh network in every application.

Requirements depend on the product, radio technologies, electrical design and target markets. A product may need radio regulatory compliance, applicable electrical safety assessment, and optional or programme-specific Matter, Thread or Zigbee certification. Cybersecurity obligations may also apply in markets such as the EU and UK.



Technical References


The following official resources provide further information on the standards and regulatory frameworks discussed in this article. Requirements should be checked against the current version and the specific product being developed.




Related Reading



bottom of page