-
Notifications
You must be signed in to change notification settings - Fork 67
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
H600D bulbs not appearing #191
Comments
i have this exact problem, what can i do then to fix this problem? |
i tried what this commenter did, and he's right, my led bulbs are working this way, however i tried to change it by going into the file and finding where you can change some stuff, and i couldn't find a way to change it, so id suggest trying to find an alternative until they fix this issue. also the new API works with other govee devices that still works with the old one |
I was also unable to find how to change it unfortunately, but I have found some more documentation on this new API, which appears to be much more powerful. @LaggAt I know you seem to have stopped work on this integration, but any chance you might be able to take a look at this? |
Found another solution, this integration https://github.com/wez/govee2mqtt has full support for the bulbs |
But does These bulbs support Local lan? i can't find the button that allows local lan on these bulbs. does it work for you |
IT WORKS, I thought this was for local API. thanks. however it's kinda slow and i can't set the actual white colour |
Version of the custom_component
Latest
Describe the bug
Currently, the H600D bulbs, and a few others, do not show up when using this integration. This appears to be because they use a slightly different version of the API to get device info and control them. In order to get the devices, this is the command.
Changing the URL from https://developer-api.govee.com/v1 to https://openapi.api.govee.com/router/api/v1/user/devices allows the bulbs to show up. It appears to be a slightly different API version.
I have verified that using my API key, the H600D bulbs show up in the response, proving that they support the API. However, the response appears to be in a different format to the current API. Here is just the response for one of my H600D bulbs.
{"sku":"H600D","device":"MAC_ADDRESS","deviceName":"Bulb 4","type":"devices.types.light","capabilities":[{"type":"devices.capabilities.on_off","instance":"powerSwitch","parameters":{"dataType":"ENUM","options":[{"name":"on","value":1},{"name":"off","value":0}]}},{"type":"devices.capabilities.range","instance":"brightness","parameters":{"unit":"unit.percent","dataType":"INTEGER","range":{"min":1,"max":100,"precision":1}}},{"type":"devices.capabilities.color_setting","instance":"colorRgb","parameters":{"dataType":"INTEGER","range":{"min":0,"max":16777215,"precision":1}}},{"type":"devices.capabilities.color_setting","instance":"colorTemperatureK","parameters":{"dataType":"INTEGER","range":{"min":2700,"max":6500,"precision":1}}},{"type":"devices.capabilities.music_setting","instance":"musicMode","parameters":{"dataType":"STRUCT","fields":[{"fieldName":"musicMode","dataType":"ENUM","options":[{"name":"Energic","value":5},{"name":"Rhythm","value":3},{"name":"Spectrum","value":6},{"name":"Rolling","value":4}],"required":true},{"unit":"unit.percent","fieldName":"sensitivity","dataType":"INTEGER","range":{"min":0,"max":100,"precision":1},"required":true},{"fieldName":"autoColor","dataType":"ENUM","options":[{"name":"on","value":1},{"name":"off","value":0}],"required":false},{"fieldName":"rgb","dataType":"INTEGER","range":{"min":0,"max":16777215,"precision":1},"required":false}]}},{"type":"devices.capabilities.dynamic_scene","instance":"lightScene","parameters":{"dataType":"ENUM","options":[]}},{"type":"devices.capabilities.dynamic_scene","instance":"diyScene","parameters":{"dataType":"ENUM","options":[]}}]}]}
It seems Govee have changed their API for some newer devices. I don't fully understand why, or how it works, but hopefully the integration can be updated to support these bulbs.
If I can help test anything with this new API/Bulbs, I would be happy to too!
The text was updated successfully, but these errors were encountered: