question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

USB discovery entries for Z-Wave JS are too generic

See original GitHub issue

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

^ not a z-wave dongle but is identified as one.

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:2
  • Comments:39 (23 by maintainers)

github_iconTop GitHub Comments

3reactions
bdracocommented, Dec 13, 2021

I think the problem is well understood, we are just waiting for vendors to provide identifiers at this point.

1reaction
mrquinclecommented, Jun 7, 2022

Even those current vendors might want to bring out different sticks in the future (e.g. Matter, etc.) with the same SiLabs chip on-board. It’s just weird to assume that a CP210x UART bridge is a Zwave device.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Unable to get Zwave to work - #22 by mwav3 - Configuration
This worked for me: Navigate to Settings > System > Hardware and click the stacked dots at the top right corner:.
Read more >
Supervisor Discovery service detects Z-Wave JS UI ... - GitHub
The problem. On an HAOS installation, if the Z-Wave JS UI add-on is installed, DNS Service Discovery is enabled by default.
Read more >
Z-Wave JS in docker with USB stick not recognizing any z ...
I am trying to make u.wave.me USB stick work in HomeAssistant in docker. I have create docker compose for zjs server as follows:...
Read more >
Home Assistant How To Set Up Z-Wave 2022 - YouTube
In this video we show you how to set up Home Assistant to use Z-Wave smart devices Z-Wave is a proprietary wireless protocol...
Read more >
Set up Z-Wave in Home Assistant - The Private Smart Home
A guide on how to set up Z-Wave JS in Home Assistant. ... USB Z-Wave controllers are often the most convenient plug and...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found