Most recent OS & Core updates broke ASUS BT540 connection
Describe the issue you are experiencing
Asus BT540 worked OK.
Today's minor update if both OS & Core, broke connection.
On Sytem / Hardware / System hardware, all 7 USB lanes appear without physical hardware (the Realtek chip) connected to them.
See also info below:
System Information
| version | core-2026.9.3 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| container_arch | aarch64 |
| user | root |
| virtualenv | false |
| python_version | 3.14.6 |
| os_name | Linux |
| os_version | 6.18.52-haos |
| arch | aarch64 |
| timezone | Asia/Jerusalem |
| config_dir | /config |
| logged_in | false |
|---|---|
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
| 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 | 4123 |
| Downloaded Repositories | 2 |
| host_os | Home Assistant OS 18.3 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2026.09.2 |
| agent_version | 1.14.0 |
| docker_version | 29.7.2 |
| disk_total | 28.0 GB |
| disk_used | 4.7 GB |
| nameservers | fe80::2a3b:82ff:fe48:941, 192.168.2.1, fd01::1 |
| healthy | true |
| supported | true |
| host_connectivity | true |
| supervisor_connectivity | true |
| ntp_synchronized | true |
| virtualization | |
| board | green |
| disk_life_time | 0 % |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Terminal & SSH (10.5.0), Get HACS (1.3.1) |
| dashboards | 2 |
|---|---|
| resources | 1 |
| views | 0 |
| mode | storage |
| adapters | lo (disabled), end0 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth4b919ff (disabled), veth696b5f5 (disabled), vethcc59ede (disabled), vethc8cf31f (disabled), veth7f22ce2 (disabled), veth265adad (disabled), veth36e72b8 (disabled) |
|---|---|
| ipv4_addresses | lo (127.0.0.1/8), end0 (192.168.2.210/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth4b919ff (), veth696b5f5 (), vethcc59ede (), vethc8cf31f (), veth7f22ce2 (), veth265adad (), veth36e72b8 () |
| ipv6_addresses | lo (::1/128), end0 (fd01::4c85:36fc:81bd:5992/64, fe80::5d9e:5193:fb77:4089/64), hassio (fd0c:ac1e:2100::1/48, fe80::bc95:43ff:fea3:3091/64), docker0 (fd23:1e90:c0d8::1/64, fe80::c870:25ff:fe58:eaff/64), veth4b919ff (fe80::b44a:d2ff:fe6b:25eb/64), veth696b5f5 (fe80::7c1b:38ff:fe8c:1c4d/64), vethcc59ede (fe80::b403:22ff:fe78:7e74/64), vethc8cf31f (fe80::bc38:f8ff:fe76:fc64/64), veth7f22ce2 (fe80::70a1:6bff:fed2:261c/64), veth265adad (fe80::444d:c1ff:fed8:14aa/64), veth36e72b8 (fe80::6064:9ff:fe51:931d/64) |
| announce_addresses | 192.168.2.210, fd01::4c85:36fc:81bd:5992, fe80::5d9e:5193:fb77:4089 |
| oldest_recorder_run | September 13, 2026 at 7:29 AM |
|---|---|
| current_recorder_run | September 19, 2026 at 11:21 AM |
| estimated_db_size | 4.16 MiB |
| database_engine | sqlite |
| database_version | 3.53.2 |
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
6.18.52
Did the problem occur after upgrading the Operating System?
Yes
Hardware details
HAbgreen
System Information
| version | core-2026.9.3 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| container_arch | aarch64 |
| user | root |
| virtualenv | false |
| python_version | 3.14.6 |
| os_name | Linux |
| os_version | 6.18.52-haos |
| arch | aarch64 |
| timezone | Asia/Jerusalem |
| config_dir | /config |
| logged_in | false |
|---|---|
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
| 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 | 4123 |
| Downloaded Repositories | 2 |
| host_os | Home Assistant OS 18.3 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2026.09.2 |
| agent_version | 1.14.0 |
| docker_version | 29.7.2 |
| disk_total | 28.0 GB |
| disk_used | 4.7 GB |
| nameservers | fe80::2a3b:82ff:fe48:941, 192.168.2.1, fd01::1 |
| healthy | true |
| supported | true |
| host_connectivity | true |
| supervisor_connectivity | true |
| ntp_synchronized | true |
| virtualization | |
| board | green |
| disk_life_time | 0 % |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | Terminal & SSH (10.5.0), Get HACS (1.3.1) |
| dashboards | 2 |
|---|---|
| resources | 1 |
| views | 0 |
| mode | storage |
| adapters | lo (disabled), end0 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth4b919ff (disabled), veth696b5f5 (disabled), vethcc59ede (disabled), vethc8cf31f (disabled), veth7f22ce2 (disabled), veth265adad (disabled), veth36e72b8 (disabled) |
|---|---|
| ipv4_addresses | lo (127.0.0.1/8), end0 (192.168.2.210/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth4b919ff (), veth696b5f5 (), vethcc59ede (), vethc8cf31f (), veth7f22ce2 (), veth265adad (), veth36e72b8 () |
| ipv6_addresses | lo (::1/128), end0 (fd01::4c85:36fc:81bd:5992/64, fe80::5d9e:5193:fb77:4089/64), hassio (fd0c:ac1e:2100::1/48, fe80::bc95:43ff:fea3:3091/64), docker0 (fd23:1e90:c0d8::1/64, fe80::c870:25ff:fe58:eaff/64), veth4b919ff (fe80::b44a:d2ff:fe6b:25eb/64), veth696b5f5 (fe80::7c1b:38ff:fe8c:1c4d/64), vethcc59ede (fe80::b403:22ff:fe78:7e74/64), vethc8cf31f (fe80::bc38:f8ff:fe76:fc64/64), veth7f22ce2 (fe80::70a1:6bff:fed2:261c/64), veth265adad (fe80::444d:c1ff:fed8:14aa/64), veth36e72b8 (fe80::6064:9ff:fe51:931d/64) |
| announce_addresses | 192.168.2.210, fd01::4c85:36fc:81bd:5992, fe80::5d9e:5193:fb77:4089 |
| oldest_recorder_run | September 13, 2026 at 7:29 AM |
|---|---|
| current_recorder_run | September 19, 2026 at 11:21 AM |
| estimated_db_size | 4.16 MiB |
| database_engine | sqlite |
| database_version | 3.53.2 |
Steps to reproduce the issue
Use the previous os + core
Connect the dongle - bluetooth will allow integration and every bt item will be controlled over ble.
Update to current OS & Core.
Bluetooth will fail initialization / setup, after reboot.
From this point, reboots, deletion of bt from Devices & Services, reconnection of the dongle (even to the 2nd usb port), etc., will not revive BT; also, new integration would fail too, with "no unconfigured bluetooth device found".
The System / Gardware / System hardware picture - as above.
Anything in the Supervisor logs that might be useful for us?
See files attachedAnything in the Host logs that might be useful for us?
See files attachedSystem information
Already inserted, above
Additional information
No response
Source: home-assistant/operating-system