OpenBK on CurryCurry Gen5.3 Curtain Switch with CB3S and TuyaMCU (PY32F003)

HansWorst7 450 19

#1 21616797 25 Jul 2025 14:57

HansWorst7 HansWorst7

Level 3

Post #1

21616797 25 Jul 2025 14:57

Hello,

I need help finalizing my device.

I have a few CurryCurry Gen5.3 Curtain switches running in my home and for me, it was time to move on from Tuya.

After a bit of research, I noticed the device has a CB3S chip and a TuyaMCU (Puya PY32F003).

Since we have a TuyaMCU, we need to cut the connections of TX and RX between it and the CB3S. I did that and managed to flash OpenBK.
The only setting the BK7231 Easy UART Flasher was able to read was a baud rate of 9600.

After finishing, I resoldered everything again, though I did kind of a sloppy job (I'm terrible at soldering)..

Still, I managed to boot the device and got onto the OpenBK UI.

In the logs of the web application, I managed to read out the physical buttons of the device, which are connected to the TuyaMCU, using startDriver TuyaMCU.
For the logging, I ran a basic "Curtains down - Curtains stop - Curtains up" sequence. This is the result of the log:


Info:TuyaMCU:Received: 55 AA 03 07 00 05 01 04 00 01 02 16 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 1 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 2
Info:TuyaMCU:Received: 55 AA 03 07 00 05 65 01 00 01 00 75 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 101 type 1-bool len 1
Info:TuyaMCU:ParseState: byte 0
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 63 7C 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 99
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 62 7B 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 98
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 61 7A 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 97
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 60 79 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 96
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 5F 78 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 95
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 5E 77 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 94
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 5D 76 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 93
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 5C 75 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 92
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 5B 74 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 91
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 5A 73 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 90
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 59 72 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 89
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 58 71 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 88
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 57 70 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 87
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 56 6F 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 86
Info:TuyaMCU:Received: 55 AA 03 07 00 05 01 04 00 01 01 15 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 1 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 1
Info:TuyaMCU:Received: 55 AA 03 07 00 05 65 01 00 01 01 76 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 101 type 1-bool len 1
Info:TuyaMCU:ParseState: byte 1
Info:TuyaMCU:Received: 55 AA 03 07 00 05 01 04 00 01 01 15 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 1 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 1
Info:TuyaMCU:Received: 55 AA 03 07 00 05 65 01 00 01 01 76 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 101 type 1-bool len 1
Info:TuyaMCU:ParseState: byte 1
Info:TuyaMCU:Received: 55 AA 03 07 00 05 01 04 00 01 00 14 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 1 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 0
Info:TuyaMCU:Received: 55 AA 03 07 00 05 65 01 00 01 00 75 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 101 type 1-bool len 1
Info:TuyaMCU:ParseState: byte 0
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 57 70 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 87
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 58 71 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 88
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 59 72 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 89
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 5A 73 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 90
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 5B 74 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 91
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 5C 75 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 92
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 5D 76 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 93
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 5E 77 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 94
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 5F 78 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 95
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 60 79 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 96
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 61 7A 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 97
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 62 7B 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 98
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 63 7C 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 99
Info:TuyaMCU:Received: 55 AA 03 07 00 08 02 02 00 04 00 00 00 64 7D 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 15
Info:TuyaMCU:ParseState: id 2 type 2-val len 4
Info:TuyaMCU:ParseState: int32 100
Info:TuyaMCU:Received: 55 AA 03 07 00 05 01 04 00 01 01 15 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 1 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 1
Info:TuyaMCU:Received: 55 AA 03 07 00 05 65 01 00 01 01 76 
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12
Info:TuyaMCU:ParseState: id 101 type 1-bool len 1
Info:TuyaMCU:ParseState: byte 1

What I can read from that is:

Quote:
Info:TuyaMCU:ParseState: id 1 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 2

dpId 1 is a type 4 - enum and was set to 2. This is most likely the button press for "curtains down", which is on channel 1 and the value that was written is 2.

Quote:
Info:TuyaMCU:ParseState: id 1 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 1

dpId 1 was now set to enum val 1, which should be the "stop" button.

Quote:
Info:TuyaMCU:ParseState: id 1 type 4-enum len 1
Info:TuyaMCU:ParseState: byte 0

dpId 1 was set to val 0 - I would say this means up.

There are a few other parameters like dpId2 which is most likely the percentage of the position (100 - open, 0 - closed) and another boolean type dpId 101 which I have no idea yet what this is for.

Anyway, using this information and getting the example from the CurrySmarter Gen6 Curtain switch (https://www.elektroda.com/rtvforum/topic4046987.html#21033819) I tried writing my own autoexec.bat:


PowerSave 1

startDriver TuyaMCU
tuyaMcu_defWiFiState 4

# Channel 1: Touch buttons (0=Open, 1=Stop, 2=Close)
setChannelType 1 textfield
setChannelLabel 1 "Touch buttons (0=Open 1=Stop 2=Close)"
setChannelVisible 1 false
linkTuyaMCUOutputToChannel 1 4 1 

startDriver httpButtons

setButtonEnabled 0 1
setButtonColor 0 "#2596be"
setButtonLabel 0 "Up/Open"
setButtonCommand 0 "setChannel 1 0"  # up

setButtonEnabled 1 1
setButtonColor 1 "#abdbe3"
setButtonLabel 1 "Stop/Pause"
setButtonCommand 1 "setChannel 1 1"  # stop

setButtonEnabled 2 1
setButtonColor 2 "#2596be"
setButtonLabel 2 "Down/Close"
setButtonCommand 2 "setChannel 1 2"  # down

Unfortunately, this does not work, no reaction whatsoever from the web UI. I would need help starting here. Any help would be appreciated.

ADVERTISEMENT
#2 21616821 25 Jul 2025 15:32

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #2
21616821 25 Jul 2025 15:32

So, with current config, commands like setChannel 1 0, or setChannel 1 2, give no reaction from device?

Hmm, are you sure that this enumeration you're using, dpID 1, is writeable? Your approach will not work if this dpID is read only, i.e. it's used only by TuyaMCU to report the state to the cloud, and NOT to control the state from the cloud.

Maybe you should try writing some of the other dpIDs.

Apart from that, your setup looks more or less okay... your baud setting and connection to MCU is okay, since you managed to received data. So no error here.

Interesting issue, I must admit. Would you be able to share your Tuya config partition, as downloaded from Web App?

@divadiow may also look here

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
ADVERTISEMENT
#3 21616830 25 Jul 2025 15:48

divadiow divadiow

Level 35

Helpful post? (0)

Post #3
21616830 25 Jul 2025 15:48
#4 21616836 25 Jul 2025 15:56

HansWorst7 HansWorst7

Level 3
Topic author Helpful post? (0)

Post #4
21616836 25 Jul 2025 15:56

Thank you for your quick replies.

Here's the TuyaConfig.

This is actually a good idea that dpID1 is RO. I might have to do some per-hand debugging throughout more channels.

Attachments:

BK7231N_TuyaConfig_obk1FE8955E.bin Download (72 KB)
ADVERTISEMENT
#5 21616846 25 Jul 2025 16:16

divadiow divadiow

Level 35

Helpful post? (0)

Post #5
21616846 25 Jul 2025 16:16

Code: JSON
Log in, to see the code
#6 21616851 25 Jul 2025 16:32

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home
Helpful post? (0)

Post #6
21616851 25 Jul 2025 16:32

Well it says RW...

Ok maybe, just for a test, you can check if you can control backlight?
Code: text Expand Select all Copy to clipboard
{ "abilityId": 7, "accessMode": "rw", "code": "switch_backlight", "name": "背光开关 (Backlight Switch)", "desc": "", "desc_en": "", "typeSpec": { "type": "bool" } },

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#7 21618254 27 Jul 2025 13:05

HansWorst7 HansWorst7

Level 3
Topic author Helpful post? (0)

Post #7
21618254 27 Jul 2025 13:05

I have tried doing this but also to no avail.

I noticed something strange though. I set the logs to ExtraDebug and get the heartbeat_valid = 0 string
Code: text Expand Select all Copy to clipboard
ExtraDebug:TuyaMCU:TuyaMCU heartbeat_valid = 0, product_information_valid=0, self_processing_mode = 1, wifi_state_valid = 0, wifi_state_timer=0

I can however receive data from tuyaMcu to CB3S, so the baud rate should be correct if I'm not wrong. Is it possible that it is the soldering after all?
If I have more time on my hands, I could try to resolder everything properly.
#8 21618258 27 Jul 2025 13:07

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #8
21618258 27 Jul 2025 13:07

Try running tuyaMcu_sendQueryState command in commandline to ask TuyaMCU for current state and check if you are getting replies

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
ADVERTISEMENT
#9 21618262 27 Jul 2025 13:10

HansWorst7 HansWorst7

Level 3
Topic author Helpful post? (0)

Post #9
21618262 27 Jul 2025 13:10

>>21618258

Code: text Expand Select all Copy to clipboard
Debug:API:POST to api/cmnd Debug:CMD:cmd [tuyaMcu_sendQueryState ] Info:CMD:[WebApp Cmd 'tuyaMcu_sendQueryState ' Result] OK

This is all I get.
#10 21618265 27 Jul 2025 13:12

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #10
21618265 27 Jul 2025 13:12

You should get lots of new dpID updates after executing that. dpIDs, types and their current values.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#11 21618269 27 Jul 2025 13:14

HansWorst7 HansWorst7

Level 3

Topic author Helpful post? (0)

Post #11
21618269 27 Jul 2025 13:14

>>21618265

Thank you for your help. I think CB3S TX -> TuyaMCU RX may have a cold solder joint. I will redo it properly and report back.
#12 21618273 27 Jul 2025 13:15

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #12
21618273 27 Jul 2025 13:15

It seems likely now, please check this contact. Check continunity with a multimeter.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#13 21618584 27 Jul 2025 18:40

PSlowik PSlowik

Level 12

» | Helpful post? (0)

Post #13
21618584 27 Jul 2025 18:40

I have similar roller shutter controllers, do you know how to set the pin settings? and is it possible to adjust the operating time?
#14 21618591 27 Jul 2025 18:43

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Helpful post? (0)

Post #14
21618591 27 Jul 2025 18:43

This is a device from TuyaMCU. Here you do not set the pins. You only have to write autoexec.bat to make the variables from the MCU available on the OBK panel and beyond.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#15 21618598 27 Jul 2025 18:47

PSlowik PSlowik

Level 12
» | Helpful post? (0)

Post #15
21618598 27 Jul 2025 18:47

from post 1? I don't want to be left without working blinds

I have just taken apart the controller and do not see the PY32 :/

Attachments:

2315CC73-3007-402E-9CA0-E7361EB86F89_4_5005_c.jpeg Download (102.88 KB)

3A3840B5-67D3-4087-8861-15F0CEEA5BAE_4_5005_c.jpeg Download (110.03 KB)
#16 21618618 27 Jul 2025 19:03

HansWorst7 HansWorst7

Level 3

Topic author Helpful post? (0)

Post #16
21618618 27 Jul 2025 19:03

Yes, it was indeed the soldering. I did a quick fix for that and now the backlight controls work like a charm! I will write a short summary once I'm done with the full setup (most likely tomorrow).
The only other thing that's left for me to figure out is why the "Curtains Up" LED keeps blinking.
#17 21618625 27 Jul 2025 19:05

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #17
21618625 27 Jul 2025 19:05

The pairing LED may be blinking if you don't force WiFi state 0x04 (connected to internet and to the cloud).

Do you need any special channel types or enumerations for your device? I can help with adding new things to OBK.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#18 21619115 28 Jul 2025 10:52

HansWorst7 HansWorst7

Level 3
Topic author Helpful post? (0)

Post #18
21619115 28 Jul 2025 10:52

Thanks, setting wifistate was the correct way to solve this.

I have yet 2 other strange issues on hand.

For one, I can only set dpID 1 to 0 (up), OBK doesn't do anything when I try to set it to 1 or 2 (pause and down).

So, using setChannel 1 2 or setChannel 1 1 does not provide any output from TuyaMCU.
Using setChannel 1 0 always gives me the correct output:
Code: text Expand Select all Copy to clipboard
Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12 Info:TuyaMCU:ParseState: id 1 type 4-enum len 1 Info:TuyaMCU:ParseState: byte 0 Info:TuyaMCU:Received: 55 AA 03 07 00 05 01 04 00 01 01 15 Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12 Info:TuyaMCU:ParseState: id 1 type 4-enum len 1 Info:TuyaMCU:ParseState: byte 1 Info:TuyaMCU:Received: 55 AA 03 07 00 05 65 01 00 01 01 76 Info:TuyaMCU:ProcessIncoming[v=3]: cmd 7 (State) len 12 Info:TuyaMCU:ParseState: id 101 type 1-bool len 1 Info:TuyaMCU:ParseState: byte 1

As I said, using setChannel 1 1 or setChannel 1 2 does not provide any output (and doesn't do anything to the curtain).
Using the percentage control with channel 2 does also work.

Then, the communication seems a bit flaky overall. Sometimes I have to use setChannel 3 or 4 times before the curtains start. I'm not sure if there is an internal signal on TuyaMCU that blocks communication for a while after getting a command. Maybe someone here knows more about these issues.

EDIT: Today I did some new tests.

- Percentage values only work with <1 for close and any other value for open. Integers do not work (e.g. setChannel 2 80). I have no idea how to use this properly because I would think you just give it the integer value from 0 to 100 which will translate into a percentage value.
Code: text Expand Select all Copy to clipboard
{ "abilityId": 2, "accessMode": "rw", "code": "percent_control", "name": "一路百分比控制 (Curtain Channel 1 Percent Control)", "desc": "", "desc_en": "", "typeSpec": { "type": "value", "max": 100, "min": 0, "scale": 0, "step": 1, "unit": "%" } },

- Opening and closing the curtains now works fine with setChannel 1 0 and setChannel 1 2. Stopping midway is done using setChannel 101 1. I now used "toggle" but there has to be a better channeltype for this (like, firing the stop button). Until then I will probably use the textfield and just always set it to 1 when used.

#19 21657634 09 Sep 2025 12:27

mvz0209 mvz0209

Level 5

Post #19

21657634 09 Sep 2025 12:27

Hello! I have a tuya electric curtain with the following motors:

I used to use esphome firmware, and with it, these motors work in home assistant. But I want to flash it in openbeken. Inside is a WBR3 chip. I desoldered it and soldered a CB3S. Now I get the opening percentage and can close and pause with the buttons, but the opening doesn't work for me. I am aware of the tuya msu commands

deciphered

Added after 1 [minutes]:

// Start NTP Driver
startDriver NTP
// Set NTP Server
ntp_setServer 194.190.168.1
// Set timezone
ntp_timeZoneOfs  7:00
startDriver TuyaMCU

tuyaMcu_defWiFiState 4

setChannelType 1 TextField
setChannelLabel 1 "Touch buttons (0=Open 1=Stop 2=Close)"
setChannelVisible 1 true


setChannelType 2 ReadOnly
setChannelLabel 2 "Procent otkr"


setChannelType 3 Percent
setChannelLabel 3 "zadanie"

setChannelType 4 ReadOnly

linkTuyaMCUOutputToChannel 1 enum 1


linkTuyaMCUOutputToChannel 3 val 2
linkTuyaMCUOutputToChannel 2 val 3


//55aa 00 06 00 05 01 04 000 100

startDriver httpButtons

setButtonEnabled 0 1


setButtonColor 0 "#2596be"

setButtonLabel 0 "Up/Open"

setButtonCommand 0 "setChannel 1 0"  # up

setButtonEnabled 1 1
setButtonColor 1 "#abdbe3"
setButtonLabel 1 "Stop/Pause"
setButtonCommand 1 "setChannel 1 1"  # stop

setButtonEnabled 2 1
setButtonColor 2 "#2596be"
setButtonLabel 2 "Down/Close"
setButtonCommand 2 "setChannel 1 2"  # down

#20 21658799 10 Sep 2025 12:11

mvz0209 mvz0209

Level 5

Helpful post? (0)

Post #20
21658799 10 Sep 2025 12:11

Success, sending to UART, added checksum
addEventHandler OnChannelChange 4 uartSendHex 55AA00060005010400010010 # up
addEventHandler OnChannelChange 5 uartSendHex 55AA00060005010400010111 # stop
addEventHandler OnChannelChange 6 uartSendHex 55AA00060005010400010212 # down
Create an account, log in here. You will receive points by participating in discussions.
Join this discussion.

Install Elektroda application

Didn't find an answer? Ask Artificial Intelligence

*I agree to send the question to OpenAI, Anthropic PBC, Perplexity AI, Inc., Kagi Inc., Google LLC - owners of language models in order to prepare the best response. The companies may monitor and log information entered into the form.

*I agree to publicly display my question and answer. The question and answer will be publicly available to everyone. The process may take a few minutes. Upon completion, you will be redirected to the page with the answer.

Wait...(2min)

Reply | New topic

Report a violation of the law

Topic summary

The discussion focuses on integrating OpenBK firmware on CurryCurry Gen5.3 curtain switches equipped with a CB3S chip and a TuyaMCU (Puya PY32F003). The user disconnected the TX and RX lines between the TuyaMCU and CB3S to flash OpenBK, successfully establishing communication at 9600 baud. However, commands targeting dpID 1 (curtain control) showed no effect, raising the possibility that dpID 1 is read-only and used solely for state reporting by the TuyaMCU. The shared Tuya configuration JSON reveals multiple properties with read-write access, including curtain control (enum: open, continue, close), percent control (0-100%), calibration, and backlight switch (boolean). Testing control commands on other dpIDs, such as the backlight switch (abilityId 7), is suggested to verify write capabilities. The setup and baud rate appear correct, but further manual debugging of dpIDs is recommended to achieve full device control under OpenBK.
Summary generated by the language model.

Home page
/
Forum
/
Smart Home
/
Smart Home IoT
/
OpenBK on CurryCurry Gen5.3 Curtain Switch with CB3S and TuyaMCU (PY32F003)

FAQ

TL;DR: Set WiFi state to 0x04 to stop the pairing LED blink; "The pairing LED may be blinking if you don't force WiFi state 0x04." This FAQ helps OpenBK users map DPIDs, fix UART issues, and control curtains without Tuya cloud. [Elektroda, p.kaczmarek2, post #21618625]

Why it matters: It shows how to make a CurryCurry Gen5.3 (CB3S+TuyaMCU) fully local with OpenBK, from wiring to commands.

Quick Facts

- Hardware: Tuya CB3S Wi‑Fi module + TuyaMCU (Puya PY32F003) under the glass touch panel. [Elektroda, HansWorst7, post #21616797]
- UART speed: 9600 bps detected by BK7231 Easy UART Flasher and used for TuyaMCU logs. [Elektroda, HansWorst7, post #21616797]
- DP map: control(enum), percent_control(0–100, step 1), switch_stop(bool). [Elektroda, divadiow, post #21616846]
- Calibration: cur_calibration enum supports start and end sequences. [Elektroda, divadiow, post #21616846]
- LED blink fix: Force WiFi state 0x04 (connected) in OpenBK to stop pairing LED flashing. [Elektroda, p.kaczmarek2, post #21618625]

What hardware is inside the CurryCurry Gen5.3 curtain switch?

It uses a Tuya CB3S (BK7231) Wi‑Fi module and a TuyaMCU based on the Puya PY32F003. The touch keys wire to the TuyaMCU, while the CB3S exchanges commands with it over UART. Knowing this helps you configure OpenBK by mapping Tuya datapoints rather than GPIOs. [Elektroda, HansWorst7, post #21616797]

What UART baud rate should I set for TuyaMCU on this device?

Set 9600 bps. BK7231 Easy UART Flasher detected 9600, and OpenBK received TuyaMCU packets at that speed. Keep TX and RX wiring short and clean for reliable frames. [Elektroda, HansWorst7, post #21616797]

How do I stop the "Curtains Up" LED flashing after flashing OpenBK?

Force Tuya Wi‑Fi state to 0x04 (connected). Add tuyaMcu_defWiFiState 4 in autoexec or run it via the console. This stops pairing-mode blinking without cloud, and keeps status LEDs consistent after reboots. [Elektroda, p.kaczmarek2, post #21618625]

Which DPIDs control open/close/stop and percentage?

Use setChannel 1 0 to open and setChannel 1 2 to close. Use setChannel 101 1 to stop. For positioning, send setChannel 2 with a percent after calibration. The user confirmed this mapping once UART was fixed. [Elektroda, HansWorst7, post #21619115]

tuyaMcu_sendQueryState returns OK, but I see no dp updates. What’s wrong?

Outbound UART likely fails. A cold solder joint on CB3S TX to TuyaMCU RX blocked outgoing frames. After reflowing CB3S TX, communication and backlight control worked immediately. Symptom: you receive Tuya frames, but the MCU ignores your commands. [Elektroda, HansWorst7, post #21618618]

How can I quickly test and restore TuyaMCU communication?

Reflow CB3S TX→MCU RX and CB3S RX→MCU TX pads.
Verify continuity with a multimeter.
In the OBK console, run tuyaMcu_sendQueryState and confirm dpID updates. "You should get lots of new dpID updates after executing that." [Elektroda, p.kaczmarek2, post #21618265]

Do I need to set GPIO pins in OpenBK for this curtain switch?

No. This is a TuyaMCU device, so you don’t assign GPIOs for relays or keys. Expose Tuya datapoints in OpenBK and operate via channels or MQTT. Configure autoexec to link DPIDs and present controls in the UI. [Elektroda, p.kaczmarek2, post #21618591]

Can I calibrate endpoints or adjust travel time?

Yes. Use dpID 3 (cur_calibration) with enum values start and end to calibrate endpoints. The schema exposes five DPIDs (1, 2, 3, 7, 101) covering control, percent, calibration, backlight, and stop. Run calibration before relying on percentage control. [Elektroda, divadiow, post #21616846]

What setChannel commands should I use day to day?

Open: setChannel 1 0. Close: setChannel 1 2. Stop: setChannel 101 1. For position, send setChannel 2 with a desired percentage after calibration. These commands worked reliably once UART wiring was corrected. [Elektroda, HansWorst7, post #21619115]

Commands only work after several tries. How do I stabilize it?

Intermittent control suggests marginal UART connections. Reinspect and reflow TX/RX joints, then verify continuity. Users reported needing 3–4 attempts before movement when wiring was suspect. Fixing solder integrity improved reliability. [Elektroda, HansWorst7, post #21619115]

How do I control the backlight LED from OpenBK?

Map dpID 7 (switch_backlight), a RW boolean, to a channel in OpenBK. Toggle that channel in the UI or via MQTT to switch the backlight. This is also a quick sanity check for bidirectional UART after repairs. [Elektroda, divadiow, post #21616846]

How can I read the panel’s physical button presses in OpenBK?

Start the TuyaMCU driver in OpenBK. The log prints dpID updates when you press Down, Stop, or Up. Use these events to discover enum values and confirm correct linking before scripting actions. [Elektroda, HansWorst7, post #21616797]

OpenBK on CurryCurry Gen5.3 Curtain Switch with CB3S and TuyaMCU (PY32F003)

Didn't find an answer? Ask Artificial Intelligence

Topic summary