logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

[BK7231T/WB3S] Globe Electronics WiFi RGB Smart Strip Light - 50278

lurch892 1602 3

TL;DR

  • Globe Electronics WiFi RGB Smart Strip Light 50278 is a 3m USB-powered RGB LED strip sold at Menards for $8.99 USD.
  • Flashing had to be done via serial because CloudCutter did not work, likely because the firmware was too new.
  • The pin config maps 6 to dInput;0 and 9, 24, 26 to PWM;1, PWM;2, PWM;3.
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):

  • Globe Electronics WiFi RGB Smart Strip Light
    Purchased at Menards (US) for $8.99 USD
    3m of RGB LED lights, powered by USB

    Flashing had to be done via serial - cloudcutter didn't work as the firmware may be too new.
    Pin Config
    "6": "dInput;0",
    "9": "PWM;1",
    "24": "PWM;2",
    "26": "PWM;3"

    Electronic module with WB3S chip showing CE and RoHS markings.

    Part of the smart RGB lighting strip circuit with connected wires.

    Black label on an electronic device with model and country of manufacture information.


    Cool? Ranking DIY
    About Author
    lurch892
    Level 3  
    Offline 
    lurch892 wrote 3 posts with rating 2. Been with us since 2023 year.
  • ADVERTISEMENT
  • #2 20882976
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14564
    Help: 654
    Rate: 12576
    Thanks, I can also see your pull request:
    https://github.com/OpenBekenIOT/webapp/pull/69/files
    I will accept it but next time please also fill "module" field

    Added after 4 [minutes]:

    I also changed dInput to Btn_SmartLED
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #3 20883334
    lurch892
    Level 3  
    Posts: 3
    Rate: 2
    Thanks! Sorry about missing data - my brain was just trying to get GitHub to behave. I managed to submit (and then close) a pull request that wanted to merge with the whole main branch.

    Would "module" in this case be the "WB3S" chip or something different? I see I left "board" as "TODO" because I didn't know what to put there - if it was any identifier for the board the chip was attached to, or the name of the chip that isn't BK7231T/N.

    I will probably end up submitting again and would like to do it as best as possible. I've been watching a few stores for any cheap smart devices to liberate from the cloud.
  • #4 20883480
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14564
    Help: 654
    Rate: 12576
    It should be WB3S, we are making per-board statistics and search function as well.

    Please submit any other devices we have, we want to reach 500 entries soon, thanks!
    Helpful post? Buy me a coffee.
Reply Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):
Report a violation of the law
Today's popular

FAQ

TL;DR: For OpenBeken users converting a 3 m USB RGB strip light, serial flashing worked while CloudCutter failed because the “firmware may be too new.” Use the posted pin map for Globe Electronics model 50278 to restore RGB control when OTA methods do not work. [#20880891]

Why it matters: This thread gives a working fallback path for a cheap US smart strip light when newer firmware blocks the easier CloudCutter route.

Method Result in this thread Stated reason Best use here
Serial flashing Worked Direct wired flashing was required Use this on the Globe 50278
CloudCutter Failed Firmware may be too new Avoid for this exact unit

Key insight: The most useful takeaway is simple: for this Globe strip, trust the serial method and the shared pin map. The maintainer also confirmed that the module field should be set to WB3S for database submissions.

Quick Facts

  • Globe Electronics WiFi RGB Smart Strip Light model 50278 was bought at Menards in the US for $8.99 USD. [#20880891]
  • The strip length is 3 m, and the light is powered by USB, which matters when planning test power during flashing. [#20880891]
  • The posted RGB mapping uses pin 9 = PWM1, pin 24 = PWM2, and pin 26 = PWM3. [#20880891]
  • The original input setting used pin 6 = dInput;0, then the maintainer changed that input to Btn_SmartLED. [#20882976]
  • For OpenBeken webapp submissions, the maintainer said the module field for this device should be WB3S and noted the project wanted to reach 500 entries soon. [#20883480]

How do I flash the Globe Electronics WiFi RGB Smart Strip Light 50278 with OpenBeken over serial when CloudCutter doesn’t work?

Use serial flashing, not CloudCutter, for this Globe Electronics 50278 strip. The thread says CloudCutter did not work and that flashing had to be done over serial.
  1. Flash the device over serial.
  2. Apply the posted pin map after flashing.
  3. Use pin 9, 24, and 26 as PWM outputs for RGB.
This is the only confirmed working method in the thread for the 3 m USB-powered strip. [#20880891]

Why might CloudCutter fail on the Globe Electronics WiFi RGB Smart Strip Light if the firmware is too new?

CloudCutter may fail because this unit appears to have firmware newer than the exploit path expected by that method. The thread states that CloudCutter did not work and gives “firmware may be too new” as the reason, so serial flashing became necessary instead. [#20880891]

What pin configuration should I use for the Globe Electronics WiFi RGB Smart Strip Light with a BK7231T or WB3S module?

Use the posted configuration: pin 6 as input, pin 9 as PWM1, pin 24 as PWM2, and pin 26 as PWM3. The exact map shared for this device was 6 dInput;0, 9 PWM;1, 24 PWM;2, and 26 PWM;3, which gives three PWM channels for RGB control. [#20880891]

How should the button input be configured on this smart strip light: dInput or Btn_SmartLED?

Configure the button as Btn_SmartLED, not the earlier generic dInput entry. The maintainer explicitly said they changed dInput to Btn_SmartLED after reviewing the submitted configuration, so Btn_SmartLED is the corrected OpenBeken setting for this device. [#20882976]

What should I enter in the "module" field when submitting a WB3S-based device to the OpenBeken webapp database?

Enter WB3S in the module field. The maintainer answered this directly and said the project uses that field for per-board statistics and search, so WB3S is the correct module value for this strip’s submission. [#20883480]

What is the difference between the "module" and "board" fields when adding a new device entry for OpenBeken?

The thread only confirms that the module field should contain WB3S and does not define the board field fully. The submitter left board as TODO because they were unsure whether it should be a board identifier or a chip name, and no final board-field rule was given in the discussion. [#20883334]

How do I identify whether my smart LED controller uses a WB3S module or another BK7231-based board?

Use the hardware marking and then record the module as WB3S when that module is present. The thread’s maintainer confirmed WB3S as the correct module entry for this device, but the posts do not provide a broader identification method for other BK7231-based boards. [#20883480]

CloudCutter vs serial flashing for BK7231T and WB3S devices — which method is better when dealing with newer firmware?

Serial flashing is the better method when newer firmware blocks CloudCutter. In this case, CloudCutter failed, while serial flashing worked on the Globe Electronics strip, making serial the confirmed path for firmware that is “too new.” [#20880891]

What is a WB3S module in Tuya or BK7231 smart devices?

“WB3S” is a wireless module category that identifies the plug-in radio board used inside a smart device, and it serves as the value entered in OpenBeken’s module field for statistics and search. In this thread, the maintainer confirmed WB3S as the correct module designation for the strip controller. [#20883480]

What is Btn_SmartLED in OpenBeken, and how is it different from a generic dInput setting?

“Btn_SmartLED” is an OpenBeken button-input role that assigns a smart-light-specific function to a hardware input, unlike a generic dInput setting that only declares a basic digital input. The maintainer changed this strip’s pin 6 setting from dInput to Btn_SmartLED, so Btn_SmartLED is the more specific mapping here. [#20882976]

How can I safely power and test a 3 m USB-powered RGB smart strip light while flashing it over serial?

Keep the setup on its normal USB power path and use serial only for flashing access. The thread confirms this strip is 3 m long, USB-powered, and required serial flashing, but it does not give extra electrical limits, current figures, or bench-power instructions beyond those facts. [#20880891]

What steps should I follow to submit a new smart device correctly to the OpenBeken GitHub webapp, including module and board details?

Submit the device with the module field filled and verify the pull request before sending it. A practical thread-based sequence is:
  1. Add the device entry and pin data.
  2. Set the module field to WB3S when that is the module.
  3. Review the pull request so it does not target the whole main branch by mistake.
The board field remained unclear in this discussion, so do not guess it without better device-specific information. [#20883334]

Where can I buy low-cost Globe Electronics or similar cloud-based smart devices in the US for OpenBeken testing and conversion?

Menards is one confirmed US retailer from this thread. The posted device was bought there for $8.99 USD, and the submitter also said they were watching a few stores for cheap cloud-based smart devices to convert, but no other store names were listed. [#20880891]

What do PWM channel assignments like pin 9 PWM1, pin 24 PWM2, and pin 26 PWM3 control on an RGB strip light?

They control the strip’s three RGB lighting channels. The thread maps pin 9 to PWM1, pin 24 to PWM2, and pin 26 to PWM3, which is the standard three-output arrangement needed to drive red, green, and blue levels on this Globe strip light. [#20880891]

How can I troubleshoot a failed or incorrect GitHub pull request when adding a new OpenBeken device template?

Close the bad pull request, correct the metadata, and resubmit cleanly. The submitter said they accidentally created and then closed a pull request that tried to merge the whole main branch, and the maintainer also asked them to fill the module field next time. [#20883334]
Generated by the language model.
ADVERTISEMENT