Z-Wave fingerprinting documentation needs update

(Benjamin Pelletier) #1

In the Device Handlers Definition page, it says the easiest way to get the fingerprint for a Z-Wave device is to look at the Raw Description for your physical device. But, the example shown on that page just has a list of 0x-prefixed numbers; e.g.:

0 0 0x2001 0 8 0x30 0x71 0x72 0x86 0x85 0x84 0x80 0x70 1 0x20

This is not what the Raw Description currently looks like. Instead, it looks like, e.g.:

zw:S type:2101 mfr:0060 prod:0006 model:0001 ver:2.01 zwv:3.52 lib:03 cc:31,60,86,72,85,84,80,70,20,71 epc:2 ep:[‘2101 20,31’]

The device handler documentation needs to be updated to reflect the new format of the device Raw Description. Most importantly, however, I need to know 1) where the device ID is in the new Raw Description format (is it the “type”?) and 2) whether the numbers in the new Raw Description format are decimal or hexadecimal.

(Jason) #2


Tagging @jim

(Duncan) #4

Sorry, that’s a great point. I was waiting for full support of the new format to add it to the docs, but I didn’t think about the fact that they’re referencing the old description format. I’ll work with Jim to get those updated asap.

For now, if you just want to target a single device, the best way is to take mfr, prod, and model from the raw description and add quotes and commas, so for your device you’d do

fingerprint mfr:"0060", prod:"0006", model:"0001"

If you want it to still work with hub v1, take the “cc” list (combined with the “sec” list if present) as “inClusters” like this:

fingerprint inClusters: "0x31,0x60,0x86,0x72,0x85,0x84,0x80,0x70,0x20,0x71"

All the values are still hexadecimal.

(Benjamin Pelletier) #5

Perfect – thanks schapper05 and duncan.