I’m working on a custom device type for a new ZigBee device and I cant get the fingerprint process to fire when the device joins the network. Here is what I have for the fingerprint section in the custom device type:
`
The device has been Published “For Me”. This has worked for me in the past with other custom device types I have written. Is anyone else having a problem or see something I’m doing wrong.
@Support@Tyler I know other people are having the same problem. Is there any news on this? Where can I go to get answers. I use to ping @urman for help but he is gone.
This issue is related to device types published to a single account. When you go to pair a device it’s not properly fingerprinting to a locally installed device type. The workaround is to pair it, then manually edit the type of the device from the My Devices page.
The fix for this issue is slated to be published today. You’ll know it’s fixed when the release notes are posted here on the forums.
Would this also have affected any zwave devices? Specifically the Enerwave SC7, which used to work and then new devices showed strange behaviour. Or is that something else?
@Tyler Yes Sir the problem is fixed!! Checked this morning and my new ZigBee device’s (Chicken Coop Door controller) footprint matched it to its custom device type and works like a champ!! Now we can close our Chicken Coop door with SmartThings!! Wife is happy!!!