Tuya / Moes 1/2/3 gang dimmer

[user1955]

Hallo my smart friends

I recently purchased a 1 and 2 gang dimmer from Ali Express. See screenshot of device:

Also the link: https://nl.aliexpress.com/item/1005003572427505.html?spm=a2g0o.productlist.0.0.44725093RPGt3R&algo_pvid=485a33c1-96c7-4184-b0e8-e561586dc25a&algo_exp_id=485a33c1-96c7-4184-b0e8-e561586dc25a-9&pdp_ext_f={"sku_id"%3A"12000026333874688"}&pdp_npi=2%40dis!EUR!46.67!23.33!!!!!%402100bddb16678188978486325e945e!12000026333874688!sea&curPageLogUid=PTrmNQnT9ixi

I added the device on HE and it gets automaticly the driver ''Moes Zigbee wall switch 1/2/3-gang'' driver. And HE also creat 4 child devices for this device. Because it didn't work with these driver l changed it to a custom ''Oz smart zigbee switch'' driver, but the 4 child devices stays there wich l can't control or delete. The problem with the ''Oz smart zigbee switch'' driver is that it don't creat new child device's in device's overview but it only creats a extra button in the device page self:

What driver is best to use for this 2-gang dimmer, so l can control the child device too. Now if l make a rule l only can select the head device wich only turns on and off the 1e of the 2 dimmers:

Also im missing futures like turn on and off the backlight.

If other sceenshots are need it let me know.

Gr Tayfun

[kkossev]

Every Zigbee device is identified by its Manufacturer and Model values, as shown on the device web page ‘Data’ section. Hubitat hub additionally uses the inClusters list in the driver selection process. All this information is called ‘Fingerprint’

Please switch manually to HE inbuilt driver named ‘device’. Then click on the’Get Info’ button, and select-copy-paste here the log lines that contain the device fingerprint. - for both the 1-gang and 2-gangs devices.

[user1955]

Hello @kkossev,

1-way

2-way

[kkossev]

Sorry @user1955 , but all the screenshots and the pictures are not searchable.

Probably I was not very clear, I need the text to be copied and pasted :

@kkossev

and select-copy-paste here the log lines that contain the device fingerprint

Thanks.

[user1955]

Oh sorry.

1-way:
dev:1442022-11-07 18:35:50.641infofingerprint profileId:"0104", endpointId:"01", inClusters:"0004,0005,EF00,0000", outClusters:"0019,000A", model:"TS0601", manufacturer:"_TZE200_ip2akl4w"

dev:1442022-11-07 18:35:50.550traceZCL version:03

dev:1442022-11-07 18:35:50.525traceSoftware Build Id:unknown

dev:1442022-11-07 18:35:50.524traceModel:TS0601

dev:1442022-11-07 18:35:50.523traceManufacturer:_TZE200_ip2akl4w

dev:1442022-11-07 18:35:50.471debuggetting info for unknown Zigbee device...

dev:1442022-11-07 18:35:48.496infoZigbee parsed:[raw:catchall: 0000 0013 00 00 0040 00 95E6 00 00 0000 00 00 09E6951C7FF99E9638C1A48E, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:95E6, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[09, E6, 95, 1C, 7F, F9, 9E, 96, 38, C1, A4, 8E]]

dev:1442022-11-07 18:35:48.443debugconfigure() called...

2-way
dev:1342022-11-07 18:31:23.485infoZigbee parsed:[raw:44DC0100001801002040E2FF2020E4FF2000, dni:44DC, endpoint:01, cluster:0000, size:18, attrId:0001, encoding:20, command:0A, value:40, clusterInt:0, attrInt:1, additionalAttrs:[[value:20, encoding:20, attrId:FFE2, consumedBytes:4, attrInt:65506], [value:00, encoding:20, attrId:FFE4, consumedBytes:4, attrInt:65508]]]

dev:1342022-11-07 18:28:36.556infofingerprint profileId:"0104", endpointId:"01", inClusters:"0004,0005,EF00,0000", outClusters:"0019,000A", model:"TS0601", manufacturer:"_TZE200_fjjbhx9d"

dev:1342022-11-07 18:28:36.456traceZCL version:03

dev:1342022-11-07 18:28:36.424traceSoftware Build Id:unknown

dev:1342022-11-07 18:28:36.423traceModel:TS0601

