WiFi+RF Curtain Module RCRec Pin, CB2S BK7231N, Tuya MS-108WR

User question

qu'elle broche est connecté RCRec sur le module WIFI+RF curtain

Artificial Intelligence Response

Direct answer to the question

Short answer: I cannot verify a published, dedicated RCRec pin for the generic WiFi+RF curtain module from official manuals. The available manufacturer/user documentation for common models such as MS-108WR and QS-WIFI-C01-RF confirms that RF is built in, but it only exposes the external screw terminals L, N, S1, S2, L1, L2 and does not document the internal RF-receiver-to-MCU pin mapping. (device.report)

Most likely practical conclusion: on the commonly discussed HFY-CL02WF+RF Rev 2.0 / CB2S(BK7231N) version, there is no separate user-accessible RCRec GPIO on the Wi-Fi SoC; the RF remote behaves like the native button inputs instead. In that teardown, the exposed/configured pins were P6 relay, P7 relay, P10 Wi-Fi LED, and P23/P24/P26 as buttons, and the author/comment thread states the RF function is handled by “other hardware.” (elektroda.com)

If you want the exact pin for your board revision, I need one of these:

• a PCB photo, front and back,
• the exact model number,
• the Wi-Fi module marking, e.g. CB2S / WB3S / CB3S,
• or the silkscreen printed on the PCB.

---

Detailed problem analysis

Your question is electrically important because “WiFi+RF curtain module” is not a single standardized board. Several products share similar marketing names, but internally they differ in:

• RF band: 433 MHz on some modules,
• RF band: 2.4 GHz remote on others,
• Wi-Fi module type: BK7231N/CB2S, WB3S, etc.,
• control architecture: direct GPIO handling versus a secondary controller. (device.report)

What the official documentation actually shows

For the MS-108WR manual:

• RF is described as built-in RF433,
• compatibility is stated for RF433 remotes with 1527 encoding,
• but the manual only documents the external wiring and installation, not internal GPIO assignment. (device.report)

For the QS-WIFI-C01-RF product page:

• the device is specified as Wi-Fi 2.4 GHz + RF433,
• again, there is no published internal pinout for the RF receiver data line. (ifreeq.cn)

For another curtain module family, CM-SS(WT):

• the document explicitly states Tuya APP + RF 2.4 GHz + push switch,
• which proves that not all “WiFi+RF curtain” modules even use the same RF technology. (iskydance.com)

So, from an engineering standpoint, there is no defensible single answer like “RCRec = GPIO4” or “RCRec = P24” for all WiFi+RF curtain modules. That would be guesswork.

What can be inferred from an actual board teardown

One teardown of a WiFi + 433 MHz RF curtain module labeled HFY-CL02WF+RF Rev 2.0 identified:

• CB2S / BK7231N Wi-Fi module,
• GPIOs in use as:
  • P6 = Relay
  • P7 = Relay
  • P10 = Wi-Fi LED
  • P23/P24/P26 = buttons
• and the report/comments note that the RF remote works through the three button actions and that RF appears to be implemented by other hardware, not by a dedicated exposed Wi-Fi GPIO called RCRec. (elektroda.com)

That is the strongest practical clue available:
on at least this common RF curtain board, RCRec is not a separately exposed pin on the Wi-Fi module.

Important correction

One of the sample answers mixed your module with RPM7238. That is a different device family: ROHM RPM7238 is an IR receiver module, not a Wi-Fi+RF curtain switch module. So any conclusion derived from “RPM7238” is not applicable to your curtain controller. (alldatasheet.com)

---

Current information and trends

As of the currently accessible documentation and teardowns:

• consumer curtain modules sold as WiFi+RF often publish only installation terminals, not MCU-level schematics, so the internal RF data pin is usually undocumented publicly; (device.report)
• there are multiple hardware families under similar names, including 433 MHz RF variants and 2.4 GHz RF remote variants; (device.report)
• community reverse-engineering of at least one common BK7231N/CB2S RF-curtain module indicates the RF path behaves as local button logic rather than a separate configurable “RCRec” GPIO. (elektroda.com)

This means that, in practice, firmware mapping often focuses on:

• relay outputs,
• local button inputs,
• Wi-Fi LED, rather than a dedicated RF receive pin.

---

Supporting explanations and details

Think of the RF section in two possible architectures:

Architecture	What it means	Consequence for “RCRec”
Direct RF-to-Wi-Fi GPIO	RF receiver data output goes straight into the Wi-Fi SoC	A real RCRec pin exists and can be mapped
RF decoded by separate hardware	RF section acts like button logic or another local controller	No separate RCRec pin is exposed to the Wi-Fi SoC

For the teardown discussed above, the evidence fits the second case better. (elektroda.com)

If your goal is OpenBeken/Tasmota-style configuration, then for that specific board family the useful pins are the ones already identified:

• P23 / P24 / P26 for stop/up/down style button inputs,
• not a separate RCRec input. (elektroda.com)

---

Ethical and legal aspects

These modules switch mains voltage for curtain or shutter motors. The manuals explicitly state installation should be performed by a qualified electrician, and they warn against disassembly or modification during normal use. (device.report)

Safety implications:

• risk of electric shock,
• risk of damaging the motor direction interlock if outputs are mishandled,
• possible compliance issues if RF behavior or mains wiring is modified improperly. (device.report)

---

Practical guidelines

If you want the exact RCRec connection on your own module, this is the correct engineering method:

1. Identify the exact board

   • read the silkscreen,
   • read the Wi-Fi module marking,
   • identify whether it is 433 MHz or 2.4 GHz RF remote.

2. Locate the RF section

   • antenna trace or spring antenna,
   • RF receiver IC or daughterboard.

3. Trace continuity

   • with power disconnected,
   • continuity-test from RF receiver data output to:
     • Wi-Fi module pads,
     • button lines,
     • or any secondary MCU/logic IC.

4. Compare with known mappings

   • if your board matches HFY-CL02WF+RF Rev 2.0, start by checking whether RF lands on the same nets as P23/P24/P26 button inputs. (elektroda.com)

5. Do not assume from the product name alone

   • because MS-108WR-type and CM-SS(WT)-type products do not even share the same RF type. (device.report)

---

Possible disclaimers or additional notes

• I am not giving you a single GPIO number because the public documentation does not support one universal answer. (device.report)
• The strongest evidence I found suggests no separate RCRec pin is exposed on at least one common BK7231N curtain RF board. (elektroda.com)
• If your board is a different revision, that conclusion may not hold.

---

Suggestions for further research

To get a definitive answer, the next useful data would be:

• high-resolution PCB photos,
• exact model text on the PCB,
• chip/module marking,
• close-up of the RF daughterboard or antenna area,
• a continuity test result between RF section and P23/P24/P26.

If you send those, I can help you identify the pin precisely.

---

Brief summary

Best answer: for the generic WiFi+RF curtain module, the RCRec pin is not published in official documentation. On a known HFY-CL02WF+RF / CB2S(BK7231N) version, the RF remote appears to act through the button inputs P23/P24/P26, so there is likely no separate RCRec GPIO exposed on the Wi-Fi module. (device.report)

If you want, send me a photo of your PCB, and I will tell you which exact pin/nets correspond to RF receive.

Disclaimer: The responses provided by artificial intelligence (language model) may be inaccurate and misleading. Elektroda is not responsible for the accuracy, reliability, or completeness of the presented information. All responses should be verified by the user.