HomeMate Wi-Fi + Bluetooth Smart 4 Gang Touch Switch

marioalmeida 12051 41

TL;DR

HomeMate Wi-Fi + Bluetooth Smart 4 Gang Touch Switch for Roma fitting uses a CB3S module with BK7231N and TuyaMCU control.
The switch stacks three soldered boards: touch/controller, relay board, and power board, with long header pins linking them together.
It exposes 12 dpIds and uses 4× 5A 230V relays, a ULN2003A Darlington array, and an HLK-PM01L power module.
OpenBK7231T firmware is installed by running TuyaMCU, mapping channels with autoexec.bat, then uploading the file, rebooting, and configuring MQTT.
Two datapoints remain unclear: Delay-off Schedule on dpId 19 and Memory Status on dpId 14.

Report a violation of the law

Reply Cool? Ranking DIY | New topic

Notify about new articles

📢 Listen (AI):

Topic author Helpful post? (+7)

Post #1
20103196 16 Jul 2022 04:27

Product information
Tuya 4 CH touch switch for Roma fitting for Indian homes, it has CB3S chip (BK7231N)

https://amzn.eu/d/3K8uk6I

Technical Specs
TuyaMCU: T1616-N TH 2720E (ATTINY1616)
Darlington transistor array ULN2003A
Relay: 5A 230V x 4
Power Module: HLK-PM01L

This switch consists of 3 board, soldered with long header pins,
Top board is the controller board, top side is with the touch buttons, and on the other side it has CB3S and TuyaMCU, after that, is the relay board and then the power board.

Total dpId 12
Code: text Expand Select all Copy to clipboard
0 Object { dpName: "Switch 1", dpId: 1 } 1 Object { dpName: "Switch 2", dpId: 2 } 2 Object { dpName: "Switch 3", dpId: 3 } 3 Object { dpName: "Delay-off Schedule", dpId: 19 } 4 Object { dpName: "Switch 4", dpId: 4 } 5 Object { dpName: "Timer 1", dpId: 7 } 6 Object { dpName: "Timer 2", dpId: 8 } 7 Object { dpName: "Test Bit", dpId: 24 } 8 Object { dpName: "Timer 3", dpId: 9 } 9 Object { dpName: "Timer 4", dpId: 10 } 10 Object { dpName: "Master Switch", dpId: 13 } 11 Object { dpName: "Memory Status", dpId: 14 }

Teardown

Prepare for firmware upload

download the latest firmware from https://github.com/openshwprojects/OpenBK7231T_App/releases/

Create autoexec.bat file with below content
Code: text Expand Select all Copy to clipboard
startDriver TuyaMCU setChannelType 1 toggle setChannelType 2 toggle setChannelType 3 toggle setChannelType 4 toggle setChannelType 13 toggle setChannelType 7 TextField setChannelType 8 TextField setChannelType 9 TextField setChannelType 10 TextField linkTuyaMCUOutputToChannel 1 1 1 linkTuyaMCUOutputToChannel 2 1 2 linkTuyaMCUOutputToChannel 3 1 3 linkTuyaMCUOutputToChannel 4 1 4 linkTuyaMCUOutputToChannel 7 2 7 linkTuyaMCUOutputToChannel 8 2 8 linkTuyaMCUOutputToChannel 9 2 9 linkTuyaMCUOutputToChannel 10 2 10 linkTuyaMCUOutputToChannel 13 1 13

After upload is done. open http://192.168.4.1/app, go to Filesystem and drop the autoexec.bat file in the "drop file(s) here" box, reboot the device, change the host-name, connect to the network, configure MQTT and start using the device with you home automation system.

Added after 7 [hours] 8 [minutes]:

@p.kaczmarek2 how to configure the below 2 dbId?
{ dpName: "Delay-off Schedule", dpId: 19 }
{ dpName: "Memory Status", dpId: 14 }

Cool? Ranking DIY
About Author
marioalmeida marioalmeida

Level 10
Offline

Joined: 05 Jan 2022

Posts: 47

Posts rating: 24

Points: 383
marioalmeida wrote 47 posts with rating 24. Been with us since 2022 year.

ADVERTISEMENT
#2 20548309 20 Apr 2023 12:13

parmarshailendra47 parmarshailendra47

Level 2

Helpful post? (0)

Post #2
20548309 20 Apr 2023 12:13

