logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Converting LSC 3203632.1 5 Meters LED Strip RGB/C + CCT/C to OpenBeken

snakesrules94 5169 19
Best answers

How can I control the RGB and white modes of the LSC 3203632.1 LED strip in OpenBeken when only one data line is connected and the cool/warm pads are unused?

You likely cannot map it as a normal separate RGB+CCT strip in OpenBeken, because the strip is driven by a single data line to an SM16703 chain and the controller firmware appears to have the pin mapping hardcoded [#21334397][#21338404] In the original Tuya app, RGB mode uses only LED 1, cool white uses LED 2, warm white uses LED 3, and the “other white” mode uses LEDs 1 and 2 together, while 24V stays present all the time [#21338334] The board wiring reported by the poster is PWM on P6, relay on P8, buttons on P9/P24/P28, IR on P26, and SM16703 on P16 [#21333653] A later report says the practical working route was to flash OpenBeken first and then flash ESPHome, where the strip was fully controllable from Home Assistant using `spi_led_strip` with `mosi_pin: 16`, `clk_pin: 18`, `num_leds: 3`, and `data_rate: 1MHz` [#21359164]
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • Helpful post
    #1 21332211
    snakesrules94
    Level 8  
    Posts: 37
    Help: 3
    Rate: 4
    In addition to the topic Converting LSC 3203632 Smart LED Strip to OpenBeken: Challenges with BK7231N Flashing , here's my attempt with the version 3203632.1 which seems different .

    To start with some pictures :

    LSC Smart LED Strip packaging with rainbow graphics.Back of the LSC Smart Connect box with QR codes and technical information.Green packaging with recycling information and FSC certification.

    There are 25 parts like this one to achieve the 5M strip :

    Smart LSC 3203632 LED strip on a black background.
    Section of LSC LED strip with code 3203632.1.Section of LED strip with visible diodes and components.

    The 2 CI's on strip are totally black, no writing, no refs.

    And finally the board itself : 3 buttons, IR receiver, 24V power

    Circuit board with wires and electronic components. Close-up of an electronic board with three buttons and an IR receiver, along with connected wires. Circuit board with three buttons and colored wires.

    As we can see, everything is driver by Do output. Cold/warm channels are not used .

    The backup from original BK7231N fw is ok but no way to retrieve the conf : "Failed to extract keys" with BK7231Flasher

    readResult...-10-09.zip (1.46 MB)You must be logged in to download this attachment.

    after investigations, here are my results :

    PWM on P6 to control light
    REL on P8 to ON/OFF the 24V on the strip
    Buttons on P9 / P24 / P28
    and SM16703 on P16

    Right now, i can on/off the strip , Brightness is ok , IR Receiver ok, colors are ok ( BRG order )
    Buttons are working but each one acts as a toggle switch for the strip in the current conf.
    I didn't find yet how to control RGB from WHITE cool/warm are there is only one channel wired to the strip.

    Code: text Expand Select all Copy to clipboard
    "pins": {
    "6": "PWM;4",
    "8": "Rel;20",
    "9": "Btn;3",
    "16": "SM16703P_DIN;0",
    "24": "Btn;4",
    "26": "IRRecv;0",
    "28": "Btn;50"
  },


    Regards.
  • ADVERTISEMENT
  • #2 21333653
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    Was Cool/Warm color working with Tuya app?

    So there is only VDD, GND and DATA going to strip? I see W (warm) and C (cool) pads not soldered...
    Helpful post? Buy me a coffee.
  • #3 21334397
    snakesrules94
    Level 8  
    Posts: 37
    Help: 3
    Rate: 4
    Hello,
    yes, white cool/warm was ok within tuya app. You could choose either color and select, or white and select cool/warm.
    Indeed, only gnd/gnd and Do line between the controller and the strip, C/W pads on the PCB are not used.

    Regards.
  • #4 21338334
    snakesrules94
    Level 8  
    Posts: 37
    Help: 3
    Rate: 4
    Hello,
    I've reflashed original FW this morning to check :

    Close-up of an LED strip with three diodes and power markings.

    When using RGB mode, only led 1 is used
    When using cool white mode, only led 2 is used
    When using warm white mode, only led 3 is used
    When using other white mode, leds 1 & 2 are used

    24V is always present when using the strip.

    I have a very basic Gabtronic Xscope on the computer but not sure what to check as there is only one output on the PCB and every action on the remote seems the same on the scope screen .

    Screenshot of the Gabotronics Xscope interface showing a signal graph.
  • ADVERTISEMENT
  • Helpful post
    #5 21338404
    divadiow
    Level 38  
    Posts: 4859
    Help: 424
    Rate: 860
    I appreciate this isn't a direct help, but here's a bit more info. the storage area in that firmware contains the following after pairing with the Tuya app, when it pulls more information down. It does not contain any pin data, which from previous experience and what others have said, means the pin mappings are hardcoded into the firmware.

    Code: JSON
    Log in, to see the code


    just more info rather than a help
  • #6 21338479
    snakesrules94
    Level 8  
    Posts: 37
    Help: 3
    Rate: 4
    I'm not a signal analysis expert, but could it be possible that the frequency change to drive RGB or white part on the same pin? It could make sense with the 2 IC on the strip, one for each "color"?

    From what I can monitor, I sometimes see some frequencies at 400Hz, sometimes 533Hz and sometimes 800Hz, but as told before, I only have basic equipment and not sure at all about the readings.
  • #7 21344971
    twoenter
    Level 4  
    Posts: 7
    snakesrules94 wrote:
    I'm not a signal analysis expert, but could it be possible that the frequency change to drive RGB or white part on the same pin? It could make sense with the 2 IC on the strip, one for each "color"?

    From what I can monitor, I sometimes see some frequencies at 400Hz, sometimes 533Hz and sometimes 800Hz, but as told before, I only have basic equipment and not sure at all about the readings.


    Yesterday I've tried to make the strip work with WLED, without the tuya controller. Just the strip connected to a ESP32 with WLED firmware. With some settings the strip lit up when I connected it, but none of the possible settings led to a fully working addressable ledstrip. Still I want to connect it to Home Assistant with addressable options like in WLED.

    After this I tried flashing the same esp32 with esphome. I used the following config:
    Code: text Expand Select all Copy to clipboard
    
spi:
  mosi_pin: 16
  clk_pin: 18

light:
  - platform: spi_led_strip
    num_leds: 3
    id: rgb_led
    name: "RGB LED Strip"
    data_rate: 1MHz


    It seemed to be working but after giving a command the strip lighted up in the requested color and I think the esp32 blew up and is not accesible anymore.

    For now I've connected it to the official Tuya integration with the original firmware of the controller on it. But there are no options for segments/partitions...

    What I understand is that the device cloudcuttable is via cloudcutter. There is no esphome yaml available yet. So I searched further, I came up to this page: https://esphome.io/components/light/beken_spi_led_strip.html and make separate segments with https://esphome.io/components/light/partition.html

    In the list with supported chips is the SM16703. But P16 must be available on the chip. My question: is P16 available on the chip, and maybe you can test it by flashing esphome to it? If P16 is not available, maybe spi_led_strip may work? I can test it also by myself but I want to have the possibility to revert back to original firmware. Is that possible with you attached file in the previous post?
  • ADVERTISEMENT
  • #10 21345443
    divadiow
    Level 38  
    Posts: 4859
    Help: 424
    Rate: 860
    oh. yes. it's what looks like a discussion about the same LED strip in the WLED Discord
  • #11 21345456
    snakesrules94
    Level 8  
    Posts: 37
    Help: 3
    Rate: 4
    I have this message with the link

    Graphic displaying the message NO TEXT CHANNELS with additional information about the lack of access to text channels on the server.
  • #12 21345460
    divadiow
    Level 38  
    Posts: 4859
    Help: 424
    Rate: 860
    what if you join the WLED Discord first? https://discord.com/invite/e2NW9hwPeV

    Added after 3 [minutes]:

    there's not a lot to see though. the conclusion was that WLED didn't support whatever it is. There was mention of WS2805 strips supporting two white channels but this mode didnt work either in WLED.
  • ADVERTISEMENT
  • #13 21345792
    twoenter
    Level 4  
    Posts: 7
    After rereading the whole topic I think the esphome approach will work because @snakesrules94 said there is a SM16703 on pin 16. I will try cloudcutter and flash it to esphome with my config above
  • #15 21348244
    twoenter
    Level 4  
    Posts: 7
    What profile did you use to cloudcut the led strip @snakesrules94? I have bk7231n with version 1.0.2. All of the profiles I tried are not working.
  • #16 21348401
    snakesrules94
    Level 8  
    Posts: 37
    Help: 3
    Rate: 4
    >>21348244
    Hello, I didn't use cloudcutter to flash as the BK is directly accessible and flashable by UART.
  • #17 21355395
    User0815
    Level 6  
    Posts: 16
    Help: 1
    Rate: 4
    Hallo,

    meine Frage ist, ob Sie es schon geschafft haben, die RGB-Farben passend über die autoexec.bat zuzuordnen und ob Sie sie veröffentlichen könnten.
  • #19 21360449
    twoenter
    Level 4  
    Posts: 7
    Now I am soldering the strip in parts with some lan cables between it. I'm facing some issues with broken strip parts. Some parts are working but uncontrollable, with brightness of all LEDs 100%, others stay always on if 24v is supplied. Don't know the reason for this.

    On the chip I can see the chip number: gzx16703 Damaged LED strip with visible components and chip gzx16703.
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion revolves around converting the LSC 3203632.1 RGB/C + CCT/C LED strip to work with OpenBeken firmware. Users share their experiences with flashing the BK7231N chip, noting challenges with the LED strip's functionality when interfaced with various firmware, including Tuya, WLED, and ESPHome. Key observations include the strip's operation in different color modes, the presence of unutilized pads on the PCB, and the need for specific configurations to achieve full control over the addressable LEDs. Some users report successful flashing and integration with Home Assistant, while others face issues with unresponsive or malfunctioning LED segments. The conversation also touches on the technical aspects of signal frequencies and pin mappings related to the LED control.
Generated by the language model.
Today's popular

FAQ

TL;DR: LSC 3203632.1 is a 5 m strip built from 25 sections; “everything is driver by Do output.” OpenBeken maps P6 PWM, P8 relay, and P16 SM16703 DIN with BRG order; IR and buttons are usable. Backup works, but BK7231Flasher can’t extract keys from stock. [Elektroda, snakesrules94, post #21332211]

Quick Facts

What hardware and wiring does the LSC 3203632.1 use?

It uses a BK7231N controller with 24 V input, three buttons, and an IR receiver. The 5 m strip is built from 25 sections with two small black ICs per section. The controller drives the strip over a single DO data line. Cold and warm pads exist on the PCB but are unused on this unit. [Elektroda, snakesrules94, post #21332211]

Can the strip output cool and warm white over a single DO line?

Yes on stock Tuya firmware. The controller selects different LED dies per mode. RGB uses LED1, cool white uses LED2, warm white uses LED3, and mixed white uses LEDs 1 and 2. The 24 V rail remains on throughout. [Elektroda, snakesrules94, post #21338334]

Whats the correct OpenBeken pin mapping for this controller?

Use P6 = PWM4 (dimming), P8 = Rel20 (24 V switching), P16 = SM16703P_DIN (data), P26 = IRRecv, and P9/P24/P28 for buttons. Set the color order to BRG. Expert note: “colors are ok ( BRG order ).” [Elektroda, snakesrules94, post #21332211]

How do I configure OpenBeken for this board (3-step quick setup)?

  1. Assign pins: P6 PWM4, P8 Rel20, P16 SM16703P_DIN, P26 IRRecv, P9/P24/P28 buttons.
  2. Set color order to BRG, then save.
  3. Power cycle, then test On/Off, brightness, IR, and colors. [Elektroda, snakesrules94, post #21332211]

How can I back up and restore the original Tuya firmware?

Connect by UART and make a full flash backup before changes. The original firmware was backed up successfully. BK7231Flasher returned “Failed to extract keys,” so stored keys weren’t retrievable. You can reflash the backup to restore stock behavior. [Elektroda, snakesrules94, post #21332211]

Does Cloudcutter work with BK7231N v1.0.2 on this device?

One user couldn’t find a working profile for BK7231N 1.0.2, and attempts failed. In that case, UART flashing is the practical alternative. [Elektroda, twoenter, post #21348244]

Is P16 available for SM16703 with ESPHome/OpenBeken?

Yes. The strip’s data line is on P16. Assign the SM16703 DIN role to P16 to drive the LEDs. This mapping enabled color and brightness control. [Elektroda, snakesrules94, post #21332211]

Can WLED drive this LSC RGBIC+CCT strip right now?

Attempts did not produce a fully working setup. A WLED Discord thread concluded it wasn’t supported. The WS2805 dual-white mode didn’t help either during tests. [Elektroda, divadiow, post #21345460]

What does the DO signal look like across different modes?

A user observed frequency shifts while changing modes. Measured values included about 400 Hz, 533 Hz, and 800 Hz. This suggests the controller varies signaling by mode on the same pin. Use a proper scope for confirmation. [Elektroda, snakesrules94, post #21338479]

What LED driver IC is on the strip segments?

A chip labeled “gzx16703” was identified on at least one segment during inspection. This label was seen after issues arose while reworking segment wiring. [Elektroda, twoenter, post #21360449]

Why can19t tools read the Tuya pin mapping from flash?

After pairing, the storage area contained no pin configuration. As an expert summarized, “pin mappings are hardcoded into the firmware.” You must define pins manually in OpenBeken. [Elektroda, divadiow, post #21338404]

Does the onboard relay actually cut power to the strip?

Yes, when configured in OpenBeken. Assign P8 to the Rel20 role to switch the strip’s 24 V rail. That provides a hard power cutoff independent of data. [Elektroda, snakesrules94, post #21332211]

Can I integrate this strip with Home Assistant?

Yes. One user flashed OpenBK, then ESPHome, and achieved full control in Home Assistant. They noted it works and planned some software polish. [Elektroda, twoenter, post #21359164]

What if a segment is stuck 100% bright or always on after rework?

A user reported uncontrollable parts locked at full brightness and others always on with 24 V applied. These symptoms point to a damaged or miswired segment. Re-check data-direction arrows, continuity, and reflow solder joints on affected parts. [Elektroda, twoenter, post #21360449]
Generated by the language model.
ADVERTISEMENT