New Zigbee HA1.2 Dimmer Device Identified as Unknown

Hi there,

I’m new here and am trying to add a fingerprint to the Zigbee Dimmer device handler so that when I pair a Zigbee dimmer that I’ve developed, it shows up as a dimmer when paired with the hub instead of showing up as a Thing of Unknown type.

I have read through the documentation and looked through some applicable forum pages such as:
http://docs.smartthings.com/en/latest/device-type-developers-guide/building-zigbee-device-handlers.html
http://docs.smartthings.com/en/latest/device-type-developers-guide/definition-metadata.html#zigbee-fingerprinting-label

At the moment, the dimmer is identified as a Thing of Unknown type. I am able to manually go into the device via the IDE and change the type to Zigbee Dimmer, RGB or RGBW bulb and it turns on/off and dims fine. However, I want the dimmer to be automatically detected on pairing instead of having to manually change it every time I want to pair one.

When the device joins, the hub gets the following info from my device:
zbjoin:
{“dni”:“AA0A”,“d”:“000D6F000BD4ED82”,
“capabilities”:“8E”,
“endpoints”:
[{“simple”:“01 0104 0102 00 07 0000 0003 0004 0005 0006 0008 0300 01 0003”,
“application”:“0E”,
“manufacturer”:“Aurora”,
“model”:“Dimmer”},
{“simple”:“02 0104 0006 00 04 0000 0003 0600 0704 01 0003”,
“application”:“0E”,
“manufacturer”:“Aurora”,
“model”:“Dimmer”},
{“simple”:“03 0104 0007 00 02 0000 0003 02 0003 0019”,
“application”:“0E”,
“manufacturer”:“Aurora”,
“model”:“Dimmer”}]}

It also shows this in the device page:
Data
model: Dimmer
application: 0E
manufacturer: Aurora
endpointId: 01

Raw Description 01 0104 0102 00 07 0000 0003 0004 0005 0006 0008 0300 01 0003

The documentation suggests that all I need to do for the device handler to automatically latch on is to add a fingerprint in the Zigbee Dimmer device handler.

I added these lines in for each endpoint in the device handler:

    fingerprint profileId: "0104", inClusters: "0000, 0003, 0004, 0005, 0006, 0008, 0300", outClusters: "0003", manufacturer: "Aurora", model: "Dimmer", deviceJoinName: "AONE.control"
    fingerprint profileId: "0104", inClusters: "0000, 0003, 0600, 0704", outClusters: "0003", manufacturer: "Aurora", model: "Dimmer", deviceJoinName: "AONE.control"
    fingerprint profileId: "0104", inClusters: "0000, 0003", outClusters: "0003, 0019", manufacturer: "Aurora", model: "Dimmer", deviceJoinName: "AONE.control"

However, on pairing the device is still detected as a Thing of Unknown type. Does anyone know what I may be doing wrong?

Cheers,
Matt

You could try using creating the Device Type Handler using the From ZigBee Device Fingerprint method described here:

http://docs.smartthings.com/en/latest/device-type-developers-guide/building-zigbee-device-handlers.html#using-the-zigbee-device-form

That will help ensure the fingerprint is created correctly. Then Save and Publish the Device Type Handler, delete your device from SmartThings and try joining it again.

1 Like

Hi Tom,

Thanks for replying. This is actually the first thing I did (since it’s so easy). After it didn’t work, I started digging deeper.

Is there any information I can provide you that will help deduce the problem?

Cheers,
Matt

You can try the following Fingerprint alone first to see if it works and later add the other endpoints:

fingerprint endpointId: “01”, profileId: “0104”, deviceId: “0102”, inClusters: “0000,0003,0004,0005,0006,0008,0300”, outClusters: “0003”, manufacturer: “Aurora”, model: “Dimmer”

Hi Rudi,

Thanks for replying, I really appreciate you trying to help the newbies out! We could be looking to certify this product as well as many others in the coming months, and getting this fingerprinting working is one of the key features to getting upper management sign off.

Unfortunately, this did not work either. What is involved in the fingerprint matching process? I’m aware that this is my first attempt at doing this so maybe there is something else that might be going wrong in the background? Eg. Do I need certain permissions in my ST account ticked? Just trying to think outside the box here because it looks like the fingerprint is correct.

Cheers,
Matt