logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

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

Wonko 13236 103

TL;DR

  • FEIT Smart WiFi Light Strip FETAPE/RGBW/CNTRSC on BK7231N was torn down and mapped for OpenBK/CloudCutter.
  • RGBW mode needs flag 24 in the native interface; the web app misreports status, and the BLE wireless remote still does not work.
  • The working pin map is 6=PWM;4, 7=PWM;2, 8=PWM;1, 9=PWM;0, plus 26=Btn_SmartLED;0, with no signal on pin 24.
  • Flashing through RX1, TX1, GND, and CEN worked without desoldering, and the 1.0.9 OpenBK update notably improved Wi‑Fi performance across five devices.
Generated by the language model.
ADVERTISEMENT
Report a violation of the law
Reply Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):
  • #91 20845411
    jzhvymetal
    Level 6  
    Posts: 7
    I have successfully flashed using tuya-cutter but when the controller boots it flashes the warm light until I press the button on the controller twice. After that it will allow me to control it from the webpage. Also the cool light does not work correctly. Am I missing something?

    Purchased: Costco
    Can not access serial pin as it is covered in black epoxy.
    Model: FETAPE/RGBW/CONT
    FCC ID: SYW-TAPRGBWCMTBM
    MCU: BK7231T


    I have successfully flashed using tuya-cutter
    Code: text Expand Select all Copy to clipboard
    
[?] 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.71 - BK7231T / bk7231t_common_user_config_ty


    I also added the following to the autoexec.bat
    Code: text Expand Select all Copy to clipboard
    
startDriver TuyaMCU
tuyaMCU_setupLED 24 0


    This is what is displayed in the Log windows when the button is pressed
    Code: text Expand Select all Copy to clipboard
    
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 01 F4 22 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 500
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 14 01 00 01 00 24 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 20, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 0
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 15 04 00 01 00 28 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 21, dataType 4-DP_TYPE_ENUM and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 0
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 16 02 00 04 00 00 01 F4 22 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 22, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 500
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 08 1A 02 00 04 00 00 00 00 31 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 15 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 26, dataType 2-DP_TYPE_VALUE and 4 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 4 int: 0
Info:TuyaMCU:TUYAMCU received: 55 AA 03 07 00 05 14 01 00 01 01 25 
Info:TuyaMCU:TuyaMCU_ProcessIncoming[ver=3]: processing command 7 (State) with 12 bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: processing dpId 20, dataType 1-DP_TYPE_BOOL and 1 data bytes
Info:TuyaMCU:TuyaMCU_ParseStateMessage: raw data 1 byte: 1


    Added after 3 [minutes]:

    I figured out the blinking. You need "tuyaMcu_defWiFiState 4" autoexec.bat. Tuya chip still thinks wifi needs to be configured on boot up.

    New autoexec.bat is as follows:

    Code: text Expand Select all Copy to clipboard
    
