Query: Tuya Led Controller DC5-12v Compatibility with Cloudcutter Flash BK7321 and OBK Drivers

Name: Query: Tuya Led Controller DC5-12v Compatibility with Cloudcutter Flash BK7321 and OBK Drivers
Uploaded: 2023-07-20T15:41:46+02:00
Description: Hi, Got this light from AliExpress: It is a waterproof light and I really can't open and see the inside components. Plus, it is not that cheap and I don't want to ruin it. I am trying to see if I can use cloudcutter to flash BK7321 (which version?), if the required drivers are supported, and...

Question

Hi, Got this light from AliExpress: It is a waterproof light and I really can't open and see the inside components. Plus, it is not that cheap and I don't want to ruin it. I am trying to see if I can use cloudcutter to flash BK7321 (which version?), if the required drivers are supported, and...

p.kaczmarek2 · Answer

Hello, individually adressable LEDs are planned, but not yet supported. Providing information what kind of driver is used there can help (is it WS2812B or something else), but still, it's currently not implemented in the codebase. Same with binary dump - if you can read flash by wires, it will help us to extend the template importer.

ferbulous · Answer

To verify if it works for cloudcutter,
Pick the cloudcut option only (not firmware flashing), you need to avoid picking the wrong firmware type first.
Select the T & N profile for that firmware version. If it gets an 'A-xx' prefix for the N profile (for example), then you can proceed flashing N firmware.

p.kaczmarek2 · Answer

But would that provide us a 2MB firmware backup? We don't have addressable LEDs support yet, so backup is recommended so you don't get stuck with device that is still waiting for driver implementation.

ferbulous · Answer

You could try the Cloudcutter app for that.

MnM1 · Answer

Thanks for the information, guys.I will look and see what I can do. The AliExpress seller is very helpful too. They said they manufacture the lights. I suspect they put them together. So if they have access to the raw materials, I think that if they can, they will tell me the name of the chips used for the LEDs.I have asked them, and I will see what they will say - probably on Monday, I suspect.With cloudcutter, I have never used it to cut the device from Tuya only. I have always flashed 3rd party firmware.@ferbulous - if I cut the devices from Tuya, will they still have full functionality? Or does it need a cloudcutter profile for that?I am careful as these 2 lights I got were not cheap, and I don't want to have them not working.

ferbulous · Answer

@mnm11 yes, it retains the full function but you'll need to use localtuya to control it since it won't connect to Tuya cloud anymore.

MnM1 · Answer

@ferbulous - so the process will be
- install localtuya in HA
- get this device connected and configured in localtuya in HA (and use the Tuya IoT platform to get it configured properly or is that Tuyalocal that needs the Tuya IoT configuration? LOL I get confused between them 2)
- then cut the device from Tuya an it will still retain full functionality? as if it was connected to Tuya cloud?

ferbulous · Answer

@mnm11 Yes, after detaching from the cloud, you'll get the device ID to use with localtuya and just need to figure out the dpids.

MnM1 · Answer

The information I have from the vendor is that they are "3535-96 beads, the lamp beads are 3535" - not sure if that helps or not.

If it doesn't help, can someone help phrase my question to the vendor as I am not sure I am asking him the right way. What exactly should I ask him?

MnM1 · Answer

New information - they tell me that the driver is 16703. I assume it's SM16703.And I noticed this in the forums here: do you think the vendor's reply is correct? Can SM16703 support addressable LEDs?

p.kaczmarek2 · Answer

If you want to experiment ,get latest build and try:


1. Start driver
startDriver SM16703P

2. Init Driver
SM16703P_Init [[pixelcount]]

3. Set Pixel
SM16703P_SetPixel 1 255 0 0
SM16703P_SetPixel 2 0 255 0
SM16703P_SetPixel 3 0 0 255

