Z-Wave.me UZB dongle not fully recognized

[jires]

trafficstars

Describe the issue you are experiencing

After updating to 11.1, my usb dongle for Z-Wave became unresponsive and integration z-wave js ui hangs or won't start from time to time. When I turn on the monitor connected to Intel NUC, I can se that dongle generates some errors when connected to usb port.

It's saying "device descriptor read/64, error -32

It's like missing driver or something. Issue persist in 11.2 version. Right now, I had to move my z-wave network to Aeotec Z-Stick 7.

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.1.63-haos - Home Assistant OS 11.2

Did you upgrade the Operating System.

Yes

Steps to reproduce the issue

1. start the system up
2. Plug an USB dongle ZMEEUZB from Z-Wave.Me into usb port

...

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

Not really

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

Not Really

System information

System Information

version	core-2023.10.3
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.63-haos
arch	x86_64
timezone	Europe/Copenhagen
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	5000
Installed Version	1.33.0
Stage	running
Available Repositories	1353
Downloaded Repositories	22

Home Assistant Cloud

logged_in	true
subscription_expiration	September 7, 2024 at 02:00
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-11.ui.nabu.casa
certificate_status	ready
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 11.2
update_channel	stable
supervisor_version	supervisor-2023.11.6
agent_version	1.6.0
docker_version	24.0.7
disk_total	916.2 GB
disk_used	64.5 GB
healthy	true
supported	true
board	generic-x86-64
supervisor_api	ok
version_api	ok
installed_addons	Advanced SSH & Web Terminal (16.0.1), InfluxDB (4.8.0), Grafana (9.1.1), Node-RED (16.0.2), File editor (5.7.0), Studio Code Server (5.14.2), Mosquitto broker (6.4.0), Home Assistant Google Drive Backup (0.112.1), Network UPS Tools (0.12.2), ESPHome (2023.11.6), Samba share (12.2.0), Filebrowser (2.23.0_7), Portainer (2.19.3), Log Viewer (0.16.0), Glances (0.20.0), Frigate (Full Access) (0.12.1), Z-Wave JS UI (3.0.2), Zigbee2MQTT (1.34.0-1)

Dashboards

dashboards	7
resources	5
views	41
mode	storage

Recorder

oldest_recorder_run	March 17, 2023 at 20:34
current_recorder_run	December 7, 2023 at 19:12
estimated_db_size	17118.81 MiB
database_engine	sqlite
database_version	3.41.2

Additional information

No response

[mcolyer]

I'm having a similar issue, after upgrading to 11.2 my usb Zwave hub is no longer recognized.

[sblogoshs]

In my case, it is the SkyConnect stick that stops working after a few hours and the problem can only be solved by unplugging it and plugging it in again. A downgrade to 11.1 solved the problem for me.

[mcolyer]

Can confirm that downgrading to 11.1 and then unplugging and replugging in the dongle (Aeotec z-stick Gen 5) fixes the issue.

[ohessel]

On my RPI 3b+ downgrading to 11.1 (ha os update --version 11.1) directly fixed the issue with Z-Wave USB Stick (ZMEEUZB1).

[bnounours]

Same as all, I upgraded to OS 11.2 Zwave stop working as the stick was no more detected. I downgraded to OS 11.1, stick is back online.

[GHGiampy]

Also related #2977

[sairon]

We suspect it could be caused by some regression in the stable kernel, because at the same time similar issues started to appear on RPi and x86 platforms. There is bunch of changes in the USB subsystem in the newer stable releases which are currently in the development branch. If there's someone willing to switch to the dev channel and test it, it will help a lot (but make sure you have backups, since it switches all the components to dev and things can go south much more often).

ha supervisor options --channel=dev
ha supervisor reload
ha supervisor update
ha os update

Otherwise there should be another beta release soon, we will appreciate early feedback after the release too.

[sairon]

Since OS 11.3.rc1 is out for a while already, has anyone been able to check if the problem persists there?

[sblogoshs]

I also noticed that with OS 11.3.rc1 but for me it just took longer until the error reappeared, it just depends on how long there is no restart.

[llroelj]

We suspect it could be caused by some regression in the stable kernel, because at the same time similar issues started to appear on RPi and x86 platforms. There is bunch of changes in the USB subsystem in the newer stable releases which are currently in the development branch. If there's someone willing to switch to the dev channel and test it, it will help a lot (but make sure you have backups, since it switches all the components to dev and things can go south much more often).

ha supervisor options --channel=dev
ha supervisor reload
ha supervisor update
ha os update

Otherwise there should be another beta release soon, we will appreciate early feedback after the release too.

I will try this tomorrow morning and will keep you posted if it works.

[agners]

@mcolyer @sblogoshs @ohessel @bnounours @llroelj do you see the same device descriptor read errors as the original poster?

@bnounours which stick are you using?

[llroelj]

@mcolyer @sblogoshs @ohessel @bnounours @llroelj do you see the same device descriptor read errors as the original poster?

