govee2mqtt

GoveeToMQTT Bridge not working HA Version: 2026.10.2 Just started using HA this week and this is the only integration I cannot get to work. I have some recessed lights (H601E) from Govee that I installed in Govee where they work great, but I cant get the MQTT piece to work at all. They allow matter (No LAN available), but each device has two lights and animation options that aren't available through that interface. I keep getting this error at logon:454 (Full log below) I am positive the email/pw are accurate. Any help/advice would be greatly appreciated! [22:48:39] INFO: mqtt_host was not explicitly configured, waiting for the Mosquitto broker Add-on to become available [22:48:40] INFO: MQTT broker is ready! GOVEE_API_KEY=REDACTED GOVEE_MQTT_HOST=core-mosquitto GOVEE_TEMPERATURE_SCALE=F GOVEE_EMAIL=REDACTED GOVEE_PASSWORD=REDACTED GOVEE_MQTT_PASSWORD=REDACTED GOVEE_MQTT_USER=addons GOVEE_MQTT_PORT=1883 ++ cd /app ++ exec /app/govee serve [2026-10-17T22:48:40 INFO govee::commands::serve] Starting service. version 2026.03.25-ab9deb66 [2026-10-17T22:48:40 INFO govee::commands::serve] Querying platform API for device list [2026-10-17T22:48:40 INFO govee::commands::serve] Querying undocumented API for device + room list Error: Error during initial undoc API discovery: request app2.govee.com status 200: OK: parsing app2.govee.com response: Failed with status 454 <unknown status code> : Request to app2.govee.com failed with code 454 <unknown status code> . Full response: {"status":454,"message":""} Startup cannot automatically continue because entity names could become inconsistent especially across frequent similar intermittent issues if/as they occur on an ongoing basis. Please see govee2mqtt#76 A workaround is to remove the Govee API credentials from your configuration, which will cause this govee2mqtt to use only the LAN API. Two consequences of that will be loss of control over devices that do not support the LAN API, and also devices changing entity ID to less descriptive names due to lack of metadata availability via the LAN API. Stack backtrace: 0: anyhow::error::<impl anyhow::Error>::msg 1: anyhow::private::format_err 2: govee::commands::serve::ServeCommand::run::{{closure}} 3: govee::Args::run::{{closure}} 4: tokio::runtime::park::CachedParkThread::block_on 5: tokio::runtime::context::runtime::enter_runtime 6: tokio::runtime::runtime::Runtime::block_on 7: govee::main 8: std::sys::backtrace::rust_begin_short_backtrace 9: std::rt::lang_start::{{closure}} 10: std::rt::lang_start_internal 11: main 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