As I understand it from this February 2018 thread, Z-Wave and ZigBee device drivers are matched to devices being paired mainly based on the inClusters listed in the fingerprint lines of all available device drivers:
Since my own "development" of device drivers is limited to ZigBee devices, I can only state that this method of matching seems to result in false positives for completely different devices which have the exact same
model: string supplied by devices at pairing be used in matching fingerprints to corresponding devices? This seems like a much better tie breaker than additionally comparing
manufacturer (if used at all).
If I am actually mistaken and the
model string is being used, then how can I get that working correctly? I have worked on device drivers with fingerprint lines containing data copied directly from the additional pairing info text given by my Hubitat hub, and yet the wrong device driver is selected for some devices that share the exact same
outClusters strings found in multiple device drivers.
Another (less important) request here: Is there any way for a fingerprint's
deviceJoinName string to be used? It would be really nice for this to be used as the initial suggested name of the device as it's paired.
Tagging @mike.maxwell since you're probably the one who decides whether this happens or not.