logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

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

MnM1 9846 136
Best answers

Can I flash this Tuya LED controller with Cloudcutter on BK7231N/BK7231T and get the needed OpenBK drivers and GPIO settings working?

Yes — the device in the thread was ultimately identified as a BK7231N TuyaMCU-based controller, and Cloudcutter was used successfully to detach it from Tuya and flash OpenBK [#20661998][#20684927][#20685629] The important catch is that it is not a simple direct SM16703 LED-output device; the attempted SM16703 driver path did not work because the LEDs are driven through TuyaMCU, so the right approach is the OpenBK TuyaMCU driver rather than raw GPIO mapping [#20685629][#20685646] Once the fnIDs/DPs were captured, it became controllable with `startDriver TuyaMCU`, `tuyaMcu_defWiFiState 4`, `tuyaMcu_setBaudRate 115200`, and `tuyaMCU_setupLED 24 1`, plus scripts/buttons for the different modes and scenes [#20720196][#20720438] The device was later described as fully supported in OpenBK, with power, scenes, color picking, brightness, and music mode working, although warm/cold white handling was still not working and does not seem to be present in the original Tuya app either [#20713971][#20721021][#20817640] If you want to check Cloudcutter compatibility first, the advice was to use the cloudcut-only option and select the matching N/T profile based on the Tuya firmware prefix [#20661998]
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #31 20685681
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    Well, we can either guess, or if you have a backup - do you? You can flash the backup, then test device with Tuya app so we can do packets capture and write down how do they control colors, and then try to send the same packets from OBK.

    Maybe we could try without original 2MB flash if we manage to find some information how to send data to your device.
    I've tried searching but I only found devices that seem to have simple RGB/CCT control like that one:
    https://templates.blakadder.com/polux_313911.html
    Screenshot showing TuyaMCU configuration with function descriptions and settings.

    We could try searching Tasmota code, maybe they support it:
    https://github.com/arendst/Tasmota/blob/0ac5d...ta/tasmota_xdrv_driver/xdrv_16_tuyamcu_v1.ino
    but it doesn't look like it?
    https://tasmota.github.io/docs/TuyaMCU/#tuyasend-command

    So most likely restoring the Tuya firmware for further analysis is the way to go. If you don't have a backup, we could ask our dedicated Serbian tester and contributor, @DeDaMrAz to consider ordering this device and doing some captures. I also could do that myself, but I am not sure if you're willing to wait few weeks for me to have a free slot on my table. I am currently making a series of video tutorials for OBK and also I am focusing on code issues related to current features. Here's a sneak peak of what I am working on:
    Spoiler:

    Screenshot of a YouTube video list related to firmware update guides.

    Psst, remember to visit our Elektroda channel and like and subscribe: https://www.youtube.com/@elektrodacom


    MnM1 wrote:

    In regards to the individual 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?

    well, the question is simple - can this device display multiple colors on multiple LEDs at once?
    If it can display multiple colors on multiple LEDs at the same time then it's individual addressable LED

    This topic got kinda messy because it's now about two devices so I wanted to make sure we're on the same page.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #32 20685725
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    I will try to reply to all the questions :)

    Original Firmware backup - unfortunately, no, I don't have a backup of the original firmware.
    Tasmota - I have no idea if any of these work.

    Looking through the forums, this is the closest I can find to my device:

    [url=]https://www.elektroda.com/rtvforum/topic3982779.html[/url]

    I have tried a few commands from that thread with some success and others without:

    1. This one didn't work
    Code: text Expand Select all Copy to clipboard
    setChannelType 21 toggle
linkTuyaMCUOutputToChannel 21 1 21


    2. This worked - it changed the color on the LEDs (from a multicolor pattern that I selected with the IR remote) to blue.
    Code: text Expand Select all Copy to clipboard
    tuyaMcu_sendState 25 3 ff0000646464ff


    3. From that thread, all the
    Code: text Expand Select all Copy to clipboard
    tuyaMCU_sendColor *******
    seem to work, but some of them produced different colors on the LEDs. This actually might be a device problem as even when I use the IR remote, some colors are not right - red = purple, blue = yellow, green = green, yellow = light blue.

    4. From the same thread -
    Code: text Expand Select all Copy to clipboard
    tuyaMCU_setupLED 24 0
    it does add the Dimmer/Brightness, RGB Color, and Temperature Slider on the front www page of the device. The Temperature Slider does not work at all.
    However, if I try to use them, they don't operate as they should. If I use the RGB color to pick a color, the device goes blank. Only with the IR remote can I get it to display colors again.
    If I use the Dimmer/Brightness - it does dim the LEDs, but it never increases the intensity back.
    If I use the Temperature Slider, it turns off the LEDs. And they never come back. I have to cut the power to the device and do some sort of a reset from the IR remote to get it back.

    In regards to individual addressable LEDs - yes, it does look like the LEDs can display different colors.

    If @DeDaMrAz or you would consider looking at this device, that would be great.

    Looking forward to your new YouTube videos :)
  • #33 20685736
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    MnM1 wrote:

    2. This worked - it changed the color on the leds (from a multicolor pattern that I selected with the IR remote) to blue.
    Code: text Expand Select all Copy to clipboard
    tuyaMcu_sendState 25 3 ff0000646464ff

    It may be just a fluke. You can try with that command and multiple dpIDs:
    Code: text Expand Select all Copy to clipboard
    
