Govee Smart Home Integration

Hey everyone, i am releasing my Govee integration:

This integration provides (hopefully) comprehensive control of Govee smart home devices through your Remote Two/3, dynamic device discovery and organization (SKU Based). The system automatically connects to your Govee account via Cloud API and creates an adaptive interface that scales from single devices to large installations without becoming cluttered. (This integration is Cloud based because for Local Direct controls it is limited to only lights and select devices and i wanted full support, and also i only have a smart kettle to use for testing lol).

Key Features:

  • Universal Device Support - Smart lights, kettles, plugs, switches, sensors, air purifiers, humidifiers

  • Dynamic Organization - Devices automatically grouped by model (SKU) across multiple UI pages

  • One-Step Setup - Enter free Govee API key, automatic device discovery in ~6 seconds

  • Secure - SSL handling, rate limiting, error recovery, multi-language support

  • Scalable Architecture - Handles 1-1000+ devices with clean, organized interface

  • Full Control - Power, brightness, RGB colors, temperature, work modes, scenes per device capabilities

Requirements: Govee account with devices, free Govee Developer API key (obtained via Govee Home app)

GitHub Repository: https://github.com/mase1981/uc-intg-govee

Thank you so much, hope it works!!!

All info in README.md file on GitHub

2 Likes

New version is up which fix toggle button

Thanks for great workšŸ™šŸ¼

1 Like

Anytime !!!

I am trying to add my Govee devices but am running into an issue. I enter my API key, I get the ā€œSetting up ā€¦ā€ screen for about 10 seconds, then the error:

Oops!

Something went wrong while setting up the integration.

CONNECTION_REFUSED

I’ve tried multiple times, with the same result. I’ve even requested and received a new API key, with the same result. I’ve set up another couple of integrations today with no problems. There is no Govee log to check. Any suggestions as to what the problem might be, or how to diagnose?

Check core logs.

I just tried again and the entries in the core log that appear to be relevant are as follows:

2025-10-21 01:39:52.777736 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl stop custom-intg@uc_intg_govee
2025-10-21 01:39:52.751451 +00:00 core NOTICE [uc_intg_govee] Session state change: Disconnected
2025-10-21 01:39:52.750570 +00:00 core NOTICE Execute system command: StopCustomIntegration(ā€œuc_intg_goveeā€, Some(ā€œcustom-intg@uc_intg_goveeā€))
2025-10-21 01:39:52.750021 +00:00 core NOTICE [uc_intg_govee] StopDriver msg
2025-10-21 01:39:52.749439 +00:00 core NOTICE Stopping driver ā€˜uc_intg_govee’: no more instances
2025-10-21 01:39:50.676852 +00:00 core NOTICE Setting rgb button backlight to: (0, 0, 0)
2025-10-21 01:39:50.676373 +00:00 core NOTICE Enter idle mode: standby in 150s
2025-10-21 01:39:43.935995 +00:00 core NOTICE Ok(DriverSetupChange { event_type: Stop, state: Error, error: Some(ConnectionRefused), require_user_action: None })
2025-10-21 01:39:43.351115 +00:00 core NOTICE Removed standby inhibitor: Integration setup: uc_intg_govee
2025-10-21 01:39:38.306390 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start custom-intg@uc_intg_govee
2025-10-21 01:39:38.284068 +00:00 core NOTICE Execute system command: StartCustomIntegration(ā€œuc_intg_goveeā€, Some(ā€œcustom-intg@uc_intg_goveeā€))
2025-10-21 01:39:38.279233 +00:00 core NOTICE Added standby inhibitor: Integration setup: uc_intg_govee

Issue is with connection refused which usually means wrong api. Redo the steps to get new key, read the read me file, there are a few suggestions to test outside of the remote to see if your govee devices are accessible.

Also, try to re download the tar.gz

Thanks for the suggestions. I’ve requested a new API key, removed the integration, redownloaded the tar.gz and reinstalled, but have the same problem.

I ran the command to test API connectivity from outside the remote and it succeeded returning the JSON file with my devices and their parameters.

Can you check if the remote is blocked on your router for getting network out to govee cloud services?

