BK7231N Tuya Switch by Aubess: Features & Customization

User question

BK7231n tuya switch aubess

Artificial Intelligence Response

Direct answer to the question

If you mean an Aubess/Tuya smart switch built around the BK7231N, then yes: it is a Beken-based Tuya device, usually using a CB2S or CB3S module, and it can usually be converted from Tuya cloud firmware to either OpenBeken or ESPHome via LibreTiny. Standard ESP8266/Tasmota binaries are not the right firmware for this chip family. (docs.libretiny.eu)

Key points

• BK7231N is a 120 MHz Wi‑Fi + BLE SoC commonly used in Tuya devices. (docs.libretiny.eu)
• Common Aubess variants use CB2S or CB3S, but hardware revisions vary, and some Aubess units are documented with a custom BK7231N PCB rather than a removable Tuya module. (docs.libretiny.eu)
• The two main open firmware paths are:
  • OpenBeken for easy local control/MQTT/Home Assistant. (github.com)
  • ESPHome + LibreTiny if you want native ESPHome workflows. (esphome.io)
• Flashing is typically done by 3.3 V UART on RX1/TX1, or by Tuya-CloudCutter OTA only if the device/profile is supported. (docs.libretiny.eu)

---

Detailed problem analysis

Because your query is very short, the most useful interpretation is: you want to identify, flash, or configure an Aubess Tuya switch that contains BK7231N. In practice, that means three separate engineering questions:

1. What hardware is inside?
2. How can it be flashed safely?
3. What GPIO map is needed after flashing? (docs.libretiny.eu)

1) Hardware platform

For Tuya-based Aubess switches, BK7231N-based modules are commonly:

• CB2S
• CB3S (docs.libretiny.eu)

Typical BK7231N/CB2S characteristics are:

• 120 MHz
• 2 MiB flash
• 256 KiB RAM
• 3.0–3.6 V supply
• 802.11 b/g/n Wi‑Fi
• BLE 5.1 (docs.libretiny.eu)

That matters because the flashing method, board selection, and GPIO names all depend on whether the board is treated as:

• cb2s
• cb3s
• or a more generic generic-bk7231n-qfn32-tuya target in ESPHome/LibreTiny. (esphome.io)

2) Firmware options

For BK7231N Aubess switches, the two practical firmware ecosystems are:

• OpenBeken / OpenBK7231T_App
  Good when you want a lightweight local web UI, MQTT, and Home Assistant integration. The project explicitly supports BK7231N and maintains a large device/template list. (github.com)

• ESPHome with LibreTiny
  Good when you already use ESPHome heavily and want YAML-based configuration. ESPHome’s LibreTiny platform explicitly supports BK7231N, including generic and module-specific boards. (esphome.io)

3) Flashing interface

For both CB2S and CB3S, the documented UART flash pins are:

• P10 / RX1
• P11 / TX1
• CEN to GND for reset/bootloader entry during flashing. (docs.libretiny.eu)

The common practical sequence is:

• connect a 3.3 V USB-UART adapter
• cross TX/RX
• start the flasher
• briefly ground CEN or repower the module when the tool waits for the bootloader. (github.com)

4) Why GPIO mapping is the hard part

With Aubess/Tuya hardware, the biggest obstacle is often not flashing, but getting the correct pin assignment for:

• relay
• button
• status LED
• external wall switch input
• energy metering UART or metering IC. (docs.libretiny.eu)

A known example is the Aubess 16 A mini switch with energy monitoring, where one published OpenBeken template shows:

• P8 = LED
• P23 = button
• P24 = toggle/switch input
• P26 = relay
• plus startup command for BL0942 energy metering. (openbekeniot.github.io)

Another Aubess ESPHome device page shows a different GPIO set for a mini switch, which confirms that revisions differ and you should not assume one Aubess template fits all units. (devices.esphome.io)

---

Current information and trends

As of March 23, 2026, the OpenBeken project’s GitHub release feed shows version 1.18.279, and the project advertises a device/template list with 800+ entries, indicating that BK7231N support is active and still developing. (github.com)

ESPHome’s current documentation still lists LibreTiny as the supported path for BK7231N/BK72xx, and still recommends choosing the correct board or falling back to generic-bk7231n-qfn32-tuya when uncertain. (esphome.io)

For OTA conversion, Tuya-CloudCutter remains relevant for BK7231N/BK7231T, but the LibreTiny guide explicitly warns that the guide can be outdated and that a device without a matching profile may not work. In other words, for many new or unusual Aubess revisions, UART remains the most reliable method. (docs.libretiny.eu)

---

Supporting explanations and details

Typical engineering decision tree

If your Aubess switch is still on Tuya firmware:

• Keep Tuya firmware

  • easiest
  • cloud-dependent
  • limited local autonomy. (solution.tuya.com)

• Flash OpenBeken

  • easiest community path for BK7231N
  • good for MQTT and local web control
  • strong template ecosystem. (github.com)

• Flash ESPHome via LibreTiny

  • best if your infrastructure is already ESPHome/Home Assistant centric
  • requires correct board and GPIO configuration
  • OTA via CloudCutter only if profile support exists. (esphome.io)

Why some flash attempts fail

Most common causes:

• wrong TX/RX cross-connection
• weak 3.3 V source
• not resetting via CEN at the correct moment
• assuming the wrong GPIO template after a successful flash. (github.com)

A useful feature of BK7231GUIFlashTool is that it can create a full backup and use that dump to extract the original GPIO configuration, which is often the fastest way to recover the right pin map for an unknown Tuya switch. (github.com)

---

Ethical and legal aspects

• This is a mains-powered switch, so there is a genuine shock and fire risk during disassembly, probing, and reflashing. The flashing tools and guides explicitly warn not to hack these devices while connected to mains power. (github.com)
• Modifying firmware can void warranty and may affect conformity with local electrical regulations or product certification in your jurisdiction. This is an engineering inference based on the fact that you are altering a mains control product beyond its certified shipped configuration. (github.com)
• Firmware backups may contain sensitive information: the flasher documentation warns that a flash dump can include your SSID and Wi‑Fi password if the device had already been paired. Handle dumps as secrets. (github.com)

---

Practical guidelines

Best practical path for your Aubess BK7231N switch

1. Open the device only when fully disconnected from AC mains. (github.com)
2. Identify whether it has:
   • a CB2S
   • a CB3S
   • or a custom BK7231N PCB. (docs.libretiny.eu)
3. If you want the most reliable result, use UART flashing.
   For CB2S/CB3S, use P10 RX1, P11 TX1, CEN reset, 3.3 V, GND. (docs.libretiny.eu)
4. Use a tool such as BK7231GUIFlashTool to:
   • make a full backup first
   • extract the Tuya config/GPIO information
   • then flash new firmware. (github.com)
5. If you prefer ESPHome, start with:
   • board: cb2s
   • board: cb3s
   • or board: generic-bk7231n-qfn32-tuya if uncertain. (esphome.io)
6. If the switch has power monitoring, check whether the metering IC is BL0942 and configure it accordingly after flashing. (openbekeniot.github.io)

Best practices

• Always backup before writing. (github.com)
• Treat Aubess GPIO maps as revision-specific, not universal. (openbekeniot.github.io)
• Prefer local control firmware only if you are comfortable verifying relay behavior, boot state, and wall-switch logic after reprogramming. This is an engineering best-practice inference supported by the variability in published pin maps. (openbekeniot.github.io)

---

Possible disclaimers or additional notes

I cannot give you an exact pin map from the phrase “BK7231N Tuya switch Aubess” alone, because Aubess has multiple switch revisions with different layouts and sometimes different module types. Published templates for Aubess mini switches do not all match each other. (openbekeniot.github.io)

So the technically correct answer is:

• Yes, it is a supported BK7231N Tuya platform.
• Yes, it is usually flashable.
• No, the exact GPIO assignment cannot be assumed without the model or PCB photo. (github.com)

---

Suggestions for further research

To get you the exact working configuration, send:

• a clear photo of the PCB front and back
• the marking on the Wi‑Fi module: CB2S / CB3S / custom
• whether you want:
  • OpenBeken
  • ESPHome
  • or just Tuya troubleshooting
• whether the device has power monitoring. (openbekeniot.github.io)

If you want, I can next provide either:

1. a step-by-step flashing guide for BK7231N Aubess, or
2. an ESPHome/OpenBeken template once you upload a board photo.

---

Brief summary

An Aubess Tuya switch with BK7231N is a Beken-based smart switch, commonly built around CB2S or CB3S, and it is generally a good candidate for OpenBeken or ESPHome via LibreTiny. UART flashing uses RX1/TX1 on P10/P11 with 3.3 V only, and the main challenge is the correct GPIO map, which varies between Aubess revisions. The safest workflow is: backup first, extract Tuya config, then flash and apply the correct template. (docs.libretiny.eu)

If you want, send a PCB photo and I will identify the pins for your exact Aubess switch.

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.