govee2mqtt no longer works (login + API) – “Service not enabled” after recent Govee changes

[andrea-git]

Govee Device SKU

Everyone

Govee2MQTT Version

2026.03.25-ab9deb66

Describe the issue

Since today, govee2mqtt has completely stopped working after what appears to be a change on Govee’s side.

Symptoms:

Add-on starts correctly but fails to retrieve devices

Log always shows:

Got unexpected response from the API: Service not enabled
Devices cannot be controlled from Home Assistant

What I tested:

Re-generated a new API key → same error
Used an invalid API key → same error (no distinction in logs)
Removed API key and used only email/password → same error
Restored a previous Home Assistant backup (when it was working) → still broken
Downgraded govee2mqtt to an older version (pre-March 2026) → still broken

Observations:

The error does not change regardless of credentials or API key validity
This suggests the issue is not configuration-related
It looks like either:
Govee changed or blocked the login flow used by the addon, or
API access is now restricted and unavailable for this account

Important detail:

Everything was working earlier the same day
After a restart/update, it stopped working and never recovered

Expected behavior:

Login (email/password) or API key should allow retrieving and controlling devices

Actual behavior:

All authentication methods fail with the same “Service not enabled” response

Questions:

Has Govee recently changed authentication or API endpoints?
Is there any known workaround or required update?

Thanks.

[QuantumDelta]

Great troubleshooting!
I went through most of the same steps and can corroborate your results I haven't found a work around yet, and unfortunately, it seems most of my bulbs don't have "LAN API" options so sort of stuck right now.
This might well be Govees side as it appears as though the devices are offline according to the alexa->govee skill as well.

[andrea-git]

In my case, alexa skill works correctly.

[QuantumDelta]

Scratch that; I forgot that months and months ago I had disabled all my lights in alexa for reasons I don't quite remember, she had been interfacing with the home assistant provided entity which was managed via Govee2MQTT, upon re-enabling they do work fine.

[QuantumDelta]

Looks like this problem was hit over at homebridge-plugins/homebridge-govee#1247

Seems like @bwp91 hit the same issue and has a work around in his beta update!

[andrea-git]

I don't think so, but I hope so :). Did you try it?

[brian316]

i got this fixed for me but not able to retrace my steps exactly.

i believe it was fixed for me by

1. removing mqtt broker service from home assistant
2. commenting out api key in .env
3. stopping docker service docker compose down
4. removing the stopped container docker rm govee2mqtt
5. starting up the service again docker compose pull && docker compose up -d (verify no errors here in logs)
6. uncommenting api key in .env
7. stopping docker service docker compose down
8. starting up the service once again docker compose pull && docker compose up -d

verified by watching these logs

1. docker logs docker logs govee2mqtt
2. mqtt client mosquitto_sub -h 127.0.0.1 -v -t "homeassistant/#" -u USERNAME -P PASSWORD

[enoversum]

I just updated the bridge, only to find my three Govee lights not working anymore (just +1-ing this one).

Edit: Not the same problem, I suppose (error 400), added my comment to the right issue here.

[Speshman]

I was getting the following error following the latest update

[15:53:30] ERROR: Got unexpected response from the API: Service not enabled [15:53:30] INFO: MQTT broker not ready yet (attempt 30/30), waiting 2 seconds... [15:53:32] ERROR: MQTT broker did not become available after 30 attempts [15:53:32] FATAL: Mosquitto MQTT broker is not available

I entered my mqqt details in manually instead of relying for it to auto find them and it seems to have resolved for now. I didnt touch the API

[wi1k1n]

got the same error 400.
fixed by:

1. invalidating credentials (just changing the api code somehow, so that it invalid)
2. restarting Govee to MQTT Bridge app
3. resetting the api code back to the correct one
4. restarting Govee to MQTT Bridge app

seems to be some caching issue or something like that

[enoversum]

got the same error 400. fixed by:

1. invalidating credentials (just changing the api code somehow, so that it invalid)
2. restarting Govee to MQTT Bridge app
3. resetting the api code back to the correct one
4. restarting Govee to MQTT Bridge app

seems to be some caching issue or something like that

Sorry, I'm not quite catching you. So you basically invalidated and corrected your API credentials, and now it's working fine?
Edit: Did exactly as you described, but devices are still unavailable.
Edit II: Took a moment, now the devices are back, thanks for the tip!

[techiem2]

I was getting the following error following the latest update

[15:53:30] ERROR: Got unexpected response from the API: Service not enabled [15:53:30] INFO: MQTT broker not ready yet (attempt 30/30), waiting 2 seconds... [15:53:32] ERROR: MQTT broker did not become available after 30 attempts [15:53:32] FATAL: Mosquitto MQTT broker is not available

I entered my mqqt details in manually instead of relying for it to auto find them and it seems to have resolved for now. I didnt touch the API

This just worked for me as well.

[rpscholtz]

