Core: Flux_led issues with RGBCW

[SonomaGTS]

Home Assistant release with the issue:

0.102.0

Last working Home Assistant release (if known):
Unknown

Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Integration:

https://www.home-assistant.io/integrations/flux_led/

Description of problem:
Bought a set of these RGBCW bulbs and get little control over them. If the mode in the config is set to "rgb" I get expected control over color pick/brightness however in "rgbw" mode I only have stable on/off functionality and the only other control that does anything is the color temperature slider moving from cool to warm increases the brightness to 200% with a weird off color and it will not reset it back. however changes made in the Magic Home Pro app reflect accurately in lovelace ui . I use these for my outside lights so normally I keep them in "warm white" mode and the only way to get the lights to turn off and on with warm white is to keep the mode set to "rgbw" because set to "rgb" turns the lights on in a blue tone from light.turn_on. These lights do not get detected unless you set ip in the config.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

`light:
  - platform: flux_led
    devices:
      192.168.2.152:
        name: left
      192.168.2.151:
        name: right
      192.168.2.153:
        name: door`

Traceback (if applicable):

Additional information:

[skylord123]

I am having a very similar issue. I bought them through this link:
https://www.amazon.com/gp/product/B07VQLZBNW/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1

Here is the issue I am having:
https://community.home-assistant.io/t/magiclight-flux-wifi-color-led-light-component/2271/76?u=skylord123

It seems CCT/RGBCW isn't working right in the flux component for these bulbs.

[SonomaGTS]

It's been frustrating and I wish I knew enough about python to try and help but unfortunately I have had to resort to using IFTTT to control the bulbs the way I need to. I currently use Flux_led just to monitor the state of the bulbs being on or off so I can keep track in the history but even just doing that causes Flux_led to still spit out errors and will randomly turn on one of the three bulbs once in awhile even when I have no automations or scripts tied to it.
I'm not prepared to break open the bulbs to reflash them to make them work so I'll just wait and see if I can figure out how to contribute or help anyone who still works on this component.

[chocobn69]

Maybe related to https://github.com/home-assistant/home-assistant/issues/27755
Not sure ... you should test

[skylord123]

I've debugged this a little bit further on this thread: https://github.com/Danielhiversen/flux_led/issues/61

[SonomaGTS]

Update of light.garage_right is taking over 10 seconds 3:14 AM __main__.py (WARNING)

I have three of the same bulbs outdoors and I get these in the logs randomly but seems to only single out one of the three randomly in a given 24 hour period which is really strange. When these show up it seems like it's a 50/50 chance it will turn on the bulb then turn it off then rinse and repeat for upwards of a dozen times sometimes while only once other times. All these are insanely close to a AP so it shouldn't be a wifi signal issue but I've seen stranger so I'm replacing that AP today and will keep watching to see if it keeps doing it.

skylord that hubitat find was awesome! I really hope that can help us get these issues resolved cause I love hass.io and these bulbs are just too cheap for what you get to not want to use them.

[skylord123]

Looks like coldwhite and warmwhite channels are being handled incorrectly in flux_led. I just made a comment about this here: https://github.com/Danielhiversen/flux_led/issues/61#issuecomment-558911734

That will need to be fixed before we can get proper cw and ww support in Home Assistant (may need some fixes inside the component as well)

I still don't understand why setting colors doesn't work though. That issue must lie inside of the Home Assistant component instead of the upstream flux_led library. I will see if I can debug that further tomorrow as I am out of time tonight.

[skylord123]

I was able to get rgbcw bulbs working by making changes to the flux_led component. My changes still need work before I can merge them back up. I also think some things should be changed in the flux_led library instead of using workarounds that I am doing (such as: flux_led doesn't detect light on only the cold white channel and thinks it is 0 so I had to build a way to get the correct brightness)

In the mean time though you can get these bulbs working by adding the flux_led component as a custom component and overriding the light.py file for the component with mine here:
https://github.com/skylord123/home-assistant/blob/skylord123-flux_led-rbgcw-support/homeassistant/components/flux_led/light.py
Then in your configuration.yaml file set your flux_led lights to mode rgbcw:

light:
  - platform: flux_led
    scan_interval: 5
    devices:
      xxx.xxx.xxx.xxx:
        name: Some Bulb
        mode: "rgbcw"

RGB and CW need to be handled separately as they cannot be on at the same time. Because of this I make it so if the brightness or RGB color is changed it sets it into RGB mode and if white value or color temperature is changed it gets set into white/warm light mode.

I make it so when warm white level is set it matches it with the white level which makes it brighter at the sacrifice of not being able to get fully warm (setting warm channel without white channel). There isn't any great ways of handling this with Home Assistant right now so with this method we have to pick one or the other (see https://github.com/home-assistant/architecture/issues/123 for more information about Home Assistant and handling white light).

One thing I wish I could figure out is why state changes take so long to reflect in the HA front-end. An example of this is switching between RGB and CW modes actually can take a few seconds before the UI updates to reflect the changes. Setting the scan_interval to 10 or less seconds seems to help some.

[skylord123]

I updated the file even further so now there is mode rgbww for bulbs that are basically rgbw bulbs but must handle rgb and warm white separately (not at same time) similar to rgbcw that I already added.

I bought some rgbw bulbs off amazon a year ago and didn't know they had a warm white channel because rgbw mode didnt work (at all, could only turn bulb off). This new mode got the bulb working perfectly.

I also added support for multiple custom effects. I want one for each holiday and that just wasn't possible with only one.

I'm still working on a couple things before I can create a pr to merge back into HA.

Here is an example using multiple custom effects:

light:
  - platform: flux_led
    scan_interval: 30
    devices:
      xxx.xxx.xxx.xxx:
        name: Living Room Couch Lamp
        mode: "rgbww"
        custom_effects:
          christmas:
            colors:
              - [0,255,0]
              - [0,0,0]
              - [255,0,0]
              - [0,0,0]
            speed_pct: 100
            transition: gradual
          strobe_rg_fast:
            colors:
              - [0,255,0]
              - [255,0,0]
            speed_pct: 100
            transition: strobe
          strobe_rg_slow:
            colors:
              - [0,255,0]
              - [255,0,0]
            speed_pct: 50
            transition: strobe

Now christmas, strobe_rg_fast, and strobe_rg_slow are available custom effects for this bulb.

The old way of doing a single custom_effect is still possible so this is backwards compatible.

[SonomaGTS]

awesome work! I will see if I can give this a try tonight!

[skylord123]

awesome work! I will see if I can give this a try tonight!

Let me know how it goes :)

[SonomaGTS]

Ok I got to try this out for a bit tonight and the RGB aspect seems to work pretty well, colors switch as expected (quick change too) as well as brightness adjustment. However once I try and replicate cool white or warm white that's where things go whacky. set on mode: "rgbcw", haven't tried rgbww yet but starting to wonder if my bulbs somehow maybe use different instructions than what the core flux_led provides. If I adjust the white slider and nothing else than my brightness goes anywhere from 0 to 200% with no color change on the bulb, if I adjust the color temperature slider sometimes it does nothing while other times it seems to try and set the bulb as an rgb value warm white rather than use the hardcoded warm white mode. Adjusting either slider does not give consistent results at all. One thing is for sure is that I believe the light component in HA needs a hard switch to turn off white mode as well as color temp in the UI. My bulbs are able to adjust brightness in all 3 modes, RGB, Warm White and Cool White and when switching between them in the app it's obvious it's a hard switch turning off the other two prior to initializing your selection.

[skylord123]

@SonomaGTS Looks like your bulb is rgbc/w instead of rgb/cw (based on what you said and also going to the amazon page and seeing someone mention that the cool white is very dim whereas the warm white is much brighter).

If that is the case then the problems you are seeing make sense. I do a mix of warm and cool light when the color temperature is changed. I also use the white level slider for controlling the brightness when in cool/warm light mode which is why you saw the brightness changing when you messed with it.