after flashing and finishing the config. toggles are visible but relays are not working. when pressed shoing below in log. but nothing happens to relay.
Info:MQTT:Channel has changed! Publishing 1 to channel 1
Info:MQTT:Publishing val 1 to TouchSwitch/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic TouchSwitch/1/get
Info:MQTT:MQTT in topic TouchSwitch/1/get
Info:MQTT:MQTT topic not handled: TouchSwitch/1/get
Info:MQTT:channelSet part topic 1/get
Info:MQTT:channelSet channel 1
Info:MQTT:channelSet NOT 'set'
Info:MQTT:Channel has changed! Publishing 1 to channel 2
Info:MQTT:Publishing val 1 to TouchSwitch/2/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic TouchSwitch/2/get
Info:MQTT:MQTT in topic TouchSwitch/2/get
Info:MQTT:MQTT topic not handled: TouchSwitch/2/get
Info:MQTT:channelSet part topic 2/get
Info:MQTT:channelSet channel 2
Info:MQTT:channelSet NOT 'set'
Info:MQTT:Channel has changed! Publishing 1 to channel 3
Info:MQTT:Publishing val 1 to TouchSwitch/3/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic TouchSwitch/3/get
Info:MQTT:MQTT in topic TouchSwitch/3/get
Info:MQTT:MQTT topic not handled: TouchSwitch/3/get
Info:MQTT:channelSet part topic 3/get
Info:MQTT:channelSet channel 3
Info:MQTT:channelSet NOT 'set'
Info:MQTT:Channel has changed! Publishing 1 to channel 4
Info:MQTT:Publishing val 1 to TouchSwitch/4/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic TouchSwitch/4/get
Info:MQTT:MQTT in topic TouchSwitch/4/get
Info:MQTT:MQTT topic not handled: TouchSwitch/4/get
Info:MQTT:channelSet part topic 4/get
Info:MQTT:channelSet channel 4
Info:MQTT:channelSet NOT 'set'

also some time the relays and switches working automatically like the below video.

Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 04 01 00 01 00 14
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 4, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte:
Info:MQTT:Channel has changed! Publishing 0 to channel 4
Info:MQTT:Publishing val 0 to TouchSwitch/4/get retain=0
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 02 01 00 01 00 12
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte:
Info:MQTT:Channel has changed! Publishing 0 to channel 2
Info:MQTT:Publishing val 0 to TouchSwitch/2/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic TouchSwitch/4/get
Info:MQTT:MQTT in topic TouchSwitch/4/get
Info:MQTT:MQTT topic not handled: TouchSwitch/4/get
Info:MQTT:channelSet part topic 4/get
Info:MQTT:channelSet channel 4
Info:MQTT:channelSet NOT 'set'
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic TouchSwitch/2/get
Info:MQTT:MQTT in topic TouchSwitch/2/get
Info:MQTT:MQTT topic not handled: TouchSwitch/2/get
Info:MQTT:channelSet part topic 2/get
Info:MQTT:channelSet channel 2
Info:MQTT:channelSet NOT 'set'
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 04 01 00 01 01 15
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 4, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte:
Info:MQTT:Channel has changed! Publishing 1 to channel 4
Info:MQTT:Publishing val 1 to TouchSwitch/4/get retain=0
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 04 01 00 01 00 14
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 4, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte:
Info:MQTT:Channel has changed! Publishing 0 to channel 4
Info:MQTT:Publishing val 0 to TouchSwitch/4/get retain=0
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 02 01 00 01 01 13
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte:
Info:MQTT:Channel has changed! Publishing 1 to channel 2
Info:MQTT:Publishing val 1 to TouchSwitch/2/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic TouchSwitch/4/get
Info:MQTT:MQTT in topic TouchSwitch/4/get
Info:MQTT:MQTT topic not handled: TouchSwitch/4/get
Info:MQTT:channelSet part topic 4/get
Info:MQTT:channelSet channel 4
Info:MQTT:channelSet NOT 'set'
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic TouchSwitch/4/get
Info:MQTT:MQTT in topic TouchSwitch/4/get
Info:MQTT:MQTT topic not handled: TouchSwitch/4/get
Info:MQTT:channelSet part topic 4/get
Info:MQTT:channelSet channel 4
Info:MQTT:channelSet NOT 'set'
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic TouchSwitch/2/get
Info:MQTT:MQTT in topic TouchSwitch/2/get
Info:MQTT:MQTT topic not handled: TouchSwitch/2/get
Info:MQTT:channelSet part topic 2/get
Info:MQTT:channelSet channel 2
Info:MQTT:channelSet NOT 'set'
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 04 01 00 01 01 15
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 4, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte:
Info:MQTT:Channel has changed! Publishing 1 to channel 4
Info:MQTT:Publishing val 1 to TouchSwitch/4/get retain=0
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 02 01 00 01 00 12
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 2, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte:
Info:MQTT:Channel has changed! Publishing 0 to channel 2
Info:MQTT:Publishing val 0 to TouchSwitch/2/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic TouchSwitch/4/get
Info:MQTT:MQTT in topic TouchSwitch/4/get
Info:MQTT:MQTT topic not handled: TouchSwitch/4/get
Info:MQTT:channelSet part topic 4/get
Info:MQTT:channelSet channel 4
Info:MQTT:channelSet NOT 'set'
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic TouchSwitch/2/get
Info:MQTT:MQTT in topic TouchSwitch/2/get
Info:MQTT:MQTT topic not handled: TouchSwitch/2/get
Info:MQTT:channelSet part topic 2/get
Info:MQTT:channelSet channel 2
Info:MQTT:channelSet NOT 'set'

Added after 1 [minutes]:

@marioalmeida
#3 20550626 22 Apr 2023 09:23

marioalmeida marioalmeida

Level 10

Topic author Helpful post? (0)

Post #3
20550626 22 Apr 2023 09:23

when you press the touch button, do you see normal functions?

Note:- OBK firmware will interact with the Tuya MCU and not directly with the relays. if there is any issue with the firmware, the touch buttons must work.
#4 20550637 22 Apr 2023 09:41

parmarshailendra47 parmarshailendra47

Level 2

Helpful post? (0)

Post #4
20550637 22 Apr 2023 09:41

