logo elektroda
logo elektroda
X
logo elektroda

TH03 Pro Temperature Humidity Sensor Compatibility with OpenBeken Integration (possibly)

io2345 984 34
Best answers

Can the TH03 Pro temperature/humidity sensor be flashed with OpenBeken or another local firmware, and how should it be wired and configured?

Yes — the TH03 Pro is a TuyaMCU device with a CB3S Wi‑Fi module, so it can be used with OpenBeken after flashing the BK7231N side and mapping the MCU data points [#21834514][#21836406] For flashing, one user had to disconnect MCU pin 10 from the CB3S RX line (lifting the IC leg worked), then connect to the MCU_RX and MCU_TX pads, and power the board from the battery pads with 3 V on V+ and GND on V- [#21836406] After first boot, you only have a short window to open the OBK web UI before the MCU puts Wi‑Fi back to sleep, so you may need to pull and reinsert a battery a few times while configuring [#21836406] The working OBK setup is `startDriver TuyaMCU` plus `startDriver tmSensor`, with `linkTuyaMCUOutputToChannel 27 val 1` for temperature, `46 val 2` for humidity, and `101 enum 3` for battery state; suggested channel types are `Temperature_div10`, `Humidity`, and `ReadOnlyLowMidHigh` [#21836420][#21836447] For battery behavior, one user reported using flags 37 and 51, with reconnect times of 6–13 seconds, and the device still running fine after two months [#21837785]
Generated by the language model.
ADVERTISEMENT
  • #31 21891156
    io2345
    Level 9  
    >>21891152 Tried that without further progress. Latest Flashtool also says "CheckRespond_FlashWrite4K: bad value returned?".
    What does it mean?

    I guess the Problem is this, right?:
    failed with serial.BytesToRead 0 (expected 15

    Hinzugefügt nach 1 [Stunden] 22 [Minuten]:

    @p.kaczmarek2 : Could you adress that to the developers? I put it in here: https://github.com/openshwprojects/BK7231GUIFlashTool/issues/21
  • ADVERTISEMENT
  • ADVERTISEMENT
  • #33 21891237
    io2345
    Level 9  
    >>21891223 Doesn't look promising either:

    [14:30:00] [INFO] CMD |C:\Users\Papa\Downloads\BKFIL\windows\bk_loader\bk_loader.dist\bk_loader.exe --initiator 1 --log_level 3 --log_path C:\Users\Papa\Downloads\BKFIL\data\log\bk_loader_log --flash_config_path_out C:\Users\Papa\Downloads\BKFIL\data\flutter_assets\assets\config\flash_config_out.yaml --bk_loader_config_path_out C:\Users\Papa\Downloads\BKFIL\data\flutter_assets\assets\config\bk_loader_config_out.yaml --bin_parser_path C:\Users\Papa\Downloads\BKFIL\data\flutter_assets\assets\config\bin_parser.yaml download -p COM7 -b 921600 --reset_baudrate 115200 --link_type 5 --reset_type 3 -i C:\Users\Papa\Downloads\OBK-FlasherBK7231_v313\firmwares\OpenBK7238_QIO_1.18.287.bin@0x0-0x132000 --pre_erase 1 --random_bin_path C:\Users\Papa\Downloads\BKFIL\data\random_bin\random.bin --reboot|
    [14:30:01] [WARN] 4.1.1.128
    [14:30:01] [WARN] comport: COM7
    [14:30:01] [WARN] link type: LINKCHECK.BOOTROM
    [14:30:01] [WARN] reset type: RESET_TYPE.MULTI
    [14:30:01] [WARN] getbus times: 100
    [14:30:01] [WARN] reboot: True
    [14:30:01] [WARN] link key: None
    [14:30:01] [WARN] work baudrate: 921600
    [14:30:01] [WARN] erase all: False
    [14:30:01] [INFO] Getting bus v2,specified LINKCHECK.BOOTROM...
    [14:30:01] [INFO] Get bus success, type: LINKCHECK.BOOTROM
    [14:30:02] [INFO] verifying chip product id...
    [14:30:02] [INFO] verifying chip product id OK.
    [14:30:02] [INFO] parse flash info...
    [14:30:02] [INFO] flash mid is 0x152085
    [14:30:02] [INFO] check BKAESRDM words in flash...
    [14:30:02] [INFO] check BKAESRDM words in flash OK.
    [14:30:02] [INFO] unprotect flash...
    [14:30:02] [INFO] unprotect flash OK.
    [14:30:02] [INFO] align start/end address...
    [14:30:02] [INFO] original start address: 0x0, length: 0x132000, aligned start address: 0x0, length: 0x132000,subsequent processing will be done using the aligned version of start address and length.
    [14:30:02] [INFO] set baudrate to 921600...
    [14:30:02] [INFO] [0] erase flash.
    [14:30:02] [INFO] [0] start: 0x0.
    [14:30:02] [INFO] [0] length: 0x132000.
    [14:30:02] [INFO] erase start address @0x0, end address @0x132000.
    [14:30:02] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 0
    [14:30:02] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 5
    [14:30:02] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 10
    [14:30:02] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 15
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 20
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 26
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 31
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 36
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 41
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 47
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 52
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 57
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 62
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 67
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 73
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 78
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 83
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 88
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 94
    [14:30:03] [INFO] DEVICE: BK, Status: Erasing Flash, Progress: 99
    [14:30:03] [INFO] end erase.
    [14:30:03] [INFO] [0] write flash.
    [14:30:03] [INFO] [0] start: 0x0.
    [14:30:03] [INFO] [0] length: 0x132000.
    [14:30:03] [INFO] write flash start @0x0, length: 0x132000
    [14:30:03] [INFO] DEVICE: BK, Status: Writing Flash, Progress: 0
    [14:30:04] [ERROR] Write sector @0x1000 fail, buf length: 0x1000
    [14:30:04] [INFO] write sector @0x1000 fail, retry
    [14:30:05] [ERROR] erase custom size fail @0x1000, size: 4096
    [14:30:05] [INFO] Getting bus v2,specified LINKCHECK.BOOTROM...
    [14:30:06] [INFO] Please reset the chip
    [14:30:06] [INFO] Waiting reset......
    [14:30:07] [INFO] Get bus success, type: LINKCHECK.BOOTROM
    [14:30:08] [ERROR] Write sector @0x1000 fail, buf length: 0x1000
    [14:30:08] [INFO] Getting bus v2,specified LINKCHECK.BOOTROM...
    [14:30:09] [INFO] Please reset the chip
    [14:30:09] [INFO] Waiting reset.....
    [14:30:11] [ERROR] Write sector @0x1000 fail, buf length: 0x1000
    [14:30:11] [INFO] Getting bus v2,specified LINKCHECK.BOOTROM...
    [14:30:12] [INFO] Please reset the chip
    [14:30:12] [INFO] Waiting reset......
    [14:30:14] [INFO] Get bus success, type: LINKCHECK.BOOTROM
    [14:30:15] [ERROR] Write sector @0x1000 fail, buf length: 0x1000
    [14:30:15] [INFO] Getting bus v2,specified LINKCHECK.BOOTROM...
    [14:30:15] [INFO] Please reset the chip
    [14:30:15] [INFO] Waiting reset......
    [14:30:17] [INFO] Get bus success, type: LINKCHECK.BOOTROM
    [14:30:18] [ERROR] Write sector @0x1000 fail, buf length: 0x1000
    [14:30:18] [INFO] Getting bus v2,specified LINKCHECK.BOOTROM...
    [14:30:19] [INFO] Please reset the chip
    [14:30:19] [INFO] Waiting reset......
    [14:30:20] [INFO] Get bus success, type: LINKCHECK.BOOTROM
    [14:30:21] [ERROR] Write sector @0x1000 fail, buf length: 0x1000
    [14:30:22] [ERROR] write sector @0x1000 by retry fail.
    [14:30:22] [ERROR] Write flash fail.
    [14:30:22] [INFO] do reboot from bootrom.
    [14:30:22] [ERROR] Download fail.
    [14:30:22] [INFO] Elapse time: 20.532138 seconds.
  • ADVERTISEMENT
  • #34 21891334
    divadiow
    Level 38  
    maybe it's now just the TuyaMCU sending stuff to T1 RX that's getting in the way
  • #35 21891398
    io2345
    Level 9  
    >>21891334 Surprisingly enough, that helped - thank you for suggesting. I detached MCUs pin 9 as well, and now I managed to flash - on the third attempt.
    Holy Moly, T1-3S is harder to defeat than CB-3S was.

Topic summary

✨ The discussion centers on the compatibility of the TH03 Pro Temperature and Humidity Sensor with OpenBeken firmware or alternative firmware solutions that avoid communication with Chinese servers. The original inquiry highlights a lack of specific information or successful integration reports for the TH03 Pro model, despite existing threads on similar sensors. A respondent, without direct experience with the TH03 Pro, suggests an alternative sensor available on AliExpress, implying potential options for users seeking compatible hardware. The focus remains on achieving proper sensor functionality within open-source or privacy-conscious firmware environments.
Generated by the language model.
ADVERTISEMENT