logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Tuya TH11 temperature & Humidity sensor (CHT8310), Configuration and autoexec

nickejonsson 570 12
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #1 21806018
    nickejonsson
    Level 3  
    Hi everyone, I'm a total newbie with OpenBeken and this TH11 sensor is turning out to be a pain in the a** to configure.

    It has a CB3S and a CHT8310 sensor. I've spent all day trying to get a reading, but I'm unsuccessful. I've tried starting the TuyaMCU driver (getting only heartbeat 55AA0003...) and also tried the CHT83XX driver on various pins without luck.

    My tolerance is drained – has anyone successfully tamed this specific model? If so, would you mind sharing your pin configuration and autoexec.bat?

    Thanks in advance!
    AI: Which version of OpenBeken firmware are you running on your TH11?
    OpenBK7231N_QIO_1.18.245.bin
    AI: Can you share exactly which pins you've tried for the CHT8310 sensor and how you have everything wired up right now?
    I soldered jumper wires to RX, TX, VDD and BAT- and managed to flash the device with the latest firmware.
    From Display to Complete System: How the Solution Team Creates Value at Unisystem [ad]
  • ADVERTISEMENT
  • #2 21806167
    divadiow
    Level 38  
    I don't recall seeing a 'TH11' labelled device before. Do you have pics of device/PCB inside?
  • ADVERTISEMENT
  • #4 21806176
    divadiow
    Level 38  
    OK, did you take a backup of the original Tuya firmware at all?
  • #5 21806275
    nickejonsson
    Level 3  
    I did, but I didn't get anything meaningful, I think.

    Code: JSON
    Log in, to see the code


    Added after 5 [minutes]:


    Electronic module with blue PCB and white Bluetooth chip
    I did take a photo, apparently. Sorry for the bad quality and for the ugly soldering. I have Essential Tremors, which don't align well with this hobby. 😅😂
  • #6 21806421
    divadiow
    Level 38  
    if this is your autoexec do you get any readings?

    Code: Text
    Log in, to see the code
  • #7 21806487
    nickejonsson
    Level 3  
    I got the following in the logs after adding your configuration suggestion for the autoexec:

    Code: text Expand Select all Copy to clipboard
    llback called for bT homeassistant/ subT homeassistant/+
