YHOPE · SMART SWITCH PANELS

A protocol mismatch is paid for twice: once in panels and gateways that no longer fit the client's platform, and again in pulled wall boxes and rebuilt scenes. The decision belongs at purchase-order stage, and it has three inputs — the platform the client mandates, who maintains the building afterwards, and whether the site has control wiring. This page gives a scenario-first decision order, a qualitative comparison of the five routes, and the YHOPE series that map to each.

Choose by scenario first

The table is not a ranking. It says one thing: the primary protocol has to align with the client's platform and with the party who maintains the building afterwards — ask the maintenance question before quoting, especially on bulk work.

The five protocols, compared

Investment sensitivity is described in qualitative terms only — no product commercial terms appear in any of this material.

Wiring is not the enemy: when RS485 and KNX are the right answer

Wireless is not correct for every project. In large residences, public buildings and premium commercial work, wiring certainty and long-term serviceability outrank commissioning speed. YHOPE runs wired 485, low-voltage 485 and several wireless options in parallel. For KNX, the range includes 17 KNX modules (8/28-gang 10A, 4/8/12/20-gang 16A, 4/8/12-gang 20A, 0-10V dimming at 4/6-gang, 1-10V dimming at 4-gang, a 960mA power supply, the DTMO super gateway, an 8-gang universal interface at 12V, and a USB downloader). The KNX fusion gateway LG1 places a KNX bus and ZigBee / BLE on one device with 200 channels, 30+ device types and ETS5.7+ configuration: the KNX side keeps engineering-grade certainty while the wireless side keeps room for later additions and mobile control. For third-party BMS or room-host integration, RS485 panels and the RCU host carry addressed panel traffic, and the Zhonghong B27 AC gateway (RS485 + UART) covers VRF and ducted units from more than nine brands across a -20°C to 65°C range.

Does it still work offline?

The question every integrator hears is "will it still work if the internet goes down". Two verifiable answers: Bluetooth Mesh is decentralised — Bluetooth products can be added to a gateway first, local scenes pushed down to the devices, and then run without the gateway; and the flagship HarmonyOS panel is positioned as "local control without the network, no dropouts, no failures". Put both into the technical requirement and verify by pulling the network during sampling, rather than accepting a verbal assurance.

Shared baseline across the range

Whichever protocol you choose, the platform behind it is specified the same way: 40–400V wide voltage, 4kV surge resistance, V0 flame-retardant housing (Bayer PC, UL94 V0), 5-year warranty, multi-ecosystem support (HarmonyOS / Mi Home / Tuya / Matter, with Apple, Google and Amazon voice), and laser engraving down to 0.3mm for branding and labelling.

Selection checklist

• ☐ Confirm the client-mandated platform (HarmonyOS / Mi Home / Tuya / Matter / Apple / Google / Amazon)
• ☐ Decide whether a gateway and repeater plan are needed from the real device count
• ☐ Keep panel and gateway on one primary protocol chain — avoid mixed chains
• ☐ Evaluate wired 485 / KNX for large residences and public buildings, not only wireless
• ☐ Where a no-neutral switch is used, confirm the load is not a motor or high-voltage lamp
• ☐ For KNX, confirm channel budget (LG1: 200 channels, 30+ device types) and tool version (ETS5.7+)
• ☐ For bulk projects, confirm dual-protocol support (Zigbee / Wi-Fi) and RCU host integration
• ☐ Confirm the 5-year warranty plus firmware-update and spare-part paths
• ☐ Demand an offline local-control demo: pull the network on site

FAQ

Zigbee or Wi-Fi switches for an ordinary home?

With few devices and no wish for a gateway, Wi-Fi & BLE commissions faster. With many rooms and a growing device count, a Zigbee mesh is generally steadier. Decide from total device count and expansion plans.

Is Matter worth adopting now?

If the client explicitly needs cross-brand, cross-ecosystem interop, Matter is the most direct route today. If a project uses a single ecosystem, mature Zigbee or Wi-Fi schemes meet the requirement without adopting a standard for its own sake.

When should wireless be abandoned for RS485 or KNX?

When the project is large, reliability is the priority, and a professional maintenance party takes over afterwards. KNX delivers engineering-grade certainty, and the KNX fusion gateway LG1 connects a KNX bus with ZigBee/BLE (200 channels, 30+ device types), so wireless expansion stays available on top of a deterministic backbone.

Can several protocols coexist in one project?

Yes — that is the practical form of multi-ecosystem support. A hotel RCU can run a Zigbee/Wi-Fi dual protocol while connecting to a Tuya hotel SaaS platform and to Xiaodu, Tmall Genie, Alexa and Google voice entry points. Before mixing, confirm the gateway performs protocol conversion and agree who commissions it.

Does the network going down stop local control?

It depends on the scheme. Bluetooth Mesh is decentralised and lets local scenes be pushed down to devices for gateway-free running, and the flagship HarmonyOS panel is positioned as local control without the network. Verify by pulling the network during sampling rather than reading a datasheet.

Get in touch