-
Notifications
You must be signed in to change notification settings - Fork 0
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
[bug] Dock LED brightness bug has *not* been fixed #304
Comments
Not fixed for me either. |
Confirmed: display issue in the web-configurator & remote-ui. |
It's not just the displayed value which is wrong. I cannot set the LED brightness to zero - nothing I have tried works. It always reverts to the previous value, and the LEDs keep coming on. |
This is the issue. It's not the configurator, it's that the brightness is not controlled by the configuration. |
For me it works from then web ui. Changing from the remote doesn't allow for setting to 0. Last time I tried it on the remote it displayed as 10% in the web ui after the change. |
See #51. It's a "feature" that certain LED notifications are still shown. A "full-off" mode will be added. Closing this ticket since the invalid dock brightness value in the web-configurator has been fixed in 1.6.9 |
Is there an existing issue for this?
Description
As #178 - this bug is not fixed in the 1.6.7 release.
If I change the dock LED brightness in either the remote or the web configurator, wait for the "change has been saved" message, leave the dock screen and come back, the LED brightness has reverted to the original value.
This bug is not - I repeat not - fixed for me.
How to Reproduce
Expected behavior
The LED brightness should be saved, not just thrown away.
System version
1.6.7
What part of the system affected by the problem?
Web Configurator, Overall system
Additional context
No response
The text was updated successfully, but these errors were encountered: