Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

HAOS randomly loses connection to Sonoff Zigbee 3.0 USB Dongle Plus #2869

Closed
robtpaton opened this issue Oct 26, 2023 · 11 comments
Closed

HAOS randomly loses connection to Sonoff Zigbee 3.0 USB Dongle Plus #2869

robtpaton opened this issue Oct 26, 2023 · 11 comments
Labels
board/generic-x86-64 Generic x86-64 Boards (like Intel NUC) bug

Comments

@robtpaton
Copy link

robtpaton commented Oct 26, 2023 •
edited
Loading

Describe the issue you are experiencing

I randomly lose connection to my Sonoff Zigbee 3.0 USB Dongle Plus and only a hardware reboot fixes the issue (until it happens again). The dongle has been upgraded to the latest firmware (CC1352P2_CC2652P_launchpad_coordinator_20230507).

When it happens, the dongle is not shown under Hardware.

The occurrences seem more frequent with HAOS 10.3 but happen with 10.2 as well.

I originally added to the issue raised here home-assistant/core#94992 (comment) but this seems like an OS issue rather than a Core issue.

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?

10.3

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

  1. Start Home Assistant
  2. Wait anywhere from 1 hour to 24 hours (seems to be no pattern as to exactly how long)
  3. Obverse that Home Assistant has lost connection to Sonoff Zigbee 3.0 USB Dongle Plus so no Zigbee commands can be sent or received
  4. Perform a hardware reboot to get the dongle working again
  5. Go to step 1

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

No

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

No

System information

System Information

version core-2023.10.5
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.11.5
os_name Linux
os_version 6.1.29
arch x86_64
timezone Europe/London
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 5000
Installed Version 1.32.1
Stage running
Available Repositories 1320
Downloaded Repositories 21
Home Assistant Supervisor
host_os Home Assistant OS 10.2
update_channel stable
supervisor_version supervisor-2023.10.1
agent_version 1.5.1
docker_version 23.0.6
disk_total 219.4 GB
disk_used 58.3 GB
healthy true
supported true
board generic-x86-64
supervisor_api ok
version_api ok
installed_addons Autossh (0.4.0), Mosquitto broker (6.3.1), Studio Code Server (5.13.0), Dnsmasq (1.6.0), Advanced SSH & Web Terminal (15.1.0), Apache2 Minimal (2.7.6), ESPHome (2023.10.3), go2rtc (1.8.1), Let's Encrypt (4.12.9), Whisper (1.0.0), Piper (1.4.0), Stock Check (1.0.0), openWakeWord (1.8.1), Assist Microphone (2.2.3)
Dashboards
dashboards 5
resources 9
views 24
mode storage
Recorder
oldest_recorder_run 16 October 2023 at 15:03
current_recorder_run 26 October 2023 at 21:01
estimated_db_size 240.15 MiB
database_engine sqlite
database_version 3.41.2

Additional information

No response
@robtpaton robtpaton added the bug label Oct 26, 2023
@rickgardner077

This comment was marked as off-topic.

Sign in to view
@agners agners added the board/generic-x86-64 Generic x86-64 Boards (like Intel NUC) label Oct 31, 2023
@agners
Copy link
Member

agners commented Oct 31, 2023

When it happens, the dongle is not shown under Hardware.

That sounds as if the device disappears from the USB bus completely.

Can you check the kernel logs after it happens next time using:

ha host logs -b 0 -n 10000 -t kernel > /config/last-boot.log

There should be at least a USB disconnect event there when it happened.

@rickgardner077 since your issue started with HAOS 11.1, is on a Raspberry Pi and leads to a complete unresponsive system this seems a different issue. Can you please open a new issue along with all information? Thank you.

@robtpaton
Copy link
Author

Hi @agners, the disconnect has happened again. I found this log in Home Assistant Core logs:

Logger: zigpy_znp.zigbee.application
Source: /usr/local/lib/python3.11/site-packages/zigpy_znp/zigbee/application.py:778
First occurred: 14:23:35 (962 occurrences)
Last logged: 15:43:51

Failed to reconnect
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/serial/serialposix.py", line 322, in open
    self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_fa23a7c87d29ec11ae146f7840c9ce8d-if00-port0'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/zigpy_znp/zigbee/application.py", line 772, in _reconnect
    await self.connect()
  File "/usr/local/lib/python3.11/site-packages/zigpy_znp/zigbee/application.py", line 115, in connect
    await znp.connect()
  File "/usr/local/lib/python3.11/site-packages/zigpy_znp/api.py", line 720, in connect
    self._uart = await uart.connect(self._config[conf.CONF_DEVICE], self)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/zigpy_znp/uart.py", line 170, in connect
    _, protocol = await zigpy.serial.create_serial_connection(
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/zigpy/serial.py", line 48, in create_serial_connection
    transport, protocol = await pyserial_asyncio.create_serial_connection(
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/serial_asyncio_fast/__init__.py", line 508, in create_serial_connection
    serial_instance = await loop.run_in_executor(None, callback)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/serial/__init__.py", line 90, in serial_for_url
    instance.open()
  File "/usr/local/lib/python3.11/site-packages/serial/serialposix.py", line 325, in open
    raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg))
