Zwave device neo coolcam recognized as node but with "Undefined Manufacturer"

[surf33]

The problem

Describe the issue you are experiencing

The device Zwave Neo CoolCam NAS-DS01 is recognized as a node but is not fully recognized. It just have the "ping" and "node status". I have the label "Undefined Manufacturer". However, it is in the official zwave database https://devices.zwave-js.io/?jumpTo=0x0258:0x0003:0x0082:0.0

Steps to reproduce the issue

• include in the zwave network the new device
• go into the zwave JS UI
• it is indicated : "Device ID undefined-undefined-undefined (0xXXXX-0xXXXX-0xXXXX)"

What version of Home Assistant Core has the issue?

2023.1.6

What was the last working version of Home Assistant Core?

latest

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Z Wave JS

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js/

Diagnostics information

config_entry-zwave_js-016c42c69c8fbc37c5e7e911a6baf02e.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `zwave_js` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Change the title of the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zwave_js` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation zwave_js source _{^{(message by IssueLinks)}}

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.