Z-Wave is not dead

Hedda · July 14, 2024, 5:24pm

No other Z-Wave USB dongle has unique product identifier, but the SkyConnect ZBT-1 does have a unique product identifier which is enough, see:

And

github.com/home-assistant/core

USB discovery entries for Z-Wave JS are too generic

opened 12:15PM - 02 Sep 21 UTC

RicArch97

integration: usb

### The problem in `/homeassistant/generated/usb.py` there are some entries for… VID/PID combo's that identify USB dongles with a specific integration. For Z-Wave JS this is included in the file: ``` { "domain": "zwave_js", "vid": "10C4", "pid": "EA60" } ``` The VID:10C4 and PID:EA60 belong to a very generic cp210x chipset by Silicon labs. The problem is that all other devices that **aren't** Z-Wave JS radio's now show up as Z-Wave. I'm sure this isn't a problem for the current core integrations as Z-Wave JS and ZHA are about the only onces that use USB, but if you'd use any other dongles from a custom integration this will become very confusing for users. Also for future proofing purposes, it might be useful to identify more devices with this chipset within core. One solution could be to identify based on description (iProduct) too just like ZHA but i'm not sure if those are provided with the Z-Wave sticks. ### What is version of Home Assistant Core has the issue? core-2021.9.0 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue USB Discovery ### Link to integration documentation on our website https://www.home-assistant.io/integrations/usb/ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? _No response_ ### Additional information ![2021-09-02T13:49:27,593849507+02:00](https://user-images.githubusercontent.com/61013287/131841603-56a4b69d-e863-4a58-8c12-19013e317ac4.png) ^ not a z-wave dongle but is identified as one.