FEIT Smart WiFi Light Strip - Model: FETAPE/RGBW/CNTRSC - FCC ID: SYW-TAPRGBWCNTRSC - 7231N

Wonko 10473 96

#31 20492825 16 Mar 2023 20:14

Wonko Wonko

Level 4

Post #31

20492825 16 Mar 2023 20:14

Hi, I'm trying to get a working build environment set up - but the instructions are a little confusing.

It seems that the SDKs are submodules of the App - but in the set instructions it says to set up the SDK directory and clone the app directly into it - resulting in sdk within app within sdk again.

And also there is no "N" App - only a "T" app - but it mentions it might need to be renamed?

Sorry if I am missing something obvious. I am trying to build on Raspbian Linux (ARM 32-bit).

I tried following the docker build instructions with same results.
It would be awesome to have a fully complete docker build environment on docker hub!

When I try to run ./b.sh it fails:

pi@Pi3b31:~/openbk/OpenBK7231T $ ./b.sh
APP_PATH=apps/OpenBK7231T_App
APP_NAME=OpenBK7231T_App
APP_VERSION=1.0.0
USER_CMD=
Calling original build_app.sh script
cd /home/pi/openbk/OpenBK7231T/apps/OpenBK7231T_App/../../platforms/bk7231t/toolchain/../bk7231t_os && sh build.sh OpenBK7231T_App 1.0.0 bk7231t 
From build.sh, variables are:
APP_BIN_NAME=OpenBK7231T_App
APP_VERSION=1.0.0
TARGET_PLATFORM=bk7231t
USER_CMD=
Start Compile
system:Linux
removing .o files from our folders, and OUR .o and .d files from Debug
find: ‘../../../apps/OpenBK7231T_App/src/hal/*.c’: No such file or directory
find: ‘../../../apps/OpenBK7231T_App/src/sim/*.c’: No such file or directory
find: ‘../../../apps/OpenBK7231T_App/src/libraries/*.c’: No such file or directory
find: ‘../../../apps/OpenBK7231T_App/src/libraries/Arduino-IRremote-mod/*.c’: No such file or directory
find: ‘../../../apps/OpenBK7231T_App/src/libraries/Arduino-IRremote-mod/src/*.c’: No such file or directory
find: ‘../../../apps/OpenBK7231T_App/src/libraries/Arduino-IRremote-mod/src/private/*.c’: No such file or directory
find: ‘../../../apps/OpenBK7231T_App/src/win32/*.c’: No such file or directory
find: ‘../../../apps/OpenBK7231T_App/src/win32/stubs/lwip/apps/*.c’: No such file or directory
not rm -rf ../tuya_common/src/*.o
not rm -rf ../tuya_common/src/driver/*.o
find: ‘../../../components’: No such file or directory
not is ci build
make[1]: Entering directory '/home/pi/openbk/OpenBK7231T/platforms/bk7231t/bk7231t_os'
make[2]: Entering directory '/home/pi/openbk/OpenBK7231T/platforms/bk7231t/bk7231t_os'
echo prerequirement0
prerequirement0
===========================================================
Build OpenBK7231T_App
===========================================================
echo prerequirement1
prerequirement1
mkdir -p Debug/obj
mkdir -p Debug/bin
echo prerequirement2
prerequirement2
build beken378/app/app_bk.o
../toolchain/gcc-arm-none-eabi-4_9-2015q1/bin/arm-none-eabi-gcc: 1: Syntax error: word unexpected (expecting ")")
make[2]: *** [application.mk:808: beken378/app/app_bk.o] Error 2
make[2]: Leaving directory '/home/pi/openbk/OpenBK7231T/platforms/bk7231t/bk7231t_os'
make[1]: *** [Makefile:5: mp] Error 2
make[1]: Leaving directory '/home/pi/openbk/OpenBK7231T/platforms/bk7231t/bk7231t_os'
make: *** [Makefile:6: all] Error 2

ADVERTISEMENT
#32 20492932 16 Mar 2023 20:52

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #32
20492932 16 Mar 2023 20:52

As readme says, the BK7231T_App is now a shared app, for all SDKs.

If docker solution fails, ask here, the Michael Kamprath is a Docker support author:
https://github.com/openshwprojects/OpenBK7231T_App/issues/732

Or maybe just fork the App repository and just use online github build - you will get them as well when you fork. You can easily then go to build details and download binaries, even if you don't run the release mechanism. It will automatically build for all platforms so you will also know if the other chips are still working after your changes (or at least compiling).

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#33 20493886 17 Mar 2023 12:18

Wonko Wonko

Level 4

Topic author Helpful post? (0)

Post #33
20493886 17 Mar 2023 12:18

Alright, that’s a lot easier.

Pull request created.

At this point everything works great. Do I need to do anything to get this tear down and configuration posted?
ADVERTISEMENT
#34 20493897 17 Mar 2023 12:22

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #34
20493897 17 Mar 2023 12:22

Hmm, so it was tested:

I'd personally just cast to integer with (int) and use %i, but if it works with our lightweight sprintf on Beken, then no problem, it's good as it is.

If the configuration is not posted, you can help me by:
1. getting config JSON from web app so I don't have to type it manually
2. maybe doing pull request here if you can:;
https://github.com/OpenBekenIOT/webapp/blob/gh-pages/devices.json
I usually do it myself and it takes time, so it's always nice if someone helps

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#35 20493926 17 Mar 2023 12:36

Wonko Wonko

Level 4

Topic author Helpful post? (0)

Post #35
20493926 17 Mar 2023 12:36

So I understand the process:

Copy the json with pin config from the web app.
Manually update the todo fields, links, etc. (link to this topic URL?}
Create pull request to add json entity to the project you linked.

Done?
#36 20493976 17 Mar 2023 12:59

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #36
20493976 17 Mar 2023 12:59

Yes... that's what needs to be done.

I also merged your first PR - the one with Discovery. Thanks!

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#37 20494007 17 Mar 2023 13:33

Wonko Wonko

Level 4

Topic author Helpful post? (0)

Post #37
20494007 17 Mar 2023 13:33

The only ones I can’t figure are flags and command.

Is this just an integer bitmask of all active flags? Mine doesn’t populate in the web app - and new_pins.h doesn’t define any flags above bit 9?

Also, web app doesn’t capture “command” but it’s listed in readme?

Added after 14 [minutes]:

PR for json created.
#38 20495739 18 Mar 2023 13:44

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #38
20495739 18 Mar 2023 13:44

Thank you for the pull request, it looks correct.

I am working on web app these days and I will try to fix bugs, please tell me what is exactly wrong, if you can. I will investigate.

Wonko wrote:

Is this just an integer bitmask of all active flags? Mine doesn’t populate in the web app - and new_pins.h doesn’t define any flags above bit 9?

It seems the flags field is missing indeed. I will add it today. But what do you mean with "above bit 9"?

Maybe you are confusing generic flags with logger flags.
Flags doc:
https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/flags.md

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#39 20502204 21 Mar 2023 22:44

Wonko Wonko

Level 4

Topic author Helpful post? (0)

Post #39
20502204 21 Mar 2023 22:44

How is the Flags field supposed to work in the web app?

Mine is blank even though I have several flags enabled - some are important to match the Pin Mappings - like how Flag 24 is needed for RGB+WW in order to work with color channels.

My expectation would be that the flags are a 64-bit mask and the value would be a single hex number that incorporates them all?
#40 20502229 21 Mar 2023 23:00

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #40
20502229 21 Mar 2023 23:00

Flags weren't exposed in older versions, an update from two or so days ago should fix it.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#41 20502236 21 Mar 2023 23:06

Wonko Wonko

Level 4

Topic author Helpful post? (0)

Post #41
20502236 21 Mar 2023 23:06

Ah, I see it is showing up now in the JSON - although flag 37 does not show up - Is that supposed to be missing?
Are there other exceptions?
Would it make more sense to use 0x values rather than decimal?
ADVERTISEMENT
#42 20503346 22 Mar 2023 18:57

bobthemonkee bobthemonkee

Level 5

Helpful post? (0)

Post #42
20503346 22 Mar 2023 18:57

I hope this isn't a thread hijack, but I have this LED strip controller in the BK7231T variant. It is running 1.1.71 firmware. Any ideas on configuration for this one?
#43 20503351 22 Mar 2023 18:58

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #43
20503351 22 Mar 2023 18:58

Do you have a 2MB flash dump for that one?

@Wonko if a flag is not included into the json template, then it's most likely a bug. I will check it out. Maybe... maybe the flags over 32 are not included somehow.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.

#44 20503415 22 Mar 2023 19:28

Wonko Wonko

Level 4

Post #44

20503415 22 Mar 2023 19:28

>>20503346
Cloudcutter does have a matching firmware version for the 7231T - so my bet is it will work.
The one funny thing about Cloudcutter is that even if it's the completely wrong device, as long as the firmware version and type of chip match, it is supposed to work.

When you go through the process it will give you a choice of manufacturers for that version like this: (I selected your firmware version on my Cloudcutter installation so you can see the path I took to get there.)

[?] How do you want to choose the device?: By firmware version and name
   By manufacturer/device name
 > By firmware version and name
   From device-profiles (i.e. custom profile)

[?] Select the firmware version and name: 1.1.71 - BK7231T / bk7231t_common_user_config_ty
   1.1.6 - BK7231T / oem_bk7231s_strip_ty
   1.1.6 - BK7231T / oem_bk7231s_switch1_zero_kjd
   1.1.7 - BK7231N / CL_DREAM_RGB_STRIP_19KEY_1KEY_5V_BK7231N
   1.1.7 - BK7231N / oem_bk7231n_ceiling_light_ty
   1.1.7 - BK7231N / oem_bk7231n_plug
   1.1.7 - BK7231T / oem_bk7231s_light_pir_ty
 > 1.1.71 - BK7231T / bk7231t_common_user_config_ty
   1.1.8 - BK7231N / oem_bk7231n_plug
   1.1.8 - BK7231T / oem_bk7231s_rnd_switch
   1.1.80 - BK7231T / bk7231t_common_user_config_ty
   1.1.9 - BK7231N / oem_bk7231n_water_sensor_plus
   1.1.9 - BK7231T / bk7231s_common_iot_config_ty
   1.1.9 - BK7231T / oem_bk7231s_ceiling_light_ty

[?] Select the brand of your device: MartinJerry
 > MartinJerry
   Mlambert
   TreatLife
   Tuya Generic

It makes no difference which manufacturer device you choose - it should work.

Let us know how it goes!

#45 20503624 22 Mar 2023 21:08

bobthemonkee bobthemonkee

Level 5

Helpful post? (0)

Post #45
20503624 22 Mar 2023 21:08

>>20503351

I just grabbed a 2mb dump from another one I had not flashed yet. I don't think it was reset, so is it safe to send to you?

>>20503415

I actually did manage to flash one of them. OBK works just fine and says it is connected. I just can't figure out the pin configuration to make the lights work. They are just solid white or off based on the switch position.

I used the only 1.1.71 Tuya Generic profile to get it flashed.
#46 20503635 22 Mar 2023 21:13

Wonko Wonko

Level 4

Topic author Helpful post? (0)

Post #46
20503635 22 Mar 2023 21:13

Open an issue on the Cloudcutter Github and attach your dump here:

https://github.com/tuya-cloudcutter/tuya-cloudcutter/issues

Read their instructions for how to submit one - and be aware if it's ever been on your WiFi and the not factory reset, the SSID and Password of the WiFi it as connected to are in cleartext in the dump.

All of that said - I'm still pretty sure you can just flash the latest OpenBeken 7231T firmware using Cloudcutter - you just have to copy the Cloudcutter flash image into your ~/tuya-cloudcutter/custom-firmware/ folder and choose the right firmware file.
#47 20503659 22 Mar 2023 21:27

bobthemonkee bobthemonkee

Level 5

Helpful post? (0)

Post #47
20503659 22 Mar 2023 21:27

Thanks for the heads up. I was successful at flashing already...just can't figure out the pin configuration to make them work properly.

I do have another dump for a different device on cloudcutter github right now
#48 20503679 22 Mar 2023 21:33

Wonko Wonko

Level 4

Topic author Helpful post? (0)

Post #48
20503679 22 Mar 2023 21:33

Ooooh, well that's the easy part.

You can do it totally by trial and error.

Basically your PWM pins will look something like this:

"pins": {
"6": "PWM;4",
"7": "PWM;2",
"8": "PWM;1",
"9": "PWM;0",
"26": "Btn_SmartLED;0"
}

(This is my LED strip)

The only PWM pins are 6, 7, 8, 9, 25, 26 - and those can be assigned to:

PWM;0 = Red
PWM;1 = Green
PWM;2 = Blue
PWM;3 = CW (If you have it)
PWM;4 = WW

Note that if your LED strip does not have CW you need to enable flag 24 in order for it to behave properly.

And in my case Pin 26 is the Smart Button that turns the light on and off and dims it.

You can literally bounce back and forth between the Web App and the native UI testing out different PIN configurations until you have it right.

Make sense?
#49 20503906 23 Mar 2023 00:01

bobthemonkee bobthemonkee

Level 5

Helpful post? (0)

Post #49
20503906 23 Mar 2023 00:01

For sure! That is the same way I figured out the pin config for my other Feit RGB light bulbs.

This seems to be different though. The button works like normally to turn on and off the strip. OBK stays connected to wifi with both, as long as the module is plugged in. None of the pins you listed do anything. The leds are just solid soft white. Nothing I've found will change the light colors or state of the lights. No idea why
#50 20503928 23 Mar 2023 02:13

Wonko Wonko

Level 4

Topic author Helpful post? (0)

Post #50
20503928 23 Mar 2023 02:13

Could be one of those fancy data/clk things rather than PWM. What other chips are on that board?
#51 20503937 23 Mar 2023 03:51

bobthemonkee bobthemonkee

Level 5

Helpful post? (0)

Post #51
20503937 23 Mar 2023 03:51

Unfortunately I think that is the case. Looks like I have a few more chips than your version

I assume the 219A chip is the controller....but that his a HUGE assumption, considering I'm still figuring this stuff out.

I should have bought the black box rather than the white and blue one :/
ADVERTISEMENT
#52 20503943 23 Mar 2023 04:51

Wonko Wonko

Level 4

Topic author Helpful post? (0)

Post #52
20503943 23 Mar 2023 04:51

Can you make out any markings on that 20-pin chip?
#53 20504015 23 Mar 2023 07:51

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #53
20504015 23 Mar 2023 07:51

@bobthemonkee can you check if the MCU-looking chip is connected to BK7231 via RX1/TX1 lines? If so, the it's a TuyaMCU, but don't worry, it's already supported by OpenBeken! You will just need to figure dpIDs.
Btw, here is BK7231 piniout:
BK7231 datasheet, pinout, programming, specification, wiki (BK7231T, BK7231N)

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#54 20507671 25 Mar 2023 13:21

bobthemonkee bobthemonkee

Level 5

Helpful post? (0)

Post #54
20507671 25 Mar 2023 13:21

I was not able to figure out which pins to check. I thought I checked all of them against RX1 and TX1 on diode setting of my fluke, but got nothing. Any other hints? Would love to get these things working![/u]
#55 20508763 26 Mar 2023 01:52

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #55
20508763 26 Mar 2023 01:52

So maybe create autoexec.bat with "startDriver TuyaMCU", reboot device and just see if it receives anything?
Can you show more photos of your device?

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#56 20522235 03 Apr 2023 02:02

bobthemonkee bobthemonkee

Level 5

Helpful post? (0)

Post #56
20522235 03 Apr 2023 02:02

I tried the autoexec for TuyaMCU and the logs show that it is receiving heartbeat. So, how do I go about finding the dpID?
#57 20545656 18 Apr 2023 17:35

bobthemonkee bobthemonkee

Level 5

Helpful post? (0)

Post #57
20545656 18 Apr 2023 17:35

Some better pictures. I still haven't figured these things out. Any other ideas that might help? Thanks in advance!
#58 20545677 18 Apr 2023 17:48

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

Helpful post? (0)

Post #58
20545677 18 Apr 2023 17:48

There are two options:
1. when still on tuya firmware, you can do uart packets capture for our tuyamcu analyzer: https://www.elektroda.com/rtvforum/topic3970199.html#20528459
2. after flashing openbeken, if your device has buttons, etc, connected to tuyamcu, you can try pressing them and see what is being sent back to wifi module from mcu

if your device features single direction communication, from wifi module to tuyamcu, then option 1 is mostly the way to go

There may be also third option, maybe you could remove mcu and route PWM gpio of bk directly to the MOSFETs, but it depends on the device and soldering skills you have.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
#59 20557828 27 Apr 2023 17:43

rjfmn rjfmn

Level 2

Helpful post? (0)

Post #59
20557828 27 Apr 2023 17:43

@p.kaczmarek2

I have the same unit as bobthemonkee (cracked it open to verify the board), still on stock firmware, and I'd like to get it going with HA as well. I'm happy to do the option 1 packet capture you mentioned but I haven't done any Tuya Cloudcutter stuff yet. Raspberry Pis and (lately) ESP32s are more my area.

I'm thinking I should just be able to connect my UART to VCC,GND,TX1,RX1 and capture to help get the answers we need. Does that sound right, or do you think I'd need to use the 24V supply and just use GND,TX1,RX1?

Thanks!
#60 20558038 27 Apr 2023 20:17

bobthemonkee bobthemonkee

Level 5

Helpful post? (0)

Post #60
20558038 27 Apr 2023 20:17

Yay! I'm not the only one now! haha

I currently have one soldered up with TX, RX, GND, and 3.3. I was able to see stuff in the RealTerm app, but it kept freezing when I tried to capture data, so I couldn't get to the Tuya Analyzer part. I eventually gave up. But, I can at least confirm that I was seeing a stream of some sort of data.

I can definitely confirm that it runs OpenBeken no problem. I have one of them already flashed and used Cloudcutter to do it.
Create an account, log in and become active in a forum and ads will not appear. You will receive points by participating in discussions.
Join this discussion.

Install the application

Reply Cool? Ranking DIY | New topic

Notify about new articles

Report a violation of the law

Topic summary

The discussion centers on the FEIT Smart WiFi Light Strip (Model: FETAPE/RGBW/CNTRSC, FCC ID: SYW-TAPRGBWCNTRSC, chipset BK7231N) and its integration with OpenBK firmware and Home Assistant (HA). Key points include the necessity of using the native interface over the web app for proper RGBW (warm white) control, requiring flag 24 to correctly handle the RGBW channels as a single light rather than separate lights. Pin assignments for PWM channels and the smart button (pin 26) were identified, with PWM pins 6, 7, 8, and 9 mapped to PWM4 (warm white), PWM2 (green), PWM1 (blue), and PWM0 (red) respectively. Firmware updates fixed earlier issues with flag 24 and HA discovery.

The thread also covers challenges in flashing and debugging the BK7231N chip, including damaged diagnostic pads and the need for external probes. Users shared methods for flashing via Raspberry Pi UART and Cloudcutter, and discussed the use of TuyaMCU for devices with additional MCU chips, including capturing UART data to identify dpIDs for LED control. The TuyaMCU setup command and autoexec.bat configurations were shared to enable LED color control and button functionality.

Further discussion addressed Home Assistant integration, specifically the handling of color temperature ranges (Mired and Kelvin units), with the introduction of the CTRange command to set min/max Mired values for accurate adaptive lighting support. The web app's YAML generator was deprecated in favor of HA discovery, which now supports 4 PWM channels with the simulate white flag.

Issues with the physical smart button not updating HA state were resolved by adding firmware support for receiving dpID 20 toggle events, enabling state synchronization between the device and HA. Users also reported improved WiFi performance and local control responsiveness with OpenBK firmware compared to native Tuya firmware.

Additional troubleshooting involved devices with different hardware configurations, including those with extra chips requiring TuyaMCU communication, and the need for UART packet captures to map dpIDs. The community shared resources such as BK7231 datasheets, pinouts, and firmware repositories to assist in device configuration and flashing.

Overall, the discussion provides detailed technical guidance on flashing, configuring, and integrating the FEIT Smart WiFi Light Strip with OpenBK firmware and Home Assistant, addressing PWM pin mapping, flag settings, TuyaMCU integration, color temperature handling, and button state synchronization.
Summary generated by the language model.

FAQ

TL;DR: Flashing the FEIT FETAPE/RGBW/CNTRSC strip with OpenBeken converts 5 / 5 test units from “poor” to “good” Wi-Fi balance while keeping full RGBW control — “This firmware significantly improves the WiFi performance” [Elektroda, Wonko, post #20471373] Why it matters: better signal means fewer drops and faster Home-Assistant updates.

Quick Facts

• Chipset: Beken BK7231N 4 × PWM + 1 Btn, 2 MB flash [Elektroda, Wonko, post #20471373]
• Safe supply: 24 V DC, galvanically isolated; flash over RX1 TX1 GND CEN pads [Elektroda, Wonko, post #20471373]
• Working pin map: 6→PWM4, 7→PWM2, 8→PWM1, 9→PWM0, 26→Btn_SmartLED [Elektroda, Wonko, post #20474832]
• Required flags: 9 10 12 24 27 28 (set Flag 24 for RGBW grouping) [Elektroda, Wonko, post #20475831]
• Home-Assistant auto-discovery fixed in commit 8741e40 (4-PWM) [Elektroda, p.kaczmarek2, post #20475261]

How do I flash the strip without desoldering?

Power the controller from its own 24 V DC brick. 2. Solder or clip to RX1, TX1, GND and CEN test pads. 3. Use tuya-cloudcutter profile “Feit TAPE16-RGBW-RP 1.0.9” and upload the latest OpenBeken-7231N binary. Wonko verified this on five units [Elektroda, Wonko, post #20471373]

What JSON pin configuration works for RGBW?

{"pins":{"6":"PWM;4","7":"PWM;2","8":"PWM;1","9":"PWM;0","26":"Btn_SmartLED;0"}}. Be sure Flag 24 is ON or Home-Assistant will split the lamp into four channels [Elektroda, Wonko, post #20474832]

Home-Assistant shows four sliders, not one. Fix?

Upgrade to firmware ≥ commit 8741e40 and rerun scheduleHADiscovery. The patch recognises 4-PWM + emulated white and publishes a single light entity [Elektroda, p.kaczmarek2, post #20475261]

Why does the strip blink warm-white after power-up?

TuyaMCU still advertises pairing mode. Add “tuyaMcu_defWiFiState 4” to autoexec.bat to force the MCU into normal Wi-Fi-OK state [Elektroda, jzhvymetal, post #20845411]

Button toggles light but HA state stays wrong — workaround?

Update to commit 5f66f0b2 or newer; it listens for dpID 20 and publishes state. Older builds only transmitted, not received, causing desync [Elektroda, p.kaczmarek2, post #20783699]

How do I calibrate colour-temperature range?

Send CTRange ; e.g. “CTRange 370 153”. Values propagate to UI and HA; min/max also appear in MQTT discovery since PR #993cd60 [Elektroda, Wonko & p.kaczmarek2, #20477493].

Is the BLE handheld remote supported?

No. OpenBeken ignores the strip’s internal Bluetooth radio, so the SYW-TAPRGBWREMSC beacon remote will not function [Elektroda, Wonko, post #20475831]

Edge case: I only see sensors in HA, no lights.

Run “scheduleHADiscovery 10” after you finish pin/flag setup, or simply reboot. Discovery sent before configuration contains only default telemetry topics [Elektroda, p.kaczmarek2, post #21468215]

Can I skip the 3.3 V wire when flashing?

Yes. Because the board is DC-only, its 24 V adapter powers the regulator; you just need GND reference for UART [Elektroda, p.kaczmarek2, post #20474359]

What’s the fast-connect flag for?

Flag 27 stores AP credentials in flash and skips full scan, cutting reconnect time from ~4 s to ~1 s on BK7231N chips [OpenBeken docs].

Statistic: how much stronger is Wi-Fi after flashing?

Unifi logs show every flashed strip moved from Fair (≈-67 dBm) to Excellent (≈-53 dBm), a 14 dB gain ≈ 5× signal power [Elektroda, Wonko, post #20471373]

Failure scenario — what breaks discovery?

If you define PWM0-2-4 but leave PWM3 absent, older builds split the light and HA rejects CT support. Always enable Flag 24 or add a dummy PWM3 to avoid this bug [Elektroda, Wonko, post #20474832]

3-step: add TuyaMCU support for other variants

Capture UART at 9600 bps; look for dpIDs 20-26 headers 55 AA. 2. Flash OpenBeken and create autoexec.bat: startDriver TuyaMCU; tuyaMCU_setupLED 0. 3. Reboot and confirm RGBW works [Elektroda, p.kaczmarek2, post #20718322]