Tuya / Moes 1/2/3 gang dimmer

user3035 · November 9, 2022, 4:56pm

Lifud
Model: LF-AAZ030-0750-42

user1955 · November 9, 2022, 5:56pm

No that model l don't know sorry

kkossev · November 9, 2022, 7:10pm

Can you post the device fingerprint?
Also, a link to the site where it was purchased will be useful.

What is in the logs when you change the brightness from the device local controls?

user3035 · November 10, 2022, 9:51am

dev:122022-11-10 09:44:02.052 AMdebuglifud1050ma sendTuyaCommand = [he cmd 0xC87D 0x01 0xEF00 0x00 {28EB0202000400000226}, delay 2000]
dev:122022-11-10 09:44:02.049 AMdebuglifud1050ma sending cmdSetLevel command=02 value=550 (00000226)
dev:122022-11-10 09:44:02.047 AMdebugcmdSetLevel: child=lifud1050ma childDni=C87D-01 value=55 duration=10
dev:122022-11-10 09:44:02.046 AMtraceendpointIdToIndex i=01
dev:122022-11-10 09:44:02.045 AMtracechildDni = C87D-01
dev:122022-11-10 09:44:02.044 AMtraceendpointIdToChildDni 01 = C87D - 01
dev:122022-11-10 09:44:02.042 AMdebuglevel=50 reScaled=55
dev:122022-11-10 09:43:53.912 AMinfoSwitch 01 is off
dev:122022-11-10 09:43:53.911 AMdebugcatchall clusterId=EF00 command=02 data=[00, 07, 01, 01, 00, 01, 00]
dev:122022-11-10 09:43:53.909 AMdebugReceived parsed: [raw:catchall: 0104 EF00 01 01 0040 00 C87D 01 00 0000 02 01 00070101000100, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:C87D, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 07, 01, 01, 00, 01, 00]]
dev:122022-11-10 09:43:53.907 AMdebugReceived raw: catchall: 0104 EF00 01 01 0040 00 C87D 01 00 0000 02 01 00070101000100
dev:122022-11-10 09:43:53.871 AMdebugTuya command 0x0B data=[00, 00]
dev:122022-11-10 09:43:53.870 AMdebugcatchall clusterId=EF00 command=0B data=[00, 00]
dev:122022-11-10 09:43:53.868 AMdebugReceived parsed: [raw:catchall: 0104 EF00 01 01 0040 00 C87D 00 00 0000 0B 01 0000, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:C87D, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]
dev:122022-11-10 09:43:53.866 AMdebugReceived raw: catchall: 0104 EF00 01 01 0040 00 C87D 00 00 0000 0B 01 0000
dev:122022-11-10 09:43:53.819 AMdebuglifud1050ma sendTuyaCommand = [he cmd 0xC87D 0x01 0xEF00 0x00 {17AB0101000100}, delay 2000]
dev:122022-11-10 09:43:53.816 AMdebuglifud1050ma sending cmdSwitch command=01 value=0 (00)
dev:12

user3035 · November 10, 2022, 10:05am

anufacturer:	_TZE200_drs6j6m5
Endpoint 01 application:	44
Endpoint 01 endpointId:	01
Endpoint 01 idAsInt:	1
Endpoint 01 inClusters:	0004,0005,EF00,0000
Endpoint 01 initialized:	true
Endpoint 01 manufacturer:	_TZE200_drs6j6m5
Endpoint 01 model:	TS0601
Endpoint 01 outClusters:	0019,000A
Endpoint 01 profileId:	0104
Endpoint 01 stage:	4
Endpoint F2 application:	unknown
Endpoint F2 endpointId:	F2
Endpoint F2 idAsInt:	242
Endpoint F2 initialized:	true
Endpoint F2 manufacturer:	unknown
Endpoint F2 model:	unknown
Endpoint F2 outClusters:	0021
Endpoint F2 profileId:	A1E0
Endpoint F2 stage:	4

kkossev · November 10, 2022, 4:50pm

Thanks. Is it a single-gang dimmer?
I can't find much information for this device, can you post a link to the site where it was purchased?

user3035 · November 10, 2022, 5:19pm

yes is single-gang dimmer.
i don´t understand but i cant post a link, do you now why?
Thanks

kkossev · November 10, 2022, 5:49pm

Try joining the ‘owners’ group, then posting links will be unlocked

kkossev · November 11, 2022, 2:25pm

@user1955 I have updated in the driver version ver 0.2.7 timeStamp "2022/11/11 4:10 PM" the code responsible for the deletion of any existing child devices and the creation of new child devices. It is now secured so that it does not go in a cycle in exceptional cases when something goes wrong with the child devices deletion.

So when you have a chance, please update to the latest version: https://raw.githubusercontent.com/kkossev/hubitat-matt-hammond-fork/development/drivers/tuya-zigbee-dimmer-module.groovy

Then DELETE your dimmer primary device from HE, and pair it again.

kkossev · November 11, 2022, 2:27pm

@user3035 your device _TZE200_drs6j6m5 is added in the same driver version linked above, you can give it a try.

user1955 · November 13, 2022, 10:24am

Hello @kkossev,

I did try it and the result is:
I can turn on and off the dimmer, but can't set level of the dimmer. This is log result after re-adding the device and send some commands:
dev:2352022-11-13 11:21:49.738errorjava.lang.NullPointerException: Cannot invoke method multiply() on null object on line 935 (method parse)

dev:2352022-11-13 11:21:43.722errorjava.lang.NullPointerException: Cannot invoke method multiply() on null object on line 922 (method setLevel)

dev:2352022-11-13 11:21:40.512errorjava.lang.NullPointerException: Cannot invoke method multiply() on null object on line 922 (method setLevel)

dev:2352022-11-13 11:21:37.186errorjava.lang.NullPointerException: Cannot invoke method multiply() on null object on line 922 (method setLevel)

dev:2352022-11-13 11:21:36.608errorjava.lang.NullPointerException: Cannot invoke method multiply() on null object on line 922 (method setLevel)

dev:2352022-11-13 11:21:34.534errorjava.lang.NullPointerException: Cannot invoke method multiply() on null object on line 922 (method setLevel)

dev:2352022-11-13 11:21:31.882errorjava.lang.NullPointerException: Cannot invoke method multiply() on null object on line 935 (method parse)

dev:2352022-11-13 11:21:24.099errorjava.lang.NullPointerException: Cannot invoke method multiply() on null object on line 935 (method parse)

dev:2352022-11-13 11:20:59.078errorjava.lang.NullPointerException: Cannot invoke method multiply() on null object on line 922 (method setLevel)

dev:2352022-11-13 11:20:51.829errorjava.lang.NullPointerException: Cannot invoke method multiply() on null object on line 922 (method setLevel)

dev:2352022-11-13 11:20:31.246errorjava.lang.NullPointerException: Cannot invoke method multiply() on null object on line 935 (method parse)

dev:2352022-11-13 11:19:43.619debug[raw:catchall: 0104 EF00 01 01 0040 00 C1E3 01 00 0000 24 01 032A, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:C1E3, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[03, 2A]]

dev:2352022-11-13 11:19:39.804debug[raw:catchall: 0104 EF00 01 01 0040 00 C1E3 01 00 0000 01 01 00C80E04000100, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:C1E3, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, C8, 0E, 04, 00, 01, 00]]

dev:2352022-11-13 11:19:39.751debug[raw:catchall: 0104 EF00 01 01 0040 00 C1E3 01 00 0000 01 01 00C71504000101, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:C1E3, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, C7, 15, 04, 00, 01, 01]]

dev:2352022-11-13 11:19:39.701debug[raw:catchall: 0104 EF00 01 01 0040 00 C1E3 01 00 0000 01 01 00C60404000100, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:C1E3, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, C6, 04, 04, 00, 01, 00]]

dev:2352022-11-13 11:19:39.659debug[raw:catchall: 0104 EF00 01 01 0040 00 C1E3 01 00 0000 01 01 00C50602000400000000, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:C1E3, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, C5, 06, 02, 00, 04, 00, 00, 00, 00]]

