logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

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

io2345 1140 38
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
Report a violation of the law
Reply | New topic
  • #1 21828759
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    Does anyone have experience with a TH03 Pro Temperatur/Humidity Sensor and the chance to get them working in a proper way with OpenBeken (or other firmware which doesn't contact chinese servers)?
    There are several threads on the forum about these sensors, yet non for this model. Some of the threads are rather old, like this one Link on elektroda.com or this one (in polish) Link on elektroda.com.
    I ordered mine out of couriousness from here: Link on Aliexpress as WiFi model.

    Digital thermometer and hygrometer with LCD showing 26°C and 58% humidity
  • ADVERTISEMENT
  • ADVERTISEMENT
  • #3 21829560
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    The item you found should be exactly the same model, TH03 Pro. That's what's inside:

    Inside of a device showing a PCB with battery spring contacts and a blue electronic module on the right

    U3 has nothing written on it, U1 reads something like "QD01 2507 NT CJT 4322X". I have no idea, which of the two chips is the MCU.

    Close-up of an SMD IC on a PCB with labels U1, R6, R11, and C3

    Communication module is CB3S, which is well known in OpenBeken. It transmits only three values: Temperature, Humidity and Battery State. It transmits data every 90 seconds (or so). Most of the time, the device is sleeping and the values in the display don't change, even if you heat or cool it. When the WiFi-Symbol starts animation, data is transmitted and some seconds later values appear in the app as well.
    What's the next recommended step to take? Just trying to flash with latest OBK-Version?
    For flashing I would have to mute the MCU, right? If anyone could help me with that? Probably there is an easier way than cutting the lead from CB3S to MCU, like setting an enable pin on the MCU to high or low signal?

    Update: Apparently U3 is the MCU, so U1 should be the LCD-Controller.
    Pin 10 of the MCU has direct connection to RX on CB3S, Pin 9 to TX. Pin 5 is V+, Pin 12 is GND.
    What does TP (Pin 2), TH_SCL (Pin14), TH_SDA (Pin 13) and TH_VOD (Pin 15) mean?
  • #4 21832736
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    Please tell me how to start. What is the best order? Trying to flash the device first or better trying to record the communication between MCU and CB3S first?
    I already did that with another device some time ago, but I don't remember how.
    Are there any guides, that are of help? Guides for flashing CB3S, or for recording traffic between MCU and CB3S?
  • ADVERTISEMENT
  • #5 21834503
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    If it can't be done with OpenBeken or no help can be provided: Is there an alternate firmware of different make with better support?
  • #6 21834514
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    Well, it's TuyaMCU. Just dump the firmware, dpId list can be downloaded from Tuya later.

    Some devices can be flashed without MCU removal/trace cut, some can't. Depends on luck.
  • #7 21834570
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    >>21834514 Thank you for your feedback. The dpId list shouldn't matter, in fact. The only user-reachable actuator is the button to connect the device to the tuya-app (which isn't of any use after flashing to OBK). As mentioned, the device only has to report temperature, humidity and general battery status via MQTT every once a while. OK, so I'll try my best to simply read out the original firmware and flash latest BK7231N firmware.
    Do you know where I can find the latest guide and software for flashing? Mine is certainly two years old. There is probably way better software now.
  • #9 21834713
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    >>21834572 Thank you. Latest release: yesterday!

    You don't have a link to latest MCU-Analyzer by chance?

    UPDATE: Found it: ]Openshwprojects
    This tool seems to be able to do dual capture on UART as well. Right?
  • #10 21836406
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    Communication log with original firmware. First without WiFi connection in the App, establishing connection and from that on transmitting values. First with light temp./humidity changes (resulting in slow update intervall), at the end with greater changes.:

    Code: text Expand Select all Copy to clipboard
    Sent by WiFi module:
55 AA   00   01      00 24   7B2270223A226C66333679356E7762386A6B78776767222C2276223A22312E302E30227D   99   
HEADER   VER=00   Product      LEN   {"p":"lf36y5nwb8jkxwgg","v":"1.0.0"}   CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   01      00 24   7B2270223A226C66333679356E7762386A6B78776767222C2276223A22312E302E30227D   99   
HEADER   VER=00   Product      LEN   {"p":"lf36y5nwb8jkxwgg","v":"1.0.0"}   CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   01      00 24   7B2270223A226C66333679356E7762386A6B78776767222C2276223A22312E302E30227D   99   
HEADER   VER=00   Product      LEN   {"p":"lf36y5nwb8jkxwgg","v":"1.0.0"}   CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   01      00 24   7B2270223A226C66333679356E7762386A6B78776767222C2276223A22312E302E30227D   99   
HEADER   VER=00   Product      LEN   {"p":"lf36y5nwb8jkxwgg","v":"1.0.0"}   CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   03      00 00      02   
HEADER   VER=00   WifiState      LEN      CHK   

Sent by WiFi module:
55 AA   00   01      00 24   7B2270223A226C66333679356E7762386A6B78776767222C2276223A22312E302E30227D   99   
HEADER   VER=00   Product      LEN   {"p":"lf36y5nwb8jkxwgg","v":"1.0.0"}   CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   10      00 01   00   10   
HEADER   VER=00   ObtainDPcache      LEN         CHK   

Sent by WiFi module:
55 AA   00   0B      00 00      0A   
HEADER   VER=00   Unk      LEN      CHK   

Sent by WiFi module:
55 AA   00   05      00 05   1404000100   22   
HEADER   VER=00   Unk      LEN   dpId=20 Enum V=0      CHK   

Sent by WiFi module:
55 AA   00   05      00 15   1B020004000000E82E0200040000002C6504000102   EE   
HEADER   VER=00   Unk      LEN   dpId=27 Val V=232,dpId=46 Val V=44,dpId=101 Enum V=2      CHK   

Sent by WiFi module:
55 AA   00   01      00 24   7B2270223A226C66333679356E7762386A6B78776767222C2276223A22312E302E30227D   99   
HEADER   VER=00   Product      LEN   {"p":"lf36y5nwb8jkxwgg","v":"1.0.0"}   CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   05      00 15   1B020004000000ED2E0200040000002C6504000102   F3   
HEADER   VER=00   Unk      LEN   dpId=27 Val V=237,dpId=46 Val V=44,dpId=101 Enum V=2      CHK   

Sent by WiFi module:
55 AA   00   01      00 24   7B2270223A226C66333679356E7762386A6B78776767222C2276223A22312E302E30227D   99   
HEADER   VER=00   Product      LEN   {"p":"lf36y5nwb8jkxwgg","v":"1.0.0"}   CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   05      00 15   1B020004000000F22E0200040000002A6504000102   F6   
HEADER   VER=00   Unk      LEN   dpId=27 Val V=242,dpId=46 Val V=42,dpId=101 Enum V=2      CHK   

Sent by WiFi module:
55 AA   00   01      00 24   7B2270223A226C66333679356E7762386A6B78776767222C2276223A22312E302E30227D   99   
HEADER   VER=00   Product      LEN   {"p":"lf36y5nwb8jkxwgg","v":"1.0.0"}   CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   05      00 15   1B020004000000F72E020004000000286504000102   F9   
HEADER   VER=00   Unk      LEN   dpId=27 Val V=247,dpId=46 Val V=40,dpId=101 Enum V=2      CHK   

Sent by WiFi module:
55 AA   00   01      00 24   7B2270223A226C66333679356E7762386A6B78776767222C2276223A22312E302E30227D   99   
HEADER   VER=00   Product      LEN   {"p":"lf36y5nwb8jkxwgg","v":"1.0.0"}   CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   05      00 15   1B020004000000F92E0200040000003F6504000102   12   
HEADER   VER=00   Unk      LEN   dpId=27 Val V=249,dpId=46 Val V=63,dpId=101 Enum V=2      CHK   

Sent by WiFi module:
55 AA   00   01      00 24   7B2270223A226C66333679356E7762386A6B78776767222C2276223A22312E302E30227D   99   
HEADER   VER=00   Product      LEN   {"p":"lf36y5nwb8jkxwgg","v":"1.0.0"}   CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   02      00 00      01   
HEADER   VER=00   McuConf      LEN      CHK   

