wez / govee2mqtt

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

A few of my devices stopped working today #208

Closed Minniemie closed 3 weeks ago

Minniemie commented 4 weeks ago

Govee Device SKU

H6062 H6062 H6072

Govee2MQTT Version

2024.04.29-30cf7732

Describe the issue

here is the error msg :

Anyone else experieincing this?

[2024-06-02T20:33:07 INFO govee::commands::serve] Starting service. version 2024.04.29-30cf7732 [2024-06-02T20:33:07 INFO govee::commands::serve] Querying platform API for device list [2024-06-02T20:33:07 INFO govee::commands::serve] Querying undocumented API for device + room list Error: database disk image is malformed

Caused by: Error code 11: The database disk image is malformed

Stack backtrace: 0: anyhow::error::<impl core::convert::From for anyhow::Error>::from 1: govee::cache::cache_get::{{closure}} 2: govee::undoc_api::GoveeUndocumentedApi::login_account_cached::{{closure}} 3: govee::commands::serve::ServeCommand::run::{{closure}} 4: govee::Args::run::{{closure}} 5: tokio::runtime::park::CachedParkThread::block_on 6: tokio::runtime::context::runtime::enter_runtime 7: tokio::runtime::runtime::Runtime::block_on 8: govee::main 9: std::sys_common::backtrace::__rust_begin_short_backtrace 10: std::rt::lang_start::{{closure}} 11: core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:284:13 12: std::panicking::try::do_call at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40 13: std::panicking::try at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19 14: std::panic::catch_unwind at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14 15: std::rt::lang_start_internal::{{closure}} at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:48 16: std::panicking::try::do_call at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40 17: std::panicking::try at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19 18: std::panic::catch_unwind at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14 19: std::rt::lang_start_internal at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:20 20: 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

Startup Diagnostics

10: std::rt::lang_start::{{closure}} 11: core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:284:13 12: std::panicking::try::do_call at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40 13: std::panicking::try at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19 14: std::panic::catch_unwind at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14 15: std::rt::lang_start_internal::{{closure}} at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:48 16: std::panicking::try::do_call at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40 17: std::panicking::try at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19 18: std::panic::catch_unwind at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14 19: std::rt::lang_start_internal at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:20 20: 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 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 ++ cd /app ++ exec /app/govee serve 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 [2024-06-02T20:36:33 INFO govee::commands::serve] Starting service. version 2024.04.29-30cf7732 [2024-06-02T20:36:33 INFO govee::commands::serve] Querying platform API for device list [2024-06-02T20:36:33 INFO govee::commands::serve] Querying undocumented API for device + room list Error: database disk image is malformed

Caused by: Error code 11: The database disk image is malformed

Stack backtrace: 0: anyhow::error::<impl core::convert::From for anyhow::Error>::from 1: govee::cache::cache_get::{{closure}} 2: govee::undoc_api::GoveeUndocumentedApi::login_account_cached::{{closure}} 3: govee::commands::serve::ServeCommand::run::{{closure}} 4: govee::Args::run::{{closure}} 5: tokio::runtime::park::CachedParkThread::block_on 6: tokio::runtime::context::runtime::enter_runtime 7: tokio::runtime::runtime::Runtime::block_on 8: govee::main 9: std::sys_common::backtrace::__rust_begin_short_backtrace 10: std::rt::lang_start::{{closure}} 11: core::ops::function::impls::<impl core::ops::function::FnOnce for &F>::call_once at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:284:13 12: std::panicking::try::do_call at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40 13: std::panicking::try at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19 14: std::panic::catch_unwind at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14 15: std::rt::lang_start_internal::{{closure}} at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:48 16: std::panicking::try::do_call at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40 17: std::panicking::try at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19 18: std::panic::catch_unwind at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14 19: std::rt::lang_start_internal at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:20 20: 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 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

Additional Logs

No response

Home Assistant Logs

No response

Anything else?

No response

wez commented 4 weeks ago

Sounds like you had a bad crash on the device running haos, and the cache database is corrupted. I would suggest removing and re-adding the addon.

Minniemie commented 4 weeks ago

You're a star! You got it right indeed, had to uninstall and reinstall the add-on. Much thanks Wez!