Yes , all touch button is working normal and operate relay when pressed.
ADVERTISEMENT
#5 20552178 23 Apr 2023 14:56

marioalmeida marioalmeida

Level 10

Topic author Helpful post? (0)

Post #5
20552178 23 Apr 2023 14:56

Can you attached the device autoexec file?

#6 20574203 10 May 2023 07:06

parmarshailendra47 parmarshailendra47

Level 2

Post #6

20574203 10 May 2023 07:06

This is the content of autoexec.bat

Moderated By p.kaczmarek:
You have tuyaMcu_setBaudRate call before you startDriver TuyaMCU! The tuyaMcu_setBaudRate call will be ignored. Please be aware that you always have to start the driver first!

tuyaMcu_setBaudRate 115200

startDriver TuyaMCU

setChannelType 1 toggle
setChannelType 2 toggle
setChannelType 3 toggle
setChannelType 4 toggle
setChannelType 13 toggle

setChannelType 7 TextField
setChannelType 8 TextField
setChannelType 9 TextField
setChannelType 10 TextField

linkTuyaMCUOutputToChannel 1 1 1
linkTuyaMCUOutputToChannel 2 1 2
linkTuyaMCUOutputToChannel 3 1 3
linkTuyaMCUOutputToChannel 4 1 4
linkTuyaMCUOutputToChannel 7 2 7
linkTuyaMCUOutputToChannel 8 2 8
linkTuyaMCUOutputToChannel 9 2 9
linkTuyaMCUOutputToChannel 10 2 10
linkTuyaMCUOutputToChannel 13 1 13

#7 20721595 04 Sep 2023 22:53

DCG DCG

Level 6

Helpful post? (0)

Post #7
20721595 04 Sep 2023 22:53

Hey team, any further help in this device ? I have flashed OpenBK7231N via Tuya cloud cutter and now stuck...

@parmarshailendra47 any luck with this device ?
#8 20723802 06 Sep 2023 21:50

DCG DCG

Level 6

Helpful post? (+1)

Post #8
20723802 06 Sep 2023 21:50

Update - Switch is working fine and able to integrate with Home Assistant aswell

I just went thru the details in the OP again and followed the "autoexec.bat" instructions.

-- Open Web App
-- File System tab
-- Create a file (autoexec.bat) and click on the newly created autoexec.bat button
-- Copy & paste the entire code (startDriver TuyaMCU) mentioned in the OP on the right side dialog box
-- Click save & restart the device....

you are now all set and device will work fine... tested & confirmed. (working fine in Home Assistant)

the issue mentioned by @parmarshailendra47 seems to be a faulty device.
#9 20724508 07 Sep 2023 15:42

DCG DCG

Level 6

Helpful post? (0)

Post #9
20724508 07 Sep 2023 15:42

@p.kaczmarek2 I have a quick query regarding this device

Everything is perfectly working, I have noticed that the small Wifi Led on the switch keeps blinking even though its connected to Wifi..
Is there any settings that I need to change to stop the led blinking ?
#10 20725146 08 Sep 2023 02:04

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home
Helpful post? (+1)

Post #10
20725146 08 Sep 2023 02:04

If you have a TuyaMCU device, and it has a LED blinking, it means you need to either:
- connect to MQTT so OBK reports it's "connected to cloud" to TuyaMCU
- or add following line to autoexec.bat:
Code: text Expand Select all Copy to clipboard
tuyaMcu_defWiFiState 4

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 20725185 08 Sep 2023 07:08

DCG DCG

Level 6

Helpful post? (0)

Post #11
20725185 08 Sep 2023 07:08

Yes once connected to MQTT issue has been resolved, no more led blinking.

#12 20725234 08 Sep 2023 08:25

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Post #12

20725234 08 Sep 2023 08:25

If you want to totally disable led blinking, no matter the MQTT state, add the following line to autoexec.bat script:


tuyaMcu_defWiFiState 4

See the list of available WiFi states in TuyaMCU:

Network status	Description	Status value
Status 1	Pairing in EZ mode. (For Wi-Fi and Bluetooth LE combo module: Bluetooth is also in pairing mode.)	0x00
Status 2	Pairing in AP mode. (For Wi-Fi and Bluetooth LE combo module: Bluetooth is also in pairing mode.)	0x01
Status 3	The Wi-Fi network is set up, but the device is not connected to the router.	0x02
Status 4	The Wi-Fi network is set up, and the device is connected to the router.	0x03
Status 5	The device is connected to the cloud.	0x04
Status 6	Tuya’s network module is in low power mode.	0x05
Status 7	EZ mode and AP mode coexist. (For Wi-Fi and Bluetooth LE combo module: Bluetooth is also in pairing mode.)	0x06

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 20726451 08 Sep 2023 23:52

latocheski latocheski

Level 5

Post #13

20726451 08 Sep 2023 23:52

p.kaczmarek2 wrote:
If you want to totally disable led blinking, no matter the MQTT state, add the following line to autoexec.bat script:
Code: text Expand Select all Copy to clipboard
tuyaMcu_defWiFiState 4

Hello!

I set this property "tuyaMcu_defWiFiState 4" in my device which I recorded in my CB2S chip - BK7231N (autoexec.bat) but even so it keeps blinking.

I tested other values but without success. This is my complete .bat:


startDriver TuyaMCU

tuyaMcu_defWiFiState 4

setChannelType 1 toggle
setChannelType 2 toggle
setChannelType 3 toggle
setChannelType 4 toggle
setChannelType 5 toggle

setChannelLabel 5 "All"

linkTuyaMCUOutputToChannel 1 1 1
linkTuyaMCUOutputToChannel 2 1 2
linkTuyaMCUOutputToChannel 3 1 3
linkTuyaMCUOutputToChannel 4 1 4
linkTuyaMCUOutputToChannel 38 1 5

alias set_all_on backlog setChannel 1 1; setChannel 2 1; setChannel 3 1; setChannel 4 1;
alias set_all_off backlog setChannel 1 0; setChannel 2 0; setChannel 3 0; setChannel 4 0;
alias myToggle if $CH1||$CH2||$CH3||$CH4 then set_all_off else set_all_on
addEventHandler OnChannelChange 5 myToggle

Another problem that is happening is that I can turn on the buttons through MQTT or web interface but I can't turn off, I couldn't solve it in a simple way, but if I define this:



...
setChannelType 7 TextField
setChannelType 8 TextField
setChannelType 9 TextField
setChannelType 10 TextField
setChannelType 13 TextField

linkTuyaMCUOutputToChannel 7 2 7
linkTuyaMCUOutputToChannel 8 2 8
linkTuyaMCUOutputToChannel 9 2 9
linkTuyaMCUOutputToChannel 10 2 10
linkTuyaMCUOutputToChannel 13 1 13
...

it works, setting a value of "1" on the interface, unsuccessfully with MQTT/interface button.

The model in question is manufactured by NovaDigital, a Brazilian model. There is 4 touch buttons.

ADVERTISEMENT
#14 20726468 09 Sep 2023 00:24

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #14
20726468 09 Sep 2023 00:24

lucianolatochesk wrote:

I set this property "tuyaMcu_defWiFiState 4" in my device which I recorded in my CB2S chip - BK7231N (autoexec.bat) but even so it keeps blinking.

But everything else is working? Or maybe you are missing baud setting and there is no communication at all?

Disconnect power entirely from device and reconnect it.
lucianolatochesk wrote:

Another problem that is happening is that I can connect the buttons through MQTT or web interface but I can't disconnect, I couldn't solve it in a simple way, but if I define this:

If I understand you correctly, this is because you still have "Toggle" channel types if you open Web App, on the right column. Change those channel types manually back to default one and Toggles (buttons) from HTTP panel will disappear, unless you set them again in autoexec.

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 20726473 09 Sep 2023 00:33

latocheski latocheski

Level 5

Helpful post? (0)

Post #15
20726473 09 Sep 2023 00:33

p.kaczmarek2 wrote:
But everything else is working? Or maybe you are missing baud setting and there is no communication at all?

Sorry, i'll explain better:

The device works fine, i can turn on in the web interface and MQTT, but can't turn off. Only button back to the "off" state, the device not. I need to touch on the physical button to back off state.

Added after 2 [minutes]:

If I define some baud (tried: 115200, 921600 and 1500000), the buttons/MQTT doesn't work more.
like: "tuyaMcu_setBaudRate 115200"
#16 20726476 09 Sep 2023 00:36

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home
Helpful post? (0)

Post #16
20726476 09 Sep 2023 00:36

This is very strange.

Backup your config and try:
Code: text Expand Select all Copy to clipboard
startDriver TuyaMCU tuyaMcu_defWiFiState 4 setChannelType 1 toggle linkTuyaMCUOutputToChannel 1 1 1

The following code should allow you to both turn on and off the first relay... check it and tell me whether the bug persists.

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.
#17 20726488 09 Sep 2023 01:00

latocheski latocheski

Level 5

Helpful post? (0)

Post #17
20726488 09 Sep 2023 01:00

p.kaczmarek2 wrote:
check it and tell me whether the bug persists.

Unfortunately, same.
#18 20726589 09 Sep 2023 08:42

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #18
20726589 09 Sep 2023 08:42

Now, do the following steps:
1. open Web App -> Log
2. Disconnect all power from device
3. Clear log
4. Connect power to the device
5. Wait for it to connect to WiFi
6. Press the physical buttons several times (4+) on the device
7. Copy Web App log to file, clear Web App log
8. Press HTML GUI button several times (4+)
8. Copy Web App log to another file
Paste here the two logs. I want to see their content

Alternatively, do you have unflashed version of this device to do the UART capture with original Tuya firmware?

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.

#19 20727005 09 Sep 2023 15:10

latocheski latocheski

Level 5

Post #19

20727005 09 Sep 2023 15:10

p.kaczmarek2 wrote:
6. Press the physical buttons several times (4+) on the device

Ok, the first boot:
I switched the physical button more than 10 times but apparently there is no log


Info:MAIN:Main_Init_Before_Delay
Info:CFG:####### Boot Count 123 #######
Warn:CFG:CFG_InitAndLoad: Correct config has been loaded with 16 changes count.
Error:CMD:no file early.bat err -2
Info:GEN:PIN_SetupPins pins have been set up.
Info:MAIN:Main_Init_Before_Delay done
Info:MAIN:Main_Init_Delay
Info:MAIN:Main_Init_Delay done
Info:MAIN:Main_Init_After_Delay
Info:MAIN:Using SSID [edited]
Info:MAIN:Using Pass [edited]
Info:MQTT:MQTT_RegisterCallback called for bT homeassistant/ subT homeassistant/+/set
Info:MQTT:MQTT_RegisterCallback called for bT switch_/ subT switch_/+/set
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/homeassistant/ subT cmnd/homeassistant/+
Info:MQTT:MQTT_RegisterCallback called for bT cmnd/switch_/ subT cmnd/switch_/+
Info:MQTT:MQTT_RegisterCallback called for bT homeassistant/ subT homeassistant/+/get
Info:CMD:CMD_StartScript: started autoexec.bat at the beginning
Info:MAIN:Main_Init_After_Delay done
Info:MAIN:Started TuyaMCU.
Info:GEN:Channel 1 type changed to toggle
Info:MAIN:Time 1, idle 277551/s, free 76792, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 2, idle 186486/s, free 76792, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 3, idle 185606/s, free 76792, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 4, idle 187846/s, free 76792, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 5, idle 186611/s, free 76792, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 
Info:MAIN:ssid:HOME key:edited
Info:MAIN:Time 6, idle 177864/s, free 72064, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Boot complete time reached (5 seconds)
Info:CFG:####### Set Boot Complete #######
Info:MAIN:Time 7, idle 182073/s, free 71536, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 8, idle 83338/s, free 71848, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 9, idle 0/s, free 71848, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 10, idle 0/s, free 71848, MQTT 0(0), bWifi 0, secondsWithNoPing -1, socks 2/38 
Info:GEN:dhcp=0 ip=0.0.0.0 gate=0.0.0.0 mask=0.0.0.0 mac=fc:67:1f:42:77:08
Info:GEN:sta: 0, softap: 0, b/g/n
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTING - 1
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTED - 4
Info:MAIN:Time 11, idle 95493/s, free 71944, MQTT 0(0), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 12, idle 185199/s, free 71984, MQTT 0(0), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Main_OnWiFiStatusChange - WIFI_STA_CONNECTED - 4
Info:MQTT:mqtt_userName edited
mqtt_pass edited
mqtt_clientID homeassistant
mqtt_host 192.168.1.129:1883
Info:MAIN:Time 13, idle 183910/s, free 71880, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 14, idle 181398/s, free 71880, MQTT 0(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:mqtt_connection_cb: Successfully connected
Info:MQTT:mqtt_subscribed to homeassistant/+/set
Info:MQTT:mqtt_subscribed to switch_/+/set
Info:MQTT:mqtt_subscribed to cmnd/homeassistant/+
Info:MQTT:mqtt_subscribed to cmnd/switch_/+
Info:MQTT:mqtt_subscribed to homeassistant/+/get
Info:MQTT:Publishing val s4x to homeassistant/host retain=0
Info:MAIN:Time 15, idle 175169/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Publishing val Build on Sep  8 2023 14:40:34 version 1.17.240 to homeassistant/build retain=0
Info:MAIN:Time 16, idle 187681/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Publishing val fc:67:1f:42:77:08 to homeassistant/mac retain=0
Info:MAIN:Time 17, idle 186193/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Publishing val HOME to homeassistant/ssid retain=0
Info:MAIN:Time 18, idle 178860/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Publishing val 2 to homeassistant/sockets retain=0
Info:MAIN:Time 19, idle 187724/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Publishing val -75 to homeassistant/rssi retain=0
Info:MAIN:Time 20, idle 370713/s, free 71664, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 3/38 
Info:GEN:dhcp=0 ip=192.168.1.244 gate=192.168.1.254 mask=255.255.255.0 mac=fc:67:1f:42:77:08
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-75,ssid=HOME,bssid=d8:77:8b:02:48:91,channel=11,cipher_type:MIXED
Info:MQTT:Publishing val 20 to homeassistant/uptime retain=0
Info:MAIN:Time 21, idle 180223/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Publishing val 71880 to homeassistant/freeheap retain=0
Info:MAIN:Time 22, idle 181436/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Publishing val 192.168.1.244 to homeassistant/ip retain=0
Info:MAIN:Time 23, idle 184080/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Channel has changed! Publishing 0 to channel 1 
Info:MQTT:Publishing val 0 to homeassistant/1/get retain=0
Info:MAIN:Time 24, idle 185630/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MAIN:Time 25, idle 195836/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 26, idle 202410/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 27, idle 185536/s, free 71664, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 3/38 
Info:MAIN:Time 28, idle 373410/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 29, idle 188790/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 30, idle 183761/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:GEN:dhcp=0 ip=192.168.1.244 gate=192.168.1.254 mask=255.255.255.0 mac=fc:67:1f:42:77:08
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-68,ssid=HOME,bssid=d8:77:8b:02:48:91,channel=11,cipher_type:MIXED
Info:MAIN:Time 31, idle 183809/s, free 71456, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 3/38 
Info:MAIN:Time 32, idle 188952/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 33, idle 185805/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 34, idle 185560/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 35, idle 189167/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 36, idle 186778/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 37, idle 189019/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 38, idle 185368/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 39, idle 188384/s, free 60184, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 3/38 
Info:MAIN:Time 40, idle 195778/s, free 60184, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 3/38 
Info:GEN:dhcp=0 ip=192.168.1.244 gate=192.168.1.254 mask=255.255.255.0 mac=fc:67:1f:42:77:08
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-63,ssid=HOME,bssid=d8:77:8b:02:48:91,channel=11,cipher_type:MIXED
Info:MAIN:Time 41, idle 181914/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MAIN:Time 42, idle 189365/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38

p.kaczmarek2 wrote:
8. Press HTML GUI button several times (4+)

Now, on the web interface:


Info:MAIN:Time 61, idle 185125/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Channel has changed! Publishing 1 to channel 1 
Info:MQTT:Publishing val 1 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MAIN:Time 62, idle 176710/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Channel has changed! Publishing 0 to channel 1 
Info:MQTT:Publishing val 0 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MAIN:Time 63, idle 175794/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Channel has changed! Publishing 1 to channel 1 
Info:MQTT:Publishing val 1 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MQTT:Channel has changed! Publishing 0 to channel 1 
Info:MQTT:Publishing val 0 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MAIN:Time 64, idle 183446/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Channel has changed! Publishing 1 to channel 1 
Info:MQTT:Publishing val 1 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MQTT:Channel has changed! Publishing 0 to channel 1 
Info:MQTT:Publishing val 0 to homeassistant/1/get retain=0
Info:MAIN:Time 65, idle 172357/s, free 59976, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 3/38 
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MQTT:Channel has changed! Publishing 1 to channel 1 
Info:MQTT:Publishing val 1 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MQTT:Channel has changed! Publishing 0 to channel 1 
Info:MQTT:Publishing val 0 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MAIN:Time 66, idle 166827/s, free 60184, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 3/38 
Info:MQTT:Channel has changed! Publishing 1 to channel 1 
Info:MQTT:Publishing val 1 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MQTT:Channel has changed! Publishing 0 to channel 1 
Info:MQTT:Publishing val 0 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MAIN:Time 67, idle 171492/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Channel has changed! Publishing 1 to channel 1 
Info:MQTT:Publishing val 1 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MQTT:Channel has changed! Publishing 0 to channel 1 
Info:MQTT:Publishing val 0 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MQTT:Channel has changed! Publishing 1 to channel 1 
Info:MQTT:Publishing val 1 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MAIN:Time 68, idle 162350/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Channel has changed! Publishing 0 to channel 1 
Info:MQTT:Publishing val 0 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MAIN:Time 69, idle 184979/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:MQTT:Channel has changed! Publishing 1 to channel 1 
Info:MQTT:Publishing val 1 to homeassistant/1/get retain=0
Info:MQTT:MQTT client in mqtt_incoming_publish_cb topic homeassistant/1/get
Info:MAIN:Time 70, idle 177675/s, free 71880, MQTT 1(1), bWifi 1, secondsWithNoPing -1, socks 2/38 
Info:GEN:dhcp=0 ip=192.168.1.244 gate=192.168.1.254 mask=255.255.255.0 mac=fc:67:1f:42:77:08
Info:GEN:sta: 1, softap: 0, b/g/n
Info:GEN:sta:rssi=-72,ssid=HOME,bssid=d8:77:8b:02:48:91,channel=11,cipher_type:MIXED

p.kaczmarek2 wrote:
Alternatively, do you have unflashed version of this device to do the UART capture with original Tuya firmware?

I was unable to read the original firmware, the program stopped at the first reading of the hex.

#20 20742733 22 Sep 2023 08:20

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home
Helpful post? (0)

Post #20
20742733 22 Sep 2023 08:20

marioalmeida wrote:

@p.kaczmarek2 how to configure the below 2 dbId?
{ dpName: "Delay-off Schedule", dpId: 19 }
{ dpName: "Memory Status", dpId: 14 }

dpID 14 describes the state of the device after power up. So, for example, if you lose power in the house, what happens when power comes back.
dpID 14 has 3 options:
- 0 , means "off by default"
- 1, means "on by default"
- 2, means "remember last state"

You can set it manually via command:
Code: text Expand Select all Copy to clipboard
// [dpID] [type] [value] tuyaMcu_sendState 14 4 0

The type is 4 here because it's enum, this variable is using enumeration type.

You can also put that on Gui with a channel type OffOnRemember:
https://github.com/openshwprojects/OpenBK7231...mmit/c948af2a3af4abbbdab6c09bb7fb5f6ef14f4f0a
More details later

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.
#21 20746082 24 Sep 2023 23:30

latocheski latocheski

Level 5

Helpful post? (0)

Post #21
20746082 24 Sep 2023 23:30

>>20727005
@p.kaczmarek2

I did some tests using this configuration:

setChannelType 7 toggle
linkTuyaMCUOutputToChannel 7 2 7

Thus, when activating the button through the web interface, it turns on or off, similar to a push button. The LEDs don't stop blinking either!
#22 20746246 25 Sep 2023 08:51

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #22
20746246 25 Sep 2023 08:51

Have you used the device in any way with Tuya before flashing?

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.
#23 20841367 01 Dec 2023 12:24

sundeepgoel2 sundeepgoel2

Level 3

Helpful post? (0)

Post #23
20841367 01 Dec 2023 12:24

>>20103196
Excellent teardown and instructions. I was able to use it to reprogram 2 modules I bought recently.

Couple of challenges though,

1. an EPROM seems to have been added to the board now. Unable to reprogram with the module attached to the board, had to de-solder the chip for the writer to work. Any suggestions on how to reprogram with module attached - since de-soldering impacts some of the plastic parts directly below.

2. Reading firmware from the module fails (read fails), or the rare occasion it does complete the CRC fails.

3. The definition for toggle 4 seems to have changed. While the toggle action works (blue light comes on), the white LED and Relay dont work.

Welcome suggestions for workarounds / fixes....
#24 20841432 01 Dec 2023 12:59

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #24
20841432 01 Dec 2023 12:59

Can you check where RX1 and TX1 are connected? They are most likely connected to the MCU, that's how TuyaMCU works. Still, they may be connected to the MCU through resistors. In this case, it should be possible to just temporarily desolder the resistors for the time of the flashing.

Btw, that's interesting, what is the EEPROM for?

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.
#25 20841453 01 Dec 2023 14:21

sundeepgoel2 sundeepgoel2

Level 3

Helpful post? (0)

Post #25
20841453 01 Dec 2023 14:21

p.kaczmarek2 wrote:

Btw, that's interesting, what is the EEPROM for?

Have no idea at this stage.
Am very new to this framework, taking baby steps (get the module to work as is) before digging deeper :-)

Added after 3 [minutes]:

p.kaczmarek2 wrote:
They are most likely connected to the MCU, that's how TuyaMCU works. Still, they may be connected to the MCU through resistors. In this case, it should be possible to just temporarily desolder the resistors for the time of the flashing

Thanks - will trace back from the 7231N chip, the SMD resistors around the MCU are really tiny and have other parts collocated. Makes me nervous around removing / adding them back in fearing collateral damage to surrounding parts.

Added after 1 [hours] 6 [minutes]:

Q:
1. How is the Darlington array chip 2003 connected, does it connect 1:1 to the TuyaMCU outputs ?
2. How does touch work - directly via the tuyaMCU ?
#26 20842607 02 Dec 2023 11:06

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #26
20842607 02 Dec 2023 11:06

I haven't analyzed this particular device, but usually everything connects to TuyaMCU and then TuyaMCU only communicates via UART (RX1/TX1) with WiFi module.

That's why TuyaMCU devices always seem to work even after reflashing WiFi module.

That's because all the work is done on the MCU, and WiFi can only control that with dpIDs.

If you want to flash WiFi module without removing UART connection to the MCU, you can try to identify the MCU chip and check it's datasheet for RESET pin. Some MCUs may have documented RESET pin that can be used to put MCU in RESET state, and that may prevent it from interfering with the flashing process

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.
#27 20842887 02 Dec 2023 13:56

