Qubino 16A plug, help needed with defining fingerprint

🚧 Developers Code Share
1

Hi Folks,
Writing driver for Qubino Smart Plug 16A, but need to be sure re correct device fingerprint.

Here is the Data from joined device:

  • zwaveSecurePairingComplete: true
  • S2: 131
  • deviceId: 84
  • deviceType: 2
  • manufacturer: 345
  • inClusters: 0x5E,0x6C,0x55,0x98,0x9F
  • secureInClusters: 0x86,0x25,0x85,0x59,0x72,0x5A,0x70,0x32,0x71,0x73,0x7A
  • firmwareVersion: 3.0
  • protocolVersion: 5.03
  • hardwareVersion: 2
  • serialNumber: 19290C1DV069
  • zwNodeInfo: D3 9C 83 04 10 01 5E 6C 55 98 9F 68 23 F1 00 86 25 85 5C 59 72 5A 70 32 71 73 7A

So, here are the questions:

  1. Device joined as S2. Should I specify as fingerprint those listed in inClusters ( "0x5E,0x6C,0x55,0x98,0x9F"), or those listed in secureInClusters ("0x86,0x25,0x85,0x59,0x72,0x5A,0x70,0x32,0x71,0x73,0x7A")?

  2. it's strange that zwNodeInfo ends as "86 25 85 5C 59 72 5A 70 32 71 73 7A" which presume are the clusters. But in there is listed also "5C" while it completely miss from both inClusters and secureInClusters. Can you advise why?

Will be great if skillful dev can write the exact fingerprint I need to use in my driver.

2

Use the driver named Device, open live logging, then run the getInfo command, use the fingerprint as sent to the logs...

2 Likes
3

Wow, so Helpful, thanks a lot!

fingerprint mfr:"0159", prod:"0002", deviceId:"0054", inClusters:"0x5E,0x6C,0x55,0x98,0x9F"

1 Like
4

A further question . . .

Is secureInClusters a recognized field in the fingerprint? I have some cases where I may want to distinguish based on secureInClusters (but if it isn't recognized, this isn't a big concern - I just don't want to start adding it only to find it isn't a proper field).

5

It isnt.

6

Did anybody manage to write a driver for this?

7

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.