You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Beelink MINI-S12 Pro Mini PC with Alder Lake-N (N95/N100) 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?
Is there a way to disable attempting to load this driver until it works? I have hot-plugged an USB-Bluetooth adapter (made by Asus) and it worked fine until the latest upgrade of the HomeAssistant OS, when now both Bluetooth adapters fail to initialize.
I also have a Beelink MINI-S12 Pro Mini PC as @davulkoy does, and my HAOS setup is in a VM in Proxmox 8.
I'm getting a similar error when trying to initialize BT. It is discovered as hci0 and added, but fails to initialize with a constant loop in the console reading: Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0040-1050.sfi (-2)
Is there any to resolve this?
I've read that some people have success renaming or linking older bluetooth driver files to 0040-1050, but I'm not sure where to find those or how to try that in HA.
Realtek RTL8761BU adapters
These adapters do not have a reset pin. If they stop responding, there is currently no way for the kernel to reset them automatically. A generic USB reset for these adapters has been introduced in Linux kernel 6.1 and later.
That adapter is not recommended and not on the high performance list.
Realtek RTL8761BU adapters
These adapters do not have a reset pin. If they stop responding, there is currently no way for the kernel to reset them automatically. A generic USB reset for these adapters has been introduced in Linux kernel 6.1 and later.
Working well here but good to know. Thanks @bdraco.
@bdraco Just curious. Is it not possible adds support for this adapter (AX101)? Is it possible that it will be supported in the future? What does it depend on? Thanks!
great idea ! - I just finished adding a new VM (Lubuntu) to my ProMox host (first one after HA) - so Ill try that - thanks
EDIT: - done above
Same error (failed to load intel firmware file ....)
I installed HA using the tteck script - I wonder if its overwriting something at boot up - when I add "/mnt/boot/firmware/" to "/sys/module/firmware_class/parameters/path" it gets zero'd out after the reboot)
hmm - just trying to figure out whats different about my install ...
If you set the /sys/module stuff that should take effect immediately - no reboot necessary. To persist that setting across reboots you need to update /mnt/boot/cmdline.txt - like this:
Does anyone have suggestions on how I could track, or where the best place is to track, the eventual "fix" being pushed for a future Linux/HA update? Is there some changelog where I could see something to indicate I can try this again without the workaround? Just want to be aware of when I can try the first-class support for this Beelink S12 Pro MiniPC
I'm still holding out, I'd like to not have to purchase a separate Bluetooth USB if support for this is coming somewhat soon.
I'm in exactly the same boat; hoping for it to work out of the box with the S12 Pro, since it was billed as a great intro miniPC model to host ProxMox/HA.
What I'm trying to figure out is how to be in the know when something does get released...
After updating HA with the latest OS 11.5, the Bluetooth is working for me.
The same. But wifi doesnt work. I tried to install pached addon https://github.com/mattlongman/Hassio-Access-Point with driver changed to iwlwifi ... but it doesnt see device/interface wlan0. And such driver is exist in the system.
So I found a workaround to the Bluetooth limitation. I got a bunch of ESP32 boards and made them BT repeaters. Now my Mini PC (with Bluetooth disabled) is still talking to all the Switchbot BT devices
Activity
home-assistant commentedon Aug 16, 2023
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
bluetoothcan trigger bot actions by commenting:@home-assistant closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign bluetoothRemoves the current integration label and assignees on the issue, add the integration domain after the command.(message by CodeOwnersMention)
bluetooth documentation
bluetooth source
(message by IssueLinks)
[-]Minipc wifi en bluetooth issue[/-][+]AX101 WiFi 6 & Bluetooth 5.2 module issue[/+]0x8000-0000 commentedon Aug 22, 2023
Is there a way to disable attempting to load this driver until it works? I have hot-plugged an USB-Bluetooth adapter (made by Asus) and it worked fine until the latest upgrade of the HomeAssistant OS, when now both Bluetooth adapters fail to initialize.
ha-elguano commentedon Aug 31, 2023
I also have a Beelink MINI-S12 Pro Mini PC as @davulkoy does, and my HAOS setup is in a VM in Proxmox 8.
I'm getting a similar error when trying to initialize BT. It is discovered as hci0 and added, but fails to initialize with a constant loop in the console reading:
Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0040-1050.sfi (-2)Is there any to resolve this?
I've read that some people have success renaming or linking older bluetooth driver files to 0040-1050, but I'm not sure where to find those or how to try that in HA.
kmanan commentedon Sep 5, 2023
JesusNietoGarcia commentedon Sep 6, 2023
Gadeo commentedon Sep 7, 2023
davulkoy commentedon Sep 7, 2023
@bdraco is it possible to have a short feedback from you? Thanks!
bdraco commentedon Sep 7, 2023
That adapter isn't supported. Pick one from https://www.home-assistant.io/integrations/bluetooth/#known-working-high-performance-adapters instead or better yet, use an ESPHome proxy.
Also see #92379
Gadeo commentedon Sep 7, 2023
I picked up months ago this one https://www.amazon.es/actualizaci%C3%B3n-Adaptador-ZEXMTE-Auriculares-transmisor/dp/B09MZ8715D and works fantastic with a very good range.
bdraco commentedon Sep 7, 2023
That adapter is not recommended and not on the high performance list.
https://www.home-assistant.io/integrations/bluetooth/#realtek-rtl8761bu-adapters
Gadeo commentedon Sep 7, 2023
Working well here but good to know. Thanks @bdraco.
davulkoy commentedon Sep 8, 2023
@bdraco Just curious. Is it not possible adds support for this adapter (AX101)? Is it possible that it will be supported in the future? What does it depend on? Thanks!
40 remaining items
julian4646 commentedon Jan 12, 2024
great idea ! - I just finished adding a new VM (Lubuntu) to my ProMox host (first one after HA) - so Ill try that - thanks
EDIT: - done above
Same error (failed to load intel firmware file ....)
I installed HA using the tteck script - I wonder if its overwriting something at boot up - when I add "/mnt/boot/firmware/" to "/sys/module/firmware_class/parameters/path" it gets zero'd out after the reboot)
hmm - just trying to figure out whats different about my install ...
dndlion commentedon Jan 12, 2024
If you set the /sys/module stuff that should take effect immediately - no reboot necessary. To persist that setting across reboots you need to update /mnt/boot/cmdline.txt - like this:
echo "firmware_class.path=/mnt/boot/firmware/ console=ttyS0 console=tty1" > /mnt/boot/cmdline.txtjulian4646 commentedon Jan 12, 2024
Thanks - I bailed on this (for now) - got it working with a "Avantree DG45" BT dongle in 5 mins (Ill revisit it later)
peter-sahajian commentedon Jan 13, 2024
Does anyone have suggestions on how I could track, or where the best place is to track, the eventual "fix" being pushed for a future Linux/HA update? Is there some changelog where I could see something to indicate I can try this again without the workaround? Just want to be aware of when I can try the first-class support for this Beelink S12 Pro MiniPC
denysdovhan commentedon Feb 1, 2024
I have AX201 Bluetooth adapter in my Beelink S12 Pro.
My drivers are also packed in
.zst. Workaround from this thread don't work for me. I still get the error message.jturmel commentedon Feb 1, 2024
I'm still holding out, I'd like to not have to purchase a separate Bluetooth USB if support for this is coming somewhat soon.
peter-sahajian commentedon Feb 2, 2024
I'm in exactly the same boat; hoping for it to work out of the box with the S12 Pro, since it was billed as a great intro miniPC model to host ProxMox/HA.
What I'm trying to figure out is how to be in the know when something does get released...
blowk commentedon Feb 6, 2024
After updating HA with the latest OS 11.5, the Bluetooth is working for me.
denysdovhan commentedon Feb 6, 2024
Same for me. Works on Beelink S12 Pro with Proxmox after upgrading to HA OS 11.5.
magamos commentedon Feb 8, 2024
The same. But wifi doesnt work. I tried to install pached addon https://github.com/mattlongman/Hassio-Access-Point with driver changed to iwlwifi ... but it doesnt see device/interface wlan0. And such driver is exist in the system.
kmanan commentedon Feb 26, 2024
So I found a workaround to the Bluetooth limitation. I got a bunch of ESP32 boards and made them BT repeaters. Now my Mini PC (with Bluetooth disabled) is still talking to all the Switchbot BT devices
AtomRoman commentedon Feb 26, 2024
Here's what Intel itself says about this problem https://community.intel.com/t5/Wireless/AX101-Linux-driver/td-p/1465559
davulkoy commentedon Feb 26, 2024
Since the problem has been solved in latest HA version, i will close this issue.