logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

OpenBeken on touch switch with T34 - offline control, 433MHz remotes, cloud

2konrafal1993 2145 31
Best answers

Can OpenBeken make a T34-based touch switch work offline with touch and 433MHz remotes, and is the T34 enough to do it?

Yes—after flashing OpenBeken, the device works locally and does not send data to the internet, so you can use it cloud-free and keep it offline after setup [#21710531] If your switch uses the common design where the RF chip is separate and only feeds the button controller/Wi‑Fi module with a digital “button pressed” signal, the 433MHz remotes should keep working after the firmware change, alongside the touch buttons [#21710531][#21710571][#21710904] The T34 is treated as a BK7231N, and you flash only that Wi‑Fi module; a backup read first is recommended so the GPIO configuration can be recovered and restored if needed [#21710531][#21710861] If there are no UART programming pads, that is actually a sign it is not TuyaMCU-based, which matches the type of board where RF can still work independently [#21710615] Initial setup can be done via the OBK AP at 192.168.4.1, and if Wi‑Fi setup fails you can force AP mode by power-cycling the device 5 times [#21710904][#21711063][#21711086]
Generated by the language model.
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Report a violation of the law
Reply | New topic
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion addresses a Chinese touch switch based on the T34 (BK7231N) processor featuring 433MHz remote control and WiFi connectivity, which crashes after prolonged WiFi use. Uploading OpenBeken firmware enables fully local operation without cloud dependency, allowing control via touch and 433MHz remotes without network connection after initial WiFi setup. The RF chip is typically connected to the button controller, which interfaces digitally with the WiFi module, preserving remote functionality post-firmware update. The device lacks visible RX/TX programming pads, complicating flashing, but soldering the T34 chip with hot air rework is feasible. Firmware flashing involves selecting BK7231N/T34 in the flasher, downloading the firmware from the web, and writing it to the device. After flashing, the device may create an Access Point at 192.168.4.1 for configuration. WiFi setup requires entering SSID and password in the web app or configuring pins manually via JSON import. If WiFi credentials are incorrect, rebooting the device five times triggers AP mode for recovery. The router used operates on 2.4GHz with AES encryption and WPA2 authentication. The user is advised to perform setup in AP mode if WiFi is unreliable, noting that the web app is downloaded live from GitHub, requiring simultaneous internet and device AP connection.
Generated by the language model.
Today's popular

FAQ

TL;DR: Flashing OpenBeken on a T34/BK7231N makes the switch run “100% locally” with no cloud, and you can still use touch and RF if the board routes them independently. [Elektroda, p.kaczmarek2, post #21710531] Why it matters: This FAQ helps DIYers fix unstable cloud touch switches and keep offline control with 433 MHz remotes.

Quick Facts

Can I go fully cloud‑free after flashing OpenBeken?

Yes. After flashing OpenBeken, the device operates 100% locally. You can use the capacitive touch keys and optional Wi‑Fi without sending data to the internet. This suits privacy‑focused installs or unreliable routers. “The device works 100% locally.” [Elektroda, p.kaczmarek2, post #21710531]

Will my 433 MHz remotes still work without the cloud?

In common two‑chip designs, RF pairing stays functional because the RF chip talks to the local button controller, not the cloud. The Wi‑Fi module just sees a virtual “button press.” Pairing remains local. See the referenced teardown guidance for this architecture. [Elektroda, p.kaczmarek2, post #21710531]

What is OpenBeken?

OpenBeken (OBK) is open firmware for BK72xx/Tuya Wi‑Fi modules that replaces cloud‑dependent code with local control and a web UI. It’s uploaded to the module’s flash and configured via its AP. It supports templates for pins and common devices. [Elektroda, p.kaczmarek2, post #21710531]

What is the T34 module, and how does it relate to BK7231N?

T34 is a Tuya module based on the BK7231N SoC. When flashing, choose BK7231N mode in your tool. Treat T34 as BK7231N for backup and writing firmware via UART1. [Elektroda, p.kaczmarek2, post #21710861]

How do I flash a T34/BK7231N with BK7231GUIFlashTool?

Three steps: 1) Select BK7231N/T34 and read a full backup. 2) Use “Download firmware from web,” then “Write firmware.” 3) Power‑cycle; the module should broadcast its config AP. Then continue setup. [Elektroda, p.kaczmarek2, post #21710944]

What IP do I use for setup? Why doesn’t 127.0.0.1 work?

127.0.0.1 is your computer’s localhost. OpenBeken hosts its portal at the device AP IP, 192.168.4.1. Connect to the OBK Wi‑Fi network first, then open that address in your browser. [Elektroda, p.kaczmarek2, post #21711050]

I entered the wrong Wi‑Fi password—how do I recover?

Force AP mode: power the device off and on five times, with short pauses. After the fifth reboot, the module starts its AP again. Join it and re‑enter credentials or continue in offline mode. [Elektroda, p.kaczmarek2, post #21711086]

How do I import the Tuya template and enable useful services?

Find the device’s new IP, open the web UI, then Import the provided Tuya JSON. In Options → Short startup command, add: PowerSave 1 and startDriver SSDP. Save and reboot to apply. [Elektroda, p.kaczmarek2, post #21711063]

My router won’t connect, but a phone hotspot works. What should I try?

Configure everything in AP mode to avoid router quirks, or set pins manually in Configure Module. Verify the router is 2.4 GHz only and WPA2‑AES. Continue offline if desired. [Elektroda, p.kaczmarek2, post #21711168]

What signal level is acceptable? I see about −69 dB RSSI.

A measured −69 dB RSSI suggests the AP and device can hear each other, yet router settings may still block association. Test with a phone hotspot, then adjust router channels and security. [Elektroda, 2konrafal1993, post #21711890]

Does the RF input really go to the CEN pin on some boards?

CEN is the BK7231N reset pin. If you observe RF activity on CEN without resets, your board may repurpose that line, affecting RF handling. Verify with an oscilloscope before mapping pins. [Elektroda, p.kaczmarek2, post #21713895]

After flashing, my RF remotes stopped toggling relays. What now?

Some batches changed routing. RF used to work without the Wi‑Fi module’s participation, but newer layouts differ. Re‑inspect RF‑to‑MCU paths, confirm the template, and try learning mode again. “That must have changed something in the party.” [Elektroda, p.kaczmarek2, post #21714063]

Do missing RX/TX test pads mean TuyaMCU is involved?

Lack of exposed RX/TX often indicates it is not a TuyaMCU serial bridge. Instead, buttons and RF feed GPIOs directly on the Wi‑Fi SoC, which OpenBeken can handle locally. [Elektroda, p.kaczmarek2, post #21710615]

Which model was identified from photos in this thread?

The board noted matches AY‑W602 SH_GANG_2_BL_WF. Use this hint when searching templates or similar teardowns for GPIO clues. [Elektroda, p.kaczmarek2, post #21710571]

Any proven soldering tips for safely reworking the T34 module?

Use hot‑air about 350 °C with a nozzle sized to the chip, generous RMA‑223 flux, airflow ~4/8, and keep the nozzle within 5 mm. Wait for the part to “float,” then lift to avoid pad damage. Secure the board to protect pads. [Elektroda, 2konrafal1993, post #21710930]

How do I keep the device discoverable on my LAN after setup?

Add startDriver SSDP in Short startup command so it appears under Network on Windows. Combine with PowerSave 1 to reduce PSU heat and extend life. [Elektroda, p.kaczmarek2, post #21711063]
Generated by the language model.
ADVERTISEMENT