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.
Well I think I've got my zigbee device's working again after trying multiple things and getting very frustrated, I ended up simply shutting down my hubitat for a couple of minutes and everything is working as it should be again.
This also made my 3 gang tuya switch work with your updated driver and the status changes instantly.
So thanks again for all your help.
This community really is amazing.
1 Like
Released version 0.2.8 of Muxa's "Zemismart ZigBee Wall Switch Multi-Gang" driver :
- added _TZ3000_18ejxno0 and _TZ3000_qewo8dlz fingerprints;
- added TS0001 wall switches fingerprints;
- added TS011F 2-gang wall outlets;
- added switchType configuration
Update May 2024 : this driver is now available for installation and update from HPM.
This is also @kkossev
One of my zemismart 3gang switches causes a continuous malfunction. When number 2 is activated, sometimes number 1 and 2 are operated simultaneously. They're both connected to the presence sensor, which is a symptom that turns on even though the presence sensor doesn't work.
So I changed the switch, and it's the same symptom.
So when I applied this driver to my zemismart 3gang switch, it didn't work very well. (https://raw.githubusercontent.com/kkossev/hubitat-muxa-fork/development/drivers/zemismart-zigbee-multigang-switch.groovy)
- endpointId: 01
- hasMultiEP: true
- application: 01
- driver: v1.0.1.1123b
- softwareBuild: 00000001
- model: FNB56-ZSW03LX2.0
- firmwareMT: 117E-0000-00000001
- manufacturer: FeiBit
search
Summary
dev:49792022-08-19 09:34:36.067 pm infoON/OFF CATCHALL CLUSTER EVENT - description:catchall: 0104 0006 03 01 0040 00 0B68 00 00 0000 0B 01 0000 | parseMap:[raw:catchall: 0104 0006 03 01 0040 00 0B68 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:0B68, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]
dev:49792022-08-19 09:34:34.476 pm infoON/OFF CATCHALL CLUSTER EVENT - description:catchall: 0104 0006 01 01 0040 00 0B68 00 00 0000 0B 01 0000 | parseMap:[raw:catchall: 0104 0006 01 01 0040 00 0B68 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0B68, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]
dev:49792022-08-19 09:34:32.883 pm infoON/OFF CATCHALL CLUSTER EVENT - description:catchall: 0104 0006 02 01 0040 00 0B68 00 00 0000 0B 01 0000 | parseMap:[raw:catchall: 0104 0006 02 01 0040 00 0B68 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:0B68, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]
dev:49792022-08-19 09:34:32.789 pm infoOn/Off Button press - description:read attr - raw: 0B680100060800001000, dni: 0B68, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00 | parseMap:[raw:0B680100060800001000, dni:0B68, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0, valueParsed:false]
dev:49792022-08-19 09:34:32.323 pm infoON/OFF CATCHALL CLUSTER EVENT - description:catchall: 0104 0006 03 01 0040 00 0B68 00 00 0000 0B 01 0000 | parseMap:[raw:catchall: 0104 0006 03 01 0040 00 0B68 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:0B68, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]
dev:49792022-08-19 09:34:32.263 pm infoON/OFF CATCHALL CLUSTER EVENT - description:catchall: 0104 0006 01 01 0040 00 0B68 00 00 0000 0B 01 0000 | parseMap:[raw:catchall: 0104 0006 01 01 0040 00 0B68 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0B68, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]
dev:49792022-08-19 09:34:32.193 pm infoON/OFF CATCHALL CLUSTER EVENT - description:catchall: 0104 0006 02 01 0040 00 0B68 00 00 0000 0B 01 0000 | parseMap:[raw:catchall: 0104 0006 02 01 0040 00 0B68 00 00 0000 0B 01 0000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:0B68, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]
dev:49792022-08-19 09:34:32.132 pm infoSending command 0 to cluster 0x0006 for Child deviceNetworkId: 4979-03
dev:49792022-08-19 09:34:32.129 pm infoSending command 0 to cluster 0x0006 for Child deviceNetworkId: 4979-01
dev:49792022-08-19 09:34:32.127 pm infoSending command 0 to cluster 0x0006 for Child deviceNetworkId: 4979-02
dev:49792022-08-19 09:34:31.783 pm infoOn/Off Button press - description:read attr - raw: 0B680100060800001001, dni: 0B68, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 01 | parseMap:[raw:0B680100060800001001, dni:0B68, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0, valueParsed:true]
dev:49792022-08-19 09:34:31.392 pm infoON/OFF CATCHALL CLUSTER EVENT - description:catchall: 0104 0006 03 01 0040 00 0B68 00 00 0000 0B 01 0100 | parseMap:[raw:catchall: 0104 0006 03 01 0040 00 0B68 00 00 0000 0B 01 0100, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:0B68, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[01, 00]]
dev:49792022-08-19 09:34:31.347 pm infoON/OFF CATCHALL CLUSTER EVENT - description:catchall: 0104 0006 01 01 0040 00 0B68 00 00 0000 0B 01 0100 | parseMap:[raw:catchall: 0104 0006 01 01 0040 00 0B68 00 00 0000 0B 01 0100, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:0B68, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[01, 00]]
dev:49792022-08-19 09:34:31.294 pm infoON/OFF CATCHALL CLUSTER EVENT - description:catchall: 0104 0006 02 01 0040 00 0B68 00 00 0000 0B 01 0100 | parseMap:[raw:catchall: 0104 0006 02 01 0040 00 0B68 00 00 0000 0B 01 0100, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:0B68, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[01, 00]]
dev:49792022-08-19 09:34:31.217 pm infoSending command 1 to cluster 0x0006 for Child deviceNetworkId: 4979-03
dev:49792022-08-19 09:34:31.214 pm infoSending command 1 to cluster 0x0006 for Child deviceNetworkId: 4979-01
dev:49792022-08-19 09:34:31.211 pm infoSending command 1 to cluster 0x0006 for Child deviceNetworkId: 4979-02
dev:49792022-08-19 09:30:58.711 pm infoOn/Off Button press - description:read attr - raw: 0B680300060800001000, dni: 0B68, endpoint: 03, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00 | parseMap:[raw:0B680300060800001000, dni:0B68, endpoint:03, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0, valueParsed:false]
dev:49792022-08-19 09:30:58.680 pm infoOn/Off Button press - description:read attr - raw: 0B680200060800001000, dni: 0B68, endpoint: 02, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00 | parseMap:[raw:0B680200060800001000, dni:0B68, endpoint:02, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0, valueParsed:false]
dev:49792022-08-19 09:30:58.659 pm infoOn/Off Button press - description:read attr - raw: 0B680100060800001000, dni: 0B68, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00 | parseMap:[raw:0B680100060800001000, dni:0B68, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:00, clusterInt:6, attrInt:0, valueParsed:false]
I'm using the Generic Zigbee Multi-Endpoint Switch driver. Occasionally, switch #2 seemed to fail changing the state --I'd notice the dashboard tile showed 'on' but the switch had turned the light off. #2 also had a tendency to show as inactive on the daily Activity Report. This switch just runs indicator lights so I use a 'dirty fix' rule to toggle it daily. No problems since.
- endpointId: 01
- application: 01
- softwareBuild: 00000001
- model: FNB56-ZSW03LX2.0
- firmwareMT: 117E-0000-00000001
- isMultiEP: true
- manufacturer: FeiBit
1 Like
I use "Zigbee - Generic Switch (with present)" and I'll have to change the driver first.
What is this?
I'm using the web core to turn off the switch where the presence sensor is not working.
Just a Rule to prevent or remove errors on problem-prone devices.
1 Like
This is not a typical Tuya MCU firmware, so the Muxa's driver may not work with this device.
1 Like
Is there any product that has no problem with HE?
In many cases, the problem is in the product itself, not in HE.
As example - check here - https://github.com/Koenkk/zigbee2mqtt/issues/4461 - 75 comments, including WireShark sniff screenshots, etc, etc..
1 Like