I'll see if I can do another update to get your bulbs working to see if this is really the problem. If so maybe the fix is to add the modes as "rgb+cw" and "rgbc+w" (I should probably figure out the LED notation cause I don't even know if this is correct).

[SonomaGTS]

In the magic home pro app I have a CCT option that adjust all the levels between warm white and cool white so I think that makes them a rgb+cw as you stated.

https://pasteboard.co/IJFyN1Q.png

https://pasteboard.co/IJFz3aI.png

[skylord123]

In the magic home pro app I have a CCT option that adjust all the levels between warm white and cool white so I think that makes them a rgb+cw as you stated.

https://pasteboard.co/IJFyN1Q.png

https://pasteboard.co/IJFz3aI.png

Your bulbs look exactly like they do in the amazon link you provided above right? WIth the RGBCW text on them?

If so that is strange it isn't working because they look exactly like my bulbs. I'm a little lost with what could be causing the problems for you.

If you could do the same debugging that I did in this comment I should be able to figure it out:
https://github.com/Danielhiversen/flux_led/issues/61#issuecomment-558450709

[SonomaGTS]

The link I provided above are the exact bulbs I have. Even came in a cheap box https://pasteboard.co/IJGgYiL.jpg

So I ran the same flux_led commands you did, I couldn't actually physically see my bulbs while running these commands so I hope it helps.

`
python -m flux_led 192.168.1.153 --warmwhite 10
Setting warm white mode, level: 10%
python -m flux_led 192.168.1.153 -i
Unknown ID [192.168.1.153] ON [Warm White: 9% raw state: 129,53,35,97,1,1,0,0,0,25,7,25,15,132,]

python -m flux_led 192.168.1.153 --warmwhite 100
Setting warm white mode, level: 100%
python -m flux_led 192.168.1.153 -i
Unknown ID [192.168.1.153] ON [Warm White: 100% raw state: 129,53,35,97,1,1,0,0,0,255,7,255,15,80,]

python -m flux_led 192.168.1.153 --coldwhite 100
Setting cold white mode, level: 100%
python -m flux_led 192.168.1.153 -i
Unknown ID [192.168.1.153] ON [Color: (0, 0, 0) Brightness: 0 raw state: 129,53,35,97,1,1,0,0,0,0,7,255,15,81,]

python -m flux_led 192.168.1.153 --coldwhite 10
Setting cold white mode, level: 10%
python -m flux_led 192.168.1.153 -i
Unknown ID [192.168.1.153] ON [Color: (0, 0, 0) Brightness: 0 raw state: 129,53,35,97,1,1,0,0,0,0,7,25,15,107,]

python -m flux_led 192.168.1.153 -c 255,0,0 # red
Setting color RGB:(255, 0, 0)
[(255, 0, 0)]
python -m flux_led 192.168.1.153 -i
Unknown ID [192.168.1.153] ON [Color: (255, 0, 0) Brightness: 255 raw state: 129,53,35,97,1,1,255,0,0,0,7,0,240,50,]

python -m flux_led 192.168.1.153 -c 0,255,0 # blue
Setting color RGB:(0, 255, 0)
[(0, 255, 0)]
python -m flux_led 192.168.1.153 -i
Unknown ID [192.168.1.153] ON [Color: (0, 255, 0) Brightness: 255 raw state: 129,53,35,97,1,1,0,255,0,0,7,0,240,50,]

python -m flux_led 192.168.1.153 -c 0,0,255 # green
Setting color RGB:(0, 0, 255)
[(0, 0, 255)]
python -m flux_led 192.168.1.153 -i
Unknown ID [192.168.1.153] ON [Color: (0, 0, 255) Brightness: 255 raw state: 129,53,35,97,1,1,0,0,255,0,7,0,240,50,]
`
You had green and blue reversed. Just went back and watched the color of the bulbs in the app and that threw me off lol

[SonomaGTS]

