(EDGE Driver-Mc): Zigbee Drivers for Motion, Open/Close, Moisture, Smoke-Co Sensors and others Devices

Mariano_Colmenarejo · January 25, 2022, 7:06pm

This time if it has been written correctly according to the response of the device.

I am going to write 0x0000 instead of 0xFFFF, according to the zigbee document it would be the same, but we are going to try

Uninstall the device and the old driver
redo the driver and device installation process again

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Multi Switch Zemismart test   │
│ Version     │ 2022-01-25T19:05:13.811691           │
└─────────────┴──────────────────────────────────────┘

Helder_Rodrigues · January 25, 2022, 7:32pm

Hello @Mariano_Colmenarejo with the drivers should not be local?
Cloud is appearing!

amin300 · January 25, 2022, 7:41pm

Tested again
Device switched of after 2 mins
but i still can control device from app
logs part 1
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! Migrating from Windows PowerShell 5.1 to PowerShell 7 - PowerShell | Microsoft Docs

PS C:\WINDOWS\system32> cd c:
PS C:> cd users
PS C:\users> cd aminhsm
PS C:\users\aminhsm> cd documents
PS C:\users\aminhsm\documents> cd cli
PS C:\users\aminhsm\documents\cli> .\smartthings edge:drivers:logcat
? Enter hub IP address with optionally appended port number: 192.168.1.58
┌───┬──────────────────────────────────────┬────────────────────────────────────┐
│ # │ Driver Id │ Name │
├───┼──────────────────────────────────────┼────────────────────────────────────┤
│ 1 │ 7d469ae2-4d8f-422e-9997-d77d67065b8d │ Zigbee Multi Switch Zemismart test │
└───┴──────────────────────────────────────┴────────────────────────────────────┘
? Select a driver. 1
2022-01-25T19:33:42.652511793+00:00 TRACE Zigbee Multi Switch Zemismart test Setup driver Zigbee_Multi_Switch with lifecycle handlers:
DeviceLifecycleDispatcher: Zigbee_Multi_Switch
default_handlers:
doConfigure:
init:
driverSwitched:
child_dispatchers:

2022-01-25T19:33:42.659045058+00:00 TRACE Zigbee Multi Switch Zemismart test Setup driver Zigbee_Multi_Switch with Capability handlers:
CapabilityCommandDispatcher: Zigbee_Multi_Switch
default_handlers:
refresh:
refresh
switch:
off
on
child_dispatchers:

2022-01-25T19:33:42.667844789+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-01-25T19:33:42.727161766+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler _resync
2022-01-25T19:33:42.732809255+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler environment_info
2022-01-25T19:33:42.749105399+00:00 TRACE Zigbee Multi Switch Zemismart test Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:33:42.760832593+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:33:42.766491754+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler _resync
2022-01-25T19:33:42.772052200+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler environment_info
2022-01-25T19:33:42.777435223+00:00 DEBUG Zigbee Multi Switch Zemismart test Z-Wave hub node ID environment changed.
2022-01-25T19:33:42.791206772+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:33:42.797331833+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler environment_info
2022-01-25T19:33:42.806374019+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler environment_info
2022-01-25T19:33:42.813839416+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler device_lifecycle
2022-01-25T19:33:42.823179417+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received lifecycle event: added
2022-01-25T19:33:42.847477894+00:00 TRACE Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received unhandled lifecycle event: added
2022-01-25T19:33:42.857776374+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:33:42.869775704+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler device_lifecycle
2022-01-25T19:33:42.885812051+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received lifecycle event: doConfigure
2022-01-25T19:33:42.898915266+00:00 TRACE Zigbee Multi Switch Zemismart test Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:33:42.942749506+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x58D4, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x4001, DataType: Uint16, data: 0x0000 > > > >
2022-01-25T19:33:42.984883229+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x58D4, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 60A423FFFE651394, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D97000200C8A4, dest_endpoint: 0x01 > > >
2022-01-25T19:33:43.002842537+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x58D4, 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-01-25T19:33:43.031197708+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x58D4, dest_endpoint: 0x02, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 60A423FFFE651394, src_endpoint: 0x02, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D97000200C8A4, dest_endpoint: 0x01 > > >
2022-01-25T19:33:43.045087983+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x58D4, 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-01-25T19:33:43.061833685+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:33:43.105837009+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:33:43.116187181+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:33:43.196470303+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x40, rssi: -84, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x0F, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2022-01-25T19:33:43.242175477+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:33:43.248117780+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:33:43.273646872+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x44, rssi: -83, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x06, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 > > > >
2022-01-25T19:33:43.299125605+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:33:43.305702225+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:33:43.314914495+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0x44, rssi: -83, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x18 >, < BindRequestResponse || status: 0x00 > > >
2022-01-25T19:33:43.335125596+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:33:43.341627512+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:33:43.358520287+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x48, rssi: -82, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x10, ZCLCommandId: 0x07 >, < ConfigureReportingReponse || ZclStatus: SUCCESS > > >
2022-01-25T19:33:43.376879129+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:33:43.383878293+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:33:43.393065885+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0x48, rssi: -82, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x19 >, < BindRequestResponse || status: 0x00 > > >
2022-01-25T19:33:43.416194110+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:33:43.423350019+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:33:43.434811414+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x48, rssi: -82, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x11, ZCLCommandId: 0x07 >, < ConfigureReportingReponse || ZclStatus: SUCCESS > > >
2022-01-25T19:33:43.450714361+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:33:44.574367907+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler device_lifecycle
2022-01-25T19:33:44.591461783+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received lifecycle event: infoChanged
2022-01-25T19:33:44.598896832+00:00 TRACE Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received unhandled lifecycle event: infoChanged
2022-01-25T19:33:44.605214323+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:34:12.695175951+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-01-25T19:34:42.688026882+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-01-25T19:35:05.802234210+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:35:05.874172161+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8001 >, lqi: 0x38, rssi: -86, body_length: 0x000C, < ZDOMessageBody || < ZDOHeader || seqno: 0x1C >, GenericBody: 00 94 13 65 FE FF 23 A4 60 D4 58 > >
2022-01-25T19:35:05.991014553+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:35:12.694271507+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-01-25T19:35:42.707961852+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-01-25T19:35:45.814317921+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:35:45.970764105+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x3C, rssi: -85, 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-01-25T19:35:46.085023206+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:35:46.101070892+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T19:35:46.110821432+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T19:35:46.207118890+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“off”},“capability_id”:“switch”,“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T19:35:46.284020988+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 false
2022-01-25T19:35:46.296837727+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:35:46.368743995+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:35:46.408735981+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x3C, rssi: -85, 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-01-25T19:35:46.443629419+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:35:46.452000936+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T19:35:46.458577556+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T19:35:46.477148837+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“off”},“capability_id”:“switch”,“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T19:35:46.520305071+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 false
2022-01-25T19:35:46.537843169+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:35:55.567171911+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T19:35:55.699253252+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received command: {“command”:“on”,“positional_args”:,“capability”:“switch”,“component”:“main”,“args”:}
2022-01-25T19:35:55.756071313+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:35:55.775420650+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x58D4, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-01-25T19:35:55.844883697+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T19:35:55.968044247+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:35:56.188079543+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:35:56.243073693+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x38, rssi: -86, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x26, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-01-25T19:35:56.326835219+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:35:56.337551575+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-01-25T19:35:56.352518721+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T19:35:56.390920246+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:35:56.400794180+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:35:56.438361621+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x38, rssi: -86, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x03, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-01-25T19:35:56.457648927+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:35:56.463236719+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T19:35:56.474232881+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T19:35:56.492621738+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T19:35:56.508829171+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 true
2022-01-25T19:35:56.522073456+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled

amin300 · January 25, 2022, 7:41pm

