Closed cryptton2004 closed 1 year ago
agners
commented
2 years ago [ 2.606952] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?Hm, that sounds like there is an issue with forwarding the USB device. It sounds like with Linux 5.15 something broke OS forwarding. I am not aware of any driver changes which could have caused that.
What Host OS do you use? Do you use the VirtualBox Extension Pack?
Can you attach the full host logs (dmesg) of 7.6 and 8.1?
ben0551
commented
2 years ago Confirmed Intel Wireless 9260 Bluetooth does not work on 8.0 and 8.1
Found this? https://bugzilla.kernel.org/show_bug.cgi?id=215167
ben0551
commented
2 years ago Windows 11, Extension Pack installed.
Puddingpanzer
commented
2 years ago Same Error for me with 8.0 and 8.1 at Synology Virtual Machine Manager
agners
commented
2 years ago @ben0551 @Puddingpanzer do your host logs show similar issues to the OT (usb usb1-port2: Cannot enable. Maybe the USB cable is bad?)?
cryptton2004
commented
2 years ago Sorry for the late reply!
Seems that the cable error no longer shows after full shutdown and startup, but there's still something:
Bluetooth: hci0: command 0xfc01 tx timeout
ben0551
commented
2 years ago @ben0551 @Puddingpanzer do your host logs show similar issues to the OT (
usb usb1-port2: Cannot enable. Maybe the USB cable is bad?)?
I get Bluetooth: hci0: command 0xfc01 tx timeout
cryptton2004
commented
2 years ago @agners Running Virtual Box (Version 6.1.34 r150636 (Qt5.6.2)) on W10 (OS Build 19044.1706) . No extensions. I edited the comment above.
cryptton2004
commented
2 years ago Hello,
Is there any plan of including the fix? (https://github.com/home-assistant/operating-system/issues/1935#issuecomment-1136689805)
fdsasdfddsa
commented
2 years ago Same issue of HAOS version 8.2 running VirtualBox (Version 6.1.34 r150636 (Qt5.6.2), with Extension Pack) on Win10 (19043.1766) PC with Intel AX1650i (201NGW). It puzzles me for a few days as a newbie of Home Assistant and a person not very familiar with VMs and Linux. I switch to HAOS 7.6 thanks for this post, and bluetooth function works fine on my PC now.
agners
commented
2 years ago Is there any plan of including the fix? (https://github.com/home-assistant/operating-system/issues/1935#issuecomment-1136689805)
That is not a fix, that is a bug report. There are potential fixes discussed and linked there. Some of them are already part of HAOS 8.1 (e.g. BTUSB_INTEL_BROKEN_SHUTDOWN_LED is set for 0x8087/0x0a2a), but they do not seem to fix the problem for you, unfortunately :(
Have you had a chance to try HAOS 8.2?
@fdsasdfddsa @ben0551 can you share the "Host" logs from Settings -> System -> Logs? So we can build a list of devices which seem to affected in our case.
cryptton2004
commented
2 years ago I am aware that the linked issue was a bug report, thank you. And indeed, I was referring to the fix you mentioned since it seemed to be included with a higher version of OS than the one I had displayed in the attached logs at the time of testing. From what I've read so far, it seems to be a driver issue with these Intel Bluetooth chipsets on particular OS versions.
Sorry, I'm not an actual power user for Linux so it's hard for me to tell what's a bait or a dead-end when searching for potential solutions, but it is in my best interest as a user to try to fix things myself (or suggest other threads where other people found ways to deal with it) if that would make my problem go away or help someone who knows how to deal with this kind of problems find a solution faster. If you'd rather deal with this by yourself, I could just step away from the thread as it's indeed a little bit above my knowledge. I could provide more logs and answer precise questions like:
Have you had a chance to try HAOS 8.2?
HAOS 8.2 has the same behavior as 8.1. The last known (Bluetooth) working version for me was 7.6.
fdsasdfddsa
commented
2 years ago Can you share the "Host" logs from Settings -> System -> Logs? So we can build a list of devices which seem to affected in our case.
@agners Host logs. For the last lines, I remove and mount the bluetooth back to the VM after its boot process finished.
mkanet
commented
2 years ago I am also started getting the below error after upgrading Home Assistant to Home Assistant 2022.7.5 (from an an old version from 6 months ago). I run Home Assistant in a VirtualBox VM on a Windows 10 host.
Home Assistant: 2022.7.5 Supervisor: 2022.07.0 Operating System: 8.2
22-07-20 09:12:08 WARNING (MainThread) [supervisor.host.network] Requested to update interface enp0s3 which does not exist or is disabled.
stalker1969
commented
2 years ago Has this problem been resolved? I also get an error (OS 8.2) 2022.7.5 Bluetooth in particular SkyKettle
mkanet
commented
2 years ago Has this problem been resolved? I also get an error (OS 8.2) 2022.7.5 Bluetooth in particular SkyKettle
I don't think so. Still seeing the same error message after upgrading to:
Home Assistant 2022.7.7 Supervisor 2022.07.0 Operating System 8.4
NOTE: I don't have a Bluetooth dongle installed on my Windows 10 PC (Host for Home Assistant VirtualBox VM). However, I started getting the same error as you recently. I have VirtualBox running in "Bridged Mode". Are you using Bridged Mode too or Host-Only mode?
I get the below error after each restart of Home Assistant Host:
22-07-26 16:14:01 WARNING (MainThread) [supervisor.host.network] Requested to update interface enp0s3 which does not exist or is disabled.
jask747
commented
2 years ago Have same issue running KVM on Linux host Intel i5 NUC. Host host detects BT device and available to forward to KVM but not detected by HassOS
Home Assistant 2022.7.6 Supervisor 2022.07.0 Operating System 8.2
agners
commented
2 years ago @mkanet
I am also started getting the below error after upgrading Home Assistant to Home Assistant 2022.7.5 (from an an old version from 6 months ago). I run Home Assistant in a VirtualBox VM on a Windows 10 host.
22-07-20 09:12:08 WARNING (MainThread) [supervisor.host.network] Requested to update interface enp0s3 which does not exist or is disabled.
This error is not related to Bluetooth, as it is about Ethernet interface. Also, the warning comes from the Supervisor. Besides the printed warning, are you having any issue with your system? If you have issues related to that warning open a issue with the Supervisor project: https://github.com/home-assistant/supervisor
@jask747
Did Bluetooth work for you before? Any helpful information in dmesg (Host logs in the frontend)? How do you forward the device exactly (I assume USB?)
jask747
commented
2 years ago @mkanet
I am also started getting the below error after upgrading Home Assistant to Home Assistant 2022.7.5 (from an an old version from 6 months ago). I run Home Assistant in a VirtualBox VM on a Windows 10 host. 22-07-20 09:12:08 WARNING (MainThread) [supervisor.host.network] Requested to update interface enp0s3 which does not exist or is disabled.
This error is not related to Bluetooth, as it is about Ethernet interface. Also, the warning comes from the Supervisor. Besides the printed warning, are you having any issue with your system? If you have issues related to that warning open a issue with the Supervisor project: https://github.com/home-assistant/supervisor
@jask747
Did Bluetooth work for you before? Any helpful information in dmesg (Host logs in the frontend)? How do you forward the device exactly (I assume USB?)
@agners
Hi
Onboard USB BT device = ID 8087:0a2a Intel Corp. Bluetooth wireless interface.
This is seen by KVM which you can then select to be available for guest OS.
Logs from HA Host logs as below (filtered on Bluetooth entries)
[ 0.478339] Bluetooth: Core ver 2.22 [ 0.478876] NET: Registered PF_BLUETOOTH protocol family [ 0.479216] Bluetooth: HCI device and connection manager initialized [ 0.480097] Bluetooth: HCI socket layer initialized [ 0.480217] Bluetooth: L2CAP socket layer initialized [ 0.480977] Bluetooth: SCO socket layer initialized [ 4.402356] Bluetooth: hci0: command 0x0c03 tx timeout [ 12.466244] Bluetooth: hci0: sending initial HCI reset failed (-110)
Regards
stalker1969
commented
2 years ago OS 8.4 problem not solved Virtual box bridge mode, Bluetooth LAN adapter TP-LINK UB400 USB 2.0
mcamou
commented
2 years ago I am having the same problem with KVM on a NUC. The host OS is Ubuntu 22.04, and can see the Bluetooth controller. I've exported the Bluetooth controller (USB ID 8087:0a2b) to the guest HAOS. bluetoothctl devices says No default controller available.
Here's the output of journalctl | grep -i blue in the guest OS:
Aug 29 14:27:03 homeassistant kernel: Bluetooth: Core ver 2.22
Aug 29 14:27:03 homeassistant kernel: NET: Registered PF_BLUETOOTH protocol family
Aug 29 14:27:03 homeassistant kernel: Bluetooth: HCI device and connection manager initialized
Aug 29 14:27:03 homeassistant kernel: Bluetooth: HCI socket layer initialized
Aug 29 14:27:03 homeassistant kernel: Bluetooth: L2CAP socket layer initialized
Aug 29 14:27:03 homeassistant kernel: Bluetooth: SCO socket layer initialized
Aug 29 14:27:04 homeassistant systemd[1]: Mounting Bluetooth persistent state...
Aug 29 14:27:04 homeassistant systemd[1]: Mounted Bluetooth persistent state.
Aug 29 14:27:04 homeassistant systemd[1]: Starting Bluetooth service...
Aug 29 14:27:04 homeassistant bluetoothd[309]: Bluetooth daemon 5.63
Aug 29 14:27:04 homeassistant systemd[1]: Started Bluetooth service.
Aug 29 14:27:04 homeassistant systemd[1]: Reached target Bluetooth Support.
Aug 29 14:27:04 homeassistant bluetoothd[309]: Starting SDP server
Aug 29 14:27:04 homeassistant bluetoothd[309]: profiles/network/bnep.c:bnep_init() kernel lacks bnep-protocol support
Aug 29 14:27:04 homeassistant bluetoothd[309]: src/plugin.c:plugin_init() System does not support network plugin
Aug 29 14:27:04 homeassistant bluetoothd[309]: Bluetooth management interface 1.21 initialized
Aug 29 14:27:04 homeassistant dbus-daemon[117]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.7' (uid=0 pid=309 comm="/usr/libexec/bluetooth/bluetoothd ")
Aug 29 14:27:05 hass kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Aug 29 14:27:05 hass kernel: Bluetooth: hci0: Reading Intel version command failed (-110)
Aug 29 14:27:44 hass ghcr.io/home-assistant/qemux86-64-homeassistant:2022.8.7/homeassistant[378]: 2022-08-29 16:27:44.285 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Bluetooth' for bluetooth integration not ready yet: Failed to start Bluetooth: adapter 'hci0' not found; Retrying in background
rubendediegomartinez
commented
2 years ago It was a pitty! :-( I'm runnig HA OS 8.4, 8.5 (switching in the boot from one to other) in VirtualBox over Windows 11. I'm using the last versions of the rest of components. Bluetooth doesn't run. I tried several adapter: 1rs- Hw computer integrated, Intel 2º One based in Realte BT 5.0 3rd. ASU BT500, one of the recommended.
My last error messages (in the guest console) are:
When is running there are continous messages, like these: (at least one per operation I suppose)
Almost all the issues described in this thread hapenned to me. ;-) It was a pitty, but in next days I will be impeled to use the EspHome BT Gw. Best regards
cryptton2004
commented
1 year ago It was a pitty! :-( I'm runnig HA OS 8.4, 8.5 (switching in the boot from one to other) in VirtualBox over Windows 11. I'm using the last versions of the rest of components. Bluetooth doesn't run. I tried several adapter: 1rs- Hw computer integrated, Intel 2º One based in Realte BT 5.0 3rd. ASU BT500, one of the recommended.
My last error messages (in the guest console) are: - Bluetooth: hci0: command 0xfc20 tx timeout - Bluetooth: hci0: RTL: download fw command failed (-110) and the bluetoth adapter is rejected.
When is running there are continous messages, like these: (at least one per operation I suppose) - Bluetooth: hci0: command 0x2042 tx timeout - Bluetooth: hci0: No gpio to reset Realtek device, ignoring - Bluetooth: hci0: unexxpected event for opcode 0x2042 - Bluetooth: hci0: failed to disable LE scan: stauts 0x1f
Almost all the issues described in this thread hapenned to me. ;-) It was a pitty, but in next days I will be impeled to use the EspHome BT Gw. Best regards
I also tried fixing this by throwing money at it and it did the trick for me. I purchased an ASUS USB-BT500, disabled the onboard Intel Wireless Bluetooth from Control Panel and restarted the PC. Windows 10 picked up the drivers right away, Home Assistant also displayed a new button "setup Bluetooth" (or something like this) on the integrations page and them Bluetooth devices started to show up. Sumup:
I still suspect the iwlwifi drivers are to blame.
github-actions[bot]
commented
1 year ago There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant OS version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
cryptton2004
commented
1 year ago /remove-lifecycle stale
ben0551
commented
1 year ago This is still an issue
michaelwingender
commented
1 year ago "To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates." Interesting strategy. Sound likes "These are not the droids you're looking for" ;-)
The issue is not fixed.
Describe the issue you are experiencing
While running Homeassistant OS 7.6 on VirtualBox, Bluetooth works (bluetoothctl shows the controller). After upgrading to 8.1, Bluetooth stops working: "No default controller available" Downgraded again, works, upgraded: stops working.
What operating system image do you use?
ova (for Virtual Machines)
What version of Home Assistant Operating System is installed?
8.1
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
bluetoothctl scan onThe cli returns the controller and relevant information"No default controller availableNote: none are displayedAnything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System Health information
Version | core-2022.5.5 -- | -- Installation Type | Home Assistant OS Development | false Supervisor | true Docker | true User | root Virtual Environment | false Python Version | 3.9.9 Operating System Family | Linux Operating System Version | 5.15.41 CPU Architecture | x86_64 Timezone | Europe/Bucharest Host Operating System | Home Assistant OS 8.1 -- | -- Update Channel | stable Supervisor Version | supervisor-2022.05.2 Docker Version | 20.10.14 Disk Total | 30.8 GB Disk Used | 3.3 GB Healthy | true Supported | true Board | ova Supervisor API | ok Version API | ok Installed Add-ons | File editor (5.3.3), Samba share (9.6.1), Terminal & SSH (9.4.0), Git pull (7.13.1), Google Assistant SDK (2.5.0) Dashboards | 2 -- | -- Resources | 0 Views | 1 Mode | storageAdditional information
Card: Gigabyte Intel Wireless-AC 9260 2x2 802.11AC Dual-Band WiFi+ Bluetooth
Other logs: