A teardown covers the Energy+ (Home Connect) Smart LED CCT GU10 5W, a Finnish-market smart bulb rated 400 lm and 3000-6500K.
Inside, it uses a WBLC5 module with BK7231T, and Tuya extraction mapped LED Cool to P26 and LED Warm to P24.
The bulb shipped with Tuya firmware V2.9.16, and the Tuya section starts at 2023424, so OpenBKT flashing via tuya cloudcutter is possible.
A generated script clears GPIOs and LFS, then assigns pin 26 to PWM channel 4 and pin 24 to PWM channel 5.
The main problem is control: the index-page toggle button does not switch the bulb on or off, while the status-page buttons do.
Generated by the language model.
Here is short "teardown" of Energy+ (Home Connect) Smart LED CCT GU10 5W. 400 lm, 3000-6500K.
This brand is exclusively in the Finnish market, so you probably won't ever find it abroad.
It had V2.9.16 Tuya firmware inside, so you can flash OpenBKT with tuya cloudcutter.
Device configuration, as extracted from Tuya:
- LED Cool (Channel 4) on P26
- LED Warm (Channel 5) on P24
Device seems to be using WBLC5 module, which is using BK7231T.
And the Tuya section starts, as usual, at 2023424
That's strange.... let's investigate this problem. How do those sliders in the Web App work for you? The ones in the Web App?
Is one linked to warm white brightness, and second to cool white brightness?
Or... [Read more]
Nimierkki
10 Dec 2023 09:31
Thanks for the fast reply @P.Kaczmarek2.
In Web App "status page", one is for cold white (4:0 role PWM) and second one (5:0 role PWM) is for warm white. I can turn them on/off and adjust them in Web App... [Read more]
p.kaczmarek2
10 Dec 2023 10:12
hmm what is the device template in the web app?
Can you try... changing channel 4 to 0 and channel 5 to 1 in the pins settings?
There might be a small logical error somewhere that I need to fix [Read more]
Nimierkki
10 Dec 2023 11:06
Thanks, changing channels was the key, now it's working like a charm :)
EDIT:
Channel 4 to 1 and Channel 5 to 0 was right one. [Read more]
p.kaczmarek2
10 Dec 2023 12:28
Still, it's a bug. Let me look into it. It should be fixed by evening. [Read more]
p.kaczmarek2
11 Dec 2023 12:51
@nimierkki I have submitted a fix for your issue, with future updates, it should always work, even with channels 4 and 5. Thank you for pointing out that issue to me! [Read more]
FAQ
TL;DR: This 5W, 400 lm GU10 teardown found a BK7231T-based WBLC5 bulb, and “changing channels was the key.” This FAQ helps OpenBeken users flash it with Tuya Cloudcutter and fix the index-page toggle bug by remapping the warm/cool channels on the web panel. [#20854582]
Why it matters: It turns one forum debugging thread into a fast, quotable fix for anyone converting a Tuya CCT GU10 bulb to OpenBeken.
Control path
Before channel fix
After channel fix
OpenBeken status page
Worked for on/off and both PWM sliders
Worked
Native HTML panel / index page
Bulb stayed off
Worked correctly
Channel assignment
4 and 5 caused panel mismatch
Channel 4 → 1, Channel 5 → 0 solved it
Key insight: The hardware mapping was correct, but the main web panel expected different logical channel ordering. Swapping channel 4 and 5 to channels 1 and 0 fixed control immediately, and a firmware fix was later submitted. [#20856249]
Quick Facts
Energy+ Home Connect Smart LED CCT GU10 is rated 5W, 400 lm, and 3000–6500K, so it is a tunable-white GU10 bulb rather than RGB. [#20853137]
The bulb used a WBLC5 module with a BK7231T chip, and the installed Tuya firmware version was V2.9.16. [#20853137]
The extracted Tuya config mapped cool white to P26 and warm white to P24; the generated OpenBeken script set both pins to PWM. [#20853137]
The JSON showed pwmhz = 1000, which indicates a 1000 Hz PWM setting in the original configuration. [#20853137]
A full 2MB dump was shared, and the Tuya data section was reported to start at 2023424 in that dump. [#20853137]
How do I flash OpenBeken on an Energy+ Home Connect Smart LED CCT GU10 5W with BK7231T using Tuya Cloudcutter?
Use Tuya Cloudcutter, because this bulb was reported with Tuya firmware V2.9.16 and was explicitly said to be flashable that way. 1. Identify the bulb as a WBLC5 / BK7231T device. 2. Extract the Tuya config to get pin data like P26 and P24. 3. Apply an OpenBeken script that sets both pins to PWM and assigns the CCT channels. [#20853137]
Why does the toggle button on the OpenBeken index page not work for this Energy+ GU10 bulb while the status page controls do?
The index page failed because its logical channel handling did not match this bulb’s working PWM setup. The status page could still control both white channels directly, so warm and cool sliders worked there while the native HTML panel left the bulb off. The maintainer called it “a bug” and later submitted a fix. [#20856249]
What pin mapping does the Energy+ Smart LED CCT GU10 5W use for warm and cool white channels on the WBLC5 module?
It uses P26 for cool white and P24 for warm white. The extracted Tuya configuration listed LED Cool (Channel 4) on P26 and LED Warm (Channel 5) on P24. The generated OpenBeken script then set both pins as PWM outputs. [#20853137]
Which channel settings fixed the OpenBeken web panel control issue on this BK7231T GU10 bulb?
The working fix was to set Channel 4 to 1 and Channel 5 to 0. An earlier suggestion mentioned changing them, but the confirmed working combination was posted afterward as the correct one. After that change, the bulb worked “like a charm” from the main panel. [#20854582]
What is the WBLC5 module, and how is it related to the BK7231T chip in Tuya-based smart bulbs?
“WBLC5 is a module that uses the BK7231T chip, acting as the bulb’s Tuya-compatible Wi‑Fi control hardware.” In this teardown, the device “seems to be using WBLC5 module, which is using BK7231T,” so WBLC5 is the module name and BK7231T is the SoC inside it. [#20853137]
What is Tuya Cloudcutter, and when should I use it instead of opening the bulb and flashing directly?
“Tuya Cloudcutter is a flashing method that targets supported Tuya firmware without requiring immediate hardware disassembly, using the device’s existing firmware path.” In this case, the thread says to use it because the bulb had Tuya V2.9.16 inside and could be flashed with OpenBeken that way. [#20853137]
How can I extract a device configuration JSON from Tuya firmware and convert it into an OpenBeken setup script?
Extract the Tuya device JSON, then map its pin fields into OpenBeken commands. Here, the JSON exposed fields such as module = WBLC5, c_pin = 26, w_pin = 24, and pwmhz = 1000. That was converted into a script with ClearIO, lfs_format, stopDriver *, and setPinRole plus setPinChannel lines for pins 26 and 24. [#20853137]
Why would channel 4 and channel 5 work from the OpenBeken status page but fail on the native HTML panel?
They worked on the status page because that page directly controlled the two PWM outputs, but the native HTML panel used a different logical interpretation for CCT control. The maintainer suspected “a small logical error,” which matches the fact that swapping channel assignments fixed the panel while the raw status controls already worked. [#20854519]
What does it mean when the Tuya section starts at 2023424 in a full 2MB firmware dump?
It means the Tuya configuration area begins at offset 2023424 inside the shared 2MB flash dump. That location matters because it tells you where the device settings were found, including fields like firmware version, module name, PWM frequency, and pin assignments. The post states that offset directly. [#20853137]
How should I configure PWM roles and channels for a CCT bulb in OpenBeken so brightness and color temperature work correctly?
Configure both white outputs as PWM pins, then use the channel order that matches the web UI logic. For this bulb, pin 26 and pin 24 were both set to PWM, and the working web-panel mapping became Channel 4 → 1 and Channel 5 → 0. That combination restored proper control for the CCT interface. [#20854582]
OpenBeken status page vs native HTML panel for CCT bulbs — what is the difference and which one should control warm and cool white properly?
The status page exposed two direct PWM sliders, and on this bulb they controlled cold white and warm white correctly before any fix. The native HTML panel is the simplified main interface, but here it did nothing until the channel order was corrected. After remapping, the native panel also controlled the bulb properly. [#20854481]
What firmware version was found inside the Energy+ Smart LED CCT GU10 5W, and why does that matter for OpenBeken flashing?
The bulb contained Tuya firmware V2.9.16. That matters because the teardown explicitly says this version could be flashed to OpenBeken with Tuya Cloudcutter, making the version a practical compatibility clue for the chosen flashing path. The same version also appeared in the extracted JSON as swv and dev_swv. [#20853137]
How can I troubleshoot a BK7231T smart bulb that stays off when controlled from the main web interface but responds on the status page?
First, confirm the PWM pins work from the status page; this bulb responded there for both white channels. Next, check whether the native panel is using the wrong logical channel order. Finally, swap the assignments; for this device, Channel 4 → 1 and Channel 5 → 0 fixed the “stays off” behavior on the main page. [#20854582]
What safety precautions should I take when tearing down and flashing a mains-powered GU10 smart bulb?
The thread does not provide any safety procedure, so it cannot support a step-by-step safety checklist. What it does confirm is that this was a GU10 mains bulb opened for teardown and firmware work. If you need electrical safety guidance, this specific thread is not the source for it. [#20853137]
Where can I buy or identify the Energy+ Home Connect GU10 bulb if it is a Finland-only brand, and what similar BK7231T bulbs should I look for instead?
The thread only says the Energy+ brand is “exclusively in the Finnish market,” so you may not find the exact bulb abroad. For identification, the useful thread markers are Home Connect, GU10, 5W, 400 lm, 3000–6500K, and a WBLC5 / BK7231T Tuya design. The thread does not name any alternative retail models. [#20853137]
Comments
That's strange.... let's investigate this problem. How do those sliders in the Web App work for you? The ones in the Web App? Is one linked to warm white brightness, and second to cool white brightness? Or... [Read more]
Thanks for the fast reply @P.Kaczmarek2. In Web App "status page", one is for cold white (4:0 role PWM) and second one (5:0 role PWM) is for warm white. I can turn them on/off and adjust them in Web App... [Read more]
hmm what is the device template in the web app? Can you try... changing channel 4 to 0 and channel 5 to 1 in the pins settings? There might be a small logical error somewhere that I need to fix [Read more]
Thanks, changing channels was the key, now it's working like a charm :) EDIT: Channel 4 to 1 and Channel 5 to 0 was right one. [Read more]
Still, it's a bug. Let me look into it. It should be fixed by evening. [Read more]
@nimierkki I have submitted a fix for your issue, with future updates, it should always work, even with channels 4 and 5. Thank you for pointing out that issue to me! [Read more]