logo elektroda
logo elektroda
X
logo elektroda

CLOUDY BAY 6 Smart WiFi LED Lights: RGB to CW Crash Issue on Version 1.17.697

yonubear 1377 14
ADVERTISEMENT
  • #1 21326515
    yonubear
    Level 4  
    I just flashed 4 CLOUDY BAY 6inch Smart Wifi LED Recessed Lights however 2 behave properly and 2 do not the ones that do not crash every time you try to change from RGB to CW. I am at a loss on where to start for sorting this issue out and help would be great I will provide whatever info is needed

    version is 1.17.697
    AI: What app or method are you using to control the CLOUDY BAY lights?
    HTTP and Home assistant
    AI: Have you tried any troubleshooting steps so far, and if so, what were they?
    full reset, different flags
  • ADVERTISEMENT
  • #2 21327450
    p.kaczmarek2
    Moderator Smart Home
    What is your device template, configuration?

    Maybe it's I2C-like LED driver and requires lower current setting?

    Is powersave on?
    Helpful post? Buy me a coffee.
  • #3 21327683
    yonubear
    Level 4  
    >>21327450

    Powersave?

    and here is the template

    Code: JSON
    Log in, to see the code
  • #4 21327701
    p.kaczmarek2
    Moderator Smart Home
    So it's just a PWM-based device?
    Screenshot of the OpenBeken Configuration Generator for parsing Tuya JSON data.

    Well, then try maybe enabling PowerSave on OBK... I am not sure.... I expected it to be a current setting related problem of I2C-like LED controller, SM2135, etc, etc.


    Helpful post? Buy me a coffee.
  • #5 21327706
    yonubear
    Level 4  
    >>21327701


    I'll give it a shot
  • ADVERTISEMENT
  • #6 21327716
    p.kaczmarek2
    Moderator Smart Home
    Also, are you using smooth LED transitions? Does it crash without them or with them, or in both cases?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #7 21331946
    yonubear
    Level 4  
    >>21327701
    it just flashes off and restarts but I just noticed that one of them if I use the test buttons in the web app all the channels are out of order for instance 100% blue turns on warn white

    I'll give it a shot>>21327716
  • #8 21332096
    p.kaczmarek2
    Moderator Smart Home
    Maybe enable "raw PWM controls" flag and try to first order the channels correctly? First is RED, then is Green, then Blue, etc...
    Helpful post? Buy me a coffee.
  • #9 21333527
    yonubear
    Level 4  
    ok i tried the raw flag

    channel 1 does nothing
    channel 2 does warm white
    channel 3 does cool white
    channel 4 does red
    channel 5 does blue

    I am confused that this one acts so different compared to the others
  • #10 21333657
    p.kaczmarek2
    Moderator Smart Home
    You've got wrong channel order and probably one of wrong pins has PWM role. Please check other PWM to see if it's green LED and reorder channels so it goes like this: RGBCW
    Helpful post? Buy me a coffee.
  • #11 21334645
    yonubear
    Level 4  
    >>21333657

    How do I reorder channels? I set this up using the same template as my other lights that are same model
  • ADVERTISEMENT
  • #13 21334754
    yonubear
    Level 4  
    I got it working changing the channels worked but I got curious and I found if I use the cloudy bay template in the web app it has the pins wrong if I use the cloudcutter template "LJD006GBSMWH-4PK 6in Gimbal Recessed Light (Cloudy Bay)" they match what I found was right
  • #14 21334806
    p.kaczmarek2
    Moderator Smart Home
    It's good to see you got it figured out, but you can share the final template in JSON format?;
    Helpful post? Buy me a coffee.
  • #15 21334816
    yonubear
    Level 4  
    Code: JSON
    Log in, to see the code

Topic summary

✨ The discussion revolves around issues faced with two out of four CLOUDY BAY 6-inch Smart WiFi LED Recessed Lights, which crash when switching from RGB to Cool White (CW) after flashing firmware version 1.17.697. Users suggest troubleshooting steps including enabling PowerSave, checking device templates, and adjusting PWM channel orders. The author discovers that using a different template resolves the channel order issue, leading to successful operation of the lights. The final working template is shared, highlighting the correct pin assignments for PWM control.

FAQ

TL;DR: Cloudy Bay 6" WiFi lights can reboot on RGB→CW switches when 5 PWM channels aren’t ordered RGBCW. "You've got wrong channel order." Reorder channels to RGBCW and ensure only actual pins have PWM roles, then save. [Elektroda, p.kaczmarek2, post #21333657]

