A smart home solution is the combination of connected devices, a local hub or controller, cloud services and user apps that lets a household monitor and automate lights, locks, climate, energy and security. In 2026 the defining choices are which radio and interoperability standards to support, how much runs locally versus in the cloud, and how you meet new security rules. Blockchain is rarely part of the answer.
This page covers the system design. The companion guide on smart home app development covers building the mobile app itself.
The layers of a smart home system
| Layer | Role | Typical technologies |
|---|---|---|
| Devices | Sensors and actuators: bulbs, plugs, locks, thermostats, meters | Microcontrollers with Thread, Zigbee, Z-Wave, Wi-Fi or BLE radios |
| Network and interoperability | How devices are discovered, commissioned and controlled | Matter over Thread or Wi-Fi; Zigbee and Z-Wave for existing ecosystems |
| Local controller | Runs automations, bridges protocols, keeps working offline | Hubs, Thread border routers, smart speakers or TVs acting as Matter controllers |
| Cloud | Remote access, account management, history, firmware updates, voice assistant links | MQTT brokers, device shadows, time-series storage, OTA pipelines |
| Apps and integrations | User control, onboarding, notifications, third-party ecosystems | iOS and Android apps, voice assistants, utility and insurer integrations |
Standards: Matter changed the defaults
Matter, published by the Connectivity Standards Alliance with its 1.0 release in 2022, gives devices a common application layer over IP so one device can work with Apple Home, Google Home, Amazon Alexa and SmartThings. It runs over Wi-Fi, Ethernet and Thread, a low-power IPv6 mesh. Its multi-admin feature lets a household control the same device from several ecosystems.
For a new device line, Matter support is now close to expected in mainstream categories such as lighting, plugs, locks, sensors and thermostats. Zigbee and Z-Wave remain relevant for existing installations and categories Matter covers less well. Certification costs and the Matter device-type list should be checked early, because unsupported device types force proprietary integrations.
Local-first versus cloud-first
Cloud-dependent products break when the company's servers or the home's internet go down, and several brands have stranded customers by shutting down services. Local-first designs run automations on the hub and use the cloud for remote access and backup. They are more resilient and better for privacy, at the cost of more complex firmware and update management. For locks, alarms and anything safety-related, local operation should be a requirement.
Security and regulation
Consumer IoT security is now regulated in several major markets. The UK's product security regime under the PSTI Act has applied since April 2024, banning universal default passwords and requiring a vulnerability disclosure policy and a stated support period. The EU's Cyber Resilience Act sets wider requirements that phase in over the next few years, and the baseline standard ETSI EN 303 645 is a practical design checklist. In the US, the FCC's voluntary Cyber Trust Mark labeling program launched in 2025. Practical implications:
- Unique per-device credentials and secure commissioning (Matter's device attestation helps here).
- Signed firmware with secure boot and a dependable over-the-air update pipeline.
- A published support period and a process for receiving and fixing vulnerability reports.
- Data minimization: occupancy, camera and energy data reveal a lot about a household.
Where blockchain fits, honestly
Most smart home functions are better served by a conventional database and well-secured cloud. A distributed ledger adds latency, cost and complexity, and household data must never be written to a public chain. The narrow cases where it can help involve several parties who need a shared record none of them controls:
- Energy: households with solar and batteries selling flexibility or surplus energy, where settlement involves aggregators and utilities. Even here, most live programs use conventional settlement; see IoT energy meter solutions.
- Shared access logs: short-term rentals or shared buildings where owner, manager and guest want a tamper-evident access history. Hash anchoring a signed log is usually enough.
- Device provenance: recording manufacturing, ownership transfer and warranty events across manufacturers, retailers and resellers.
The broader trade-offs are covered under blockchain IoT development, and device-security patterns under blockchain for cyber security.
Planning a smart home product
- Define the categories and ecosystems. Which device types, which assistants and platforms customers already use.
- Choose radios and chipsets. Matter-certified modules from major silicon vendors reduce firmware work.
- Design local and cloud responsibilities. What must work offline, what needs the cloud.
- Build the update and security pipeline early. Retrofitting OTA and secure boot is painful.
- Certify. Matter, radio and safety certifications take weeks to months; plan them into the schedule.
Frequently asked questions
Do I still need a hub with Matter?
Matter needs a controller, and Thread devices need a border router. Many households already have one inside a smart speaker, TV streamer or router, so a dedicated hub is optional for many setups.
Should a smart home product use blockchain?
Usually not. Use it only if several independent parties need a shared, tamper-evident record, such as energy settlement or device provenance, and even then consider simpler hash anchoring first.
Thread or Wi-Fi for battery devices?
Thread is designed for low-power mesh networking and suits battery sensors and locks. Wi-Fi suits mains-powered, higher-bandwidth devices like cameras.
What happens if the company behind a smart home system shuts down?
Cloud-only devices may stop working. Matter and local-control designs reduce that risk because devices can be controlled by other ecosystems and run automations without the vendor's servers.