Setting a scene in the Home App defaults to red color

[TonnyCS]

Hi,

when I set a scene using the Home app with a brightness value and a color value, the brightness value sets correctly but the color value changes to red.

Any ideas?

[buss0140]

I am having the same issue.

[Sibek]

The same

[bor9455]

I've been having the same issue. I think it might be because I have SK6812 RGBW strips connected. I say that because I didn't buy the strips or install them, I inherited them from the previous owner.

[ElectricCharlie]

I am also having this issue. I'm using an ESP-32-WROOM, and SK6812 LEDs. Here's my config:

{ "platform": "WLED", "wleds": [ { "name": "WLED-Office", "host": "192.168.1.13", "effects": [ "Rainbow Runner", "Ripple Rainbow", "Flow", "Fireworks" ], "defaultEffectSpeed": 20, "showEffectControl": true, "log": false } ] }

[jacob-r-g]

Same issue. I am using an ESP-WROOM-32 and ALITOVE WS2811 LEDS Including my config too, if it is useful:

{
    "platform": "WLED",
    "wleds": [
        {
            "name": "WLED",
            "host": [
                "192.168.1.200",
                "10.0.0.54"
            ],
           "log": true
        }
    ]
}

In my log I do see messages like this when setting a scene which seems like a clue:

[19/03/2023, 17:50:57] [WLED] Changed color to 255,128,0 on host 192.168.1.200
[19/03/2023, 17:50:57] [WLED] Changed color to 255,128,0 on host 10.0.0.54
[19/03/2023, 17:50:57] [WLED] Set brightness to 66% 168
[19/03/2023, 17:50:59] [WLED] Updating WLED in HomeKIT (Because of Polling) 192.168.1.200
[19/03/2023, 17:50:59] [WLED] Changed color to 255,0,0 on host 192.168.1.200
[19/03/2023, 17:50:59] [WLED] Changed color to 255,0,0 on host 10.0.0.54
[19/03/2023, 17:53:11] [WLED] Error while polling WLED (brightness) WLED (192.168.1.200,10.0.0.54)
[19/03/2023, 17:53:11] [WLED] Error while changing color of WLED WLED (10.0.0.54)

It looks like it tries to send the right color, then the color changes to red? what could this be?

edit: adding more verbose log data after turning on log/debug.

• @jstrausd I have just donated 3 beers to you for this amazing work (and perhaps to persuade you to have a look at this one issue ;) happy to support on debugging in any way possible)

[bor9455]

I have an observation that I wonder if might not be helpful. When I bought my home, the previous owner had left me a couple of WLED light sets in the house. It took me a while to figure out what they were but once I figure them out, I got them in the HomeKit just fine. Then a couple of months in of living here and one of my ESP8266 gets burned up by what I later learned was a 5A USB brick that was pushing out 6A+, so it’s surprising that didn’t happen sooner.

So, I had to figure out the WLED project and I got a replacement off Amazon. This was Oct 2022, so I flashed it with the latest version which was like 13.8 and so I later did the other two in the kitchen that day. The board in the bar area was hard to get at and I didn’t know you could update it OTA, so I never updated it. It is running 10.2 and it reliably can be controlled with voice and scenes.

Of course, all my new projects have been with the latest and greatest version of WLED for some of the effects and stuff, but just like those other updates boards, the lights default to red no matter what color I tell Siri to set them.

Could the way WLED handles the color input impact what it does? I saw that this happened with Govee plug ins/HomeKit. That one had something to do with AWS Color or something. I can control the colors from the WLED App or HomeKit but only to manually find a color….which I hate because on a color wheel I can never get my colors to match the voice command one. Sorry for the rant, but I wondered if it might not be something like how WLED does color versus what the plug-in sends over.

[caiotadashi]

Same issue here.

Here's my config:

        {
            "platform": "WLED",
            "wleds": [
                {
                    "name": "LED-LG",
                    "host": "192.168.1.123",
                    "log": false
                },
                {
                    "name": "LED Strip",
                    "host": "192.168.1.124",
                    "log": true
                }
            ]
        }

And I noticed that if I choose the color manually, the log shows something like this:

[7/26/2023, 6:54:48 PM] [WLED] Changed color to 162,0,255 on host 192.168.1.124
[7/26/2023, 6:54:58 PM] [WLED] Changed color to 0,64,255 on host 192.168.1.124
[7/26/2023, 6:55:01 PM] [WLED] Changed color to 162,0,255 on host 192.168.1.124

But if I set a scene, the log shows:

[7/26/2023, 6:55:01 PM] [WLED] Set brightness to 100% 255
[7/26/2023, 6:55:04 PM] [WLED] Updating WLED in HomeKIT (Because of Polling) 192.168.1.124

[Sboyle00]

I am having the same issue, I have installed LEDS on the stairs with PIR top and bottom, when I trigger the top PIR the light goes red, when I pass the bottom one it changes to the colour I selected. also when I put on effects it defaults to red. Has anyone got a fix yet?

[bor9455]

I am having the same issue, I have installed LEDS on the stairs with PIR top and bottom, when I trigger the top PIR the light goes red, when I pass the bottom one it changes to the colour I selected. also when I put on effects it defaults to red. Has anyone got a fix yet?

Roll back your WLED to v0.10.2 Fumikiri and that solved the issue for me. Since I don’t really care to use WLED, I don’t miss the extra features in more recent updates.

[Sboyle00]

I went back to v0.10.2 this morning and can't get the led strip to work now, just getting one white and one green led lit. And the colour wheel in the UI is blacked out. I can't update to the version I was on, updates not enabled on this version

[trhessel]

Just wanted to add that I am having this issue and downgrading my WLED controllers to v.0.10.2 is the fix. I do have a QUINLED Quad controller that I cannot downgrade so I am not able to use that in homekit with this plugin until the issue of making the LEDs RED when using a homekit controller to turn on/off.

[Sboyle00]

I made a second automation and it worked fine I just turned off the first automation that was turning red.