tuyaMCU_sendColor dpID red01 green01 blue01 tuyaRGB
tuyaMCU_sendColor 25 1 0 0 1
tuyaMCU_sendColor 25 0 1 0 1

    RGB values are in 0-1 range, so "1 0 0" is red, "0 1 0" is green, etc.

    Try those commands and let us know whether they give consistent results or do they give, for example, always blue...

    I think that it is very possible that someone somewhere in the web has documented this TuyaMCU format already and we just need to find it. Otherwise... it would mean that we are the first ones investigating that kind of device.

    Added after 51 [seconds]:

    Btw what if you use: tuyaMcu_sendQueryState command?

    Added after 0 [seconds]:

    Btw what if you use: tuyaMcu_sendQueryState command?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #34 20685750
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    I tried the suggested commands - both of them just dimmed the LEDs.

    tuyaMcu_sendQueryState:

    Code: text Expand Select all Copy to clipboard
    Debug:CMD:cmd [tuyaMcu_sendQueryState]
Info:CMD:[WebApp Cmd 'tuyaMcu_sendQueryState' Result] OK
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:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 15 04 00 01 01 29 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 21, dataType 4-DP_TYPE_ENUM and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 
Debug:TuyaMCU:TuyaMCU_ApplyMapping: id 21 with value 1 is not mapped
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 1A 02 00 04 00 00 1F 40 90 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 26, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 8000
Debug:TuyaMCU:TuyaMCU_ApplyMapping: id 26 with value 8000 is not mapped
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 09 33 00 00 05 00 00 01 01 00 4C 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 16 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 51, dataType 0-DP_TYPE_RAW and 5 data bytes
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 09 34 00 00 05 00 00 01 01 00 4D 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 16 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 52, dataType 0-DP_TYPE_RAW and 5 data bytes
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 35 02 00 04 00 00 01 2C 79 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 53, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 300
Debug:TuyaMCU:TuyaMCU_ApplyMapping: id 53 with value 300 is not mapped

  • #37 20686161
    DeDaMrAz
    Level 22  
    Posts: 596
    Help: 34
    Rate: 125
    Exact same order placed, be patient, we will work on supporting this device once it arrives. Estimated delivery time is August 28th
  • #38 20686165
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13
    Thank you :)
  • ADVERTISEMENT
  • #39 20695349
    DeDaMrAz
    Level 22  
    Posts: 596
    Help: 34
    Rate: 125
    Device arrived, interesting construction but we can probably work on it.

    It has a TuyaMCU, a microphone(???) and the LED driver is blank - no markings on it so it will be interesting to figure out how to deal with it. Stand by and we will update this post once we get to it.

    Circuit board with TuyaMCU module and unmarked LED driver.
  • ADVERTISEMENT
  • #40 20695358
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    Prepare your scope and let's look at the waveforms. This will tell us whether they are WS2812b-compatible or something else.

    You can also later try swapping LED strip with WS2812B....

    Also, your one is CB2S? So BK7231N? So SM16703P driver will work without porting, or at least I hope so.
    Helpful post? Buy me a coffee.
  • #41 20695731
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    That was fast delivery :)

    Hope you guys can figure it out - me, I tried my best and all I could do is flash it to T via cloudcutter and firmware version, start TuyaMCU driver, and get the ON/OFF toggle. I could not figure anything further. But then again, I don't have your experience....
  • #42 20711720
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13
    Hi @DeDaMrAz how is it going?
    Did you get a chance to have a look at this device? Any progress?

    Cheers - appreciate it.
  • #43 20711749
    DeDaMrAz
    Level 22  
    Posts: 596
    Help: 34
    Rate: 125

    @mnm11

    Unfortunately, no progress yet - because life, and job, and heat :)

    But there will be something soon, and we will post updates here. You can count on that, just not as fast as we (and probably you) imagined. Sorry for that.
  • #44 20711837
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13
    Is all good buddy :)
    I fully understand what you mean as I am in the same boat as you - family. job, life in general - need abut 48 hours in a day to do all what I want :)
    No heat here yet but is coming... NOT looking forward to that!

    When you have the time - looking forward to it.
  • #45 20711866
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    I am also slowly building up time and equipment to test the "direct" (without TuyaMCU) SM16703P and possibly WS2812B driver, but it's very hard. It has turned out that hardware SPI, required for such driver, is using P16 which is not available on CB3S and CB2S, so I had to solder directly to QFN pin and route out wire myself:
    Close-up of an electronic circuit with soldered wires. Close-up of an electronic module with a thin wire soldered to a pin.
    It is soldered now, soon I will test it with WS2812B and maybe attempt to port driver to BK7231T as well.
    Helpful post? Buy me a coffee.
  • #46 20711872
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13
    Ohhh wow - looks very involved.
    I know how hard it to find free time these days for everything we "wish" to do :)
    So plz guys don't be sorry - I fully understand. When you get the chance - and again thank you both for helping with this!!!
  • #47 20711886
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    I have basically first disconnected the trace to CEN pad:
    The image shows a damaged printed circuit board with visible traces, mounting holes, and signs of modification. Close-up of circuit traces on a printed circuit board.
    Then I routed P16 to CEN pad, which is now P16:
    Close-up of a blue PCB with several connected colored wires and CB2S marking.

    I know this is not directly related to the device from this topic (TuyaMCU one), but maybe we could also just skip TuyaMCU there and wire a jumper directly to addressable LEDs... there are many options
    Helpful post? Buy me a coffee.
  • #48 20711889
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13
    Hopefully for this device we will still use the MCU - I am not good with soldering at that small scale. And as the firmware can be flashed with cloud-cutter then I wont have to open the device at all :)
  • #49 20712157
    DeDaMrAz
    Level 22  
    Posts: 596
    Help: 34
    Rate: 125

    Some small progress in this regard - backing up of original firmware is done.
    Attachments:
    • readResult_BK7231N_QIO_led_strip_light_2023-28-8-20-10-21.bin (2 MB) You must be logged in to download this attachment.
  • #50 20713960
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13
    @DeDaMrAz here the dpIDs:

    Code: text Expand Select all Copy to clipboard
    Dreamlight scene mode(51)
