Zemismart Zigbee 1/2/3/4 gang light switches

I’ve noticed the device(tuya ts0013) doesn’t refresh status when switched manually anybody else had this problem?

I’ve created a 30second rule to refresh for now.

Please turn the Debug logs on and copy/paste the logs when the switches (1 2 and 3) are turned on/off manually.

You can use the forum editor 'Hide Details' feature (select the log lines first) :

Refreshing every 30 seconds will work but is not the best solution long term.

dev:2902022-06-04 08:08:38.940 pm debugoff()

dev:2902022-06-04 08:08:34.662 pm debugon()

dev:2902022-06-04 08:07:35.623 pm infoChild switch 01 turned off

dev:2902022-06-04 07:57:35.302 pm infoChild switch 01 turned on

dev:2902022-06-04 07:49:28.755 pm debugon()

--- Live Log Started, waiting for events ---
The switch was turn off manually almost instantly but took 10mins to show

I'll try getting the other logs just not easy in a busy house

Actually just realised device status dosnt seem to update when turn on and off on the device page but the switch dose do as asked just dosnt show the correct status still so seems as though it's not just manual.

Seems like the Debug option is not switched on.
Look at the 'Parent' device logs, you mus see something similar to this:

Summary

dev:13762022-06-04 22:30:35.963 debugTuya Switch Module TS0004 Parsed: [raw:72E70100060800001000, dni:72E7, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]

dev:13762022-06-04 22:30:35.944 debugTuya Switch Module TS0004 Parsed: [raw:72E70100060800001000, dni:72E7, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]

dev:13762022-06-04 22:30:34.184 debugTuya Switch Module TS0004 Parent switch on

dev:13762022-06-04 22:30:34.172 debugTuya Switch Module TS0004 Parsed: [raw:72E70300060800001001, dni:72E7, endpoint:03, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0]

dev:13762022-06-04 22:30:28.747 debugTuya Switch Module TS0004 Parsed: [raw:72E70200060800001000, dni:72E7, endpoint:02, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]

dev:13762022-06-04 22:30:21.994 debugTuya Switch Module TS0004 Parent switch on

Says on the child devices page and parent that debug logs are on.

search

