HAOS installed on Beelink MiniS12, Bluetooth failing

Lcw731 · February 7, 2024, 8:19am

I recently installed HAOS on a Beelink Mini S12. Everything went well, with one exception. I keep getting an error that Bluetooth is failing to start/not found I have looked and I have found some threads about a kernel not yet supported, and referencing a work around on github. I have no idea how to even attempt to implement that. Would anyone be willing to guide me through how to fix this issue?

FriedCheese · February 11, 2024, 3:33pm

Honestly, getting into kernel manipulation is a bit much to bite off if you’re first getting started with *nix.

After some digging, it looks like this might be fixed now.

github.com/home-assistant/core

AX101 WiFi 6 & Bluetooth 5.2 module issue

opened 11:27AM - 16 Aug 23 UTC

davulkoy

integration: bluetooth

### The problem I have a Beelink MINI-S12 Pro Mini PC with Alder Lake-N (N95/N1…00) with the AX101 WiFi 6 & Bluetooth 5.2 module This is not working in Home Assistant yet. Home Assistant automatically recognized and added the integration: "Bluetooth", but its not working. The integration gives the error "hc10: Failed to start Bluetooth: adapter 'hci0' not found" and after that it tries to setup again without success (with text: "initializing"). So it keeps going on in a loop. Any ideas? I think this is a new device and maybe not yet supported by HA. Note: I have installed the full HAOS software (Generic x86-64). ### What version of Home Assistant Core has the issue? 2023.08.1 ### 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 _No response_ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

Cyberbeni · February 11, 2024, 3:53pm

I’ve also recently tried setting up a Bluetooth dongle but it had some issues, so I’ve decided to go for an ESPHome BLE proxy instead.

benzoid1 · February 11, 2024, 4:14pm

I also recently (a week ago) upgraded from a RPi4 to Beelink Mini S12, and it went smoothly for me. The internal bluetooth has been recognised and configured, although I’m not using it for anything at the moment.
One thing that I initially mistook for a bluetooth configuration problem was that when restoring the backup from the RPi4, the bluetooth configuration was for the BT MAC/ID found in the RPi4, which of course wasn’t present. I deleted that config and installed bluetooth again, with the wizard detecting the Mini S12’s bluetooth device without a problem. If you’ve restored a backup from a previous Home Assistant installation, this might be the problem.
I’ve been trying to find the model of the BT device in my Mini S12, but lsusb seems to only have very basic info.

mobile.andrew.jones · February 11, 2024, 4:36pm

The recommended advice from the developers from previous live release parties - is that the ESP Home Bluetooth Proxy is the way to go anyway, because native bluetooth has to pass through so many layers before Home Assistant gets hold of it, but with the ESP Home Bluetooth Proxy, the bluetooth data is direct to Home Assistant over the network.

Lcw731 · February 12, 2024, 12:59am

I did not upgrade from a rpi, and i had ordered a bluetooth dongle, but i had not thought about this. I deleted the bluetooth devices, restarted HAOS, and that was what finally got it going for me with the Beelink bluettooth.

FriedCheese · February 12, 2024, 5:00am

Not to mention that they’re about the cost of a Bluetooth dongle with the advantage of being able to stick them anywhere with WiFi coverage.