zwave-js / node-zwave-js

Z-Wave driver written entirely in JavaScript/TypeScript
https://zwave-js.github.io/node-zwave-js/
MIT License
751 stars 602 forks source link

Missing device configuration: <enter manufacturer and device name> #3887

Closed TeckPete closed 2 years ago

TeckPete commented 2 years ago

Checklist

Which device is missing?

Yale yrd256

Manufacturer ID

0x0129

Product Type

0x8002

Product ID

0xA570

Firmware Version

No response

Is the device listed on the Z-Wave Alliance website?

https://products.z-wavealliance.org/products/3882?selectedFrequencyId=2

Do you have a manual?

80B20A9E-51E8-4642-BE43-D1792DE94219 D7348438-84FF-412D-9F38-F17A6FFAFC49 C4441CCD-BBDF-4FAC-99F8-CEF8874A1881

marcus-j-davies commented 2 years ago

The Identifier you have provided is already supported. https://devices.zwave-js.io/?jumpTo=0x0129:0x8002:0xa570:0.0 - (YRD256-ZW3 )

However, the one in your screenshot: 0x0131:0x0003:0x1111 is not found - which is some Zipato device?

What ID's are we looking at here in your report - My head hurts!

Please could you correct where necessary, including the title

Missing device configuration: \<enter manufacturer and device name>

blhoward2 commented 2 years ago

Please post the actual dump, not a screenshot. We need to be able to scroll through it. What node is at issue?

TeckPete commented 2 years ago

When I try to upload the zwave_jsdump.json I get an error saying the file type is not supported. So how do I include it?

blhoward2 commented 2 years ago

Just zip it and upload the zip file.

TeckPete commented 2 years ago

zwave_js_dump.zip

AlCalzone commented 2 years ago

Node 14 in your dump has almost no information and the bit that's there seems like zwave-js wasn't able to determine which security classes it uses. It is also missing the identification part, which is probably why its not being identified properly. To better diagnose this, please do the following:

  1. Make a driver log, loglevel debug or silly
  2. Exclude the node, and re-include it. Leave the log active
  3. Wait until it is interviewed completely
  4. Send me the logfile to the e-mail in my profile, referencing this issue
TeckPete commented 2 years ago

So I did it and during inclusion this time it pulled the correct attribute's not sure why I tried this 3 times before but it's working great not thanks anyway.