dev:1342022-11-07 18:28:36.422traceManufacturer:_TZE200_fjjbhx9d

dev:1342022-11-07 18:28:36.366debuggetting info for unknown Zigbee device...

[kkossev]

You can try this version of the "Tuya Zigbee dimmer module" driver : https://raw.githubusercontent.com/kkossev/hubitat-matt-hammond-fork/master/drivers/tuya-zigbee-dimmer-module.groovy

My recommendation is first to delete the device from the HE web page, then pair it again close to HE hub. This driver should be selected automatically during the pairing process.

[user1955]

1-way first add info:

It does not take the driver you say. Again the moes switch. Then l change it to the driver you say.

2-way first add info:

Same for this one. I change it to the driver you say. This driver doesn't work, I already tried this driver l think

[kkossev]

@user1955

, I already tried this driver l think

No, I added these two new devices fingerprints 30 minutes ago.
Please make sure the "Tuya Zigbee dimmer module" is updated and you see these lines on the first page of the code:

[user1955]

The dimmer works only the first of the 2 dimmer. But the status of the switch doenst work for the first dimmer. Also the child device doesn't work:

Also it gives errors in logging:

And the 1-way does work only as on and off. The dimmer function doesn't work.

[kkossev]

OK, let's talk only for the 1-gang dimmer first.
It should have NO child devices. Only one main device.

Switch the Debug logging on and click on Configure button. Then click on On, Off and SetLevel buttons. I will need the debug logs from these actions.

Did you pair the 1-way dimmer close to the hub, or you paired it on it's final place?

[user1955]

Oke l will do that only for the 1-way. Final place. thats 6m from the hub.

[user1955]

My log is going crazy right now. There are so much events that the HE is hanging or reacting very slow if l go in logging page.

[kkossev]

Try to get to the device page, then disable this device

After disabling, reboot the hub

[user1955]

Did it. doing the same. When l put the driver you say and enable debug this is what comes in the logging:

And events:

After l open logging page it keeps hanging. i can open new webpage then it works again.

[kkossev]

Don't use this driver with this device anymore, until we find out why it behaves like this.
Better delete the 2 dimmers first, then don't use or even delete the driver.

Until I find out what is wrong, don't use it.

[user1955]

[kkossev]

I see where the problem is, but it is not my code so will need more time to secure it and ensure such endless loops will never happen again... Sorry about that.

Until there is a fix, don't use this driver. I don't know what is the core reason for this bug to show up (technically, the operation to delete an existing child device failed and the current code was trying to delete it endlessly).

[user1955]

No problem lol you trying to help I will figure out to calmdown my HE. he keeps going

[user3035]

Hello,
I´m trying to use the code in the link you send with drivers Lifud dimming zigbee, i add the footprint of my device and now i can turn it of and on but i cant use the dimming. can you help?

dev:132022-11-09 02:40:15.111 PMinfoSwitch 01 is off
dev:132022-11-09 02:40:15.108 PMdebugcatchall clusterId=EF00 command=02 data=[00, 35, 01, 01, 00, 01, 00]
dev:132022-11-09 02:40:15.106 PMdebugReceived parsed: [raw:catchall: 0104 EF00 01 01 0040 00 841C 01 00 0000 02 01 00350101000100, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:841C, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 35, 01, 01, 00, 01, 00]]
dev:132022-11-09 02:40:15.104 PMdebugReceived raw: catchall: 0104 EF00 01 01 0040 00 841C 01 00 0000 02 01 00350101000100
dev:132022-11-09 02:40:15.067 PMdebugTuya command 0x0B data=[00, 00]
dev:132022-11-09 02:40:15.066 PMdebugcatchall clusterId=EF00 command=0B data=[00, 00]
dev:132022-11-09 02:40:15.063 PMdebugReceived parsed: [raw:catchall: 0104 EF00 01 01 0040 00 841C 00 00 0000 0B 01 0000, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:841C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]
dev:132022-11-09 02:40:15.061 PMdebugReceived raw: catchall: 0104 EF00 01 01 0040 00 841C 00 00 0000 0B 01 0000
dev:132022-11-09 02:40:15.005 PMdebuglifud750ma sendTuyaCommand = [he cmd 0x841C 0x01 0xEF00 0x00 {C0AA0101000100}, delay 2000]
dev:132022-11-09 02:40:15.002 PMdebuglifud750ma sending cmdSwitch command=01 value=0 (00)
dev:132022-11-09 02:40:15.000 PMdebugcmdSwitch: childDni=841C-01 onOff=0
dev:132022-11-09 02:40:14.999 PMtracechildDni = 841C-01
dev:132022-11-09 02:40:14.998 PMtraceendpointIdToChildDni 01 = 841C - 01
dev:132022-11-09 02:39:54.539 PMinfoSwitch 01 is on
dev:132022-11-09 02:39:54.535 PMdebugcatchall clusterId=EF00 command=02 data=[00, 34, 01, 01, 00, 01, 01]
dev:132022-11-09 02:39:54.532 PMdebugReceived parsed: [raw:catchall: 0104 EF00 01 01 0040 00 841C 01 00 0000 02 01 00340101000101, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:841C, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 34, 01, 01, 00, 01, 01]]
dev:132022-11-09 02:39:54.528 PMdebugReceived raw: catchall: 0104 EF00 01 01 0040 00 841C 01 00 0000 02 01 00340101000101
dev:132022-11-09 02:39:54.493 PMdebugTuya command 0x0B data=[00, 00]
dev:132022-11-09 02:39:54.492 PMdebugcatchall clusterId=EF00 command=0B data=[00, 00]
dev:132022-11-09 02:39:54.489 PMdebugReceived parsed: [raw:catchall: 0104 EF00 01 01 0040 00 841C 00 00 0000 0B 01 0000, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:841C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]
dev:132022-11-09 02:39:54.482 PMdebugReceived raw: catchall: 0104 EF00 01 01 0040 00 841C 00 00 0000 0B 01 0000
dev:132022-11-09 02:39:54.411 PMdebuglifud750ma sendTuyaCommand = [he cmd 0x841C 0x01 0xEF00 0x00 {128E0101000101}, delay 2000]
dev:132022-11-09 02:39:54.408 PMdebuglifud750ma sending cmdSwitch command=01 value=1 (01)
dev:132022-11-09 02:39:54.406 PMdebugcmdSwitch: childDni=841C-01 onOff=1
dev:132022-11-09 02:39:54.404 PMtracechildDni = 841C-01
dev:132022-11-09 02:39:54.403 PMtraceendpointIdToChildDni 01 = 841C - 01
dev:132022-11-09 02:38:44.727 PMinfoSwitch 01 is off
dev:132022-11-09 02:38:44.724 PMdebugcatchall clusterId=EF00 command=02 data=[00, 33, 01, 01, 00, 01, 00]
dev:132022-11-09 02:38:44.721 PMdebugReceived parsed: [raw:catchall: 0104 EF00 01 01 0040 00 841C 01 00 0000 02 01 00330101000100, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:841C, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 33, 01, 01, 00, 01, 00]]
dev:132022-11-09 02:38:44.719 PMdebugReceived raw: catchall: 0104 EF00 01 01 0040 00 841C 01 00 0000 02 01 00330101000100
dev:132022-11-09 02:38:44.680 PMdebugTuya command 0x0B data=[00, 00]
dev:132022-11-09 02:38:44.679 PMdebugcatchall clusterId=EF00 command=0B data=[00, 00]
dev:132022-11-09 02:38:44.676 PMdebugReceived parsed: [raw:catchall: 0104 EF00 01 01 0040 00 841C 00 00 0000 0B 01 0000, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:841C, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]
dev:132022-11-09 02:38:44.674 PMdebugReceived raw: catchall: 0104 EF00 01 01 0040 00 841C 00 00 0000 0B 01 0000
dev:132022-11-09 02:38:44.622 PMdebuglifud750ma sendTuyaCommand = [he cmd 0x841C 0x01 0xEF00 0x00 {89BC0101000100}, delay 2000]
dev:132022-11-09 02:38:44.618 PMdebuglifud750ma sending cmdSwitch command=01 value=0 (00)
dev:132022-11-09 02:38:44.616 PMdebugcmdSwitch: childDni=841C-01 onOff=0
dev:132022-11-09 02:38:44.614 PMtracechildDni = 841C-01
dev:132022-11-09 02:38:44.613 PMtraceendpointIdToChildDni 01 = 841C - 01
dev:132022-11-09 02:38:43.486 PMinfoSwitch 01 is on

[user1955]

Hello @user3035,

What type of device are you using. Maybe l have a driver for you that would work.