Disabling WiFi also disables Bluetooth since HAOS 11.2

[nanard69]

Describe the issue you are experiencing

I'have updated HA OS on my Raspberry Pi 4 from version 11.1 to 11.2 and i've lost bluetooth functionality. If i downgrade to 11.1, everthing works fine. I've discovered that happened because i have disactivated my wifi in the /mnt/boot/config.txt file.
In version 11.2 of HA OS, if i want the bluetooth, i need to activate wifi in the /mnt/boot/config.txt file. Is it possible to give the choice of activating or not the wifi, because i don't need it ?

What operating system image do you use?

rpi4-64 (Raspberry Pi 4/400 64-bit OS)

What version of Home Assistant Operating System is installed?

11.2

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

1. update HA OS to 11.2
2. desactivate wifi in the /mnt/boot/config.txt
3. reboot

the bluetooth will work no longer

Anything in the Supervisor logs that might be useful for us?

no

Anything in the Host logs that might be useful for us?

no

System information

No response

Additional information

No response

[vtb77]

Hello:

The same thing happens to me. I would appreciate it if it will be solved because I do not use WiFi because I have the Raspberry connected by a network cable.

Thank you.

Greetings.

[virtualj]

Similar issue for me. I use HAOS on intel minipc. Waiting for the fix.

[mikenhu]

Same issue for me. I'm on Home Assistant Yellow

[BTCanada]

Same issue for me. It looks like #2948 broke bluetooth for those of us with wifi disabled in config.txt. The condition that patch uses to disable bluetooth is ConditionPathExists=!/sys/bus/sdio/devices/mmc1:0001:1
However, it looks like if you disable wifi, that device is never created, which causes that patch to remove the hci_uart module though /usr/sbin/modprobe -r hci_uart.
If you manually reenable hci_uart by using /usr/sbin/modprobe hci_uart, then bluetooth immediately starts working again (and the device referenced above still doesn't exist). @agners, #2948 breaks bluetooth on devices where wifi is disabled; can #2944 get a different fix? Thanks!

[virtualj]

I confirm: I have also wi-fi disabled in config

[kimtoiva]

My bluetooth also stopped working after updating. I have wifi active. If I delete it and restart HA and install it again it will work a few hours

[markonsmith]

Bluetooth on Raspberry Pi 4 simply does not work regardless of the state of wifi. The problem has started after I upgraded OS from version 11.0 to 11.2 and Core from 2023.11.2 to 2023.12.3.

Restoring full 11.2 core backup did not work as well as downgrading OS to 11.0. I am getting the "failed setup" error message for bluetooth device.

I can delete device, restart RP4 and configure bluetooth again to make it work for 2-3 days after which the same problem reocurrs.

[Nexulo]

I have the same issues and switched yesterday from openhab to HA.

Unfortunately, it seems to pick out bluetooth somehow when I restart and it then suddenly recognizes a second bluetooth adapter, although there is only one.

I use Home Assistant on my raspberry pi 3b.

[bcutter]

Bluetooth on Raspberry Pi 4 simply does not work regardless of the state of wifi. The problem has started after I upgraded OS from version 11.0 to 11.2 and Core from 2023.11.2 to 2023.12.3.

Restoring full 11.2 core backup did not work as well as downgrading OS to 11.0. I am getting the "failed setup" error message for bluetooth device.

I can delete device, restart RP4 and configure bluetooth again to make it work for 2-3 days after which the same problem reocurrs.

Oh dear, that's bad news. I was hoping to finally update from HA OS 10.5 to latest "stable" 11.2 on my Pi 4. WiFi is not disabled (so enabled) so I initially thought "well I don't care about #2975, let's finally update!". But that sounds like a real update blocker to me. I need bluetooth e. g. for the Switchbot integration.

[agners]

The reported issue here is that deactivating WiFi using config.txt also affects Bluetooth. I am guessing this is related to the new kernel Bluetooth initialization which came in with the upgrade to the latest Raspberry Pi Linux kernel (#2904).

If you experience Bluetooth issues even with WiFi enabled (no config.txt change, e.g. as @markonsmith reports): Please do not hijack this thread, and open a new issue along with details of your system's configuration. Thanks!

@bcutter note that we have thousands of user using Raspberry Pi 4 with HAOS 11.2 and Bluetooth without problems. Don't get discouraged by one report 😅 You can downgrade the OS also relatively safely in case the update does not work out for you (using ha os update --version 10.5). Just in case, a full backup is always good advice.

[bcutter]

note that we have thousands of user using Raspberry Pi 4 with HAOS 11.2 and Bluetooth without problems

Thanks for pointing this out. Last general question (warning: off-topic) before this issue can re-focus on the core issue itself:

How do you know? Because of the analytics/statistics from https://analytics.home-assistant.io ? From that data I can

• neither map a specific board to a specific OS version
• nor see if those "are running without issues"

Therefore really interested in this. Would indeed encourage future update decisions, as my current (focusing on stability instead of cutting-edge features) update strategy is "wait at least 4 to 8 weeks, then check open GitHub issues with OS version and board type".

---

(small note: updated to 11.2, everything fine, Bluetooth working afaics, only ran into the breaking change "eth0 --> end0" which rendered few systemmonitor integration entities unavailable, should have read the release notes a third time)

[Nexulo]

As far as I know, this problem occurs when using a Raspberry Pi 3b. When I switched from Openhab to Home Assistant, I first tested this on a 3B model and I always had the problem with Bluetooth. Now that I have switched to Raspberry Pi 4B, I no longer have any problems.

I set up both devices in exactly the same way, but when I switched to the 4B model, I imported everything from the backup of the 3B model.

So I no longer have this problem thanks to the change.