wez / govee2mqtt

Govee2MQTT: Connect Govee lights and devices to Home Assistant
MIT License
327 stars 18 forks source link

Login error on new add-on swap (same API setup as previous govee-hass) #159

Open jdy98p opened 3 months ago

jdy98p commented 3 months ago

Govee Device SKU

H705A

Govee2MQTT Version

2024.01.24-ea3cd430

Describe the issue

I switched add-ons per recommendation, but the new MQTT version is having an issue connecting to Govee API. I have removed the previous add-on. I have tripled checked the API key and login credentials, and they appear to be correct.

Startup Diagnostics

Including HA logs (below)

Additional Logs

No response

Home Assistant Logs

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 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 [2024-03-30T16:35:40 INFO govee::commands::serve] Starting service. version 2024.01.24-ea3cd430 [2024-03-30T16:35:40 INFO govee::commands::serve] Querying platform API for device list [2024-03-30T16:35:40 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::runtime::Runtime::block_on 6: govee::main 7: std::sys_common::backtrace::__rust_begin_short_backtrace 8: std::rt::lang_start::{{closure}} 9: core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/ops/function.rs:284:13 10: std::panicking::try::do_call at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:552:40 11: std::panicking::try at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:516:19 12: std::panic::catch_unwind at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panic.rs:142:14 13: std::rt::lang_start_internal::{{closure}} at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/rt.rs:148:48 14: std::panicking::try::do_call at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:552:40 15: std::panicking::try at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:516:19 16: std::panic::catch_unwind at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panic.rs:142:14 17: std::rt::lang_start_internal at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/rt.rs:148:20 18: std::rt::lang_start 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

Anything else?

No response

nerfslinger commented 2 months ago

Having the same issue:

[2024-04-20T21:41:11 INFO govee::commands::serve] Starting service. version 2024.01.24-ea3cd430 [2024-04-20T21:41:11 INFO govee::commands::serve] Querying platform API for device list [2024-04-20T21:41:11 INFO govee::commands::serve] Querying undocumented API for device + room list Error: request https://app2.govee.com/account/rest/account/v1/login status 200: OK: parsing https://app2.govee.com/account/rest/account/v1/login response: Failed with status 400 Bad Request Bad Request: Request to https://app2.govee.com/account/rest/account/v1/login failed with code 400 Bad Request Incorrect password. Full response: {"status":400,"message":"Incorrect password"}

Carltoffel commented 2 months ago

Same here. Did anyone figure it out yet?

Carltoffel commented 2 months ago

Removing email and password from the config did the trick: https://github.com/wez/govee2mqtt/issues/141#issuecomment-1957655671