http port already in use - how to change port?
Opened this issue · 1 comments
Govee Device SKU
H6110, H6199
Govee2MQTT Version
2024.04.29-30cf7732
Describe the issue
Hi there,
when I try to start this, the connection will be established to Govee.
The devices will be found, but cannot be stored.
The port use by this addon is already in use by another application. If I stop that, it surely will work, but this is not a possible option right now.
Is it possible to change the port, manually?
Maybe you can add a config field to specify a http-port if someone has the same case.
Startup Diagnostics
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=C
GOVEE_EMAIL=REDACTED
GOVEE_PASSWORD=REDACTED
GOVEE_MQTT_PASSWORD=REDACTED
GOVEE_MQTT_USER=myuser
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-05-22T02:29:54 INFO govee::commands::serve] Starting service. version 2024.04.29-30cf7732
[2024-05-22T02:29:54 INFO govee::commands::serve] Querying platform API for device list
[2024-05-22T02:29:55 INFO govee::commands::serve] Querying undocumented API for device + room list
[2024-05-22T02:29:57 INFO govee::service::iot] Connected to IoT: CONNACK code 0: Connection Accepted.
[2024-05-22T02:29:57 INFO govee::service::iot] IoT (re)connected with status CONNACK code 0: Connection Accepted.
[2024-05-22T02:29:57 INFO govee::commands::serve] Starting LAN discovery
[2024-05-22T02:29:57 INFO govee::commands::serve] Waiting 10 seconds for LAN API discovery
[2024-05-22T02:30:07 INFO govee::commands::serve] Devices returned from Govee's APIs
[2024-05-22T02:30:07 INFO govee::commands::serve] Licht Sofa (3C:62:A4:C1:22:F7:11:E9 H6110)
[2024-05-22T02:30:07 INFO govee::commands::serve] Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-05-22T02:30:07 INFO govee::commands::serve] color_temp=Some((2000, 9000)) segment_rgb=None
[2024-05-22T02:30:07 INFO govee::commands::serve] Undoc: room=None supports_iot=true ble_only=false
[2024-05-22T02:30:07 INFO govee::commands::serve]
[2024-05-22T02:30:07 INFO govee::commands::serve] Licht Fernseher (9C:EC:44:C1:38:4D:33:04 H6110)
[2024-05-22T02:30:07 INFO govee::commands::serve] Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-05-22T02:30:07 INFO govee::commands::serve] color_temp=Some((2000, 9000)) segment_rgb=None
[2024-05-22T02:30:07 INFO govee::commands::serve] Undoc: room=None supports_iot=true ble_only=false
[2024-05-22T02:30:07 INFO govee::commands::serve]
[2024-05-22T02:30:07 INFO govee::commands::serve] DreamView (24:88:D9:32:37:99:71:25 H6199)
[2024-05-22T02:30:07 INFO govee::commands::serve] Platform API: devices.types.light. supports_rgb=true supports_brightness=true
[2024-05-22T02:30:07 INFO govee::commands::serve] color_temp=Some((2000, 9000)) segment_rgb=Some(0..15)
[2024-05-22T02:30:07 INFO govee::commands::serve] Undoc: room=None supports_iot=true ble_only=false
[2024-05-22T02:30:07 INFO govee::commands::serve]
Error: Starting HTTP service on port 8056
Caused by:
0: run_http_server: binding to port 8056
1: Address in use (os error 98)
Stack backtrace:
0: anyhow::context::<impl anyhow::Context<T,E> for core::result::Result<T,E>>::with_context
1: govee::commands::serve::ServeCommand::run::{{closure}}
2: govee::Args::run::{{closure}}
3: tokio::runtime::park::CachedParkThread::block_on
4: tokio::runtime::context::runtime::enter_runtime
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/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:284:13
10: std::panicking::try::do_call
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
11: std::panicking::try
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
12: std::panic::catch_unwind
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
13: std::rt::lang_start_internal::{{closure}}
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:48
14: std::panicking::try::do_call
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:554:40
15: std::panicking::try
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panicking.rs:518:19
16: std::panic::catch_unwind
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/panic.rs:142:14
17: std::rt::lang_start_internal
at /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/std/src/rt.rs:148:20
18: 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
Hi there, are you running it on docker?