Info:CMD:CMD_StartScript: started @startup at the beginning
Info:CMD:CMD_PowerSave: will set to 1
Info:MAIN:Started battery.
Info:NTP:NTP driver initialized with server=217.147.223.78, offset=0, syncing every 60 seconds
Info:MAIN:Started NTP.
Info:MAIN:Driver CHT8305 is not known in this build.
Info:MAIN:Available drivers: 
Info:MAIN:TuyaMCU
Info:MAIN:, tmSensor
Info:MAIN:, PixelAnim
Info:MAIN:, NTP
Info:MAIN:, HTTPButtons
Info:MAIN:, I2C
Info:MAIN:, BL0942
Info:MAIN:, BL0942SPI
Info:MAIN:, BL0937
Info:MAIN:, CSE7766
Info:MAIN:, SM16703P
Info:MAIN:, SM15155E
Info:MAIN:, IR
Info:MAIN:, RC
Info:MAIN:, DDP
Info:MAIN:, SSDP
Info:MAIN:, DGR
Info:MAIN:, Wemo
Info:MAIN:, Hue
Info:MAIN:, PWMToggler
Info:MAIN:, DoorSensor
Info:MAIN:, SM2135
Info:MAIN:, BP5758D
Info:MAIN:, BP1658CJ
Info:MAIN:, SM2235
Info:MAIN:, CHT83XX
Info:MAIN:, KP18058
Info:MAIN:, ADCSmoother
Info:MAIN:, AHT2X
Info:MAIN:, DS1820
Info:MAIN:, Battery
Info:MAIN:, Bridge
Info:MAIN:, NEO6M
Info:CMD:CMD_StartScript: started autoexec.bat at the beginning
Info:MAIN:Main_Init_After_Delay done
Info:MAIN:Started TuyaMCU.
Info:MAIN:Started tmSensor.
Info:GEN:Channel 1 type changed to temperature_div10
Info:GEN:Channel 2 type changed to Humidity
Info:MAIN:Time 1, idle 138651/s, free 74664, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:TuyaMCU:Received: 55 AA 00 01 00 24 7B 22 70 22 3A 22 6A 33 66 6A 61 6A 66 32 78 30 61 70 73 71 67 70 22 2C 22 76 22 3A 22 31 2E 30 2E 30 22 7D A3 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 1 (QueryProductInformation) len 43
Info:TuyaMCU:ParseQueryProductInformation: received {"p":"j3fjajf2x0apsqgp","v":"1.0.0"}
Info:DRV:DRV_BATTERY : Measure Battery volt en perc
Info:DRV:DRV_BATTERY : ADC Value low device not on battery
Info:DRV:DRV_BATTERY : battery voltage : -0.585937 and percentage 0.000000%
Info:MAIN:Time 2, idle 62712/s, free 74664, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 3, idle 65549/s, free 74664, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 4, idle 66145/s, free 74664, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 5, idle 65129/s, free 74664, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Registered for wifi changes
Info:MAIN:Connecting to SSID [Weekend]
Info:MAIN:Time 6, idle 134045/s, free 69136, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Boot complete time reached (5 seconds)
Info:CFG:####### Set Boot Complete #######
Info:MAIN:Time 7, idle 132952/s, free 69136, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 8, idle 62422/s, free 69200, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 9, idle 0/s, free 69200, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 10, idle 0/s, free 69200, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:GEN:dhcp=0 ip=0.0.0.0 gate=0.0.0.0 mask=0.0.0.0 mac=38:a5:c9:b7:69:9b
Info:GEN:sta: 0, softap: 0, b/g/n
Info:MAIN:Time 11, idle 0/s, free 69200, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTING - 1
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTED - 4
Info:DRV:DRV_BATTERY : Measure Battery volt en perc
Info:DRV:DRV_BATTERY : ADC Value low device not on battery
Info:DRV:DRV_BATTERY : battery voltage : -0.585937 and percentage 0.000000%
Info:MAIN:Time 12, idle 43071/s, free 69392, MQTT 0(0), bWifi 1, secondsWithNoPing -1, socks 3/38 POWERSAVE
Info:TuyaMCU:Received: 55 AA 00 02 00 00 01 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 2 (MCUconf) len 7
Info:TuyaMCU:ProcessIncoming: TUYA_CMD_MCU_CONF, TODO!
Info:NTP:Seconds since Jan 1 1900 = 3977209497
Info:NTP:Unix time  : 1768220697 - local Time 2026-01-12 12:24:57
Info:MAIN:Time 13, idle 65292/s, free 69624, MQTT 0(0), bWifi 1, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MQTT:mqtt_host empty, not starting mqtt
Info:MAIN:Time 14, idle 67537/s, free 69624, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 15, idle 68260/s, free 69624, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:TuyaMCU:Received: 55 AA 00 02 00 00 01 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 2 (MCUconf) len 7
Info:TuyaMCU:ProcessIncoming: TUYA_CMD_MCU_CONF, TODO!
Info:TuyaMCU:Received: 55 AA 00 10 00 04 03 09 17 18 4E 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 16 (Unknown) len 11
Info:TuyaMCU:Received: 55 AA 00 0B 00 00 0A 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 11 (QuerySignalStrngth) len 7
Info:TuyaMCU:ProcessIncoming: received TUYA_V0_CMD_QUERYSIGNALSTRENGTH, so sending back signal
Info:TuyaMCU:Received: 55 AA 00 05 00 15 09 04 00 01 00 17 02 00 04 00 00 00 00 18 02 00 04 00 00 00 00 62 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 5 (WiFiSelect) len 28
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 9, dataType 4-enum and 1 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: byte 0
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: int32 0
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 24, dataType 2-val and 4 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: int32 0
Info:MAIN:Time 16, idle 69387/s, free 69624, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:TuyaMCU:Received: 55 AA 00 05 00 15 01 02 00 04 00 00 00 E6 02 02 00 04 00 00 00 14 03 04 00 01 02 2C 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 5 (WiFiSelect) len 28
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 1, dataType 2-val and 4 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: int32 230
Info:GEN:CHANNEL_Set channel 1 has changed to 230 (flags 0)

Info:MQTT:Channel has changed! Publishing 230 to channel 1 
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 2, dataType 2-val and 4 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: int32 20
Info:GEN:CHANNEL_Set channel 2 has changed to 20 (flags 0)

Info:MQTT:Channel has changed! Publishing 20 to channel 2 
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 3, dataType 4-enum and 1 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: byte 2
Info:MAIN:Time 17, idle 66147/s, free 69624, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 18, idle 69697/s, free 69624, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38 POWERSAVE
  • ADVERTISEMENT
  • #8 21806506
    divadiow
    Level 38  
    Code: Text
    Log in, to see the code


    this is not needed when the TuyaMCU is between the Beken MCU and temp/hum sensor.

    also, may need tuyaMcu_defWiFiState 4

    Code: Text
    Log in, to see the code
  • #9 21806563
    nickejonsson
    Level 3  
    Now I got this:

    Code: text Expand Select all Copy to clipboard
    rCallback called for bT cmnd/bekens_n/ subT cmnd/bekens_n/+
Info:MQTT:MQTT_RegisterCallback called for bT obkC9B7699B/ subT obkC9B7699B/+/get
Info:MQTT:MQTT_RegisterCallback called for bT homeassistant/ subT homeassistant/+
Info:CMD:CMD_StartScript: started @startup at the beginning
Info:CMD:CMD_PowerSave: will set to 1
Info:MAIN:Started battery.
Info:NTP:NTP driver initialized with server=217.147.223.78, offset=0, syncing every 60 seconds
Info:MAIN:Started NTP.
Info:MAIN:Driver CHT8305 is not known in this build.
Info:MAIN:Available drivers: 
Info:MAIN:TuyaMCU
Info:MAIN:, tmSensor
Info:MAIN:, PixelAnim
Info:MAIN:, NTP
Info:MAIN:, HTTPButtons
Info:MAIN:, I2C
Info:MAIN:, BL0942
Info:MAIN:, BL0942SPI
Info:MAIN:, BL0937
Info:MAIN:, CSE7766
Info:MAIN:, SM16703P
Info:MAIN:, SM15155E
Info:MAIN:, IR
Info:MAIN:, RC
Info:MAIN:, DDP
Info:MAIN:, SSDP
Info:MAIN:, DGR
Info:MAIN:, Wemo
Info:MAIN:, Hue
Info:MAIN:, PWMToggler
Info:MAIN:, DoorSensor
Info:MAIN:, SM2135
Info:MAIN:, BP5758D
Info:MAIN:, BP1658CJ
Info:MAIN:, SM2235
Info:MAIN:, CHT83XX
Info:MAIN:, KP18058
Info:MAIN:, ADCSmoother
Info:MAIN:, AHT2X
Info:MAIN:, DS1820
Info:MAIN:, Battery
Info:MAIN:, Bridge
Info:MAIN:, NEO6M
Info:CMD:CMD_StartScript: started autoexec.bat at the beginning
Info:MAIN:Main_Init_After_Delay done
Info:MAIN:Started TuyaMCU.
Info:MAIN:Started tmSensor.
Info:GEN:Channel 1 type changed to temperature_div10
Info:GEN:Channel 2 type changed to Humidity
Info:GEN:Channel 3 type changed to ReadOnlyLowMidHigh
Info:MAIN:Time 1, idle 137401/s, free 74416, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:TuyaMCU:Received: 55 AA 00 01 00 24 7B 22 70 22 3A 22 6A 33 66 6A 61 6A 66 32 78 30 61 70 73 71 67 70 22 2C 22 76 22 3A 22 31 2E 30 2E 30 22 7D A3 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 1 (QueryProductInformation) len 43
Info:TuyaMCU:ParseQueryProductInformation: received {"p":"j3fjajf2x0apsqgp","v":"1.0.0"}
Info:DRV:DRV_BATTERY : Measure Battery volt en perc
Info:DRV:DRV_BATTERY : ADC Value low device not on battery
Info:DRV:DRV_BATTERY : battery voltage : -0.585937 and percentage 0.000000%
Info:MAIN:Time 2, idle 64173/s, free 74416, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 3, idle 64254/s, free 74416, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 4, idle 65139/s, free 74416, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 5, idle 66234/s, free 74416, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Registered for wifi changes
Info:MAIN:Connecting to SSID [Weekend]
Info:MAIN:Time 6, idle 148524/s, free 69024, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Boot complete time reached (5 seconds)
Info:CFG:####### Set Boot Complete #######
Info:MAIN:Time 7, idle 134883/s, free 69024, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 8, idle 64969/s, free 69216, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 9, idle 0/s, free 69216, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 10, idle 0/s, free 69216, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:GEN:dhcp=0 ip=0.0.0.0 gate=0.0.0.0 mask=0.0.0.0 mac=38:a5:c9:b7:69:9b
Info:GEN:sta: 0, softap: 0, b/g/n
Info:MAIN:Time 11, idle 0/s, free 69216, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTING - 1
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTED - 4
Info:DRV:DRV_BATTERY : Measure Battery volt en perc
Info:DRV:DRV_BATTERY : ADC Value low device not on battery
Info:DRV:DRV_BATTERY : battery voltage : -0.585937 and percentage 0.000000%
Info:MAIN:Time 12, idle 44719/s, free 69256, MQTT 0(0), bWifi 1, secondsWithNoPing -1, socks 3/38 POWERSAVE
Info:TuyaMCU:Received: 55 AA 00 02 00 00 01 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 2 (MCUconf) len 7
Info:TuyaMCU:ProcessIncoming: TUYA_CMD_MCU_CONF, TODO!
Info:NTP:Seconds since Jan 1 1900 = 3977213243
Info:NTP:Unix time  : 1768224443 - local Time 2026-01-12 13:27:23
Info:MAIN:Time 13, idle 70542/s, free 69496, MQTT 0(0), bWifi 1, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MQTT:mqtt_host empty, not starting mqtt
Info:MAIN:Time 14, idle 74006/s, free 57792, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 3/38 POWERSAVE
Info:MAIN:Time 15, idle 67709/s, free 69496, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:TuyaMCU:Received: 55 AA 00 02 00 00 01 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 2 (MCUconf) len 7
Info:TuyaMCU:ProcessIncoming: TUYA_CMD_MCU_CONF, TODO!
Info:TuyaMCU:Received: 55 AA 00 10 00 04 03 09 17 18 4E 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 16 (Unknown) len 11
Info:TuyaMCU:Received: 55 AA 00 0B 00 00 0A 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 11 (QuerySignalStrngth) len 7
Info:TuyaMCU:ProcessIncoming: received TUYA_V0_CMD_QUERYSIGNALSTRENGTH, so sending back signal
Info:TuyaMCU:Received: 55 AA 00 05 00 15 09 04 00 01 00 17 02 00 04 00 00 00 00 18 02 00 04 00 00 00 00 62 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 5 (WiFiSelect) len 28
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 9, dataType 4-enum and 1 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: byte 0
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 23, dataType 2-val and 4 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: int32 0
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 24, dataType 2-val and 4 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: int32 0
Info:MAIN:Time 16, idle 71794/s, free 69496, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:TuyaMCU:Received: 55 AA 00 05 00 15 01 02 00 04 00 00 00 F1 02 02 00 04 00 00 00 1D 03 04 00 01 02 40 
Info:TuyaMCU:ProcessIncoming[v=0]: cmd 5 (WiFiSelect) len 28
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 1, dataType 2-val and 4 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: int32 241
Info:GEN:CHANNEL_Set channel 1 has changed to 241 (flags 0)

