Closed IGastel closed 2 years ago
[ 1.888321] usb 3-1: New USB device found, idVendor=10ac, idProduct=0102, bcdDevice= 1.01
[ 1.889626] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.890734] usb 3-1: Product: TUSB3410 Boot Device
[ 1.891643] usb 3-1: Manufacturer: Texas Instruments
[ 1.892596] usb 3-1: SerialNumber: TUSB3410
[ 1.895562] usb 3-1: can't set config #1, error -32
Error -32 means "broken pipe", which often points to a USB hardware problem.
Can you try revert back to HAOS 8.4 to see if that fixes your poblem indeed? E.g. by selecting the other Boot slot at boot up in GRUB2, or by using:
ha os update --version 8.4
I downgraded, but my problem remained. strange coincidence that my USB device breaks at the moment i upgrade.
Thanks for confirming. Maybe a complete system reboot helps? I'd suggest to try different USB port/different cables as well.
@IGastel When I upgraded to 8.5, Zigbee2MQTT wouldn't start because it couldn't find the coordinator USB stick, which wasn't identified by device ID. Changing it so it was identified by device ID fixed it. I think this is perhaps the opposite of your problem but it suggests that something in the handling of USB devices could have changed. Don't know, I'm new here.
@lakofka i have 4 USB devices all identified by their device ID. i did this to prevent a reboot would giving my USB devices a new port number. only 1 device is not recognized anymore after reboot.
@IGastel sounds like your problem is different to what mine was, then. I wish I could be some help, good luck, I hope you find a solution.
After multiple restarts of the virtual machine, the USB device appeared again. appologies for waisting time.
Describe the issue you are experiencing
after upgrade from 8.4 to 8.5 my USB reviever (honeywell HGI80 which uses a TI USB3410 chip) is no longer showing in the hardware list. i have the following error in the log: Failed to open /dev/serial/by-id/usb-Texas_Instruments_TUSB3410_Boot_Device_TUSB3410-if00-port0 (config: {'rtscts': False, 'baudrate': 115200, 'dsrdtr': False, 'xonxoff': True, 'timeout': 0}): [Errno 2] could not open port /dev/serial/by-id/usb-Texas_Instruments_TUSB3410_Boot_Device_TUSB3410-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-Texas_Instruments_TUSB3410_Boot_Device_TUSB3410-if00-port0'
What operating system image do you use?
ova (for Virtual Machines)
What version of Home Assistant Operating System is installed?
8.5
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
upgraded via UI from 8.4 to 8.5
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System Health information
System Information
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 5000 Installed Version | 1.26.2 Stage | running Available Repositories | 1099 Downloaded Repositories | 9Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | August 23, 2023 at 02:00 relayer_connected | true remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | true remote_server | eu-west-2-2.ui.nabu.casa can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 8.5 -- | -- update_channel | stable supervisor_version | supervisor-2022.08.3 agent_version | 1.2.1 docker_version | 20.10.14 disk_total | 30.8 GB disk_used | 9.5 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | ESPHome (2021.8.2), File editor (5.3.3), Mosquitto broker (6.1.2), SSH & Web Terminal (12.0.2), Samba share (10.0.0), deCONZ (6.15.0), Studio Code Server (5.3.0)Dashboards
dashboards | 2 -- | -- resources | 3 views | 4 mode | storageRecorder
oldest_recorder_run | August 18, 2022 at 19:25 -- | -- current_recorder_run | August 24, 2022 at 22:07 estimated_db_size | 312.97 MiB database_engine | sqlite database_version | 3.38.5Spotify
api_endpoint_reachable | ok -- | --Additional information
No response