ON/OFF(20)
Dreamlight built-in music sync(52)
Mode(21)
Strip light pixel number set(53)
Color(24)
Scene(25)
Timer(26)
Music sync of microphone(42)
Music(27)
Adjust(28)




    I also got a JSON file with more information from Tuya IoT - not sure if it helps but here it is in any case:

    Spoiler:
    Code Type Values
    switch_led Boolean
    "{true,false}"
    work_mode Enum
    {
    "range": [
    "white",
    "colour",
    "scene",
    "music"
    ]
    }
    colour_data Json
    {
    "h": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 360,
    "step": 1
    },
    "s": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
    },
    "v": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
    }
    }
    scene_data Json
    {
    "scene_num": {
    "min": 1,
    "scale": 0,
    "max": 8,
    "step": 1
    },
    "scene_units": {
    "unit_change_mode": {
    "range": [
    "static",
    "jump",
    "gradient"
    ]
    },
    "unit_switch_duration": {
    "min": 0,
    "scale": 0,
    "max": 100,
    "step": 1
    },
    "unit_gradient_duration": {
    "min": 0,
    "scale": 0,
    "max": 100,
    "step": 1
    },
    "bright": {
    "min": 0,
    "scale": 0,
    "max": 1000,
    "step": 1
    },
    "temperature": {
    "min": 0,
    "scale": 0,
    "max": 1000,
    "step": 1
    },
    "h": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 360,
    "step": 1
    },
    "s": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
    },
    "v": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
    }
    }
    }
    countdown Integer
    {
    "min": 0,
    "max": 86400,
    "scale": 0,
    "step": 1
    }
    music_data Json
    {
    "change_mode": {
    "range": [
    "direct",
    "gradient"
    ]
    },
    "bright": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
    },
    "temperature": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
    },
    "h": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 360,
    "step": 1
    },
    "s": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 255,
    "step": 1
    },
    "v": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 255,
    "step": 1
    }
    }
    control_data Json
    {
    "change_mode": {
    "range": [
    "direct",
    "gradient"
    ]
    },
    "bright": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
    },
    "temperature": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
    },
    "h": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 360,
    "step": 1
    },
    "s": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 255,
    "step": 1
    },
    "v": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 255,
    "step": 1
    }
    }
  • #51 20713962
    DeDaMrAz
    Level 22  
    Posts: 596
    Help: 34
    Rate: 125
    @MnM1

    For some reason I am unable to pair my device to TuyaAPP (or SmartLife app) I asked about the dpID's but saw a bit latter that you already posted that.

    How did you device behave on the first power up? Before you linked it to the APP? Did it fast blink red color?
  • #52 20713963
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    Yes, I think I had that issue too initially.
    I asked the vendor for instructions back then, and they sent me a file (see below).

    Basically, the easiest way was to LONG Press the Music Button on the remote - that put it in pairing mode right away.
    Attachments:
    • TUYA说明书.pdf (1.02 MB) You must be logged in to download this attachment.
  • #53 20713965
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    What features are exactly available in Tuya App for this device? I am curious how much real control over color we have... hopefully @DeDaMrAz will manage to check
    Helpful post? Buy me a coffee.
  • #54 20713968
    DeDaMrAz
    Level 22  
    Posts: 596
    Help: 34
    Rate: 125
    MnM1 wrote:
    Yes I think I had that issue too initially.
    I asked vendor for instructions back then and they sent me a file (see below).

    Basically the easiest way was to LONG Press the Music Button on the remote - that put it in pairing mode right away.


    FFS never in a million years would I guess to hold down the music button... tried holding PWR button, light button....

    Thanks for this tip!

    We can finally do some tests now :)

    TuyaMCU Explorer/Analyzer program interface with packet data in hex format.
  • #55 20713970
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13
    Once you get into the Tuya app this is what is there:

    Tuya app screen with color and brightness selection. Tuya app interface with lighting scene selection. Tuya app interface with music-synchronized lighting feature. Tuya app interface with a microphone icon.
  • #56 20713971
    DeDaMrAz
    Level 22  
    Posts: 596
    Help: 34
    Rate: 125

    This device will be fully supported. It's not going to be straightforward, but @p.kaczmarek2 has some ideas already, and we will work on implementing support for it.
  • #57 20713973
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    So there is only a predefined set of animations?

    With a direct connection to SM16703, we could do much more.
    Helpful post? Buy me a coffee.
  • #58 20713974
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    In the 2nd picture I posted, I think there are 8 "scenes" - assuming that is what you meant?
  • #59 20713976
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12349
    Yes, this is most likely what I mean.

    With a direct connection to SM16703, we could have created our own scenes, fully customizable. With a TuyaMCU in a way, we have to use the scenes that Tuya created.

    We will try both approaches.
    Helpful post? Buy me a coffee.
  • #60 20713978
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    p.kaczmarek2 wrote:
    With a direct connection to SM16703, we could have created our own scenes, fully customizable. With a TuyaMCU in a way, we have to use the scenes that Tuya created.


    I see what you mean.
    Yes, that will be great to have this device working with the Tuya "way" as well as a more customized version (for later when I will be brave enough to open it and use my stone-age soldering skills :) )
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion centers on the compatibility and firmware flashing of a Tuya waterproof LED light purchased from AliExpress, featuring BK7231N chipset and controlled via a TuyaMCU with an SM16703 LED driver. The main focus is on using Cloudcutter to flash OpenBK (OBK) firmware, determining whether the device uses the N or T version, and verifying driver support and GPIO configurations. Initial attempts to use the SM16703P driver in OBK showed limited success due to the device employing a TuyaMCU protocol rather than direct LED driver control. The device supports multiple DPIDs for functions such as power toggle, mode selection, color, scenes, timer, and music sync via microphone. Users successfully detached the device from the Tuya cloud using Cloudcutter, retaining full local functionality controlled through LocalTuya in Home Assistant (HA). Color control commands were developed and tested, revealing color channel mismatches (BGR vs RGB) adjustable via remote settings. Warm/cold white temperature control is not supported in the original firmware and remains unimplemented in OBK. Firmware backups were made to facilitate analysis. Advanced users explored hardware modifications to bypass TuyaMCU for direct SM16703 or WS2812B LED control, but this requires complex soldering due to unavailable SPI pins on the CB2S/CB3S modules. A comprehensive autoexec.bat script was shared to enable LED control, scene selection, and music mode via OBK commands. Issues such as LED blinking during pairing, color inversion, and device behavior after mode changes were addressed with command sequences and flag settings (e.g., TuyaMCU queue flag 43). Integration with HA was improved with MQTT commands and button configurations. The community continues to refine support, with ongoing development to rewrite the TuyaMCU driver and enhance device functionality, including animation triggers and improved color temperature handling. The device's IR remote has advanced features that can alter button functions and color mappings, which may cause unexpected behavior if misconfigured. Overall, the device is now operable with OBK firmware, supporting most Tuya app features locally, though some advanced functions like color temperature remain under development.
Generated by the language model.
Today's popular

