Bluetooth active scanning failing on Yellow+CM5

[GregKet1]

The problem

I have a new HA-Yellow with CM5. Within 24 hours of power-on I receive a notification "Bluetooth adapter requires system power cycle". After power cycling the system the message comes back by the next day. Getting full-detail on the notification:

The Bluetooth adapter hci0 (2C:CF:67:FA:D8:17) (bcm43438-bt) is stuck in passive scanning mode despite requesting active scanning mode. Automatic recovery was attempted but failed. This is likely a kernel, firmware, or operating system issue, and the system requires a complete power cycle to recover the adapter.

In passive mode, the adapter can only receive advertisements but cannot request additional data from devices, which will affect device discovery and functionality.

Manual intervention required:

Shut down the system completely (not just a reboot)
Remove power (unplug or turn off at the switch)
Wait 10 seconds
Restore power and boot the system
If the issue persists after power cycling:

Check for kernel/firmware updates
The onboard Bluetooth adapter may have hardware issues

I don't know if it is related but the system is also VERY slow compared to my other Yellow+CM4. When logged into SSH there will frequently be a 15-30 second delay before getting responses to 'ls' or 'cd'. 'ps aux' shows no significant CPU or memory usage.

Installation method. Home Assistant OS
Core. 2025.11.3
Supervisor. 2025.11.4
Operating System. 16.3
Frontend. 20251105.1

System Information

version	core-2025.11.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
container_arch	aarch64
user	root
virtualenv	false
python_version	3.13.9
os_name	Linux
os_version	6.12.47-haos-raspi
arch	aarch64
timezone	America/Los_Angeles
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	2427
Downloaded Repositories	1

Home Assistant Cloud

logged_in	false
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	stable
supervisor_version	supervisor-2025.11.4
agent_version	1.7.2
docker_version	28.3.3
disk_total	468.7 GB
disk_used	10.7 GB
nameservers	10.0.250.1
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	yellow
supervisor_api	ok
version_api	ok
installed_addons	Matter Server (8.1.1), ESPHome Device Builder (2025.11.0), Advanced SSH & Web Terminal (22.0.1), File editor (5.8.0)

Dashboards

dashboards	3
resources	0
views	1
mode	storage

Network Configuration

adapters	lo (disabled), end0 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth7118313 (disabled), vethfa35825 (disabled), vethb4f92a0 (disabled), vethc86fcc6 (disabled), vethaedb7c7 (disabled), veth61819aa (disabled), vethcc4dd77 (disabled)
ipv4_addresses	lo (127.0.0.1/8), end0 (10.0.100.2/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth7118313 (), vethfa35825 (), vethb4f92a0 (), vethc86fcc6 (), vethaedb7c7 (), veth61819aa (), vethcc4dd77 ()
ipv6_addresses	lo (::1/128), end0 (fe80::7770:9c2d:d23:f8b1/64), docker0 (fe80::38b5:14ff:feb5:aff3/64), hassio (fe80::6cc6:a5ff:fed8:1ed6/64), veth7118313 (fe80::fccf:7cff:fee6:483e/64), vethfa35825 (fe80::3099:4dff:feff:9d99/64), vethb4f92a0 (fe80::e0cf:9cff:fef3:8297/64), vethc86fcc6 (fe80::6c32:28ff:fe7b:2d60/64), vethaedb7c7 (fe80::6455:4eff:fe3c:b22/64), veth61819aa (fe80::5418:d4ff:fea2:a13a/64), vethcc4dd77 (fe80::80d0:8cff:fe94:c160/64)
announce_addresses	10.0.100.2, fe80::7770:9c2d:d23:f8b1

Recorder

error	failed to load: timeout

What version of Home Assistant Core has the issue?

core-2025.11.03

What was the last working version of Home Assistant Core?

No response

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

home-assistant_bluetooth_2025-11-24T22-44-20.291Z.log

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[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)}}

[GregKet1]

Any further diagnostics you need from me?

[GregKet1]

Issue continues to exist in Core 2025.12.4

[kusmi]

I do have a raspi-4, but it has the same onboard bluetooth model (bcm43438-bt) and have the same problem. I do the reboot cycle (powering down und unplug power and powering up again), but problem re-appears for many month now...

[GregKet1]

2026.1.1 still has the problem.

[goetzc]

Same devices and same error once each week or so, but no slowness.

Home Assistant Yellow+CM5 and build-in bcm43438-bt.

A regular full system reboot (Reboot system option) usually fixes the issue. There's no need to power cycle the system with the removed power adapter, but it's still annoying to have to reboot all the containers.

[slikone27]

I just started getting these as well since a few updates ago. Hopefully they can fix this.

[GregKet1]

Core 26.4.3 still has the issue.

[tarmacalastair]

Yup, I also get this every couple of days now. It's been happening for over 3 months but seems to be getting more and more frequent.

I'm running on a Pi4 with 4GB memory and my HA specs are:

Installation method Home Assistant OS
Core 2026.5.1
Supervisor 2026.05.0
Operating System 17.3
Frontend 20260429.3

[MartinLichtblau]

Didn't update for a year and now my Docker HA causes bluetooth crashes too.
Pi5 internal bluetooth and external Realtek stick crash after 1-2 days.
For me that's a critical issue, since my heatpump depends on the various inkbird bluetooth sensors.