Discussions

I have the API key up and running successfully with 8 devices being detected. 4 devices are not detected - they are all H6004 series WiFi + Bluetooth bulbs.
I've verified that all 4 are connected to my WiFi router by verifying them in the app, and also verifying they have IP addresses assigned to them in the DHCP routing table on my router.

Since we have all this new functionality I was thinking about some of the quirks with end users having to get API tokens. I wanted to start a conversation about a better way to obtain API Keys. It would be nice if there was a authenticated way we can have users obtain the key/token instead of the formal request through the app.

So far the documentation has been written up very good to cover how the new API works, but I do have a problem with how to obtain information for all of the possible devices Govee makes. Simply put i do not have a way to obtain the device capabilities and data unless I first have the device. I would like to propose a solution to that

When integrating this with HA Platforms they often support a fade over time. I would like to request ability be added to the new API. I would suggest it be added to the command to set brightness.

Hey all,

It is returned with H713C as:

I send:

My tower fan has been unplugged for about 2 weeks now, and the app (correctly) shows it as "Not Connected".

Is there a issue with folks getting new API tokens's not being able to access the new API. I have had a few users hit me up with issues getting devices to do simple things. The ironic thing is I can do it with my setup and in some cases we have the exact same device models.

Would be great to have API support for H5074 units that are set up with "Remote View"