I’ve developed my own ZigBee HA dimmable light and joined it to my SmartThings hub. The device successfully joins the network, but the hub does not identify it as a device type. I can manually enter the type as “ZigBee Dimmer” under “My Devices”, but I don’t understand why the hub doesn’t automatically recognize this as a dimmer.
My device has the following clusters:
inClusters: 0000 0003 0004 0005 0006 0008 0300 0B05
Shouldn’t this match the first fingerprint in the “ZigBee Dimmer” device handler? Or am I misunderstanding how the matching happens? The first fingerprint for the ZigBee Dimmer is:
fingerprint profileId: “0104”, inClusters: “0000, 0003, 0004, 0005, 0006, 0008”
Looks like it would match more clusters as a color light since you have 0300, but the 0B05 might be throwing it off. Does your device identify as HA profile 0104? I think it looks for the most comprehensive match first (including manufacturer and model), but needs to at least fully match the supported clusters. There are also a lot of zigbee dimmer deviceTypes (GE Link, Cree, Osram, etc…), so maybe it couldn’t narrow it down enough.
@tpmanley any insight here?
Is it showing up as a Thing or a different type? I’m not positive but I think the fingerprint would actually match the first fingerprint in zigbee-white-color-temperature-bulb
fingerprint profileId: "0104", inClusters: "0000, 0003, 0004, 0005, 0006, 0008, 0300", outClusters: "0019"
In order to make sure it uses ZigBee Dimmer you could try using the new ‘From ZigBee Device Form’ available here: https://graph.api.smartthings.com/ide/device/create. We’re working on improving the documentation for this new feature, but basically it makes it easy to add a new fingerprint for your device to an existing generic ZigBee device handler. If you enter the correct set of in and out clusters, manufacturer and model for your device then it should fingerprint as a ZigBee Dimmer.
Thanks for the quick replies! The device does identify as HA profile 104 and shows up as a Thing. Using the “From ZigBee Device Form” feature does work as expected.
I guess I was just wondering why the hub doesn’t identify it as anything. I would expect one of the fingerprints to match by default. But I don’t know enough about how the fingerprint matching works. Maybe without a manufacturer and model, the clusters have to match exactly.
The fingerprinting is a bit complicated. Basically if multiple device handlers match your device based on the simple descriptor (profile, in/out clusters), and any of those fingerprints also contains manufacturer and model then you need to have a fingerprint that specifies your device’s manufacturer and model too. Otherwise it will fingerprint as a “Thing”.
We’re looking at changing this so you don’t need to add a fingerprint with the manufacturer and model in this scenario. I think this will be a much better experience for developers and users working with new devices.