Missing driver/support for Bluetooth [Azurewave AW-XM548NF (?)]

[Draghmar]

Describe the issue you are experiencing

Hi. After upgrading my setup to x86 I noticed that the BT stopped working and both official integration and Passive BLE Monitor do not get any info. At the moment of adding BT integration there's also notification that there's a new device to add and that device is hci0 with MAC address of the Wi-Fi/BT device.

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.6.54-haos

Did the problem occur after upgrading the Operating System?

No

Hardware details

Main hardware is Radxa X4 8GB without eMMC. NVMe disk installed. There's a Zigbee dongle attached to USB2 port /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0.
Bluetooth adapter is integrated with Wi-Fi and it's probably Azurewave AW-XM548NF, or at least Radxa docs says that and this is probably specification of it.

Steps to reproduce the issue

1. Install HA on Radxa X4.
2. Add BT integration.
3. Try to find any BT device.

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

Nothing related to BT and nothing that I haven't seen before.

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

Many, many of:
2024-11-17 20:06:48.134 homeassistant kernel: Bluetooth: hci0: Failed to read codec capabilities (-22)

Not sure if that's related but it touches Wi-Fi so...
2024-11-17 18:44:17.621 homeassistant wpa_supplicant[452]: TDLS: Creating peer entry for xx:xx:xx:xx:xx
2024-11-17 18:44:17.628 homeassistant wpa_supplicant[452]: TDLS: Dialog Token in TPK M1 2
2024-11-17 18:44:17.641 homeassistant wpa_supplicant[452]: nl80211: kernel reports: key addition failed
2024-11-17 18:44:17.641 homeassistant wpa_supplicant[452]: TDLS: Failed to set TPK to the driver

System information

System Information

version	core-2024.11.2
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.12.4
os_name	Linux
os_version	6.6.54-haos
arch	x86_64
timezone	Europe/Warsaw
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.1
Stage	running
Available Repositories	1458
Downloaded Repositories	8

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 13.2
update_channel	stable
supervisor_version	supervisor-2024.11.2
agent_version	1.6.0
docker_version	27.2.0
disk_total	116.7 GB
disk_used	8.9 GB
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	generic-x86-64
supervisor_api	ok
version_api	ok
installed_addons	CEC Scanner (3.0), File editor (5.8.0), Terminal & SSH (9.15.0), Mosquitto broker (6.4.1), Let's Encrypt (5.2.3), etrv2mqtt (0.03), Piper (1.5.2), Whisper (2.2.0), Everything Presence Zone Configurator (1.1.0), Studio Code Server (5.17.3)

Dashboards

dashboards	2
resources	2
views	6
mode	storage

Recorder

oldest_recorder_run	15 June 2023 at 17:08
current_recorder_run	17 November 2024 at 21:05
estimated_db_size	18173.64 MiB
database_engine	mysql
database_version	11.6.2

Spotify

api_endpoint_reachable	ok

Additional information

No response

[Draghmar]

Update:
Some of the BT sensors I'm using are LYWSD03MMC with modded firmware. Because they are part of TRV temp monitoring, I started looking for some ways to "fix" them. I found that they can be converted to Zigbee but because mine were quite old, I first had to make update to new pvvx's firmware, with default settings. After that I noticed that HA's BTHome discovered device...the BT sensor I just updated. So it looks like the BT radio does work but there some issues with specific integrations/firmware/hardware?
I converted most sensors to Zigbee except one (coincidence as I didn't noticed BTHome), which was left with new BT firmware and intergrated with BTHome. Passive BLE Monitor is disabled for now. That error is still there. One of the sensors (LYWSDCGQ) still can't be found as it doesn't have custom firmware and HA can't see it.