You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The add-on starts and then shuts down. It was working fine till yesterday. No change on Home Assistant side. This morning, I just restarted HA after updating couple of other add-ons and noticed that all Govee devices were offline. When they remained offline for several hours, I checked the Govee2MQTT logs and it looks like it is not able to logon.
Startup Diagnostics
GOVEE_API_KEY=REDACTED
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_TEMPERATURE_SCALE=C
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-09-16T16:13:44 INFO govee::commands::serve] Starting service. version 2024.07.13-82ddc6e9
[2024-09-16T16:13:44 INFO govee::commands::serve] Querying platform API for device list
[2024-09-16T16:13:44 INFO govee::commands::serve] Querying undocumented API for device + room list
Error: request https://app2.govee.com/device/rest/devices/v1/list status 200: OK
Caused by:
0: parsing https://app2.govee.com/device/rest/devices/v1/list response
1: Failed with status 401 Unauthorized Unauthorized: Request to https://app2.govee.com/device/rest/devices/v1/list failed with code 401 Unauthorized please login. Full response: {"message":"please login","status":401}
Stack backtrace:
0: anyhow::context::<impl anyhow::Context<T,E> for core::result::Result<T,E>>::with_context
1: govee::undoc_api::GoveeUndocumentedApi::get_device_list::{{closure}}
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_common::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: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Additional Logs
No response
Home Assistant Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
This morning, at 7:00 AM, the add-on started working fine. I did not do anything. Maybe some issue on Govee side? No idea. But things are working fine as of now.
This morning, at 7:00 AM, the add-on started working fine. I did not do anything. Maybe some issue on Govee side? No idea. But things are working fine as of now.
I experienced the same issue last night and it appeared to have resolved itself this morning. Assumed it was on the Govee side as well.
Govee Device SKU
Any device
Govee2MQTT Version
2024.07.13-82ddc6e9
Describe the issue
The add-on starts and then shuts down. It was working fine till yesterday. No change on Home Assistant side. This morning, I just restarted HA after updating couple of other add-ons and noticed that all Govee devices were offline. When they remained offline for several hours, I checked the Govee2MQTT logs and it looks like it is not able to logon.
Startup Diagnostics
Additional Logs
No response
Home Assistant Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: