H6054 Brightness slider issue
See original GitHub issueWhat issue do you have? Please be as thorough and explicit as possible.
The brightness adjust slider for H6054 appears to be inaccurate- the slider doesn’t seem to go above the 40% mark, but that is actually 100% on the actual light. In other words I can control 100% of the light but only using the bottom 40% of the brightness slider in HomeKit. I have another light, a different model, and the slider works fine.
Details of your setup.
- Do you use (1) Homebridge (+ config-ui), (2) Homebridge (CLI) or (3) HOOBS?
(1) Homebridge (+ config-ui)
- Which version of Homebridge/HOOBS do you have?
1.3.4
- Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Raspberry Pi 3B+ Node.js 14.17.2
- Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
Latest 3.3.0 but it was also present in the previous version (I started using this on the version prior to 3.3.0 - big thanks, it’s a fantastic plug-in and works really well even despite this minor UI issue on this particular model - thank you!!)
- Which Govee devices do you have that are causing issues? Please include product models if applicable.
H6054
Please paste any relevant logs below.
06/07/2021, 23:29:59] [Govee] [TV Lights] current brightness [39%].
[06/07/2021, 23:30:14] [Govee] [TV Lights] current brightness [39%].
[06/07/2021, 23:30:29] [Govee] [TV Lights] current brightness [39%].
[06/07/2021, 23:30:32] [Homebridge UI] [homebridge-govee] Terminating child process...
[06/07/2021, 23:30:32] [Homebridge UI] [homebridge-govee] Child process ended
[06/07/2021, 23:30:44] [Govee] [TV Lights] current brightness [39%].
[06/07/2021, 23:30:59] [Govee] [TV Lights] current brightness [39%].
[06/07/2021, 23:31:13] [Homebridge UI] [homebridge-govee] Terminating child process...
[06/07/2021, 23:31:13] [Homebridge UI] [homebridge-govee] Child process ended
[06/07/2021, 23:31:14] [Govee] [TV Lights] current brightness [39%].
[06/07/2021, 23:31:29] [Govee] [TV Lights] current brightness [39%].
[06/07/2021, 23:31:36] [Govee] [TV Lights] could not be updated as Request failed with status code 400 at createError (/usr/lib/node_modules/homebridge-govee/node_modules/axios/lib/core/createError.js:16:15).
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Tapping on brightness slider causes the phone to go ... - Reddit
I'm having exactly the same problem, no matter where I touch on the brightness slider it always opens "Network and Internet" settings.
Read more >Top 8 Fixes for the Windows 10 Brightness Slider Not ...
Is the brightness slider not working on Windows 10? Here are 8 best troubleshooting methods that can help you fix the brightness related ......
Read more >SYLVANIA H6054 Basic Halogen Sealed Beam Headlight ...
Buy SYLVANIA H6054 Basic Halogen Sealed Beam Headlight 142x200, (Contains 1 Bulb): Headlight Bulbs - Amazon.com ✓ FREE DELIVERY possible on eligible ...
Read more >Brightness keys/ slider not working in windows 11
With regards to the brightness slider being missing in Windows, to resolve that, go to the support page for your PC on the...
Read more >Screen Brightness Control Not Working on Windows 10 or 11
The problem with adjusting the screen brightness can occur in both Windows 10 and Windows 11. Typically, users complain that they cannot ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing this as original issue re
H6054
model has been fixed in the current version of the plugin! ThanksYou can ignore the node version warning, the plugin will still work on node 14.17.2