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 am using a Gigabyte NUC (model GB-BXi7H-4500) with a mini PCIe Atheros AR5B22 card that includes Wi-Fi and Bluetooth 4.0. While the Wi-Fi functionality works perfectly, Bluetooth is not functioning.
When I check the Bluetooth integration in the Home Assistant OS (HAOS) web interface, it shows the message:
• No unconfigured Bluetooth adapters found. There are 0 ignored adapters.
When I run the lsusb command, the VID and PID are detected, showing the following output:
• VID: 04ca
• PID: 3007
However, when interacting with Bluetooth using the bluetoothctl command, I receive the error:
• Error: Unable to open mgmt_socket.
I have confirmed that the Bluetooth device is working, as it functioned correctly when I had Windows installed on the system just a few days ago. It is also detected and functional when booting a Live USB with Ubuntu.
The exact model of the Wi-Fi + Bluetooth card is Atheros AR5B22.
At some point when trying to activate Bluetooth, I did see “Lite-On” (full brand name: Lite-On Technology Corp.) as the Bluetooth device name, which indicates that the Bluetooth adapter was detected. Therefore, I suspect that Bluetooth support might have broken after a recent update
What version of Home Assistant Operating System is installed?
6.6.66-haos
Did the problem occur after upgrading the Operating System?
No
Hardware details
Hardware details:
• Device model: Gigabyte NUC
• Model: GB-BXi7H-4500
• Processor: Intel Core i7-4500U
• RAM: 12GB
• Storage: SSD 240GB
• Graphics: Integrated Intel HD Graphics 4400
• Wi-Fi + Bluetooth card: Atheros AR5B22 (Mini PCIe)
• Bluetooth version: Bluetooth 4.0
• Wi-Fi: Working correctly (Wi-Fi functionality works fine)
• Bluetooth: Not functioning correctly in Home Assistant OS
• USB devices:
• No additional USB devices attached.
• Operating System: Home Assistant OS
• Version: (please provide the specific version you’re using)
Steps to reproduce the issue
...
Anything in the Supervisor logs that might be useful for us?
2025-01-01 01:26:48.447 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running
2025-01-01 01:26:48.447 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system
2025-01-01 01:26:48.448 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system
2025-01-01 01:26:48.448 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon
2025-01-01 01:26:48.715 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system
2025-01-01 01:26:48.715 INFO (MainThread) [supervisor.resolution.checks.base] Run check for no_current_backup/system
2025-01-01 01:26:48.716 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system
2025-01-01 01:26:48.716 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server
2025-01-01 01:26:48.717 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor
2025-01-01 01:26:48.727 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disabled_data_disk/system
2025-01-01 01:26:48.728 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core
2025-01-01 01:26:48.728 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server
2025-01-01 01:26:48.729 INFO (MainThread) [supervisor.resolution.check] System checks complete
2025-01-01 01:26:48.729 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running
2025-01-01 01:26:48.937 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
2025-01-01 01:26:48.938 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running
2025-01-01 01:26:48.938 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
Anything in the Host logs that might be useful for us?
Describe the issue you are experiencing
I am using a Gigabyte NUC (model GB-BXi7H-4500) with a mini PCIe Atheros AR5B22 card that includes Wi-Fi and Bluetooth 4.0. While the Wi-Fi functionality works perfectly, Bluetooth is not functioning.
When I check the Bluetooth integration in the Home Assistant OS (HAOS) web interface, it shows the message:
• No unconfigured Bluetooth adapters found. There are 0 ignored adapters.
When I run the lsusb command, the VID and PID are detected, showing the following output:
• VID: 04ca
• PID: 3007
However, when interacting with Bluetooth using the bluetoothctl command, I receive the error:
• Error: Unable to open mgmt_socket.
I have confirmed that the Bluetooth device is working, as it functioned correctly when I had Windows installed on the system just a few days ago. It is also detected and functional when booting a Live USB with Ubuntu.
The exact model of the Wi-Fi + Bluetooth card is Atheros AR5B22.
At some point when trying to activate Bluetooth, I did see “Lite-On” (full brand name: Lite-On Technology Corp.) as the Bluetooth device name, which indicates that the Bluetooth adapter was detected. Therefore, I suspect that Bluetooth support might have broken after a recent update
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.66-haos
Did the problem occur after upgrading the Operating System?
No
Hardware details
Hardware details:
• Device model: Gigabyte NUC
• Model: GB-BXi7H-4500
• Processor: Intel Core i7-4500U
• RAM: 12GB
• Storage: SSD 240GB
• Graphics: Integrated Intel HD Graphics 4400
• Wi-Fi + Bluetooth card: Atheros AR5B22 (Mini PCIe)
• Bluetooth version: Bluetooth 4.0
• Wi-Fi: Working correctly (Wi-Fi functionality works fine)
• Bluetooth: Not functioning correctly in Home Assistant OS
• USB devices:
• No additional USB devices attached.
• Operating System: Home Assistant OS
• Version: (please provide the specific version you’re using)
Steps to reproduce the issue
...
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Additional information
No response
The text was updated successfully, but these errors were encountered: