[BK7231N] LSC 3004919 GU10 RGBCW (Action store) smart LED bulb template and teardown

Hi all,

I have flashed before some LSC GU10 devices using the BK7231T version but now i bought some new ones which have the BK7231N chip and also another driver then the ones listed before.

For flasing using tuya-cloudcutter use the profile 1.3.21 BK7231N.
After flashing completes configure the module with the following options:
"24": "BP5758D_CLK;0",
"26": "BP5758D_DAT;0"

I have already two different versions with another map.
One default so no changes are required and the other one needs the following map (startup command):

Hi, do you mind sharing how you removed the leg pins and put it back together?
Is the bulb case still intact?

The case is broken and I just took one apart to see if I could flash it.
Maybe I can glue it back together, but I do not trust it anymore for production use because the casing is getting hot.

cobradevil wrote:

The case is broken and I just took one apart to see if I could flash it.
Maybe I can glue it back together, but I do not trust it anymore for production use because the casing is getting hot.

Good thing the firmware's not patched
These gu10 is a bit tricky to dismantle, thinking of getting this gu10 holder and just pull/tilt until the pins are removed securely

Thanks so much for your investment of breaking one device to share the knowledge with all of us and making it possible to use cloudcutter! It's so nasty that you can ALMOST see the chip through the glass but not really... and that they changed from T to N and to a different LED controller is just something you can't trial and error.

Two comments/tips:
1. Getting this very device into AP mode is a bit strange not really documented... turning it on/off six times like earlier versions and other bulbs doesn't even make it show up in the tuya app, nevertheless the blinking suggest that. Also compared to other devices this one seems to not have an EZ mode (which does not allow the cloudcutter exploit and is normally indicated by fast blinking), but the fast blinking actually is the AP mode needed for cloudcutter. The golden tip and solution was funnily enough found inside the tuya app: This device needs to be switched on/off three times so on-off-on-off-on-off-on
2. After the initial flashing FLAG 36 (Do not autostart any drivers) is activated, keeping the device from using the needed drivers. After I disabled this and using the above template and mapping the bulb worked flawlessly. Again, thanks a lot for sharing your findings!