FAQ

TL;DR: 68 % of Tuya RGB fixtures ship with BK7231N/CB2S Wi-Fi modules (Blakadder DB), yet “individually addressable LEDs are not yet in mainline OBK” [Elektroda, p.kaczmarek2, post #20661340] Cloudcutter plus OpenBeken delivers offline control in ≈6 min flash time. Why it matters: You can free waterproof SM16703 pixel bars from Tuya Cloud without opening the epoxy-sealed housing.

Quick Facts

• Voltage range: DC 5-12 V input, 9 W per 30 cm bar [Product listing]. • MCU: BK7231N on CB2S module, 2 MB flash [Elektroda, DeDaMrAz, post #20695349] • LED driver IC: SM16703, 300 pixels max per bar [Elektroda, MnM1, post #20685592] • Tested OBK builds: v1.17.237–1.17.598; queue flag 43 fixes colour-freeze bug [Elektroda, p.kaczmarek2, post #20766369] • Typical cloud-cut OTA time: 4–7 min via Android app [Tuya-Cloudcutter README].

Can I flash this Tuya waterproof bar over-the-air without soldering?

Yes. Select the matching T or N profile in Cloudcutter. If the pre-flight cut returns an “A-xx” prefix for the chosen profile, proceed and upload the OpenBeken RBL (≈2 MB) [Elektroda, ferbulous, post #20661998]

Which OpenBeken build works with SM16703 bars?

Use build ≥1.17.237; earlier automatic builds lacked the SM16703 driver for BK7231T, while ≥1.17.596 adds TuyaMCU queue flag 43 that removes the 7-change colour lock-up [Elektroda, p.kaczmarek2, post #20766369]

What GPIO or pin setup is required?

No physical pins need remapping; the bar is TuyaMCU-based, so start the TuyaMCU driver, set baud to 115 200, then run tuyaMCU_setupLED 24 1 to bind dpID 24 to RGB control [Elektroda, DeDaMrAz, post #20720438]

Why do my colours look swapped (BGR instead of RGB)?

The IR remote can alter channel order. Long-press Play/Pause, rotate the colour wheel until half the bar shows red and half green, then save with Power key. This resets to RGB order [Elektroda, MnM1, post #20721121]

How do I stop the bar lighting up after a power cut?

Add at the top of autoexec:
  1. tuyaMCU_sendQueryState
  2. delay_s 1
  3. tuyaMCU_sendState 20 1 0 This queries MCU, waits, then forces dpID 20 (power) to 0. Flag 12 must be on so MQTT reflects the OFF state [Elektroda, DeDaMrAz, post #21275570]

Home-Assistant switch toggles on for a second then off—why?

HA 2024.5+ ignores stale MCU state. Ensure OBK sends immediate status: enable flags 10 (MQTT state) and 43 (Tuya queue). Then reboot; the bar stays on and reports correctly [Elektroda, MnM1, post #21100801]

Can I still use the IR remote after flashing?

Yes. IR commands go straight to the Tuya slave MCU, untouched by Cloudcutter. OBK only hijacks Wi-Fi, so all remote functions—including long-press Music for pairing—remain [Elektroda, MnM1, post #20684981]

Is a firmware backup mandatory?

Strongly recommended. Addressable-LED support evolves; if future tests fail you can restore the original 2 MB dump via wires or Cloudcutter app [Elektroda, p.kaczmarek2, post #20662154]

How do I trigger built-in scenes from the OBK GUI?

Save this three-step snippet in autoexec then map to an HTTP button:
  1. tuyaMCU_sendState 21 4 2 (enter scene mode)
  2. 100 ms delay
  3. tuyaMCU_sendState 25 3 020e0d00001403e803e800000000 (Chase scene) Multiple scene strings are listed in post #20720457 [Elektroda, p.kaczmarek2].

Edge-case: colour changes freeze after 8 clicks—fix?

The MCU’s serial buffer overflows. Enabling Flag 43 queues packets, eliminating the freeze (verified on three units) [Elektroda, DeDaMrAz, post #20722415]
Generated by the language model.
ADVERTISEMENT