Closed teejay-87 closed 4 years ago
No one?
Same here...
Same here...
At least, i'm not the only one
I installer a fresh copy of HA 0.104.3 in docker container, copied just the following config:
light:
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
Setting protocol: 'ledenet'
does nothing different, nor does setting it to 'rgbw'
mode (despite mine is RGB model without white)
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
Having the same issue too.... Please someone help.
Can someone escalate this ?
same problem
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.
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.
Still no news on this one.
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.
I highly recommend to flash it with esphome or tasmota
https://tasmota.github.io/docs/devices/MagicHome-LED-strip-controller/
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?
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.
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.
How about color wheel? MagicLight app is not important for me
You have that color wheel option too.
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:
I attach two videos: https://www.dropbox.com/s/jel5upxdzyjrag4/RPReplay_Final1569015128.MP4 https://www.dropbox.com/s/rzbchb60q18104v/RPReplay_Final1569015081.MP4