Zigbee Gateway Manufacturer — Smart Home Hub OEM/ODM
深圳星廖智能科技有限公司
深圳星廖智能科技有限公司
A Zigbee gateway coordinates a Zigbee mesh network, pairing sensors, switches and locks, and connects that mesh to IP so it can be controlled remotely. Xingliao, a Shenzhen manufacturer founded in 2014 with 110 staff, builds Zigbee 3.0 gateways and hubs for OEM buyers, with device and app co-development.
A Zigbee gateway is the box that lets battery-powered sensors and switches talk to a phone. Without it, a Zigbee device is an isolated island: it can join a mesh, but nothing outside that mesh can reach it. This is the single most misunderstood product in the smart home range, because buyers price it as an accessory when it is actually the reliability centre of the whole installation.
XingLiao builds Zigbee 3.0 gateways, Matter controllers and protocol bridges in Shenzhen for brands and project contractors. We manufacture on proven platforms with 7 to 15 day sampling, and we supply gateways matched to our own switches, sensors and locks so the mesh behaves predictably from day one.
| Parameter | Standard build | Why it matters |
|---|---|---|
| Protocol | Zigbee 3.0, with Thread and Matter support on selected platforms | Zigbee 3.0 is the safe default; Matter matters if you sell into Apple or Google ecosystems |
| Device capacity | 32 to 128 end devices depending on platform | Under-specify this and the mesh saturates mid-project |
| Uplink | Wi-Fi 2.4 GHz, or Ethernet on selected models | Ethernet removes a whole class of support calls |
| Local automation | Rules run on the hub, not the cloud | This is what keeps scenes working when the internet drops |
| Mesh type | Zigbee mesh with mains devices acting as routers | Battery sensors do not route; mains switches do |
| Power | USB-C or mains adapter, with optional battery backup | Battery backup keeps alarm scenes alive during outages |
| App | Tuya, or white-label app with your branding | The app is the product as far as the end user is concerned |
| Bridging | Zigbee to Wi-Fi to cloud, with scene mirroring | Needed when a customer mixes Zigbee devices with Wi-Fi devices |
The honest answer: a hub is required whenever the end device is Zigbee, and it is optional whenever the end device is Wi-Fi. Everything else follows from that.
If you are selling a starter kit of two sensors, a hub is an unwelcome extra cost and an extra thing to explain. Wi-Fi sensors win there. If you are selling a whole-home system with fifteen sensors, four switches and two locks, a hub makes the installation cheaper, more reliable and far easier to support — because every device reports to one address, and because the mesh extends coverage into rooms where Wi-Fi is weak.
There is a middle case worth planning for. Many customers start with Wi-Fi devices and later add Zigbee ones. Because both run under the same app account, that migration works without replacing anything — which is exactly why we keep both families on the same platform rather than treating them as separate product lines.
Zigbee and Wi-Fi both live in the 2.4 GHz band, and a poorly chosen Zigbee channel sits directly on top of a busy Wi-Fi channel. The symptom is not a clean failure; it is a mesh that works most of the time and drops sensors occasionally, which is much harder to support. We ship gateways with sensible default channel selection and document the Wi-Fi channels to avoid in the manual.
Physical placement matters just as much. A gateway inside a metal cabinet, behind a television, or on the floor next to a router will underperform. We specify placement guidance in the quick-start card rather than burying it in a PDF, because this is the cheapest support problem to prevent.
Finally, capacity. A platform rated for 64 end devices will behave badly at 70, long before it refuses to pair number 71. If your project has a defined device count, tell us and we will size the platform.
This is the feature that separates a serious hub from a cheap one. Cloud automation means the hub detects motion, sends it to a server, the server decides, and the server tells the light to turn on. Cut the internet and nothing works. Local automation means the rule lives on the hub: motion detected, light on, no round trip.
For alarm and security scenes, local execution is not a nice-to-have. A door sensor that cannot trigger a siren during an internet outage is a security product that fails precisely when it is needed. We build local scene execution as standard and make sure the pairing flow keeps working with the WAN unplugged, because that is the failure mode customers actually hit.
Standard gateways with your logo, housing colour, packaging and manual start at 500 pieces per colour. Firmware changes — your app name, custom scene logic, provisioning behaviour for installers — start around 3,000 to 5,000 pieces, with new tooling at 25 to 40 days.
One thing to budget for: gateway firmware takes longer to stabilise than simple devices, because the failure modes are network-level. We recommend a pilot batch and a firmware freeze before mass production.
Gateways are almost always developed alongside door and window sensors, motion sensors, Tuya smart switches and Matter controllers.
Gateways are always-on radio devices, so they carry radio, EMC and safety requirements in every market: CE and RoHS for Europe, UKCA for Great Britain, FCC for the United States, PSE for Japan. Products sold as Matter controllers additionally need CSA certification and a registered vendor ID, which is a process with its own timeline — raise it at enquiry stage rather than at tooling sign-off.
No. Wi-Fi devices connect to the router directly. You need a gateway when your end devices are Zigbee or when you want local automation that survives an internet outage.
Between 32 and 128 depending on platform. Tell us your per-unit device count and we will size it with headroom rather than at the limit.
Yes for local scenes — the rules run on the hub. Remote access from outside the home obviously requires a connection.
Today, Zigbee 3.0 has the larger device ecosystem and lower cost. Matter is the interoperability standard that lets one device join Apple, Google and Amazon ecosystems. A Matter controller with Thread is the forward-looking choice for new platforms.
500 pieces per colour on an existing platform. Custom firmware or tooling from about 3,000 to 5,000 pieces.
Yes. We support bulk provisioning workflows so an installer can commission dozens of units without scanning each one.
Yes. Matching sensors, switches and locks are the reason to buy gateway and end devices from one factory — the mesh is validated as a system.
Download the full 2026 product catalog
125 pages · 10 categories · sensors, video doorbells, cameras, smart switches, control panels, locks, gateways and home appliances — with model numbers, specifications and OEM/ODM terms.