Installed device not being found(?) in fingerprint data

I installed a couple of WD500Z-1 dimmer switches. Before doing so I found a driver on ST that had a fingerprint for a sister dimmer from the one installed.
I added the WD500Z-1 fingerprint data and loaded it into HE ( I also made the porting changes required)

When The WD500Z-1 is discovered it is identified as "other". When I select the above ST in "TYPE" it works fine.

Is my assumption that adding the new dimmer data to the drive was all that is needed?

BTW why is the device list data in decimal for type, ID and MFG, but the in clusters is in hex?

    metadata {
	definition(name: "Z-Wave Dimmer Switch Generic", namespace: "hubitat", author: "SmartThingsMod", ocfDeviceType: "oic.d.light", runLocally: true, minHubCoreVersion: '000.019.00012', executeCommandsLocally: true) {
		capability "Switch Level"
		capability "Actuator"
		capability "Health Check"
		capability "Switch"
		capability "Polling"
		capability "Refresh"
		capability "Sensor"
		capability "Light"

		fingerprint inClusters: "0x26", deviceJoinName: "Z-Wave Dimmer"
		fingerprint mfr: "001D", prod: "1902", deviceJoinName: "Z-Wave Dimmer"
		fingerprint mfr: "001D", prod: "3301", model: "0001", deviceJoinName: "Leviton Dimmer Switch"
		fingerprint mfr: "001D", prod: "3201", model: "0001", deviceJoinName: "Leviton Dimmer Switch"
		fingerprint mfr: "001D", prod: "1B03", model: "0334", deviceJoinName: "Leviton Universal Dimmer"
		fingerprint mfr: "011A", prod: "0102", model: "0201", deviceJoinName: "Enerwave In-Wall Dimmer"
		fingerprint mfr: "001D", prod: "1001", model: "0334", deviceJoinName: "Leviton 3-Speed Fan Controller"
		fingerprint mfr: "001D", prod: "0602", model: "0334", deviceJoinName: "Leviton Magnetic Low Voltage Dimmer"
		fingerprint mfr: "001D", prod: "0401", model: "0334", deviceJoinName: "Leviton 600W Incandescent Dimmer"
		fingerprint mfr: "0111", prod: "8200", model: "0200", deviceJoinName: "Remotec Technology Plug-In Dimmer"
		fingerprint mfr: "1104", prod: "001D", model: "0501", deviceJoinName: "Leviton 1000W Incandescant Dimmer"
		fingerprint mfr: "0063", prod: "4944", model: "3034", deviceJoinName: "GE In-Wall Smart Fan Control"
		fingerprint mfr: "0063", prod: "4944", model: "3131", deviceJoinName: "GE In-Wall Smart Fan Control"
		fingerprint mfr: "001A", prod: "4449", model: "0101", deviceJoinName: "Eaton RF Master Dimmer"
		fingerprint mfr: "001A", prod: "4449", model: "0003", deviceJoinName: "Eaton RF Dimming Plug-In Module"
		fingerprint mfr: "0086", prod: "0103", model: "0063", deviceJoinName: "Aeotec Smart Dimmer 6"
		fingerprint mfr: "014F", prod: "5744", model: "3530", deviceJoinName: "GoControl In-Wall Dimmer"
		fingerprint mfr: "014F", prod: "4457", model: "3034", deviceJoinName: "GoControl In-Wall Dimmer"		// added for our WD500Z-1 not sure if it will work
	}
}	// --- end of metadata ---

WD500Z-1 Dimmer after installation

deviceType: 17495 <- decmial
inClusters: 0x26,0x2B,0x2C,0x27,0x73,0x70,0x86,0x72
deviceId: 12340 <- decmial
manufacturer: 335 <- decmial

HE currently requires the inClusters listed in the pairing process to identify the driver, this property needs to be included in the fingerprint line. The driver you posted uses the newer msr fingerprint style that we don't support at this time.
The other pairing data elements are integers as that's how they are used internally.
All the fingerprint elements are hex, these are not used for anything other than initial device identification.

I understand,

Thanks
John

@mike.maxwell,

Mike, for my learning (and likely others) can you point me to a simple device driver that follows what you would consider "best practices" for Hubitat?

Thanks

John

Hello.
Has your WD500Z-1 been working well? Any suggestion prior to installing the one I have on hand? Thanks.

I have 3 of the WD500Z-1, I use the Generic zwave smart dimmer driver. Everything is fine except the indicator light which I have set to be on when the light is off, keeps changing to On when light is on.
Not a real problem for me but annoying.

When your pair it with Hubitat, after pushing the dimmer paddle, wait some 1 minute or so before thinking it is not connecting.

John

1 Like

I'm guessing this isn't of use to you anymore John, but I see that Mike missed this question or maybe you got the answer in another thread. For anyone looking for examples, they are here.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.