4. Start Output (each call will trigger one
SM16703P_Start

I can't test it myself because I don't have this device... make sure you have Tuya firmware backup!

MnM1 · Answer

On step 2 I get this error: Error:CMD:cmd SM16703P_Init NOT found (args [[pixelcount]]) Unknown command

p.kaczmarek2 · Answer

Sorry, it seems that the automatic build didn't catch last commit. Let me check...

MnM1 · Answer

Latest build 202 - can't download the file = 404 errorEdit: OpenBK7231T_1.17.202* = file not available. The files for N are OK.

p.kaczmarek2 · Answer

Yes, it seems that the LED driver contributor currently provided a version only for N. Are you possibly on T platform?

If so, I would need to try to fix T compilation first. I assumed you're on N, because N is most popular these days.

MnM1 · Answer

Yeah, I am on T - however, I am not testing on the device in this thread. As mentioned before, this device is too expensive for me to test on.
I have ordered a shorter one (the one in the pic is 1.2M long) which is much cheaper, so I can test when it arrives - around 10 days.

I am testing on this one at the moment - see if I get lucky

and it uses the same LEDs

https://www.elektroda.com/rtvforum/topic3990174.html

p.kaczmarek2 · Answer

Driver would work on N, I am not sure about T. Let me try to port it and we will see.

MnM1 · Answer

@p.kaczmarek2 - Is the 205T version supposed to have the SM16703 feature enabled?Just tried it and the drivers are not loading.

p.kaczmarek2 · Answer

For now, only basic build was fixed. I will try to port the SM16703 feature to T in the following days.

MnM1 · Answer

I have received my test device today.According to the manufacturer, it uses SM16703. It also uses BK7231N.I added it to Tuya, and I got a cloud cutter supported firmware on it.I have added it to HA with LocalTuya and have got a list of dp_ids from the Tuya IoT site.As per my previous 2 devices, these are really sealed and weatherproof - so I have no chance in opening it without destroying it. And as I really don't want to kill it, I went ahead and uploaded 1.17.206 to it. Complete the upload and initial setup, and I have the device on my wifi now.I went ahead and ran the commands as instructed. I can see the driver loaded now: But I am not seeing anything else in the menu (Toggle, dimming/rgb/temp options, etc.)What do you advise I should do next?Or if you need any logs or anything from me, please let me know.

p.kaczmarek2 · Answer

This is a good news, we can test finally that SM16703P driver from contributor.

His comments says:

Please do steps from the image and let me know if anything lights up. Those commands show turn on 3 LEDs. There is no GUI for that yet. We can work on GUI once we know that at least LED communication is working.

MnM1 · Answer

I have tried the commands and this is what I get from the last one (SM16703P_Start):

Error: CMD: before enable tx 0x0000020c
Error: CMD: enable tx 0x0000020c

This device is behaving funny. As soon as I start it, the LEDs are blinking blue on it.
It also has an IR remote control that is still fully functional even with BK7231N 1.17.206 on it. I guess it must have an additional module for it somewhere.

p.kaczmarek2 · Answer

Can you post a video of that blinking? Do they always blink? Or maybe it's blinking as in "pair mode"?

According to the contributor, those commands should enable first 3 LEDs. If they doesn't, please get Tuya Config partition so I can check it for TuyaMCU traces:
https://www.youtube.com/watch?v=WunlqIMAdgw&ab_channel=Elektrodacom
You not getting correct colors lit may mean multiple things:
- this is not a SM16703P
- this may be a TuyaMCU device (maybe even with SM16703P, but not connected to Beken)
- SM16703P driver is broken (no one tested it yet except the original contributor)

I may try to check this driver with ws2812b soon, maybe fix T port, etc, but it all depends on my free time, I am just a one person, and for now I was making some new vids (with little help of my assistant!) for our YT channel: https://www.youtube.com/@elektrodacom maybe this week I will manage to look into addressable LEDs more

Added after 3 [minutes]:

MnM1 wrote:

This device is behaving funny. As soon as I start it, the LEDs are blinking blue on it.

As soon as you start the driver, or as soon you power device?

If as soon you power device, even with OBK, leds are blinking blue, then it would mean it's a TuyaMCU device.

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.

MnM1 · Answer

The LEDs turn on and start flashing as soon as I turn the power on the device.
In the attached video, I turn the power on and the LEDs blink, and then I turn the power off:

This is what Tuya showed me in the app:

Here is the Tuya Config partition:

Thanks again for your help, I know you are very busy.

Edit: The device is not in pairing mode. It is not broadcasting a WIFI AP. As mentioned, it has been flashed with BK7231N version 1.17.206

MnM1 · Answer

Not sure if it helps - these are the dp_ids I got from Tuya IOT:

{
  "result": {
    "properties": [
      {
        "code": "switch_led",
        "custom_name": "",
        "dp_id": 20,
        "time": 1691419039226,
        "value": true
      },
      {
        "code": "work_mode",
        "custom_name": "",
        "dp_id": 21,
        "time": 1691419328172,
        "value": "scene"
      },
      {
        "code": "colour_data",
        "custom_name": "",
        "dp_id": 24,
        "time": 1691419314227,
        "value": "000303e803e8"
      },
      {
        "code": "scene_data",
        "custom_name": "",
        "dp_id": 25,
        "time": 1691419366859,
        "value": "000d0d00002e03e803e800000000"
      },
      {
        "code": "countdown",
        "custom_name": "",
        "dp_id": 26,
        "time": 1691418854707,
        "value": 8000
      },
      {
        "code": "music_data",
        "custom_name": "",
        "dp_id": 27,
        "time": 1691418746551,
        "value": ""
      },
      {
        "code": "control_data",
        "custom_name": "",
        "dp_id": 28,
        "time": 1691418746551,
        "value": ""
      },
      {
        "code": "mic_music_data",
        "custom_name": "",
        "dp_id": 42,
        "time": 1691418746551,
        "value": ""
      },
      {
        "code": "dreamlight_scene_mode",
        "custom_name": "",
        "dp_id": 51,
        "time": 1691418849564
      },
      {
        "code": "dreamlightmic_music_data",
        "custom_name": "",
        "dp_id": 52,
        "time": 1691418849564
      },
      {
        "code": "lightpixel_number_set",
        "custom_name": "",
        "dp_id": 53,
        "time": 1691418854707,
        "value": 300
      }
    ]
  },
  "success": true,
  "t": 1691421341635,
  "tid": "45cd0986353511ee94e0a2e0adfc0b14"
}

p.kaczmarek2 · Answer

The SM driver will not work for this device, as it's a TuyaMCU device.
Your Tuya config even shows the baud rate:

The LEDs are blinking because MCU thinks it's in pairing mode. They will stop blinking as soon as you do:


tuyaMcu_defWiFiState 4

to tell MCU that is "paired and connected to the cloud".

First of all, are you sure this device has individually addressable LEDs?

MnM1 · Answer

Hi - yes, I have made some progress - as per my post above yours.

In regards to the individually addressable LED - I was only going by what you said in post number 2 in this thread (https://www.elektroda.com/rtvforum/topic3990646.html#20661340)

and from the information I got from the sellers - "New information - they tell me that the driver is 16703. I assume it's SM16703."
But maybe it is not?

p.kaczmarek2 · Answer

Are you able to control this device with IR remote? I saw something like that mentioned in previous posts.

If so, do a methodical test of changing, let's say, first colors, and copy the log from the Web App, and write down what each packet does. Something like:

Quote:

Info:TuyaMCU:TUYAMCU received: ?? ??? ??? ??? <--- this sets RED
Info:TuyaMCU:TUYAMCU received: ?? ??? ??? ??? <--- this sets BLUE

etc, etc.

Try to capture dpID 24, dpID 28, etc, and always make sure to write down which particular TUYAMCU event does.

I haven't seen yet an individually addressable LEDs with TuyaMCU, but they should be supportable.

We could also use this command to manually send packets from OBK to the MCU to check what is working:

but first we need to know what to send.

MnM1 · Answer

While I can control the device with the remote, it doesn't show anything in the logs.
I can only see

Info:TuyaMCU:TUYAMCU received: 55 AA 03 00 00 01 01 04 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Heartbeat) with 8 bytes

Info:TuyaMCU:TUYAMCU received: 55 AA 03 03 00 00 05 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 3 (WiFiState) with 7 bytes

When I press the OFF button

Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 14 01 00 01 00 24 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 20, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 
Info:GEN:CHANNEL_Set channel 20 has changed to 0 (flags 0)
Info:MQTT:Channel has changed! Publishing 0 to channel 20

And when I press the ON button

Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 0 (Heartbeat) with 8 bytes
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 14 01 00 01 01 25 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 20, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 
Info:GEN:CHANNEL_Set channel 20 has changed to 1 (flags 0)
Info:MQTT:Channel has changed! Publishing 1 to channel 20

I can't see anything else in the logs (I have all features selected including IR)

Query: Tuya Led Controller DC5-12v Compatibility with Cloudcutter Flash BK7321 and OBK Drivers

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Post #21

Post #22

Post #23

Post #24

Post #25

Post #26

Post #27

Post #28

Post #29

Post #30

Topic summary