operating-system icon indicating copy to clipboard operation
operating-system copied to clipboard

Published 20 hours ago • verified publisher icon home-assistant

USB ports lost on Intel Nuc at random intervals

Open djansen1987 opened this issue 1 year ago • 18 comments
trafficstars

Describe the issue you are experiencing

My zigbee2mqqt was failing once in a while. Rebooting the system resolved it. Today it happened again so i started digging through the log files, there i found in de debug log of zigbee2mqtt that the USB Dongle was suddenly disconnected. Looking into the HA core logfiles i could see at that time not only my zigbee dongle became unavailable, but also my Bluetooth chip and DSMR P1 USB dongle.

If i go into the terminal and do a less /dev/tty… there is no USB device available.

I Also have a Intel Nuc, NUC5i3RYH with HA: Home Assistant 2024.1.3 Supervisor 2023.12.0 Operating System 11.4 Frontend 20240104.0

The USB dongle is also extended with a sort usb extend cable (20 cm)

If i go the all hardware under system i see a couple of usb ports listed as:


**usb1**
Subsystem:
usb
Device path:
/dev/bus/usb/001/001
Attributes:
BUSNUM: '001'
DEVNAME: /dev/bus/usb/001/001
DEVNUM: '001'
DEVPATH: /devices/pci0000:00/0000:00:1d.0/usb1
DEVTYPE: usb_device
DRIVER: usb
ID_BUS: usb
ID_FOR_SEAT: usb-pci-0000_00_1d_0
ID_MODEL: EHCI_Host_Controller
ID_MODEL_ENC: EHCI\x20Host\x20Controller
ID_MODEL_ID: '0002'
ID_PATH: pci-0000:00:1d.0
ID_PATH_TAG: pci-0000_00_1d_0
ID_REVISION: '0601'
ID_SERIAL: Linux_6.1.71-haos_ehci_hcd_EHCI_Host_Controller_0000:00:1d.0
ID_SERIAL_SHORT: 0000:00:1d.0
ID_USB_INTERFACES: ':090000:'
ID_USB_MODEL: EHCI_Host_Controller
ID_USB_MODEL_ENC: EHCI\x20Host\x20Controller
ID_USB_MODEL_ID: '0002'
ID_USB_REVISION: '0601'
ID_USB_SERIAL: Linux_6.1.71-haos_ehci_hcd_EHCI_Host_Controller_0000:00:1d.0
ID_USB_SERIAL_SHORT: 0000:00:1d.0
ID_USB_VENDOR: Linux_6.1.71-haos_ehci_hcd
ID_USB_VENDOR_ENC: Linux\x206.1.71-haos\x20ehci_hcd
ID_USB_VENDOR_ID: 1d6b
ID_VENDOR: Linux_6.1.71-haos_ehci_hcd
ID_VENDOR_ENC: Linux\x206.1.71-haos\x20ehci_hcd
ID_VENDOR_ID: 1d6b
MAJOR: '189'
MINOR: '0'
PRODUCT: 1d6b/2/601
SUBSYSTEM: usb
TAGS: ':seat:'
TYPE: 9/0/0
USEC_INITIALIZED: '1594405'

**usb2**
Subsystem:
usb
Device path:
/dev/bus/usb/002/001
Attributes:
BUSNUM: '002'
DEVNAME: /dev/bus/usb/002/001
DEVNUM: '001'
DEVPATH: /devices/pci0000:00/0000:00:14.0/usb2
DEVTYPE: usb_device
DRIVER: usb
ID_BUS: usb
ID_FOR_SEAT: usb-pci-0000_00_14_0
ID_MODEL: xHCI_Host_Controller
ID_MODEL_ENC: xHCI\x20Host\x20Controller
ID_MODEL_ID: '0002'
ID_PATH: pci-0000:00:14.0
ID_PATH_TAG: pci-0000_00_14_0
ID_REVISION: '0601'
ID_SERIAL: Linux_6.1.71-haos_xhci-hcd_xHCI_Host_Controller_0000:00:14.0
ID_SERIAL_SHORT: '0000:00:14.0'
ID_USB_INTERFACES: ':090000:'
ID_USB_MODEL: xHCI_Host_Controller
ID_USB_MODEL_ENC: xHCI\x20Host\x20Controller
ID_USB_MODEL_ID: '0002'
ID_USB_REVISION: '0601'
ID_USB_SERIAL: Linux_6.1.71-haos_xhci-hcd_xHCI_Host_Controller_0000:00:14.0
ID_USB_SERIAL_SHORT: '0000:00:14.0'
ID_USB_VENDOR: Linux_6.1.71-haos_xhci-hcd
ID_USB_VENDOR_ENC: Linux\x206.1.71-haos\x20xhci-hcd
ID_USB_VENDOR_ID: 1d6b
ID_VENDOR: Linux_6.1.71-haos_xhci-hcd
ID_VENDOR_ENC: Linux\x206.1.71-haos\x20xhci-hcd
ID_VENDOR_ID: 1d6b
MAJOR: '189'
MINOR: '128'
PRODUCT: 1d6b/2/601
SUBSYSTEM: usb
TAGS: ':seat:'
TYPE: 9/0/1
USEC_INITIALIZED: '1601101'

**ttyUSB0**
/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
Subsystem:
tty
Device path:
/dev/ttyUSB0
ID:
/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
Attributes:
DEVLINKS: >-
  /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
  /dev/serial/by-path/pci-0000:00:14.0-usb-0:4:1.0-port0
DEVNAME: /dev/ttyUSB0
DEVPATH: /devices/pci0000:00/0000:00:14.0/usb2/2-4/2-4:1.0/ttyUSB0/tty/ttyUSB0
ID_BUS: usb
ID_MODEL: USB_Serial
ID_MODEL_ENC: USB\x20Serial
ID_MODEL_ID: '7523'
ID_PATH: pci-0000:00:14.0-usb-0:4:1.0
ID_PATH_TAG: pci-0000_00_14_0-usb-0_4_1_0
ID_REVISION: '0264'
ID_SERIAL: 1a86_USB_Serial
ID_TYPE: generic
ID_USB_DRIVER: ch341
ID_USB_INTERFACES: ':ff0102:'
ID_USB_INTERFACE_NUM: '00'
ID_USB_MODEL: USB_Serial
ID_USB_MODEL_ENC: USB\x20Serial
ID_USB_MODEL_ID: '7523'
ID_USB_REVISION: '0264'
ID_USB_SERIAL: 1a86_USB_Serial
ID_USB_TYPE: generic
ID_USB_VENDOR: 1a86
ID_USB_VENDOR_ENC: 1a86
ID_USB_VENDOR_ID: 1a86
ID_VENDOR: 1a86
ID_VENDOR_ENC: 1a86
ID_VENDOR_ID: 1a86
MAJOR: '188'
MINOR: '0'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '2079542'

**ttyUSB1**
/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A174J5O9-if00-port0
Subsystem:
tty
Device path:
/dev/ttyUSB1
ID:
/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A174J5O9-if00-port0
Attributes:
DEVLINKS: >-
  /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A174J5O9-if00-port0
  /dev/serial/by-path/pci-0000:00:14.0-usb-0:3:1.0-port0
DEVNAME: /dev/ttyUSB1
DEVPATH: /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/ttyUSB1/tty/ttyUSB1
ID_BUS: usb
ID_MODEL: FT232R_USB_UART
ID_MODEL_ENC: FT232R\x20USB\x20UART
ID_MODEL_ID: '6001'
ID_PATH: pci-0000:00:14.0-usb-0:3:1.0
ID_PATH_TAG: pci-0000_00_14_0-usb-0_3_1_0
ID_REVISION: '0600'
ID_SERIAL: FTDI_FT232R_USB_UART_A174J5O9
ID_SERIAL_SHORT: A174J5O9
ID_TYPE: generic
ID_USB_DRIVER: ftdi_sio
ID_USB_INTERFACES: ':ffffff:'
ID_USB_INTERFACE_NUM: '00'
ID_USB_MODEL: FT232R_USB_UART
ID_USB_MODEL_ENC: FT232R\x20USB\x20UART
ID_USB_MODEL_ID: '6001'
ID_USB_REVISION: '0600'
ID_USB_SERIAL: FTDI_FT232R_USB_UART_A174J5O9
ID_USB_SERIAL_SHORT: A174J5O9
ID_USB_TYPE: generic
ID_USB_VENDOR: FTDI
ID_USB_VENDOR_ENC: FTDI
ID_USB_VENDOR_ID: '0403'
ID_VENDOR: FTDI
ID_VENDOR_ENC: FTDI
ID_VENDOR_ID: '0403'
MAJOR: '188'
MINOR: '1'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '2140064'

This is wat the core logfiles tell right before failing all usb ports:

2023-11-01 15:22:22.211 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'temperature' when rendering '{{value_json.temperature}}'
2023-11-01 15:22:23.233 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'temperature' when rendering '{{value_json.temperature}}'
2023-11-01 15:22:24.257 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'temperature' when rendering '{{value_json.temperature}}'
2023-11-01 15:22:25.277 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'temperature' when rendering '{{value_json.temperature}}'
2023-11-01 15:22:26.342 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'temperature' when rendering '{{value_json.temperature}}'
2023-11-01 15:47:31.498 ERROR (SyncWorker_9) [custom_components.dhl.sensor] API returned 401
2023-11-01 16:12:34.818 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [34:13:E8:24:BF:4D] due to timeout after 5 seconds
2023-11-01 16:12:48.572 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [34:13:E8:24:BF:4D]: [Errno 110] Operation timed out
2023-11-01 16:12:53.574 WARNING (MainThread) [bluetooth_auto_recovery.recover] Bluetooth adapter hci0 [34:13:E8:24:BF:4D] could not be reset:
2023-11-01 16:14:18.755 ERROR (MainThread) [dsmr_parser.clients.protocol] disconnected due to exception
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/serial_asyncio/__init__.py", line 115, in _read_ready
data = self._serial.read(self._max_read_size)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/serial/serialposix.py", line 595, in read
raise SerialException(
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2023-11-01 16:14:19.164 ERROR (MainThread) [bluetooth_auto_recovery.recover] Unexpected error while attempting USB reset of hci0: [Errno 19] No such device
zigbee2mqtt stopped 16:14:18


Zigbee2MQTT:debug 2023-11-01 16:14:08: Received MQTT message on 'homeassistant/climate/diyless_thermostat_dhw/config' with data '{"name":"DIYLESS DHW","unique_id":"diyless_thermostat_dhw","dev":{"ids":[ "00:00:00:00:00:02" ],"mdl":"DIYLESS Thermostat","sw":"1.7","mf":"DIYLESS"},"~":"diyless_thermostat","avty_t":"~/tele/LWT","pl_avail":"Online","pl_not_avail":"Offline","act_t":"~/stat/things/thermostat/properties","act_tpl":"{{value_json.DHWAction}}","mode_cmd_t":"~/cmnd/things/thermostat/properties/DHWMode","mode_stat_t":"~/stat/things/thermostat/properties","mode_stat_tpl":"{{value_json.DHWMode}}","temp_cmd_t":"~/cmnd/things/thermostat/properties/DHWSetpoint","temp_stat_t":"~/stat/things/thermostat/properties","temp_stat_tpl":"{{value_json.DHWSetpoint}}","curr_temp_t":"~/stat/things/thermostat/properties","curr_temp_tpl":"{{value_json.DHWTemperature}}","pl_on":true,"pl_off":false,"min_temp":"30","max_temp":"80","temp_step":"1","modes":["heat","off"]}'
Zigbee2MQTT:error 2023-11-01 16:14:18: Adapter disconnected, stopping
Zigbee2MQTT:debug 2023-11-01 16:14:18: Saving state to file /share/zigbee2mqtt/state.json
Zigbee2MQTT:info  2023-11-01 16:14:18: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'offline'
Zigbee2MQTT:info  2023-11-01 16:14:18: Disconnecting from MQTT server
Zigbee2MQTT:info  2023-11-01 16:14:18: Stopping zigbee-herdsman...
Zigbee2MQTT:error 2023-11-01 16:14:18: Failed to stop Zigbee2MQTT

This allmost looks like drivers failing or something, who can help?

Post on the community with other users with the same issue: https://community.home-assistant.io/t/usb-ports-lost/446289/9?u=djansen1987

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?

11.4

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

  1. Random interval USB Ports become unavailable
  2. Check ssh to check /dev/tty*** (none) (aditially tried to unplug and plug in the usb devices to diverent ports without luck)
  3. Reboot host -> all port become avalible

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

2023-11-01 15:22:22.211 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'temperature' when rendering '{{value_json.temperature}}'
2023-11-01 15:22:23.233 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'temperature' when rendering '{{value_json.temperature}}'
2023-11-01 15:22:24.257 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'temperature' when rendering '{{value_json.temperature}}'
2023-11-01 15:22:25.277 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'temperature' when rendering '{{value_json.temperature}}'
2023-11-01 15:22:26.342 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'temperature' when rendering '{{value_json.temperature}}'
2023-11-01 15:47:31.498 ERROR (SyncWorker_9) [custom_components.dhl.sensor] API returned 401
2023-11-01 16:12:34.818 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not reset the power state of the Bluetooth adapter hci0 [34:13:E8:24:BF:4D] due to timeout after 5 seconds
2023-11-01 16:12:48.572 WARNING (MainThread) [bluetooth_auto_recovery.recover] Could not cycle the Bluetooth adapter hci0 [34:13:E8:24:BF:4D]: [Errno 110] Operation timed out
2023-11-01 16:12:53.574 WARNING (MainThread) [bluetooth_auto_recovery.recover] Bluetooth adapter hci0 [34:13:E8:24:BF:4D] could not be reset:
2023-11-01 16:14:18.755 ERROR (MainThread) [dsmr_parser.clients.protocol] disconnected due to exception
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/serial_asyncio/__init__.py", line 115, in _read_ready
data = self._serial.read(self._max_read_size)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/serial/serialposix.py", line 595, in read
raise SerialException(
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2023-11-01 16:14:19.164 ERROR (MainThread) [bluetooth_auto_recovery.recover] Unexpected error while attempting USB reset of hci0: [Errno 19] No such device
zigbee2mqtt stopped 16:14:18


Zigbee2MQTT:debug 2023-11-01 16:14:08: Received MQTT message on 'homeassistant/climate/diyless_thermostat_dhw/config' with data '{"name":"DIYLESS DHW","unique_id":"diyless_thermostat_dhw","dev":{"ids":[ "00:00:00:00:00:02" ],"mdl":"DIYLESS Thermostat","sw":"1.7","mf":"DIYLESS"},"~":"diyless_thermostat","avty_t":"~/tele/LWT","pl_avail":"Online","pl_not_avail":"Offline","act_t":"~/stat/things/thermostat/properties","act_tpl":"{{value_json.DHWAction}}","mode_cmd_t":"~/cmnd/things/thermostat/properties/DHWMode","mode_stat_t":"~/stat/things/thermostat/properties","mode_stat_tpl":"{{value_json.DHWMode}}","temp_cmd_t":"~/cmnd/things/thermostat/properties/DHWSetpoint","temp_stat_t":"~/stat/things/thermostat/properties","temp_stat_tpl":"{{value_json.DHWSetpoint}}","curr_temp_t":"~/stat/things/thermostat/properties","curr_temp_tpl":"{{value_json.DHWTemperature}}","pl_on":true,"pl_off":false,"min_temp":"30","max_temp":"80","temp_step":"1","modes":["heat","off"]}'
Zigbee2MQTT:error 2023-11-01 16:14:18: Adapter disconnected, stopping
Zigbee2MQTT:debug 2023-11-01 16:14:18: Saving state to file /share/zigbee2mqtt/state.json
Zigbee2MQTT:info  2023-11-01 16:14:18: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'offline'
Zigbee2MQTT:info  2023-11-01 16:14:18: Disconnecting from MQTT server
Zigbee2MQTT:info  2023-11-01 16:14:18: Stopping zigbee-herdsman...
Zigbee2MQTT:error 2023-11-01 16:14:18: Failed to stop Zigbee2MQTT



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

```txt
Jan 15 09:22:32 homeassistant kernel: audit: type=1300 audit(1705310552.288:242): arch=c000003e syscall=321 success=yes exit=15 a0=5 a1=c000131be0 a2=78 a3=0 items=0 ppid=4255 pid=4264 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
Jan 15 09:22:46 homeassistant systemd[1]: var-lib-docker-overlay2-1507281147c6c4e8867d872898d0044d916b0ca7713382e6bab710ecd60008a5\x2dinit-merged.mount: Deactivated successfully.
Jan 15 09:22:46 homeassistant systemd[1]: mnt-data-docker-overlay2-1507281147c6c4e8867d872898d0044d916b0ca7713382e6bab710ecd60008a5\x2dinit-merged.mount: Deactivated successfully.
Jan 15 09:22:46 homeassistant systemd[1]: Started libcontainer container 8f506e81224a89ed3d88fe732cd6fa36dfb1d29f0a802d5b7c0367fb49145303.
Jan 15 09:22:46 homeassistant kernel: kauditd_printk_skb: 1 callbacks suppressed
Jan 15 09:22:46 homeassistant kernel: audit: type=1334 audit(1705310566.734:243): prog-id=69 op=LOAD
Jan 15 09:22:46 homeassistant kernel: audit: type=1334 audit(1705310566.735:244): prog-id=70 op=LOAD
Jan 15 09:22:46 homeassistant kernel: audit: type=1300 audit(1705310566.735:244): arch=c000003e syscall=321 success=yes exit=16 a0=5 a1=c00018d988 a2=78 a3=0 items=0 ppid=5026 pid=5037 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
Jan 15 09:22:46 homeassistant kernel: audit: type=1327 audit(1705310566.735:244): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F38663530366538313232346138396564336438386665373332
Jan 15 09:22:46 homeassistant kernel: audit: type=1334 audit(1705310566.735:245): prog-id=71 op=LOAD
Jan 15 09:22:46 homeassistant kernel: audit: type=1300 audit(1705310566.735:245): arch=c000003e syscall=321 success=yes exit=18 a0=5 a1=c00018d720 a2=78 a3=0 items=0 ppid=5026 pid=5037 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
Jan 15 09:22:46 homeassistant kernel: audit: type=1327 audit(1705310566.735:245): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F38663530366538313232346138396564336438386665373332
Jan 15 09:22:46 homeassistant kernel: audit: type=1334 audit(1705310566.735:246): prog-id=71 op=UNLOAD
Jan 15 09:22:46 homeassistant kernel: audit: type=1334 audit(1705310566.735:247): prog-id=70 op=UNLOAD
Jan 15 09:22:46 homeassistant kernel: audit: type=1334 audit(1705310566.735:248): prog-id=72 op=LOAD
Jan 15 09:23:18 homeassistant systemd[1]: var-lib-docker-overlay2-c320d1b31de8067ebe01d69b814033d43f1cff7828093c3b0c6885484b6db61e\x2dinit-merged.mount: Deactivated successfully.
Jan 15 09:23:18 homeassistant systemd[1]: mnt-data-docker-overlay2-c320d1b31de8067ebe01d69b814033d43f1cff7828093c3b0c6885484b6db61e\x2dinit-merged.mount: Deactivated successfully.
Jan 15 09:23:18 homeassistant kernel: hassio: port 7(veth0b6ed9e) entered blocking state
Jan 15 09:23:18 homeassistant kernel: hassio: port 7(veth0b6ed9e) entered disabled state
Jan 15 09:23:18 homeassistant kernel: device veth0b6ed9e entered promiscuous mode
Jan 15 09:23:18 homeassistant kernel: kauditd_printk_skb: 2 callbacks suppressed
Jan 15 09:23:18 homeassistant kernel: audit: type=1700 audit(1705310598.977:249): dev=veth0b6ed9e prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
Jan 15 09:23:18 homeassistant kernel: audit: type=1300 audit(1705310598.977:249): arch=c000003e syscall=44 success=yes exit=40 a0=c a1=c0015082a0 a2=28 a3=0 items=0 ppid=1 pid=486 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" subj=unconfined key=(null)
Jan 15 09:23:18 homeassistant NetworkManager[400]: <info>  [1705310598.9803] manager: (veth355de26): new Veth device (/org/freedesktop/NetworkManager/Devices/21)
Jan 15 09:23:18 homeassistant kernel: audit: type=1327 audit(1705310598.977:249): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D636F6E7461696E6572643D2F72756E2F636F6E7461696E6572642F636F6E7461696E6572642E736F636B
Jan 15 09:23:18 homeassistant NetworkManager[400]: <info>  [1705310598.9849] manager: (veth0b6ed9e): new Veth device (/org/freedesktop/NetworkManager/Devices/22)
Jan 15 09:23:19 homeassistant kernel: audit: type=1325 audit(1705310599.001:250): table=nat:84 family=2 entries=1 op=nft_register_rule pid=5224 subj=unconfined comm="iptables"
Jan 15 09:23:19 homeassistant kernel: audit: type=1300 audit(1705310599.001:250): arch=c000003e syscall=46 success=yes exit=508 a0=3 a1=7ffd8560a1d0 a2=0 a3=7ffd8560a1bc items=0 ppid=486 pid=5224 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-nft-multi" subj=unconfined key=(null)
Jan 15 09:23:19 homeassistant kernel: audit: type=1327 audit(1705310599.001:250): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D4100444F434B4552002D7000746370002D6400302F30002D2D64706F72740031363237002D6A00444E4154002D2D746F2D64657374696E6174696F6E003137322E33302E33332E313A313632370000002D690068617373696F
Jan 15 09:23:19 homeassistant kernel: audit: type=1325 audit(1705310599.010:251): table=filter:85 family=2 entries=1 op=nft_register_rule pid=5228 subj=unconfined comm="iptables"
Jan 15 09:23:19 homeassistant kernel: audit: type=1300 audit(1705310599.010:251): arch=c000003e syscall=46 success=yes exit=648 a0=3 a1=7fffe344a5c0 a2=0 a3=7fffe344a5ac items=0 ppid=486 pid=5228 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-nft-multi" subj=unconfined key=(null)
Jan 15 09:23:19 homeassistant kernel: audit: type=1327 audit(1705310599.010:251): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D740066696C746572002D4100444F434B45520000002D690068617373696F002D6F0068617373696F002D7000746370002D64003137322E33302E33332E31002D2D64706F72740031363237002D6A00414343455054
Jan 15 09:23:19 homeassistant kernel: audit: type=1325 audit(1705310599.015:252): table=nat:86 family=2 entries=1 op=nft_register_rule pid=5230 subj=unconfined comm="iptables"
Jan 15 09:23:19 homeassistant systemd[1]: Started libcontainer container 77376f4ad73e5042a5e7fa168c2e2afec375aed8943005561b36b2effb5b43f2.
Jan 15 09:23:19 homeassistant kernel: eth0: renamed from veth355de26
Jan 15 09:23:19 homeassistant kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0b6ed9e: link becomes ready
Jan 15 09:23:19 homeassistant kernel: hassio: port 7(veth0b6ed9e) entered blocking state
Jan 15 09:23:19 homeassistant kernel: hassio: port 7(veth0b6ed9e) entered forwarding state
Jan 15 09:23:19 homeassistant NetworkManager[400]: <info>  [1705310599.2439] device (veth0b6ed9e): carrier: link connected
Jan 15 09:23:19 homeassistant systemd[1]: Started libcontainer container 3edac1d828fc5dd86d9a5f10918d08e2359dd953cf2263e3cfde7960b29177e2.
Jan 15 09:23:19 homeassistant kernel: hassio: port 8(vethce3844a) entered blocking state
Jan 15 09:23:19 homeassistant kernel: hassio: port 8(vethce3844a) entered disabled state
Jan 15 09:23:19 homeassistant kernel: device vethce3844a entered promiscuous mode
Jan 15 09:23:19 homeassistant kernel: hassio: port 8(vethce3844a) entered blocking state
Jan 15 09:23:19 homeassistant kernel: hassio: port 8(vethce3844a) entered forwarding state
Jan 15 09:23:19 homeassistant NetworkManager[400]: <info>  [1705310599.7336] manager: (veth367d9d6): new Veth device (/org/freedesktop/NetworkManager/Devices/23)
Jan 15 09:23:19 homeassistant NetworkManager[400]: <info>  [1705310599.7419] manager: (vethce3844a): new Veth device (/org/freedesktop/NetworkManager/Devices/24)
Jan 15 09:23:19 homeassistant systemd[1]: Started libcontainer container 9fa691a5c0f052bed984d0f7ad914404b97fa9f19073852ce409d6a66323ceb8.
Jan 15 09:23:19 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-77376f4ad73e5042a5e7fa168c2e2afec375aed8943005561b36b2effb5b43f2-runc.YICmO9.mount: Deactivated successfully.
Jan 15 09:23:19 homeassistant kernel: hassio: port 8(vethce3844a) entered disabled state
Jan 15 09:23:20 homeassistant kernel: eth0: renamed from veth367d9d6
Jan 15 09:23:20 homeassistant kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethce3844a: link becomes ready
Jan 15 09:23:20 homeassistant kernel: hassio: port 8(vethce3844a) entered blocking state
Jan 15 09:23:20 homeassistant kernel: hassio: port 8(vethce3844a) entered forwarding state
Jan 15 09:23:20 homeassistant NetworkManager[400]: <info>  [1705310600.1743] device (vethce3844a): carrier: link connected
Jan 15 09:23:20 homeassistant systemd[1]: var-lib-docker-overlay2-0f20a07eb46ea2b2fe713cbdc1ffef91c4c774a9ec5ce876c770ebab14027a4d\x2dinit-merged.mount: Deactivated successfully.
Jan 15 09:23:20 homeassistant systemd[1]: mnt-data-docker-overlay2-0f20a07eb46ea2b2fe713cbdc1ffef91c4c774a9ec5ce876c770ebab14027a4d\x2dinit-merged.mount: Deactivated successfully.
Jan 15 09:23:20 homeassistant NetworkManager[400]: <info>  [1705310600.4631] manager: (vethddab1dd): new Veth device (/org/freedesktop/NetworkManager/Devices/25)
Jan 15 09:23:20 homeassistant NetworkManager[400]: <info>  [1705310600.4676] manager: (veth28de15e): new Veth device (/org/freedesktop/NetworkManager/Devices/26)
Jan 15 09:23:20 homeassistant kernel: hassio: port 9(veth28de15e) entered blocking state
Jan 15 09:23:20 homeassistant kernel: hassio: port 9(veth28de15e) entered disabled state
Jan 15 09:23:20 homeassistant kernel: device veth28de15e entered promiscuous mode
Jan 15 09:23:20 homeassistant kernel: hassio: port 9(veth28de15e) entered blocking state
Jan 15 09:23:20 homeassistant kernel: hassio: port 9(veth28de15e) entered forwarding state
Jan 15 09:23:20 homeassistant systemd[1]: Started libcontainer container 128b5a6c8131ce44695d52fc02604795193e94eee9bc15ee83354b29478a520f.
Jan 15 09:23:20 homeassistant kernel: eth0: renamed from vethddab1dd
Jan 15 09:23:21 homeassistant kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth28de15e: link becomes ready
Jan 15 09:23:21 homeassistant NetworkManager[400]: <info>  [1705310601.0055] device (veth28de15e): carrier: link connected
Jan 15 09:23:26 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-128b5a6c8131ce44695d52fc02604795193e94eee9bc15ee83354b29478a520f-runc.9g0fz3.mount: Deactivated successfully.
Jan 15 09:23:35 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-2413245af44a10267fe2f4ed23a836a3151126dca7e3b84ce55ccded2fea9a96-runc.4emfk4.mount: Deactivated successfully.
Jan 15 09:23:36 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-128b5a6c8131ce44695d52fc02604795193e94eee9bc15ee83354b29478a520f-runc.kd60jk.mount: Deactivated successfully.
Jan 15 09:24:11 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-128b5a6c8131ce44695d52fc02604795193e94eee9bc15ee83354b29478a520f-runc.UYphFO.mount: Deactivated successfully.
Jan 15 09:24:19 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-3edac1d828fc5dd86d9a5f10918d08e2359dd953cf2263e3cfde7960b29177e2-runc.34PfgK.mount: Deactivated successfully.
Jan 15 09:24:22 homeassistant kernel: kauditd_printk_skb: 146 callbacks suppressed
Jan 15 09:24:22 homeassistant kernel: audit: type=1334 audit(1705310662.126:309): prog-id=89 op=LOAD
Jan 15 09:24:22 homeassistant kernel: audit: type=1334 audit(1705310662.126:310): prog-id=90 op=LOAD
Jan 15 09:24:22 homeassistant kernel: audit: type=1334 audit(1705310662.126:311): prog-id=91 op=LOAD
Jan 15 09:24:22 homeassistant systemd[1]: Starting Hostname Service...
Jan 15 09:24:22 homeassistant systemd[1]: Started Hostname Service.
Jan 15 09:24:22 homeassistant kernel: audit: type=1334 audit(1705310662.531:312): prog-id=92 op=LOAD
Jan 15 09:24:22 homeassistant kernel: audit: type=1334 audit(1705310662.531:313): prog-id=93 op=LOAD
Jan 15 09:24:22 homeassistant kernel: audit: type=1334 audit(1705310662.531:314): prog-id=94 op=LOAD
Jan 15 09:24:22 homeassistant systemd[1]: Starting Time & Date Service...
Jan 15 09:24:22 homeassistant systemd[1]: Started Time & Date Service.
Jan 15 09:24:52 homeassistant systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Jan 15 09:24:52 homeassistant kernel: audit: type=1334 audit(1705310692.586:315): prog-id=91 op=UNLOAD
Jan 15 09:24:52 homeassistant kernel: audit: type=1334 audit(1705310692.586:316): prog-id=90 op=UNLOAD
Jan 15 09:24:52 homeassistant kernel: audit: type=1334 audit(1705310692.586:317): prog-id=89 op=UNLOAD
Jan 15 09:24:52 homeassistant systemd[1]: systemd-timedated.service: Deactivated successfully.
Jan 15 09:24:52 homeassistant kernel: audit: type=1334 audit(1705310692.867:318): prog-id=94 op=UNLOAD
Jan 15 09:24:52 homeassistant kernel: audit: type=1334 audit(1705310692.867:319): prog-id=93 op=UNLOAD
Jan 15 09:24:52 homeassistant kernel: audit: type=1334 audit(1705310692.867:320): prog-id=92 op=UNLOAD
Jan 15 09:35:30 homeassistant kernel: audit: type=1334 audit(1705311330.812:321): prog-id=95 op=LOAD
Jan 15 09:35:30 homeassistant systemd-timesyncd[472]: Network configuration changed, trying to establish connection.
Jan 15 09:35:30 homeassistant systemd-timesyncd[472]: Contacted time server 162.159.200.123:123 (time.cloudflare.com).
Jan 15 09:35:30 homeassistant systemd[1]: Started Journal Gateway Service.
Jan 15 09:35:31 homeassistant systemd-journal-gatewayd[10721]: microhttpd: MHD_OPTION_EXTERNAL_LOGGER is not the first option specified for the daemon. Some messages may be printed by the standard MHD logger.
Jan 15 09:36:36 homeassistant systemd[1]: Starting Cleanup of Temporary Directories...
Jan 15 09:36:36 homeassistant systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Jan 15 09:36:36 homeassistant systemd[1]: Finished Cleanup of Temporary Directories.
Jan 15 09:36:36 homeassistant systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.

System information

System Information

version core-2024.1.3
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.11.6
os_name Linux
os_version 6.1.71-haos
arch x86_64
timezone Europe/Amsterdam
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 4924
Installed Version 1.33.0
Stage running
Available Repositories 1377
Downloaded Repositories 11
Home Assistant Cloud
logged_in true
subscription_expiration August 7, 2024 at 2:00 AM
relayer_connected true
relayer_region eu-central-1
remote_enabled true
remote_connected true
alexa_enabled false
google_enabled true
remote_server eu-central-1-3.ui.nabu.casa
certificate_status ready
instance_id a00d7c3253584417bca037041fbc4817
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 11.4
update_channel stable
supervisor_version supervisor-2023.12.0
agent_version 1.6.0
docker_version 24.0.7
disk_total 458.4 GB
disk_used 88.9 GB
healthy true
supported true
board generic-x86-64
supervisor_api ok
version_api ok
installed_addons Samba share (12.2.0), Home Assistant Google Drive Backup (0.112.1), Node-RED (17.0.2), Mosquitto broker (6.4.0), motionEye (0.20.0), Terminal & SSH (9.8.1), ESPHome (2023.12.5), AirCast (4.1.1), emby (4.7.11), Zigbee2MQTT (1.35.1-1), Advanced SSH & Web Terminal (17.0.3), Matter Server (5.0.2), AirSonos (4.1.1), FTP (5.0.1), Nextcloud (28.0.1-6), Music Assistant BETA (2.0.0b82)
Dashboards
dashboards 2
resources 6
views 31
mode storage
Recorder
oldest_recorder_run January 5, 2024 at 5:38 PM
current_recorder_run January 15, 2024 at 10:22 AM
estimated_db_size 2373.16 MiB
database_engine sqlite
database_version 3.41.2
Spotify
api_endpoint_reachable ok

Additional information

No response

djansen1987 avatar Jan 15 '24 09:01 djansen1987

There are several similar reports with USB devices going missing in this issue tracker, e.g. #2995.

Did this start with recently? E.g. can you try to downgrade to 11.1 using ha os update --version 11.1?

agners avatar Jan 15 '24 11:01 agners

Hi @agners, thanks for you quick reply. Unfortunally when i created my post 2 months back i was running version 11.1 and it might even already been in an OS version before that. Strange part is it could be running days, sometimes weeks without an issue. But sometimes also twice a day. Nothing noteworthy happening that can relate the events for me. I will maintain looking in the logs when it occurse again, but this makes the wife very unhappy...

djansen1987 avatar Jan 16 '24 07:01 djansen1987

@djansen1987 you can also go further back then 11.1, e.g. 10.5. You are certain that the same hardware combination used to work reliably at one point?

From the host logs you've provided (which include the kernel logs) it seems they are cut-off or really doesn't have any issue reported (no log entries from January 16th).

It does sound like it is OS related indeed since the device doesn't come back even after unplugging/replugging, but I'd expect kernel errors in this case.

Can you double check the kernel logs using ha host logs --identifier kernel -n 10000? Especially for that timeframe the Core and Z2M reported issues?

agners avatar Jan 16 '24 08:01 agners

I am sure the config has worked correct at some point. Let me know after viewing the logs if you still want me to revert to the old os version (what might i experience when reverting ?)

It seems like the host log time is 1 hour off (earlier) with the zigbee2mqtt log. So start looking in the host.log at: Jan 15 08:51:12 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout

host.log

Zigbee2mqtt.txt

djansen1987 avatar Jan 16 '24 09:01 djansen1987

I am having the same issue as you with a Dell Wyse 5070 running 11.4

First the bluetooth times out then it cascades to my USB ports timing out (I have a zwave controller, a zigbee controller, and a coral tpu connected via usb).

Somapolice avatar Jan 16 '24 18:01 Somapolice

Same problem here for last 6 months. Hardware is Intel NUC 5i5RYK. I have tried several Linux kernel, Ubuntu and Home Assistant versions but the problem persists. I have a Zwave and zigbee USB sticks connected. I guess it is either a problem with the USB hub (Bluetooth is internally connected to the USB HUB) or a power supply issue. I am using a generic 65W PSU. Note: I am using HA docker not HAOS

khayamgondal avatar Jan 17 '24 01:01 khayamgondal

Hi @agners, did you find anything in the logs ? It occurred multiple times in the meanwhile. If need i can collect more logs

djansen1987 avatar Jan 25 '24 10:01 djansen1987

The logs show various USB related issues, e.g. this:

Jan 15 08:53:06 homeassistant kernel: usb 2-7: reset full-speed USB device number 5 using xhci_hcd
Jan 15 08:53:21 homeassistant kernel: usb 2-7: device descriptor read/64, error -110
Jan 15 08:53:37 homeassistant kernel: usb 2-7: device descriptor read/64, error -110
Jan 15 08:53:37 homeassistant kernel: usb 2-7: reset full-speed USB device number 5 using xhci_hcd
Jan 15 08:53:53 homeassistant kernel: usb 2-7: device descriptor read/64, error -110
Jan 15 08:54:09 homeassistant kernel: usb 2-7: device descriptor read/64, error -110
Jan 15 08:54:09 homeassistant kernel: usb 2-7: reset full-speed USB device number 5 using xhci_hcd
Jan 15 08:54:14 homeassistant kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
Jan 15 08:54:20 homeassistant kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
Jan 15 08:54:20 homeassistant kernel: usb 2-7: device not accepting address 5, error -62
Jan 15 08:54:20 homeassistant kernel: usb 2-7: reset full-speed USB device number 5 using xhci_hcd
Jan 15 08:54:31 homeassistant kernel: xhci_hcd 0000:00:14.0: Abort failed to stop command ring: -110
Jan 15 08:54:31 homeassistant kernel: xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
Jan 15 08:54:31 homeassistant kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up
Jan 15 08:54:31 homeassistant kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
Jan 15 08:54:31 homeassistant kernel: usb 2-1: USB disconnect, device number 2
Jan 15 08:54:31 homeassistant kernel: usb 2-1: failed to send control message: -19
Jan 15 08:54:31 homeassistant kernel: ch341-uart ttyUSB1: ch341-uart converter now disconnected from ttyUSB1
Jan 15 08:54:31 homeassistant kernel: ch341 2-1:1.0: device disconnected
Jan 15 08:54:31 homeassistant kernel: usb 2-3: USB disconnect, device number 3
Jan 15 08:54:31 homeassistant kernel: ftdi_sio ttyUSB0: error from flowcontrol urb
Jan 15 08:54:31 homeassistant kernel: ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Jan 15 08:54:31 homeassistant kernel: ftdi_sio 2-3:1.0: device disconnected
Jan 15 08:54:31 homeassistant kernel: usb 2-4: USB disconnect, device number 4
Jan 15 08:54:31 homeassistant kernel: usb 2-7: USB disconnect, device number 0

This is most likely a Linux kernel issue. Given that USB seems to work rather reliable for must users, it seems to be some interaction with newer stable kernel releases and your particular system.

We are soon going to update to Linux 6.6, initial development version on the dev channel will soon follow once https://github.com/home-assistant/operating-system/pull/3063 is merged. Maybe this new major release helps? :thinking: :crossed_fingers:

agners avatar Feb 02 '24 10:02 agners

Okay, goed to hear it is still moving forward. Will wait for the new kernal update to be production ready

djansen1987 avatar Feb 02 '24 14:02 djansen1987

@djansen1987 what Zigbee dongle are you using?

henriklund avatar Feb 25 '24 19:02 henriklund

@djansen1987 OS version 12 with the updated kernel is in the stable channel, please let us know if it fixed your issues.

sairon avatar Feb 26 '24 15:02 sairon

@henriklund i have a "zzh! CC2652R Multiprotocol RF Stick" with the latest firmware. I do have to say i has been a while for it to break. What i also noticed but it might be a coincidence. That when it happend the stick was in a continues "permit join" state as i forgot to turn it of a couple of time. Did not yet had the time to see if i could reproduce.

PS: Maybe unrelated but, last night my homeassistant web interface was not responding so was the app. I was able to run turn off/on devices via google voice assistant -> nabu casa. When i went to the console screen on my NUC i saw the following:

image (ignore the ```````` on the command line as that was me pluggin in a keyboard)

djansen1987 avatar Feb 27 '24 13:02 djansen1987

My observations are somewhat similar and then again... running with a ConBee II and Aeotec ZWave Stick for a few years. Until recently I (also) ran Home Assistant from a NUC. Although all devices worked like a charm after a reboot, I would frequently (within days or 1-2 weeks) experience the USB sticks getting disconnected. On a few occassions they reconnected, but the predominant experience was that they remained disconnected. This was a bit of a nuisance for which I had to create a few automations to monitor the state and implement responses (restart integration or even reboot the host). Two months ago I decided to run HA virtualized (on Proxmox) as means to better utilize the NUC capacity. All hardware remained the same. I noted an improved handling of the hardware (less frequent disconnects of USB), Only problem now was that the Zigbee network (through ConBee II) started becoming unstable (I saw errors in the logs that indicated some capacity constrain / device fault). I opted for replacing with ConBee III (less hassle on migration) and behold, no more USB disconnects. To say I was pleased is an understatement.

That is until I started rebooting the NUC. Now the ZWave chimes in with a connect, only to disconnect 20sec later: image

Ejecting and reinserting the USB (from Proxmox by removing / adding the device) works without problems and afterwards everything is stable. image

(this was also the case before the latest update).

henriklund avatar Feb 28 '24 08:02 henriklund

@henriklund So do I understand it correctly that with bare-metal install, you had more disconnects, and with ConBee III in a VM, it does not happen anymore?

About the first log capture, if you don't filter for USB, is there anything around that USB disconnect event that would justify it?

sairon avatar Feb 28 '24 09:02 sairon

@sairon you are correct. My infrastructure seems far better off now (running virtualized and with ConBee III) than two months ago when it ran bare-metal. As soon as all is up and running everything appears stable; nothing in logs, no sudden lights failing to turn on / off. The only hiccup left if the odd disconnect of the ZWave USB during boot. And even here I yesterday saw the odd case (when trying it out) where everything started up and worked; it happened once during 5 tries.

This is what I see relates to discovering USBs: image Then a lot of logging related to apparmour, docker, network, CIFS before this: image

henriklund avatar Feb 28 '24 09:02 henriklund

@sairon, I do not know if my error qualifies as a new issue (I do not want to hijack this one). If so, please let me know.

However, I had a strange observation today. I was trying to experiment with some simple monitoring of my ZWave. While doing so I restarted ZWave JS UI (to simulate loss of ZWave). What intrigued me was that the first restart went fine while the second caused the USB to become disconnected. Time between restarts did not seem to influence the outcome (whether it was 2 minutes or 5); the USB was no longer visible in /dev/serial/by-id/ and last entry in dmesg was a USB disconnect. A quick remove and add in Proxmox (ie. a virtual inject insert) and USB was back.

henriklund avatar Mar 08 '24 18:03 henriklund

Worth mentioning; this appears to a consistent behaviour. Second restart makes the USB disconnect.

henriklund avatar Mar 08 '24 19:03 henriklund

@henriklund Problems with the ZWave sticks are tracked in #2995, and there is a fix/workaround in 12.1.rc1. Let's keep this issue only for problems not related to ZWave sticks, and continue in discussion in the other one if the ZWave problems persist for you after upgrading to 12.1.rc1.

sairon avatar Mar 11 '24 09:03 sairon

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.

github-actions[bot] avatar Jun 10 '24 05:06 github-actions[bot]

Seeing the same issue with a 5th gen i5 nuc

acvigue avatar Jul 22 '24 21:07 acvigue

@acvigue, this issue is closed. I think it would be better to raise a new request to track. I decided to do something in an attempt to ‘fix’ this since I ran HA inside a ProxMox on my NUC. So far it has not reoccurred since. The rough outline was that I:

  • installed an Alpine LXC
  • Installed ZwaveJS on Alpine
  • Made a complete copy of ZWaveJS configuration from HA docker to Alpine
  • Changed USB pass through to Alpine
  • Stopped HA ZwaveJS and pointed ZWave to Alpine
  • started ZwaveJS on Alpine and checked everything was OK (ie. all devices found) This is not for the faint hearted, however, so far everything behaves perfectly and no more drops of the Zwave stick

henriklund avatar Jul 23 '24 05:07 henriklund

Although this is an old topic, it seems that i have the same combination. Conbee II, Aeontec Zwave. After enabling Bluetooth integration, it occasionally disconnects USBs.

Martinvdm avatar Aug 25 '24 10:08 Martinvdm