Gateway Bridge Manufacturer — Protocol Bridge OEM/ODM
深圳星廖智能科技有限公司
深圳星廖智能科技有限公司
A gateway bridge, also called a smart home hub, translates between protocols such as Zigbee, Bluetooth Mesh and RF and your Wi-Fi network or the cloud, so devices using different radios appear in one app. Xingliao, a Shenzhen manufacturer founded in 2014 with 110 staff, builds gateways and bridges for OEM buyers, including Zigbee 3.0 and Matter controllers.
A bridge exists because the smart home never agreed on one protocol. Zigbee devices, 433 MHz RF fittings, infrared appliances and Matter fabrics all work perfectly and none of them talk to each other. A bridge does not make an old device smarter — it makes an old device reachable from the app your customer already has open.
XingLiao builds protocol bridges in Shenzhen: Zigbee to Wi-Fi, RF to app, IR to app, and Matter bridges that expose an existing non-Matter fleet to a Matter fabric. Sampling on existing platforms takes 7 to 15 days.
| Device | What it does | When you need it |
|---|---|---|
| Zigbee gateway | Connects a Zigbee mesh to the network and runs the mesh | Your end devices are Zigbee |
| Matter controller | Commissions Matter devices and border-routes Thread | You need one device to join Apple, Google and Amazon ecosystems |
| Multi-protocol hub | Runs more than one protocol in one box | You ship both Zigbee and Matter devices and want one SKU |
| Protocol bridge | Translates between protocols so devices appear in one app | Devices already exist and cannot be replaced |
The distinction matters commercially. A gateway is infrastructure for devices you sell. A bridge is a retrofit tool for devices somebody else sold — and that is a different customer, usually an installer or a building owner with an installed base rather than a consumer buying a starter kit.
RF to app. Enormous quantities of installed equipment — screens, curtain motors, cheap sockets, garage doors — run on 433 MHz with no app at all. A bridge with an RF receiver learns those remotes and gives them on/off and scene control. The end devices cannot report state, so the app knows what it sent and not whether it arrived. That limitation is acceptable for curtains and screens and unacceptable for security, and buyers should be told which is which.
IR to app. Same principle for infrared appliances: televisions, set-top boxes and above all air conditioners. This is the retrofit story in markets where replacing white goods is not realistic. See the IR controller range for the product built specifically for this job.
Non-Matter to Matter. A Matter bridge exposes existing Zigbee or Wi-Fi devices into a Matter fabric, so a customer with an installed base can add Apple Home or Google Home without replacing hardware. This is increasingly a procurement requirement in retrofit projects, and it is the strongest argument for building a bridge into your hub rather than selling it separately.
Being direct about the limits saves returns. A bridge gives you control, not capability. It cannot add state feedback to a device that has none, it cannot make a one-way RF socket report whether it is on, and it cannot turn a dumb appliance into a sensor. If the underlying device has no feedback channel, the app will show what was commanded rather than what happened.
There is also a latency and reliability cost. Every translation hop is one more thing that can fail, and support calls about a bridged device require knowing which of three layers broke. We recommend bridges for retrofit and renovation, and native devices for new installations — a rule that keeps the support burden proportionate.
Standard bridge platforms with your branding start at 500 pieces per colour. Firmware work — code library additions, custom scene logic, installer bulk provisioning — begins around 3,000 to 5,000 pieces, with new tooling at 25 to 40 days.
Bridge firmware is the most support-sensitive category in the range, because a single unrecognised remote or appliance model produces a support ticket. We maintain the code library through over-the-air updates and support per-client branches so one client's additions never leak into another's build.
Bridges are almost always sold alongside automation systems, curtain motors and scene switches.
Bridges carry the radio approvals of every protocol they transmit: CE and RoHS for Europe, UKCA for Great Britain, FCC for the United States, PSE for Japan. 433 MHz operation is licence-exempt in some markets and restricted in others, and Matter bridges require CSA certification with a registered vendor ID — both need to be settled at platform selection rather than at tooling sign-off.
A gateway for Zigbee devices you sell. A bridge for devices that already exist and cannot be replaced. Many project installations end up needing both.
Yes, for fixed and rolling code 433 MHz. The app can command them but cannot confirm state, because the curtains have no feedback channel.
Yes, through a Matter bridge that exposes non-Matter devices to a Matter fabric. That is the standard retrofit route.
No. It makes them reachable. Control and scheduling, yes; new sensing or feedback, no.
For RF and IR, one per area that needs line of sight or RF coverage — IR cannot pass through walls. For protocol bridging, one is normally enough.
500 pieces per colour on an existing platform; custom firmware or tooling from about 3,000 to 5,000 pieces.
Yes, via over-the-air firmware updates, with per-client branches for private-label additions.
Local scenes run on the hub, so bridged devices keep responding to schedules and sensors during an internet outage.
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.