@bnounours which stick are you using?

After going through the above mentioned steps I am having the same error as mentioned above and the one I had before downgrading to 11.1

usb 1-1.1.2: device descriptor read/64, error -32

I see in the Z-Wave JS addon also the same error popping up: " Driver: Failed to open the serial port: Error: No such file or directory, cannot open /dev/serial/by-id/usb-0658_0200-if00 (ZW0100)"

Currently I am running the following versions:

Core: 2023.12.3 Supervisor: 2024.01.0.dev0201 Operating System: 11.4.dev20231226 Frontend: 20231208.2

[agners]

@llroelj so you are saying you had the device descriptor read with 11.2 as well as the OS version from the dev channel?

What (exact) hardware are you running HAOS on?

[llroelj]

@llroelj so you are saying you had the device descriptor read with 11.2 as well as the OS version from the dev channel?

What (exact) hardware are you running HAOS on?

Indeed I had the same message in 11.2 and now the dev channel. With both the zwave stick cannot be found by the system itself (no serial folder). If needed I can share my dmesg log with all information.

I am running HAOS on a RPi3 B+ 1GB memory installed on a SanDisk Ultra 32GB microSDHC card The Zwave USB stick is a Z-Wave.me Stick (ZMEEUZB1)

[mnorrsken]

My problems with USB is solved now after upgrading to HAOS 11.3. I had problems with ConbeeII zigbee dongle not being detected. This is possibly another issue but worth trying 11.3 as I see a couple of kernel USB fixes.

[sblogoshs]

With the final version OS 11.3 the error seems to be fixed, but due to various updates I haven't had 24 hours without a restart yet, I hope that it will still work.

[jires]

I can tell that upgrade to OS 11.3 DID NOT FIXED (? or did?) the issue with Z-Wave.me UZB. Descriptor error is still coming, however it's looks like that dongle is working as expected Log output from host, after plugin dongle in the usb port, when system reboted with dongle plugged in, there is no errors in the log:

Jan 07 12:04:09 homeassistanttest kernel: usb 1-1.3: new full-speed USB device number 6 using xhci_hcd
Jan 07 12:04:09 homeassistanttest kernel: usb 1-1.3: device descriptor read/64, error -32
Jan 07 12:04:09 homeassistanttest kernel: usb 1-1.3: device descriptor read/64, error -32
Jan 07 12:04:10 homeassistanttest kernel: usb 1-1.3: new full-speed USB device number 7 using xhci_hcd
Jan 07 12:04:10 homeassistanttest kernel: usb 1-1.3: device descriptor read/64, error -32
Jan 07 12:04:10 homeassistanttest kernel: usb 1-1.3: device descriptor read/64, error -32
Jan 07 12:04:10 homeassistanttest kernel: usb 1-1-port3: attempt power cycle
Jan 07 12:04:11 homeassistanttest kernel: usb 1-1.3: new full-speed USB device number 8 using xhci_hcd
Jan 07 12:04:11 homeassistanttest kernel: usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
Jan 07 12:04:11 homeassistanttest kernel: usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 07 12:04:11 homeassistanttest kernel: cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device

[kvandt]

I have the same on my HA Yellow. When upgrading to 11.2 or 11.3 my UZB Zwave stick cannot be found anymore. No usb device available. When downgrading to 11.1, everything works again. I have tried the upgrade three times, but no luck. I hope this can be fixed in next release.

[ohessel]