Logs part2
2022-01-25T19:35:57.410437083+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T19:35:57.427854120+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received command: {“command”:“on”,“positional_args”:,“capability”:“switch”,“component”:“switch2”,“args”:}
2022-01-25T19:35:57.434302343+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:35:57.443754733+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x58D4, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-01-25T19:35:57.461238471+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T19:35:57.487378534+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:35:57.725540556+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:35:57.734763498+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x3C, rssi: -85, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x27, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-01-25T19:35:57.749851372+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:35:57.759776999+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-01-25T19:35:57.766734809+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T19:35:57.781816346+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:35:57.788761150+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:35:57.801094314+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x40, rssi: -84, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x04, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-01-25T19:35:57.816233213+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:35:57.822142499+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T19:35:57.827932726+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T19:35:57.836757470+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T19:35:57.852050779+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 true
2022-01-25T19:35:57.858923214+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:35:59.633700159+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:35:59.658418178+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x38, rssi: -86, body_length: 0x0019, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x05, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 >, < AttributeRecord || AttributeId: 0x8001, DataType: Enum8, Enum8: 0x01 >, < AttributeRecord || AttributeId: 0x8002, DataType: Enum8, Enum8: 0x00 > > > >
2022-01-25T19:35:59.674252091+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:35:59.680003299+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T19:35:59.687319622+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T19:35:59.694542231+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T19:35:59.718284430+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 true
2022-01-25T19:35:59.726113676+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:35:59.746369465+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:35:59.761294591+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x3C, rssi: -85, body_length: 0x0011, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x06, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 > > > >
2022-01-25T19:35:59.776847363+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:35:59.782444827+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T19:35:59.790053630+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T19:35:59.798239721+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T19:35:59.816083305+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 true
2022-01-25T19:35:59.824223039+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:36:12.725182962+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-01-25T19:36:42.720157621+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-01-25T19:37:12.730350219+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-01-25T19:37:42.729509636+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-01-25T19:37:58.852293332+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:37:58.865435900+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x38, rssi: -86, 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-01-25T19:37:58.881500929+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:37:58.886747884+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T19:37:58.893282817+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T19:37:58.900790902+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“off”},“capability_id”:“switch”,“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T19:37:58.919880776+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 false
2022-01-25T19:37:58.928810905+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:37:58.976062186+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:37:58.989439204+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x38, rssi: -86, 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-01-25T19:37:59.009035331+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:37:59.016592441+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T19:37:59.023079016+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T19:37:59.030582432+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“off”},“capability_id”:“switch”,“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T19:37:59.048754180+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 false
2022-01-25T19:37:59.058913257+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:38:11.281276718+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:38:11.325682243+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x38, rssi: -86, body_length: 0x0019, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x03, 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-01-25T19:38:11.485252322+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:38:11.498495273+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T19:38:11.517045210+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T19:38:11.527436737+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“off”},“capability_id”:“switch”,“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T19:38:11.567063874+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 false
2022-01-25T19:38:11.582573625+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:38:11.596749376+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:38:11.626616302+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x38, rssi: -86, body_length: 0x0011, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x04, 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-01-25T19:38:11.659858248+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:38:11.665050843+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T19:38:11.671110871+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T19:38:11.683635130+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“off”},“capability_id”:“switch”,“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T19:38:11.715316296+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 false
2022-01-25T19:38:11.725363984+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:38:12.759109932+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-01-25T19:38:18.859988514+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T19:38:18.870201951+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received command: {“command”:“on”,“positional_args”:,“capability”:“switch”,“component”:“main”,“args”:}
2022-01-25T19:38:18.876532115+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:38:18.885125743+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x58D4, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-01-25T19:38:18.907733708+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T19:38:18.937368184+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:38:19.065690313+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:38:19.074758512+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x38, rssi: -86, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x30, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-01-25T19:38:19.093644283+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:38:19.098804529+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-01-25T19:38:19.105772344+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T19:38:19.123046644+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:38:19.129004621+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:38:19.139943755+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x38, rssi: -86, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x05, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-01-25T19:38:19.158043467+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:38:19.163843365+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T19:38:19.170084151+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T19:38:19.177065640+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T19:38:19.193352112+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 true
2022-01-25T19:38:19.201504853+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:38:20.328217595+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T19:38:20.345093695+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received command: {“command”:“on”,“positional_args”:,“capability”:“switch”,“component”:“switch2”,“args”:}
2022-01-25T19:38:20.351473884+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:38:20.359948786+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x58D4, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-01-25T19:38:20.382659469+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T19:38:20.407356478+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:38:20.625384104+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:38:20.635279716+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x3C, rssi: -85, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x31, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-01-25T19:38:20.655359751+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:38:20.660916528+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-01-25T19:38:20.668399601+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T19:38:20.753953690+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T19:38:20.761232661+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T19:38:20.787087582+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x38, rssi: -86, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x06, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-01-25T19:38:20.889134246+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T19:38:20.895556122+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T19:38:20.937071203+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T19:38:20.982991818+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“capability_id”:“switch”,“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T19:38:21.047046163+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 true
2022-01-25T19:38:21.067410340+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled

amin300 · January 25, 2022, 7:51pm

