bwp91 / homebridge-govee

Homebridge plugin to integrate Govee devices into HomeKit.
MIT License
449 stars 49 forks source link

Govee H6199 Hardware version 1.00.01 - no colour change and brightness only to 35% #471

Closed johannes-schilling closed 1 year ago

johannes-schilling commented 1 year ago

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

If I want to change the colour of my H6199 / Hardware version 1.00.01 /Firmware 1.07.02 in homekit nothing happens. Changing the brightness works but not to a level of 100%. When I change the brightness to 100% it only reports 35% in the Govee app.

Inside the Govee App everything works fine.

I have a second H6199 / Hardware version 3.02.01 /Firmware 1.09.12 where everything works fine via homekit. Brightness and colour is adjustable. Both strips have the latest firmware for their HW version installed.

Details of your setup.

Config: "debug": true, "colourSafeMode": true, "platform": "Govee",

Please paste any relevant logs below.

#Changing Colour
[14/03/2023, 17:47:25] [Govee] [Kuecheninsel] [AWS] sending update {"msg":{"cmd":"colorwc","cmdVersion":0,"data":{"color":{"r":99,"g":255,"b":56,"red":99,"green":255,"blue":56},"colorTemInKelvin":0},"transaction":"v_1678812445026000","type":1}}.
[14/03/2023, 17:47:25] [Govee] [Kuecheninsel] current colour [rgb 99 255 56].

#Changing brightness to 100% --> results in 35% brightnes in the Govee app
[14/03/2023, 17:49:29] [Govee] [Kuecheninsel] [AWS] sending update {"msg":{"cmd":"brightness","cmdVersion":0,"data":{"val":100},"transaction":"v_1678812569568000","type":1}}.
[14/03/2023, 17:49:29] [Govee] [Kuecheninsel] current brightness [100%].
[14/03/2023, 17:49:30] [Govee] [AWS] message event [{"proType":2,"pactType":1,"pactCode":1,"sku":"H6199","device":"F5:36:A4:C1:38:85:7F:04","softVersion":"1.07.02","hardVersion":"1.00.01","cmd":"brightness","type":0,"transaction":"v_1678812569568000","cmdVersion":0,"state":{"connected":"true","onOff":1,"wifiSoftVersion":"1.00.29","wifiHardVersion":"1.00.01","brightness":100}}].
[14/03/2023, 17:49:30] [Govee] [Kuecheninsel] [AWS] receiving update {"source":"AWS","connected":"true","onOff":1,"wifiSoftVersion":"1.00.29","wifiHardVersion":"1.00.01","brightness":100,"proType":2,"pactType":1,"pactCode":1,"sku":"H6199","device":"F5:36:A4:C1:38:85:7F:04","softVersion":"1.07.02","hardVersion":"1.00.01","cmd":"brightness","type":0,"transaction":"v_1678812569568000","cmdVersion":0,"state":{"connected":"true","onOff":1,"wifiSoftVersion":"1.00.29","wifiHardVersion":"1.00.01","brightness":100}}.
[14/03/2023, 17:49:30] [Govee] [Kuecheninsel] current brightness [100%].

Node.js Version v18.15.0

bwp91 commented 1 year ago

Hi @johannes-schilling thanks for this report.

Just wanted to clarify - is the brightness 35% (as you have stated) or 39%?

johannes-schilling commented 1 year ago

Hello, thanks for the fast reply. The brightness is 35% in the Govee app. With the newer HW version everything works fine.

johannes-schilling commented 1 year ago

Looks like the brightness get updated to 100% now after the newest version but the colour does still not change via homebridge at the "Kuecheninsel" device with H6199 / Hardware version 1.00.01 /Firmware 1.07.02.

In the logs the command for both devices looks the same but "Kuecheninsel" does not change colour and "Ambilight Schlafzimmer" changes colour.

[31/03/2023, 17:05:04] [Govee] [Kuecheninsel] current colour [rgb 99 255 56]. [31/03/2023, 17:05:11] [Govee] [Ambilight Schlafzimmer] current colour [rgb 99 255 56].

Within the Govee app I can change the colour.

bwp91 commented 1 year ago

@johannes-schilling please try this:

Please use the “light devices” section of the plugin config screen to enter the device id of the model that doesn’t change colour and a label. Then use the “aws colour mode” option to change to an option that is NOT the colorwc option. Restart the plugin and see if this works. If not then try the other non-colorwc option. restart and try again.

please let me know if either of these options work for the colour

johannes-schilling commented 1 year ago

@bwp91: Thanks for this hint.

Now everything is working as expected. Issue can be marked as resolved :)