Beginners question: fantastic button controller not working

Continuing the discussion from Sunricher ZG2833K8_EU05 driver:

I need help because I really don't know what to do even after reading the mentioned thread above.

I was confident there would be a driver for the (amazingly well build) ICZB-KPD18S-QUICK 8 button controller.

But i cannot get it to work and as a Hubitat and Zigbee/Zwave novice I don't know what steps to take to solve this issue.

If I add this device the seems to be 4 component devices but Only S1 and S2 are "working" and S3 registers as S2 ???

This is such a great device with many variants/brands, I would be so great to get this working!

Fingerprint below the images!

many thanks for any help!

Click button 'I"
dev:1042022-10-27 18:00:34.554infoZigbee parsed:[raw:catchall: 0104 0006 01 01 0040 00 3B98 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

Click button '0'
dev:1042022-10-27 18:01:18.431infoZigbee parsed:[raw:catchall: 0104 0006 01 01 0040 00 3B98 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]
---


HOLD button 'I'
dev:1042022-10-27 18:01:50.037infoZigbee parsed:[raw:catchall: 0104 0008 01 01 0040 00 3B98 01 00 0000 05 00 0032, profileId:0104, clusterId:0008, clusterInt:8, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:05, direction:00, data:[00, 32]]

RELEASE after HOLD button 'I'
dev:1042022-10-27 18:01:53.544infoZigbee parsed:[raw:catchall: 0104 0008 01 01 0040 00 3B98 01 00 0000 07 00 , profileId:0104, clusterId:0008, clusterInt:8, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:00, data:[]]
---


HOLD button '0'

dev:1042022-10-27 18:03:02.963infoZigbee parsed:[raw:catchall: 0104 0008 01 01 0040 00 3B98 01 00 0000 05 00 0132, profileId:0104, clusterId:0008, clusterInt:8, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:05, direction:00, data:[01, 32]]

RELEASE after HOLD button '0'

dev:1042022-10-27 18:03:06.066infoZigbee parsed:[raw:catchall: 0104 0008 01 01 0040 00 3B98 01 00 0000 07 00 , profileId:0104, clusterId:0008, clusterInt:8, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:00, data:[]]
---

CLICK button S1

dev:1042022-10-27 18:05:31.538infoZigbee parsed:[raw:catchall: 0104 0005 01 01 0040 00 3B98 01 00 0000 05 00 0000010000, profileId:0104, clusterId:0005, clusterInt:5, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:05, direction:00, data:[00, 00, 01, 00, 00]]

HOLD button S1 for 3 or more seconds

dev:1042022-10-27 18:06:25.154infoZigbee parsed:[raw:catchall: 0104 0005 01 01 0040 00 3B98 01 00 0000 04 00 000001, profileId:0104, clusterId:0005, clusterInt:5, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:00, data:[00, 00, 01]]

---

CLICK button S2

dev:1042022-10-27 18:07:19.281infoZigbee parsed:[raw:catchall: 0104 0005 01 01 0040 00 3B98 01 00 0000 05 00 0000020000, profileId:0104, clusterId:0005, clusterInt:5, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:05, direction:00, data:[00, 00, 02, 00, 00]]

HOLD button S2 for 3 or more seconds

dev:1042022-10-27 18:07:38.834infoZigbee parsed:[raw:catchall: 0104 0005 01 01 0040 00 3B98 01 00 0000 04 00 000002, profileId:0104, clusterId:0005, clusterInt:5, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:00, data:[00, 00, 02]]

---

CLICK button S3

dev:1042022-10-27 18:08:56.601infoZigbee parsed:[raw:catchall: 0104 0005 01 01 0040 00 3B98 01 00 0000 05 00 0000030000, profileId:0104, clusterId:0005, clusterInt:5, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:05, direction:00, data:[00, 00, 03, 00, 00]]

HOLD button S3 for 3 or more seconds

dev:1042022-10-27 18:09:19.501infoZigbee parsed:[raw:catchall: 0104 0005 01 01 0040 00 3B98 01 00 0000 04 00 000003, profileId:0104, clusterId:0005, clusterInt:5, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:00, data:[00, 00, 03]]
---

CLICK button S4

dev:1042022-10-27 18:09:31.958infoZigbee parsed:[raw:catchall: 0104 0005 01 01 0040 00 3B98 01 00 0000 05 00 0000040000, profileId:0104, clusterId:0005, clusterInt:5, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:05, direction:00, data:[00, 00, 04, 00, 00]]

HOLD button S4 for 3 or more seconds

dev:1042022-10-27 18:09:57.185infoZigbee parsed:[raw:catchall: 0104 0005 01 01 0040 00 3B98 01 00 0000 04 00 000004, profileId:0104, clusterId:0005, clusterInt:5, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:00, data:[00, 00, 04]]
---

CLICK button S5

dev:1042022-10-27 18:10:11.567infoZigbee parsed:[raw:catchall: 0104 0005 01 01 0040 00 3B98 01 00 0000 05 00 0000050000, profileId:0104, clusterId:0005, clusterInt:5, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:05, direction:00, data:[00, 00, 05, 00, 00]]

HOLD button S5 for 3 or more seconds

dev:1042022-10-27 18:10:29.898infoZigbee parsed:[raw:catchall: 0104 0005 01 01 0040 00 3B98 01 00 0000 04 00 000005, profileId:0104, clusterId:0005, clusterInt:5, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:00, data:[00, 00, 05]]
---

CLICK button S6

dev:1042022-10-27 18:10:45.125infoZigbee parsed:[raw:catchall: 0104 0005 01 01 0040 00 3B98 01 00 0000 05 00 0000060000, profileId:0104, clusterId:0005, clusterInt:5, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:05, direction:00, data:[00, 00, 06, 00, 00]]

HOLD button S6 for 3 or more seconds

dev:1042022-10-27 18:11:01.245infoZigbee parsed:[raw:catchall: 0104 0005 01 01 0040 00 3B98 01 00 0000 04 00 000006, profileId:0104, clusterId:0005, clusterInt:5, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3B98, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:00, data:[00, 00, 06]]
---

1 Like

That may have been a bad assumption. You can check List of Compatible Devices | Hubitat Documentation for supported devices.

Hopefully someone that knows zigbee protocol can help get a correct driver built. It looks like it matched up to a RGBGenie dimmer switch which it clearly isn't.

1 Like
1 Like

EDIT: device will be returned... sadly!

Is it possible to change an existing driver using the fingerprint info?

just change the driver on the device page

1 Like

Yes I did that, I tried for hour to use different drivers.

In earlier posts was a Sunricher 8 button driver mentioned but that one is removed?

But the package has been prepared for return. :pensive:
It's an amazing switch, very sturdy and well build. Much better look and feel than the Philips Hue Dimmer Switches of which I have several in use.

For the Eurpoean market there are not many such switches available which fit into the EU wall mounts.

Wait one more week if you can, before returning the device.
From the logs that you provided it shouldn't be too much difficult to make it work in HE. All the needed data (button number, pressed or held) is there.

When you changed drivers, did you click configure? Another option is to change driver to "Device" click save, then click delete all children and states, then switch back to the driver you want and click save then click configure.

1 Like

@WWJD when you assign the 'device' driver, please click on the ''Get Info' and press any of the buttons at the same time to wake up the device. I need the generated fingerprint in the logs.

@WWJD when you assign the 'device' driver, please click on the ''Get Info' and press any of the buttons at the same time to wake up the device. I need the generated fingerprint in the logs.

Also, when you HOLD a button for 3 or more seconds, is only one message generated in the logs at the time when you release the button? Or the message in the logs is generated while you still keep the button held?

1 Like

Oh that would be great...

I have 2 weeks to return the device.

@rlithgow1 I feel a bit stupid but as I said, I am so new to the (AMAZING) Hubitat platform that I don't know what the configure button does.

I will try to get you kind folks the info asked. Give me an hour... ! many thanks!

1 Like

Basically it tells the driver to get info from the device so it can properly interpret it.

1 Like

But thinking a bit more about it, would it not be better to buy the device that was mentioned before, from Robbshop?

It's the same thing.

2 Likes

Ok, will try to get the info you need ASAP

This Zigbee switch has a top row with dimming capability, the rows 2,3 and 4 are only switches

And YES when I hold the switches for 3 or more seconds, the log is generaed WHILE holding the button.

Is this the info you need?

No, the fingerprint log should look like this:

fingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0B05,1000", outClusters:"0003,0004,0005,0006,0008,0019,0300,1000", model:"ICZB-KPD18S", manufacturer:"icasa"

Did you click with the mouse on the 'Get Info' button and at the same time press a physical button on the device?

sorry, will try again

Buttons labeled S1..S6 will be mapped to HE button number 1..6. The possible states seems to be 'pushed' and 'held'.
Button "0" will be mapped to button '7', button "I" will be mapped to HE button number 8. The possible states seems to be 'pushed' and 'held' and 'released''.

1 Like

This the code while pressing a few times a button and GET INFO

Did you also see the fingerprint results from all button combinations in my opening post?

dev:1042022-10-27 20:46:39.897infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0B05,1000", outClusters:"0003,0004,0005,0006,0008,0019,0300,1000", model:"ICZB-KPD18S", manufacturer:"icasa"

dev:1042022-10-27 20:46:39.214traceZCL version:03

dev:1042022-10-27 20:46:39.212traceSoftware Build Id:2.7.6_r25

dev:1042022-10-27 20:46:39.211traceModel:ICZB-KPD18S

dev:1042022-10-27 20:46:39.209traceManufacturer:icasa

dev:1042022-10-27 20:46:39.194infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0B05,1000", outClusters:"0003,0004,0005,0006,0008,0019,0300,1000", model:"ICZB-KPD18S", manufacturer:"icasa"

dev:1042022-10-27 20:46:39.179infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0B05,1000", outClusters:"0003,0004,0005,0006,0008,0019,0300,1000", model:"ICZB-KPD18S", manufacturer:"icasa"

dev:1042022-10-27 20:46:39.100infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0B05,1000", outClusters:"0003,0004,0005,0006,0008,0019,0300,1000", model:"ICZB-KPD18S", manufacturer:"icasa"

dev:1042022-10-27 20:46:39.060infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0B05,1000", outClusters:"0003,0004,0005,0006,0008,0019,0300,1000", model:"ICZB-KPD18S", manufacturer:"icasa"

dev:1042022-10-27 20:46:38.121debuggetting info for unknown Zigbee device...

1 Like