startDriver TuyaMCU
tuyaMcu_defWiFiState 4
tuyaMCU_setupLED 24 0
  • ADVERTISEMENT
  • #92 20845553
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12345
    Good job on resolving issue. I am seriously considering making tuyaMcu_defWiFiState 4 a default state because it seems..... it's always more required than I initially expected.
    Helpful post? Buy me a coffee.
  • #93 21462114
    kadeross
    Level 2  
    Posts: 3
    My home assistant discovery is only showing sensors off the MQTT topic, and no switches or lights. Any idea why that would be
  • ADVERTISEMENT
  • #94 21462176
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12345
    Which device, configuration, script?
    Helpful post? Buy me a coffee.
  • #95 21462491
    kadeross
    Level 2  
    Posts: 3
    >>21462176 (FEIT) Smart LED Light Strip (FETAPE/RGBW/CNTRSC)

    Current Device:
    UpTime: 27130s

    Build: Built on Mar 1 2025 05:19:31 version 1.18.51

    IP Address: 192.168.0.182

    MAC Address: 38:1f:8d:0e:83:18

    MQTT Server: 192.168.0.25:1883

    MQTT Topic: homeassistant

    Device Short Name: Bed_Light

    WEBAPP Url root: https://openbekeniot.github.io/webapp/

    Chipset: BK7231N

    Flags: 1080628359

    Version: 1.18.51

    Error: TypeError: Failed to fetch
  • ADVERTISEMENT
  • #96 21468053
    kadeross
    Level 2  
    Posts: 3
    >>21462176

    Here's what MQTT explorer gives me:

    Screen of the MQTT Explorer app showing details of the connection with the homeassistant device.
  • #97 21468215
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12345
    You have all LED topics visible, maybe you need to do Home Assistant discovery again. Maybe you did it before configuring the LED.
    Helpful post? Buy me a coffee.
  • #98 21629751
    jzhvymetal
    Level 6  
    Posts: 7
    I have this working with version 1.17.262, but when I upgrade to 1.18.134, it no longer accepts commands from the webpage. The weird thing is that the button on the unit still works to turn the LEDs on, and the status on the webpage reflects the change. However, I am unable to control it from the built-in webpage. Anyone have any suggestions?

    Purchased: Costco
    Can not access serial pin as it is covered in black epoxy.
    Model: FETAPE/RGBW/CONT
    FCC ID: SYW-TAPRGBWCMTBM
    MCU: BK7231T

    autoexec.bat
    startDriver TuyaMCU
    tuyaMcu_defWiFiState 4
    tuyaMCU_setupLED 24 0

    No Pin Configure as it using TuyaMCU driver
  • #99 21629841
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12345
    That's a lot of versions in between, would you be able to narrow down which version first breaks?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #100 21630106
    jzhvymetal
    Level 6  
    Posts: 7
    Ok took me a while but it is a more recent version where it stop working

    OpenBK7231T_1.18.143 Not Working

    OpenBK7231T_1.18.142 Working
  • #101 21630484
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12345
    Then it's this PR from user...
    https://github.com/openshwprojects/OpenBK7231...mmit/bc64926da307addfb856b1c482f88c81f71d2102
    Probably g_tuyaMCU_allowAutomaticSending should be 1 to maintain backwards compatibiltiy..

    EDIT: The command is tuyaMcu_enableAutoSend, this is for autoexec.bat, the one with g_ is used in C code
    Helpful post? Buy me a coffee.
  • #102 21630537
    jzhvymetal
    Level 6  
    Posts: 7
    >>21630484

    I tried OpenBK7231T_1.18.146 version with the following below and still does not respond to webpage. Back with OpenBK7231T_1.18.142 with tuyaMCU_allowAutomaticSending 1 or it also did not work with the line in autoexec.bat

    autoexec.bat
    startDriver TuyaMCU
    tuyaMCU_allowAutomaticSending 1
    tuyaMcu_defWiFiState 4
    tuyaMCU_setupLED 24 0
  • #103 21630611
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14408
    Help: 650
    Rate: 12345
    Sorry, can you repeat? Does it work with tuyaMcu_enableAutoSend 1 in autoexec.bat or does it not?
    The command is tuyaMcu_enableAutoSend, the global variable in code is with g_ prefix, command is not.
    tuyaMcu_enableAutoSend is the only change made between releases breaking stuff for you...

    tuyaMcu_enableAutoSend is reverted to default state 1, but built came today, 1.18.148
    Helpful post? Buy me a coffee.
  • #104 21630831
    jzhvymetal
    Level 6  
    Posts: 7
    >>21630611

    Thanks...That fixed the issues. tuyaMcu_enableAutoSend 1 in autoexec.bat does work.
Reply Cool? Ranking DIY | New topic
Notify about new articles
📢 Listen (AI):
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.
Generated by the language model.
Today's popular

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?

  1. 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]

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]

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

  1. 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]
Generated by the language model.
ADVERTISEMENT