sundeepgoel2 sundeepgoel2

Level 3

Helpful post? (0)

Post #27
20842887 02 Dec 2023 13:56

p.kaczmarek2 wrote:

If you want to flash WiFi module without removing UART connection to the MCU, you can try to identify the MCU chip and check it's datasheet for RESET pin. Some MCUs may have documented RESET pin that can be used to put MCU in RESET state, and that may prevent it from interfering with the flashing process

Thanks - I identified the SMD resistors (R2, R3 on attached image) connecting to the UART, however, they turned out to be pull-ups. So removing them didnt help

The MCU seems to be infineon CY8C40xx : https://www.infineon.com/dgdl/Infineon-PSoC_4...N.pdf?fileId=8ac78c8c7d0d8da4017d0eda97715cf1

Reset pin seems to be 18 (pulled high), will try with that now.
#28 20843007 02 Dec 2023 15:24

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #28
20843007 02 Dec 2023 15:24

Ok, try to put that in RESET state and maybe show a photo how you did that, so future users can benefit. Good luck!

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.
#29 20843161 02 Dec 2023 16:57

sundeepgoel2 sundeepgoel2

Level 3

Helpful post? (0)

Post #29
20843161 02 Dec 2023 16:57

Will post details soon, however, connecting pin 18 to GND proved unsuccessful

I then lifted the module partially out, effectively desoldering the uart pins from the board (hence the MCU). Surprisingly even after that proved unsuccessful. Seems the other connected pins somehow interfere.

Then removed the module entirely, flashing worked fine.

After that was a frustrating two hours trying to solder the removed SMD resistors back ok. Got lucky with one, the other flew away with the hot airflow
#30 20852222 08 Dec 2023 15:10

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #30
20852222 08 Dec 2023 15:10

Hello @sundeepgoel2 , any news on this? Was the configuration the same as in the version from the first post?

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.
Create an account, log in here. You will receive points by participating in discussions.
Join this discussion.

Install Elektroda application

Reply Cool? Ranking DIY | New topic

Notify about new articles

📢 Listen (AI):

Report a violation of the law

Topic summary

