logo elektroda
logo elektroda
X
logo elektroda

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

MnM1 3462 49
ADVERTISEMENT
  • ADVERTISEMENT
  • #32 21233172
    Nimierkki
    Level 4  
    Christmas is coming and light is still not running, any luck with this one without buying esp board ? :D
  • ADVERTISEMENT
  • #33 21234845
    jshstadler
    Level 4  
    >>21233172
    No, not as far as I'm aware.
    The experience with an ESP has been much more reliable so far than with the previous board and Tuya firmware. I'd say the ESP is worth it.
  • #34 21234855
    p.kaczmarek2
    Moderator Smart Home
    WS2812 with animations is supported by OBK on BK7231N platform, but T is still pending. See PixelAnim driver info: https://www.elektroda.com/rtvforum/topic4057187.html
    Helpful post? Buy me a coffee.
  • #35 21359022
    openbaker
    Level 2  
    Has there anyone been successful with flashing this WB8 module? I connected wires from the GND, RX1, TX1 test pins (see picture above #6) of the WB8 module to a Serial-UART adapter but was not able to flash. The module was powered via barrel socket, the adapter from USB. But even with several attempts to disconnect and reconnect the module from power the flasher application was not able to communicate. It seems btw that the wiring at least for TX1, RX1, Vcc and GND is the same as for the WB3S module. Now that we have the SPI driver integrated it would be cool if we could reflash the BK7231T chip.
  • #36 21373382
    tozim
    Level 4  
    >>21359022
    I managed to flash it without any issues, using a CH340 UART adapter connected to the measure points on the back for GND, 3.3V, RX1 and TX1 (the latter two switched on the UART adapter obviously), and without connecting the barrel plug.
    I haven't been able to get the LED string to work however.
  • ADVERTISEMENT
  • #37 21720184
    MnM1
    Level 10  
    I have updated to the latest ALT firmware for this device.
    It seems that WS2812 with animations is still not supported. Is this correct?

    With this latest firmware there was little progress - I get random led lights turning on upon reboot (while light, blue or red - a mix of these sometime) but I cant control anything (on/off, dimmer, rgb, speed or animations).
  • #39 21720688
    MnM1
    Level 10  
    Yeah saw that but no idea how to make it work. Guess I still need to wait till it makes it into the OBK firmware.
  • #40 21720699
    insmod
    Level 29  
    >>21720688
    It already did 2 months ago, but only in ALT firmware.
    I checked it on BK7231U, which is just an original non-Tuya BK7231T, and it worked fine.
    T OTA image - https://github.com/openshwprojects/OpenBK7231...ownload/1.18.194/OpenBK7231T_ALT_1.18.194.rbl

    And in autoexec or startup command and replace {LEDs} with how many LEDs you have:
    startDriver SM16703P
    SM16703P_Init {LEDs} GRB
    startDriver PixelAnim
  • #41 21720723
    divadiow
    Level 36  
    insmod wrote:
    T OTA image

    ah, maybe @MnM1 used download link in web gui and updated to latest old SDK? hence the direct link to ALT rbl..?
  • #42 21722225
    MnM1
    Level 10  
    The file I am using is called "OpenBK7231T_ALT_1.18.194.rbl" so I think is the correct one.
    Also I have the the correct lines in the autoexec file.

    As mentioned before nothing is happening hen I press buttons/sliders in the GUI
    All I get are some LEDs (not all of them) lighting up when I reboot the device. After each reboot the color of the LEDs are different (sometimes all white, other times some red, blue, yellow, sometime ALL LEDs white, etc).
    What I have noticed is that I have to press the Toggle Light button in the GUI and then preform a reboot for the LEDs to turn on (in the colors/manner mentioned above)
  • #43 21722531
    insmod
    Level 29  
    Re-checked on BK7231U.
    It works, but one bug is still there (last led in series is always on for me), and a new one - animations are bugged if brightness is higher than half.
    Is data pin connected to P16 on your board?
  • ADVERTISEMENT
  • #44 21722589
    MnM1
    Level 10  
    Not sure about P16 - I just flashed the firmware. Hardware wise is exactly the same as it was from factory, never changed anything.
  • #45 21727936
    Nimierkki
    Level 4  
    @MnM1, could you provide me your GPIO pin settings / flags?
    I still didn't get my fairy light to work / light up, maybe this Christmas :D

    Here is mine:

    Screenshot of GPIO pin settings with PWM assigned to pin 16OpenBK7231T configuration screen with startup commands for SM16703P driver
  • #46 21728138
    MnM1
    Level 10  
    Hi @Nimierkki - I have what you have in autoexec file (but with 33 leds that is what my device has).
    I don't have any other flags/GPIO/Settings done. I resisted moving to ESPHome as I really like the enclosure and power for this device, but come Christmas I will move to it if OBK does not support this device by then.
  • #48 21728417
    insmod
    Level 29  
    >>21728401
    It doesn't matter for beken, since the only SPI output is at P16.
    >>21728138
    As far as i know ESPHome doesn't support addressable leds for BK7231T.
    SPI_DAT is set to SPI_BASE + 3 * 4
    https://github.com/esphome/esphome/blob/6edbb...ponents/beken_spi_led_strip/led_strip.cpp#L28
    Which is a BK7231N and newer address.
    For earlier chips, like BK7231U, BK7231T and BK7252 it should be SPI_BASE + 2 * 4
    https://github.com/openshwprojects/OpenBK7231...bba9f1b1daf0dab3e/src/driver/drv_spidma.h#L33
  • #49 21728421
    divadiow
    Level 36  
    insmod wrote:
    It doesn't matter for beken, since the only SPI output is at P16.

    sure, but @MnM1's image also showed PWM set, so just to clear that (assuming that would manifest as an issue)
  • #50 21728868
    MnM1
    Level 10  
    >>21728401

    I have downloaded the one you linked and update to it (as I was running an earlier version). So yes I can confirm that.
    Set PIN16 too as suggested - no difference the issue is still there.

    After pressing some of the GUI buttons and rebooting the unit, white lights come (and sometimes RGB lights depending on what buttons I have pressed in the GUI before the reboot). These lights come on after the reboot by themselves and without me pressing anything. GUI shows all buttons off.

    >>21728417

    That is correct ESPHome does not support this chipset yet. But (as discussed earlier in this thread) and can move the LEDs to an ESP32 module and run it that way. I would lose the existing casing and power supply - that's why I have mentioned that is not an ideal solution.

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.
Summary generated by the language model.
ADVERTISEMENT