Why it matters: This fixes mode-change crashes for OpenBK-flashed Cloudy Bay lights controlled via Home Assistant or HTTP, restoring reliable operation.

Quick Facts

How do I stop my Cloudy Bay 6" light from rebooting when switching RGB→CW?

Remap the PWM channels. Open the device UI and set the channel order to RGBCW. If the bundled template is wrong, apply the Cloudcutter template “LJD006GBSMWH-4PK,” then verify each channel lights the correct color. After reordering, the user reported normal operation. [Elektroda, yonubear, post #21334754]

What’s the correct order and pin mapping for colors?

Use the RGBCW order. Map Red→pin 8, Green→pin 7, Blue→pin 6, Cool White→pin 26, Warm White→pin 24. This aligns with the device configuration’s r_pin, g_pin, b_pin, c_pin, and w_pin values. Save and reboot after applying the mapping. [Elektroda, yonubear, post #21327683]

How do I reorder channels in the OpenBK UI?

Open the LED configuration page. Change the channel numbers so the order becomes RGBCW. Save settings and reboot to apply. This UI allows directly renumbering channel order without changing wiring. [Elektroda, p.kaczmarek2, post #21334731]

How can I quickly find the right order if colors are wrong?

Enable “raw PWM controls,” then verify outputs in order. "First is RED, then is Green, then Blue, etc." Adjust the channel numbers until raw channel 1 drives Red, then Green, then Blue, followed by CW and WW. Save and test RGB↔CW switching again. [Elektroda, p.kaczmarek2, post #21332096]

Channel 1 does nothing or Blue turns on Warm White—what does that mean?

That pattern signals misordered channels. One report showed: Ch1 nothing, Ch2 Warm White, Ch3 Cool White, Ch4 Red, Ch5 Blue. Reassign channels to RGBCW and retest. This mismatch can trigger reboots during mode changes. [Elektroda, yonubear, post #21333527]

Should I enable PowerSave on OBK for this light?

Yes, try enabling PowerSave if reboots persist. The maintainer suggested this for PWM-based setups. Toggle PowerSave in OpenBK settings, save, and reboot. Then retest RGB↔CW transitions. "Try maybe enabling PowerSave on OBK." [Elektroda, p.kaczmarek2, post #21327701]

Do smooth LED transitions affect the crash?

They might. The maintainer asked whether smooth transitions were enabled. Test with transitions off, then on, after fixing channel order. Log the behavior for each test so you can isolate configuration-related resets. [Elektroda, p.kaczmarek2, post #21327716]

Is this light PWM-driven or using an I2C LED driver?

It’s PWM-driven. The configuration exposes color pins (r_pin, g_pin, b_pin, w_pin, c_pin) and specifies a 1,000 Hz PWM frequency. That confirms standard PWM control rather than an I2C LED driver. [Elektroda, yonubear, post #21327683]

What firmware and control stack were involved when the issue appeared?

Firmware was 1.17.697. Control was via HTTP and Home Assistant. A full reset and flag changes did not resolve it until channels were corrected. The problem was device-level mapping, not HA itself. [Elektroda, yonubear, post #21326515]

Which template should I use—Cloudy Bay (web app) or Cloudcutter?

Use the Cloudcutter template “LJD006GBSMWH-4PK.” The built-in Cloudy Bay template had incorrect pin assignments for the affected unit. After applying the Cloudcutter template, pins matched the working mapping. [Elektroda, yonubear, post #21334754]

What exact pin-to-channel mapping worked in the final template?

Final working mapping: pin 8→PWM1, pin 7→PWM2, pin 6→PWM3, pin 26→PWM4, pin 24→PWM5. In OpenBK’s terms: 6: PWM3, 7: PWM2, 8: PWM1, 24: PWM5, 26: PWM4. Confirm that these align with RGBCW in your channel order. [Elektroda, yonubear, post #21334816]

What if reboots continue after reordering to RGBCW?

Verify no unused pins still carry a PWM role. Re-check raw outputs and confirm the order is RGBCW. Remove any stray PWM assignments, save, and reboot. "Wrong channel order and probably one of wrong pins has PWM role." [Elektroda, p.kaczmarek2, post #21333657]

Do units in the same pack behave differently?

Yes. Two of four identical lights behaved differently in one report. Validate channel mapping per unit before relying on a template. Correct any mismatches, then test RGB↔CW changes. [Elektroda, yonubear, post #21326515]

How can I share my working setup with others?

Export your final JSON template and post it to the thread when requested. Maintainers asked for the final working template to help others. [Elektroda, p.kaczmarek2, post #21334806]
ADVERTISEMENT