No Neutral zigbee switch - driver needed

Sekenenz · April 14, 2023, 6:26pm

Can't find a working driver for a mini switch (no neutral).

I have tried the generic driver (single and multiple) and the zemismart multi gang, but it does not respond. It is recorded correctly in the log.

Manufacturer: _TZ3000_ji4araar
Endpoint 01 application:	43
Endpoint 01 endpointId:	01
Endpoint 01 idAsInt:	1
Endpoint 01 inClusters:	0003,0004,0005,0006,E000,E001,0000
Endpoint 01 initialized:	true
Endpoint 01 manufacturer:	_TZ3000_ji4araar
Endpoint 01 model:	TS0011
Endpoint 01 outClusters:	0019,000A
Endpoint 01 profileId:	0104
Endpoint 01 stage:	4

This is the device

kkossev · April 14, 2023, 6:50pm

If you look at the Device Details, Data section - do you see endpointId:01 and the same model and manufacturer as in the data that you have obtained during the pairing?

Was the Zemismart driver installed in advance, before you paired the switch as a new device?
Was this driver selected automatically during the pairing? Which version of the Zemismart driver are you using?

mike.maxwell · April 14, 2023, 7:57pm

after switching drivers have you clicked the configure command?, there shouldn't be any reason this device shouldn't work with the generic zigbee switch driver based on the info you posted.

Sekenenz · April 14, 2023, 9:22pm

Yes

endpointId: 01
application: 43
manufacturer: _TZ3000_ji4araar
model: TS0011

Yes

Yes, at any repairing is always selected automatically. The driver version is 0.5.1

I just noticed that after initialization in debug it shows button:0
Is this normal?

dev:1362023-04-14 22:57:27.777debugAtrio Parent createChildDevices
dev:1362023-04-14 22:57:27.774debugAtrio model: TS0011 buttons: 0
dev:1362023-04-14 22:57:27.767debugAtrio Parent deleteChildren
dev:1362023-04-14 22:57:27.766debugAtrio Parent setupChildDevices
dev:1362023-04-14 22:57:27.760debugAtrio sendZigbeeCommands : [he raw 0x8B94 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0x8B94 0x01 0x0000 0xFFDE 0x20 {0D} {}, delay 50, zdo bind 0x8B94 0x01 0x01 6 {A4C13813CDF5E141} {}, delay 2000, he cr 0x8B94 0x01 6 0 16 0 600 {}, delay 2000, he rattr 0x8B94 0x01 6 0 {}, delay 2000]
dev:1362023-04-14 22:57:27.751debugAtrio configure()..

Of course. After configure, initialize.
The same procedure I followed with all other devices and never had any problems. This is the only device without a neutral that I have, so I cannot make any comparison.

kkossev · April 15, 2023, 5:59am

Hi @Sekenenz ,
All the initialization commands sent to this switch are as expected...
Do you see anything received back from the switch in the live logs? There should be logs starting with "Parsed descMap: ..........."

Yes, the original author of this driver has chosen not the best descriptive name - 'button' actually means ''the number of the child devices'. As this is a single gang switch, there are no child devices to be created.

I can only speculate, that this may be one of the problematic devices that changes their NWK address and is not accessible shortly after the initial pairing... You can verify this by observing the Zigbee logs - open in a new browser tab Settings->Zigbee Details->Zigbee logs and pair the switch again. If the device changes its NWK, you will observe several new devices poping up during the pairing - like this : https://community.hubitat.com/uploads/default/original/3X/c/4/c491f7cfddbbab3e31bc9cefee1c8b6eb442672c.png
Also, if you click the switch button immediately after HE discovers the device, it may manage to send the on/off events for a few seconds, then it will stop after changing the NWK address. Can you try that?

Sekenenz · April 15, 2023, 6:57am

Initially there was no "Parsed descMap" in the log, but an error popped up (I don't know if relevant):

errororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_muxa_Zemismart_ZigBee_Wall_Switch_Multi_Gang_588.logsOff() is applicable for argument types: () values: []
Possible solutions: logInfo(java.lang.Object), off(), notify() (method logsOff)

After a new pairing it show this:

dev:1372023-04-15 08:34:42.535debugAtrio Parent createChildDevices
dev:1372023-04-15 08:34:42.534debugAtrio model: TS0011 buttons: 0
dev:1372023-04-15 08:34:42.530debugAtrio Parent deleteChildren
dev:1372023-04-15 08:34:42.529debugAtrio Parent setupChildDevices
dev:1372023-04-15 08:34:42.523debugAtrio sendZigbeeCommands : [he raw 0xEFF3 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0xEFF3 0x01 0x0000 0xFFDE 0x20 {0D} {}, delay 50, zdo bind 0xEFF3 0x01 0x01 6 {A4C13813CDF5E141} {}, delay 2000, he cr 0xEFF3 0x01 6 0 16 0 600 {}, delay 2000, he rattr 0xEFF3 0x01 6 0 {}, delay 2000]
dev:1372023-04-15 08:34:42.515debugAtrio configure()..
dev:1372023-04-15 08:34:42.513infoAtrio InitializeVars()... fullInit = true
dev:1372023-04-15 08:34:42.512debugAtrio Initializing...
dev:1372023-04-15 08:34:37.161infoAtrio Turning all child switches on
dev:1372023-04-15 08:30:26.765infoAtrio Turning all child switches on
dev:1372023-04-15 08:30:24.965infoAtrio Turning all child switches off
dev:1372023-04-15 08:30:23.912infoAtrio Turning all child switches on
dev:1372023-04-15 08:30:20.026debugAtrio sendZigbeeCommands : [he raw 0xEFF3 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0xEFF3 0x01 0x0000 0xFFDE 0x20 {0D} {}, delay 50, zdo bind 0xEFF3 0x01 0x01 6 {A4C13813CDF5E141} {}, delay 2000, he cr 0xEFF3 0x01 6 0 16 0 600 {}, delay 2000, he rattr 0xEFF3 0x01 6 0 {}, delay 2000]
dev:1372023-04-15 08:30:20.019debugAtrio configure()..
dev:1372023-04-15 08:30:19.402infoAtrio Turning all child switches on
dev:1372023-04-15 08:30:18.888infoAtrio Turning all child switches off
dev:1372023-04-15 08:30:18.132infoAtrio Turning all child switches on
dev:1372023-04-15 08:30:05.724warnZemismart ZigBee Wall Switch Multi-Gang parseBasicClusterAttribute cluster:null UNKNOWN attrId FFDF value:«¬!ÚM9ÔSÔ
dev:1372023-04-15 08:30:05.716debugZemismart ZigBee Wall Switch Multi-Gang Parsed descMap: [raw:EFF30100003ADFFF4219AB18000012AC21000012DA4D00001239D400001253D4000016, dni:EFF3, endpoint:01, cluster:0000, size:3A, attrId:FFDF, encoding:42, command:0A, value:«¬!ÚM9ÔSÔ, clusterInt:0, attrInt:65503] (description:read attr - raw: EFF30100003ADFFF4219AB18000012AC21000012DA4D00001239D400001253D4000016, dni: EFF3, endpoint: 01, cluster: 0000, size: 3A, attrId: FFDF, encoding: 42, command: 0A, value: 19AB18000012AC21000012DA4D00001239D400001253D4000016)
dev:1372023-04-15 08:30:05.048debugZemismart ZigBee Wall Switch Multi-Gang Attribite FFE4 : 00
dev:1372023-04-15 08:30:05.045debugZemismart ZigBee Wall Switch Multi-Gang Attribite FFE2 : 33
dev:1372023-04-15 08:30:05.043debugZemismart ZigBee Wall Switch Multi-Gang Applicaiton version: 43
dev:1372023-04-15 08:30:05.037debugZemismart ZigBee Wall Switch Multi-Gang Parsed descMap: [raw:EFF30100001801002043E2FF2033E4FF2000, dni:EFF3, 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]]] (description:read attr - raw: EFF30100001801002043E2FF2033E4FF2000, dni: EFF3, endpoint: 01, cluster: 0000, size: 18, attrId: 0001, encoding: 20, command: 0A, value: 43E2FF2033E4FF2000)
dev:1372023-04-15 08:30:04.395debugZemismart ZigBee Wall Switch Multi-Gang Parent switch off
dev:1372023-04-15 08:30:04.389debugZemismart ZigBee Wall Switch Multi-Gang Parsed descMap: [raw:EFF30100060A00001000, dni:EFF3, endpoint:01, cluster:0006, size:0A, attrId:0000, encoding:10, command:01, value:00, clusterInt:6, attrInt:0] (description:read attr - raw: EFF30100060A00001000, dni: EFF3, endpoint: 01, cluster: 0006, size: 0A, attrId: 0000, encoding: 10, command: 01, value: 00)
dev:1372023-04-15 08:30:02.390debugZemismart ZigBee Wall Switch Multi-Gang Zemismart ZigBee Wall Switch Multi-Gang unprocessed EP: 01 cluster: 0006 attrId: null
dev:1372023-04-15 08:30:02.385debugZemismart ZigBee Wall Switch Multi-Gang Parsed descMap: [raw:catchall: 0104 0006 01 01 0040 00 EFF3 00 00 0000 07 01 00000000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:EFF3, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00, 00, 00, 00]] (description:catchall: 0104 0006 01 01 0040 00 EFF3 00 00 0000 07 01 00000000)
dev:1372023-04-15 08:30:00.374debugZemismart ZigBee Wall Switch Multi-Gang Zemismart ZigBee Wall Switch Multi-Gang unprocessed EP: 00 cluster: 8021 attrId: null
dev:1372023-04-15 08:30:00.368debugZemismart ZigBee Wall Switch Multi-Gang Parsed descMap: [raw:catchall: 0000 8021 00 00 0040 00 EFF3 00 00 0000 00 00 D600, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:EFF3, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[D6, 00]] (description:catchall: 0000 8021 00 00 0040 00 EFF3 00 00 0000 00 00 D600)
dev:1372023-04-15 08:30:00.255debugZemismart ZigBee Wall Switch Multi-Gang Zemismart ZigBee Wall Switch Multi-Gang unprocessed EP: 01 cluster: 0000 attrId: null
dev:1372023-04-15 08:30:00.250debugZemismart ZigBee Wall Switch Multi-Gang Parsed descMap: [raw:catchall: 0104 0000 01 01 0040 00 EFF3 00 00 0000 04 01 00, profileId:0104, clusterId:0000, clusterInt:0, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:EFF3, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]] (description:catchall: 0104 0000 01 01 0040 00 EFF3 00 00 0000 04 01 00)
dev:1372023-04-15 08:30:00.091debugZemismart ZigBee Wall Switch Multi-Gang Model Identifier: TS0011
dev:1372023-04-15 08:30:00.089debugZemismart ZigBee Wall Switch Multi-Gang Applicaiton version: 43
dev:1372023-04-15 08:30:00.087debugZemismart ZigBee Wall Switch Multi-Gang ZLC version: 03
dev:1372023-04-15 08:30:00.084debugZemismart ZigBee Wall Switch Multi-Gang Manufacturer name: _TZ3000_ji4araar
dev:1372023-04-15 08:30:00.067debugZemismart ZigBee Wall Switch Multi-Gang Parsed descMap: [raw:EFF301000068040042105F545A333030305F6A693461726161720000002003010000204305000042065453303031310700003003FEFF003000, dni:EFF3, endpoint:01, cluster:0000, size:68, attrId:0004, encoding:42, command:01, value:_TZ3000_ji4araar, 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:TS0011, encoding:42, attrId:0005, consumedBytes:9, attrInt:5]]] (description:read attr - raw: EFF301000068040042105F545A333030305F6A693461726161720000002003010000204305000042065453303031310700003003FEFF003000, dni: EFF3, endpoint: 01, cluster: 0000, size: 68, attrId: 0004, encoding: 42, command: 01, value: 105F545A333030305F6A693461726161720000002003010000204305000042065453303031310700003003FEFF003000)
dev:1372023-04-15 08:30:00.056infoZemismart ZigBee Wall Switch Multi-Gang InitializeVars()... fullInit = false
dev:1372023-04-15 08:30:00.052debugZemismart ZigBee Wall Switch Multi-Gang updating the settings from the current driver Zemismart ZigBee Wall Switch Multi-Gang version null to the new version 0.5.1 2023/04/05 7:27 AM [model TS0011, manufacturer _TZ3000_ji4araar, application 43, endpointId 01]
dev:1372023-04-15 08:29:59.769debugZemismart ZigBee Wall Switch Multi-Gang sendZigbeeCommands : [he raw 0xEFF3 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he wattr 0xEFF3 0x01 0x0000 0xFFDE 0x20 {0D} {}, delay 50, zdo bind 0xEFF3 0x01 0x01 6 {A4C13813CDF5E141} {}, delay 2000, he cr 0xEFF3 0x01 6 0 16 0 600 {}, delay 2000, he rattr 0xEFF3 0x01 6 0 {}, delay 2000]
dev:1372023-04-15 08:29:59.759debugZemismart ZigBee Wall Switch Multi-Gang configure()..
dev:1372023-04-15 08:29:59.751infoZemismart ZigBee Wall Switch Multi-Gang model TS0011, manufacturer _TZ3000_ji4araar, application 43, endpointId 01
dev:1372023-04-15 08:29:59.749infoZemismart ZigBee Wall Switch Multi-Gang Parent installed, typeName Zemismart ZigBee Wall Switch Multi-Gang, version 0.5.1 2023/04/05 7:27 AM, deviceNetworkId EFF3, zigbeeId A4C13813CDF5E141

The zigbee log showed two device while pairing, one that's the appropriate device and another without ID that I suppose is what you are referring to.

kkossev · April 15, 2023, 8:13am

logsOff() is a scheduled job from another driver, so I have added deleting of all previously scheduled jobs in the initialize() function.

08:29:59.749 - device installed (dni:EFF3)
08:30:00.067 - the requested data from the device is received successfuly
08:30:04.389 - received message from profileId:0104, clusterId:0006, value:00 - processed as 'Parent switch off' - all is OK here.
08:30:05.716 - this is the last message received ( dni:EFF3, cluster:0000, attrId:FFDF, encoding:42, command:0A ) - it's a Tuya specific check-in message, sent by many other Tuya devices periodically.

... and this is the last message received from the device. All later logs show only sent commands, but nothing received.

44C4 is not the NWK of the device that produced the logs before (it was EFF3 !)
The timestamps are between 8:48:39 and 8:48:

ZDO clusters 8004 and 8005 (active endpoints response) are usually sent by the device on a new device pairing or when the ''Get Info" button from the HE inbuilt driver "Device" was clicked..
Is this 44C4 device the same switch?

The timestamps for the "Zemismart Zigbee Wall Switc...." on the second screenshot are between 8:48:43 and 8:48:48:40. But the logs do not show what is the DNI / NWK of this device - probably y the same switch, but another attempt to pair made 18 minutes later?

Shortly, for me, this is a connectivity issue of this particular device with HE.

Sekenenz · April 15, 2023, 9:33am

Exactly. I paired again to get the zigbee log but it's the same device.

...and it is going back to where it came from.

Thanks a lot for your assistance.

jshimota · April 15, 2023, 3:17pm

@kkossev Clearing all states , preferences etc... should be a function of ALL drivers!!! heck, it should be a standard routine for Initialize... my 2 cents

kkossev · April 16, 2023, 6:56am

@jshimota fully agree!

system · April 15, 2024, 6:56am

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.