Govee Appliances (Heaters, Fans, Purifiers)

Not yet Because I don’t own one. I can give you on/off support immediately and if you want more, you’ll need to paste me your API response as an issue in the repo.
I put the URI in the readme.

1 Like

Awesome! I see it has fan support for the air purifier. I assume that’s just an on/off switch entity? Do you know if this new API would support reading the actual air quality values into HA? I’m happy to help contribute code. I was just looking into getting a smart air purifier where I could read the air quality values into HA.

I have an air purifier which is, at this time, fully operational using this integration. The air purifier supports on off as well as preset modes including fan speed.
The API does not offer air quality readings or filter lifetime readings just yet. Therefore these objects are not yet available. As soon as the API offers them I will implement.

1 Like

Ah, I just saw that the air purifier doesn’t have a built in air quality monitor anyway… they made that a little misleading in the product description… it apparently has to be paired with a separate air quality monitor.

Sorry,

but does anyone have the same problem as me? Turning on/ff works, but changing modes does not do anything:

I’m using a h713a space-heater.

After struggling with this integration for the past few days, I figured I should post about my experience with the Govee API, Homebridge, and Home Assistant.

When I started integrating this, I figured I would use the API method to control my H7130 and H7135 heaters. The first problem I encountered was finding the 23-character product ID. I don’t know if the Govee App changed, but I could not find it in the App, and posting an API request didn’t return anything (more on that. soon).

Since I couldn’t find the Device ID, I loaded Homebridge in a Docker container on my Synology to see if it could retrieve the IDs. It worked like a charm. As soon as I loaded the Govvee plugin and rebooted Home Bridge, the Device IDs popped up in the log files.

Armed with the Device IDs, I set up my rest command for the appliance, I set up my script, and I wrote an automation to turn on and off the H7130 heater. Then, I set up a button to trigger the automation, and everything worked perfectly. Hurray. Little did I know that was the last time I would see success for a while.

Next, I focused on controlling the Mode, Fan, and Temperature. I tried every variation of the API commands I could think of. I read the API documentation (it’s very sparse, btw), and nothing worked. So, I tried sending an API command to query the device’s state. No luck. I tried PUT commands and GET. Apparently (and as suggested in the above posts), you can’t query the state of the Govee devices as of July 10th, 2024. Hopefully, these changes will happen in the future, but by this time, I was fed up and decided to return to the Homebridge integration.

When I tried to get that to work on my Synology, I quickly realized that the Node.js version on Synology is 12.0, and Homebridge requires version 20. So, I decided to load Homebridge on my HA Yellow. That worked great, except that HA complained that this was a non-supported change to the system and I should remove Homebridge. So, I created a VM on my Synology with Ubuntu and loaded Homebridge on that. That was the answer. It worked great, and I now have a VM with a clean version of Linux on it, so I can also load other apps on it in the future. Yeah!

So here’s where I stand after three days of work. The Govee integration works great through Homebridge and appears in HA under Homekit. For the H7130 heater, I can query and control the temperature and on/off. For the H7135, I can query and control the on/off, temperature, and fan mode.

In summary. If all you want to control is the on/off, then I recommend using the API. You won’t be able to query the status of your heater (but you could plug it into a smart plug and query the state that way). If you want to control or query anything else, I suggest Homebridge. As an added benefit, Homebridge does not require any API keys. All you need is your username and password for the Govee app. The downside to Homebridge is you need a separate app running on a machine at all times.

I hope this helps.

Update: I found a way to make the query work using the following command: curl -X GET “https://openapi.api.govee.com/router/api/v1/user/devices” -H "Govee-API-Key: xxxx-xxxx-xxxx-xxxx-xxxx (where x represents your API key).

I will continue working on this to see if I can get the API method to work.

Second Update: I found this integration referenced above on Github: async_forward_entry_setup Warning for GoveeLife Integration · Issue #16 · disforw/goveelife · GitHub

It does everything I want it to so I am abandoning Homebridge in favor of the native integration.

1 Like