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

Andy_Godber · October 11, 2022, 3:43pm

Thanks Mariano - on the voltage, I noted it was available when I was messing around with some of the ‘inbuilt’ device through the IDE.
For example, the SMARTENIT device showed the voltage - perhaps that driver could be used to extract the cluser info (when you have time )

Jansi · October 11, 2022, 8:51pm

Hi, is there a downloadlink to download this edge driver?

NickA · October 11, 2022, 9:29pm

It is towards the very beginning of the thread

Mariano_Colmenarejo · October 12, 2022, 11:31am

@Coelhorj and @Liran1115
https://community.smartthings.com/t/post-requests-for-edge-drivers-here-community-created/237327/927?u=mariano_colmenarejo

Please, could you try with new version with yours multi switches devices?
I found some things in others forum 2mqtt… and I implemented it to test

───────────────────────────────────────────────────
 Name         Zigbee Multi Switch and Child Mc     
 Version      2022-10-12T15:06:19.100815561        
───────────────────────────────────────────────────

Liran1115 · October 12, 2022, 4:20pm

Hi @Mariano_Colmenarejo

I just updated right now the driver and try to delete the module and add it again.
Same problem, turnning on both of the lamps together when I am press on switch 2

Open to see the logs

connecting… connected
2022-10-12T16:16:44.806923341+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler device_lifecycle2022-10-12T16:16:44.863476008+00:00 TRACE Zigbee Multi Switch and Child Mc Zigbee Device: 74d8597d-5696-478c-8393-10957ec6cdb8
Manufacturer: _TZ3000_zmy4lslw Model: TS0002
[1]: Identify, Groups, Scenes, OnOff, SimpleMetering, ElectricalMeasurement, 0xE000, 0xE001, Basic [2]: Groups, Scenes, OnOff [242]:
2022-10-12T16:16:44.877827341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received lifecycle event: added
2022-10-12T16:16:44.926686341+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler device_lifecycle2022-10-12T16:16:44.941075341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received lifecycle event: doConfigure
2022-10-12T16:16:44.970641341+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:16:44.977797008+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:44.984519341+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:16:44.997159341+00:00 PRINT Zigbee Multi Switch and Child Mc device_network_id >>> 02E6
2022-10-12T16:16:45.007914341+00:00 PRINT Zigbee Multi Switch and Child Mc label >>> TS0002 Switch
2022-10-12T16:16:45.020889674+00:00 PRINT Zigbee Multi Switch and Child Mc parent_device_id >>> 2bb61878-8883-4aa4-88fa-3a657f9489a1
2022-10-12T16:16:45.027830008+00:00 PRINT Zigbee Multi Switch and Child Mc manufacturer >>>
2022-10-12T16:16:45.043658341+00:00 PRINT Zigbee Multi Switch and Child Mc model >>>
2022-10-12T16:16:45.060754341+00:00 PRINT Zigbee Multi Switch and Child Mc vendor_provided_label >>>
2022-10-12T16:16:45.067838008+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> restoreState Preference value: 255
2022-10-12T16:16:45.073468008+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch2Child Preference value: No
2022-10-12T16:16:45.084572341+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> signalMetricsVisibles Preference value: No
2022-10-12T16:16:45.090243341+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch1Child Preference value: No
2022-10-12T16:16:45.095619341+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> changeProfileTwoSwPw Preference value: Single
2022-10-12T16:16:45.110389008+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> version Preference value:
2022-10-12T16:16:45.115791008+00:00 PRINT Zigbee Multi Switch and Child Mc Parent_devices[74d8597d-5696-478c-8393-10957ec6cdb8]>>>>>> <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)>
2022-10-12T16:16:45.121116674+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Read Basic clusters attributes >>>
2022-10-12T16:16:45.128790008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0004 > > >
2022-10-12T16:16:45.143013341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-10-12T16:16:45.168847341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0001 > > >
2022-10-12T16:16:45.185508341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0004 > > >
2022-10-12T16:16:45.214689008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0005 > > >
2022-10-12T16:16:45.231657674+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0007 > > >
2022-10-12T16:16:45.256086341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0xFFFE > > >
2022-10-12T16:16:45.278312341+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Write restore state >>>
2022-10-12T16:16:45.286286008+00:00 PRINT Zigbee Multi Switch and Child Mc <<<< Componente, end_point >>>> main 12022-10-12T16:16:45.294790341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, 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-12T16:16:45.315015341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, 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-12T16:16:45.342411674+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Write restore state >>>
2022-10-12T16:16:45.349607008+00:00 PRINT Zigbee Multi Switch and Child Mc <<<< Componente, end_point >>>> switch2
2
2022-10-12T16:16:45.361762008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x4003, DataType: Enum8, data: 0xFF > > > >
2022-10-12T16:16:45.387006008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x8002, DataType: Enum8, data: 0x02 > > > >
2022-10-12T16:16:45.399673008+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:45.420773674+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:45.437196341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0x88, rssi: -66, body_length: 0x0018, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x03, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0004, ZclStatus: SUCCESS, DataType: CharString, ManufacturerName: “_TZ3000_zmy4lslw” > > > >
2022-10-12T16:16:45.461565674+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:16:45.489113008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C1381B3361FFD3, src_endpoint: 0x01, cluster: ElectricalMeasurement, dest_addr_mode: 0x03, dest_address: 286D9700020A70CC, dest_endpoint: 0x01 > > >
2022-10-12T16:16:45.507899008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x050B, DataType: Int16, minimum_reporting_interval: 0x0001, maximum_reporting_interval: 0x0E10, reportable_change: 1 > > > >
2022-10-12T16:16:45.538896341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C1381B3361FFD3, src_endpoint: 0x01, cluster: SimpleMetering, dest_addr_mode: 0x03, dest_address: 286D9700020A70CC, dest_endpoint: 0x01 > > >
2022-10-12T16:16:45.568219008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0400, DataType: Int24, minimum_reporting_interval: 0x0001, maximum_reporting_interval: 0x0E10, reportable_change: 1 > > > >
2022-10-12T16:16:45.597073341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Uint48, minimum_reporting_interval: 0x0005, maximum_reporting_interval: 0x0E10, reportable_change: 0x000000000001 > > > >
2022-10-12T16:16:45.621579674+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C1381B3361FFD3, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D9700020A70CC, dest_endpoint: 0x01 > > >
2022-10-12T16:16:45.647007341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, 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-12T16:16:45.669833008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x02, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C1381B3361FFD3, src_endpoint: 0x02, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D9700020A70CC, dest_endpoint: 0x01 > > >
2022-10-12T16:16:45.691647674+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, 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-12T16:16:45.705382674+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0605 > > >
2022-10-12T16:16:45.721279008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0604 > > >
2022-10-12T16:16:45.744486674+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0302 > > >
2022-10-12T16:16:45.791974008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0301 > > >
2022-10-12T16:16:45.814782008+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:45.822934341+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:45.833418008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0x88, rssi: -66, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x04, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Uint8, ZCLVersion: 0x03 > > > >
2022-10-12T16:16:45.902200674+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:45.919679008+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:45.936107008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0x88, rssi: -66, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x05, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0001, ZclStatus: SUCCESS, DataType: Uint8, ApplicationVersion: 0x46 > > > >
2022-10-12T16:16:45.960503674+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:45.974107341+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:45.986670008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0x88, rssi: -66, body_length: 0x0018, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x06, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0004, ZclStatus: SUCCESS, DataType: CharString, ManufacturerName: “_TZ3000_zmy4lslw” > > > >
2022-10-12T16:16:46.007231341+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:46.014026008+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:46.022504341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0x88, rssi: -66, body_length: 0x000E, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x07, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0005, ZclStatus: SUCCESS, DataType: CharString, ModelIdentifier: “TS0002” > > > >
2022-10-12T16:16:46.077758341+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:46.085358341+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:46.125778008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0x88, rssi: -66, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x08, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0007, ZclStatus: SUCCESS, DataType: Enum8, PowerSource: PowerSource[SINGLE_PHASE_MAINS] > > > >
2022-10-12T16:16:46.146103674+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:46.153681008+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:46.196721341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0x88, rssi: -66, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x09, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0xFFFE, ZclStatus: SUCCESS, DataType: Enum8, Enum8: 0x00 > > > >
2022-10-12T16:16:46.214894674+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:46.221643674+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:46.248178008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x0A, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x4003 > > > >
2022-10-12T16:16:46.262349341+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:46.273432341+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:46.286259341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x0B, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2022-10-12T16:16:46.352486674+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:46.364178674+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:46.372545008+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x0C, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x4003 > > > >
2022-10-12T16:16:46.404500341+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:46.411855008+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:46.424214674+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x0D, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x8002 > > > >
2022-10-12T16:16:46.443222674+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:46.449939341+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:46.466536674+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0x88, rssi: -66, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x5A >, < BindRequestResponse || status: 0x00 > > >2022-10-12T16:16:46.491427008+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:46.498672341+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:46.507732341+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x07, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x8002, DataType: Enum8, Enum8: 0x02 > > > >
2022-10-12T16:16:46.528305341+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T16:16:46.537952674+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T16:16:46.572388674+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, lqi: 0x88, rssi: -66, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x0E, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: SUCCESS, direction: 0x00, attr_id: 0x050B > > > >
2022-10-12T16:16:46.600013008+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled

Liran1115 · October 12, 2022, 4:23pm

I couldn’t send it in 1 message so I just send 3 answers for you

Open to see the logs

2022-10-12T16:16:46.615789341+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:46.648426008+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0x88, rssi: -66, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x5B >, < BindRequestResponse || status: 0x00 > > >2022-10-12T16:16:46.710929341+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:46.726788341+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:46.747943674+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0x88, rssi: -66, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x0F, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, direction: 0x00, attr_id: 0x0400 > > > >
2022-10-12T16:16:46.791357008+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:46.816081008+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler device_lifecycle2022-10-12T16:16:46.845256341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received lifecycle event: infoChanged
2022-10-12T16:16:46.855565341+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:46.877895341+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:46.886112341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0x88, rssi: -66, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x10, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: SUCCESS, direction: 0x00, attr_id: 0x0000 > > > >
2022-10-12T16:16:46.947080341+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:46.958864341+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:46.981809341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0x88, rssi: -66, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x5C >, < BindRequestResponse || status: 0x00 > > >2022-10-12T16:16:47.007639008+00:00 TRACE Zigbee Multi Switch and Child Mc  Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:16:47.013034341+00:00 PRINT Zigbee Multi Switch and Child Mc  device.preferences[infoChanged]=    255
2022-10-12T16:16:47.021170341+00:00 PRINT Zigbee Multi Switch and Child Mc  << Preference changed name: restoreState   oldPreferenceValue:      nil     newParameterValue: >>   255
2022-10-12T16:16:47.028416341+00:00 PRINT Zigbee Multi Switch and Child Mc  <<< Write restore state >>>
2022-10-12T16:16:47.033952341+00:00 PRINT Zigbee Multi Switch and Child Mc  <<<< Componente, end_point >>>>     main   12022-10-12T16:16:47.045037341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, 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-12T16:16:47.071435341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, 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-12T16:16:47.093291008+00:00 PRINT Zigbee Multi Switch and Child Mc  <<< Write restore state >>>
2022-10-12T16:16:47.098644008+00:00 PRINT Zigbee Multi Switch and Child Mc  <<<< Componente, end_point >>>>     switch2
2
2022-10-12T16:16:47.105754674+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x4003, DataType: Enum8, data: 0xFF > > > >
2022-10-12T16:16:47.123927008+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x8002, DataType: Enum8, data: 0x02 > > > >
2022-10-12T16:16:47.139478674+00:00 PRINT Zigbee Multi Switch and Child Mc  device.preferences[infoChanged]=    No
2022-10-12T16:16:47.144812008+00:00 PRINT Zigbee Multi Switch and Child Mc  << Preference changed name: switch2Child   oldPreferenceValue:      nil     newParameterValue: >>   No
2022-10-12T16:16:47.150189008+00:00 PRINT Zigbee Multi Switch and Child Mc  device.preferences[infoChanged]=    No
2022-10-12T16:16:47.155490008+00:00 PRINT Zigbee Multi Switch and Child Mc  << Preference changed name: signalMetricsVisibles   oldPreferenceValue:     nil     newParameterValue: >>   No
2022-10-12T16:16:47.167911674+00:00 PRINT Zigbee Multi Switch and Child Mc  device.preferences[infoChanged]=    No
2022-10-12T16:16:47.173337674+00:00 PRINT Zigbee Multi Switch and Child Mc  << Preference changed name: switch1Child   oldPreferenceValue:      nil     newParameterValue: >>   No
2022-10-12T16:16:47.191504341+00:00 PRINT Zigbee Multi Switch and Child Mc  device.preferences[infoChanged]=    Single
2022-10-12T16:16:47.199249674+00:00 PRINT Zigbee Multi Switch and Child Mc  << Preference changed name: changeProfileTwoSwPw    oldPreferenceValue:     nil     newParameterValue: >>   Single
2022-10-12T16:16:47.215615008+00:00 PRINT Zigbee Multi Switch and Child Mc  device.preferences[infoChanged]=
2022-10-12T16:16:47.223920674+00:00 PRINT Zigbee Multi Switch and Child Mc  << Preference changed name: version oldPreferenceValue:     nil     newParameterValue: >>
2022-10-12T16:16:47.231141674+00:00 PRINT Zigbee Multi Switch and Child Mc  Device ID   <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)>
2022-10-12T16:16:47.236515674+00:00 PRINT Zigbee Multi Switch and Child Mc  Manufacturer >>>    _TZ3000_zmy4lslw       Manufacturer_Len >>>     16
2022-10-12T16:16:47.241976341+00:00 PRINT Zigbee Multi Switch and Child Mc  Model >>>   TS0002  Model_len >>>   6
2022-10-12T16:16:47.250751008+00:00 PRINT Zigbee Multi Switch and Child Mc  Memory >>>>>>>      1887.8603515625  Kbytes
2022-10-12T16:16:47.255971674+00:00 PRINT Zigbee Multi Switch and Child Mc  <<<<< Firmware Version >>>>>        Unknown
2022-10-12T16:16:47.261773341+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.278609341+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:47.287289341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x11, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: SUCCESS, direction: 0x00, attr_id: 0x0000 > > > >
2022-10-12T16:16:47.309197674+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.317868341+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:47.330129008+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0x88, rssi: -66, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x5D >, < BindRequestResponse || status: 0x00 > > >2022-10-12T16:16:47.348325008+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.355298008+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:47.381304341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x12, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: SUCCESS, direction: 0x00, attr_id: 0x0000 > > > >
2022-10-12T16:16:47.401143341+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.413177675+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:47.421769341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, lqi: 0x88, rssi: -66, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x13, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0605, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2022-10-12T16:16:47.441064008+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.448177008+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:47.457250008+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, lqi: 0x88, rssi: -66, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x14, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0604, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2022-10-12T16:16:47.492516008+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.499894008+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:47.515501341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0x88, rssi: -66, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x15, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0302, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2022-10-12T16:16:47.534790675+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.543038008+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:47.553342341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0x88, rssi: -66, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x16, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0301, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2022-10-12T16:16:47.567936341+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.575171341+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:47.584611341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x17, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x4003 > > > >
2022-10-12T16:16:47.600264675+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.607559008+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:47.617282341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x18, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2022-10-12T16:16:47.637896341+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.650284341+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:47.664175341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x19, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x4003 > > > >
2022-10-12T16:16:47.704247008+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.711333341+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:47.721448341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x1A, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x8002 > > > >
2022-10-12T16:16:47.738089008+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.746073675+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.754237675+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.904666675+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:47.916273675+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE000 >, lqi: 0x88, rssi: -66, body_length: 0x000F, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x08, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xD003, DataType: CharString, CharString: "AAAAAgAA" > > > >
2022-10-12T16:16:47.942508675+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:47.964199675+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:47.974939341+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-12T16:16:47.985116341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE000 >, lqi: 0x88, rssi: -66, body_length: 0x0009, GenericBody:  08 09 0A 01 D0 48 02 00 06 >
2022-10-12T16:16:48.014069008+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:48.033968341+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:48.047334341+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-12T16:16:48.054874008+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE000 >, lqi: 0x88, rssi: -66, body_length: 0x0009, GenericBody:  08 0A 0A 02 D0 48 02 00 0A >
2022-10-12T16:16:48.094846341+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:48.107216008+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:48.127789675+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0015, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0B, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 >, < AttributeRecord || AttributeId: 0x8002, DataType: Enum8, Enum8: 0x02 > > > >
2022-10-12T16:16:48.164021008+00:00 TRACE Zigbee Multi Switch and Child Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:16:48.169155008+00:00 INFO Zigbee Multi Switch and Child Mc  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-12T16:16:48.180258675+00:00 PRINT Zigbee Multi Switch and Child Mc  function: on_off_attr_handler
2022-10-12T16:16:48.187703008+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"dni: 0x02E6, lqi: 136, rssi: -66dBm"},"visibility":{"displayed":false}}
2022-10-12T16:16:48.225553341+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2022-10-12T16:16:48.245259675+00:00 PRINT Zigbee Multi Switch and Child Mc  src_endpoint =      1       value = false
2022-10-12T16:16:48.271523675+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:48.279546008+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:48.305573675+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xE001 >, lqi: 0x88, rssi: -66, body_length: 0x002E, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0C, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xD030, DataType: Enum8, Enum8: 0x00 >, < AttributeRecord || AttributeId: 0xD000, DataType: Uint8, Uint8: 0x00 >, < AttributeRecord || AttributeId: 0xD001, DataType: Bitmap32, Bitmap32: 0x00000000 >, < AttributeRecord || AttributeId: 0xD002, DataType: Uint32, Uint32: 0x00000000 >, < AttributeRecord || AttributeId: 0xD003, DataType: Uint32, Uint32: 0x00000000 >, < AttributeRecord || AttributeId: 0xD004, DataType: Uint32, Uint32: 0x00000000 >, < AttributeRecord || AttributeId: 0xD005, DataType: Uint32, Uint32: 0x00000000 > > > >
2022-10-12T16:16:48.328629008+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:48.335840008+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:48.345814675+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0011, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0D, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 > > > >
2022-10-12T16:16:48.362633341+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:48.372448008+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:16:48.381049008+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0E, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x8002, DataType: Enum8, Enum8: 0x02 > > > >
2022-10-12T16:16:48.398281008+00:00 TRACE Zigbee Multi Switch and Child Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:16:48.410671008+00:00 INFO Zigbee Multi Switch and Child Mc  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-12T16:16:48.417209675+00:00 PRINT Zigbee Multi Switch and Child Mc  function: on_off_attr_handler
2022-10-12T16:16:48.423593675+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"dni: 0x02E6, lqi: 136, rssi: -66dBm"},"visibility":{"displayed":false}}
2022-10-12T16:16:48.452276008+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch2","state":{"value":"off"}}
2022-10-12T16:16:48.493008341+00:00 PRINT Zigbee Multi Switch and Child Mc  src_endpoint =      2       value = false
2022-10-12T16:16:48.503490675+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:48.512325341+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:48.521059675+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:50.287938008+00:00 PRINT Zigbee Multi Switch and Child Mc  all_switches_status >>>>>
2022-10-12T16:16:50.297866342+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:16:50.520346342+00:00 PRINT Zigbee Multi Switch and Child Mc  all_switches_status >>>>>
2022-10-12T16:16:50.526007675+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:12.583645344+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler capability
2022-10-12T16:17:12.592639678+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received command: {"args":{},"capability":"switch","command":"on","component":"switch2","positional_args":{}}
2022-10-12T16:17:12.598525011+00:00 TRACE Zigbee Multi Switch and Child Mc  Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:17:12.605345344+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On ||  > > >
2022-10-12T16:17:12.617449344+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch2","state":{"value":"on"}}
2022-10-12T16:17:12.653889678+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled

Liran1115 · October 12, 2022, 4:24pm

Open to see the logs


2022-10-12T16:17:12.661557344+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:12.925798678+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:17:12.940580344+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x1C, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-10-12T16:17:12.960078011+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:17:12.969880011+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x10, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-10-12T16:17:12.986766011+00:00 TRACE Zigbee Multi Switch and Child Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:17:12.992015011+00:00 INFO Zigbee Multi Switch and Child Mc  Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-10-12T16:17:13.000678678+00:00 PRINT Zigbee Multi Switch and Child Mc  <<<<<< default_response_handler >>>>>>
2022-10-12T16:17:13.005978344+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:13.017137344+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:17:13.035392678+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x84, rssi: -67, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x12, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-10-12T16:17:13.062538011+00:00 TRACE Zigbee Multi Switch and Child Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:17:13.068130011+00:00 INFO Zigbee Multi Switch and Child Mc  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-12T16:17:13.073723011+00:00 PRINT Zigbee Multi Switch and Child Mc  function: on_off_attr_handler
2022-10-12T16:17:13.079724678+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"dni: 0x02E6, lqi: 136, rssi: -66dBm"},"visibility":{"displayed":false}}
2022-10-12T16:17:13.099846678+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2022-10-12T16:17:13.119805011+00:00 PRINT Zigbee Multi Switch and Child Mc  src_endpoint =      1       value = true
2022-10-12T16:17:13.131582678+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:13.142119678+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:17:13.152223011+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x84, rssi: -67, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x13, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-10-12T16:17:13.168611011+00:00 TRACE Zigbee Multi Switch and Child Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:17:13.173712344+00:00 INFO Zigbee Multi Switch and Child Mc  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-12T16:17:13.179251011+00:00 PRINT Zigbee Multi Switch and Child Mc  function: on_off_attr_handler
2022-10-12T16:17:13.185831678+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"dni: 0x02E6, lqi: 132, rssi: -67dBm"},"visibility":{"displayed":false}}
2022-10-12T16:17:13.207176011+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"on"}}
2022-10-12T16:17:13.221672344+00:00 PRINT Zigbee Multi Switch and Child Mc  src_endpoint =      1       value = true
2022-10-12T16:17:13.231677678+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:13.239117344+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:17:13.247361011+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x98, rssi: -62, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x11, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-10-12T16:17:13.263090344+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:13.270193011+00:00 TRACE Zigbee Multi Switch and Child Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:17:13.277143011+00:00 INFO Zigbee Multi Switch and Child Mc  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-12T16:17:13.282674011+00:00 PRINT Zigbee Multi Switch and Child Mc  function: on_off_attr_handler
2022-10-12T16:17:13.288656344+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"dni: 0x02E6, lqi: 132, rssi: -67dBm"},"visibility":{"displayed":false}}
2022-10-12T16:17:13.304071344+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch2","state":{"value":"on"}}
2022-10-12T16:17:13.318886011+00:00 PRINT Zigbee Multi Switch and Child Mc  src_endpoint =      2       value = true
2022-10-12T16:17:13.329073678+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:13.336777011+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:13.345197344+00:00 TRACE Zigbee Multi Switch and Child Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:17:13.350690344+00:00 INFO Zigbee Multi Switch and Child Mc  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-12T16:17:13.357501344+00:00 PRINT Zigbee Multi Switch and Child Mc  function: on_off_attr_handler
2022-10-12T16:17:13.364315344+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"dni: 0x02E6, lqi: 152, rssi: -62dBm"},"visibility":{"displayed":false}}
2022-10-12T16:17:13.382311344+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch2","state":{"value":"on"}}
2022-10-12T16:17:13.399071011+00:00 PRINT Zigbee Multi Switch and Child Mc  src_endpoint =      2       value = true
2022-10-12T16:17:13.409333678+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:13.417422678+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:13.425303344+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:14.679376678+00:00 PRINT Zigbee Multi Switch and Child Mc  all_switches_status >>>>>
2022-10-12T16:17:14.696113011+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:15.146908011+00:00 PRINT Zigbee Multi Switch and Child Mc  all_switches_status >>>>>
2022-10-12T16:17:15.152343011+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:15.244051011+00:00 PRINT Zigbee Multi Switch and Child Mc  all_switches_status >>>>>
2022-10-12T16:17:15.249464011+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:15.335467678+00:00 PRINT Zigbee Multi Switch and Child Mc  all_switches_status >>>>>
2022-10-12T16:17:15.341404011+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:15.412602678+00:00 PRINT Zigbee Multi Switch and Child Mc  all_switches_status >>>>>
2022-10-12T16:17:15.417943678+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:18.889115678+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler capability
2022-10-12T16:17:19.047390678+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received command: {"args":{},"capability":"switch","command":"off","component":"switch2","positional_args":{}}
2022-10-12T16:17:19.107855678+00:00 TRACE Zigbee Multi Switch and Child Mc  Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:17:19.184065012+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x02E6, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < Off ||  > > >
2022-10-12T16:17:19.231085678+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch2","state":{"value":"off"}}
2022-10-12T16:17:19.587617012+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:19.641813012+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:17:19.712060345+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x98, rssi: -62, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x1D, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >
2022-10-12T16:17:19.743083345+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:19.760058012+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:17:19.774931345+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, 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: 0x14, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-10-12T16:17:19.800625345+00:00 TRACE Zigbee Multi Switch and Child Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:17:19.805735678+00:00 INFO Zigbee Multi Switch and Child Mc  Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-10-12T16:17:19.811344345+00:00 PRINT Zigbee Multi Switch and Child Mc  <<<<<< default_response_handler >>>>>>
2022-10-12T16:17:19.820302345+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:19.827056678+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:17:19.848983345+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x98, rssi: -62, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x16, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-10-12T16:17:19.867494345+00:00 TRACE Zigbee Multi Switch and Child Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:17:19.880652678+00:00 INFO Zigbee Multi Switch and Child Mc  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-12T16:17:19.886160345+00:00 PRINT Zigbee Multi Switch and Child Mc  function: on_off_attr_handler
2022-10-12T16:17:19.892329012+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"dni: 0x02E6, lqi: 156, rssi: -61dBm"},"visibility":{"displayed":false}}
2022-10-12T16:17:19.947038678+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2022-10-12T16:17:19.978700012+00:00 PRINT Zigbee Multi Switch and Child Mc  src_endpoint =      1       value = false
2022-10-12T16:17:20.014711012+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:20.021603012+00:00 TRACE Zigbee Multi Switch and Child Mc  Received event with handler zigbee
2022-10-12T16:17:20.041246012+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x02E6, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x98, rssi: -62, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x17, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-10-12T16:17:20.092182345+00:00 TRACE Zigbee Multi Switch and Child Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:17:20.100090012+00:00 INFO Zigbee Multi Switch and Child Mc  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-12T16:17:20.118880012+00:00 PRINT Zigbee Multi Switch and Child Mc  function: on_off_attr_handler
2022-10-12T16:17:20.134093678+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"dni: 0x02E6, lqi: 152, rssi: -62dBm"},"visibility":{"displayed":false}}
2022-10-12T16:17:20.158310345+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
2022-10-12T16:17:20.188114345+00:00 PRINT Zigbee Multi Switch and Child Mc  src_endpoint =      1       value = false
2022-10-12T16:17:20.205126678+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:20.217873345+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:20.225869345+00:00 TRACE Zigbee Multi Switch and Child Mc  Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T16:17:20.235396012+00:00 INFO Zigbee Multi Switch and Child Mc  Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-12T16:17:20.241253012+00:00 PRINT Zigbee Multi Switch and Child Mc  function: on_off_attr_handler
2022-10-12T16:17:20.247202678+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"dni: 0x02E6, lqi: 152, rssi: -62dBm"},"visibility":{"displayed":false}}
2022-10-12T16:17:20.264144012+00:00 INFO Zigbee Multi Switch and Child Mc  <ZigbeeDevice: 74d8597d-5696-478c-8393-10957ec6cdb8 [0x02E6] (TS0002 Switch)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"switch2","state":{"value":"off"}}
2022-10-12T16:17:20.279083345+00:00 PRINT Zigbee Multi Switch and Child Mc  src_endpoint =      2       value = false
2022-10-12T16:17:20.288940012+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:20.295758345+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:20.303594012+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:21.475240345+00:00 PRINT Zigbee Multi Switch and Child Mc  all_switches_status >>>>>
2022-10-12T16:17:21.480987345+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:22.010538012+00:00 PRINT Zigbee Multi Switch and Child Mc  all_switches_status >>>>>
2022-10-12T16:17:22.020496345+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:22.204956345+00:00 PRINT Zigbee Multi Switch and Child Mc  all_switches_status >>>>>
2022-10-12T16:17:22.210338012+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled
2022-10-12T16:17:22.300934345+00:00 PRINT Zigbee Multi Switch and Child Mc  all_switches_status >>>>>
2022-10-12T16:17:22.306272679+00:00 DEBUG Zigbee Multi Switch and Child Mc  TS0002 Switch device thread event handled

Mariano_Colmenarejo · October 12, 2022, 5:23pm

@Liran1115

Please, could you remove the format </> for logs?
Is imposible understand them for me

Liran1115 · October 12, 2022, 5:42pm

@Mariano_Colmenarejo

oops sorry
fixed it.

Mariano_Colmenarejo · October 12, 2022, 7:20pm

@Liran1115

Please, could you install this version with CLI?

───────────────────────────────────────────────────
 Name         Zigbee Multi Switch and Child Mc     
 Version      2022-10-12T19:14:22.817756471        
───────────────────────────────────────────────────

Liran1115 · October 12, 2022, 9:55pm

@Mariano_Colmenarejo

Did it.
same.

about the other person that have this issue the problem solved? maybe the electric guy didn’t connect it correctly or its driver problem?

logs:
? Select a driver. 10
connecting… connected
2022-10-12T21:54:31.900021003+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-10-12T21:54:31.907791336+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“switch2”,“positional_args”:{}}
2022-10-12T21:54:31.913595336+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-10-12T21:54:31.920324336+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x881B, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-10-12T21:54:31.941198003+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-10-12T21:54:31.973010336+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:31.981052003+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:32.046273670+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T21:54:32.061052003+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x881B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x88, rssi: -66, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x53, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-10-12T21:54:32.082457670+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T21:54:32.087861670+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-10-12T21:54:32.094167003+00:00 PRINT Zigbee Multi Switch and Child Mc <<<<<< default_response_handler >>>>>>
2022-10-12T21:54:32.099618003+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:32.105077003+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T21:54:32.113292337+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x881B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x84, rssi: -67, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0xE0, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-10-12T21:54:32.130064337+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T21:54:32.135326003+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-12T21:54:32.141057337+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-12T21:54:32.147041337+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x881B, lqi: 132, rssi: -67dBm”},“visibility”:{“displayed”:false}}
2022-10-12T21:54:32.166225670+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-10-12T21:54:32.188886670+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 1 value = true
2022-10-12T21:54:32.199292670+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:32.205992003+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T21:54:32.214856670+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x881B, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x84, rssi: -67, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0xE2, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-10-12T21:54:32.234963003+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:32.240509337+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T21:54:32.250024337+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x881B, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x84, rssi: -67, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0xE3, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-10-12T21:54:32.268289670+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T21:54:32.273415670+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-12T21:54:32.279000337+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-12T21:54:32.284970337+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x881B, lqi: 132, rssi: -67dBm”},“visibility”:{“displayed”:false}}
2022-10-12T21:54:32.301862003+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-10-12T21:54:32.317863337+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 1 value = true
2022-10-12T21:54:32.327674337+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:32.335017337+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-10-12T21:54:32.343213003+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x881B, 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: 0xE1, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-10-12T21:54:32.362178670+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T21:54:32.367405003+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-12T21:54:32.372991003+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-12T21:54:32.379334337+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x881B, lqi: 132, rssi: -67dBm”},“visibility”:{“displayed”:false}}
2022-10-12T21:54:32.396486003+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-10-12T21:54:32.411415003+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 2 value = true
2022-10-12T21:54:32.421581337+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:32.429277337+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:32.437333337+00:00 TRACE Zigbee Multi Switch and Child Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-10-12T21:54:32.442632670+00:00 INFO Zigbee Multi Switch and Child Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-10-12T21:54:32.448594670+00:00 PRINT Zigbee Multi Switch and Child Mc function: on_off_attr_handler
2022-10-12T21:54:32.454634337+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“dni: 0x881B, lqi: 156, rssi: -61dBm”},“visibility”:{“displayed”:false}}
2022-10-12T21:54:32.473721670+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: fbf5ceb9-891a-425c-a42a-7277e675492a [0x881B] (TS0002 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-10-12T21:54:32.490224337+00:00 PRINT Zigbee Multi Switch and Child Mc src_endpoint = 2 value = true
2022-10-12T21:54:32.501175670+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:32.509039003+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:32.517157337+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:33.987904671+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-12T21:54:34.047085004+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:34.223163004+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-12T21:54:34.228679004+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:34.335023004+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-12T21:54:34.343154338+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:34.426451671+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-12T21:54:34.432017338+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled
2022-10-12T21:54:34.512238004+00:00 PRINT Zigbee Multi Switch and Child Mc all_switches_status >>>>>
2022-10-12T21:54:34.531491338+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0002 Switch device thread event handled

Mariano_Colmenarejo · October 12, 2022, 10:19pm

@Liran1115
I don’t see controller initialization in this log.
In the previous log I saw some errors and strange data

Could you install this driver version with the CLI to see the initialization in the log?

───────────────────────────────────────────────────
Name Zigbee Multi Switch and Child Mc
Version 2022-10-12T22:04:53.080968194
───────────────────────────────────────────────────

Coelhorj · October 13, 2022, 2:42am

Tried.
Not yet.

Same behavior

Mariano_Colmenarejo · October 13, 2022, 12:07pm

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

Liran1115 · October 13, 2022, 2:05pm

@Mariano_Colmenarejo

still the same
power on both of the lamps together

Coelhorj · October 13, 2022, 7:26pm

Same here…

Mariano_Colmenarejo · October 13, 2022, 7:50pm

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

Coelhorj · October 13, 2022, 8:14pm

My apologies but How can i collect that log?

Mariano_Colmenarejo · October 13, 2022, 9:34pm

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

Coelhorj · October 13, 2022, 11:31pm

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,

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

Customers

Developers

Download the SmartThings App