So messing around a little more I noticed if I manually set the warm white to the default and max brightness which is as far left in the CCT screen it goes i get this output from flux_led

python -m flux_led 192.168.1.153 -i
Unknown ID [192.168.1.153] ON [Warm White: 100% raw state: 129,53,35,97,1,1,0,0,0,255,0,15,81,]

which to me should be the default of the command of

python -m flux_led 192.168.1.153 --warmwhite 100

which it is not that comes out as

python -m flux_led 192.168.1.153 -i
Unknown ID [192.168.1.153] ON [Warm White: 100% raw state: 129,53,35,97,1,1,0,0,0,255,7,255,15,80,]

[SonomaGTS]

So I had more time to play around with these bulbs today and using your light.py @skylord123 in mode "rgbcw". After trying to test different states using both the HA interface as well as the Magic APP and checking the output using the library it doesn't seem to stay consistent no matter what I do once the bulbs switch off RGB mode. At first it seemed the "rgbcw" mode was controlling my cool-white side of the bulbs just fine but after a bit it became unstable and the bulb itself even became unresponsive. I can see adjusting various levels between the white value and the color temperature in HA does infact set the bulb in warm-white mode as well as cool-white but with no ability to adjust the color aspect in CCT as well as no ability to control brightness while in ww/cw modes I am not sure how my bulbs would ever work correctly in HA.

Ideally flux needs to integrate a CCT color wheel as well actual toggles for switching between modes cause how it's setup now is flaky because it seems the code relies on certain attributes to hit certain values then does all the switching in the background and it's that aspect that caused the bulbs to become unresponsive.

[skylord123]

@SonomaGTS Can you try commenting out or removing lines 400 and 401 to see if it helps at all? These are the lines: https://github.com/skylord123/home-assistant/blob/skylord123-flux_led-rbgcw-support/homeassistant/components/flux_led/light.py#L401-L402

Also when you were setting coldwhite and warmwhite using the command line was the bulb white temperature changing correctly outside?

[SonomaGTS]

@skylord123 Commenting out lines 400-401 seems to have worked! I need to do some testing to check the state of the bulbs later but for the time I was standing outside adjusting it appears that the temperature slider does infact now accurately swap between cold white and warm white. Not sure adjusting the white value to anything between 0-100 is doing what it's supposed to be doing since I thought the white value was the brightness for warm white and cold white but as long as the white value is at 0 or 100 the bulbs are working as they should while adjusting the temperature slider.

---

Using the library (command line) was not setting the warm white side of my bulbs correctly.
Using the command line for -w 100% yielded this for me,
python -m flux_led 192.168.1.153 -i
Unknown ID [192.168.1.153] ON [Warm White: 100% raw state: 129,53,35,97,1,1,0,0,0,255,7,255,15,80,]
and the bulbs were actually set to their coldest warm setting I believe.

When the bulbs were manually set through the app at their warmest warm setting the library (command line) reported their raw status as,
python -m flux_led 192.168.1.153 -i
Unknown ID [192.168.1.153] ON [Warm White: 100% raw state: 129,53,35,97,1,1,0,0,0,255,0,15,81,]

---

Update: played around with them a little more trying to understand what the sliders in the HA UI were actually doing. There is still some sporadic glitches.
If I manually adjust the sliders temperature and white value to max on or off the bulbs work as expected.
If I leave the white value maxed and adjust the temperature slider between cold and warm the bulbs work as expected.
Adjusting the white value down while the temperature slider is at max warm setting reduces the brightness of the warm led while leaving the white led on full brightness.
If I adjust the white value down while the temperature slider is at max cold setting the brightness lowers of the whole bulb.
Not sure if these are normal behaviors given the way we have to adjust between the modes or not.

I think the UI also plays a role in some of what I see because it appears that sometimes while you are moving a slider what HA sends to the bulbs can get mixed up alittle and yield a result you wouldn't expect. My bulbs love to glitch back to showing a blue rgb color so that's usually the state I see when I turn the bulbs on from off in HA UNLESS I turned the bulbs off while they were at some max setting but anything in between is a quarter toss.

