Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flux LED/ Magic Light screwed up after 0.97 #26779

Closed
teejay-87 opened this issue Sep 20, 2019 · 17 comments
Closed

Flux LED/ Magic Light screwed up after 0.97 #26779

teejay-87 opened this issue Sep 20, 2019 · 17 comments

Comments

@teejay-87
Copy link

Starting from 0.97, this component acts completely random, both via HA interface and via HomeKit.

When I select one color, HA then switch to another random one (but the LED remains to the one I set).
Also the brightness is not set correctly.

This causes issues also in HomeKit, with the color and brightness continuously changing in random way.

My controller is this one:
FB27D2F1-0F70-4A9F-AD63-DA3BD91E2DAB

I attach two videos:
https://www.dropbox.com/s/jel5upxdzyjrag4/RPReplay_Final1569015128.MP4
https://www.dropbox.com/s/rzbchb60q18104v/RPReplay_Final1569015081.MP4

@teejay-87
Copy link
Author

No one?

@MattXcz
Copy link

MattXcz commented Jan 13, 2020

Same here...

@teejay-87
Copy link
Author

Same here...

At least, i'm not the only one

@teejay-87
Copy link
Author

I installer a fresh copy of HA 0.104.3 in docker container, copied just the following config:

light:

  • platform: flux_led
    devices:
    192.168.1.100:
    name: Colore LED
    mode: "rgb"

and I have the very same behaviour. I made another video from the web interface:

https://www.dropbox.com/s/gm1e2r1u6294qo2/Registrazione%20schermo%202020-01-25%20alle%2002.38.33.mov

@teejay-87
Copy link
Author

teejay-87 commented Jan 25, 2020

Setting protocol: 'ledenet' does nothing different, nor does setting it to 'rgbw' mode (despite mine is RGB model without white)

@Matcheryt
Copy link

Having the same issue with this integration...
Can turn off led controller but not turn on, also changing colors and brightness is delayed on the UI

@M4TH1EU
Copy link

M4TH1EU commented Mar 19, 2020

Having the same issue too....
Please someone help.

@MattXcz
Copy link

MattXcz commented Mar 19, 2020

Can someone escalate this ?

@Doppelherz
Copy link

same problem

@Fealthas
Copy link

Fealthas commented Jun 26, 2020

https://community.home-assistant.io/t/fixed-flux-led-does-not-set-brightness-or-color-correctly-when-device-is-initially-off/157578

Possibly related?

It seems to ignore commands sent too soon to the controller. So if the strip is off, it turns on, ignores new command, reads past config (off), turns off. The solution that guy did was a simple sleep(.5) to let the controller wake up and then start sending settings.

It also refuses to turn on if the light.turn_off command was sent more than once.

@stale
Copy link

stale bot commented Oct 4, 2020

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.

@stale stale bot added the stale label Oct 4, 2020
@stale stale bot closed this as completed Oct 12, 2020
@teejay-87
Copy link
Author

Still no news on this one.

https://community.home-assistant.io/t/fixed-flux-led-does-not-set-brightness-or-color-correctly-when-device-is-initially-off/157578

Possibly related?

It seems to ignore commands sent too soon to the controller. So if the strip is off, it turns on, ignores new command, reads past config (off), turns off. The solution that guy did was a simple sleep(.5) to let the controller wake up and then start sending settings.

It also refuses to turn on if the light.turn_off command was sent more than once.

No, for me happens even minutes after the light has been turned on.

Still no news on this?

It seems that this integration supports a lot of controllers, and when on one is fixed another get broke, and viceversa.

@MattXcz
Copy link

MattXcz commented Dec 8, 2020

I highly recommend to flash it with esphome or tasmota

https://tasmota.github.io/docs/devices/MagicHome-LED-strip-controller/

@teejay-87
Copy link
Author

I highly recommend to flash it with esphome or tasmota

https://tasmota.github.io/docs/devices/MagicHome-LED-strip-controller/

Have you experience that solves these problems? How do you use it in HA after flashing?

@MattXcz
Copy link

MattXcz commented Dec 8, 2020

I highly recommend to flash it with esphome or tasmota
https://tasmota.github.io/docs/devices/MagicHome-LED-strip-controller/

Have you experience that solves these problems? How do you use it in HA after flashing?

Yes, its a whole different (and stable) firmware after flashing.
You can than integrete it with build in addon "esphome" in integrations.
This is rather workaround then solution.
You can't controll it with magichome app after flashing.

image

This is my RGBW Flux LED / Magic Light after flashing with esphome.
I use white chanell as separate light.
M+ or M- on remote controler are just binary sensory, for wich i use automations...
I can share yaml config if someone want.

@teejay-87
Copy link
Author

teejay-87 commented Dec 8, 2020

How about color wheel?
MagicLight app is not important for me

@MattXcz
Copy link

MattXcz commented Dec 8, 2020

You have that color wheel option too.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants