Fingerprint (of device)

Hi @duncan, I’ve been working on getting an off the shelf NXP module (ZigBee) to communicate well with ST. I have it talking now and am working on getting bindings correct etc. But one thing that would be nice is if the configure() ran automatically and my understanding from @urman is that it runs just once after pairing. If I don’t have my device type being identified though on pair (as is the case today) then doesn’t it lose it’s chance to run configure()?

So I have 2 related questions:

  1. is there a log or something that I can spit out when I pair a device to see what ST hub saw and used for it’s fingerprinting attempt? I’m guessing that’s probably not something you have today except internally but figured I would ask.

  2. If inClusters and outClusters match multiple Device Types how do you chose which one to use? I know there are other things like profileId and deviceId in the fingerprint statement, but you didnt mention those being used in the fingerprint process?

If the answer to (1) is there is no way, then I’m stuck either sniffing (and I don’t yet have a sniffer) or maybe I can log it out of the ZCL on the device side. Or I could try JTAG also but I don’t have JTAG. In which case I may just try to keep guessing for a while. :stuck_out_tongue:

Justin