dev:2352022-11-13 11:19:39.598debug[raw:catchall: 0104 EF00 01 01 0040 00 C1E3 01 00 0000 01 01 00C40302000400000000, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:C1E3, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, C4, 03, 02, 00, 04, 00, 00, 00, 00]]

dev:2352022-11-13 11:19:39.549debug[raw:catchall: 0104 EF00 01 01 0040 00 C1E3 01 00 0000 01 01 00C305020004000003E8, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:C1E3, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, C3, 05, 02, 00, 04, 00, 00, 03, E8]]

dev:2352022-11-13 11:19:39.501debug[raw:catchall: 0104 EF00 01 01 0040 00 C1E3 01 00 0000 01 01 00C202020004000003E8, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:C1E3, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, C2, 02, 02, 00, 04, 00, 00, 03, E8]]

dev:2352022-11-13 11:19:39.480debugParent Switch ON

dev:2352022-11-13 11:19:39.460debug[raw:catchall: 0104 EF00 01 01 0040 00 C1E3 01 00 0000 01 01 00C10101000101, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:C1E3, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, C1, 01, 01, 00, 01, 01]]

dev:2352022-11-13 11:19:36.194infoRefreshing...

dev:2352022-11-13 11:19:36.159errorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 83 (method parse)

dev:2352022-11-13 11:19:36.153debug[raw:C1E301EF000A00002000, dni:C1E3, endpoint:01, cluster:EF00, size:0A, attrId:0000, encoding:20, command:01, value:00, clusterInt:61184, attrInt:0]

dev:2352022-11-13 11:19:36.106debug{executed} 0xC1E3 0x01 0xEF00 0x00

dev:2352022-11-13 11:19:36.103debugcomponent refresh 235-04 Moes ZigBee Wall Switch 1/2/3-Gang EP04

dev:2352022-11-13 11:19:36.094errorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 83 (method parse)

dev:2352022-11-13 11:19:36.089debug[raw:C1E301EF000A00002000, dni:C1E3, endpoint:01, cluster:EF00, size:0A, attrId:0000, encoding:20, command:01, value:00, clusterInt:61184, attrInt:0]

dev:2352022-11-13 11:19:36.059errorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 83 (method parse)

dev:2352022-11-13 11:19:36.054infoCreating device 235-04

dev:2352022-11-13 11:19:36.050debug[raw:C1E301EF000A00002000, dni:C1E3, endpoint:01, cluster:EF00, size:0A, attrId:0000, encoding:20, command:01, value:00, clusterInt:61184, attrInt:0]

dev:2352022-11-13 11:19:36.050debug{executed} 0xC1E3 0x01 0xEF00 0x00

dev:2352022-11-13 11:19:36.047debugcomponent refresh 235-03 Moes ZigBee Wall Switch 1/2/3-Gang EP03

dev:2352022-11-13 11:19:36.015errorjava.lang.NullPointerException: Cannot invoke method getAt() on null object on line 83 (method parse)

dev:2352022-11-13 11:19:35.998infoCreating device 235-03

dev:2352022-11-13 11:19:35.997debug[raw:C1E301EF000A00002000, dni:C1E3, endpoint:01, cluster:EF00, size:0A, attrId:0000, encoding:20, command:01, value:00, clusterInt:61184, attrInt:0]

dev:2352022-11-13 11:19:35.995debug{executed} 0xC1E3 0x01 0xEF00 0x00

dev:2352022-11-13 11:19:35.992debugcomponent refresh 235-02 Moes ZigBee Wall Switch 1/2/3-Gang EP02

dev:2352022-11-13 11:19:35.938infoCreating device 235-02

dev:2352022-11-13 11:19:35.934debug{executed} 0xC1E3 0x01 0xEF00 0x00

dev:2352022-11-13 11:19:35.930debugcomponent refresh 235-01 Moes ZigBee Wall Switch 1/2/3-Gang EP01

dev:2352022-11-13 11:19:35.817infoCreating device 235-01

dev:2352022-11-13 11:19:35.813debugParent createChildDevices

dev:2352022-11-13 11:19:35.812infomodel: _TZE200_ip2akl4w buttons: 4

dev:2352022-11-13 11:19:35.808debugParent deleteChildren

dev:2352022-11-13 11:19:35.807debugParent setupChildDevices

dev:2352022-11-13 11:19:35.806warnDebug logging will be automatically disabled after 30 minutes!

dev:2352022-11-13 11:19:35.805infoInstalling

Also it didn't select automaticly this driver again. it selects a diffents driver.

kkossev · November 13, 2022, 12:24pm

@user1955 seems like you have some strange mix of drivers or modifications...

The debug logs above are not from the "Tuya Zigbee dimmer module" driver, but from Martin's "Moes ZigBee Wall Switch 1/2/3-Gang" driver, which is for TS0601 switches, while your device is a dimmer.

If you open the "Moes ZigBee Wall Switch 1/2/3-Gang" driver in HE, does it look like this?

If you have ever added the fingerprint for your _TZE200_ip2akl4w single-gang dimmer device in this driver for tests, you must delete the line containing the fingerprint and save the driver again.

The first thing to do is to make sure that the "Tuya Zigbee dimmer module" version "0.2.7" timeStamp "2022/11/11 4:10 PM" is automatically selected during the ZIgbee pairing of your device _TZE200_ip2akl4w. All the errors in the logs are result from the fact that the correct driver is not selected during the pairing.

Second question: have you ever used HPM (Hubitat Package Manager) app for installing the "Tuya Zigbee dimmer module" driver or you have always installed it manually?

user1955 · November 13, 2022, 5:44pm

Hi @kkossev,

This happens because when l re-add the dimmer it automaticly select the driver "Moes ZigBee Wall Switch 1/2/3-Gang" then l change it manualy too '' Tuya Zigbee dimmer module ''.

i never add things in drivers my-self. And l add drivers by copy past and sometimes from url.

I can test it again if you want.

Gr Tayfun

kkossev · November 13, 2022, 5:47pm

OK, can you make a screenshot of the first screen of the "Moes ZigBee Wall Switch 1/2/3-Gang" driver - same as my screenshot in the previous post?

user1955 · November 13, 2022, 5:56pm

kkossev · November 13, 2022, 6:10pm

Thanks. Now let's check the "Tuya Zigbee Dimmer module" driver.

First, make sure you have only one instance of this driver (I have seen cases when due to unknown reasons, there may be more than once instance of one and the same driver.).
Press Ctrl-F on the drivers page and enter "Tuya Zigbee Dimmer" in the search box.
There should be only one driver found :

Then, go to the Tuya Zigbee dimmer module" driver and check whether the text circled in green is the same as on my screenshot:

user1955 · November 13, 2022, 6:15pm

oke

kkossev · November 13, 2022, 6:55pm

Everything seems OK... Did you search (using Control-F) on the drivers page for a duplicated driver with the same name? ( like in the first picture in my previous post )

I have two more ideas remaining:

if you do not have any devices that use the "Moes ZigBee Wall Switch 1/2/3-Gang" driver, you can delete the driver from your hub and you can check again whether the correct driver driver will be automatically selected.

Do you have any Zigbee switches that youse this driver?

I can add a hardcoded fingerprint of _TZE200_ip2akl4w dimmer in the Tuya Zigbee dimmer module'' driver, and you can try again. This driver uses a neat and not standard way of dynamically adding fingeprints.... it has always worked... until now.

Let me know first if any of your existing Tuya switches are actually using the 1/2/3 .. driver ?

user1955 · November 13, 2022, 7:32pm

Yes l used Control-F
this driver "Moes ZigBee Wall Switch 1/2/3-Gang" is used by other device that works fine. Don't want to touch them cause it will interrupt alot of things.

But when l re-add the device. Then l change it to "Tuya Zigbee Dimmer module". The on and off does work only dim function give error. I tested it again. This is log from previous post. But its same

:2352022-11-13 11:21:49.738errorjava.lang.NullPointerException: Cannot invoke method multiply() on null object on line 935 (method parse)