-
Notifications
You must be signed in to change notification settings - Fork 403
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
L3-5M-P control issues #1394
Comments
Sorry for the low-effort bug report. Here are some diagnostic data:
(The 1 offline is normal, its just my nightstand which I often manually switch off) Warning and errors on logs: None related to SonoffLAN Device debug experiments:
My understanding of the problem, is that the integration doesn't send a full command, containing both the RGB value and the brightness, and instead sends only the value that changed. Sonoff's servers then probably automatically fill in the 'gaps', setting 100% if the brightness is missing and ~(80,225,255) if the color is missing. If the LEDs are set to a preset from a Scene, SonoffLAN sends a full command, containing both RGB AND brightness, but it also includes the "Effect", which you cannot disable, because a "None" or "Disabled" option is missing from the drop-down menu for "Effects", meaning that you're actually forced to select one, (which you shouldn't, effects are optional, since they're a different mode, and they override any RGB/brightness set by the user anyway). |
I can't confirm your words. I don't have this bulb. But tests say than integration sends brightness+rgb without any problems: eea500d |
Hello, the integration indeed seems to work fine. I think the problem comes from what the UI is asking the integration to do.
And it worked! The LEDs indeed turned Red and at 10% brightness. Then I tried to set just the brightness with:
and the LEDs turned into RGB(80,225,255) at 11% brightness exactly after that, I ran:
which is missing it's "bright" value. and the LEDs turned Red but at full brightness! Curiously, I tried the same experiment with my other LED controller by Sonoff, "L2", which is a standalone RGB strip controller, and it doesn't behave that way, instead it 'remembers' the values of RGB and brightness, and doesn't reset them every time a new command is ordered. I didn't entirely understand the test you conducted earlier, but by sending Also curiously, it doesn't seem that anyone else has this issue. It's very hard if impossible to miss, and it would have been caught during development... Thanks for looking into this. |
L3-5M-P behaves weirdly, when using custom colors, you can control the RGB color, or the brightness, but not both.
Setting the RGB color sets the brightness to 100%
Setting the brightness sets the RGB to a seemingly arbitrary value of, loosely, ~(80,225,255)
Control via the native app works fine.
The text was updated successfully, but these errors were encountered: