logo elektroda
logo elektroda
X
logo elektroda

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

Wonko 10296 96
ADVERTISEMENT
  • #91 20845411
    jzhvymetal
    Level 3  
    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
    
    [?] 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
    
    startDriver TuyaMCU
    tuyaMCU_setupLED 24 0
    


    This is what is displayed in the Log windows when the button is pressed
    
    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:

    
    startDriver TuyaMCU
    tuyaMcu_defWiFiState 4
    tuyaMCU_setupLED 24 0
    
    
  • ADVERTISEMENT
  • #92 20845553
    p.kaczmarek2
    Moderator Smart Home
    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.
  • ADVERTISEMENT
  • #93 21462114
    kadeross
    Level 2  
    My home assistant discovery is only showing sensors off the MQTT topic, and no switches or lights. Any idea why that would be
  • ADVERTISEMENT
  • #95 21462491
    kadeross
    Level 2  
    >>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  
    >>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
    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.

Topic summary

The discussion revolves around the FEIT Smart WiFi Light Strip (Model: FETAPE/RGBW/CNTRSC) and its integration with Home Assistant (HA) using the OpenBK7231T firmware. Users share experiences regarding the setup, including the necessity of using the native interface instead of the web app for RGBW functionality, and the importance of setting flag 24 for proper operation. Issues with pin configurations, UART communication, and the functionality of the smart button are addressed. Users also discuss capturing UART data for TuyaMCU integration and troubleshooting light control issues. Solutions include using specific commands in the autoexec.bat file to enable LED control and linking dpIDs for button functionality to reflect changes in HA.
Summary generated by the language model.
ADVERTISEMENT