Info:MQTT:Channel has changed! Publishing 241 to channel 1 
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 2, dataType 2-val and 4 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: int32 29
Info:GEN:CHANNEL_Set channel 2 has changed to 29 (flags 0)

Info:MQTT:Channel has changed! Publishing 29 to channel 2 
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: processing id 3, dataType 4-enum and 1 data bytes
Info:TuyaMCU:V0_ParseRealTimeWithRecordStorage: byte 2
Info:GEN:CHANNEL_Set channel 3 has changed to 2 (flags 0)

Info:MQTT:Channel has changed! Publishing 2 to channel 3 
Info:MAIN:Time 17, idle 66408/s, free 69496, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38 POWERSAVE
Info:MAIN:Time 18, idle 71317/s, free 69496, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38 POWERSAVE


    Added after 11 [minutes]:

    Any suggestions on how to keep it up and running while troubleshooting?
    I can't find why it still wants to install the CHT8305 driver. It's not in the autoexec-file...
  • #10 21806580
    divadiow
    Level 38  
    nickejonsson wrote:
    I can't find why it still wants to install the CHT8305 driver. It's not in the autoexec-file..

    it could be set in startup commands

    “Change Startup Command Text” button and software version details
  • ADVERTISEMENT
  • #11 21806590
    nickejonsson
    Level 3  
    Yep!
    Can I just remove everything from there, or should I just remove that specific part?
    Screen showing startup command configuration for OpenBK7231N device
  • #12 21806599
    divadiow
    Level 38  
    get rid of it all. any parts you want to keep, like ntp and powersave, can go into autoexec
  • #13 21806604
    nickejonsson
    Level 3  
    Alright. So, I tried Google Geminis suggestion:

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

