Concept prototype — protocol matrix is indicative. Compatibility always depends on exact SKU and firmware. No universal claims.
Ecosystems · buyer decision aid

Wi‑Fi, Zigbee, Matter, voice — pick what your market installs

Full coverage appears as RFQ options. Compatibility always depends on the exact SKU, module revision and firmware — never claim universal support on a trading catalogue.

Why this page exists

Wrong protocol choice becomes after-sales, not a feature list

Importers and integrators need a decision frame: hub tolerance, device density, app brand lock-in and certification path. This page is education for RFQs, not a promise that every factory SKU supports every stack.

Wi‑Fi wall switches

Hub-free path for residential distributors and short-let packs. App ecosystems such as Tuya / Smart Life are common in OEM supply. Voice via Alexa / Google Home as supported by the cloud stack.

No gateway SKU2.4 GHz only typicalSample: PL-SW-T3-WIFI-86

Zigbee + gateway

Better for multi-device rooms, hotels and sensor-heavy packs when a hub is acceptable. Mesh reliability narrative for larger installs; pairing discipline required for installers.

Hub requiredSensors scale betterSample GW: PL-GW-ZB-MTR

Matter-ready path

Position as a buyer checklist item: bridge vs native endpoint, certification status, multi-admin. Confirm factory capability in writing before promising Matter on any RFQ line.

Bridge or nativeRevision-sensitiveDo not over-claim

Z-Wave & project bus

Available through partner factories on request. List in RFQ rather than homepage promises. Wired RS485 / KNX-class paths belong to SI projects — declare early.

On requestMarket-specificSI-led
Comparison matrix

Indicative trade-offs for wall control RFQs

DimensionWi‑FiZigbeeMatter path
GatewayUsually noneRequired (sample PL-GW-ZB-MTR)Bridge and/or native endpoint — confirm
Best densityFew devices / apartment packsMulti-device rooms, hotels, sensorsRoadmap-driven multi-admin buyers
Radio load on home routerEach device on 2.4 GHz SSIDLower on router; mesh on Zigbee channelDepends on transport (Wi‑Fi / Thread)
Voice pathCloud skill via app stackVia hub / cloud bridgeMulti-admin promise — verify revision
After-sales riskSSID coverage, cloud outagesPairing, hub placement, channel planOver-claiming unsupported firmware
OEM app private labelCommon at higher MOQCommon with hub brand constraintsFactory-specific — ask early
Sample SKU narrativePL-SW-T3-WIFI-86PL-SW-R2-ZB-EU + gatewayGateway Matter narrative only until confirmed

Deep dive article: Wi‑Fi vs Zigbee wall switches.

Scenario guide

Which lean fits which package

ScenarioLean Wi‑FiLean ZigbeeNotes
Apartment resale packs, few devicesYesOptionalHub friction kills conversion
Hotel / multi-sensor roomOnly if proven Wi‑Fi designOften betterSee hotel kit
Buyer refuses hubsDefaultHard sellDocument cloud dependency
Office meeting-room scenesPossibleOften preferredIT policy may reject consumer apps
Short-let / Airbnb opsDefaultRareRemote access + simple pairing
Future Matter roadmapConfirm module revisionConfirm bridge/endpointNever promise without factory letter
Voice & app ecosystems

What buyers should write in the RFQ

Tuya / Smart Life class

Most common OEM path for Wi‑Fi glass switches. State whether retail app branding is acceptable or private-label app is required (higher MOQ).

Alexa / Google Home

Usually via the same cloud account stack — not a separate radio. Confirm skill enablement language packs for target markets.

Private cloud / local only

Hotel SI and enterprise buyers may forbid consumer clouds. Flag this before quoting Tuya-class modules; may need wired or local-gateway paths.

Matter boundary: Classic Tuya Wi‑Fi modules are not automatically Matter devices. Treat Matter as a separate line item with factory confirmation of revision, certification and multi-admin behaviour.
RFQ checklist — protocol block

Fields that prevent wrong module selection

Must answer

  • Preferred radio: Wi‑Fi / Zigbee / Z-Wave / Matter path / wired
  • Gateway allowed? Per room / floor / building / none
  • App brand: Tuya / Smart Life / private label / other
  • Voice required: Alexa / Google / none
  • Device count per room and per floor (density)

Should attach

  • Existing hub brand if retrofit
  • IT policy constraints (no consumer cloud)
  • SSID plan or site survey notes for pure Wi‑Fi hotels
  • Matter requirement as contractual clause or nice-to-have
  • Pairing responsibility: factory guide vs SI SOP
Specify protocol in RFQ Sample Wi‑Fi SKU Packages by scenario Comparison article
FAQ

Protocol questions we see on first RFQs

Can one RFQ mix Wi‑Fi switches and Zigbee sensors?

Yes, but support cost rises. Prefer one ecosystem per phase. If mixed, quote gateways and pairing guides explicitly and train installers on both paths.

Does Wi‑Fi mean 5 GHz works?

Typical Tuya-class wall modules are 2.4 GHz only. Do not promise 5 GHz. Site surveys should check 2.4 GHz coverage at each back box.

Is Matter the same as Zigbee?

No. Matter is an application layer with multiple transports. A Zigbee device is not automatically Matter-certified. Ask for the exact certification status per SKU.

Will private-label app change the radio?

Usually not — private label is cloud/branding. Radio module and cert path stay with the hardware revision. MOQ and NRE differ.

Where do certs intersect with protocols?

RF products (Wi‑Fi / Zigbee) often need market RF marks (e.g. FCC narrative for North America). See Certifications.

Related

Keep reading before locking the RFQ