For the future, if the device is already paired, you should be able to choose a driver from the device’s three-dot menu if you install something different you’d like to use.
Is that a custom DTH? It sounds like a stock one but worth asking. If it’s custom, you can edit it and comment out the fingerprint section (if it even has a matching fingerprint to your device); I thought that DTH’s had dropped off the priority list for pairing at this point though, so if it paired with a driver previously and this DTH is completely random then it sounds like something changed in error behind the scenes (@nayelyz ?).
That’s a fallback handler that seems to do the square root of beggar all apart from exist. It has a fingerprint of deviceId: "0x01" and I don’t think it is the first time lately that it, or one with a similarly terse fingerprint, seems to have been confusing pairing for Zigbee Edge drivers.
If it is paired to a stock DTH it’s because no compatible driver was found. @RBoy, does this driver have the exact fingerprint for those devices?
If so, we should check what’s going on, we’ve seen some devices aren’t reporting their fingerprints correctly to the Hub and as they’re incomplete, the closest match is selected.
Once, @RBoy confirms, we’ll need your help @sulisenator by following these steps:
Replicate the issue and take note of the time when you did.
Send your Hub’s logs. Note: Do not reboot the Hub during these steps, otherwise, all the logs will be deleted
The fingerprint of the device to know which values are expected from it
Your Hub’s ID (the one that appears in the IDE)
(www.rboyapps.com - Making SmartThings Easy!)
Yes it does. However in his screenshot above I don’t see any fingerprint. Maybe the device hasn’t paired correctly plus it’s using a zwave dth while it’s a ZigBee device. Never seen that happen before. @sulisenator whats the raw description on that page. It’s not showing in the screenshot