Sent by WiFi module:
55 AA   00   05      00 15   1B020004000000F92E020004000000296504000102   FC   
HEADER   VER=00   Unk      LEN   dpId=27 Val V=249,dpId=46 Val V=41,dpId=101 Enum V=2      CHK   


    Hinzugefügt nach 17 [Minuten]:

    >>21836406 For flashing you will need to disconnect MCU and CB3S. For me it worked to just heat up MCU-Pin 10 and lift up the IC-leg with a needle - just enough, that it has no longer connection with the board. You can check with a multimeter between leg and pad "MCU_RX" - there should be no longer connection if succesful.
    Inside a device: PCB with ICs and a two-AA battery compartment with a metal spring contact.

    For flashing I soldered wires to the pads MCU_RX and MCU_TX (which is - in this order - CB3S_TX and CB3S_RX). For power you can use the battery connectors on the right side. Apply 3V to V+, Ground to V-.
    After succesful flashing and device startup you only have a minute or so to connect to the OBK-Webpage for configuring, as MCU will send the WiFi-module to sleep after a while. Just pull out a battery and reinsert to complete configuration. You'll probably have to do that several times.
  • #11 21836420
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    This makes it easy to configure OBK.

    setChannelType 1 Temperature_div10
    linkTuyaMCUOutputToChannel 27 val 1
    setChannelType 2 Humidity
    linkTuyaMCUOutputToChannel 46 val 2
    setChannelType 3 ReadOnlyLowMidHigh
    linkTuyaMCUOutputToChannel 101 enum 3
  • #12 21836423
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    >>21836420 Thank you @insmod. Didn't reload the page before sending Post#12.

    Entries in autoexec.bat should then be:

    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU
setMqttRetain 1  -> Setting Flag7

setChannelType 1 Temperature_div10
linkTuyaMCUOutputToChannel 27 val 1

setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 46 val 2

setChannelType 3 ReadOnlyLowMidHigh
linkTuyaMCUOutputToChannel 101 enum 3 

setChannelLabel 1 Temperatur
setChannelLabel 2 Luftfeuchte
setChannelLabel 3 Batterie
  • #13 21836447
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    >>21836423
    There are no such commands as "tuyaMCU_map", "setMqttRetain" or "setChannelScale"
    Your full autoexec would be
    Code: text Expand Select all Copy to clipboard
    
startDriver TuyaMCU
startDriver tmSensor

setChannelLabel 1 "Temperatur"
setChannelLabel 2 "Luftfeuchte"
setChannelLabel 3 "Batterie"

setChannelType 1 Temperature_div10
linkTuyaMCUOutputToChannel 27 val 1
setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 46 val 2
setChannelType 3 ReadOnlyLowMidHigh
linkTuyaMCUOutputToChannel 101 enum 3
  • #14 21836454
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    >>21836447 You are right. Didn't have a look into the docs at
    OBK-Docs on Github
    I edited Post#12 now for not to confuse others...

    Setting the MQTT retain can be achieved by activating flag 7, right?

    Is driver tmSensor necessary? The sensor is read by the MCU, not by OBK

    EDIT: Again a look into this docs cleared things (at least for this driver):
    More OBK docs on github
    The driver is necessary for battery driven devices in order to keep the WiFi module sleeping as long as possible
  • #15 21836460
    divadiow
    Level 38  
    Posts: 4859
    Help: 424
    Rate: 860
    io2345 wrote:
    In case you are still collecting original dumps, let me know. I'll send you the Tuya-Dump.

    yes please
  • #16 21836479
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    >>21836454
    To keep values in HA while device is asleep - flag 35 (avty_t is availability).
  • #17 21836495
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    >>21836479 I'm on ioBroker, not HA. As far as I understand, Flag 35 is specifically for HA, is it?
    Flag 7 should then be the right choice for me, I guess.
  • #18 21837785
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    I activated flags 37 + 51. Reconnect times are between 6 - 13 seconds.
    Let's wait and see how battery life turns out to be.

    Final autoexec.bat is

    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU
startDriver tmSensor

setChannelLabel 1 "Temperatur"
setChannelLabel 2 "Luftfeuchte"
setChannelLabel 3 "Batterie"

setChannelType 1 Temperature_div10
linkTuyaMCUOutputToChannel 27 val 1
setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 46 val 2
setChannelType 3 ReadOnlyLowMidHigh
linkTuyaMCUOutputToChannel 101 enum 3

    ======================
    Feedback after three months: Still running without any signs of battery weakness. Recommendable.
  • ADVERTISEMENT
  • #19 21890518
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    I re-ordered another TH03Pro, and this time arrived with T1-3S controller instead of CB3S.

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

    From searching in elektroda.com I found, that this is supposed to be BK7231T - BK7238 to be exact.
    Can anyone confirm that?

    Hinzugefügt nach 8 [Minuten]:

    Should definitely do a read-out of the original firmware, as this is my only T1-3s so far.
    @divadiow : Do you need the FW in this version, or is it just "same same" as CB3S?
  • #20 21890540
    divadiow
    Level 38  
    Posts: 4859
    Help: 424
    Rate: 860
    it'd be a nice-to-have, sure. it'll be different to the BK7231N/CB3S version. T1=BK7238
  • #21 21890692
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    >>21890540 I can't back up the original firmware. Read stops after 8 or 9 seconds, independently from hardware and baud settings. I used a different PC and a different serial adapter, tried all available baud settings. Even, if I connect the T1-3s's Vcc (pin 8) directly to 3,3V. No idea how to get on

    Hinzugefügt nach 2 [Minuten]:

    RX/TX are connected to the pads MCU_TX and MCU_RX on the board, MCUs Pin 10 is disconnected from the board - same procedure as above with the CB3S
  • #22 21891042
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    That's what I get:


    Code: text Expand Select all Copy to clipboard
    
Backup name is set to Th03Pro_T1-S3.Starting read!
Read parms: start 0x00 (sector 0), len 0x200000 (512 sectors)
Now is: Sunday, 26 April 2026 10:10:15.
Flasher mode: BK7238
Going to open port: COM7.
Serial port open!
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (115200)!
Chip ID: 0x7238
Will try to read device flash MID (for unprotect N):
Flash MID loaded: 152085
Will now search for Flash def in out database...
Flash def found! For: 152085
Flash information: mid: 152085, icName: P25Q16HBK, manufacturer: Puya, szMem: 200000, szSR: 2, cwUnp: 0, cwEnp: 7, cwMsk: 407C, sb: 2, lb: 5, cwdRd: 05-35-FF-FF, cwdWr: 01-31-FF-FF
Flash size is 2MB
Entering SetProtectState(True)...
sr: 7c
sr: 7c
final sr: 7c
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
sr: 0
sr: 0
final sr: 0
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
SetProtectState(True) success!
Going to start reading at offset 0x00...
0x00...
  • #23 21891045
    divadiow
    Level 38  
    Posts: 4859
    Help: 424
    Rate: 860
    Yes. Unfortunately TuyaMCU on RX/TX can often get in the way of flashing efforts. It's been known that the traces between module and TuyaMCU need to be temporarily severed for successful flashing.

    Or desolder the whole T1 module if you have hot air gun to cleanly remove it

    Added after 2 [minutes]:

    Potentially TuyaMCU could be held in reset mode so it's effectively offline. BUT, I'm not sure if these unmarked generic 16-pin MCUs have that ability. No idea if we know what each pin on the IC is.
  • #24 21891084
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    >>21891045 Found, that the MCU periodically pulls Pin1 of T1-3S to ground. That's why read-back stops. This Pin is directly connected to Pin3 of the MCU. So you have to detach that line as well. Check between leg and R1 if detach was successful.


    TH03 Pro Temperature Humidity Sensor Compatibility with OpenBeken Integration (possibly)
  • #25 21891087
    divadiow
    Level 38  
    Posts: 4859
    Help: 424
    Rate: 860
    Ah of course. TuyaMCU will cut power too. Maybe powering T1 module directly would have had lead to success too
  • #26 21891088
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    >>21891087 Unfortunately not - that's what I tried first.
  • #27 21891091
    divadiow
    Level 38  
    Posts: 4859
    Help: 424
    Rate: 860
    Silly me. Pad1 is RST, so that would make sense
  • #28 21891092
    io2345
    Level 9  
    Posts: 244
    Help: 1
    Rate: 6
    Next problem: OBK can not be flashed:

    Code: text Expand Select all Copy to clipboard
    Starting flash new (no backup)!