I was getting the following error following the latest update
[15:53:30] ERROR: Got unexpected response from the API: Service not enabled [15:53:30] INFO: MQTT broker not ready yet (attempt 30/30), waiting 2 seconds... [15:53:32] ERROR: MQTT broker did not become available after 30 attempts [15:53:32] FATAL: Mosquitto MQTT broker is not available
I entered my mqqt details in manually instead of relying for it to auto find them and it seems to have resolved for now. I didnt touch the API

This just worked for me as well.

Entered details manually and working 100%

[Fanton69]

[20:29:44] ERROR: Got unexpected response from the API: Service not enabled
[20:29:44] INFO: MQTT broker not ready yet (attempt 28/30), waiting 2 seconds...
[20:29:47] ERROR: Got unexpected response from the API: Service not enabled
[20:29:47] INFO: MQTT broker not ready yet (attempt 29/30), waiting 2 seconds...
[20:29:49] ERROR: Got unexpected response from the API: Service not enabled
[20:29:49] INFO: MQTT broker not ready yet (attempt 30/30), waiting 2 seconds...
[20:29:51] ERROR: MQTT broker did not become available after 30 attempts
[20:29:51] FATAL: Mosquitto MQTT broker is not available
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: warning: service s6rc-oneshot-runner is marked as essential, not stopping it
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[20:29:54] INFO: mqtt_host was not explicitly configured, waiting for the Mosquitto broker Add-on to become available
[20:29:54] ERROR: Got unexpected response from the API: Service not enabled
[20:29:54] INFO: MQTT broker not ready yet (attempt 1/30), waiting 2 seconds...
[20:29:57] ERROR: Got unexpected response from the API: Service not enabled
[20:29:57] INFO: MQTT broker not ready yet (attempt 2/30), waiting 2 seconds...
[20:29:59] ERROR: Got unexpected response from the API: Service not enabled
[20:29:59] INFO: MQTT broker not ready yet (attempt 3/30), waiting 2 seconds...

What am I missing? I have tried all of the above but no dice?

[Speshman]

[20:29:44] ERROR: Got unexpected response from the API: Service not enabled [20:29:44] INFO: MQTT broker not ready yet (attempt 28/30), waiting 2 seconds... [20:29:47] ERROR: Got unexpected response from the API: Service not enabled [20:29:47] INFO: MQTT broker not ready yet (attempt 29/30), waiting 2 seconds... [20:29:49] ERROR: Got unexpected response from the API: Service not enabled [20:29:49] INFO: MQTT broker not ready yet (attempt 30/30), waiting 2 seconds... [20:29:51] ERROR: MQTT broker did not become available after 30 attempts [20:29:51] FATAL: Mosquitto MQTT broker is not available s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: warning: service s6rc-oneshot-runner is marked as essential, not stopping it s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [20:29:54] INFO: mqtt_host was not explicitly configured, waiting for the Mosquitto broker Add-on to become available [20:29:54] ERROR: Got unexpected response from the API: Service not enabled [20:29:54] INFO: MQTT broker not ready yet (attempt 1/30), waiting 2 seconds... [20:29:57] ERROR: Got unexpected response from the API: Service not enabled [20:29:57] INFO: MQTT broker not ready yet (attempt 2/30), waiting 2 seconds... [20:29:59] ERROR: Got unexpected response from the API: Service not enabled [20:29:59] INFO: MQTT broker not ready yet (attempt 3/30), waiting 2 seconds...

What am I missing? I have tried all of the above but no dice?

set your mqtt info in advanced options in the config for govee

[Fanton69]

[20:29:44] ERROR: Got unexpected response from the API: Service not enabled [20:29:44] INFO: MQTT broker not ready yet (attempt 28/30), waiting 2 seconds... [20:29:47] ERROR: Got unexpected response from the API: Service not enabled [20:29:47] INFO: MQTT broker not ready yet (attempt 29/30), waiting 2 seconds... [20:29:49] ERROR: Got unexpected response from the API: Service not enabled [20:29:49] INFO: MQTT broker not ready yet (attempt 30/30), waiting 2 seconds... [20:29:51] ERROR: MQTT broker did not become available after 30 attempts [20:29:51] FATAL: Mosquitto MQTT broker is not available s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: warning: service s6rc-oneshot-runner is marked as essential, not stopping it s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started [20:29:54] INFO: mqtt_host was not explicitly configured, waiting for the Mosquitto broker Add-on to become available [20:29:54] ERROR: Got unexpected response from the API: Service not enabled [20:29:54] INFO: MQTT broker not ready yet (attempt 1/30), waiting 2 seconds... [20:29:57] ERROR: Got unexpected response from the API: Service not enabled [20:29:57] INFO: MQTT broker not ready yet (attempt 2/30), waiting 2 seconds... [20:29:59] ERROR: Got unexpected response from the API: Service not enabled [20:29:59] INFO: MQTT broker not ready yet (attempt 3/30), waiting 2 seconds...
What am I missing? I have tried all of the above but no dice?

set your mqtt info in advanced options in the config for govee

Thank you my man! I never saw the advances options... Entered my MQTT info and it worked immediately. Appreciate your help.