dev:2892022-06-04 08:20:09.180 pm debugParsed: [raw:catchall: 0104 0006 01 01 0040 00 F99F 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:2892022-06-04 08:20:09.044 pm debugcomponentOff 289-01

dev:2892022-06-04 08:20:03.950 pm debugParsed: [raw:catchall: 0104 0006 01 01 0040 00 F99F 00 00 0000 0B 01 0100, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[01, 00]]

dev:2892022-06-04 08:20:03.672 pm debugcomponentOn 289-01

dev:2892022-06-04 08:19:51.009 pm debugParsed: [raw:catchall: 0104 0006 01 01 0040 00 F99F 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:2892022-06-04 08:19:50.796 pm debugcomponentOff 289-01

dev:2892022-06-04 08:19:47.887 pm debugParsed: [raw:catchall: 0104 0006 01 01 0040 00 F99F 00 00 0000 0B 01 0100, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[01, 00]]

dev:2892022-06-04 08:19:47.608 pm debugcomponentOn 289-01

dev:2892022-06-04 08:19:28.598 pm debugParsed: [raw:catchall: 0104 0006 03 01 0040 00 F99F 00 00 0000 0B 01 0100, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[01, 00]]

dev:2892022-06-04 08:19:28.385 pm debugcomponentOn 289-03

dev:2892022-06-04 08:19:26.523 pm debugParsed: [raw:catchall: 0104 0006 03 01 0040 00 F99F 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:2892022-06-04 08:19:26.388 pm debugcomponentOff 289-03

dev:2892022-06-04 08:19:24.447 pm debugParsed: [raw:catchall: 0104 0006 03 01 0040 00 F99F 00 00 0000 0B 01 0100, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[01, 00]]

dev:2892022-06-04 08:19:24.186 pm debugcomponentOn 289-03

dev:2892022-06-04 08:19:22.369 pm debugParsed: [raw:catchall: 0104 0006 03 01 0040 00 F99F 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:2892022-06-04 08:19:22.241 pm debugcomponentOff 289-03

dev:2892022-06-04 08:19:20.302 pm debugParsed: [raw:catchall: 0104 0006 03 01 0040 00 F99F 00 00 0000 0B 01 0100, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[01, 00]]

dev:2892022-06-04 08:19:20.155 pm debugcomponentOn 289-03

dev:2892022-06-04 08:19:05.967 pm debugParsed: [raw:catchall: 0104 0006 03 01 0040 00 F99F 00 00 0000 0B 01 0100, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[01, 00]]

dev:2892022-06-04 08:19:05.865 pm debugcomponentOn 289-03

dev:2892022-06-04 08:19:02.121 pm debugParsed: [raw:catchall: 0104 0006 03 01 0040 00 F99F 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:2892022-06-04 08:19:01.818 pm debugcomponentOff 289-03

dev:2892022-06-04 08:08:39.431 pm debugParsed: [raw:catchall: 0104 0006 01 01 0040 00 F99F 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:2892022-06-04 08:08:38.946 pm debugcomponentOff 289-01

dev:2892022-06-04 08:08:35.113 pm debugParsed: [raw:catchall: 0104 0006 01 01 0040 00 F99F 00 00 0000 0B 01 0100, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[01, 00]]

dev:2892022-06-04 08:08:34.723 pm debugcomponentOn 289-01

dev:2892022-06-04 08:07:35.608 pm debugParsed: [raw:F99F0100060800001000, dni:F99F, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]

dev:2892022-06-04 07:57:35.303 pm debugParent switch on

dev:2892022-06-04 07:57:35.289 pm debugParsed: [raw:F99F0100060800001001, dni:F99F, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0]

dev:2892022-06-04 07:49:28.936 pm debugParsed: [raw:catchall: 0104 0006 01 01 0040 00 F99F 00 00 0000 0B 01 0100, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[01, 00]]

dev:2892022-06-04 07:49:28.761 pm debugcomponentOn 289-01

dev:2892022-06-04 07:47:34.627 pm debugParsed: [raw:F99F0100060800001000, dni:F99F, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]

dev:2892022-06-04 07:47:30.703 pm debugParsed: [raw:catchall: 0104 0006 01 01 0040 00 F99F 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:2892022-06-04 07:47:30.427 pm debugcomponentOff 289-01

dev:2892022-06-04 07:47:08.976 pm debugParsed: [raw:catchall: 0104 0006 01 01 0040 00 F99F 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:2892022-06-04 07:47:08.668 pm debugcomponentOff 289-01

dev:2892022-06-04 07:40:26.756 pm debugParsed: [raw:catchall: 0104 0006 01 01 0040 00 F99F 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F99F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:2892022-06-04 07:40:26.580 pm debugcomponentOff 289-01

dev:2892022-06-04 07:39:30.357 pm debugParent switch on

dev:2892022-06-04 07:39:30.352 pm debugParsed: [raw:F99F0300060A00001000, dni:F99F, endpoint:03, cluster:0006, size:0A, attrId:0000, encoding:10, command:01, value:00, clusterInt:6, attrInt:0]

dev:2892022-06-04 07:39:30.346 pm debugParent switch on

dev:2892022-06-04 07:39:30.340 pm debugParsed: [raw:F99F0200060A00001001, dni:F99F, endpoint:02, cluster:0006, size:0A, attrId:0000, encoding:10, command:01, value:01, clusterInt:6, attrInt:0]

dev:2892022-06-04 07:39:30.336 pm debugParsed: [raw:F99F0100060A00001001, dni:F99F, endpoint:01, cluster:0006, size:0A, attrId:0000, encoding:10, command:01, value:01, clusterInt:6, attrInt:0]

dev:2892022-06-04 07:39:30.084 pm debugrefreshing

dev:2892022-06-04 07:39:00.238 pm debugParent switch on

dev:2892022-06-04 07:39:00.238 pm debugParent switch on

dev:2892022-06-04 07:39:00.232 pm debugParsed: [raw:F99F0300060A00001000, dni:F99F, endpoint:03, cluster:0006, size:0A, attrId:0000, encoding:10, command:01, value:00, clusterInt:6, attrInt:0]

1 Like

Thanks, I have the logs data now, it should help to find where the problem is.

1 Like

@ADDs can you try the fix in the new version 0.2.7 (the second link in this post) ?

@kkossev I uploaded the driver still dosnt seem to have made any difference.

Is it this version ( lines 31 and 32 in the code) ?

def version() { "0.2.7" }
def timeStamp() {"2022/06/05 12:15 AM"}

Yes it’s that one.

What was found in your previous logs was that this device sends the response to On/Off commands from HE using a Zigbee command that was not processed by the previous versions of this driver. So when using version 0.2.7 the on/off status of the 3 gangs should be reflected in HE, but obviously there is also something else that we don't know.

The only thing that comes in my mind for now is to completely remove the device from HE, and then re-pair it as a new device. Some Tuya devices require that they receive the specific initialization sequence exactly at the time of the pairing, simply pressing Initialize or Configure button does not work.

Thank you for the tests, if I find something more for this device I will let you know.

I tried deleting as you said and repaired the device but that didn't work at all only showed 1 child device and couldn't switch anything on or off I'm afraid, I couldn't even delete the device after I had to change the device handler to something else before it would let me delete it otherwise would just hang on the removal page.

I know your trying to help and I appreciate it I'm sorry this isn't working :weary:

1 Like

Just an update don’t know if this help’s i only get logs in the zigbee logs
This is when I turned off and on all switches manually

3 gang tuya switch2022-06-05 19:29:40.740 profileId:0x104, clusterId:0x6, sourceEndpoint:3, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-73

3 gang tuya switch2022-06-05 19:29:39.632 profileId:0x104, clusterId:0x6, sourceEndpoint:2, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-73

3 gang tuya switch2022-06-05 19:29:38.525 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-73

3 gang tuya switch2022-06-05 19:29:37.920 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-73

3 gang tuya switch2022-06-05 19:29:34.599 profileId:0x104, clusterId:0x6, sourceEndpoint:3, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-73

3 gang tuya switch2022-06-05 19:29:33.491 profileId:0x104, clusterId:0x6, sourceEndpoint:2, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-73

3 gang tuya switch2022-06-05 19:29:32.887 profileId:0x104, clusterId:0x6, sourceEndpoint:2, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-73

3 gang tuya switch2022-06-05 19:29:31.377 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-72

3 gang tuya switch2022-06-05 19:29:30.872 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-73

These are the hub Zigbee logs, without much data sent/received details.
Can you try to find the 3 gang tuya switch logs - same as the logs you posted here.

This is from the parent device is found in past logs.

:4092022-06-05 07:37:40.232 pminfo3 gang tuya switch Creatung device 409-02

dev:4092022-06-05 07:37:40.226 pminfo3 gang tuya switch Child device 409-01 already exists (3 gang tuya switch EP01)

dev:4092022-06-05 07:37:40.204 pmdebug3 gang tuya switch Parent createChildDevices

dev:4092022-06-05 07:37:40.201 pmdebug3 gang tuya switch model: TS0013 buttons: 3

dev:4092022-06-05 07:37:40.142 pmdebug3 gang tuya switch Parent deleteChildren

dev:4092022-06-05 07:37:40.139 pmdebug3 gang tuya switch Parent setupChildDevices

dev:4092022-06-05 07:37:39.946 pminfo3 gang tuya switch InitializeVars()... fullInit = true

dev:4092022-06-05 07:37:39.938 pmdebug3 gang tuya switch Initializing...

dev:4092022-06-05 07:12:47.828 pminfo3 gang tuya switch Creatung device 409-01

dev:4092022-06-05 07:12:47.811 pmdebug3 gang tuya switch Parent createChildDevices

dev:4092022-06-05 07:12:47.810 pmdebug3 gang tuya switch model: TS0013 buttons: 3

dev:4092022-06-05 07:12:47.799 pmdebug3 gang tuya switch Parent deleteChildren

dev:4092022-06-05 07:12:47.798 pmdebug3 gang tuya switch Parent setupChildDevices

dev:4092022-06-05 07:12:47.785 pminfo3 gang tuya switch InitializeVars()... fullInit = true

dev:4092022-06-05 07:12:47.784 pmdebug3 gang tuya switch Initializing...

dev:4092022-06-05 07:12:13.841 pmdebugZemismart ZigBee Wall Switch Multi-Gang UNPROCESSED EP: 01 cluster: 0000 attrId: FFDF

dev:4092022-06-05 07:12:13.838 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C701000076DFFF423714662F2A1315662F2A12DB6E2F2A12A8742F2A12E67B2F2A12857D2F2A124F802F2A1290812F2A1207AD2F2A1275AD2F2A1283AD2F2A16, dni:26C7, endpoint:01, cluster:0000, size:76, attrId:FFDF, encoding:42, command:0A, value:f/*f/*Ûn/*¨t/*æ{/*…}/*O€/*/*a­/*u­/*ƒ­/*, clusterInt:0, attrInt:65503]

dev:4092022-06-05 07:12:13.582 pmdebugZemismart ZigBee Wall Switch Multi-Gang UNPROCESSED EP: 01 cluster: 0000 attrId: 0001

dev:4092022-06-05 07:12:13.579 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C70100001801002043E2FF2033E4FF2000, dni:26C7, endpoint:01, cluster:0000, size:18, attrId:0001, encoding:20, command:0A, value:43, clusterInt:0, attrInt:1, additionalAttrs:[[value:33, encoding:20, attrId:FFE2, consumedBytes:4, attrInt:65506], [value:00, encoding:20, attrId:FFE4, consumedBytes:4, attrInt:65508]]]

dev:4092022-06-05 07:12:13.454 pmwarnZemismart ZigBee Wall Switch Multi-Gang Child device 409-03 not found. Initialise parent device first

dev:4092022-06-05 07:12:13.451 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C70300061C0000100001402100000240210000, dni:26C7, endpoint:03, cluster:0006, size:1C, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0, additionalAttrs:[[value:0000, encoding:21, attrId:4001, consumedBytes:5, attrInt:16385], [value:0000, encoding:21, attrId:4002, consumedBytes:5, attrInt:16386]]]

dev:4092022-06-05 07:12:13.325 pmwarnZemismart ZigBee Wall Switch Multi-Gang Child device 409-02 not found. Initialise parent device first

dev:4092022-06-05 07:12:13.322 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C70200061C0000100001402100000240210000, dni:26C7, endpoint:02, cluster:0006, size:1C, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0, additionalAttrs:[[value:0000, encoding:21, attrId:4001, consumedBytes:5, attrInt:16385], [value:0000, encoding:21, attrId:4002, consumedBytes:5, attrInt:16386]]]

dev:4092022-06-05 07:12:13.196 pmdebugZemismart ZigBee Wall Switch Multi-Gang UNPROCESSED EP: 01 cluster: E001 attrId: D030

dev:4092022-06-05 07:12:13.194 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C701E0010830D03000, dni:26C7, endpoint:01, cluster:E001, size:08, attrId:D030, encoding:30, command:0A, value:00, clusterInt:57345, attrInt:53296]

dev:4092022-06-05 07:12:13.085 pmwarnZemismart ZigBee Wall Switch Multi-Gang Child device 409-01 not found. Initialise parent device first

dev:4092022-06-05 07:12:13.081 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C701000624000010000140210000024021000002803002, dni:26C7, endpoint:01, cluster:0006, size:24, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0, additionalAttrs:[[value:0000, encoding:21, attrId:4001, consumedBytes:5, attrInt:16385], [value:0000, encoding:21, attrId:4002, consumedBytes:5, attrInt:16386], [value:02, encoding:30, attrId:8002, consumedBytes:4, attrInt:32770]]]

dev:4092022-06-05 07:12:12.403 pmdebugZemismart ZigBee Wall Switch Multi-Gang UNPROCESSED EP: 01 cluster: E000 attrId: D003

dev:4092022-06-05 07:12:12.401 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C701E0002003D0420C414141414167414142414141, dni:26C7, endpoint:01, cluster:E000, size:20, attrId:D003, encoding:42, command:0A, value:AAAAAgAABAAA, clusterInt:57344, attrInt:53251]

dev:4092022-06-05 07:12:10.330 pmwarnZemismart ZigBee Wall Switch Multi-Gang Child device 409-03 not found. Initialise parent device first

dev:4092022-06-05 07:12:10.328 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C70300060800001000, dni:26C7, endpoint:03, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]

dev:4092022-06-05 07:12:10.203 pmwarnZemismart ZigBee Wall Switch Multi-Gang Child device 409-02 not found. Initialise parent device first

dev:4092022-06-05 07:12:10.200 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C70200060800001000, dni:26C7, endpoint:02, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]

dev:4092022-06-05 07:12:10.077 pmwarnZemismart ZigBee Wall Switch Multi-Gang Child device 409-01 not found. Initialise parent device first

dev:4092022-06-05 07:12:10.075 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C70100060800001000, dni:26C7, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0]

dev:4092022-06-05 07:12:07.913 pmdebugZemismart ZigBee Wall Switch Multi-Gang UNPROCESSED EP: 01 cluster: 0000 attrId: FFDF

dev:4092022-06-05 07:12:07.911 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C701000076DFFF423714662F2A1315662F2A12DB6E2F2A12A8742F2A12E67B2F2A12857D2F2A124F802F2A1290812F2A1207AD2F2A1275AD2F2A1283AD2F2A16, dni:26C7, endpoint:01, cluster:0000, size:76, attrId:FFDF, encoding:42, command:0A, value:f/*f/*Ûn/*¨t/*æ{/*…}/*O€/*/*a­/*u­/*ƒ­/*, clusterInt:0, attrInt:65503]

dev:4092022-06-05 07:12:07.274 pmdebugZemismart ZigBee Wall Switch Multi-Gang UNPROCESSED EP: 01 cluster: 0000 attrId: 0001

dev:4092022-06-05 07:12:07.270 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C70100001801002043E2FF2033E4FF2000, dni:26C7, endpoint:01, cluster:0000, size:18, attrId:0001, encoding:20, command:0A, value:43, clusterInt:0, attrInt:1, additionalAttrs:[[value:33, encoding:20, attrId:FFE2, consumedBytes:4, attrInt:65506], [value:00, encoding:20, attrId:FFE4, consumedBytes:4, attrInt:65508]]]

dev:4092022-06-05 07:12:04.626 pmdebugZemismart ZigBee Wall Switch Multi-Gang UNPROCESSED EP: null cluster: null attrId: null

dev:4092022-06-05 07:12:04.623 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:catchall: 0104 0006 01 01 0040 00 26C7 00 00 0000 07 01 00000000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:26C7, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00, 00, 00, 00]]

dev:4092022-06-05 07:12:02.577 pmdebugZemismart ZigBee Wall Switch Multi-Gang UNPROCESSED EP: null cluster: null attrId: null

dev:4092022-06-05 07:12:02.574 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:catchall: 0000 8021 00 00 0040 00 26C7 00 00 0000 00 00 7C00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:26C7, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[7C, 00]]

dev:4092022-06-05 07:12:02.509 pmwarnZemismart ZigBee Wall Switch Multi-Gang Child device 409-03 not found. Initialise parent device first

dev:4092022-06-05 07:12:02.507 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C70300060A00001000, dni:26C7, endpoint:03, cluster:0006, size:0A, attrId:0000, encoding:10, command:01, value:00, clusterInt:6, attrInt:0]

dev:4092022-06-05 07:12:02.483 pmwarnZemismart ZigBee Wall Switch Multi-Gang Child device 409-02 not found. Initialise parent device first

dev:4092022-06-05 07:12:02.480 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C70200060A00001000, dni:26C7, endpoint:02, cluster:0006, size:0A, attrId:0000, encoding:10, command:01, value:00, clusterInt:6, attrInt:0]

dev:4092022-06-05 07:12:02.474 pmwarnZemismart ZigBee Wall Switch Multi-Gang Child device 409-01 not found. Initialise parent device first

dev:4092022-06-05 07:12:02.468 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C70100060A00001000, dni:26C7, endpoint:01, cluster:0006, size:0A, attrId:0000, encoding:10, command:01, value:00, clusterInt:6, attrInt:0]

dev:4092022-06-05 07:12:02.245 pmdebugZemismart ZigBee Wall Switch Multi-Gang UNPROCESSED EP: 01 cluster: 0000 attrId: 0004

dev:4092022-06-05 07:12:02.240 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parsed: [raw:26C701000068040042105F545A333030305F797067726938797A0000002003010000204305000042065453303031330700003003FEFF003000, dni:26C7, endpoint:01, cluster:0000, size:68, attrId:0004, encoding:42, command:01, value:_TZ3000_ypgri8yz, clusterInt:0, attrInt:4, additionalAttrs:[[value:03, encoding:20, attrId:0000, consumedBytes:4, attrInt:0], [value:43, encoding:20, attrId:0001, consumedBytes:4, attrInt:1], [value:TS0013, encoding:42, attrId:0005, consumedBytes:9, attrInt:5]]]

dev:4092022-06-05 07:12:02.233 pminfoZemismart ZigBee Wall Switch Multi-Gang InitializeVars()... fullInit = false

dev:4092022-06-05 07:12:02.227 pmdebugZemismart ZigBee Wall Switch Multi-Gang updating the settings from the current driver version null to the new version 0.2.7 2022/06/05 12:15 AM

dev:4092022-06-05 07:12:01.991 pmdebugZemismart ZigBee Wall Switch Multi-Gang sendZigbeeCommands received : [he raw 0x26C7 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he rattr 0x26C7 0xFF 0x0006 0x0, zdo bind 0x26C7 0x01 0x01 6 {A4C138F0086C122E} {}, delay 2000, he cr 0x26C7 0x01 6 0 16 0 600 {}, delay 2000]

dev:4092022-06-05 07:12:01.984 pmdebugZemismart ZigBee Wall Switch Multi-Gang refreshing

dev:4092022-06-05 07:12:01.979 pmdebugZemismart ZigBee Wall Switch Multi-Gang configure()..

dev:4092022-06-05 07:12:01.973 pmdebugZemismart ZigBee Wall Switch Multi-Gang Parent installed

1 Like

Until 07:12 you had the child devices either missing or created from previous drivers or tests with wrong IDs.
At 07:37 the switch was re-paired (probably deleted before), but the logs stop here...

What are the current logs showing?

I’ve just realised something has happened to my zigbee device’s because suddenly they’re not working correctly so it might be this is the problem not your driver I need to investigate further.

1 Like

The device doesn’t show in current logs

Probably the best approach would be to ensure that the other Zigbee devices work OK, then go back to this switch, In all the cases, there should be some logs when you try pressing the device web page buttons, even if the device is not paired to the hub.