The remote is not blocked, I checked the network traffic flows to and from the remote and see no blocked traffic, and several outbound connections to openapi.api.govee.com on port 443.

Your issue is 100% connection refused from the remote to the govee server via your api.

Are you using govee hub, or app? Can you check your router logs? Connection refused is network issue where the request is being rejected. I cant replicate this. Sorry. Not sure how to help other then investigate on your network.

It certainly seems that way, but checking the router log shows that the remote is connecting to openapi.api.govee.com on port 443 successfully, no flows are being blocked. I’ve even set it to emergency access temporarily, so nothing too or from the remote’s IP address is blocked, no change.

I’ve no idea why testing connectivity from my PC to Govee works fine, but not from the remote, it makes no sense, at least not to me. I guess I’m stuck, thanks for trying.

1 Like

On the readme file on github I have some instructions on how to test your api key, if you comfortable with it, test your api key to make are your able to get it outside of the remote

I ran the curl command with my api key and it successfully returned my devices and their parameters, so it seems the key is working and I can access the Govee api from outside the remote.

I released a new version past night. It has no changes to authentication but it added support for other devices, version was tested working. Try it. If it still doesn’t work i am unsure how to help further, seems like your remote unable to access govee to authenticate. Are you using seperate vlans? Latest version confirmed working by myself and others.

Tried version 0.2.0, unfortunately no change. I don’t understand, as my Govee devices work, the remote works with all my other integrations (though I believe they are all operating over the local network, not over the WAN). I can access the api from multiple other devices from the command line, and using my hubitat home automation hub (which turns some of my Govee lights off at night). I am trying to diagnose with firewalla, but there are no rules set for the remote, so it shouldn’t behave any differently and the logs show the expected outbound traffic and nothing being blocked.

Thank you again for your help, its obviously something weird with my network, but it does seem there is something different when the remote tries to access the api vs other devices on the same network as they are communicating with the api without problems.

I just tested again for version 0.2.0 and it worked perfectly on first try:

I agree, it is on your network.

A few suggestion i could make, you have not answered also if your remote in on a seperate vlan?

i would do this:

  1. apply for a new API key
  2. completely turn off firewall for the test duration
  3. redo the integration using a new api key

if work, just need to figure out why the remote is blocked , this integration rely on the cloud access. if it still doesnt work with firewall off and the remote, i am honestly not sure. alternatively, maybe try to tether from your phone temporarily and connect your remote to your phone hotspot over your carrier network, just to rule out your local network

Hi,
I’ve got the same failure.
Connection refused after entering the API Key.
I tested the API Key with Home Assistant and there works fine but not with my Integration for the remote 3.
It would be great if you could help me. Attached the Log.

2025-10-28 17:45:19.684094 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl stop custom-intg@uc-intg-govee
2025-10-28 17:45:19.615660 +00:00 core NOTICE Execute system command: StopCustomIntegration(ā€œuc-intg-goveeā€, Some(ā€œcustom-intg@uc-intg-goveeā€))
2025-10-28 17:45:19.614986 +00:00 core NOTICE [uc-intg-govee] StopDriver msg
2025-10-28 17:45:19.614309 +00:00 core NOTICE Stopping driver ā€˜uc-intg-govee’: no more instances
2025-10-28 17:45:19.555401 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl stop custom-intg@uc-intg-govee
2025-10-28 17:45:19.492064 +00:00 core NOTICE [uc-intg-govee] Session state change: Disconnected
2025-10-28 17:45:19.489922 +00:00 core NOTICE Execute system command: StopCustomIntegration(ā€œuc-intg-goveeā€, Some(ā€œcustom-intg@uc-intg-goveeā€))
2025-10-28 17:45:19.488483 +00:00 core NOTICE [uc-intg-govee] StopDriver msg
2025-10-28 17:45:19.487779 +00:00 core NOTICE Stopping driver ā€˜uc-intg-govee’: no more instances
2025-10-28 17:45:13.415339 +00:00 core NOTICE Ok(DriverSetupChange { event_type: Stop, state: Error, error: Some(ConnectionRefused), require_user_action: None })
2025-10-28 17:45:11.122986 +00:00 core NOTICE Removed standby inhibitor: Integration setup: uc-intg-govee
2025-10-28 17:45:06.003680 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start custom-intg@uc-intg-govee
2025-10-28 17:45:05.940588 +00:00 core NOTICE Execute system command: StartCustomIntegration(ā€œuc-intg-goveeā€, Some(ā€œcustom-intg@uc-intg-goveeā€))
2025-10-28 17:45:05.935818 +00:00 core NOTICE Added standby inhibitor: Integration setup: uc-intg-govee
2025-10-28 17:45:00.273919 +00:00 core NOTICE [uc-intg-govee] SessionAuthenticated msg
2025-10-28 17:45:00.273423 +00:00 core NOTICE [uc-intg-govee] Session state change: Authenticated
2025-10-28 17:45:00.269902 +00:00 core WARN [uc-intg-govee] Failed to get integration session, not sending connect: BadRequest: Integration ID not found
2025-10-28 17:45:00.268905 +00:00 core NOTICE [uc-intg-govee] Session became active: sending subscribe_events, get_driver_version, connect
2025-10-28 17:45:00.267708 +00:00 core NOTICE [uc-intg-govee] SessionAuthenticated msg
2025-10-28 17:45:00.266473 +00:00 core NOTICE [uc-intg-govee] Session state change: Authenticated
2025-10-28 17:45:00.262520 +00:00 core NOTICE [uc-intg-govee] Connected to: ws://127.0.0.1:9002
2025-10-28 17:44:59.404107 +00:00 core ERROR [uc-intg-govee] Error connecting to driver ws://127.0.0.1:9002: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:44:58.747130 +00:00 core ERROR [uc-intg-govee] Error connecting to driver ws://127.0.0.1:9002: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:44:58.241503 +00:00 core ERROR [uc-intg-govee] Error connecting to driver ws://127.0.0.1:9002: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:44:54.540431 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start custom-intg@uc-intg-govee
2025-10-28 17:44:54.478528 +00:00 core NOTICE Execute system command: StartCustomIntegration(ā€œuc-intg-goveeā€, Some(ā€œcustom-intg@uc-intg-goveeā€))
2025-10-28 17:44:51.684503 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/opt/uc/integrations/install-custom-intg.sh /tmp/upload/intg uc-intg-govee 9002
2025-10-28 17:44:40.241658 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/opt/uc/integrations/extract-custom-intg.sh /tmp/upload/uc-intg-govee-0.2.0-aarch64.tar.gz /tmp/upload/intg
2025-10-28 17:44:18.340716 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl restart avahi-daemon
2025-10-28 17:44:18.279527 +00:00 core WARN Error encountered while processing the incoming HTTP request: NotFound
2025-10-28 17:44:18.278284 +00:00 core NOTICE Starting mDNS discovery for _uc-integration._tcp, timeout=30s
2025-10-28 17:44:14.108337 +00:00 core WARN Error encountered while processing the incoming HTTP request: NotFound
2025-10-28 17:43:35.502312 +00:00 core NOTICE No dock updates available
2025-10-28 17:43:35.382125 +00:00 core NOTICE Contacting OTA server for dock update check. Channel=testing, model=UCD3, version=0.8.0
2025-10-28 17:43:35.229792 +00:00 core NOTICE Check OTA server for UCD3 firmware update: UCD3-0BEB5C
2025-10-28 17:43:35.228532 +00:00 core NOTICE Created Dock IR emitter: dock_id=UCD3-0BEB5C, name=ā€˜Dock-Kinoraum’, model=UCD3, active=true, port_mask=0
2025-10-28 17:43:35.108731 +00:00 core NOTICE No dock updates available
2025-10-28 17:43:34.920373 +00:00 core NOTICE Added standby inhibitor: Web configurator
2025-10-28 17:43:34.914683 +00:00 core NOTICE Created Dock IR emitter: dock_id=UCD3-0C6E34, name=ā€˜Dock-Serverschrank’, model=UCD3, active=true, port_mask=12
2025-10-28 17:43:34.910064 +00:00 core NOTICE Contacting OTA server for dock update check. Channel=testing, model=UCD3, version=0.8.0
2025-10-28 17:43:34.722986 +00:00 core NOTICE Check OTA server for UCD3 firmware update: UCD3-0C6E34
2025-10-28 17:43:34.405911 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:43:33.848724 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:43:30.405220 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:43:30.392705 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:43:30.381020 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:43:27.999076 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:43:24.341455 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:43:20.843777 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:43:17.383597 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:43:13.845861 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:43:10.344918 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:43:06.843478 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:43:03.346364 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:42:59.847770 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:42:56.619139 +00:00 core NOTICE Setting rgb button backlight to: (0, 0, 0)
2025-10-28 17:42:56.617792 +00:00 core NOTICE Enter low-power mode: standby in 160s
2025-10-28 17:42:56.458572 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:42:52.843694 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:42:50.219792 +00:00 core NOTICE Sent get_entity_states to hass: Ok(())
2025-10-28 17:42:50.214324 +00:00 core NOTICE Sent get_entity_states to hass: Ok(())
2025-10-28 17:42:49.739716 +00:00 core NOTICE Sent get_entity_states to uc_appletv_driver: Ok(())
2025-10-28 17:42:49.498350 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:42:48.911579 +00:00 core NOTICE Sent get_entity_states to uc_appletv_driver: Ok(())
2025-10-28 17:42:48.895599 +00:00 core NOTICE [uc_appletv_driver] SessionAuthenticated msg
2025-10-28 17:42:48.895495 +00:00 core NOTICE [uc_appletv_driver] Session state change: Authenticated
2025-10-28 17:42:48.894550 +00:00 core NOTICE [uc_appletv_driver] Session became active: sending subscribe_events, get_driver_version, connect
2025-10-28 17:42:48.894244 +00:00 core NOTICE [uc_appletv_driver] SessionAuthenticated msg
2025-10-28 17:42:48.894001 +00:00 core NOTICE [uc_appletv_driver] Session state change: Authenticated
2025-10-28 17:42:48.891318 +00:00 core NOTICE [uc_appletv_driver] Connected to: ws://127.0.0.1:8097
2025-10-28 17:42:48.721485 +00:00 core WARN [UCD3-0C6E34] Can’t handle dock TryReconnect command in state: Active
2025-10-28 17:42:48.720925 +00:00 core WARN [UCD3-0C6E34] No transition for: state=Active, event=TryReconnect
2025-10-28 17:42:48.710126 +00:00 core WARN [UCD3-0BEB5C] Can’t handle dock TryReconnect command in state: Active
2025-10-28 17:42:48.708468 +00:00 core WARN [UCD3-0BEB5C] No transition for: state=Active, event=TryReconnect
2025-10-28 17:42:46.611740 +00:00 core NOTICE Setting rgb button backlight to: (0, 0, 0)
2025-10-28 17:42:46.610620 +00:00 core NOTICE Enter idle mode: standby in 170s
2025-10-28 17:42:46.226281 +00:00 core NOTICE Created Dock IR emitter: dock_id=UCD3-0BEB5C, name=ā€˜Dock-Kinoraum’, model=UCD3, active=true, port_mask=0
2025-10-28 17:42:46.153892 +00:00 core NOTICE [UCD3-0BEB5C] Authenticated (features=3)
2025-10-28 17:42:46.092328 +00:00 core NOTICE [UCD3-0BEB5C] Resolved ucd3-0beb5c.local: 192.168.1.70
2025-10-28 17:42:46.090016 +00:00 core NOTICE [UCD3-0BEB5C] Resolving: ucd3-0beb5c.local
2025-10-28 17:42:46.089479 +00:00 core NOTICE [UCD3-0BEB5C] Connected to: ws://ucd3-0beb5c.local/ws
2025-10-28 17:42:45.943053 +00:00 core NOTICE Created Dock IR emitter: dock_id=UCD3-0C6E34, name=ā€˜Dock-Serverschrank’, model=UCD3, active=true, port_mask=12
2025-10-28 17:42:45.882084 +00:00 core NOTICE [UCD3-0C6E34] Authenticated (features=3)
2025-10-28 17:42:45.845325 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:42:45.838119 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:42:45.825858 +00:00 core ERROR Error encountered while processing the incoming HTTP request: AuthError(ā€œAuthentication errorā€)
2025-10-28 17:42:45.825006 +00:00 core NOTICE No session state has been found for a valid session key, creating a new empty session.
2025-10-28 17:42:45.819979 +00:00 core NOTICE [UCD3-0C6E34] Resolved ucd3-0c6e34.local: 192.168.1.72
2025-10-28 17:42:45.816710 +00:00 core NOTICE [UCD3-0C6E34] Resolving: ucd3-0c6e34.local
2025-10-28 17:42:45.816182 +00:00 core NOTICE [UCD3-0C6E34] Connected to: ws://ucd3-0c6e34.local/ws
2025-10-28 17:42:45.754511 +00:00 core ERROR [uc_appletv_driver] Error connecting to driver ws://127.0.0.1:8097: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:42:46.780683 +00:00 core NOTICE [UCD3-0C6E34] WiFi connected: connecting dock
2025-10-28 17:42:46.780497 +00:00 core NOTICE [UCD3-0BEB5C] WiFi connected: connecting dock
2025-10-28 17:42:46.778800 +00:00 core NOTICE WiFi interface is up and routable, sending connected event
2025-10-28 17:42:46.776695 +00:00 core NOTICE Network changed: link_name: wlan0, operational_state: routable, address_state: routable, ipv4_address_state: routable, online_state: online
2025-10-28 17:42:46.756519 +00:00 core NOTICE [UCD3-0C6E34] Reconnecting in: 3.13s
2025-10-28 17:42:46.755937 +00:00 core ERROR [UCD3-0C6E34] Error connecting to dock ws://ucd3-0c6e34.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:46.745237 +00:00 core NOTICE [UCD3-0BEB5C] Reconnecting in: 3.13s
2025-10-28 17:42:46.744168 +00:00 core ERROR [UCD3-0BEB5C] Error connecting to dock ws://ucd3-0beb5c.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:46.691809 +00:00 core NOTICE Ignoring connected event from WiFi driver, using operational state instead
2025-10-28 17:42:46.690383 +00:00 core NOTICE Network changed: link_name: wlan0, operational_state: carrier, carrier_state: carrier
2025-10-28 17:42:46.657863 +00:00 core NOTICE Network changed: link_name: wlan0, operational_state: dormant, carrier_state: dormant
2025-10-28 17:42:46.091630 +00:00 core NOTICE WifiEvent: NETWORK_NOT_FOUND
2025-10-28 17:42:45.020709 +00:00 core NOTICE Sent get_entity_states to trinnov: Ok(())
2025-10-28 17:42:44.959400 +00:00 core NOTICE [trinnov] SessionAuthenticated msg
2025-10-28 17:42:44.959012 +00:00 core NOTICE [trinnov] Session state change: Authenticated
2025-10-28 17:42:44.948090 +00:00 core NOTICE [trinnov] Session became active: sending subscribe_events, get_driver_version, connect
2025-10-28 17:42:44.947372 +00:00 core NOTICE [trinnov] SessionAuthenticated msg
2025-10-28 17:42:44.944671 +00:00 core NOTICE [trinnov] Session state change: Authenticated
2025-10-28 17:42:44.939515 +00:00 core NOTICE [trinnov] Connected to: ws://127.0.0.1:9001
2025-10-28 17:42:44.509878 +00:00 core ERROR [uc_appletv_driver] Error connecting to driver ws://127.0.0.1:8097: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:42:44.341881 +00:00 core NOTICE [UCD3-0C6E34] Reconnecting in: 2.408s
2025-10-28 17:42:44.341339 +00:00 core ERROR [UCD3-0C6E34] Error connecting to dock ws://ucd3-0c6e34.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:44.332461 +00:00 core NOTICE [UCD3-0BEB5C] Reconnecting in: 2.408s
2025-10-28 17:42:44.331818 +00:00 core ERROR [UCD3-0BEB5C] Error connecting to dock ws://ucd3-0beb5c.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:43.827072 +00:00 core ERROR [trinnov] Error connecting to driver ws://127.0.0.1:9001: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:42:42.980809 +00:00 core ERROR [trinnov] Error connecting to driver ws://127.0.0.1:9001: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:42:42.654162 +00:00 core ERROR [uc_appletv_driver] Error connecting to driver ws://127.0.0.1:8097: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:42:42.481389 +00:00 core NOTICE [UCD3-0C6E34] Reconnecting in: 1.853s
2025-10-28 17:42:42.480891 +00:00 core ERROR [UCD3-0C6E34] Error connecting to dock ws://ucd3-0c6e34.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:42.472003 +00:00 core NOTICE [UCD3-0BEB5C] Reconnecting in: 1.853s
2025-10-28 17:42:42.471165 +00:00 core ERROR [UCD3-0BEB5C] Error connecting to dock ws://ucd3-0beb5c.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:42.359376 +00:00 core NOTICE Added standby inhibitor: charger
2025-10-28 17:42:42.358911 +00:00 core NOTICE Changed battery status: 96% Discharging, 3994mV, charger: false
2025-10-28 17:42:42.328637 +00:00 core ERROR [trinnov] Error connecting to driver ws://127.0.0.1:9001: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:42:41.826998 +00:00 core ERROR Error starting custom integration session: Failed to connect to host: Connection refused (os error 111)
2025-10-28 17:42:41.825220 +00:00 core ERROR [trinnov] Error connecting to driver ws://127.0.0.1:9001: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:42:41.229870 +00:00 core ERROR [uc_appletv_driver] Error connecting to driver ws://127.0.0.1:8097: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:42:41.101499 +00:00 core NOTICE BtDaemonStatus { status: Working, hci_log: true, log_level: Debug, connections: 0, max_connections: 1, paired_profiles: 0, active_profile: 0, advertising: true, advertising_name: ā€œRemote3 68DEFBā€, version: ā€œ0.6.0ā€ }
2025-10-28 17:42:41.092523 +00:00 core NOTICE [BT] Scan mode: discoverable=false, connectable=false
2025-10-28 17:42:41.049162 +00:00 core NOTICE [UCD3-0C6E34] Reconnecting in: 1.426s
2025-10-28 17:42:41.048543 +00:00 core ERROR [UCD3-0C6E34] Error connecting to dock ws://ucd3-0c6e34.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:41.036911 +00:00 core NOTICE [UCD3-0BEB5C] Reconnecting in: 1.426s
2025-10-28 17:42:41.036388 +00:00 core ERROR [UCD3-0BEB5C] Error connecting to dock ws://ucd3-0beb5c.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:40.556940 +00:00 core NOTICE BtDaemonStatus { status: Initializing, hci_log: true, log_level: Debug, connections: 0, max_connections: 1, paired_profiles: 0, active_profile: 0, advertising: true, advertising_name: ā€œRemote3 000000ā€, version: ā€œ0.6.0ā€ }
2025-10-28 17:42:40.556246 +00:00 core NOTICE Connected to BT daemon: 127.0.0.1:13333
2025-10-28 17:42:40.552500 +00:00 core NOTICE Restarting BT daemon client, enabled=true
2025-10-28 17:42:40.124364 +00:00 core ERROR [uc_appletv_driver] Error connecting to driver ws://127.0.0.1:8097: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:42:39.947747 +00:00 core NOTICE [UCD3-0C6E34] Reconnecting in: 1.097s
2025-10-28 17:42:39.945931 +00:00 core ERROR [UCD3-0C6E34] Error connecting to dock ws://ucd3-0c6e34.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:39.939683 +00:00 core NOTICE [UCD3-0BEB5C] Reconnecting in: 1.097s
2025-10-28 17:42:39.939357 +00:00 core ERROR [UCD3-0BEB5C] Error connecting to dock ws://ucd3-0beb5c.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:39.270142 +00:00 core ERROR [uc_appletv_driver] Error connecting to driver ws://127.0.0.1:8097: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:42:39.267717 +00:00 core ERROR Cannot connect to BT daemon: I/O error. Reconnecting in 1.287710788s
2025-10-28 17:42:39.260892 +00:00 core NOTICE Restarting BT daemon client, enabled=true
2025-10-28 17:42:39.086130 +00:00 core NOTICE [UCD3-0C6E34] Reconnecting in: 844ms
2025-10-28 17:42:39.085489 +00:00 core ERROR [UCD3-0C6E34] Error connecting to dock ws://ucd3-0c6e34.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:39.078635 +00:00 core NOTICE [UCD3-0BEB5C] Reconnecting in: 844ms
2025-10-28 17:42:39.078173 +00:00 core ERROR [UCD3-0BEB5C] Error connecting to dock ws://ucd3-0beb5c.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:38.614396 +00:00 core ERROR [uc_appletv_driver] Error connecting to driver ws://127.0.0.1:8097: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:42:38.418714 +00:00 core NOTICE [UCD3-0C6E34] Reconnecting in: 650ms
2025-10-28 17:42:38.418196 +00:00 core ERROR [UCD3-0C6E34] Error connecting to dock ws://ucd3-0c6e34.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:38.416436 +00:00 core NOTICE [UCD3-0BEB5C] Reconnecting in: 650ms
2025-10-28 17:42:38.415810 +00:00 core ERROR [UCD3-0BEB5C] Error connecting to dock ws://ucd3-0beb5c.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:38.357114 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start custom-intg@trinnov
2025-10-28 17:42:38.293394 +00:00 core ERROR Cannot connect to BT daemon: I/O error. Reconnecting in 964.807962ms
2025-10-28 17:42:38.292475 +00:00 core NOTICE Restarting BT daemon client, enabled=true
2025-10-28 17:42:38.183795 +00:00 core NOTICE Execute system command: StartCustomIntegration(ā€œtrinnovā€, Some(ā€œcustom-intg@trinnovā€))
2025-10-28 17:42:38.148211 +00:00 core NOTICE Not starting driver ā€˜uc_roon_driver’: no configured instances
2025-10-28 17:42:38.144971 +00:00 core NOTICE Not starting driver ā€˜uc_androidtv_driver’: no configured instances
2025-10-28 17:42:38.123701 +00:00 core NOTICE Not starting driver ā€˜uc_hue_driver’: no configured instances
2025-10-28 17:42:38.115765 +00:00 core ERROR [uc_appletv_driver] Error connecting to driver ws://127.0.0.1:8097: ServiceUnavailable(ā€œFailed to connect to host: Connection refused (os error 111)ā€)
2025-10-28 17:42:38.103600 +00:00 core NOTICE Not starting driver ā€˜uc_gc_driver’: no configured instances
2025-10-28 17:42:38.103315 +00:00 core NOTICE Not starting driver ā€˜uc_denon_driver’: no configured instances
2025-10-28 17:42:38.096349 +00:00 core NOTICE Not starting driver ā€˜uc_roku_driver’: no configured instances
2025-10-28 17:42:38.082312 +00:00 core NOTICE Not starting driver ā€˜uc_sonos_driver’: no configured instances
2025-10-28 17:42:38.081681 +00:00 core NOTICE [hass] Session became active: sending subscribe_events, get_driver_version, connect
2025-10-28 17:42:38.076841 +00:00 core NOTICE [hass] SessionAuthenticated msg
2025-10-28 17:42:38.076615 +00:00 core NOTICE [hass] Session state change: Authenticated
2025-10-28 17:42:38.076175 +00:00 core NOTICE [hass] SessionAuthenticated msg
2025-10-28 17:42:38.075856 +00:00 core NOTICE [hass] Session state change: Authenticated
2025-10-28 17:42:38.069769 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start wpa_supplicant
2025-10-28 17:42:38.063543 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/sbin/wl country DE
2025-10-28 17:42:38.063256 +00:00 core NOTICE [hass] Connected to: ws://127.0.0.1:8000/ws
2025-10-28 17:42:38.061826 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/bin/systemctl start btstack
2025-10-28 17:42:38.054984 +00:00 core NOTICE uccore : PWD=/opt/uc/data ; USER=root ; COMMAND=/usr/sbin/wl band a
2025-10-28 17:42:38.026685 +00:00 core NOTICE Not starting driver ā€˜uc_bo_driver’: no configured instances
2025-10-28 17:42:37.922258 +00:00 core ERROR Cannot connect to BT daemon: I/O error. Reconnecting in 371.377048ms
2025-10-28 17:42:37.910767 +00:00 core NOTICE Execute system command: StartBluetooth
2025-10-28 17:42:37.908669 +00:00 core NOTICE Updating BT service configuration file, connections=1
2025-10-28 17:42:37.908419 +00:00 core NOTICE [UCD3-0C6E34] Reconnecting in: 500ms
2025-10-28 17:42:37.907606 +00:00 core ERROR [UCD3-0C6E34] Error connecting to dock ws://ucd3-0c6e34.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:37.903222 +00:00 core NOTICE [UCD3-0BEB5C] Reconnecting in: 500ms
2025-10-28 17:42:37.898272 +00:00 core ERROR [UCD3-0BEB5C] Error connecting to dock ws://ucd3-0beb5c.local/ws: ServiceUnavailable(ā€œFailed to connect to host: Failed resolving hostname: failed to lookup address information: Temporary failure in name resolutionā€)
2025-10-28 17:42:37.866741 +00:00 core NOTICE Created Dock IR emitter: dock_id=UCD3-0BEB5C, name=ā€˜Dock-Kinoraum’, model=UCD3, active=true, port_mask=0
2025-10-28 17:42:37.866645 +00:00 core NOTICE [UCD3-0BEB5C] Resolved ws url: ws://UCD3-0BEB5C.local:80/ws
2025-10-28 17:42:37.866536 +00:00 core NOTICE Created Dock IR emitter: dock_id=UCD3-0C6E34, name=ā€˜Dock-Serverschrank’, model=UCD3, active=true, port_mask=0
2025-10-28 17:42:37.866321 +00:00 core NOTICE [UCD3-0C6E34] Resolved ws url: ws://UCD3-0C6E34.local:80/ws
2025-10-28 17:42:37.844782 +00:00 core NOTICE Execute system command: StartWifi
2025-10-28 17:42:37.844549 +00:00 core NOTICE Execute system command: EnableWoWLAN(true)
2025-10-28 17:42:37.844201 +00:00 core NOTICE Execute system command: SetWifiBand(A)
2025-10-28 17:42:37.835199 +00:00 core NOTICE Starting active WiFi scanning interval: 10s
2025-10-28 17:42:37.835014 +00:00 core NOTICE Feature flag enabled: routable_if_link. Using operational state ā€˜routable’ for WiFi connect events.
2025-10-28 17:42:37.829823 +00:00 core NOTICE Monitoring network link ā€˜wlan0’ for changes
2025-10-28 17:42:37.777109 +00:00 core NOTICE Setting rgb button backlight to: (251, 90, 9)
2025-10-28 17:42:37.776380 +00:00 core NOTICE Execute system command: SetWlCommand(ā€œcountryā€, ā€œDEā€)
2025-10-28 17:42:37.775311 +00:00 core NOTICE Enter normal mode: standby in 180s
2025-10-28 17:42:37.500479 +00:00 core NOTICE starting service: ā€œactix-web-service-127.0.0.1:9000ā€, workers: 1, listening on: 127.0.0.1:9000
2025-10-28 17:42:37.500221 +00:00 core NOTICE Actix runtime found; starting in Actix runtime
2025-10-28 17:42:37.424324 +00:00 core NOTICE Feature flag enabled: routable_if_link. Using operational state ā€˜routable’ for WiFi connect events.
2025-10-28 17:42:37.134828 +00:00 core NOTICE starting 1 workers
2025-10-28 17:42:36.675781 +00:00 core NOTICE Cleaning up downloaded system OTA updates <= 2.7.0
2025-10-28 17:42:36.657993 +00:00 core NOTICE Core-API listening on: 127.0.0.1:9000

this is the root cause: 2025-10-28 17:45:00.269902 +00:00 core WARN [uc-intg-govee] Failed to get integration session, not sending connect: BadRequest: Integration ID not found

this sometimes happen when the tar.gz download is getting corrupted, would you mind trying to download the tar.gz again, if unsure try different browser, delete the current one , reboot the remote and then re upload and re configure the new tar.gz . if still fail, download only the integration logs, not the core logs and share. if its easier, join the discord community to discuss there…

1 Like