BTW miles ahead man, you are doing awesome. This is by far the most control I have had over these bulbs and I am thrilled to death. hehe

[skylord123]

@SonomaGTS thanks for the quick reply and I am glad we are getting closer to figuring this out.

So the white level jumping around and acting weird is expected after you changed the above lines. I am going to have to make two modes for RGBCW bulbs (one for my version and one for yours) and make the white level detection work correctly for your bulbs. Commenting out those lines I told you to will make white level not calculate correctly. Adding two modes for these bulbs would fix that by being able to change how white level is detected for these two different version of RGBCW bulbs.

Whenever you change color temperature/RGB value/white value in HA it tries to pull the values for all the other options a couple seconds later. This is why you see the sliders jump around a bit.

Because there are so many different types of bulbs out there and they all handle modes differently it is hard for HA to build an interface that works for all of them. I am basically having to convert to and from what these bulbs expect to what HA expects and then do it in reverse when we are setting the values.

I'll see if I get some time to play with this tonight to see if I can fix the sporadic values.

[SonomaGTS]

@skylord123 I just realized you got me off IFTTT completely! That additional custom_effects option is a wonderful addition! That took care of my christmas light setup since these bulbs are used outside without needing IFTTT plus with me being able to use

entity_id: light.garage_left color_temp: 500 white_value: 255 brightness_pct: 100

to set my warm white mode for normal porch light color and brightness that took care of me needing to use IFTTT to switch them back as well!

You gave me a good christmas present. I know you'll get these bulbs working flawlessly in the end but for the purposes of what I generally use these bulbs for you fixed my issue. I'm still dedicated to helping polish this for the UI aspect as well as for others who may be stuck in our shoes but wanted to give thanks because this whole rabbit hole for me started when I had to rely on IFTTT to make these bulbs do the basic tasks I needed them too and now you fixed that for me.

[SonomaGTS]

@skylord123 Does your bulbs show the color_temp attribute? Is there anyway to pull up the color_temp attribute? Although the color_temp is being used as it works for me switching between the cool/warm my states never show that attribute.
https://pasteboard.co/ILoxgcs.png

[skylord123]

@skylord123 I just realized you got me off IFTTT completely! That additional custom_effects option is a wonderful addition! That took care of my christmas light setup since these bulbs are used outside without needing IFTTT

I am glad the changes got you off IFTTT. More power to you ;) I've been using it for my christmas lights and it has been great so far.

@skylord123 Does your bulbs show the color_temp attribute? Is there anyway to pull up the color_temp attribute? Although the color_temp is being used as it works for me switching between the cool/warm my states never show that attribute.
https://pasteboard.co/ILoxgcs.png

Currently I have reporting the color temp disabled. Color temp in Home Assistant is based in mireds. I do this conversion from mireds to kelvin then map the kelvin range I want to the range the bulbs expect. I need to write code to do all of this backwards so I can get mireds from the bulbs and I just haven't done that yet. I am not great at doing formulas and probably need to change my code so instead of converting to kelvin then to what the bulbs want I should probably just convert from mireds straight to what the bulbs want so it is easier to go backwards.

If all you need to do is detect if the bulb is in RGB mode or white light mode you can do that using the "white level" property. If the white level is above 0 then the bulb is in white level if it is 0 and brightness is above 0 then it is in rgb mode. If both white level and brightness are 0 then the bulb is off. There currently is no way to get color_temp until I add it though.

Note:
The one problem I see with all magiclight bulbs I have tried is that they update really slow. When you change settings it can take a while for the UI to detect the bulb has changed. This is really weird and I have tried setting the update interval to a lower number as well as other things and nothing seems to really help. Because of this slow update that is why the UI jumps around a bit and glitches out sometimes. This is why when you change the white level the color temperature changes instead of keeping the temperature the same and just adjusting the brightness like it should (I have the code set so if you change white level it will use the existing color temp and just adjust the brightness for it but for some reason the current temperture HA gives me is always wrong in this code so changing the white level always changes the color temperature). I believe this is an issue with how flux_led is polling states from the bulbs. I've seen this issue that attempt to fix it but yet I still have the same problem:
https://github.com/home-assistant/home-assistant/issues/11565

So I will look into adding color_temp reporting. I also need to play around with the flux_led library a bit and see if I can fix the state updating problem. If I check state using flux_led on terminal it always returns current state so HA should be getting the same.

[SonomaGTS]

The one problem I see with all magiclight bulbs I have tried is that they update really slow. When you change settings it can take a while for the UI to detect the bulb has changed. This is really weird and I have tried setting the update interval to a lower number as well as other things and nothing seems to really help. Because of this slow update that is why the UI jumps around a bit and glitches out sometimes.

That delay was already implemented here
https://github.com/skylord123/home-assistant/blob/4ceb316e4b45c816a1c9d78f565ff8833097d8c7/homeassistant/components/flux_led/light.py#L201-L206

at the risk at showing just how little I know of all this I will say in my experience everytime you touch the UI to adjust the bulb HA issues that light_on thus triggering that delay that was already implemented.

I have to have my bulbs change from using an effect back to going to warm white when the garage is opened and then back again. In a script I can change the bulb from effect to warm white with the simple color_temp, brightness and white_value light_on command. To change back to the effect from a warm white my script has to issue a blank light_on, 1 second delay then a second light_on with the effect to make it switch. switching between warm white and cool white only requires a color_temp, brightness and white_value command with a light_on.

I use a custom button that will tell me what mode the bulb is currently in so I can see if it's using an effect, on rgb or warm white and able to adjust the icon color accordingly. It works for effect, rgb and warm white however the attributes shows the exact same rather the bulb is in warm white or cold white mode so that's why i was asking about the color_temp.

I play with these things every chance I get so if you need me to do something to help test just point in me in the direction.

[SonomaGTS]

@skylord123 so after some looking around (and still learning python) I keep finding other light components using the same library 'homeassistant.util.color' just as magic home does. There seems to be a mired to kelvin converter in it 'color_temperature_mired_to_kelvin' and many of the components implement the reporting and converting to color_temp the same exact way. Can't we just do it the exact same way? I been looking at this component in particular opple and after christmas I thought about taking a stab at seeing if I can figure out how to do any of this. lol

[sheminasalam]

I updated the file even further so now there is mode rgbww for bulbs that are basically rgbw bulbs but must handle rgb and warm white separately (not at same time) similar to rgbcw that I already added.

I bought some rgbw bulbs off amazon a year ago and didn't know they had a warm white channel because rgbw mode didnt work (at all, could only turn bulb off). This new mode got the bulb working perfectly.

I also added support for multiple custom effects. I want one for each holiday and that just wasn't possible with only one.

I'm still working on a couple things before I can create a pr to merge back into HA.

Here is an example using multiple custom effects:

light:
  - platform: flux_led
    scan_interval: 30
    devices:
      xxx.xxx.xxx.xxx:
        name: Living Room Couch Lamp
        mode: "rgbww"
        custom_effects:
          christmas:
            colors:
              - [0,255,0]
              - [0,0,0]
              - [255,0,0]
              - [0,0,0]
            speed_pct: 100
            transition: gradual
          strobe_rg_fast:
            colors:
              - [0,255,0]
              - [255,0,0]
            speed_pct: 100
            transition: strobe
          strobe_rg_slow:
            colors:
              - [0,255,0]
              - [255,0,0]
            speed_pct: 50
            transition: strobe

Now christmas, strobe_rg_fast, and strobe_rg_slow are available custom effects for this bulb.

The old way of doing a single custom_effect is still possible so this is backwards compatible.

I am not able to implement this. The config check produces error report even after copy pasting the above code. It says custom_effects is an invalid command. Any advises

[SonomaGTS]

@sheminasalam you have to be running his modified light.py as a custom component in HA before it will work. https://github.com/skylord123/home-assistant/tree/skylord123-flux_led-rbgcw-support/homeassistant/components/flux_led