serial.serialutil.SerialException: [Errno 2] could not open port /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_fa23a7c87d29ec11ae146f7840c9ce8d-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_fa23a7c87d29ec11ae146f7840c9ce8d-if00-port0'

and after running the command you provided, there are definitely disconnects at 14:23:

Nov 02 14:20:18 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:20:18 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:20:20 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:20:20 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:20:20 homeassistant kernel: Bluetooth: hci0: failed to restart LE scan: status -110
Nov 02 14:20:23 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:20:23 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:20:23 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:20:25 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:20:25 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:20:25 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:20:25 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:20:27 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:20:27 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:20:27 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:20:27 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:20:27 homeassistant kernel: Bluetooth: hci0: stop background scanning failed: -110
Nov 02 14:20:37 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:20:37 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:20:37 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:20:37 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:20:37 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:20:39 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:20:39 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:20:39 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:20:39 homeassistant kernel: Bluetooth: hci0: stop background scanning failed: -110
Nov 02 14:20:39 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:20:49 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:20:49 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:20:49 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:20:49 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:20:49 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:20:51 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:20:51 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:20:51 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:20:51 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:20:51 homeassistant kernel: Bluetooth: hci0: stop background scanning failed: -110
Nov 02 14:21:01 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:21:01 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:21:01 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:21:01 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:01 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:03 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:21:03 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:21:03 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:21:03 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:03 homeassistant kernel: Bluetooth: hci0: stop background scanning failed: -110
Nov 02 14:21:13 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:21:13 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:21:13 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:13 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:21:13 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:15 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:21:15 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:15 homeassistant kernel: Bluetooth: hci0: stop background scanning failed: -110
Nov 02 14:21:15 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:21:15 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:21:25 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:21:25 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:21:25 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:21:25 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:25 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:27 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:21:27 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:21:27 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:21:27 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:27 homeassistant kernel: Bluetooth: hci0: stop background scanning failed: -110
Nov 02 14:21:37 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:21:37 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:21:37 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:21:37 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:37 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:39 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:21:39 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:39 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:21:39 homeassistant kernel: Bluetooth: hci0: stop background scanning failed: -110
Nov 02 14:21:39 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:21:49 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:21:49 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:21:49 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:21:49 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:49 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:51 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:21:51 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:21:51 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:51 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:21:51 homeassistant kernel: Bluetooth: hci0: stop background scanning failed: -110
Nov 02 14:21:53 homeassistant kernel: Bluetooth: hci0: Opcode 0x200c failed: -110
Nov 02 14:21:53 homeassistant kernel: Bluetooth: hci0: Unable to disable scanning: -110
Nov 02 14:21:53 homeassistant kernel: Bluetooth: hci0: command 0x200c tx timeout
Nov 02 14:21:53 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:21:56 homeassistant kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Nov 02 14:21:56 homeassistant kernel: Bluetooth: hci0: No way to reset. Ignoring and continuing
Nov 02 14:22:04 homeassistant kernel: Bluetooth: hci0: HCI reset during shutdown failed
Nov 02 14:22:06 homeassistant kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110
Nov 02 14:22:09 homeassistant kernel: usb 2-7: reset full-speed USB device number 4 using xhci_hcd
Nov 02 14:22:25 homeassistant kernel: usb 2-7: device descriptor read/64, error -110
Nov 02 14:22:41 homeassistant kernel: usb 2-7: device descriptor read/64, error -110
Nov 02 14:22:41 homeassistant kernel: usb 2-7: reset full-speed USB device number 4 using xhci_hcd
Nov 02 14:22:57 homeassistant kernel: usb 2-7: device descriptor read/64, error -110
Nov 02 14:23:13 homeassistant kernel: usb 2-7: device descriptor read/64, error -110
Nov 02 14:23:13 homeassistant kernel: usb 2-7: reset full-speed USB device number 4 using xhci_hcd
Nov 02 14:23:18 homeassistant kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
Nov 02 14:23:24 homeassistant kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
Nov 02 14:23:24 homeassistant kernel: usb 2-7: device not accepting address 4, error -62
Nov 02 14:23:24 homeassistant kernel: usb 2-7: reset full-speed USB device number 4 using xhci_hcd
Nov 02 14:23:34 homeassistant kernel: xhci_hcd 0000:00:14.0: Abort failed to stop command ring: -110
Nov 02 14:23:34 homeassistant kernel: xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
Nov 02 14:23:34 homeassistant kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up
Nov 02 14:23:34 homeassistant kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
Nov 02 14:23:34 homeassistant kernel: usb 2-1: USB disconnect, device number 2
Nov 02 14:23:35 homeassistant kernel: usb 2-3: USB disconnect, device number 3
Nov 02 14:23:35 homeassistant kernel: cp210x ttyUSB0: failed set request 0x7 status: -19
Nov 02 14:23:35 homeassistant kernel: cp210x ttyUSB0: failed set request 0x12 status: -19
Nov 02 14:23:35 homeassistant kernel: cp210x ttyUSB0: failed set request 0x0 status: -19
Nov 02 14:23:35 homeassistant kernel: cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
Nov 02 14:23:35 homeassistant kernel: cp210x 2-3:1.0: device disconnected
Nov 02 14:23:35 homeassistant kernel: usb 2-7: USB disconnect, device number 0
Nov 02 14:23:35 homeassistant kernel: usb 2-7: device not accepting address 4, error -22
Nov 02 15:48:03 homeassistant kernel: audit: type=1334 audit(1698940083.755:743): prog-id=252 op=LOAD
Nov 02 15:48:21 homeassistant kernel: audit: type=1334 audit(1698940101.725:744): prog-id=253 op=LOAD
Nov 02 15:48:21 homeassistant kernel: audit: type=1334 audit(1698940101.725:745): prog-id=254 op=LOAD
Nov 02 15:48:21 homeassistant kernel: audit: type=1300 audit(1698940101.725:745): arch=c000003e syscall=321 success=yes exit=16 a0=5 a1=c00018d988 a2=78 a3=0 items=0 ppid=605131 pid=605140 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)
Nov 02 15:48:21 homeassistant kernel: audit: type=1327 audit(1698940101.725:745): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F37343835396639666631633931653837363432383534333465
Nov 02 15:48:21 homeassistant kernel: audit: type=1334 audit(1698940101.726:746): prog-id=255 op=LOAD
Nov 02 15:48:21 homeassistant kernel: audit: type=1300 audit(1698940101.726:746): arch=c000003e syscall=321 success=yes exit=18 a0=5 a1=c00018d720 a2=78 a3=0 items=0 ppid=605131 pid=605140 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)
Nov 02 15:48:21 homeassistant kernel: audit: type=1327 audit(1698940101.726:746): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F37343835396639666631633931653837363432383534333465
Nov 02 15:48:21 homeassistant kernel: audit: type=1334 audit(1698940101.726:747): prog-id=255 op=UNLOAD
Nov 02 15:48:21 homeassistant kernel: audit: type=1334 audit(1698940101.726:748): prog-id=254 op=UNLOAD
Nov 02 15:48:21 homeassistant kernel: audit: type=1334 audit(1698940101.726:749): prog-id=256 op=LOAD