@agners I did not download the logs, and the journal of the error is rotated away already. If it helps, I could update again (or better setup a clone, as I don't want to break my system) and see if those exact logs appear.

[afaucogney]

I'm in the same situation, with 2 different Zwave devices. Now running 11.4OS

[ohessel]

@afaucogney So you're saying 11.4 has the same issue?

[afaucogney]

@ohessel Yes it seems the same issue. I have reboot to be certain that everything is clear, but then I canot find my usb stick in the all_hardware list And ZWaveJS is not able to talk to the controller. Should it work with that version ?

[kvandt]

@sairon can you please add the board/yellow label as well? I have this issue on the yellow (see earlier post).

[afaucogney]

Is there some activity on this topic, or do you need some information/log to help you ?

[sairon]

I finally got my hands on the UZB stick to test myself. What should be noted is that the device descriptor read messages appear to be a red herring - I get them every time the device is hotplugged, and I get them on other kernels/distros too - I assume it's caused by a HW design fault that the device appears on the USB bus before it's properly initialized. The following lines (starting with New USB device found ...) indicate it's loaded properly in the end.

So far the device works for me on 11.2 through 11.4, so there must be something different on the problematic devices. For those who have the issues, can you share a bit more info?

1. What HW are you running HAOS on?
2. What version is the UZB firmware (shown on Z-Wave integration detail)?
3. Is the stick missing immediately when the host device is cold-booted (i.e. no USB hot-plugging)? If so, please post the dmesg output or host logs.
4. If the issue appears after some time of HA running, how long does it take, and does anything appear in the host logs/dmesg when it happens?

[MUN0X]

I had this issue after upgrading to 11.2 so I stayed on 11.1 for now. Will try 11.4 and see what happens.
Running Home assistant on a Yellow. UZB firmware 5.27. If i remember correctly the device never showed up after cold booting

[MUN0X]

Problem still persists in 11.4 Here is the output of dmesg | grep -i usb: [ 0.112239] usbcore: registered new interface driver usbfs [ 0.112302] usbcore: registered new interface driver hub [ 0.112374] usbcore: registered new device driver usb [ 0.112728] usb_phy_generic phy: supply vcc not found, using dummy regulator [ 1.449922] usbcore: registered new interface driver uas [ 1.450005] usbcore: registered new interface driver usb-storage [ 1.450107] usbcore: registered new interface driver usbserial_generic [ 1.450150] usbserial: USB Serial support registered for generic [ 1.462440] usbcore: registered new interface driver usbhid [ 1.462450] usbhid: USB HID core driver [ 6.225448] dwc2 fe980000.usb: supply vusb_d not found, using dummy regulator [ 6.298391] dwc2 fe980000.usb: supply vusb_a not found, using dummy regulator [ 6.546981] dwc2 fe980000.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [ 6.555240] dwc2 fe980000.usb: DWC OTG Controller [ 6.567977] dwc2 fe980000.usb: new USB bus registered, assigned bus number 1 [ 6.575236] dwc2 fe980000.usb: irq 46, io mem 0xfe980000 [ 6.580794] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 [ 6.589347] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 6.596674] usb usb1: Product: DWC OTG Controller [ 6.601449] usb usb1: Manufacturer: Linux 6.1.63-haos-raspi dwc2_hsotg [ 6.616774] usb usb1: SerialNumber: fe980000.usb [ 6.636862] hub 1-0:1.0: USB hub found [ 7.034989] usb 1-1: new high-speed USB device number 2 using dwc2 [ 7.247798] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.00 [ 7.261414] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 7.275315] usb 1-1: Product: USB 2.0 Hub [MTT] [ 7.304109] hub 1-1:1.0: USB hub found [ 7.775013] usb 1-1.1: new full-speed USB device number 3 using dwc2 [ 7.974937] usb 1-1.1: device descriptor read/64, error -32 [ 8.286902] usb 1-1.1: device descriptor read/64, error -32 [ 8.602957] usb 1-1.1: new full-speed USB device number 4 using dwc2 [ 8.802978] usb 1-1.1: device descriptor read/64, error -32 [ 9.114943] usb 1-1.1: device descriptor read/64, error -32 [ 9.227169] usb 1-1-port1: attempt power cycle [ 9.934939] usb 1-1.1: new full-speed USB device number 5 using dwc2 [ 9.959294] usb 1-1.1: device descriptor read/8, error -32 [ 10.095291] usb 1-1.1: device descriptor read/8, error -32 [ 10.386948] usb 1-1.1: new full-speed USB device number 6 using dwc2 [ 10.407313] usb 1-1.1: device descriptor read/8, error -32 [ 10.539288] usb 1-1.1: device descriptor read/8, error -32 [ 10.651088] usb 1-1-port1: unable to enumerate USB device [ 10.854957] usb 1-1.2: new full-speed USB device number 7 using dwc2 [ 11.077618] usb 1-1.2: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00 [ 11.077645] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 11.077663] usb 1-1.2: Product: ConBee II [ 11.077678] usb 1-1.2: Manufacturer: dresden elektronik ingenieurtechnik GmbH [ 11.077692] usb 1-1.2: SerialNumber: DE2215099 [ 11.232100] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device [ 11.232189] usbcore: registered new interface driver cdc_acm [ 11.232196] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 11.431673] usb 1-1.2: USB disconnect, device number 7 [ 11.754923] usb 1-1.2: new full-speed USB device number 8 using dwc2 [ 11.977619] usb 1-1.2: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00 [ 11.977648] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 11.977666] usb 1-1.2: Product: ConBee II [ 11.977681] usb 1-1.2: Manufacturer: dresden elektronik ingenieurtechnik GmbH [ 11.977695] usb 1-1.2: SerialNumber: DE2215099 [ 11.979327] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device

[afaucogney]

Hi,

I use the HA yellow with firmware 5.5 for the Zwave stick + HA OS 11.4 I have also tried with another purchased stick that I return back, because it changed nothing (no info about the firmware, but should be recent) I get some info in the Zwave integration, but the ZWaveJS failed to start. I do not see it in the "all-hardware" list. I didn't tested recently with hot-plugging ? does it make sens to help you ?

Anthony

[Taraman17]

Has anyone tried HAOS 11.5 with regard to this issue? Was there any change in it that could fix this?

[Tomfr06]

Just tried 11.5 jump from 11.1 and my Z-Wave.Me stick went missing... Reverted to 11.1 and it's back