logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Tuya Wi-Fi Thermostat DTC2201 - problem pairing with cloud via WBR1

GAAD 378 6
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Reply | New topic
  • #1 21366515
    GAAD
    Level 17  
    Hello.
    Is it possible to do anything with the WBR1 module? Is it possible to upload an OBK? I have such thermostats for controlling underfloor heating. They are convenient because they also work without the cloud. This piece theoretically works, it has lost communication with the cloud and I cannot add it again. It turns on the pairing, the Tuya app detects it, but before it manages to add it to the cloud the pairing mode shuts down and the operation fails.

    There are integrated circuits under the display, probably one of them is an MCU. After removing the display board and MCU, the WBR1 pins are free.

    Electronic thermostat with a display showing 25 degrees Celsius, an antenna, and buttons. Electronic module with a display and buttons. Electronic module with exposed circuit board containing integrated circuits and connectors. Close-up of a circuit board with a WBR1 module, antenna, and wired connector. WBR1 module on a circuit board with visible electronic components and pins. Close-up of a circuit board with a WBR1 module, antenna, and wired connector. WBR1 module on a circuit board with visible electronic components and pins.
  • ADVERTISEMENT
  • #2 21369023
    GAAD
    Level 17  
    I took the display out to see what was underneath.
    HC32F005C6PA - I think that would be the MCU, and 74HC595D - that's the driver for the display.

    Printed circuit board with electronic components on a pink background. .

    The cloud connection issue is also now cleared up, my WBR1 is faulty as it gets a 5V supply. I converted the DS18B20 power supply to 5 volts because the controller is in the boiler room, and the DS18B20 sensor itself on a long cable and at 3.3 volts was reporting errors - I didn't notice that by hooking up the DS to 5 volts I was also powering the WBR. It worked like this for over a year. The question is whether it is possible to replace the WBR1 with something?
  • ADVERTISEMENT
  • #3 21371186
    GAAD
    Level 17  
    Instead of the WBR1, I connected a Wi-Fi module removed from another Tuya device.
    OBK uploaded.
    It seems to me that the WBR1 itself is only used here for communication, it only has power, Rx, Tx for communication with MCU and EN connected.
    OBK configuration:
    Code: text Expand Select all Copy to clipboard
    
startDriver NTP
ntp_setServer 192.168.1.253
waitFor NTPState 1
ntp_timeZoneOfs 1
startDriver TuyaMCU
startDriver tmSensor
setChannelType 3 temperature_div10
linkTuyaMCUOutputToChannel 3 val 3
    .

    OBK log for Tuya MCU:
    Code: text Expand Select all Copy to clipboard
    
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 F3 0D 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 243
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 F7 11 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 247
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 F5 0F 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 245
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 F3 0D 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 243
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 F1 0B 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 241
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 EE 08 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 238
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 EC 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 236
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 EB 05 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 235
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 E9 03 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 233
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 E7 01 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 231
    .

    That is, the temperature measurement works, it even displays itself correctly in the HA.
    The thermostat itself "in manual mode" too.
    Is there any chance to refine the commands to make it a fully functional thermostat in HA?

    Thermostat test configuration page with temperature and connection information. .
    Home Assistant user interface displaying thermostat BK7231N information
  • ADVERTISEMENT
  • #4 21372234
    GAAD
    Level 17  
    Unfortunately, I won't embrace it myself, is there a chance to make it into a thermostat in HA?

    MCU works. The thermostat itself has 4 parameters to configure from the keypad:
    F1; temperature setpoint range -40 to 99.9 degrees precision 0.1 degrees
    F2: Hysteresis range 0.3 to 10 degrees precision 0.1 degree
    F3: Cooling delay range 1 to 10 minutes precision 1 minute
    F4: Temperature correction range -10 to +10 degrees precision 0,1 degree

    The MCU logs show that:
    channel 2 is the set temp value: parameter F1
    channel 3 current temperature
    channel 101 hysteresis parameter F2
    channel 102 cooling delay parameter F3
    channel 103 temperature correction parameter F4
    channel 14 heating relay status byte 1 - off byte 0 - on

    I have not been able to log the tripping of the cooling relay.

    Only channel two with the set temperature I managed to configure in OBK so that the value is visible and I can set it, only that without the decimal point, i.e. 25 degrees is the value 250.


    Excerpts from the logs:
    Code: text Expand Select all Copy to clipboard
    
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 184
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 B7 D0 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 183
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 B6 CF 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 182
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 B5 CE 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 181
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 B4 CD 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 180
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
Info:TuyaMCU:ParseState: id 101 type 2-val len 4
Info:TuyaMCU:ParseState: int32 13
Info:TuyaMCU:Received: 55 AA 03 07 00 08 65 02 00 04 00 00 00 0C 88 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 101 type 2-val len 4
Info:TuyaMCU:ParseState: int32 12
Info:TuyaMCU:Received: 55 AA 03 07 00 08 65 02 00 04 00 00 00 03 7F 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 101 type 2-val len 4
Info:TuyaMCU:ParseState: int32 3
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ParseState: id 102 type 2-val len 4
Info:TuyaMCU:ParseState: int32 5
Info:TuyaMCU:Received: 55 AA 03 07 00 08 66 02 00 04 00 00 00 06 83 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 102 type 2-val len 4
Info:TuyaMCU:ParseState: int32 6
Info:TuyaMCU:Received: 55 AA 03 07 00 08 66 02 00 04 00 00 00 07 84 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 102 type 2-val len 4
Info:TuyaMCU:ParseState: int32 7
Info:TuyaMCU:Received: 55 AA 03 07 00 08 66 02 00 04 00 00 00 0A 87 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 102 type 2-val len 4
Info:TuyaMCU:ParseState: int32 10
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ParseState: id 103 type 2-val len 4
Info:TuyaMCU:ParseState: int32 -8
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 D2 EC 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 210
Info:TuyaMCU:Received: 55 AA 03 07 00 08 67 02 00 04 FF FF FF F7 72 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 103 type 2-val len 4
Info:TuyaMCU:ParseState: int32 -9
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 D0 EA 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 208
Info:TuyaMCU:Received: 55 AA 03 07 00 08 67 02 00 04 FF FF FF F6 71 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 103 type 2-val len 4
Info:TuyaMCU:ParseState: int32 -10
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
Info:TuyaMCU:ParseState: id 14 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 1
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 F3 0D 
Info:TuyaMCU:ParseState: id 14 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 1
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 250
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 FA 13 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 250
Info:TuyaMCU:Received: 55 AA 03 07 00 05 0E 04 00 01 00 21 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 14 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 0
    .

    MCU also sows connection errors all the time:

    Code: text Expand Select all Copy to clipboard
    
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
Info:GEN:dhcp=0 ip=192.168.1.80 gate=192.168.1.1 mask=255.255.255.0 mac=1c:90:ff:cd:73:cd
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-70,ssid=SALON,bssid=10:fe:ed:76:04:0c,channel=6,cipher_type:Error
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 DB F5 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 219
Info:GEN:CHANNEL_Set channel 3 has changed to 219 (flags 0)
Info:TuyaMCU:Received: 55 AA 03 07 00 08 03 02 00 04 00 00 00 DA F4 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 3 type 2-val len 4
Info:TuyaMCU:ParseState: int32 218
Info:GEN:CHANNEL_Set channel 3 has changed to 218 (flags 0)
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
Info:GEN:dhcp=0 ip=192.168.1.80 gate=192.168.1.1 mask=255.255.255.0 mac=1c:90:ff:cd:73:cd
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-69,ssid=SALON,bssid=10:fe:ed:76:04:0c,channel=6,cipher_type:Error
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
Info:GEN:dhcp=0 ip=192.168.1.80 gate=192.168.1.1 mask=255.255.255.0 mac=1c:90:ff:cd:73:cd
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-69,ssid=SALON,bssid=10:fe:ed:76:04:0c,channel=6,cipher_type:Error
Info:TuyaMCU:Received: 55 AA 03 04 00 00 06 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 4 (WiFiReset) len 7
Info:TuyaMCU:ProcessIncoming: 0x04 replying
    .

    Could the cause be an unconnected EN?

    autoexec:
    Code: text Expand Select all Copy to clipboard
    
startDriver NTP
ntp_setServer 192.168.1.253
waitFor NTPState 1
ntp_timeZoneOfs 1
startDriver TuyaMCU
startDriver tmSensor
setChannelType 3 temperature_div10
linkTuyaMCUOutputToChannel 3 val 3
SetChannel 2 keywords
SetChannelLabel 2 "Temperatura zadana"
linkTuyaMCUOutputToChannel 2 val 2
GetChannel 2
SetChannel 4 keywords
SetChannelLabel 4 "Histereza"
linkTuyaMCUOutputToChannel 4 val 101
SetChannel 5 keywords
SetChannelLabel 5 "Cooling delay"
linkTuyaMCUOutputToChannel 5 val 102
SetChannel 6 keywords
SetChannelLabel 6 "Korekta temperatury"
linkTuyaMCUOutputToChannel 6 val 103
    .

    Thermostat configuration screen with channels and values. .

    Is it possible to configure channels above 100 to read/set these parameters via Wi-Fi? It is not necessary, but it may be possible.
    How to configure channel 14 to read the operating status of the heating relay?

    How to configure the OBK to report to the HA as a thermostat? Perhaps it would be possible to control it via BetterThermostat?
  • ADVERTISEMENT
  • #5 21373539
    GAAD
    Level 17  
    I have connected the WBR1 to ltchiptool the communication is there and therefore it is not faulty.
    However I can't read the memory because I don't have or don't know how to where the CEN is
    Code: text Expand Select all Copy to clipboard
    