Now is: Sunday, 26 April 2026 11:23:35.
Flasher mode: BK7238
Going to open port: COM7.
Serial port open!
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus failed, will try again - 0/100!
Getting bus success!
Going to set baud rate setting (115200)!
Chip ID: 0x7238
Will try to read device flash MID (for unprotect N):
Flash MID loaded: 152085
Will now search for Flash def in out database...
Flash def found! For: 152085
Flash information: mid: 152085, icName: P25Q16HBK, manufacturer: Puya, szMem: 200000, szSR: 2, cwUnp: 0, cwEnp: 7, cwMsk: 407C, sb: 2, lb: 5, cwdRd: 05-35-FF-FF, cwdWr: 01-31-FF-FF
Flash size is 2MB
Entering SetProtectState(True)...
sr: 0
sr: 0
final sr: 0
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
SetProtectState(True) success!
Reading file firmwares/OpenBK7238_QIO_1.18.287.bin...
Loaded 1253376 bytes from firmwares/OpenBK7238_QIO_1.18.287.bin...
Preparing to write data file to chip - resetting bus and baud...
Getting bus... (now, please do reboot by CEN or by power off/on)
Getting bus success!
Going to set baud rate setting (115200)!
Will try to read device flash MID (for unprotect N):
Flash MID loaded: 152085
Will now search for Flash def in out database...
Flash def found! For: 152085
Flash information: mid: 152085, icName: P25Q16HBK, manufacturer: Puya, szMem: 200000, szSR: 2, cwUnp: 0, cwEnp: 7, cwMsk: 407C, sb: 2, lb: 5, cwdRd: 05-35-FF-FF, cwdWr: 01-31-FF-FF
Flash size is 2MB
Entering SetProtectState(True)...
sr: 0
sr: 0
final sr: 0
msk: 407c
cw: 0, sb: 2, lb: 5
bfd: 0
SetProtectState(True) success!
Going to do erase, start 0x00, sec count 306!
Erasing block 0x00... ok! Erasing block 0x10000... ok! Erasing block 0x20000... ok! Erasing block 0x30000... ok! Erasing block 0x40000... ok! Erasing block 0x50000... ok! Erasing block 0x60000... ok! Erasing block 0x70000... ok! Erasing block 0x80000... ok! Erasing block 0x90000... ok! Erasing block 0xA0000... ok! Erasing block 0xB0000... ok! Erasing block 0xC0000... ok! Erasing block 0xD0000... ok! Erasing block 0xE0000... ok! Erasing block 0xF0000... ok! Erasing block 0x100000... ok! Erasing block 0x110000... ok! Erasing block 0x120000... ok! Erasing sector 0x130000... ok! Erasing sector 0x131000... ok! 
All selected sectors erased!
failed with serial.BytesToRead 0 (expected 15)
The beginning of buffer in UART contains  data.
0x00... Writing sector 0x00 failed!
Writing file data to chip failed.
  • #29 21891142
    divadiow
    Level 38  
    Posts: 4859
    Help: 424
    Rate: 860
    Hmm. Maybe this is now the TuyaMCU comms getting in the way. But dunno why you could read but not write
  • #30 21891152
    insmod
    Level 31  
    Posts: 1353
    Help: 160
    Rate: 425
    Just to be sure, connect module GND to adapter GND.
    On many MCU devices, it's GND that's being used to control if module is on or off, not 3.3V.
Reply | New topic
Report a violation of the law

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.
Today's popular
ADVERTISEMENT