[sheminasalam]

@SonomaGTS Tried it but not successful. Might have missed something. Can you please explain in exact steps?

[skylord123]

@SonomaGTS Tried it but not successful. Might have missed something. Can you please explain in exact steps?

You can override components that Home Assistant ships with by adding a custom_components folder inside your HA directory. You then need to add a folder inside that one called flux_led that you will add the files from this link to:
https://github.com/skylord123/home-assistant/tree/skylord123-flux_led-rbgcw-support/homeassistant/components/flux_led

Download each of the files in that directory from that link and place them in the new custom_components/flux_led folder you created (you can get each file by opening each one and clicking RAW then saving from your browser with ctrl+s). You are now overriding the flux_led component home assistant ships with and it will instead use the custom code from this folder.

This is a method until I am able to get something merged back up to ship with Home Assistant. Right now I am busy from the holidays and work so I am just waiting for some free time to get to this. :)

[sheminasalam]

I have tried it earlier too but this is not working for me. i am getting configuration not valid still now.

[skylord123]

I have tried it earlier too but this is not working for me. i am getting configuration not valid still now.

Paste the error from the log as well as your configuration. I can't really help you very well without it.

[sheminasalam]

I have tried it earlier too but this is not working for me. i am getting configuration not valid still now.

Paste the error from the log as well as your configuration. I can't really help you very well without it.

Invalid config for [light.flux_led]: [custom_effects] is an invalid option for [light.flux_led]. Check: light.flux_led->devices->192.168.0.15->custom_effects. (See ?, line ?). Please check the docs at https://home-assistant.io/integrations/flux_led/

[skylord123]

I have tried it earlier too but this is not working for me. i am getting configuration not valid still now.

Paste the error from the log as well as your configuration. I can't really help you very well without it.

Invalid config for [light.flux_led]: [custom_effects] is an invalid option for [light.flux_led]. Check: light.flux_led->devices->192.168.0.15->custom_effects. (See ?, line ?). Please check the docs at https://home-assistant.io/integrations/flux_led/

Do you see anything in your logs about loading flux_led as a custom component? Should be a warning in there about it. If this is not there then HA isn't loading the custom component and first thing I would check in this case is if permissions for the custom_component and all it's files are correctly set so HA can access them.

[sheminasalam]

I have been using customs components for a long time. Now I am using HACS to use custom components. As advised I have created the folder and placed the files in it. Is there any other permissions that I should be checking to.

[skylord123]

I have been using customs components for a long time. Now I am using HACS to use custom components. As advised I have created the folder and placed the files in it. Is there any other permissions that I should be checking to.

Do you see a warning about using flux_led as a custom component?

[sheminasalam]

No. i believe as you said, the custom component is not loading. I dont see any reasons for that as of now. The custom components with HACS are also working great. Also at this point of time I dont have other custom integrations that I manually integrated.

[skylord123]

No. i believe as you said, the custom component is not loading. I dont see any reasons for that as of now. The custom components with HACS are also working great. Also at this point of time I dont have other custom integrations that I manually integrated.

If you are on linux I would do an ls -all from within the home assistant directory and see what the permissions for the files are. I would also do this for inside the custom_components and flux_led folder. I would verify it has permissions the same as other files that are working with home assistant already (such as the HA config file).

[sheminasalam]

I am running hassio 2.12 in OPI. Is there any way i can add it through HACS?

[skylord123]

No. You need to add it as a custom component the way I mentioned for now.

[sheminasalam]

it worked...i just deleted the entire folder and redone it...thanks for the support man... i really appreciate the time you found for me during vacations.. happy new year

[stale[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[christensonautohome]

Curious if this will be fixed in an up coming release? Not sure why this issue was closed by the bot if the required 'fix' includes adding a custom component.

[Fealthas]

Still broken.

[JuneManUA]

I also have same issue. Flux_led doesn't turn on stripe and color change works with delay.
All actions above were performed without any success.