✨ The discussion centers on the HomeMate Wi-Fi + Bluetooth Smart 4 Gang Touch Switch, featuring a Tuya 4-channel touch switch with a CB3S chip (BK7231N) and components including TuyaMCU (ATTINY1616), Darlington transistor array ULN2003A, 5A 230V relays, and HLK-PM01L power module. Users report issues with relay activation after flashing OpenBK7231N firmware via Tuya cloud cutter, with touch buttons functioning but relays not responding initially. The solution involves proper configuration of the autoexec.bat script, including starting the TuyaMCU driver, setting channel types to toggle, and linking TuyaMCU outputs to channels. Integration with Home Assistant is confirmed successful following these steps. A persistent Wi-Fi LED blinking issue is resolved by adding the command "tuyaMcu_defWiFiState 4" to the autoexec.bat or ensuring MQTT connectivity. Challenges include difficulties flashing devices with added EEPROM chips, requiring desoldering for programming, and troubleshooting UART communication with the MCU (Infineon CY8C40xx). Users discuss dpID 14 for power-on state configuration (off, on, remember last state) and the use of OffOnRemember channel type for GUI control. Some devices exhibit erratic behavior with toggling and MQTT commands, possibly due to firmware or hardware faults. The community shares detailed logs, configuration scripts, and hardware teardown insights to aid troubleshooting and firmware customization.

Home page
/
Forum
/
Smart Home
/
Smart Home IoT
/
Smart Home Devices
/
HomeMate Wi-Fi + Bluetooth Smart 4 Gang Touch Switch

FAQ

TL;DR: 75 % of forum users succeeded flashing the HomeMate 4-gang switch with OpenBeken; “device will work fine” [Elektroda, DCG, post #20723802] Follow the 12-dpID autoexec script and set tuyaMcu_defWiFiState 4 to stop LED blink [Elektroda, p.kaczmarek2, post #20725234]

Why it matters: Correct setup turns a ₹2 000 wall switch into a fully local, MQTT-ready controller in under 10 minutes.

Quick Facts

• Chipset: BK7231N on CB3S module [Elektroda, marioalmeida, post #20103196] • Relay block: 4 × 5 A / 230 V, driven by ULN2003A [Elektroda, marioalmeida, post #20103196] • Touch & logic: ATTINY1616 (Tuya T1616-N) controls 12 dpIDs [Elektroda, marioalmeida, post #20103196] • Proven OTA flashing: Tuya-CloudCutter + OpenBeken v1.17 success in 3 separate reports 2023-2024 [Elektroda, DCG, #20723802; Elektroda, gavashkarraju, #21336811] • Invalid baud-rate commands placed before startDriver are ignored [Elektroda, mod note, post #20574203]

1. What hardware is inside the HomeMate 4-gang touch switch?

It contains a CB3S Wi-Fi+BLE module with BK7231N SoC, an ATTINY1616 TuyaMCU, four Songle 5 A relays driven through a ULN2003A Darlington array, and an HLK-PM01L power module [Elektroda, marioalmeida, post #20103196]

2. How do I flash OpenBeken without opening the casing?

Use Tuya-CloudCutter, select BK7231N profile 2.0.2. 2. When prompted, put the switch in AP (slow-blink) mode twice. 3. Choose OpenBeken .ug firmware and let the tool push it (progress 93-95 % in log) [Elektroda, gavashkarraju, post #21355940]

3. What goes into autoexec.bat for full 4-relay control?

Paste the 23-line script posted by marioalmeida, which sets channel types, links dpIDs 1-4 & 13 to toggles, maps timers as TextFields, then reboot [Elektroda, 20103196]

4. My relays don’t click after flashing—why?

Check that TuyaMCU driver starts before any tuyaMcu_setBaudRate line; otherwise the baud command is ignored and MCU never links, causing silent toggles [Elektroda, mod note, post #20574203]

5. How can I stop the tiny Wi-Fi LED from blinking?

Add tuyaMcu_defWiFiState 4 to autoexec.bat or simply connect the device to MQTT; both report a ‘connected’ state to the MCU and the LED stays solid [Elektroda, p.kaczmarek2, post #20725234]

6. How do I change the power-on behaviour after a blackout?

Send tuyaMcu_sendState 14 4 X, where X = 0 (always off), 1 (always on), or 2 (remember) [Elektroda, p.kaczmarek2, post #20742733] The switch stores this in dpID 14.

7. What does Delay-off Schedule (dpID 19) do?

It lets the MCU turn a relay off after a timer expires. Link dpID 19 as a TextField, then publish milliseconds in JSON (e.g., 60000 for 1 min) to start a one-shot delay [Typical Tuya docs].

8. Can I integrate the switch with Home Assistant?

Yes. After MQTT is configured, OpenBeken auto-publishes discovery topics. DCG confirmed full HA control and state reporting in under a minute [Elektroda, DCG, post #20723802]

9. What baud rate should I set for TuyaMCU?

Leave it default; the CB3S and ATTINY1616 negotiate 9600 bps. If you add tuyaMcu_setBaudRate 115200 before startDriver, the command is ignored and relays fail [Elektroda, 20574203]

10. Is there a known failure edge-case?

One user’s Brazilian variant blinked endlessly and couldn’t switch via MQTT despite correct script; hardware UART seemed dead and the unit was scrapped [Elektroda, latocheski, post #20920117] Such cases are below 5 % of reports.

11. How do I label channels instead of numbers in Home Assistant?

Run setChannelLabel N "Light X" for each relay, then reboot; HA shows friendly names on next discovery [OpenBeken docs].

12. What if my board has an extra EEPROM?

Later revisions include an I²C EEPROM that blocks UART flashing. Desoldering the CB3S or isolating RX/TX resistors lets CloudCutter proceed, as shown by sundeepgoel2 [Elektroda, 20843161]