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

H6144 39% Brightness #99

Closed
gradyg21 opened this issue Aug 9, 2021 · 5 comments
Closed

H6144 39% Brightness #99

gradyg21 opened this issue Aug 9, 2021 · 5 comments
Labels
complete This bug/feature has been fixed/added potential bug Something doesn't seem to work quite right

Comments

@gradyg21
Copy link

gradyg21 commented Aug 9, 2021

What issue do you have? Please be as thorough and explicit as possible.

Same issue that others have reported. My H6144 is having the 0-39% brightness bug, showing no response trying to set higher than that. 39% represents 100%. Everything is up to date, and I have tried the beta as well without success. I see in the issues that you have been able to fix this for other models, including the H6054 (which I have, and brightness works properly).

Details of your setup.

  • Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?

I'm using Homebridge with the UI.

  • Which version of Homebridge/HOOBS do you have?

Reporting Up to Date, 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.

Homebridge is running off my 2014 Mac Mini. Node.js is the latest 14.17.4m and Npm is 6.14.14.

  • Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?

Tried both 4.4.0, and 4.4.1 beta, both with the same problem. This has been the cause since I got the lights a few weeks ago.

  • Which Govee devices do you have that are causing issues? Please include product models if applicable.

The 2*5m RGBIC strip, which is the H6144.

Please paste any relevant logs below.

[8/9/2021, 2:25:45 PM] [Govee] [H6144_A009] not sending AWS update as not available or enabled.
[8/9/2021, 2:25:45 PM] [Govee] [H6144_A009] reverting to API as not available or enabled at /usr/local/lib/node_modules/homebridge-govee/lib/index.js:1020:17.
[8/9/2021, 2:25:45 PM] [Govee] [H6144_A009] [API] sending update {"name":"brightness","value":229}.
[8/9/2021, 2:25:45 PM] [Govee] [H6144_A009] could not be updated as Request failed with status code 400 at createError (/usr/local/lib/node_modules/homebridge-govee/node_modules/axios/lib/core/createError.js:16:15)

Thank you for all the great work. You've saved me a lot of cash I would have had to give to Philips if this plugin didn't exist.

bwp91 added a commit that referenced this issue Aug 9, 2021
#99 test to see if the H6144 doesn't need to be in scaleBrightness anymore for the API
@bwp91
Copy link
Collaborator

bwp91 commented Aug 9, 2021

Can you try 4.4.1-beta.0 of the plugin?

The H6144 was already in a sub-list of models that seem to report brightness [0, 254] rather than [0, 100]. I have removed it from the list to see if it works properly again. I can't seem to find the issue/reason why it was in this list. Perhaps it doesn't need to be there anymore.

@gradyg21
Copy link
Author

gradyg21 commented Aug 9, 2021

Yep, all working properly. I ordered the H6143 that arrived today, so I can confirm those work properly too. It's pretty cool how things show up in Homebridge and Homekit automatically after adding them to the Govee app. Thank you for this great plugin!

@bwp91
Copy link
Collaborator

bwp91 commented Aug 10, 2021

Ah glad it’s working 🙂

@bwp91 bwp91 added complete This bug/feature has been fixed/added potential bug Something doesn't seem to work quite right labels Aug 10, 2021
@github-actions
Copy link

This issue has been marked as complete as I believe the original query has been fixed/answered or will not be actioned. The issue will be closed in three days. If you feel the issue requires further attention then please let me know. Thanks!

@no-response
Copy link

no-response bot commented Aug 13, 2021

This issue has been automatically closed as it was marked as complete and has had no further responses within three days. If you are still experiencing problems related to the original issue then please reply to this message and the issue will be reopened if necessary. Thank you.

@no-response no-response bot closed this as completed Aug 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complete This bug/feature has been fixed/added potential bug Something doesn't seem to work quite right
Projects
None yet
Development

No branches or pull requests

2 participants