Does this point to a particular issue or anything else I should try? TIA!

@robtpaton robtpaton changed the title HAOS >=10.3 randomly loses connection to Sonoff Zigbee 3.0 USB Dongle Plus HAOS randomly loses connection to Sonoff Zigbee 3.0 USB Dongle Plus Dec 17, 2023
@robtpaton
Copy link
Author

I've updated the bug report as originally I said the issue only happened with 10.3 but it actually occurs with other versions as well.

I've also just found this issue which could be related.

home-assistant/supervisor#3740

Can anyone help?

Thanks

@robtpaton robtpaton reopened this Dec 17, 2023
@robtpaton
Copy link
Author

@mike10101011 I see you raised a similar issue, did you ever solve it? TIA

@Sebazzz
Copy link

Sebazzz commented Jan 8, 2024

Is this the same issue as #2756?

@robtpaton
Copy link
Author

Since changing USB power settings in the BIOS of my NUC (suggestion from Discord), I have not had a single occurrence of this (so it probably wasn't an issue with Home Assistant itself). Closing this issue for now!

@agners
Copy link
Member

agners commented Jan 8, 2024

@robtpaton you used the native HAOS installation on your NUC correct?

Can you be more specific what the power option was?

@robtpaton
Copy link
Author

@agners that's correct HAOS installed on the NUC using the x86_64 image.

I haven't had a chance to connect it back up to a screen to review the settings but I tweaked anything I could find related to powering USB devices to favour less power-saving, and generally disabled any advanced USB features (I think I even set some sort of USB Handling setting to Legacy or Basic, something like that).

So far so good, everything rock solid since then. I will reply with more specifics when I can

Thanks

@robtpaton robtpaton reopened this Jan 15, 2024
@rt18de
Copy link

rt18de commented Jan 30, 2024

I think I have the exactly same issue with Sonoff P dongle (HA on Raspberry Pi). When the problem occurs, restarting HA will not resolve the issue. All devices are not available. Restarting Zigbee2MQTT add-on can resolve the problem and all devices will immediately work again. That's why I suspect it's Sonoff P drop. I don't know however, where I can change the USB settings.
Looking forward to hearing your experienes again

@robtpaton
Copy link
Author

Not sure if yours is the same issue or a different one @rt18de. The settings that have definitely helped for me were in my BIOS, so probably specific to the host hardware. But here are the screens I believe I changed:

PXL_20240209_115527268
PXL_20240209_115545145

I have to say I can't remember exactly what the settings were before I changed them, but I think I enabled USB Legacy and anything that sounded related to USB power.

Good luck!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
board/generic-x86-64 Generic x86-64 Boards (like Intel NUC) bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@agners @Sebazzz @robtpaton @rickgardner077 @rt18de