== Rtl8710c IoT Platform ==
Chip VID: 5, Ver: 3
ROM Version: v3.0

== Boot Loader ==
Dec  5 2019:14:02:18

fwx SELE[fffffffc]
fw SELE Bitidx 2, fw1 valid 1, sn 0, fw2 valid 1, sn 1
fw1 USE, return sn 0

== Rtl8710c IoT Platform ==
Chip VID: 5, Ver: 3
ROM Version: v3.0

== Boot Loader ==
Dec  5 2019:14:02:18

fwx SELE[fffffffc]
fw SELE Bitidx 2, fw1 valid 1, sn 0, fw2 valid 1, sn 1
fw1 USE, return sn 0

Boot Loader <==

== RAM Start ==
Build @ 14:39:51, Mar 14 2022
interface 0 is initialized
interface 1 is initialized
[WIFI DEBUG]tuya[01-01 18:1_os_adapt_fl2:15 TUYA Iash_write er][lr:0x9b04r
[WIFI DEbd8b] mqc aBUG]get counpp init ...try code:0
[01-01 18:

Initia12:15 TUYA Ilizing WIFI][lr:0x9b057 ...4cb] thread_create name:sys_timer,stackDepth:4096,totalstackDepth:4096,priority:5
[01-01 18:12:15 TUYA I][lr:0x9b0574cb] thread_create name:cmmod,stackDepth:4096,totalstackDepth:8192,priority:4
[01-01 18:12:15 TUYA D][lr:0x9b04bcad] mq_pro:5 cnt:1
[01-01 18:12:15 TUYA D][lr:0x9b04bcad] mq_pro:31 cnt:2
[01-01 18:12:15 TUYA D][lr:0x9b0778eb] svc online log init success
[01-01 18:12:15 TUYA D][lr:0x9b057353] Thread:sys_timer Exec Start. Set to Running Stat
[01-01 18:12:15 TUYA D][lr:0x9b07047b] read m:2 f:0 l:1
[01-01 18:12:15 TUYA I][lr:0x9b0574cb] thread_create name:wk_th-0,stackDepth:5120,totalstackDepth:13312,priority:3
[01-01 18:12:15 TUYA E][lr:0x9b05b30f] wd_protected_read fails gw_bi -23
[01-01 18:12:15 TUYA D][lr:0x9b05b583] gw base read finish:-23
[01-01 18:12:15 TUYA D][lr:0x9b072d1f] ty bt cmmod regist ok:1
dev id key: 16
d4 1d 8c d9 8f 00 b2 04 e9 80 09 98 ec f8 42 7e 
[BT NOTICE]tuya_os_adapt_param_init mode:1
[BT DEBUG]tuya_os_adapt_bt_stack_init
[BT DEBUG]current_bt_mode:255, new bt_param->mode:1
[BT DEBUG]###init ble slave###
[01-01 18:12:15 TUYA D][lr:0x9b057353] Thread:cmmod Exec Start. Set to Running Stat
[01-01 18:12:15 TUYA D][lr:0x9b057353] Thread:wk_th-0 Exec Start. Set to Running Stat

WIFI initialized
[WIFI DEBUG]get country code:0

init_thread(65), Available heap 0x1BT BUILD Da71e8te: Mar 14 2022, 14:39:42 
BT RESET LOG...
read wifi mac:50:8b:b9:cd:98:08[BT NOTICE]BLE MAC: 0x50-0x8b-0xb9-0xcd-0x98-0x08
BT Reset ok
bt_iqk_efuse_valid: has data

hci_tp_phy_efuse[0]=0,
bt_dump_iqk:    DUMP,
the IQK_xx  data is 0x108,
the IQK_yy  data is 0x3f6,
the QDAC   data is 0x1e,
the IDAC   data is 0x1c,
the QDAC2  data is 0x20,
the IDAC2  data is 0x1d,
hci_read_rom_check: rom_version 0x0003, bt_hci_chip_id 0x0004

BT ADDRESS:
50:8b:b9:cd:98:08:

 WRITE  physical FLATK=tx_flatk=efff 

We use fw_buf=1002e008, fw_len = 1fb8, config_buf = 10012bd8, config_len= 32
Set baudrate to 921600

hci_tp_config:BT INIT success 7
Start upperStack

[BLE peripheral] GAP stack ready
[BT DEBUG]###init ble slave succ###
[01-01 18:12:15 TUYA N][lr:0x9b04868f] ble sdk re_inited
[01-01 18:12:15 TUYA D][lr:0x9b073711] bt active init
[01-01 18:12:15 TUYA N][lr:0x9b072e3b] ty bt sdk init success finish
[01-01 18:12:15 TUYA D][lr:0x9b01a2c3] < TUYA IOT SDK V:2.3.3 BS:40.00_PT:2.2_LAN:3.4_CAD:1.0.5_CD:1.0.0 >
< BUILD AT:2022_03_02_16_20_08 BY ci_manage FOR ty_iot_sdk AT rtl8720cf_ameba >
IOT DEFS < WIFI_GW:1 DEBUG:1 KV_FILE:0 SHUTDOWN_MODE:0 LITTLE_END:1 TLS_MODE:2 ENABLE_CLOUD_OPERATION:0 OPERATING_SYSTEM:2 ENABLE_SYS_RPC:0 RELIABLE_TRANSFER:0 ENABLE_LAN_ENCRYPTION:1 ENABLE_LAN_LINKAGE:0 ENABLE_LAN_DEV:0 >

[01-01 18:12:15 TUYA D][lr:0x9b01a2cd] rtl8720cf_common_user_config_ty:2.6.3
[01-01 18:12:15 TUYA N][lr:0x9b06e5fb] key_addr: 0x1d8000   block_sz 4096
[01-01 18:12:15 TUYA N][lr:0x9b06e683] get key:
0x63 0x68 0x68 0x2c 0x90 0x5 0x37 0xde 0x64 0x84 0xe3 0xd 0xec 0x49 0x2d 0x1d 
[01-01 18:12:15 TUYA N][lr:0x9b043a07] have actived over 15 min, not enter mf_init
[01-01 18:12:15 TUYA N][lr:0x9b0192d3] mf_init succ
    .

    maybe it would help to rework this thermostat?
  • #6 21374650
    GAAD
    Level 17  
    It works and I think it's the way I wanted it to but on ESPHome.
    I haven't configured cooling because I control the floor valves purely as heating.

    Home Assistant dashboard displaying temperature and heating data for various rooms. .

    This is what the log from ESP looks like when reading the MCU:
    Code: text Expand Select all Copy to clipboard
    
[02:20:26][C][tuya:041]: Tuya:
[02:20:26][C][tuya:056]:   Datapoint 1: switch (value: ON)
[02:20:26][C][tuya:058]:   Datapoint 2: int value (value: 205)
[02:20:26][C][tuya:058]:   Datapoint 3: int value (value: 229)
[02:20:26][C][tuya:062]:   Datapoint 14: enum (value: 1)
[02:20:26][C][tuya:064]:   Datapoint 13: bitmask (value: 0)
[02:20:26][C][tuya:058]:   Datapoint 101: int value (value: 3)
[02:20:26][C][tuya:058]:   Datapoint 102: int value (value: 600)
[02:20:26][C][tuya:058]:   Datapoint 103: int value (value: 0)
[02:20:27][C][tuya:074]:   Product: '{"p":"izsvppl83kwq3vu1","v":"1.0.0","m":2}'
    .
  • Helpful post
    #7 21375328
    p.kaczmarek2
    Moderator Smart Home  
    I have not seen this topic, WBR1 has been supported for a short time:
    WBR2, WBR3, WBRU, W701-VA2-CG pinout, data sheet, flashing for Home Assistant .

    You read the channels normally with the get/set themes:
    https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/mqttTopics.md
    if you want to have non-standard device handling in HA, you can manually write an entry in configuration.yaml and then script the whole thing as you wish.
    Helpful post? Buy me a coffee.
Reply | New topic
Report a violation of the law

Topic summary

The discussion addresses issues with pairing the Tuya Wi-Fi thermostat model DTC2201 to the cloud via the WBR1 Wi-Fi module. The WBR1 module was found to be faulty due to incorrect 5V power supply, causing loss of cloud communication. The thermostat MCU identified is an HC32F005C6PA, with a 74HC595D display driver. Attempts to replace the WBR1 with a Wi-Fi module from another Tuya device succeeded, allowing OBK firmware upload and communication via UART (power, Rx, Tx, EN pins). OBK configuration includes NTP and TuyaMCU drivers, enabling temperature and relay control channels. The thermostat parameters (setpoint, hysteresis, cooling delay, temperature correction) are accessible via MCU channels and can be integrated with Home Assistant (HA) or ESPHome for local control without cloud dependency. The WBR1 module uses the Rtl8710c IoT platform, but reading its memory is hindered by unknown CEN pin location. Community support references recent WBR1 support in OpenBK7231T firmware and MQTT topic usage for device integration in HA, suggesting manual configuration for non-standard devices.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT