(EDGE Driver-Mc): Zigbee Switch Mc, Zigbee Switch Power Mc, Zigbee Multi Switch and Child Mc

Devices & Integrations Community Created Device Types
,
347

I can not download file.
Is better in copy and paste.
You can use in tools the paste them hidden detaills

I found that the logs match quite a bit.
It gives an error that the lua libraries identify a data type 06 as unknown and the message is not displayed.
I can’t find that type of data in the zigbee libraries either.

I don’t know if this has something to do with it or not, ask me in another forum

Also the TUYA cluster E000, attribute D003 has a similar text (AAAAAgAA) or (AAAAAgAABAAA) in both, in the documentation of TUYA I don’t find this correct

According to the documentation TUYA cluster E000 and the attribute 0xD003 should be:
0xD003 Inching switch (Tuya-specific attribute) type array (0x48)

DP19 Inching switch

Direction Cluster ID Command/Attribute ID Value
Client to server 0xE000 (Tuya private cluster 0) 0xFB: Tuya-specific command Payload
Server to client 0xE000 (Tuya private cluster 0) 0xD003: Tuya-specific attribute Payload

Payload format: 3 × n (n ≤ 6) Fields from the On/Off are specified for a single time node.

Feature Length Description
Channel ID + bit for enablement 1 byte Bit 0:
  • 0: Enable
  • 1: Disable

Bits 7 to 1: Channel ID.|
|Inching duration|2 bytes|00 3C is 0x003c in hex, representing 60 seconds.|

Example:
1-gang switch: 01 00 3C indicates the first gang is enabled, with an inching duration of 60 seconds.
Multi-gang switch: 00 00 3C 03 00 3C indicates the first gang is disabled, with an inching duration of 60 seconds, and the second

I’ll see what I can do or ask on the forums

1 Like
348

@Mariano_Colmenarejo

my friend, you are the best.

Ill try this as soon as i get back home. I’m on a trip, right now, but i let you know if it worked…

tks once again,

349

ALL right thanks for the efforts!

Its a Very long shot but i Will try my contact at chinese Manufacturer (Zemismart) and ask kindly to read your reports and doubts here, maybe foward to Company Dev. With Tuya direct contact…
Maybe…

2 Likes
350

Hey @Mariano_Colmenarejo Their engineer can´t speak english! :astonished:

Judy - Zemismart: hi Rodrigo， are you a software enginee？ Our enginer can not learn English, we now also seek a way to make our device worke ith smartthing after edge, could you help us ?

Judy - Zemismart: can let us know what we need supply , i will feedback to our company

Do you have any way to explain? Really can´t understand how since the code is probably in EN

351

He can use a translator like google, like everyone does when they don’t know a language

2 Likes
352

@Coelhorj @Liran1115

Please could you try install this driver version.

I changed some things

───────────────────────────────────────────────────
Name Zigbee Multi Switch and Child Mc
Version 2022-10-16T11:00:13.440958837
───────────────────────────────────────────────────

353

:pensive:
Not yet

But dont give up.
Waiting more info from Zemismart

354

@Mariano_Colmenarejo

Still the same thing.
both of them turn on.

connecting… connected
2022-10-16T12:46:20.138332485+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-10-16T12:46:20.161468485+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“switch2”,“positional_args”:{}}
2022-10-16T12:46:20.188529151+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-10-16T12:46:20.259545485+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:20.290259818+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:20.505848152+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-16T12:46:20.514177485+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x24E8, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x8C, rssi: -65, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7E, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-10-16T12:46:20.536062485+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-16T12:46:20.545961485+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-10-16T12:46:20.551859818+00:00 PRINT Zigbee Multi Switch and Child Mc <<<<<< default_response_handler >>>>>>
2022-10-16T12:46:20.557755818+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:20.564225818+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-16T12:46:20.572454818+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x24E8, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x8C, rssi: -65, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2A, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-10-16T12:46:20.590016485+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-16T12:46:20.600030485+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x24E8, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x8C, rssi: -65, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2C, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-10-16T12:46:20.616211485+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-16T12:46:20.621409152+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-16T12:46:20.626928818+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-16T12:46:20.633510152+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x24E8, lqi: 140, rssi: -65dBm”},“visibility”:{“displayed”:false}}
2022-10-16T12:46:20.652103818+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-10-16T12:46:20.673918818+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 1 value = true
2022-10-16T12:46:20.686285152+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:20.693129152+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-16T12:46:20.701440485+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x24E8, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x8C, rssi: -65, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2D, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-10-16T12:46:20.721926152+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-16T12:46:20.727592485+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-16T12:46:20.733111818+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-16T12:46:20.741362485+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x24E8, lqi: 140, rssi: -65dBm”},“visibility”:{“displayed”:false}}
2022-10-16T12:46:20.760113485+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-10-16T12:46:20.779304485+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 1 value = true
2022-10-16T12:46:20.789450152+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:20.796130485+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-16T12:46:20.804368152+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x24E8, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x9C, rssi: -61, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2B, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-10-16T12:46:20.821341485+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:20.829363485+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-16T12:46:20.834480152+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-16T12:46:20.840548818+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-16T12:46:20.846507485+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x24E8, lqi: 140, rssi: -65dBm”},“visibility”:{“displayed”:false}}
2022-10-16T12:46:20.864971485+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-10-16T12:46:20.884465818+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 2 value = true
2022-10-16T12:46:20.896791818+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:20.905976819+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:20.914194819+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-16T12:46:20.919311152+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-16T12:46:20.924838819+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-16T12:46:20.931367485+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x24E8, lqi: 156, rssi: -61dBm”},“visibility”:{“displayed”:false}}
2022-10-16T12:46:20.950055152+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-10-16T12:46:20.966084819+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 2 value = true
2022-10-16T12:46:20.976655485+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:20.987086485+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:20.994681152+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:22.247868486+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-16T12:46:22.254173819+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-10-16T12:46:22.272292152+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:22.704635486+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-16T12:46:22.710776819+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-10-16T12:46:22.725750486+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:22.795691819+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-16T12:46:22.802278486+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-10-16T12:46:22.817295153+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:22.904536819+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-16T12:46:22.910720819+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-10-16T12:46:22.925605153+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:22.983702486+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-16T12:46:22.990143153+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-10-16T12:46:23.005522153+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:24.932912154+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-10-16T12:46:24.960228487+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“off”,“component”:“switch2”,“positional_args”:{}}
2022-10-16T12:46:24.966087154+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-10-16T12:46:25.000900487+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:25.014822487+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:25.085760154+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-16T12:46:25.104596487+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x24E8, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x9C, rssi: -61, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7F, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >
2022-10-16T12:46:25.133476154+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-16T12:46:25.150382487+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x24E8, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x9C, rssi: -61, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2E, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-10-16T12:46:25.177260154+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-16T12:46:25.182335487+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-10-16T12:46:25.192320487+00:00 PRINT Zigbee Multi Switch and Child Mc <<<<<< default_response_handler >>>>>>
2022-10-16T12:46:25.200307487+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:25.212090821+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-16T12:46:25.231785154+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x24E8, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x9C, rssi: -61, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x30, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-10-16T12:46:25.267965487+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-16T12:46:25.274698154+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-16T12:46:25.313420154+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-16T12:46:25.328456487+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x24E8, lqi: 156, rssi: -61dBm”},“visibility”:{“displayed”:false}}
2022-10-16T12:46:25.377848154+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-10-16T12:46:25.409095154+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 1 value = false
2022-10-16T12:46:25.434548154+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:25.442541154+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-16T12:46:25.454232821+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x24E8, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x9C, rssi: -61, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x31, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-10-16T12:46:25.499403487+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-16T12:46:25.507838821+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-16T12:46:25.513897487+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-16T12:46:25.527740821+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x24E8, lqi: 156, rssi: -61dBm”},“visibility”:{“displayed”:false}}
2022-10-16T12:46:25.550059154+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-10-16T12:46:25.567615154+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 1 value = false
2022-10-16T12:46:25.577426821+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:25.584295821+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-16T12:46:25.593216487+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x24E8, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x90, rssi: -64, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2F, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-10-16T12:46:25.609405487+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:25.617560487+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-16T12:46:25.623504154+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-16T12:46:25.629594154+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-16T12:46:25.635672487+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x24E8, lqi: 156, rssi: -61dBm”},“visibility”:{“displayed”:false}}
2022-10-16T12:46:25.655848821+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-10-16T12:46:25.675000487+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 2 value = false
2022-10-16T12:46:25.687540154+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:25.694187154+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:25.702126487+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-16T12:46:25.707346154+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-16T12:46:25.713002821+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-16T12:46:25.719005154+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x24E8, lqi: 144, rssi: -64dBm”},“visibility”:{“displayed”:false}}
2022-10-16T12:46:25.740982821+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-10-16T12:46:25.757120487+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 2 value = false
2022-10-16T12:46:25.767807821+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:25.779623154+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:25.789099821+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:27.014750155+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-16T12:46:27.021115155+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-10-16T12:46:27.041432155+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:27.444676822+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-16T12:46:27.450968155+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-10-16T12:46:27.465741155+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:27.585034155+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-16T12:46:27.591453155+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-10-16T12:46:27.606148488+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:27.694846488+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-16T12:46:27.701040155+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-10-16T12:46:27.715775488+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-16T12:46:27.776327488+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-16T12:46:27.782322155+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 7a7d6483-02ad-4dff-b92e-3c7955c6e0a3 [0x24E8] (TS0002 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-10-16T12:46:27.798283822+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled

355

@Coelhorj @Liran1115

Are you uninstall and reinstall device?

356

@Mariano_Colmenarejo

yea.

I deleted it from the smartthings app and search for new device in pairing mode.

1 Like
357

I didnt (my fault) but still the same.
But THIS TIME just at FIRST press (APP) switch TWO Turned on alone. After that started same inching behavior as before

A brief update:
That behavior i described before also occurs with Switch one after FIRST pairing and turning OFF the Switch.
If o turn any ON, same “follow” problem

:point_up_2: :point_up_2: :point_up_2: :point_up_2: :point_up_2: :point_up_2:

1 Like
358

Hi @Mariano_Colmenarejo , any chance you could add the following 3A Smart Switches?

You already have a couple of 3A switches, but seemingly not this one. It’s an Australian smart plug.

Data * zigbeeNodeType: ROUTER

  • firmwareManufacturerCode: 4478
  • firmwareFullVersion: 00000001
  • application: 01
  • endpointId: 0B
  • firmwareImageType: 0
  • manufacturer: 3A Smart Home DE
  • model: LXN56-0S27LX1.3
    Raw Description 0B C05E 0000 01 07 0000 0004 0003 0006 0005 1000 0008 01 0019

These next two are dual GPOs. I think you have similar devices already - these are Australian versions.

Data * zigbeeNodeType: ROUTER

  • firmwareManufacturerCode: 4478
  • firmwareFullVersion: 00000001
  • application: 01
  • endpointId: 01
  • firmwareImageType: 256
  • manufacturer: 3A Smart Home DE
  • model: LXN56-TS27LX1.2
  • onOff: catchall
    Raw Description 01 0104 0100 01 06 0000 0004 0003 0006 0005 1000 01 0019

Data * zigbeeNodeType: ROUTER

  • firmwareManufacturerCode: 4478
  • firmwareFullVersion: 00000001
  • application: 01
  • endpointId: 0B
  • firmwareImageType: 0
  • manufacturer: FeiBit
  • model: FNB56-SKT1DHG1.4
    Raw Description 0B C05E 0000 01 07 0000 0004 0003 0006 0005 1000 0008 01 0019

And finally (?), a single gang light switch, a 3-gang light switch and a 4-gang light switch

Data * zigbeeNodeType: ROUTER

  • firmwareManufacturerCode: 4478
  • firmwareFullVersion: 00000001
  • application: 01
  • endpointId: 01
  • firmwareImageType: 0
  • manufacturer: 3A Smart Home DE
  • model: LXN-3S27LX1.0
  • onOff: catchall
    Raw Description 01 C05E 0000 01 07 0000 0004 0003 0006 0005 1000 0008 01 0019

Data * zigbeeNodeType: ROUTER

  • firmwareManufacturerCode: 4478
  • firmwareFullVersion: 00000001
  • application: 01
  • endpointId: 01
  • firmwareImageType: 0
  • manufacturer: 3A Smart Home DE
  • model: LXN-3S27LX1.0
  • onOff: catchall
    Raw Description 01 C05E 0000 01 07 0000 0004 0003 0006 0005 1000 0008 01 0019

Data * zigbeeNodeType: ROUTER

  • application: 01
  • endpointId: 13
  • manufacturer: Feibit Inc co.
  • model: FB56+ZSW1JKJ2.7
  • onOff: catchall
    Raw Description 13 0104 0002 00 05 0000 0003 0004 0005 0006 00

Thanks for all your amazing work, and sorry for swamping you.

Do you have any way of donating to you for your work?

361

Sorry these two (single and 3 gang) are the same manufacturer and model, is an error?

362

Added to this driver version

───────────────────────────────────────────────────
 Name         Zigbee Switch Mc
 Version      2022-10-19T11:40:36.132772629        
───────────────────────────────────────────────────
  - id: "3A SMart/LXN56-0S27LX1.3"
    deviceLabel: 3A SMart Switch
    manufacturer: 3A SMart Home DE
    model: LXN56-0S27LX1.3
    deviceProfileName: single-switch-plug
363

Added to this driver version

───────────────────────────────────────────────────
 Name         Zigbee Multi Switch and Child Mc
 Version      2022-10-19T12:27:04.348948652
───────────────────────────────────────────────────
  - id: "3A Smart/LXN56-TS27LX1.2"
    deviceLabel: 3A Smart 2 Switch
    manufacturer: 3A Smart Home DE
    model: LXN56-TS27LX1.2
    deviceProfileName: two-switch
  - id: "FeiBit/FNB56-SKT1DHG1.4"
    deviceLabel: FeiBit 2 Switch
    manufacturer: FeiBit
    model: FNB56-SKT1DHG1.4
    deviceProfileName: two-switch
  - id: "FeiBit/FB56-ZSW1JKJ2.7"
    deviceLabel: FeiBit 2 Switch
    manufacturer: Feibit Inc co.
    model: FB56+ZSW1JKJ2.7
    deviceProfileName: four-switch
364

You’re the best!

365

A couple more fingerprint supports to request:
014F/5457/3033 - Linear/GoControl accessory switch (WT00Z-1)
014F/5257/3533 - Linear/GoControl switch (WS15Z-1)
I saw some other Linear/GoControl fingerprints in there, but I have these 2 devices and didn’t see them there. TIA!

366

Apologies Mariano, I must have copied the 3-gang switch twice.

Here’s the single light switch:

Data * application: 01

  • endpointId: 0B
  • firmwareFullVersion: 00000001
  • firmwareImageType: 0
  • firmwareManufacturerCode: 4478
  • manufacturer: 3A Smart Home DE
  • model: LXN-1S27LX1.0
  • zigbeeNodeType: ROUTER
    Raw Description 0B C05E 0000 01 07 0000 0004 0003 0006 0005 1000 0008 01 0019

And this is the triple light switch
Data * application: 01

  • endpointId: 01
  • firmwareFullVersion: 00000001
  • firmwareImageType: 0
  • firmwareManufacturerCode: 4478
  • manufacturer: 3A Smart Home DE
  • model: LXN-3S27LX1.0
  • onOff: catchall
  • zigbeeNodeType: ROUTER
    Raw Description 01 C05E 0000 01 07 0000 0004 0003 0006 0005 1000 0008 01 0019
367

Thanks Mariano. I have migrated across most of my devices. For some reason, these Smart Plugs are still picking up the old Zigbee Switch DH and not picking up your Edge driver. Any ideas?

Data * application: 01

  • endpointId: 0B
  • manufacturer: 3A Smart Home DE
  • model: LXN56-0S27LX1.3
  • zigbeeNodeType: ROUTER
    Raw Description 0B C05E 0000 01 07 0000 0004 0003 0006 0005 1000 0008 01 0019
368

Added to this driver version

───────────────────────────────────────────────────
 Name         Zigbee Switch Mc
 Version      2022-10-20T09:47:59.853934965
───────────────────────────────────────────────────
  - id: "3A SMart/LXN-1S27LX1.0"
    deviceLabel: 3A SMart Switch
    manufacturer: 3A SMart Home DE
    model: LXN-1S27LX1.0
    deviceProfileName: single-switch

This device was added time ago to this driver

───────────────────────────────────────────────────
 Name         Zigbee Multi Switch and Child Mc
 Version      2022-10-20T09:52:35.56515183
───────────────────────────────────────────────────

This device is added fine to driver Zigbee Switch Mc.
may be have you a custom DTH with this fingerprints?