`/run/dbus/system_bus_socket` doesn't get closed.

[Mariusthvdb]

The problem

continuing from

The sockets dump shows it's /run/dbus/system_bus_socket which apparently doesn't get closed. HA Core uses it mainly for Bluetooth but it's not clear if it's the source - it might be some custom integration as well. To get all the pieces together, when the issue is happening, could you enable debug logging in the Bluetooth integration for couple of minutes and then open a Core issue along with your setup details and new profiler sockets dump?

Originally posted by @sairon in home-assistant/operating-system#4166 (reply in thread)

What version of Home Assistant Core has the issue?

2026.1.0bx

What was the last working version of Home Assistant Core?

2025.11.x (no sure which patch release that was)

re-started December 22d (after an initial problem earlier on midway November, which was the reason to start logging this in the first place)

What type of installation are you running?

Home Assistant OS

Integration causing the issue

bluetooth

Link to integration documentation on our website

https://www.home-assistant.io/integrations/bluetooth/

Diagnostics information

System Information

version	core-2026.1.0b2
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
container_arch	amd64
user	root
virtualenv	false
python_version	3.13.11
os_name	Linux
os_version	6.12.51-haos
arch	x86_64
timezone	Europe/Amsterdam
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.5
Stage	running
Available Repositories	2503
Downloaded Repositories	52

Home Assistant Cloud

logged_in	true
subscription_expiration	31 augustus 2026 om 02:00
relayer_connected	true
relayer_region	eu-central-1
remote_enabled	false
remote_connected	false
alexa_enabled	false
google_enabled	true
cloud_ice_servers_enabled	true
remote_server	eu-central-1-5.ui.nabu.casa
certificate_status	ready
instance_id	f51092d0098f40faa50dfd391c4bf925
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 16.3
update_channel	beta
supervisor_version	supervisor-2025.12.3
agent_version	1.7.2
docker_version	28.3.3
disk_total	458.4 GB
disk_used	27.0 GB
nameservers	192.168.1.1
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	generic-x86-64
supervisor_api	ok
version_api	ok
installed_addons	Log Viewer (0.17.1), Samba share (12.5.4), Terminal & SSH (9.21.0), Mosquitto broker (6.5.2), Z-Wave JS (0.27.0), Studio Code Server (6.0.1), Get HACS (1.3.1), ESPHome Device Builder (2025.12.4), File editor (5.8.0), Network UPS Tools (0.17.0), Advanced SSH & Web Terminal (22.0.3), Matter Server (8.1.2), DbStats (0.5.12)

Dashboards

dashboards	14
resources	27
views	152
mode	yaml

Network Configuration

adapters	lo (disabled), enp2s0 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth9e3bac5 (disabled), veth015594c (disabled), veth24d015b (disabled), veth81c6137 (disabled), veth69a595c (disabled), veth2b35d5e (disabled), veth28b6d04 (disabled), veth03b1866 (disabled), veth96c8ed6 (disabled), veth07f6920 (disabled), veth7859701 (disabled)
ipv4_addresses	lo (127.0.0.1/8), enp2s0 (192.168.1.61/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth9e3bac5 (), veth015594c (), veth24d015b (), veth81c6137 (), veth69a595c (), veth2b35d5e (), veth28b6d04 (), veth03b1866 (), veth96c8ed6 (), veth07f6920 (), veth7859701 ()
ipv6_addresses	lo (::1/128), enp2s0 (fd6c:1c21:8800:f099:8655:fe7b:7b2a:6d79/64, fe80::696d:3be9:f0cd:407a/64), docker0 (fe80::40ba:94ff:fe64:8258/64), hassio (fe80::b0de:daff:fe76:5ea0/64), veth9e3bac5 (fe80::1012:6eff:fe63:b7dc/64), veth015594c (fe80::58af:deff:fecf:7496/64), veth24d015b (fe80::1cea:5aff:fe86:63c2/64), veth81c6137 (fe80::24a7:40ff:fef2:c013/64), veth69a595c (fe80::4837:e8ff:fe51:b58d/64), veth2b35d5e (fe80::5c72:acff:fe57:9590/64), veth28b6d04 (fe80::7057:87ff:fe00:68ff/64), veth03b1866 (fe80::64ee:55ff:fe25:e23a/64), veth96c8ed6 (fe80::68fb:f5ff:fec1:c5f6/64), veth07f6920 (fe80::b85f:61ff:fef3:54be/64), veth7859701 (fe80::789a:ccff:fe5c:ae2/64)
announce_addresses	192.168.1.61, fd6c:1c21:8800:f099:8655:fe7b:7b2a:6d79, fe80::696d:3be9:f0cd:407a

Recorder

oldest_recorder_run	20 december 2025 om 20:48
current_recorder_run	3 januari 2026 om 12:49
estimated_db_size	3526.25 MiB
database_engine	sqlite
database_version	3.49.2

Spotify

api_endpoint_reachable	ok

Example YAML snippet

Anything in the logs that might be useful for us?

Host log shows endless repeat of

2026-01-05 07:47:14.494 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 07:48:14.493 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 07:49:14.494 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 07:50:14.494 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 07:51:14.494 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 07:52:14.494 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 07:53:14.494 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 07:54:14.494 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 07:55:14.494 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 07:56:14.494 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 07:57:14.493 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 07:58:14.494 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 07:59:14.494 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 08:00:14.494 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)
2026-01-05 08:01:14.494 hassio bluetoothd[513]: Failed to disconnect device: Disconnected (0x0e)

sockets dump.txt

Additional information

[home-assistant]

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (bluetooth) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of bluetooth can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign bluetooth Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

The make and model of your Bluetooth adapter will significantly influence your Bluetooth experience and connection times. Be sure to include it in the report, and check if it's on the high-performance list.
If the adapter fails to set up after restarting Home Assistant or upgrading, it's likely a hardware or OS-level kernel issue. You can resolve most set-up problems by powering down and restarting the system. Rebooting the system is not sufficient without powering it down.
Please enable Bluetooth debug logging, let it run for 10-15 minutes, and make sure to capture whatever problem you're having in the debug log.
Finally, be sure to include diagnostics for the Bluetooth adapter.
_{^{(message by IssueContext)}}

---

bluetooth documentation
bluetooth source
_{^{(message by IssueLinks)}}

[Mariusthvdb]

Added the 2 main BT adapters, the one in the host (Mini_PC) running the system, and the one for the high-performance adaptor attached to the host via usb

config_entry-bluetooth-3b75472a9bf2a84ba3917df6ba2c56e0.json

config_entry-bluetooth-a1f9584751a8f3eb427d1149db604de7.json