This is amazing!!!
I can’t wait to get started on this. Count me in!
Are we thinking of moving to an official HA integration? Or HACS?
Keep in mind, there is already an official Govee bluetooth integration, and a custom component for Govee lights (on the old API).
I can get started on a logo PR if you want.
Interesting, thank you. Early returns. It failed to find my 2 fans, humidifier, and purifier. It found my heater (7131) but only shows the power switch and it is unavailable. Not sure what I could have done wrong since it did find all lights and they seem to work properly.
HACS is already implemented.
I am not planning for an official integration - not did this for any of my other integrations. But would be happy if someone wants to take over code into official integration. At the moment the integration is only a necessary thing for me to get rid of too many manual sensors etc 
Feel free about logo PR - at the moment I am still mainly focusing on the functionality … so logo has lower priority
As written here and in the github page I only have a single heater + the example states from api documentation page (which are unfortunately only lights).
Please provide the diagnostics output of the integration and I might be able to get some of functionality of your fans, humidifier & purifier working.
for what its worth- I also plan on getting another heater and would like the integration to support multiple devices.
I’ve had success with another project: GitHub - wez/govee2mqtt: Govee2MQTT: Connect Govee lights and devices to Home Assistant
I wonder if these could be combined and underscores the need for an official integration in my mind.
I’ve also had success with govee2mqtt. The biggest hurdle has been a lot of inconsistency and limitations in the new API from Govee. Hopefully the API improves, as those issues will plague any integration that uses it.
Followed the govee2mqtt/docs/ADDON.md at main · wez/govee2mqtt (github.com) and everything worked perfectly
Govee2mqtt seems like highly integrated & documented to me.
Really great solution.
makes a stand-alone integration obsolete to me.
Think I do not need to investigate more into the jus released one 
@mk-maddin I thought I saw some stuff in your repo that is lacking currently in govee2mqtt. Namely the use of standard typed entities allowing use of normal entity cards. If so, I suggest contributing to govee2mqtt if @wezfurlong is open to that?
Nonono! I’d rather help work on a proper integration with you… If you’re not interested, would you mind if I take your code?
I have an API key, and when running the curl command in my terminal I get an empty response:
{“data”:{“devices”:},“message”:“Success”,“code”:200}%
The Air Purifier H7126 is cloud connected (I have it linked to Alexa) and controlled there. Any ideas for why I can’t get it from a curl response?
Would need to see what you’re actually sending to the API to know why you’re not getting the data you want back.
curl --request GET
–url https://developer-api.govee.com/v1/devices/
–header ‘Content-Type: application/json’
–header ‘Govee-API-Key: mykey’
and I just get this back:
{“data”:{“devices”:},“message”:“Success”,“code”:200}%
curl --request GET
–url https://developer-api.govee.com/v1/appliance/devices/
–header ‘Content-Type: application/json’
–header ‘Govee-API-Key: API KEY’
That is the old API. Use this:
curl --request GET
–url https://openapi.api.govee.com/router/api/v1/user/devices
–header ‘Content-Type: application/json’
–header ‘Govee-API-Key: API KEY’
@mk-maddin do you happen to still have this code somewhere? I’d love to play around with it if you dont mind…
Lmk if you don’t hear back from mk-maddin, I still have his integration and can share if it can be an official Govee integration for heaters.
There’s really no need to have an integration for each separate appliance.
Govee2mqtt already does a ton of different lights and appliances.
The more information we give the dev about things acting up the better it should get
It is my understanding that MQTT devices wouldn’t come over the same way entities from an integration would come in. An example of this would be the govvy heater, instead of coming in as a single climate thermostat entity, it comes over as a bunch of different switch, select, and number entities.
Furthermore error handling and integration authentication would also be problematic using an MQTT platform.
If I’m wrong then it is my limited knowledge of MQTT…