Cannot Access Web UI for Board at IP Address in Chrome—No Drivers or Channels Displayed

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 canno...

Initial assessment
- Your device is reachable and running OpenBeken 1.18.177 (build Sep 20, 2025). It also reports that 1.18.226 is available.
- The page you pasted is the OpenBeken WebApp (the cloud configurator injected from GitHub), not the native OpenBeken WWW. That is why you don’t see the classic “Drivers / Channels / Relays / Buttons” view from many screenshots.
- The current template is effectively “empty”. It only shows several WifiLED roles, one button on pin 28, one ADC on pin 23, and a startup command to start the TuyaMCU driver, but there are no UART pins assigned for TuyaMCU. With that, no channels will appear.

Direct answer
- To see the classic native UI, open: http://10.0.0.200/index
- If the root page still opens the WebApp, keep using the /index path (bookmark it). From there you should have menu items like Drivers, Console, Channels, etc.

Detailed problem analysis
1) Why you don’t see “Drivers / Channels …”
- The WebApp is primarily for templates/pins and advanced config; the native UI is at /index. Nothing is broken—just a different entry point.

2) Your device type
- A “no‑name TEMU temperature/humidity meter” is usually a Tuya design with a small local MCU that reads the sensor and drives the LCD, while BK7231N exchanges data with that MCU via UART (“TuyaMCU” protocol).
- Your template includes “backlog startdriver tuyamcu”, but no Tuya RX/TX pins are assigned yet, so the driver starts and finds no UART → no data → no channels.

3) What must be present for TH readings to appear
- Correct UART mapping: one pin must be TuyaRX, one TuyaTX (to the local MCU).
- TuyaMCU driver running at the correct baud (normally 9600).
- DP (DataPoint) mapping so temperature/humidity get routed to OpenBeken channels and shown on the native page.

4) Version note
- You said you flashed 1.18.213, but the device reports 1.18.177. This suggests the previous flash is still running or OTA did not actually update. It’s fine for now, but once basic comms work, I recommend updating to the reported available 1.18.226 from the device’s About/OTA page.

Current information and trends
- Recent OpenBeken builds expose both the WebApp and the native WWW. The WebApp line you see (WEBAPP Url root: https://openbekeniot.github.io/webapp/) is normal.
- Most Tuya TH-meters use 9600 baud TuyaMCU. A minority instead wire the sensor directly (I2C SHT3x/SHTC3) to BK7231N. If your board is that minority, we’d use I2C roles + SHT3x driver instead of TuyaMCU. We’ll verify below.

Practical guidelines (do this step by step)
1) Open the native UI
- Try: http://10.0.0.200/index
- If you still land on the WebApp, look for a text link like “Native Web UI / Index” on the page; otherwise just keep using the /index path directly.

2) Check drivers and status (from native UI → Console)
- In the console run:
- drivers
- status
- pins
- Post the output here. It tells us what is actually active and how pins are set.

3) Assign Tuya UART pins (if this is really TuyaMCU)
- In WebApp → Pin Settings (or native Config → Pins), pick two unused pins and set:
- one to TuyaRX
- one to TuyaTX
- Save and reboot. Typical pairs on many TH meters are among mid‑numbered GPIOs; without the PCB photo we can’t know which two, so:
- Start with any pair not already used (avoid the button on 28).
- After each attempt, open Console and look for live Tuya logs (dpId messages). If nothing, try another pair.
- In Console, also set baud if needed:
- If there is a TuyaMCU page in WebApp, set 9600 there; or from console if available in your build: TuyaMCU_SetBaudRate 9600

4) Verify data reception
- As soon as the RX/TX pair is correct, the console will start printing Tuya frames (dpIds). You should then see Temperature/Humidity channels appear on the native “Channels” page.
- Use the WebApp’s TuyaMCU section (or the native TuyaMCU mapping page if present) to map dpIds to channels and types (Temperature, Humidity). Save and reboot.

5) If no Tuya traffic on any UART pair
- Then your unit likely wires the sensor directly to BK7231N. In that case:
- Assign two pins as I2C_SCL and I2C_SDA.
- Start the SHT3x/SHTC3 driver.
- Temperature/Humidity should appear on Channels if the pins are right.
- Without the board photos, expect a little trial-and-error on pin pairs.

6) Clean up pins
- You have WifiLED assigned to many pins (22, 24, 25, 26, 27). Only one WifiLED is needed. Remove duplicates to free pins for UART/I2C.

7) Optional: update firmware after it works
- From About/OTA, update to the offered 1.18.226 to get the latest fixes and consistent menus. Do not update in the middle of pin probing—do it once basic functionality works.

Supporting explanations
- “Drivers, Channels …” only populate when a driver is started and at least one channel exists. With TuyaMCU unmapped, Channels remains empty.
- The WebApp’s Devices dropdown (803 devices) lets you try a close template. If you find a “Tuya TH meter” template, apply it, then adjust pins if needed.

Safety and legal
- If this meter is mains powered, unplug before opening the case. If it’s battery powered, still avoid shorting pads while probing.
- Modifying firmware voids manufacturer warranty.

Suggestions for further research
- If you can, post PCB photos (both sides, sharp, readable chip markings). With that we can read the BK7231N pinout and spot the UART/I2C routing in minutes.
- Share console outputs of drivers, status, pins after each step.

Brief summary
- You are on the WebApp, not the native UI—open http://10.0.0.200/index to see the classic pages.
- Configure the correct pins: either TuyaRX/TuyaTX + TuyaMCU at 9600, or I2C_SCL/I2C_SDA + SHT3x driver.
- Once pins and driver are correct, Temperature/Humidity channels will appear. Then you can tidy the template and optionally update to 1.18.226.

Questions for you
1) What exactly do you see at http://10.0.0.200/index (list the tabs)?
2) Can you paste the outputs of drivers, status and pins from Console?
3) Is the device battery powered or mains? Does it have an LCD?
4) Can you provide clear photos of the PCB (both sides), especially around the BK7231N and any small 8‑bit MCU or sensor chip?