after being away from app, it seems device lose the connection to hub and i cant control device from app ( no response to switch on/off)

Mariano_Colmenarejo · January 25, 2022, 8:04pm

amin300:

2022-01-25T19:37:58.865435900+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 50036b93-03e9-4fcd-84fb-6893b5609012 [0x58D4] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x58D4, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x38, rssi: -86, 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 > > > >

In the logs now a different response is seen, it is sending the shutdown message with the information of the attributes 0x04001, 0x4002 and then the attributes 0x8001 = value 0x01 and 0x8002= value 0x00.

We can try to write 0xFFFF in attribute 0x4001(onTime) and 0xFFFF in attribute 0x4002 (offTime) and try

Since they do it to screw up usage outside of their platform, you may have to write to both clusters

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Multi Switch Zemismart test   │
│ Version     │ 2022-01-25T20:02:07.060971           │
└─────────────┴──────────────────────────────────────┘

Mariano_Colmenarejo · January 25, 2022, 8:40pm

All Edge drivers run local.
If you see cloud un IDE, this information is not valid for Edge drivers

dusanhauko · January 31, 2022, 6:05pm

A question. Sorry if i’m asking about issue that has allready been discussed…
I’ve added Lidl 3xAC+3xUSB power strip with your driver and it shows: main, switch2, switch3.

Is it possible to:
A1. Rename names acording to connected devices
A2. Create child devices ?
B1. Switch also USB ports separately?

Regards, Dusan

Mariano_Colmenarejo · January 31, 2022, 6:13pm

Components cannot be renamed.

It is something that has been requested and I don’t know if it will be possible

You cannot create zigbee child devices in the beta version, only LAN type.

Now, with virtual devices type LAN you can create devices and with routines you can synchronize their state to the state with child devices 2 and 3.

USB ports always are ON, I think

dusanhauko · January 31, 2022, 6:17pm

Thank you for quick response.
For Lidl power plug it’s better for me to stay on DTH for now.
But as i move last of my devices to edge this will bother me a little

Mariano_Colmenarejo · January 31, 2022, 6:19pm

I have 2, one with edge drive and another with DTH, let’s see how the beta phase evolves

uncledaveghr · February 1, 2022, 11:42am

Any idea why i cant get the new edge driver to work on this

application: 01
endpointId: 0B
manufacturer: GLEDOPTO
model: GL-C-008

Raw Description 0B C05E [0210 02 07 0000 0003](tel:0210 02 07 0000 0003) [0004 0005 0006 0008](tel:0004 0005 0006 0008) 0300 00

Mariano_Colmenarejo · February 1, 2022, 12:25pm

That exact model is not in the fingerprints of the driver.
There is the GL-C-008P and GL-C-008S.

What profile do I put, RGB, RGBW?

uncledaveghr · February 1, 2022, 12:42pm

Hi
Its using ZLL RGBW Bulb
on the old IDE at the min

uncledaveghr · February 1, 2022, 12:44pm

uncledaveghr · February 1, 2022, 12:50pm

Mariano_Colmenarejo · February 1, 2022, 2:16pm

Added to this version of driver

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Light Multifunction Mc        │
│ Version     │ 2022-02-01T14:14:27.232487           │
└─────────────┴──────────────────────────────────────┘

  - id: "GLEDOPTO/GL-C-008"
    deviceLabel: GLEDOPTO GL-C-008
    manufacturer: GLEDOPTO
    model: GL-C-008
    deviceProfileName: rgbw-level-colortemp-2700-6500

Crap_Portraits · February 1, 2022, 2:20pm

Tried using the new edge driver for Ikea motion sensors .
All ok but discovered if I installed the aeotec motion sensor after edge drivers in place it used the edge driver for aeotec too Instead of the standard.
Whilst this worked the aeotec showed as cloud rather than local. I had to delete the edge drivers from hub to get it to use the local driver for aeotec.
Is there a less drastic means?

Paul_Oliver · February 1, 2022, 2:31pm

Edge drivers are truly local. The the IDE incorrectly shows them as cloud, because the IDE is part of the Groovy platform.

uncledaveghr · February 1, 2022, 3:39pm

Just tried it and all good.
Thanks a lot for your help
Keep up the good work
Cheers Dave

(EDGE Driver-Mc): Zigbee Drivers for Motion, Open/Close, Moisture, Smoke-Co Sensors and others Devices

Customers

Developers

Download the SmartThings App