How to control which device handler a device connects to

I am testing a new ZigBee device handler but even though its published, for me, the device connects to another ZigBee device handler, that is also home built.

The new device handler doesn’t show up in the app after it has been installed on IDE.

What am I doing wrong?

My understanding is that the device type that it picks up during pairing is based on a fingerprint of the device. Maybe your device types have the same fingerprint? I dunno, I’m not totally clear on how that works.

You can always change the device type in the IDE after you pair the device. Just go to the Devices link, click on the device and edit it, then change the device type in the dropdown.

Yep :smile:

Thanks for the replies.

tamaracks gave me the idea so I connected the new thing and changed it, in IDE, to the device handler I wanted.

Here is the comparison of the raw description from my Leviton LCM (old device handler) and the new, (Orbit Drip valve).

Hot water Heater connected as ZigBee Load Control Switch
Raw Description (from IDE) 09 0104 0002 70 03 0000 0003 0006 01 000A
fingerprint profileId: “0104”, inClusters: “0000,0003,0006”, outClusters: “000A”

Compared to Drip Valve
Raw Description (from IDE) 01 0104 0002 00 06 0000 0001 0003 0020 0006 0201 02 000A 0019
fingerprint profileId: “0104”, inClusters: “0000,0001,0003,0004,0005,0020,0006,0B02”, outClusters: “0003”

The problem is: The Drip valve will connect and can be turned on and off, as expected; but my app shows a “not yet configured” alert to connect to the ZigBee Load Control Switch. It still tries to connect to the old device handler.

Is there a way to lock the ZigBee Load Control Switch so there can be no further connections, or how do I refine the fingerprint to do this?


The “Hot Water Heater” device is connected via the Zigbee Load Control Switch (LCM), in “My Device Types”.

The “Orbit Drip Valve”, which had connected as a “LCM” “my device type” was changed in IDE to “ZigBee Orbit Drip Valve” in “my device types”.

The problem intensifies this morning when the LCM kicked off to turn on my hot water heater, which caused 37 new devices to connect as “ZigBee Load Control Switch”. (I have reduced that to 7 for manageability…) In other words, new devices were connected having no relation to the Orbit Drip Valve device or the Hot water Heater device; they connected merely because I have a LCM in “my Devices.”

It seems to me the problem is the profile of the LCM. No?

Profile of LCM with Raw description of “Hot Water Heater” device from IDE:
profileId:‘0104’ in:‘0000,0003,0006’ out:'000A’
Raw Description: 09 0104 0002 70 03 0000 0003 0006 01 000A

Profile of ZigBee Orbit Drip Valve with the Raw Description
profileId:‘0104’ in:‘0000,0001,0003,0004,0005,0020,0006,0B02’ out:'0003’
Raw Description: 01 0104 0002 00 06 0000 0001 0003 0020 0006 0201 02 000A 0019