// dpID 1 = temperature (value is 10x, so 200 => 20.0C)
setChannelType 1 temperature_div10
linkTuyaMCUOutputToChannel 1 val 1

// dpID 2 = humidity %
setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 2 val 2

// dpID 3 = battery state enum: low(0), mid(1), high(2)
setChannelType 3 ReadOnlyLowMidHigh
setChannelLabel 3 Battery
linkTuyaMCUOutputToChannel 3 enum 3


    And managed to get some readings that actually looked correct. Then I removed everything in "Change Startup Command Text" and now I don't get any readings again. Since it couldn't start the CHT8305 driver I'm guessing that's not the reason but what about the rest:
    Code: text Expand Select all Copy to clipboard
     backlog PowerSave 1; startDriver battery; startDriver NTP; 
    ?

    Added after 8 [minutes]:

    Alright, I added
    Code: text Expand Select all Copy to clipboard
    startdriver battery
    and
    Code: text Expand Select all Copy to clipboard
    startdrive NTP
    together with the code from Gemini, to the autoexec file and removed everything from the "Change Startup Command" and everything seems to work now. It also looks like I don't need the
    Code: text Expand Select all Copy to clipboard
    backlog PowerSave 1
    (which I expect puts it to sleep between updates) 'cause I seem to have lost connection to it again...?

    Added after 1 [hours]:

    Just wanted to let everyone know that it works now. Thank you for all your help!

    My complete autoexec looks like this now:
    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU
startDriver tmSensor
//backlog PowerSave 1
startDriver battery
startDriver NTP
tuyaMcu_defWiFiState 4

// dpID 1 = temperature (value is 10x, so 200 => 20.0C)
setChannelType 1 temperature_div10
linkTuyaMCUOutputToChannel 1 val 1

// dpID 2 = humidity %
setChannelType 2 Humidity
linkTuyaMCUOutputToChannel 2 val 2

// dpID 3 = battery state enum: low(0), mid(1), high(2)
setChannelType 3 ReadOnlyLowMidHigh
setChannelLabel 3 Battery
linkTuyaMCUOutputToChannel 3 enum 3
Reply | New topic
Report a violation of the law

Topic summary

The discussion focuses on configuring the Tuya TH11 temperature and humidity sensor, which integrates a CB3S microcontroller and a CHT8310 sensor. The main challenge is obtaining sensor readings using OpenBeken firmware, specifically version OpenBK7231N_QIO_1.18.245.bin. Attempts to use the TuyaMCU driver yield only heartbeat signals (55AA0003...), while the CHT83XX driver fails to produce data despite testing various pin configurations. Wiring includes soldered jumper wires connected to RX, TX, VDD, and BAT- pins. The user seeks successful pin assignments and an autoexec.bat configuration to enable proper sensor communication and data acquisition.
Summary generated by the language model.
Today's popular
ADVERTISEMENT