Govee2MQTT errors and unstable behavior

Third party integrations
1

I wonder if I have too many Govee devices for Govee2MQTT or I do remember there was a limitation to how many messages were allowed. Regardless, I am positive my API key, username and password are correct.

I have a lot of things and not all of them turn on or off when I call them on my automations. I am also seeing errors and 401 warnings, too.

I have the MQTT integration, which I use. I have cloud available if I need to and I could have LAN if that would be preferred. I do have the leak sensors and the clound integration works with them, not MQTT.

I even generated a new API key.

If it is that I just have too much stuff (and I am getting more), how do I change the configuration to back off on how much gets sent to and from Govee?

All my lights are set to allow LAN control, too. I would rather not use the cloud if I do not have to but it did not seem as if I could run LAN and Cloud together.

MQTT runs on my Home Assistant VM

I would be happy to upload a log file but it is not letting me on here. However, here are some examples of error messages and warnings, and they seem to be on Govee’s end.

[2026-09-14T19:46:01 e[1me[31mERRORe[0m govee::commands::serve] while polling Office AI Sync Box (75:2C:E4:68:E5:B8:65:82 H6603): get_device_state: request https://openapi.api.govee.com/router/api/v1/device/state status 401: Unauthorized. Response body: 

[2026-09-14T19:46:02 e[1me[31mERRORe[0m govee::commands::serve] while polling Stairwell Strip Light (0D:65:F1:66:04:C6:2C:0A H61E5): get_device_state: request https://openapi.api.govee.com/router/api/v1/device/state status 401: Unauthorized. Response body: 

[2026-09-14T19:46:06 e[33mWARN e[0m govee::cache] request https://openapi.api.govee.com/router/api/v1/device/scenes status 401: Unauthorized. Response body: , will use prior results
[2026-09-14T19:46:06 e[33mWARN e[0m govee::cache] request https://openapi.api.govee.com/router/api/v1/device/diy-scenes status 401: Unauthorized. Response body: , will use prior results
[2026-09-14T19:46:20 e[33mWARN e[0m govee::cache] request https://openapi.api.govee.com/router/api/v1/device/scenes status 401: Unauthorized. Response body: , will use prior results
[2026-09-14T19:46:20 e[33mWARN e[0m govee::cache] request https://openapi.api.govee.com/router/api/v1/device/scenes status 401: Unauthorized. Response body: , will use prior results
[2026-09-14T19:46:20 e[33mWARN e[0m govee::cache] request https://openapi.api.govee.com/router/api/v1/device/diy-scenes status 401: Unauthorized. Response body: , will use prior results
[2026-09-14T19:46:20 e[33mWARN e[0m govee::cache] request https://openapi.api.govee.com/router/api/v1/device/diy-scenes status 401: Unauthorized. Response body: , will use prior results
2

If it helps, here is my configuration (passwords and API key stripped out)

temperature_scale: F
mqtt_username: [MQTT Connection Username]
mqtt_password: [MQTT Connection Password]
govee_email: [GOVEE Username]
govee_password: [GOVEE PASSWORD]
mqtt_host: [Inside IP Address of my HA server running MQTT]
mqtt_port: 1883
govee_api_key: [GOVEE API KEY]
3

Nevermind. My API Key was not up to date even though I swear I used the correct. Maybe someone can learn from my mistake…