OpenBK7231N Web UI Missing Drivers, Channels, Relays After Flashing Temu Meter

4711leow wrote:

@ElektrodaBot
chatgpt tells me below
1️⃣ Access the Web UI

Open Chrome and go to the board’s IP (e.g., http://10.0.0.200).

You should now see Drivers, Channels, Relays, Buttons, etc. i cannot ...

Initial assessment
- Your device is reachable at 10.0.0.200 and is running OpenBeken for BK7231N.
- You’re seeing the minimal “native” page (device info, pins, command tool). That page will not show the “Drivers, Channels, Relays, Buttons” panels you expect until:
1) you use the external WebApp UI, and/or
2) your hardware is actually configured (template/pins/drivers) so there are channels to show.
- TuyaMCU driver is loaded, but your current pin roles don’t include any UART pins for TuyaMCU, so no DP data can arrive and no channels can be created.

Direct answer
- To get the full UI: open https://openbekeniot.github.io/webapp/ and connect to your device at 10.0.0.200. If the browser warns about “mixed/insecure content” (HTTPS page talking to HTTP device), allow insecure content for that site or temporarily use another Chromium-based browser/profile with that setting. Then you will see Drivers, Channels, Buttons, Logs, Flash/OTA, etc.
- If WebApp still won’t connect, you can reach the native subpages directly on the device:
- http://10.0.0.200/index
- http://10.0.0.200/cfg
- http://10.0.0.200/cfg_pins
- http://10.0.0.200/cfg_script
- http://10.0.0.200/ota (or Flash tab in WebApp)

Detailed problem analysis
1) Why the UI looks “empty”
- The advanced controls are in the external WebApp. The minimal native page only shows what the firmware already knows about your hardware. With no template and no valid TuyaMCU UART, there are no channels to render yet.

2) Your current pins don’t define TuyaMCU UART
- You have Pin 23 as ADC and Pin 28 as Btn_n; many others are WifiLED. A TuyaMCU device requires one RX and one TX pin to the onboard Tuya MCU. Without setting those roles, the driver is “loaded” but receives no data.

3) The device is a “no‑name TEMU TH meter”
- Most of these are TuyaMCU-based TH meters: the sensor values are sent by the small Tuya MCU over UART to the BK7231N. Occasionally they’re I2C (AHT/SHT) or analog NTC, but your current state (tuyamcu loaded) suggests UART.

Current information and trends
- Recent OpenBeken builds keep moving features into the WebApp to save flash and RAM on-device. Expect the richest experience through the WebApp. The native pages are for recovery and quick configuration.
- Mixed-content restrictions in modern browsers can block the WebApp from talking to an HTTP device; adjusting the “Insecure content” site setting is the usual fix.

Supporting explanations and details
Follow this exact sequence to bring up the controls:

A. Connect with the WebApp
- Open https://openbekeniot.github.io/webapp/ → Device IP: 10.0.0.200 → Connect.
- If you see “blocked mixed content”:
- Chrome: click the lock icon → Site settings → Insecure content → Allow → reload.
- Or open the WebApp in another Chromium profile where you allow insecure content.

B. Update to the offered build
- Your page shows “1.18.226 available”. Use the WebApp Flash/OTA page (or http://10.0.0.200/ota) and update. Reboot after update. This avoids bugs already fixed upstream.

C. Apply a template (best case)
- In WebApp → Devices/Templates, search for a close match (Tuya TH, Hygrometer, Thermometer). Apply, Save, Reboot. If a matching template exists, it will set RX/TX and any status LED/Button automatically and you’ll immediately see Channels for temperature/humidity.

D. If no template matches, set TuyaMCU UART manually
- In Pins:
- Set unrelated roles (WifiLED on 24–27, ADC on 23) to None for now.
- Assign one pin to UART1 RX and one to UART1 TX (names in dropdown are typically RX1 and TX1, or UART1_RX / UART1_TX).
- Save Pins and Reboot.
- Typical baud for TuyaMCU is 9600. In Console:
- loglevel 5
- TuyaMCU_BaudRate 9600
- restart
- Verify reception:
- TuyaMCU_SendQueryDataPoints
- Watch Live Log: you should see dpIds arriving (often temperature and humidity as value or scaled integer). If you see nothing, try another plausible pin pair for RX1/TX1 and repeat. Use Safe Mode (5 quick power cycles) to recover if you mis-assign a critical pin.

E. Map dpIds to channels
- In WebApp → TuyaMCU (or Channel Types):
- Map the reported dpIds to Temperature and Humidity channels. Save, Reboot.
- Once mapped, the “Channels” panel will show readings, and you’ll get the UI controls you expected.

F. Optional: If your unit is not TuyaMCU
- If, after trying plausible UART pairs at 9600 and 115200, you never see Tuya frames, your meter may be direct-sensor:
- I2C sensors: set two pins to I2C_SCL / I2C_SDA and startdriver for the sensor (AHTx0, SHT3x, etc.).
- Analog NTC: keep ADC on the single ADC-capable pin and configure the NTC Beta/series resistor in Channels. This is less common for humidity.

Practical guidelines
- Keep a photo of the PCB handy. If you can, open the case and read the Wi‑Fi module (e.g., CB2S/CB3S) and look for MCU test pads marked RX/TX—this instantly reveals which pins to try.
- Change only two pins at a time when searching for UART; always save and reboot, then check the log.
- Once channels appear, set your WiFi LED and Button back as needed.

Possible disclaimers or notes
- Pin numbering in OpenBeken is module-specific; the numbers you see (0–28) are not the silk-screen names. Without a template or PCB photo, pin trial-and-error is normal.
- Browser security can block WebApp→device communication; this is not a device fault.

Suggestions for further checks
- Post a clear PCB photo (both sides), especially the area between the BK7231N module and the small Tuya MCU/sensor board.
- From Console, paste outputs of:
- help
- drivers
- pins
- TuyaMCU_SendQueryDataPoints (after setting RX/TX)
- A minute of log with loglevel 5 right after reboot

Brief summary
- You’re seeing the minimal on-device UI. Use the WebApp to get the full “Drivers/Channels/Buttons” interface. Then either apply a matching template or set the TuyaMCU UART pins, confirm dpIds in the log, and map them to temperature/humidity channels. After that, the expected controls will appear.

Questions for you
1) Does the WebApp connect to 10.0.0.200, or do you get a mixed-content warning?
2) After setting any RX1/TX1 pair and 9600 baud, do you see Tuya dpIds in the log? Which ones?
3) Can you share PCB photos and the module marking (e.g., CB2S/CB3S) so I can point you to the most likely UART pins?