Tuya Smart Switches with Integrated 433MHz RF Remote Control – Models, Brands, Forum Threads

User question

I want to find forum topics related to tuya smart switch/relay devices that integrates the ability to control their relays with 433mhz remotes

Artificial Intelligence Response

Direct answer to the question

• Below is a curated, up‑to‑date set of forum topics specifically about Tuya smart switches/relays that integrate a built‑in 433 MHz RF receiver so their relays can be driven from handheld RF remotes, alongside Wi‑Fi/Zigbee control.
• “Start here” index (many threads in one place):
  • Tuya smart switches with integrated 433 MHz RF – models, brands, and forum links (continuously updated). (elektroda.com)

Key threads (each includes device details, pairing steps, GPIO/pinouts, or firmware notes):

• Configuring RF on a Tuya 2‑channel CB3S (BK7231N) wall switch with RF433: learning/pairing and the reset button usage. (elektroda.com)
• TYWB/TYWD 4‑relay Tuya module with on‑board 433 MHz receiver (CB3S/BK7231N): RF data line, flashing hurdles, and working mappings after swapping to ESP/Tasmota. (elektroda.com)
• Tuya 4‑channel “garage door/relay” board (CB3S) that exposes RF parameters in logs (e.g., remote_io=20): notes on RF width and datapoints. (elektroda.com)
• Andeli 2‑gang Tuya wall switch with RF (CB2S/BK7231N): TuyaMCU baud rate, DPIDs, and why RF still works after flashing. (elektroda.com)
• LLXLJY 8‑channel Tuya relay with 433 MHz learning menu: OBK (OpenBeken) setup, DPIDs, and user‑reported RF pairing steps. (elektroda.com)
• Tuya Wi‑Fi + RF curtain controller modules (CB2S/CB3S): flashing, wiring, and the “RF just works” notes. (elektroda.com)
• Tuya “Universal IR+RF” remote (S11‑SH4‑CBU‑V2.4) teardown and firmware configuration (useful as an RF bridge within Tuya ecosystem). (elektroda.com)
• Appio/Lumenix 9605 Wi‑Fi/RF no‑neutral wall switch (TYWE3S/ESP8285) – Tasmota experience and RF capability. (elektroda.com)
• Home Assistant: pairing a Sonoff RM433 remote to a Tuya 4‑ch RF switch (interoperability boundaries of fixed‑code protocols). (community.home-assistant.io)
• Hubitat: Tuya Zigbee wall switch that also listens to a kinetic 433 MHz RF wall transmitter; state sync reported in the hub. (community.hubitat.com)
• Reddit: Tuya Wi‑Fi switch lost cloud pairing, continued to work via its separate 433 MHz remote (confirming the dual‑path design). (reddit.com)

Detailed problem analysis

• Architectural patterns you will see across these threads:
  • RF integrated at board level: a discrete 433 MHz ASK/OOK receiver (e.g., SYN590R/SYN470R class) feeds a “main MCU” (or TuyaMCU) that drives relays and LEDs. The Wi‑Fi module (ESP8266/TYWE3S of older units, BK7231N/T on CB2S/CB3S today) either reads the RF line directly or exchanges UART packets with the main MCU. (elektroda.com)
  • TuyaMCU devices: after flashing OpenBeken/Tasmota, relays still work via local buttons and RF because the TuyaMCU (separate small MCU) continues to handle those, while the Wi‑Fi module talks to it over UART (often 9600 bps). You map DPIDs to channels to expose relay states and timers to MQTT/HA. (elektroda.com)
  • Direct‑GPIO devices: some boards wire the RF DATA output straight into a Wi‑Fi SoC GPIO; community firmware must decode OOK timings on that pin (e.g., BK7231N P20 as “remote_io”). (elektroda.com)
• RF protocol reality in Tuya relays:
  • Most integrated RF is “fixed‑code” (EV1527/PT2262 families) – easy to learn/replay; rolling‑code (e.g., many garage doors) is generally unsupported. This is why a Sonoff RM433 may not pair with some Tuya RF relays: not all fixed‑code timings match. (community.home-assistant.io)
• Typical troubleshooting themes in the threads:
  • Identify the module and wiring: CB2S/CB3S (BK7231) vs TYWE3S (ESP8266). Extract boot logs or inspect board silkscreen. On 4‑ch boards, users consistently confirm RF on BK7231 P20 with Tuya logs showing “remote_io: 20”. (elektroda.com)
  • Flashing pitfalls: new Tuya devices often block tuya‑convert; UART flashing is the fallback. Some 4‑ch RF boards place capacitors on UART1 lines that must be removed to flash reliably. (elektroda.com)
  • Baud rates and DPIDs: for TuyaMCU variants, start at 9600 bps, then try 115200 bps; map DPIDs for relays, countdowns, backlight, etc., until “heartbeat_valid” goes 1. (elektroda.com)
  • Range optimizations: many threads discuss simple ANT lead routing (quarter‑wave ≈17 cm insulated wire) and enclosure effects; if range is still poor, an external bridge (IR+RF, Sonoff RF Bridge) can be used to receive RF and trigger Tuya entities over MQTT/automation. (elektroda.com)

Current information and trends

• Hardware trend: Tuya has broadly shifted from ESP8266 (TYWE3S) to Beken BK7231 (CB2S/CB3S). Community firmware (OpenBeken) now covers many BK7231 RF+Wi‑Fi devices, with active per‑model threads (e.g., CB3S 2‑gang, 4‑ch relays, curtain modules). (elektroda.com)
• Aggregated “what works” lists: the Elektroda index is being updated with new models and GPIO/DPID maps, making it a strong live entry point for RF+Tuya research. (elektroda.com)
• Ecosystem takeaway: if you need platform‑wide RF reception or want to integrate many RF sensors/remotes, users still deploy an RF bridge (e.g., Tuya IR+RF, Sonoff RF Bridge) and link to Home Assistant/Hubitat; but if you only need a few relays, integrated Tuya RF relay modules are simpler. (elektroda.com)

Supporting explanations and details

• Example: Tuya 4‑channel relay board (CB3S) log exposes “remote_io: 20” and RF timing (rf_width), confirming the RF‑to‑MCU path. This helps you bind the correct pin in community firmware or check TuyaMCU behavior. (elektroda.com)
• Example: On TYWB/TYWD 4‑ch RF boards, users report the SYN590R superhet RX and document working mappings after replacing CB3S with ESP/Tasmota (demonstrating protocol compatibility across firmwares where the RF is fixed‑code). (elektroda.com)
• Case: Andeli 2‑gang RF switch (CB2S) – after OpenBeken flash, relays and RF still function because the on‑board MCU handles them; you only restore MCU↔Wi‑Fi UART (TuyaMCU) and map DPIDs to expose features to MQTT/HA. (elektroda.com)

Ethical and legal aspects

• United States: 433.92 MHz devices typically operate under FCC Part 15.231 for intermittent control signals (e.g., remotes). Ensure gear is FCC‑certified for 433.92 MHz under Part 15.231; examples of authorized devices exist in the FCC database. (fccid.io)
• General guidance: 433 MHz is ISM/SRD in many regions (for EU, ETSI EN 300 220); in the U.S. it is allowed for specific low‑power, short‑duration uses under Part 15. Avoid rolling‑code cloning (security/legality) and respect device certification and interference rules. (en.wikipedia.org)
• Mains safety: opening/altering in‑wall relays carries shock and fire risk; maintain creepage/clearance and isolation. Follow local electrical codes.

Practical guidelines

• How to quickly find more relevant threads:
  • Site‑filtered queries that work well:
  • site:elektroda.com “CB3S” “RF433” | “TYWB 4ch-RF” | “TuyaMCU 433” (elektroda.com)
  • site:community.home-assistant.io Tuya 433 RF switch/relay (integration, pairing, templating) (community.home-assistant.io)
  • site:community.hubitat.com Tuya 433 RF relay | kinetic switch Tuya Zigbee + RF (community.hubitat.com)
• Vet the hardware before buying/modding:
  • Identify the radio/Wi‑Fi module: CB2S/CB3S=Beken; TYWE3S=ESP8266.
  • Look for “RF433” and “EV1527/PT2262” in listings/manuals; avoid devices that say “rolling code”.
  • Prefer boards documented in the index thread (above) to benefit from known GPIO/DPID maps. (elektroda.com)
• Sniff and verify RF codes:
  • Use rtl_433 (cheap RTL‑SDR) to confirm your remote’s code family and stability before integration; export to MQTT if desired. (github.com)
• Firmware paths:
  • TuyaMCU devices: keep RF via the Tuya sub‑MCU; map DPIDs in OpenBeken/Tasmota; set correct UART baud (often 9600). (elektroda.com)
  • Direct‑GPIO devices: enable RF receive component and point to the correct pin (e.g., BK7231N P20 on several 4‑ch boards). (elektroda.com)
  • If OTA fails, plan for UART flashing; on some 4‑ch boards, remove series caps on UART to program. (elektroda.com)

Possible disclaimers or additional notes

• Many newer Tuya units replaced ESP modules with BK7231, so legacy OTA methods (tuya‑convert) often no longer work; consult device‑specific notes. (templates.blakadder.com)
• RF bridges and RF‑integrated relays are complementary: bridges are flexible for many sensors; integrated relays are simpler for point control. (elektroda.com)

Suggestions for further research

• Track the Elektroda index for newly added models and wiring maps; post your board photos/boot logs there for help. (elektroda.com)
• For HA/Hubitat specifics (automations, state sync), search those communities for your exact model string plus “RF433” or the Tuya product code. (community.home-assistant.io)
• If you need broad RF intake, also research Portisch‑flashed Sonoff RF Bridge and Broadlink RM series as alternatives. (tasmota.github.io)

Brief summary

• The threads above focus on Tuya smart switches/relays that embed a 433 MHz receiver so relays can be controlled from an RF remote in addition to Wi‑Fi/Zigbee. They document exact models, chips (CB2S/CB3S/TYWE3S), RF pins (e.g., P20), DPIDs/baud for TuyaMCU devices, and practical flashing/pairing steps. Start with the live index, then dive into the specific model thread that matches your hardware to speed up a working RF+smart integration. (elektroda.com)

If you want, tell me your exact model (photos/label/PCB code), and I’ll pinpoint the best thread and the known RF pin/DPIDs for it.