logo elektroda
logo elektroda
X
logo elektroda

Teardown and Flashing Guide for SYLVANIA SmartPlus A19CCECWF RGBCT Bulb

rronnander 3624 17
ADVERTISEMENT
  • I have a bunch of these and decided to sacrifice one bulb so I could use cloudcutter on the others if it all works out. I was able to successfully flash the bulb using the cloudcutter method.

    Packaging of Sylvania SMART+ smart bulb with WiFi and color control features.

    Model name stamped on the base:

    Close-up of a smart LED bulb with visible model and specifications.

    The model name is a bit obfuscated with this one:

    Model: A19CCECWF (Printed on the base of the bulb itself, but this is nowhere to be found online or on LEDVANCE/SYLVANIA's website anywhere)
    SKU: 75663 (1-pack)
    SKU: 75674 (4-pack)
    product_id: 1ijupffokexbz0cl (Tuya / Sylvania product identifier found with [tuya-uncover](https://github.com/blakadder/tuya-uncover))

    Like all smart bulbs, they basically come apart the same way:

    Disassembled LED bulb with visible internal components.

    LED close up:

    LED board of a smart bulb with visible diodes.

    Board close up 1:

    Close-up of a circuit board with electronic components.

    Board close up 2 (thought I needed to get the capacitors out of the way to read the flash, but not needed):

    Close-up of a circuit board with electronic components and capacitors.

    WB8P BK7231T:

    Close-up of the internal components of a smart bulb with a visible WB8P module.

    Original firmware:

    sylvania-s...t-bulb.bin Download (2 MB)

    The only thing odd is the device configuration states it is a WB3S, however, the module is a WB8P. Maybe that's actually "normal"?

    I'll flash another fully functional bulb soon to try and see if I can get it dialed in with all of the RGBCT settings.

    Cool? Ranking DIY
    About Author
    rronnander
    Level 5  
    Offline 
    rronnander wrote 8 posts with rating 3, helped 2 times. Been with us since 2024 year.
  • ADVERTISEMENT
  • #2 20952709
    p.kaczmarek2
    Moderator Smart Home
    Thank you, but can you also please include a full JSON template from the Web App, so I can add this device to our list here: https://openbekeniot.github.io/webapp/devicesList.html
    Helpful post? Buy me a coffee.
  • #3 20953766
    rronnander
    Level 5  
    Here's the JSON:

    
    {
      "vendor": "SYLVANIA",
      "bDetailed": "0",
      "name": "SYLVANIA SmartPlus A19CCECWF RGBCT Bulb",
      "model": "A19CCECWF",
      "chip": "BK7231T",
      "board": "WB8P",
      "flags": "1024",
      "keywords": [
        "RGBCW",
        "A19CCECWF",
        "A19",
        "75663",
        "75674",
        "1ijupffokexbz0cl"
      ],
      "pins": {},
      "command": "",
      "image": "https://obrazki.elektroda.pl/7127409900_1707464379_thumb.jpg",
      "wiki": "https://www.elektroda.com/rtvforum/viewtopic.php?p=20952709"
    }
    
  • Helpful post
    #4 20953843
    Sunnysky
    Level 8  
    rronnander wrote:

    The only thing odd is the device configuration states it is a WB3S, however, the module is a WB8P. Maybe that's actually "normal"?


    Near as I can tell from comparing these boards is that the 8P has improved characteristics for antenna gain 2 dBi vs 1.2 and higher operating temp 105 'C vs 85'C with a new layout with I/O pins on 1 side vs 3 sides.
    Top view of an electronic module with an antenna and pins.
    Comparative schematic of two electronic boards with different pin layouts.

    Thus "normal" to use latest Revision. So they keep track of major revisions by changing the model # and firmware changes ought to be compatible but may have bugs fixed.
  • #5 20953853
    rronnander
    Level 5  

    I've taken a closer look at the main chips used on the circuit board:

    BP2306 - LED Driver:

    Close-up of a printed circuit board with visible chips BP2306, BP5628C, and KP15051SPA.

    BP5628C - Dimmer:

    Close-up of a printed circuit board with visible electronic components, including the BP5628C chip.

    KP15051SPA - Power Distribution:

    Close-up of a circuit board with various components and chips visible, including BP2306, BP5628C, and KP15051SPA.

    No idea how to try to test these out with the configuration / pinout. I'll take a look around the forums for some other examples.
  • ADVERTISEMENT
  • #6 20953869
    Sunnysky
    Level 8  

    LED driver is controlled by PWM Diagram of LED controller IC BP2306XJ with labels like HV, DRAIN, VCC, and DIM.

    The low side switch for regulation and buffer of current is provided by FET
    Diagram of two ICs BP5628C and BP5629C.

    This chip supports PWM Current Sensing (CS) Schematic of an LED driver circuit with PWM and current sensing.
  • #7 20953963
    rronnander
    Level 5  

    Okay, I have the following PWM mappings:

    Screenshot of a table with PWM settings for pins.

    RGB mode seems to be working well with brightness and colors. The RED seems a little miscalibrated in the color picker. There's a sweet spot of deep red and then everything quickly looks pink, other colors seem pretty calibrated.

    Setting the proper color range (2700-6500K):
    
    CTRange 154 370
    


    Playing around with the PWM mappings on 24/26 give me the temp color slider. This puts the bulb into what appears to be white color mode stock temp (2700K). Adjusting the slider just acts as a weird additional brightness control but the color temp stays at 2700K. Looking into this more, but progress!

    Added after 2 [hours] 20 [minutes]:

    Okay, I think I have it working as expected now.

    I enabled the following extra flags:

    Flag 8 - [LED] Alternate CW light mode (first PWM for warm/cold slider, second for brightness)
    Flag 24 - [LED] Emulate Cool White with RGB in device with four PWMS - Red is 0, Green 1, Blue 2, and Warm is 4

    
      "pins": {
        "7": "PWM;1",
        "8": "PWM;2",
        "9": "PWM;3",
        "24": "PWM;5"
      },
    


    It's "working" in all modes. Looks good at first glance, but I'll test it against a tuya firmware version later this weekend. When the dust settles I'll update my original post with all the current config/info.
  • #8 21250933
    floydcohen
    Level 2  
    Gotten a few of these, how did you get the cloudcutter to work? Can't seem to get these bulbs into slow-flashing AP mode. Just quick flashing color cycling.
  • ADVERTISEMENT
  • #9 21250984
    p.kaczmarek2
    Moderator Smart Home
    Which version did you get? Maybe it's patched already.
    Here are tutorials for UART flash method (check which BK7231 chip you got):
    https://www.youtube.com/playlist?list=PLzbXEc2ebpH0CZDbczAXT94BuSGrd_GoM
    Helpful post? Buy me a coffee.
  • #10 21251013
    floydcohen
    Level 2  
    p.kaczmarek2 wrote:
    Which version did you get? Maybe it's patched already.


    Same model: A19CCECWF
    But different SKU 75812 (4-pack)

    Sylvania Wifi App shows device firmware version 1.1.4. Can't add to SmartHome/Tuya to double check firmware version.
    Tried many different methods of trying to get into Access Point(AP) mode, but no luck, just quick flashes - 3 quick on/off, 5 quick on/off, 8 quick on/off, 10 quick on/off and same variations with 1 sec on/2 sec off, 5 sec on, 5 sec off, etc.. No SYLVANIA-* or any new Wifi APs show up with wifi scan on another computer, just the existing wifi APs around me. Maybe this model/update just uses bluetooth to do the pairing for WIFI.
  • #11 21255509
    rronnander
    Level 5  
    >>21251013
    I believe the magic number is 6 cycles. This is technically 6.5/7 cycles if you count the first power on event as a cycle. When flashing I was easily able to get each bulb into AP mode by powering the bulb up for ~10 seconds, then cycling the power 6 times. I hope they didn't patch these bulbs, they're a great option. I've also since moved on to ESPHome for these particular bulbs. Let me know if you can still flash the latest bulbs.

    From tuya-cloudcutter's INSTRUCTIONS.md:
    Quote:
    When instructed, put your Tuya device in AP Mode by toggling it off and on again 6 times, with around 1 second in between each toggle. If it's a light bulb, it will blink slowly. If it blinks quickly, power cycle it 3 more times.
  • ADVERTISEMENT
  • #12 21345974
    ScottK
    Level 1  
    >>21255509 Just joined. I can confirm that the 4 packs from Menards with this bulb still work, and still are exploitable.
    I have just converted 2 of my 4 just now, using tuya-cloudcutter.
    Worked perfectly, and exactly like the instructions there (and here) say.

    PS: If you have a Menards local to you, they are Clearancing them out for $6 for the 4 pack.

    Added after 8 [minutes]:

    rronnander wrote:
    >>21251013
    I've also since moved on to ESPHome for these particular bulbs.


    Where did you get the config for ESPHome to be able to set the LEDs themselves?

    I was planning to use this similar model as a guide, but wasn't sure:
    https://devices.esphome.io/devices/LEDVANCE-E27-RGBW

    Thanks for any info/help!
  • #13 21357820
    birwin88
    Level 2  
    >>21345974

    Thanks for the Menards tip.. I grabbed a few boxes today at $6.

    I also grabbed a box of the smart plugs for $7.. I have been able to use cloudcutter on those as well. So far I don't see energy monitoring but useful for on/off.
  • #14 21375154
    birwin88
    Level 2  
    >>21255509 >>21251013

    I bought 5 boxes of these from the Menards clearance deal. I had a set of 4 bulbs from back in 2022 already outside that I was using local Tuya with. I was able to flash the 4 I already had with cloudcutter without issue. I was then able to flash 4 out of 5 boxes I got from Menards. One of the boxes I could not get a single bulb to go into AP Mode/Slow blink. I have no clue what the difference is with that one box. From the outside of the box, there's no difference. Same order number/shipment sticker on them. Boxes look the same. Considering I flashed 20 bulbs of this variety just fine, I think it's pretty safe to say there are some floating around that can't easily be put into AP Mode. The normal 3 cycles or 6 cycles just doesn't get them there. I will be deconstructing one of them for science.
  • #15 21382639
    byarg
    Level 1  
    >>21255509 A little more info on getting these into slow blink AP mode. Rronnander's (#21251013) advice worked well for me:
    Quote:
    I believe the magic number is 6 cycles. This is technically 6.5/7 cycles if you count the first power on event as a cycle. When flashing I was easily able to get each bulb into AP mode by powering the bulb up for ~10 seconds, then cycling the power 6 times.


    When I did it, I did the off & on each less than a second, and did the initial power-on for about 20 seconds. After turning the power off & on the 5th time, the bulbs very briefly flashed off for a fraction of a second after turning on. I turned the bulb off and back on immediately after the brief flash.

    On the first few bulbs I wasn't as consistent and now those will not go into slow blink AP mode. My guess is this mode gets locked out if it sees too many power off/on cycles or some other pattern it doesn't like.
  • #16 21386684
    bleeblak8
    Level 4  
    I am struggling to get these A19CCECWF Bulbs to get into Slow AP flash. I've tried so many different versions of the above.
    Power on for 20 seconds, turn off and on 6 times with 1 second inbetween.
    Power on for 10 seconds, turn off and on 6 times but 5 seconds inbetween.
    And a few other variations in there as well.
    Is there a fool proof plan to get these into slow AP? I have the top off one and think I might hook up UART and flash it, but the EN pin is in a terrible location.
    Thanks in advance.
  • #17 21390305
    dizzinator00
    Level 1  
    bleeblak8 wrote:
    I am struggling to get these A19CCECWF Bulbs to get into Slow AP flash. I've tried so many different versions of the above.
    Power on for 20 seconds, turn off and on 6 times with 1 second inbetween.
    Power on for 10 seconds, turn off and on 6 times but 5 seconds inbetween.
    And a few other variations in there as well.
    Is there a fool proof plan to get these into slow AP? I have the top off one and think I might hook up UART and flash it, but the EN pin is in a terrible location.
    Thanks in advance.


    Same issue here. Unable to get these into slow AP. Following in case someone knows a reliable method

    Model: A19CCECWF
    SKU: 75812 (4 pack)
  • #18 21391865
    racer7
    Level 1  
    I was able to grab four boxes of these from Menards. I've only opened two boxes so far, and here are my findings.

    Box #1
    Firmware v1.1.4
    Unable to place into AP mode to run tuya-cloudcutter against it. tuya-convert is also unable to exploit it.

    Box #2
    Firmware v1.0.9
    Able to place this box into AP mode and successfully flash via firmware selection (1.0.9 - BK7231T / oem_bk7231s_light_sp_mix4to5_db). Attempting to exploit by brand did not work. Like was said above, the process to get these bulbs into slow mode does not match any documentation I was able to find.

    To get these bulbs into slow flash/AP mode:
    1) Turn bulb on, wait until it starts flashing
    2) Turn bulb off for .5 seconds
    3) Turn bulb on for .5 seconds (First power-on)
    4) Turn bulb off for .5 seconds
    5) Turn bulb on for .5 seconds (Second power on)
    6) Turn bulb off for .5 seconds
    7) Turn bulb on for .5 seconds (Third power on)
    8) Turn bulb off for .5 seconds
    9) Turn bulb on for .5 seconds (Fourth power on)
    10) Turn bulb off for .5 seconds
    11) Turn bulb on, wait for flicker in light (Fifth power on)
    12) Light should start flashing in AP mode

    If you power the light on and it doesn't do a quick fade to on, but instead immediately turns on at full brightness, the controller didn't reboot and you turned the light on and off too fast. Also note that after the exploit runs, and you see the message block appear that says to power cycle and place the device into AP mode *again*, you need to power the bulb off quickly, then power it back on after a few seconds. If you wait too long, the exploit will fail.

    Will update with more information as I work through these.

    EDIT: I've got ESPHome working on all 8 v1.0.9 bulbs I've received. Easy process via tuya-cloudcutter. The v1.1.4 bulbs... I can't get them into AP mode to run cloudcutter. Some people were asking for an ESPHome template for the bulbs, below is what I was able to get working, adding it here for reference.:

    esphome:
      name: SYLVANIA-Smart-A19CCECWF-RGBCT
      comment: SYLVANIA Smart+ A19CCECWF RGBCT Light
      friendly_name: SYLVANIA Smart+ A19CCECWF RGBCT Light
    
    bk72xx:
      board: generic-bk7231t-qfn32-tuya
    
    # Make sure logging is not using the serial port
    logger:
      baud_rate: 0
      
    # Enable Home Assistant API
    api:
    
    ota:
      - platform: esphome
    
    # WiFi connection
    wifi:
      ap:
    
    captive_portal:
    
    # Enable Web server
    web_server:
    
    output:
      - platform: libretiny_pwm
        id: output_green
        pin: P8
      - platform: libretiny_pwm
        id: output_blue
        pin: P9
      - platform: libretiny_pwm
        id: output_red
        pin: P7
      - platform: libretiny_pwm
        id: output_white
        pin: P24
    
    light:
      - platform: rgbw
        id: light_rgbw
        name: None
        color_interlock: true
        red: output_red
        green: output_green
        blue: output_blue
        white: output_white
        effects:
          - random:
              name: "Random"
          - flicker:
              name: "Flicker"

Topic summary

The discussion revolves around the teardown and flashing of the SYLVANIA SmartPlus A19CCECWF RGBCT bulb using the cloudcutter method. The user successfully flashed one bulb and shared details about the model, including its SKU and product ID. Other participants contributed by providing a JSON template for device integration, insights on the circuit board components, and PWM mappings for color calibration. Challenges in entering Access Point (AP) mode for flashing were noted, with suggestions for cycling power to achieve this. The conversation also touched on firmware versions and potential compatibility issues with different SKUs of the same model.
Summary generated by the language model.
ADVERTISEMENT