Iโm in the same situation as Amin300. Would be great to get the edge driver working without the timeout. Here are my logs with the latest test version 2022-01-25. Everything seem to be working apart from the timeout.
There is another referense to the IsOrvibo in the working (when modified) DTH for โrefreshโ if that is of some clue.
Logs
`Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell Install PowerShell on Windows, Linux, and macOS - PowerShell | Microsoft Docs
PS C:\Users\tomas> cd C:\Temp\ST
PS C:\Temp\ST> .\smartthings.exe edge:drivers:logcat
? Enter hub IP address with optionally appended port numbe5 canโt be established. Certificate fingerprint is75
? Are you sure you want to continue connecting? Yes
ยป Warning: Permanently added to the list of known hubs.
โโโโโฌโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฌโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ # โ Driver Id โ Name โ
โโโโโผโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโผโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ 1 โ 8a5a5586-aa12-4cbb-b7ed-fa3ad735df0d โ Zigbee Aqara Water Leak Sensor Mc โ
โโโโโดโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโดโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
? Select a driver. (all)
PS C:\Temp\ST> .\smartthings.exe edge:drivers:logcat
? Enter hub IP address with optionally appended port number: 10.10.10.50
โโโโโฌโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฌโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ # โ Driver Id โ Name โ
โโโโโผโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโผโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ 1 โ 8a5a5586-aa12-4cbb-b7ed-fa3ad735df0d โ Zigbee Aqara Water Leak Sensor Mc โ
โ 2 โ 7d469ae2-4d8f-422e-9997-d77d67065b8d โ Zigbee Multi Switch Zemismart test โ
โโโโโดโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโดโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
? Select a driver. 2
2022-02-05T15:09:01.864051910+00:00 TRACE Zigbee Multi Switch Zemismart test Setup driver Zigbee_Multi_Switch with lifecycle handlers:
DeviceLifecycleDispatcher: Zigbee_Multi_Switch
default_handlers:
driverSwitched:
doConfigure:
init:
child_dispatchers:
2022-02-05T15:09:01.868147278+00:00 TRACE Zigbee Multi Switch Zemismart test Setup driver Zigbee_Multi_Switch with Capability handlers:
CapabilityCommandDispatcher: Zigbee_Multi_Switch
default_handlers:
switch:
off
on
refresh:
refresh
child_dispatchers:
2022-02-05T15:09:01.873474446+00:00 TRACE Zigbee Multi Switch Zemismart test Setup driver Zigbee_Multi_Switch with Zigbee handlers:
ZigbeeMessageDispatcher: Zigbee_Multi_Switch
default_handlers:
attr:
ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
global:
ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
cluster:
zdo:
child_dispatchers:
2022-02-05T15:09:01.905314810+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler _resync
2022-02-05T15:09:01.908539988+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler environment_info
2022-02-05T15:09:01.916546650+00:00 TRACE Zigbee Multi Switch Zemismart test Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:09:01.922704819+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:01.926074133+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler _resync
2022-02-05T15:09:01.929243631+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler environment_info
2022-02-05T15:09:01.932255458+00:00 DEBUG Zigbee Multi Switch Zemismart test Z-Wave hub node ID environment changed.
2022-02-05T15:09:01.939866067+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:01.943380518+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler device_lifecycle
2022-02-05T15:09:01.946877143+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received lifecycle event: added
2022-02-05T15:09:01.951306261+00:00 TRACE Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received unhandled lifecycle event: added
2022-02-05T15:09:01.954384263+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:01.957828707+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler device_lifecycle
2022-02-05T15:09:01.961064671+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received lifecycle event: doConfigure
2022-02-05T15:09:01.966644172+00:00 TRACE Zigbee Multi Switch Zemismart test Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:09:01.975849317+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 2C1165FFFE3AD443, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x03, dest_address: D052A835AEAD0001, dest_endpoint: 0x01 > > >
2022-02-05T15:09:01.997358598+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, 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-02-05T15:09:02.006195844+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, dest_endpoint: 0x02, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 2C1165FFFE3AD443, src_endpoint: 0x02, cluster: OnOff, dest_addr_mode: 0x03, dest_address: D052A835AEAD0001, dest_endpoint: 0x01 > > >
2022-02-05T15:09:02.013995401+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, 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-02-05T15:09:02.023167604+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x4001, DataType: Uint16, data: 0xFFFF > > > >
2022-02-05T15:09:02.031699170+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x4002, DataType: Uint16, data: 0xFFFF > > > >
2022-02-05T15:09:02.045892736+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:02.055309525+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:02.263790774+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:02.269488257+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xFF, rssi: -53, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x38 >, < BindRequestResponse || status: 0x00 > > >
2022-02-05T15:09:02.278705230+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:02.335986283+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler device_lifecycle
2022-02-05T15:09:02.344579776+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received lifecycle event: infoChanged
2022-02-05T15:09:02.350069447+00:00 TRACE Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received unhandled lifecycle event: infoChanged
2022-02-05T15:09:02.353139869+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:02.439962478+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:02.447731924+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -53, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x11, ZCLCommandId: 0x07 >, < ConfigureReportingReponse || ZclStatus: SUCCESS > > >
2022-02-05T15:09:02.456322169+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:02.470408747+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:02.474599692+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xFF, rssi: -53, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x39 >, < BindRequestResponse || status: 0x00 > > >
2022-02-05T15:09:02.482238287+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:02.550405145+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:02.554943458+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -53, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x12, ZCLCommandId: 0x07 >, < ConfigureReportingReponse || ZclStatus: SUCCESS > > >
2022-02-05T15:09:02.563828347+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:06.888984813+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:06.899613121+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -53, body_length: 0x0019, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x00, 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: 0x8001, DataType: Enum8, Enum8: 0x01 >, < AttributeRecord || AttributeId: 0x8002, DataType: Enum8, Enum8: 0x00 > > > >
2022-02-05T15:09:06.908746302+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:09:06.911859953+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T15:09:06.915373945+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-02-05T15:09:06.919604745+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {โcapability_idโ:โswitchโ,โattribute_idโ:โswitchโ,โcomponent_idโ:โmainโ,โstateโ:{โvalueโ:โoffโ}}
2022-02-05T15:09:06.928925333+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 false
2022-02-05T15:09:06.932961314+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:07.160742783+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:07.165972458+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -53, body_length: 0x0011, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x01, 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-02-05T15:09:07.174549876+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:09:07.177590146+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T15:09:07.186183889+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-02-05T15:09:07.190212457+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {โcapability_idโ:โswitchโ,โattribute_idโ:โswitchโ,โcomponent_idโ:โswitch2โ,โstateโ:{โvalueโ:โoffโ}}
2022-02-05T15:09:07.203151859+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 false
2022-02-05T15:09:07.206638990+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:11.510216792+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:11.521397074+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -54, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x13, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2022-02-05T15:09:11.533451627+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:11.543079686+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:11.548005388+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -54, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x03, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 > > > >
2022-02-05T15:09:11.559981148+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:11.563885861+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:11.568378905+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -54, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x14, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2022-02-05T15:09:11.577307272+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:11.708694004+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:11.715924262+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -54, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x04, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x2000 > > > >
2022-02-05T15:09:11.724785038+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:15.695987861+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:15.746603082+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: DeviceTemperatureConfiguration >, lqi: 0xFF, rssi: -54, body_length: 0x0003, < ZDOMessageBody || < ZDOHeader || seqno: 0x82 >, GenericBody: 00 00 > >
2022-02-05T15:09:15.780863277+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:21.011411945+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:21.022021596+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -55, body_length: 0x0019, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x05, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x2000 >, < AttributeRecord || AttributeId: 0x8001, DataType: Enum8, Enum8: 0x01 >, < AttributeRecord || AttributeId: 0x8002, DataType: Enum8, Enum8: 0x00 > > > >
2022-02-05T15:09:21.036977156+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:09:21.042200210+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T15:09:21.045681719+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-02-05T15:09:21.053079976+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {โcapability_idโ:โswitchโ,โattribute_idโ:โswitchโ,โcomponent_idโ:โmainโ,โstateโ:{โvalueโ:โoffโ}}
2022-02-05T15:09:21.062644108+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 false
2022-02-05T15:09:21.066640817+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:21.180348810+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:21.185660278+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -55, body_length: 0x0011, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x06, 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-02-05T15:09:21.195822486+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:09:21.198870211+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T15:09:21.202284295+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-02-05T15:09:21.206410772+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {โcapability_idโ:โswitchโ,โattribute_idโ:โswitchโ,โcomponent_idโ:โswitch2โ,โstateโ:{โvalueโ:โoffโ}}
2022-02-05T15:09:21.215927928+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 false
2022-02-05T15:09:21.219922138+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:31.887831268+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-02-05T15:10:01.894820025+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-02-05T15:10:31.896560783+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-02-05T15:10:53.023724047+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-02-05T15:10:53.029687897+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received command: {โcapabilityโ:โswitchโ,โargsโ:,โcommandโ:โonโ,โcomponentโ:โmainโ,โpositional_argsโ:}
2022-02-05T15:10:53.033079034+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch