A smart home gateway (hub) is the device that bridges low-power protocols such as Zigbee and Thread to Wi-Fi and the cloud. Whether you need one depends on your product mix: if your line includes battery sensors or Zigbee switches, you need a gateway; if everything is Wi-Fi, you do not. Getting this decision wrong either inflates your bill of materials or leaves customers with devices they cannot commission.

This guide covers when a gateway is required, what to specify, and the questions buyers should ask before committing to a platform.

Smart Home Gateway OEM: When You Need a Hub and What to Specify

When you actually need a hub

You need one if any device in the line uses Zigbee, Thread, Z-Wave or another non-Wi-Fi radio, because those devices cannot reach the router directly.
You need one if you want local automations that keep running when the internet drops.
You do not need one if every device is Wi-Fi — a Wi-Fi-only line can be commissioned straight from the app.

The mistake buyers make is shipping a Zigbee sensor range without a matching hub. The customer buys a sensor, cannot pair it, and returns the whole order.

What to specify on a gateway

Radios

Zigbee 3.0 – the most widely deployed for sensors and switches. Confirm the stack version and device class support.
Thread – required for many Matter-over-Thread devices. Ask whether the gateway acts as a Thread border router, and say so in the documentation.
Wi-Fi and Ethernet – Ethernet is preferred for stable installations; Wi-Fi-only gateways are cheaper but less reliable.
Bluetooth – often used for commissioning; useful but not essential.

Capacity and reliability

Maximum number of paired child devices, and the realistic number before performance drops.
Whether mains-powered devices act as mesh repeaters, and how many hops the network supports.
Behaviour after a power cut: does the gateway recover its configuration and re-pair automatically?
Local automation engine — which rules run on-device rather than in the cloud.

Commissioning experience

The pairing flow is where customer frustration starts. Specify QR or code-based provisioning, clear in-app error states (“device not found” is not an error message), and a documented reset procedure.

Platform choice: Tuya, Matter, or your own cloud

Tuya-based gateway – fastest to market, works with the large Tuya device ecosystem, white-label app available. Trade-off is cloud dependency.
Matter controller – interoperable with Apple Home, Google Home, Amazon and SmartThings. Requires Matter certification for the controller role and careful documentation of what it can and cannot do.
Own cloud and app – maximum control and no per-device fees, but you own the development and maintenance.

Most real product lines combine them: a Tuya or Matter-certified gateway for mainstream markets, with your own cloud for specific enterprise projects.

Certification for gateways

A gateway is a radio device and usually a mains-powered IT device, so it needs both tracks:

US – FCC (Wi-Fi, Zigbee, Thread radios), plus UL or ETL for safety.
EU – CE under the Radio Equipment Directive, EMC, plus RoHS and REACH.
UK – UKCA.
China domestic – CCC where applicable, with SRRC radio approval.
Japan – PSE and MIC.

We support CE, FCC, RoHS, UKCA, CCC and PSE depending on the destination market. Plan certification in parallel with tooling, because lab scheduling is usually the critical path.

MOQ and timeline

Standard gateway platform with your branding – MOQ from 500 pcs per colour.
Custom housing or new tooling – typically 3,000–5,000 pcs.
Prototyping – 7–15 days; tooling – 25–40 days after design freeze.

Questions to ask a gateway supplier

Does this gateway act as a Thread border router, and is that documented for end users?
How many child devices are supported in practice, not on the spec sheet?
Which automations run locally if the internet goes down?
What is the recovery behaviour after a power failure?
Who owns the cloud account, and what are the per-device costs at my volume?

Gateway and hub programmes at Xingliao

Xingliao Technology develops smart home gateways alongside smart switches, video doorbells, pet feeders and sensors, with OEM and ODM service across 172 production-ready platforms and 16 product categories. Send your device list and target markets, and we will tell you honestly whether your line needs a gateway at all.

Send your product list for a platform review

Related sourcing guides

Frequently Asked Questions

Do I need a hub if all my devices are Wi-Fi?

No. Wi-Fi devices connect to the router directly and can be commissioned from the app. A hub becomes necessary when your line includes Zigbee, Thread or other low-power mesh devices.

What is a Thread border router?

A device that connects a Thread mesh network to your Wi-Fi or Ethernet network and to the internet. Many Matter-over-Thread devices cannot be controlled remotely without one, so if you sell Thread devices you must document whether a border router is included or required separately.

Can one gateway support both Zigbee and Matter?

Yes, many gateways run Zigbee 3.0 and act as a Matter controller or Thread border router. Confirm which roles are actually implemented and certified rather than assumed, because the roles have separate requirements.

What MOQ applies to a custom gateway?

On our lines, a standard gateway platform with your branding starts from 500 pcs per colour. A custom housing with new tooling typically requires 3,000–5,000 pcs. Prototyping takes 7–15 days and tooling 25–40 days.

What happens to automations when the internet drops?

It depends on where the automation engine runs. Ask specifically which rules execute on the gateway itself. Well-specified gateways keep local schedules, sensor triggers and scenes running during an outage; cloud-only automations stop.

📌 This article is part of our Complete Smart Hub — more guides and buying tips inside.

szxl

Tech writer at XingLiao, testing and reviewing smart devices so you can buy with confidence.

查看全部文章 →