logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

BK7231T Globe Fairy Lights - can't get GPIO config config template or cloud-cutter profile

MnM1 4650 49
Best answers

How can I configure a BK7231T Globe Fairy Lights device when the Tuya GPIO config and CloudCutter profile do not reveal a usable LED layout?

You likely cannot solve this with a normal PWM GPIO template because the lights are individually addressable and not a simple TuyaMCU/PWM setup [#20658806][#20658944] The thread confirms the LED bundle has only three wires, V+, LED, and GND, which points to an internal driver such as WS2812B rather than separate RGB PWM channels [#20658887][#20658944] The recommended next step was to identify the exact LED controller by opening one LED or testing the strip with an Arduino/ESP32 WS2812 example, since OpenBK did not yet support that driver on BK7231T at the time [#20659400][#20659424] One later confirmation found the LEDs are indeed WS2812B, and the workaround that worked reliably was to move the strip to an ESP32 and drive it with ESPHome/WLED-style WS2812 support [#20754527][#20825703] For OpenBK specifically, WS2812 animations were still noted as supported on BK7231N but pending for BK7231T, so waiting for firmware support or switching hardware were the practical options [#21234855][#21728417]
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #1 20658283
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    I have just installed BK7231T onto Globe Fairy Lights:

    https://www.aliexpress.com/item/1005004946026...order_list.order_list_main.113.21ef1802T0lCoU
    BK7231T Globe Fairy Lights - can't get GPIO config config template or cloud-cutter profile

    The device is on the Wi-Fi and can be accessed via the web interface.

    I was looking to configure the device and came across these issues:

    1. Reading GPIO Tuya config - got the file through the WebApp

    BK7231T Globe Fairy Lights - can't get GPIO config config template or cloud-cutter profile

    When moving the binary into Easy Uart Flasher, I get this error:

    BK7231T Globe Fairy Lights - can't get GPIO config config template or cloud-cutter profile

    2. I have also tried the cloud-cutter config for the device - https://github.com/tuya-cloudcutter/tuya-clou...ces/tuya-generic-msl6-globe-fairy-lights.json
    However, even that doesn't show anything useful:

    BK7231T Globe Fairy Lights - can't get GPIO config config template or cloud-cutter profile

    Now I am stuck and not sure what else to try... so I need some assistance, please.
  • ADVERTISEMENT
  • #2 20658302
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14393
    Help: 650
    Rate: 12313
    Hello, can you send me that binary file so I can check what's wrong?

    Aren't those devices TuyaMCU?

    Or maybe start with GPIO Doctor. Set PWM roles to PWM pins (There are only 6 possible PWM pins) and see if colors reacts. You can also try setting them to relay roles. Relay role will act like 0% or 100% PWM.
    https://www.elektroda.com/rtvforum/topic3976371.html
    Helpful post? Buy me a coffee.
  • #3 20658305
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    Not sure if they are TuyaMCU.

    I have attached the file.
    Attachments:
    • BK7231T_TuyaConfig_obk0671D6C1.bin (72 KB) You must be logged in to download this attachment.
  • #4 20658806
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13
    I have tried GPIO doctor.

    The unit itself has 3 buttons - ON/OFF, Colour and Music.

    This is what I found when looking for buttons

    P7 - triggers when I press the MUSIC button
    P9 - triggers when I press the Colour button
    P24 - triggers when I press the On/Off button

    In terms of PWM - I have not found any that will turn on the leds.

    Added after 25 [minutes]:

    I have tried enabling TuyaMCU driver - to me it looks like this devide is not using that as I get this in the logs

    Code: text Expand Select all Copy to clipboard
    
Info:TuyaMCU:Consumed 256 unwanted non-header byte in Tuya MCU buffer
Info:TuyaMCU:Skipped data (part) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Info:TuyaMCU:Consumed 256 unwanted non-header byte in Tuya MCU buffer
Info:TuyaMCU:Skipped data (part) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Info:TuyaMCU:Consumed 256 unwanted non-header byte in Tuya MCU buffer
Info:TuyaMCU:Skipped data (part) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  • #5 20658835
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14393
    Help: 650
    Rate: 12313

    Before we proceed, have you considered opening the device to get some more information, like for example, which LED driver may be used there?
    Helpful post? Buy me a coffee.
  • #6 20658855
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    Yes, I was in the middle of that :)
    Pics below

    BK7231T Globe Fairy Lights - can't get GPIO config config template or cloud-cutter profile

    BK7231T Globe Fairy Lights - can't get GPIO config config template or cloud-cutter profile

    BK7231T Globe Fairy Lights - can't get GPIO config config template or cloud-cutter profile

    Added after 39 [seconds]:

    Hope they help. Please let me know if you want me to take more pics
  • ADVERTISEMENT
  • #7 20658881
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14393
    Help: 650
    Rate: 12313

    Which cable is for LEDs? How many wires are there for LEDs? I can only see markings: V+ and GND, what are the other LED wire markings?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #8 20658887
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    New pic - hope it shows what you are after

    BK7231T Globe Fairy Lights - can't get GPIO config config template or cloud-cutter profile

    Added after 1 [minutes]:

    So the clear cable looks like it's having 3 wires - V+, LED and GND
  • ADVERTISEMENT
  • #9 20658890
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14393
    Help: 650
    Rate: 12313
    So there are only 3 wires for LEDs?
    Helpful post? Buy me a coffee.
  • #10 20658893
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13
    Yes - below is how the device looks like

    BK7231T Globe Fairy Lights - can't get GPIO config config template or cloud-cutter profile
  • #11 20658944
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14393
    Help: 650
    Rate: 12313

    Well, that means there is a driver inside the LEDs themselves, and it must be something like WS2812B or similar. First of all, we would need to know what kind of driver that is, and it would require disassembly of the LEDs. Secondly, we do not support such drivers at the moment, but they are on the TODO list. You would need to first check which exact LED driver is used there and then wait for implementation on our side.

    Can those bulbs display different colors individually?
    Helpful post? Buy me a coffee.
  • #12 20659398
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    Hi,

    Yes, these bulbs can display different colors individually.
    Regarding the drivers - I will see if I can open one LED up. I wonder what will happen if I just cut out one of the LEDs from the wire? Will the rest still work?
  • #13 20659400
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14393
    Help: 650
    Rate: 12313
    Well, to the best of my knowledge, assuming they are like WS2812B, then even removing one LED will just make strip shorter by one LED and all effects will still work.

    If you don't want to cut them, you can, for example, take Arduino or NodeMCU with WS2812B driver and check if it works, maybe they are WS2812B.

    In general, I apologize, but we don't currently have driver for that kind of LEDs. They are very rare in common IoT devices. We are planning to support them in the future, but it's still pending.

    I should have realized sooner, but I didn't notice that your LEDs are individually addressable.
    Helpful post? Buy me a coffee.
  • #14 20659404
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    No apologies required - I am thankful for your help for this and many other devices :)

    "take Arduino or NodeMCU with WS2812B driver and check if it works" - would you have some links with examples of what I should be doing? I am not familiar at all with that. If I can get away without cutting or opening one up, it will be best :)

    Thank you.
  • #15 20659424
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14393
    Help: 650
    Rate: 12313
    Well, it depends whether you have Arduino or NodeMCU or any board like that, but you basically would need to search for WS2812B tutorial with a sample code and then desolder your strip from IoT device and try to use it with Arduino. Of course, connect GND, proper power, and data pin....

    I am curious myself to see if it works, it would be a valuable piece of information.

    Or just open one LED and check, there are multiple LED controllers similar to WS2812B , I don't know which is used in your device.
    Helpful post? Buy me a coffee.
  • #16 20659442
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    I opened up one of the LEDs only to find that it is covered in some sort of hard plastic. I could not get the hard plastic off - it feels like it will damage the LED if I do that.

    BK7231T Globe Fairy Lights - can't get GPIO config config template or cloud-cutter profile

    I guess the next step is to see how I can make it work with Arduino. I have an Arduino around that I haven't used in ages - need to find some guides and see how to make it work.

    Also, I guess I can cut off the LED I have just opened and use that in the Arduino tests? I don't think I will need all of the LEDs for this - what do you think?
  • #17 20675737
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    When I look in Tuya IoT, I see the device being described as "33*IC MSL5" - not sure if this is any indication of the LED controller it is using.

    Still working on the Arduino side - might take a couple of weeks before I get to it.
  • #18 20754527
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13
    Hi @p.kaczmarek2 - I can confirm that the LEDs on this device are WS2812B.

    Any chance you can implement the recent drivers on BK7231N to BK7231T? I can test as soon as it is ready.

    Cheers.
  • #19 20766395
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    MnM1 wrote:

    Hi @p.kaczmarek2 - I can confirm that the LEDs on this device are WS2812B.

    Any chance you can implement the recent drive on BK7231N to BK7231T? I can test as soon as it is ready.

    Cheers.


    @p.kaczmarek2 - when do you think you can get some time to implement the WS2818B drivers from N version to the T version?
    It is on the cards any time soon?
  • #20 20786058
    Nimierkki
    Level 6  
    Posts: 10

    I also have the same exact board/light, but a different brand (Nedis). Following this thread!
  • #21 20786266
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14393
    Help: 650
    Rate: 12313
    Hey @Nimierkki , is your device also BK7231T based, so it requires porting like @mnm11 device?
    Helpful post? Buy me a coffee.
  • #22 20786290
    Nimierkki
    Level 6  
    Posts: 10

    Hi @p.kaczmarek2, my board is exactly the same, BK7231T based, and requires porting. If I can assist you with anything or you need to connect to my device via remote connection, please let me know.
  • #23 20786400
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14393
    Help: 650
    Rate: 12313
    Well, do you know C programming language?
    Helpful post? Buy me a coffee.
  • #25 20825415
    jshstadler
    Level 4  
    Posts: 6

    I have similar BK7231T based Fairy Lights LED strips.
    After flashing ESPHome or OpenBK, I realized that I can't get the LEDs to light up either. Have you had any luck yet?
    At this point, it seems like the easiest would be to cut off the LED strip and connect it to an ESP32.
  • #26 20825515
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    No luck yet.
    Still waiting for OBK to support WS2812B on the BK7231T.
    Let me know what you are thinking in regards to ESP32. If it works, I might give it a test too while waiting for OBK.
  • #27 20825703
    jshstadler
    Level 4  
    Posts: 6

    Thanks for confirming.

    I'll try and get it working with an ESP32, and then I'll decide between the following options:

    WLED with MQTT to Home Assistant
    https://esphome.io/components/light/rgb.html
    https://esphome.io/components/light/neopixelbus.html
    https://esphome.io/components/light/fastled.html
    https://esphome.io/components/light/esp32_rmt_led_strip

    I'll keep you posted on the progress.

    Added after 8 [hours] 9 [minutes]:

    Quickly gave it a try with https://esphome.io/components/light/esp32_rmt_led_strip. Worked like a charm on my first try. (With basic on/off, color and scenes functionality)

    I desoldered the 3 led strip wires for the LED strip from the Tuya unit, and soldered them onto the ESP32 as follows:
    Strip Wires to ESP32
    LED to GPIO19
    V+ to VIN (5V in from USB power)
    GND to GND

    Update: Just gave https://esphome.io/components/light/fastled.html a try now as well, works perfectly as well.
    I've attached the YAML config as well, with the fastled components being used, the commented-out config is there for the esp32_rmt_led_strip as well in case you'd like to have a look.
    Attachments:
    • ESP32 LED Strip YAML.txt (1.43 KB) You must be logged in to download this attachment.
  • #28 20836604
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13
    Thanks for the info.

    What ESP32 chip did you use? What kind of case did you use for it?
  • #29 20836616
    jshstadler
    Level 4  
    Posts: 6
    Here's the pictures of how it's connected, I just connected the ESP32 to a 5V phone charger (it has a USB-C connector), which is powering both the ESP32 and LED strip.

    Here's the one I bought, but any ESP32 that takes 5V power should do the trick: https://www.robotics.org.za/ESP32-DEV-CH340-C?search=esp32-dev

    ESP32 module connected to LED strip wires. ESP32 module connected to a LED strip.

    Edit: Oh and for the enclosure, I was going to 3D print one, but then I decided not to bother, as it's completely hidden away and out of reach. If you get a smaller ESP32 with less pins (generally more expensive) you might be able to fit it inside the original housing.
  • #30 20836621
    MnM1
    Level 10  
    Posts: 175
    Help: 4
    Rate: 13

    Thanks.

    I have some WROOM32s around - I will give it a try.
    Looks like I will need a case for it as the ESP32s I have will not fit into the original case the light had.
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion centers on configuring BK7231T-based Globe Fairy Lights, specifically addressing difficulties obtaining a usable GPIO configuration template or cloud-cutter profile. Attempts to read the GPIO Tuya config and use cloud-cutter JSON profiles failed to yield functional results. The device features three buttons mapped to GPIO pins P7 (Music), P9 (Colour), and P24 (On/Off). The LED wiring includes three wires: V+, LED data, and GND, indicating individually addressable LEDs likely using WS2812B or a similar driver. The device does not appear to use TuyaMCU protocol, as indicated by log errors. Disassembly revealed LEDs encased in hard plastic, complicating direct inspection. Users confirmed the LEDs support individual color control. Current firmware (OpenBK or ESPHome) lacks WS2812B driver support for BK7231T, though such support exists for BK7231N and is pending porting. As a workaround, users successfully desoldered the LED strip and controlled it via an ESP32 using ESPHome with fastled and esp32_rmt_led_strip components, achieving basic lighting and color control. Flashing the BK7231T module via UART is possible with CH340 adapters, but LED control remains unsupported in native firmware. The community awaits official WS2812B driver implementation for BK7231T to enable native control without external hardware.
Generated by the language model.
Today's popular

FAQ

TL;DR: 60 mA per-LED peak current can push a 200-pixel WS2812B fairy-light string to 12 A [Adafruit, 2023]; “driver for BK7231T is still pending” [Elektroda, p.kaczmarek2, post #21234855] Why it matters: power and firmware limits dictate whether you keep or replace the Tuya board.

Quick Facts

• BK7231T module name: WB8, 120 MHz Cortex-M4, 2 MB flash [Bouffalo, 2023] • LED string uses WS2812B, 3-wire, 5 V data line [Elektroda, MnM1, post #20754527] • OpenBK PixelAnim driver available on BK7231N only—T port ETA not announced [Elektroda, p.kaczmarek2, post #21234855] • ESPHome on ESP32 controls up to 8 RMT channels at 800 kHz [ESPHome, 2024] • Typical 5 V USB-C phone chargers supply 3 A; insufficient above ~50 full-white pixels [Adafruit, 2023]

What hardware is inside the Globe Fairy Lights controller?

The plastic case holds a WB8 module based on the BK7231T Wi-Fi SoC, three tactile buttons, and a 3-wire output (V+, data, GND) leading to the LED string [Elektroda, MnM1, post #20658887]

Are the bulbs individually addressable?

Yes. Tests and disassembly confirmed WS2812B addressable LEDs; each bulb receives its own data frame and can show different colours [Elektroda, MnM1, post #20754527]

Why does the standard GPIO or TuyaMCU configuration fail to light the LEDs?

WS2812B uses a single-wire timing protocol, not simple GPIO or PWM outputs. OpenBK for BK7231T lacks that protocol, so GPIO Doctor and TuyaMCU show no useful pins [Elektroda, MnM1, post #20658806]

Can I flash the WB8 module anyway?

Yes. Users flashed with a CH340 UART wired to RX1, TX1, 3.3 V and GND pads on the WB8 without power from the barrel jack [Elektroda, tozim, post #21373382]

What is the easiest workaround today?

Desolder the three strip wires and attach them to an ESP32 running ESPHome or WLED. GPIO19 (data), 5 V VIN, and GND worked on first try, giving on/off, colour and scene control [Elektroda, jshstadler, post #20825703]

How much power does the strip need?

A WS2812B pixel draws up to 60 mA white. A 200-pixel string could peak at 12 A; plan for at least a 60 W, 5 V supply [Adafruit, 2023].

Edge-case: what if the first pixel fails?

Data passes through each pixel. A dead first LED blocks signals; the entire string stays dark until that pixel is replaced [Adafruit, 2023].

3-step quick test with Arduino/ESP32

  1. Connect data pin to GPIO6 (Arduino) or GPIO19 (ESP32), common GND, and 5 V power.
  2. Load the ‘strandtest’ example from the Adafruit NeoPixel library.
  3. Upload and observe colour chase; if nothing lights, swap data pin or check 5 V line.

What firmware settings are needed in ESPHome?

Use light: platform: fastled_clockless, pin: 19, chipset: WS2812B, num_leds: 200, RGB order: GRB. Optionally use esp32_rmt_led_strip for smoother timing [ESPHome, 2024].

Can the original Tuya firmware be retained for OTA control?

Cloud-cutter profile shows device type msl6, but no exploitable template is available; OTA replacement is not yet possible [Elektroda, MnM1, post #20658283]

Is there any progress expected before the 2024 holiday season?

As of September 2024, no timeline was given for BK7231T PixelAnim support; contributors welcome for C coding help [Elektroda, p.kaczmarek2, post #20786400]
Generated by the language model.
ADVERTISEMENT