(EDGE Driver-Mc) Zigbee switch MC, Zigbee switch power MC, Zigbee multi switch and child MC

@Coelhorj @Liran1115

I made some changes, but I have implemented the same solution as Hubitat and Zigbee2mqtt for these same devices and it seems to work for them.

───────────────────────────────────────────────────
 Name         Zigbee Multi Switch and Child Mc     
 Version      2022-10-13T11:42:19.485726074        
───────────────────────────────────────────────────

@Mariano_Colmenarejo

still the same :sob:
power on both of the lamps together

Same here…

:pensive:

Please, could you send a log of the device pairing?
I like see if It’s similar to log of the @Liran1115

My apologies but How can i collect that log?

You would have to install the CLI on a PC following these steps for windows

Edge Driver or Device Handeler for a TUYA (Zemismart) Zigbee plug with energy mesurment capabilities - #18 by Mariano_Colmenarejo

Manufacturer: _TZ3000_vjhcenzo Model: TS0003
[1]: Identify, Groups, Scenes, OnOff, 0xE000, 0xE001, Basic [2]: Groups, Scenes, OnOff, 0xE001 [3]: Groups, Scenes, OnOff, 0xE001 [242]:
2022-10-13T23:28:08.939670833+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received lifecycle event: added
2022-10-13T23:28:08.974937857+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler device_lifecycle
2022-10-13T23:28:08.981331659+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received lifecycle event: doConfigure
2022-10-13T23:28:08.990739286+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-10-13T23:28:08.996040634+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:09.004569367+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-10-13T23:28:09.009873381+00:00 PRINT Zigbee Multi Switch and Child Mc device_network_id >>> 988B
2022-10-13T23:28:09.015428935+00:00 PRINT Zigbee Multi Switch and Child Mc label >>> TS0003 Switch
2022-10-13T23:28:09.021264349+00:00 PRINT Zigbee Multi Switch and Child Mc parent_device_id >>> 945b94b6-57fc-4228-b56d-ebcf042c8661
2022-10-13T23:28:09.026533713+00:00 PRINT Zigbee Multi Switch and Child Mc manufacturer >>>
2022-10-13T23:28:09.031859049+00:00 PRINT Zigbee Multi Switch and Child Mc model >>>
2022-10-13T23:28:09.037017135+00:00 PRINT Zigbee Multi Switch and Child Mc vendor_provided_label >>>
2022-10-13T23:28:09.043128412+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch3Child Preference value: No
2022-10-13T23:28:09.048482400+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> version Preference value:
2022-10-13T23:28:09.054289162+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> restoreState Preference value: 255
2022-10-13T23:28:09.059552529+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> signalMetricsVisibles Preference value: No
2022-10-13T23:28:09.064828556+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch1Child Preference value: No
2022-10-13T23:28:09.070438416+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch2Child Preference value: No
2022-10-13T23:28:09.075691455+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> changeProfileThreeSw Preference value: Single
2022-10-13T23:28:09.189349931+00:00 PRINT Zigbee Multi Switch and Child Mc Parent_devices[97a3eb51-9928-4894-8b1c-3863b566605a]>>>>>> <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)>
2022-10-13T23:28:09.196880830+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Read Basic clusters attributes >>>
2022-10-13T23:28:09.203733069+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0004 > > >
2022-10-13T23:28:09.226358417+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-10-13T23:28:09.241269625+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0001 > > >
2022-10-13T23:28:09.262742883+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0005 > > >
2022-10-13T23:28:09.283602448+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0007 > > >
2022-10-13T23:28:09.312414035+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0xFFFD > > >
2022-10-13T23:28:09.334933769+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0xFFFE > > >
2022-10-13T23:28:09.360652903+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Write restore state >>>
2022-10-13T23:28:09.368363379+00:00 PRINT Zigbee Multi Switch and Child Mc <<<< Componente, end_point >>>> main 1
2022-10-13T23:28:09.376122831+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x4003, DataType: Enum8, data: 0xFF > > > >
2022-10-13T23:28:09.395612415+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x8002, DataType: Enum8, data: 0x02 > > > >
2022-10-13T23:28:09.428574259+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Write restore state >>>
2022-10-13T23:28:09.437695696+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Write restore state >>>
2022-10-13T23:28:09.443591746+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:09.454036855+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:09.474397003+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xD0, rssi: -48, body_length: 0x0018, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x5E, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0004, ZclStatus: SUCCESS, DataType: CharString, ManufacturerName: “_TZ3000_vjhcenzo” > > > >
2022-10-13T23:28:09.518777801+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-10-13T23:28:09.548264051+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138758FED5B51, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D97000207265F, dest_endpoint: 0x01 > > >
2022-10-13T23:28:09.562106126+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-10-13T23:28:09.610453607+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x02, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138758FED5B51, src_endpoint: 0x02, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D97000207265F, dest_endpoint: 0x01 > > >
2022-10-13T23:28:09.637550052+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-10-13T23:28:09.652478917+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x03, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138758FED5B51, src_endpoint: 0x03, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D97000207265F, dest_endpoint: 0x01 > > >
2022-10-13T23:28:09.683455421+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-10-13T23:28:09.698514888+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:09.705768925+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:09.728874367+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xD0, rssi: -48, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x5F, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Uint8, ZCLVersion: 0x03 > > > >
2022-10-13T23:28:09.893383071+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:09.901237476+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:09.911678253+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xD0, rssi: -48, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x60, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0001, ZclStatus: SUCCESS, DataType: Uint8, ApplicationVersion: 0x51 > > > >
2022-10-13T23:28:09.955212808+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:09.962255618+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:09.973404041+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xD0, rssi: -48, body_length: 0x000E, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x61, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0005, ZclStatus: SUCCESS, DataType: CharString, ModelIdentifier: “TS0003” > > > >
2022-10-13T23:28:10.002360555+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:10.009655240+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:10.018295917+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xD0, rssi: -48, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x62, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0007, ZclStatus: SUCCESS, DataType: Enum8, PowerSource: PowerSource[SINGLE_PHASE_MAINS] > > > >
2022-10-13T23:28:10.065331721+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:10.073068850+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:10.083837463+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xD0, rssi: -48, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x63, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0xFFFD, ZclStatus: SUCCESS, DataType: Uint16, Uint16: 0x0002 > > > >
2022-10-13T23:28:10.113392012+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:10.120469805+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:10.131379014+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xD0, rssi: -48, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x64, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0xFFFE, ZclStatus: SUCCESS, DataType: Enum8, Enum8: 0x00 > > > >
2022-10-13T23:28:10.173278054+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:10.183848100+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:10.208527754+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x65, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x4003 > > > >
2022-10-13T23:28:10.274368483+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:10.292686320+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:10.351876377+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x66, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2022-10-13T23:28:10.396867870+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:10.405905349+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:10.426692950+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xD0, rssi: -48, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x25 >, < BindRequestResponse || status: 0x00 > > >
2022-10-13T23:28:10.471405582+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:10.480218174+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:10.497260981+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x67, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: SUCCESS, direction: 0x00, attr_id: 0x0000 > > > >
2022-10-13T23:28:10.578511336+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:10.586521662+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:10.596858824+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xD0, rssi: -48, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x26 >, < BindRequestResponse || status: 0x00 > > >
2022-10-13T23:28:10.652271437+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:10.661311582+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:10.672456673+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xF2, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x8002, DataType: Enum8, Enum8: 0x02 > > > >
2022-10-13T23:28:10.721524793+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:10.833299878+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:10.862623875+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xCC, rssi: -49, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x27 >, < BindRequestResponse || status: 0x00 > > >
2022-10-13T23:28:10.973096944+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:11.006981327+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:11.108162711+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x68, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: SUCCESS, direction: 0x00, attr_id: 0x0000 > > > >
2022-10-13T23:28:12.060863122+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:12.253873902+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:12.300562213+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE001 >, lqi: 0xD0, rssi: -48, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xF3, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xD010, DataType: Enum8, Enum8: 0x02 > > > >
2022-10-13T23:28:13.925401053+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:14.089535279+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:14.146652706+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE001 >, lqi: 0xD0, rssi: -48, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xF4, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xD010, DataType: Enum8, Enum8: 0x02 > > > >
2022-10-13T23:28:14.258471768+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:14.266839249+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:14.289140426+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x03, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x69, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: SUCCESS, direction: 0x00, attr_id: 0x0000 > > > >
2022-10-13T23:28:14.338524055+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:14.373468574+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:14.388350796+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x03, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE001 >, lqi: 0xD0, rssi: -48, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xF5, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xD010, DataType: Enum8, Enum8: 0x02 > > > >
2022-10-13T23:28:14.571680752+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:14.609525820+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:14.636755198+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE000 >, lqi: 0xD0, rssi: -48, body_length: 0x0013, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xF6, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xD003, DataType: CharString, CharString: “AAAAAgAABAAA” > > > >
2022-10-13T23:28:14.734110496+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:14.763704692+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:14.772526612+00:00 WARN Zigbee Multi Switch and Child Mc Error encountered parsing Zigbee message defaulting to generic body: [string “st/zigbee/data_types/ZigbeeDataType.lua”]:32: DataType value is an unrecognized data type: 0x06
2022-10-13T23:28:14.779819964+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE000 >, lqi: 0xD0, rssi: -48, body_length: 0x0009, GenericBody: 08 F7 0A 01 D0 48 02 00 06 >
2022-10-13T23:28:14.818290052+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:14.826798796+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:14.838332359+00:00 WARN Zigbee Multi Switch and Child Mc Error encountered parsing Zigbee message defaulting to generic body: [string “st/buf.lua”]:695: buffer too short
2022-10-13T23:28:14.847456129+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE000 >, lqi: 0xD0, rssi: -48, body_length: 0x0009, GenericBody: 08 F8 0A 02 D0 48 02 00 0A >
2022-10-13T23:28:14.878277377+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:14.888290035+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:14.903034659+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0021, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xF9, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 >, < AttributeRecord || AttributeId: 0x8001, DataType: Enum8, Enum8: 0x01 >, < AttributeRecord || AttributeId: 0x8002,

DataType: Enum8, Enum8: 0x02 >, < AttributeRecord || AttributeId: 0x5000, DataType: Enum8, Enum8: 0x01 >, < AttributeRecord || AttributeId: 0x8000, DataType: Boolean, Boolean: false > > > >
2022-10-13T23:28:14.938342329+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:14.951590702+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler device_lifecycle
2022-10-13T23:28:14.984158077+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received lifecycle event: infoChanged
2022-10-13T23:28:14.994542215+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:15.003857889+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:15.012935014+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE001 >, lqi: 0xD0, rssi: -48, body_length: 0x000B, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xFA, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xD010, DataType: Enum8, Enum8: 0x02 >, < AttributeRecord || AttributeId: 0xD030, DataType: Enum8, Enum8: 0x00 > > > >
2022-10-13T23:28:15.042979651+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-13T23:28:15.048722445+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-13T23:28:15.054445582+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-13T23:28:15.060603502+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x988B, lqi: 208, rssi: -48dBm”},“visibility”:{“displayed”:false}}
2022-10-13T23:28:15.101926830+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-10-13T23:28:15.121001954+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 1 value = true
2022-10-13T23:28:15.133034268+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:15.141303132+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:15.152330615+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0011, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xFB, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 > > > >
2022-10-13T23:28:15.181080566+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-10-13T23:28:15.186753395+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]= No
2022-10-13T23:28:15.192285961+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: switch3Child oldPreferenceValue: nil newParameterValue: >> No
2022-10-13T23:28:15.197528338+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]=
2022-10-13T23:28:15.203114877+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: version oldPreferenceValue: nil newParameterValue: >>
2022-10-13T23:28:15.208426553+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]= 255
2022-10-13T23:28:15.213920138+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: restoreState oldPreferenceValue: nil newParameterValue: >> 255
2022-10-13T23:28:15.220014756+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Write restore state >>>
2022-10-13T23:28:15.225693249+00:00 PRINT Zigbee Multi Switch and Child Mc <<<< Componente, end_point >>>> main 1
2022-10-13T23:28:15.232796029+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x4003, DataType: Enum8, data: 0xFF > > > >
2022-10-13T23:28:15.247265457+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x8002, DataType: Enum8, data: 0x02 > > > >
2022-10-13T23:28:15.258980263+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Write restore state >>>
2022-10-13T23:28:15.264624440+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Write restore state >>>
2022-10-13T23:28:15.280578126+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]= No
2022-10-13T23:28:15.285975759+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: signalMetricsVisibles oldPreferenceValue: nil newParameterValue: >> No
2022-10-13T23:28:15.301708222+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]= No
2022-10-13T23:28:15.307440021+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: switch1Child oldPreferenceValue: nil newParameterValue: >> No
2022-10-13T23:28:15.313369055+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]= No
2022-10-13T23:28:15.328504151+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: switch2Child oldPreferenceValue: nil newParameterValue: >> No
2022-10-13T23:28:15.333950093+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]= Single
2022-10-13T23:28:15.340445177+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: changeProfileThreeSw oldPreferenceValue: nil newParameterValue: >> Single
2022-10-13T23:28:15.363604259+00:00 PRINT Zigbee Multi Switch and Child Mc Device ID <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)>
2022-10-13T23:28:15.371371373+00:00 PRINT Zigbee Multi Switch and Child Mc Manufacturer >>> _TZ3000_vjhcenzo Manufacturer_Len >>> 16
2022-10-13T23:28:15.377022546+00:00 PRINT Zigbee Multi Switch and Child Mc Model >>> TS0003 Model_len >>> 6
2022-10-13T23:28:15.386724026+00:00 PRINT Zigbee Multi Switch and Child Mc Memory >>>>>>> 1696.123046875 Kbytes
2022-10-13T23:28:15.391957741+00:00 PRINT Zigbee Multi Switch and Child Mc <<<<< Firmware Version >>>>> Unknown
2022-10-13T23:28:15.399454658+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:15.406843628+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:15.419337045+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE001 >, lqi: 0xD0, rssi: -48, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xFC, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xD010, DataType: Enum8, Enum8: 0x02 > > > >
2022-10-13T23:28:15.453811466+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:15.461273066+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:15.473067833+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x03, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0011, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xFD, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 > > > >
2022-10-13T23:28:15.500898244+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:15.508341520+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:15.518797623+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x03, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE001 >, lqi: 0xD0, rssi: -48, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xFE, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xD010, DataType: Enum8, Enum8: 0x02 > > > >
2022-10-13T23:28:15.551982023+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-13T23:28:15.566458447+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-13T23:28:15.572920548+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-13T23:28:15.611345326+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x988B, lqi: 208, rssi: -48dBm”},“visibility”:{“displayed”:false}}
2022-10-13T23:28:15.641189063+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-10-13T23:28:15.667285675+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 2 value = true
2022-10-13T23:28:15.684515056+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:15.698894530+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-10-13T23:28:15.770901175+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:15.779002122+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:15.799124723+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x6A, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x4003 > > > >
2022-10-13T23:28:15.850607968+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-13T23:28:15.867908647+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-13T23:28:15.883286954+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-13T23:28:15.907848001+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x988B, lqi: 208, rssi: -48dBm”},“visibility”:{“displayed”:false}}
2022-10-13T23:28:15.963267610+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch3”,“state”:{“value”:“on”}}
2022-10-13T23:28:15.998130503+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 3 value = true
2022-10-13T23:28:16.016389369+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:16.029379538+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:16.038889780+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x6B, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2022-10-13T23:28:16.066956740+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:16.074977394+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:16.097846620+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x00, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x8002, DataType: Enum8, Enum8: 0x02 > > > >
2022-10-13T23:28:16.158090150+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:16.166160446+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:16.177651365+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE001 >, lqi: 0xD0, rssi: -48, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x01, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xD010, DataType: Enum8, Enum8: 0x02 > > > >
2022-10-13T23:28:16.206430635+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received command: {“args”:{},“capability”:“refresh”,“command”:“refresh”,“component”:“main”,“positional_args”:{}}
2022-10-13T23:28:16.212804779+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-10-13T23:28:16.221667013+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-10-13T23:28:16.245634356+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-10-13T23:28:16.261678997+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x988B, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-10-13T23:28:16.274360986+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:16.286337661+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:16.307988497+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE001 >, lqi: 0xD0, rssi: -48, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x02, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xD010, DataType: Enum8, Enum8: 0x02 > > > >
2022-10-13T23:28:16.351992817+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:16.368459913+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:16.429810889+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x03, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE001 >, lqi: 0xD0, rssi: -48, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x03, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xD010, DataType: Enum8, Enum8: 0x02 > > > >
2022-10-13T23:28:16.708739354+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:16.800278895+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:16.858381496+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x03, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x6C, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-10-13T23:28:17.648566872+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:18.130401168+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:18.249390310+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x6D, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-10-13T23:28:18.495778055+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:18.532394737+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-13T23:28:18.570458362+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x988B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xD0, rssi: -48, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x6E, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-10-13T23:28:18.644223128+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:18.677224952+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:18.691406858+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:18.707023379+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-13T23:28:18.713067689+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-13T23:28:18.721008716+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-13T23:28:18.732387691+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x988B, lqi: 208, rssi: -48dBm”},“visibility”:{“displayed”:false}}
2022-10-13T23:28:18.767481801+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch3”,“state”:{“value”:“on”}}
2022-10-13T23:28:18.797017693+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 3 value = true
2022-10-13T23:28:18.809465799+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:18.816745824+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-13T23:28:18.822172109+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-13T23:28:18.827950219+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-13T23:28:18.834079486+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x988B, lqi: 208, rssi: -48dBm”},“visibility”:{“displayed”:false}}
2022-10-13T23:28:18.852723826+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-10-13T23:28:18.872682508+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 1 value = true
2022-10-13T23:28:18.884567896+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:18.893154600+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-13T23:28:18.899809271+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-13T23:28:18.905552731+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-13T23:28:18.911661342+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x988B, lqi: 208, rssi: -48dBm”},“visibility”:{“displayed”:false}}
2022-10-13T23:28:18.930689823+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-10-13T23:28:18.950321003+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 2 value = true
2022-10-13T23:28:18.964718134+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:18.972285015+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:18.979716964+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:18.986910366+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:18.998072448+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-13T23:28:19.004468915+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-10-13T23:28:19.023154568+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:19.034505556+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-13T23:28:19.041614+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-10-13T23:28:19.057280163+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:19.067798901+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-13T23:28:19.073930834+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-10-13T23:28:19.089681621+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:20.815811790+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-13T23:28:20.822435810+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-10-13T23:28:20.839960044+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:20.894065644+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-13T23:28:20.900395477+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-10-13T23:28:20.918392474+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled
2022-10-13T23:28:20.975072787+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-13T23:28:20.981267355+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 97a3eb51-9928-4894-8b1c-3863b566605a [0x988B] (TS0003 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-10-13T23:28:21.002122255+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0003 Switch device thread event handled

When i switch On main channel:
Log Txt Zip

TXT is easier and clean :wink:

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

@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,

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

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

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

2 Likes

@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
───────────────────────────────────────────────────

:pensive:
Not yet

But dont give up.
Waiting more info from Zemismart

@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

@Coelhorj @Liran1115

Are you uninstall and reinstall device?

@Mariano_Colmenarejo

yea.

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

1 Like

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