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

Mariano_Colmenarejo · May 8, 2022, 10:09am

Added to this version as power plug.
If power and energy do not work tell me and change device to zigbee switch Mc

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Switch Power Mc               │
│ Version     │ 2022-05-08T10:08:38.62751            │
└─────────────┴──────────────────────────────────────┘

  - id: "_TZ3000_ksw8qtmt/TS011F"
    deviceLabel: TS011F Plug
    manufacturer: _TZ3000_ksw8qtmt
    model: TS011F
    deviceProfileName: switch-power-energy-plug

Mariano_Colmenarejo · May 8, 2022, 10:21am

The determination of the offline state is done automatically by the firmware when it does not receive periodic report messages from the device for x time.

As for this device to work I do not have to configure periodic reports, it may have something to do with this.

There is a 120 sec timer, which starts in the init lifecycle, that reads the on-off attributes of switches 1 and 2. If the device answers, an Off or On event should be emitted with the answer, therefore it should not be marked as offline.

The timer should reset itself every time there is a hub reboot or an driver or hub update

Could you send me 5 minutes of logs being switches in off to see if the 120 sec timer is working well and what response it sends?

Mariano_Colmenarejo · May 8, 2022, 10:33am

This device uses the same subdriver for battery handler as the stock zigbee motion sensor, the battery should work, but it may take a while to give the first reading.

You can try to do a refresh or remove the battery, wait a few seconds and reinstall it to see if it emits a new level

amin300 · May 8, 2022, 10:56am

Hi @Mariano_Colmenarejo
Thanks for your reply
I believe the driver is really stable enough but only i have noticed this issue of moving to offline maybe 3 or 4 times so far. Sometime it happens after 2 or 3 days and i am not sure it is something related to driver or not, maybe because i am busy working on something else and having the hub many times in pairing mode!!

Logs

Summary

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:\WINDOWS\system32> cd…
PS C:\WINDOWS> cd…
PS C:> cd \users\aminhsm\documents\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 │ 1d68e5c3-03c0-4229-985d-14e225550049 │ ONVIF Video Camera V1 │
│ 2 │ c411db9e-a042-459a-a145-f005c65412ee │ ST Zigbee Button Mc │
│ 3 │ 86d761b1-e962-4756-a9b2-edab02b8567d │ Tasmota Edge │
│ 4 │ 981aab30-6f78-4b31-bf0b-b422bef161ec │ Yeelight.Color │
│ 5 │ 71915c2a-8604-4cd5-aaba-22988490bcbb │ Z-Wave Switch Mc │
│ 6 │ ad9f537d-e2d9-4354-8673-471a5306fad8 │ Zigbee Button Groups │
│ 7 │ 1e45a851-8f07-48d1-bcbf-932fb377e95e │ Zigbee Dimmer Remote │
│ 8 │ ccea734e-e56e-4d2c-a259-3b2e1fdebd82 │ Zigbee Humidity Sensor │
│ 9 │ 6b86005f-95b4-49cb-a3d5-d3a17fd94177 │ Zigbee Light Multifunction Mc │
│ 10 │ d620900d-f7bc-4ab5-a171-6dd159872f7d │ Zigbee Motion Sensor │
│ 11 │ 00425c55-0932-416f-a1ba-78fae98ab614 │ Zigbee Motion Sensor Mc │
│ 12 │ fe12554c-d40f-439c-a57c-cbc0f27b11dd │ Zigbee Multi Switch Test │
│ 13 │ 580a4441-7d16-437e-8cdc-97c03f59e2df │ Zigbee Switch Mc │
│ 14 │ f732925a-9ae3-462a-9641-f03f474c661e │ Zigbee Switch Power Mc │
│ 15 │ 026385b3-dfa9-43e5-b443-cfc42123f042 │ Zigbee Temp Humidity Sensor Mc │
│ 16 │ bd79913f-0309-4256-b669-74c489b81140 │ Zigbee Temp Humidity Sensor Mc-(OLD) │
└────┴──────────────────────────────────────┴──────────────────────────────────────┘
? Select a driver. 12
connecting… connected
2022-05-08T10:48:23.081778900+00:00 PRINT Zigbee Multi Switch Test <<< Timer read attribute >>>
2022-05-08T10:48:23.089966233+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x102C, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T10:48:23.103565900+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x102C, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T10:48:23.126550900+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:23.437006900+00:00 TRACE Zigbee Multi Switch Test Received event with handler zigbee
2022-05-08T10:48:23.454777567+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x102C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x70, rssi: -72, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x1F, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: false > > > >
2022-05-08T10:48:23.499971900+00:00 TRACE Zigbee Multi Switch Test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T10:48:23.505428567+00:00 INFO Zigbee Multi Switch Test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T10:48:23.511567233+00:00 PRINT Zigbee Multi Switch Test function: on_off_attr_handler
2022-05-08T10:48:23.519912900+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-05-08T10:48:23.538853567+00:00 PRINT Zigbee Multi Switch Test src_endpoint = 1 value = false
2022-05-08T10:48:23.552440567+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:23.558365900+00:00 TRACE Zigbee Multi Switch Test Received event with handler zigbee
2022-05-08T10:48:23.568395900+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x102C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x20, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: false > > > >
2022-05-08T10:48:23.585356567+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:23.593466567+00:00 TRACE Zigbee Multi Switch Test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T10:48:23.598893233+00:00 INFO Zigbee Multi Switch Test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T10:48:23.606670900+00:00 PRINT Zigbee Multi Switch Test function: on_off_attr_handler
2022-05-08T10:48:23.613081233+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-05-08T10:48:23.630736567+00:00 PRINT Zigbee Multi Switch Test src_endpoint = 2 value = false
2022-05-08T10:48:23.643307233+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:23.651434900+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:25.181599234+00:00 PRINT Zigbee Multi Switch Test <<< Timer read attribute >>>
2022-05-08T10:48:25.216626567+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T10:48:25.294956567+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T10:48:25.376930568+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:25.578460234+00:00 PRINT Zigbee Multi Switch Test all_switches_status >>>>>
2022-05-08T10:48:25.617148901+00:00 PRINT Zigbee Multi Switch Test Total_on >>>>>> 0 Total >>> 2
2022-05-08T10:48:25.660810901+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T10:48:25.841892234+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:25.860503901+00:00 TRACE Zigbee Multi Switch Test Received event with handler zigbee
2022-05-08T10:48:25.886723568+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x70, rssi: -72, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x21, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: false > > > >
2022-05-08T10:48:25.910944568+00:00 TRACE Zigbee Multi Switch Test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T10:48:25.919363568+00:00 INFO Zigbee Multi Switch Test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T10:48:25.932956568+00:00 PRINT Zigbee Multi Switch Test function: on_off_attr_handler
2022-05-08T10:48:25.945389234+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-05-08T10:48:25.995493568+00:00 PRINT Zigbee Multi Switch Test src_endpoint = 1 value = false
2022-05-08T10:48:26.027566234+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:26.034169568+00:00 PRINT Zigbee Multi Switch Test all_switches_status >>>>>
2022-05-08T10:48:26.041781234+00:00 PRINT Zigbee Multi Switch Test Total_on >>>>>> 0 Total >>> 2
2022-05-08T10:48:26.056677235+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T10:48:26.084753235+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:26.090332901+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:26.106984235+00:00 TRACE Zigbee Multi Switch Test Received event with handler zigbee
2022-05-08T10:48:26.117018568+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x70, rssi: -72, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x22, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: false > > > >
2022-05-08T10:48:26.144705901+00:00 TRACE Zigbee Multi Switch Test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T10:48:26.153062235+00:00 INFO Zigbee Multi Switch Test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T10:48:26.163813901+00:00 PRINT Zigbee Multi Switch Test function: on_off_attr_handler
2022-05-08T10:48:26.186908235+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-05-08T10:48:26.205660568+00:00 PRINT Zigbee Multi Switch Test src_endpoint = 2 value = false
2022-05-08T10:48:26.236407235+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:26.244301235+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:28.017201902+00:00 PRINT Zigbee Multi Switch Test all_switches_status >>>>>
2022-05-08T10:48:28.023869902+00:00 PRINT Zigbee Multi Switch Test Total_on >>>>>> 0 Total >>> 2
2022-05-08T10:48:28.030373902+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T10:48:28.048689902+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:28.232420569+00:00 PRINT Zigbee Multi Switch Test all_switches_status >>>>>
2022-05-08T10:48:28.239017902+00:00 PRINT Zigbee Multi Switch Test Total_on >>>>>> 0 Total >>> 2
2022-05-08T10:48:28.245922236+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T10:48:28.263802569+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:48:48.306792245+00:00 DEBUG Zigbee Multi Switch Test driver device thread event handled
2022-05-08T10:49:18.316769250+00:00 DEBUG Zigbee Multi Switch Test driver device thread event handled
2022-05-08T10:49:48.316772164+00:00 DEBUG Zigbee Multi Switch Test driver device thread event handled
2022-05-08T10:50:18.327569845+00:00 DEBUG Zigbee Multi Switch Test driver device thread event handled
2022-05-08T10:50:23.084478847+00:00 PRINT Zigbee Multi Switch Test <<< Timer read attribute >>>
2022-05-08T10:50:23.092848181+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x102C, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T10:50:23.106606181+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x102C, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T10:50:23.127190847+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:50:23.264569847+00:00 TRACE Zigbee Multi Switch Test Received event with handler zigbee
2022-05-08T10:50:23.283107847+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x102C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x24, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: false > > > >
2022-05-08T10:50:23.318767514+00:00 TRACE Zigbee Multi Switch Test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T10:50:23.324062514+00:00 INFO Zigbee Multi Switch Test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T10:50:23.329922514+00:00 PRINT Zigbee Multi Switch Test function: on_off_attr_handler
2022-05-08T10:50:23.336495847+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-05-08T10:50:23.367980514+00:00 PRINT Zigbee Multi Switch Test src_endpoint = 1 value = false
2022-05-08T10:50:23.382635181+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:50:23.388457181+00:00 TRACE Zigbee Multi Switch Test Received event with handler zigbee
2022-05-08T10:50:23.398649847+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x102C, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x25, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: false > > > >
2022-05-08T10:50:23.416632847+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:50:23.424688181+00:00 TRACE Zigbee Multi Switch Test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T10:50:23.430278181+00:00 INFO Zigbee Multi Switch Test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T10:50:23.436148514+00:00 PRINT Zigbee Multi Switch Test function: on_off_attr_handler
2022-05-08T10:50:23.442721847+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-05-08T10:50:23.461872181+00:00 PRINT Zigbee Multi Switch Test src_endpoint = 2 value = false
2022-05-08T10:50:23.474741514+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:50:23.482612514+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:50:25.183790182+00:00 PRINT Zigbee Multi Switch Test <<< Timer read attribute >>>
2022-05-08T10:50:25.192077848+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T10:50:25.210622182+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T10:50:25.299270848+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:50:25.387937515+00:00 PRINT Zigbee Multi Switch Test all_switches_status >>>>>
2022-05-08T10:50:25.431534182+00:00 PRINT Zigbee Multi Switch Test Total_on >>>>>> 0 Total >>> 2
2022-05-08T10:50:25.464655515+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T10:50:25.549228182+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:50:25.646366182+00:00 PRINT Zigbee Multi Switch Test all_switches_status >>>>>
2022-05-08T10:50:25.658552515+00:00 PRINT Zigbee Multi Switch Test Total_on >>>>>> 0 Total >>> 2
2022-05-08T10:50:25.728014848+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 88552b9b-f088-41f4-89b9-1e02cb11face [0x102C] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T10:50:25.847173182+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:50:25.881464182+00:00 TRACE Zigbee Multi Switch Test Received event with handler zigbee
2022-05-08T10:50:25.968346515+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x26, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: false > > > >
2022-05-08T10:50:26.066616515+00:00 TRACE Zigbee Multi Switch Test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T10:50:26.094789849+00:00 INFO Zigbee Multi Switch Test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T10:50:26.108299849+00:00 PRINT Zigbee Multi Switch Test function: on_off_attr_handler
2022-05-08T10:50:26.123295849+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-05-08T10:50:26.168431849+00:00 PRINT Zigbee Multi Switch Test src_endpoint = 1 value = false
2022-05-08T10:50:26.202947182+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:50:26.216893182+00:00 TRACE Zigbee Multi Switch Test Received event with handler zigbee
2022-05-08T10:50:26.234575182+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x27, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: false > > > >
2022-05-08T10:50:26.258808182+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:50:26.271310182+00:00 TRACE Zigbee Multi Switch Test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T10:50:26.279883849+00:00 INFO Zigbee Multi Switch Test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T10:50:26.289140182+00:00 PRINT Zigbee Multi Switch Test function: on_off_attr_handler
2022-05-08T10:50:26.301306515+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-05-08T10:50:26.332490515+00:00 PRINT Zigbee Multi Switch Test src_endpoint = 2 value = false
2022-05-08T10:50:26.352585182+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:50:26.366783849+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:50:28.199584183+00:00 PRINT Zigbee Multi Switch Test all_switches_status >>>>>
2022-05-08T10:50:28.217556183+00:00 PRINT Zigbee Multi Switch Test Total_on >>>>>> 0 Total >>> 2
2022-05-08T10:50:28.227306516+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T10:50:28.258341183+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled
2022-05-08T10:50:28.355882516+00:00 PRINT Zigbee Multi Switch Test all_switches_status >>>>>
2022-05-08T10:50:28.362034183+00:00 PRINT Zigbee Multi Switch Test Total_on >>>>>> 0 Total >>> 2
2022-05-08T10:50:28.368703183+00:00 INFO Zigbee Multi Switch Test <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T10:50:28.388590183+00:00 DEBUG Zigbee Multi Switch Test TS0012 Switch device thread event handled

One more question maybe more related to CLI time stamp
Is it normal to have not correct time zone? Hub and pc time zone are correct!

Mariano_Colmenarejo · May 8, 2022, 11:53am

The logs show that every 120 sec the on-off attribute of switches 1 and 2 is read, there is a response of their status and the event is emitted.

It should not show offline lest the connection to the hub be lost at some point.

When you stay offline, how do you get back online when you turn on the physical switch?
If it goes offline again, try sending an On command with a scene to see how the device reacts.

I made a new version of the zigbee multi switch Mc, so it goes offline again and you want to try, but the multiple mosaic doesn’t work yet, let’s see if they fix it soon.

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Multi Switch Mc               │
│ Version     │ 2022-05-08T09:59:07.283133           │
└─────────────┴──────────────────────────────────────┘

I don’t know if I understood your question correctly
I have no idea why they have chosen that the CLI always works with the UTC time for their timestamps, I guess that it is also a valid reference for everyone and to know which version is the most modern

amin300 · May 8, 2022, 12:13pm

What do you mean it goes offline? Sorry but i did not get it

eric182 · May 8, 2022, 12:20pm

@Mariano_Colmenarejo

Can you please add these temperature and humidity sensors to your driver?

Mariano_Colmenarejo · May 8, 2022, 12:24pm

I meant that if the device goes offline again and you want to try this version

amin300 · May 8, 2022, 12:28pm

Sure, i will try it and let you know
Have you changed anything related to offline?

Mariano_Colmenarejo · May 8, 2022, 12:35pm

Yes, I changed something, among them the custom vids of the multiple mosaic, they were missing the refresh capability and I added it.
If there is no refresh capability in the presentation, it does not run correctly.

Mariano_Colmenarejo · May 8, 2022, 12:40pm

Sorry Erick, this driver has a custom presentation vid and until smartthings fixes the problem with these drivers I can’t add anything as packaging the new version of the driver breaks it for all current users.

As soon as they fix it I’ll add it and let you know

eric182 · May 8, 2022, 12:46pm

So I switched these motion sensors to the stock edge driver from the Smartthings channel and now they report battery.

eric182 · May 8, 2022, 12:47pm

@nayelyz can You guys please add these?

amin300 · May 8, 2022, 7:51pm

Hi Mariano

I have moved to this updated driver and now the switch switched off by itself
Already switched OFF 3 times (Not OFFLINE) so far, but last time i used timer and it is approx after 4 minutes

I could capture logs once switch is switched OFF - please check last part of logs

Logs part 1

Summary

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 │ 1d68e5c3-03c0-4229-985d-14e225550049 │ ONVIF Video Camera V1 │
│ 2 │ c411db9e-a042-459a-a145-f005c65412ee │ ST Zigbee Button Mc │
│ 3 │ 86d761b1-e962-4756-a9b2-edab02b8567d │ Tasmota Edge │
│ 4 │ 981aab30-6f78-4b31-bf0b-b422bef161ec │ Yeelight.Color │
│ 5 │ 71915c2a-8604-4cd5-aaba-22988490bcbb │ Z-Wave Switch Mc │
│ 6 │ ad9f537d-e2d9-4354-8673-471a5306fad8 │ Zigbee Button Groups │
│ 7 │ 1e45a851-8f07-48d1-bcbf-932fb377e95e │ Zigbee Dimmer Remote │
│ 8 │ ccea734e-e56e-4d2c-a259-3b2e1fdebd82 │ Zigbee Humidity Sensor │
│ 9 │ 6b86005f-95b4-49cb-a3d5-d3a17fd94177 │ Zigbee Light Multifunction Mc │
│ 10 │ d620900d-f7bc-4ab5-a171-6dd159872f7d │ Zigbee Motion Sensor │
│ 11 │ 00425c55-0932-416f-a1ba-78fae98ab614 │ Zigbee Motion Sensor Mc │
│ 12 │ 91a22a50-31a2-4177-9999-8ed3770bfee6 │ Zigbee Multi Switch Mc │
│ 13 │ fe12554c-d40f-439c-a57c-cbc0f27b11dd │ Zigbee Multi Switch Test │
│ 14 │ 580a4441-7d16-437e-8cdc-97c03f59e2df │ Zigbee Switch Mc │
│ 15 │ f732925a-9ae3-462a-9641-f03f474c661e │ Zigbee Switch Power Mc │
│ 16 │ 026385b3-dfa9-43e5-b443-cfc42123f042 │ Zigbee Temp Humidity Sensor Mc │
│ 17 │ bd79913f-0309-4256-b669-74c489b81140 │ Zigbee Temp Humidity Sensor Mc-(OLD) │
└────┴──────────────────────────────────────┴──────────────────────────────────────┘
? Select a driver. 12
connecting… connected
2022-05-08T19:36:23.452665575+00:00 DEBUG Zigbee Multi Switch Mc driver device thread event handled
2022-05-08T19:36:24.969768644+00:00 TRACE Zigbee Multi Switch Mc Received event with handler capability
2022-05-08T19:36:25.018443961+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received command: {“args”:{“value”:“All Off”},“capability”:“legendabsolute60149.switchAllOnOff1”,“command”:“setSwitchAllOnOff”,“component”:“main”,“positional_args”:[“All Off”]}
2022-05-08T19:36:25.024712159+00:00 TRACE Zigbee Multi Switch Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:36:25.030107793+00:00 PRINT Zigbee Multi Switch Mc command.args.value >>>>> All Off
2022-05-08T19:36:25.036626865+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T19:36:25.060104120+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < Off || > > >
2022-05-08T19:36:25.116252366+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < Off || > > >
2022-05-08T19:36:25.144940681+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:25.361291452+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:36:25.372323599+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x25, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >
2022-05-08T19:36:25.399371402+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:36:25.405462355+00:00 INFO Zigbee Multi Switch Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-05-08T19:36:25.418495169+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-05-08T19:36:25.857761093+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:25.865095757+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:36:25.875769751+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x07, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-05-08T19:36:25.890476394+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:36:25.895920004+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:36:25.903473558+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:36:25.909916669+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-05-08T19:36:25.924892177+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 1 value = false
2022-05-08T19:36:25.935550512+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:25.941302968+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:36:25.952409078+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x26, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >
2022-05-08T19:36:25.966724251+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:25.972559998+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:36:25.982499359+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x08, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-05-08T19:36:26.000811199+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:36:26.006315112+00:00 INFO Zigbee Multi Switch Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-05-08T19:36:26.015276629+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-05-08T19:36:26.032743891+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:26.042219484+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:36:26.050051233+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:36:26.056489012+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:36:26.063254628+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-05-08T19:36:26.077975930+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 2 value = false
2022-05-08T19:36:26.088916790+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:26.096848822+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:27.768399296+00:00 TRACE Zigbee Multi Switch Mc Received event with handler capability
2022-05-08T19:36:27.872151061+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received command: {“args”:{“value”:“All On”},“capability”:“legendabsolute60149.switchAllOnOff1”,“command”:“setSwitchAllOnOff”,“component”:“main”,“positional_args”:[“All On”]}
2022-05-08T19:36:27.910658131+00:00 TRACE Zigbee Multi Switch Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:36:27.943948478+00:00 PRINT Zigbee Multi Switch Mc command.args.value >>>>> All On
2022-05-08T19:36:27.994094059+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:36:28.035269461+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-05-08T19:36:28.083517658+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-05-08T19:36:28.120563793+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:28.141910780+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:36:28.153697884+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 0 Total >>> 2
2022-05-08T19:36:28.182808988+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T19:36:28.236144640+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:28.251955730+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:36:28.266215930+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 0 Total >>> 2
2022-05-08T19:36:28.284081659+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T19:36:28.298841942+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:28.390314850+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:36:28.409451277+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x27, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-05-08T19:36:28.474269851+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:36:28.485616841+00:00 INFO Zigbee Multi Switch Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-05-08T19:36:28.506693631+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-05-08T19:36:28.573343290+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:28.608581995+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:36:28.623743077+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x09, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:36:28.677851676+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:36:28.700168179+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:36:28.712979770+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:36:28.733696073+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-05-08T19:36:28.768695565+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 1 value = true
2022-05-08T19:36:28.779525814+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:28.785279269+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:36:28.802459674+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x28, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-05-08T19:36:28.816256439+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:28.826783839+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:36:28.839506142+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x0A, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:36:28.873991890+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:36:28.879289573+00:00 INFO Zigbee Multi Switch Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-05-08T19:36:28.885859287+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-05-08T19:36:28.912597578+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:28.923990545+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:36:28.938222092+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:36:28.948683859+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:36:28.961256569+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-05-08T19:36:28.979149952+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 2 value = true
2022-05-08T19:36:28.989881583+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:28.997858593+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:30.790241620+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:36:30.796882298+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:36:30.804462839+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:36:30.821739530+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:31.000136620+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:36:31.006169269+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:36:31.012671683+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:36:31.028563066+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:53.453862146+00:00 DEBUG Zigbee Multi Switch Mc driver device thread event handled
2022-05-08T19:36:59.693701001+00:00 PRINT Zigbee Multi Switch Mc <<< Timer read attribute >>>
2022-05-08T19:36:59.745746299+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:36:59.774153754+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:36:59.844495233+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:36:59.860278337+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:36:59.876731440+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:59.892446245+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:36:59.911109576+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:36:59.920581504+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2B, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:36:59.947108900+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:36:59.952546513+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:36:59.968365600+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:36:59.983748571+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}

amin300 · May 8, 2022, 7:51pm

Logs
Part 2

Summary

2022-05-08T19:37:00.001952132+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 1 value = true
2022-05-08T19:37:00.015536823+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:00.024974147+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:00.207016303+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:37:00.220282331+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2C, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:37:00.235521423+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:37:00.240952175+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:37:00.247007298+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:37:00.255207734+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-05-08T19:37:00.272856347+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 2 value = true
2022-05-08T19:37:00.285607621+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:00.291315575+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:37:00.300144712+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2D, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:37:00.321713462+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:00.327982816+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:37:00.338012050+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2E, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:37:00.365170144+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:37:00.388670976+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:37:00.397572745+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:37:00.418351537+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-05-08T19:37:00.469752777+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 1 value = true
2022-05-08T19:37:00.513726879+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:00.529067256+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:37:00.553970421+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:37:00.559936253+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:37:00.569376100+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-05-08T19:37:00.607719212+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 2 value = true
2022-05-08T19:37:00.622989288+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:00.631335655+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:00.639729666+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:01.881714312+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:37:01.907181646+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:37:01.929169646+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:02.022616312+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:37:02.029346646+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:37:02.036089979+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:37:02.053397979+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:02.129819979+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:37:02.140930312+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2F, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:37:02.159963646+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:37:02.171354979+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:37:02.177899312+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:37:02.197003312+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-05-08T19:37:02.229535646+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 1 value = true
2022-05-08T19:37:02.327321312+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:02.373475312+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:02.403973979+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:37:02.445155312+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x30, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:37:02.505900312+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:37:02.534735979+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:37:02.583480312+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:37:02.612820312+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-05-08T19:37:02.787475312+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 2 value = true
2022-05-08T19:37:02.911130979+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:03.033415312+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:03.101099979+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:37:03.123059646+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:37:03.138148312+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:37:03.174553646+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:03.187834979+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:37:03.201878646+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:37:03.224002979+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:37:03.254750646+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:03.275190646+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:37:03.284115646+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:37:03.290545312+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:37:03.319431979+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:04.319927979+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:37:04.326624312+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:37:04.333588312+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:37:04.350620979+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:04.863828313+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:37:04.889211979+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:37:04.897605646+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:37:04.915101313+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:37:23.463869981+00:00 DEBUG Zigbee Multi Switch Mc driver device thread event handled
2022-05-08T19:37:53.473868652+00:00 DEBUG Zigbee Multi Switch Mc driver device thread event handled
2022-05-08T19:38:23.484622655+00:00 DEBUG Zigbee Multi Switch Mc driver device thread event handled
2022-05-08T19:38:53.483886821+00:00 DEBUG Zigbee Multi Switch Mc driver device thread event handled
2022-05-08T19:38:59.696314824+00:00 PRINT Zigbee Multi Switch Mc <<< Timer read attribute >>>
2022-05-08T19:38:59.743096491+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:38:59.778351491+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:38:59.795387157+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:38:59.823680491+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:38:59.852118491+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:38:59.872175157+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:38:59.952478824+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:38:59.969006157+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x34, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:39:00.017872824+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:39:00.023607491+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:39:00.029424157+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:39:00.036091491+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-05-08T19:39:00.053925157+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 1 value = true
2022-05-08T19:39:00.068230491+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:00.074422824+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:39:00.083516491+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x7C, rssi: -69, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x35, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:39:00.097954157+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:00.107211824+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:39:00.112785491+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:39:00.118549824+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:39:00.125545157+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-05-08T19:39:00.144571824+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 2 value = true
2022-05-08T19:39:00.160628157+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:00.172079491+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:00.180336157+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:39:00.197214158+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x36, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:39:00.216872824+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:39:00.222752158+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:39:00.228456158+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:39:00.234989824+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-05-08T19:39:00.252573491+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 1 value = true
2022-05-08T19:39:00.266085158+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:00.271857491+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:39:00.280543824+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x37, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:39:00.295011824+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:00.304067824+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:39:00.309586491+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:39:00.317254491+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:39:00.326448491+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-05-08T19:39:00.347792824+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 2 value = true
2022-05-08T19:39:00.361536824+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:00.369503158+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:01.852480158+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:39:01.877012825+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:39:01.895911158+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:02.069725492+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:39:02.076618825+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:39:02.083302158+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:39:02.100758158+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:02.166514158+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:39:02.177293158+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:39:02.185340825+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:39:02.204897158+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:02.215702492+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:39:02.228188492+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x38, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:39:02.242973825+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:39:02.250394158+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:39:02.256459492+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:39:02.264814492+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-05-08T19:39:02.283004158+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 1 value = true
2022-05-08T19:39:02.295993825+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:02.301658159+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:39:02.310412825+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x39, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:39:02.327263825+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:02.333945492+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:39:02.339377825+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:39:02.345255159+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:39:02.351787825+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-05-08T19:39:02.419670825+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 2 value = true
2022-05-08T19:39:02.485306825+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:02.529037492+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:02.563741825+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:39:02.593648159+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:39:02.623938159+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:39:02.774520159+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:02.863703159+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:39:02.908037159+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:39:03.033912492+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:39:03.212342159+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:04.301902159+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:39:04.308657493+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:39:04.315312159+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:39:04.332896493+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:04.452170160+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:39:04.458836493+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:39:04.465540493+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:39:04.484088826+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:39:23.493858835+00:00 DEBUG Zigbee Multi Switch Mc driver device thread event handled
2022-05-08T19:39:53.493835183+00:00 DEBUG Zigbee Multi Switch Mc driver device thread event handled

amin300 · May 8, 2022, 7:52pm

Logs
Part 3

Summary

2022-05-08T19:40:23.503876864+00:00 DEBUG Zigbee Multi Switch Mc driver device thread event handled
2022-05-08T19:40:53.877623212+00:00 DEBUG Zigbee Multi Switch Mc driver device thread event handled
2022-05-08T19:40:59.713931548+00:00 PRINT Zigbee Multi Switch Mc <<< Timer read attribute >>>
2022-05-08T19:40:59.733737215+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:40:59.794131215+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:40:59.819100548+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:40:59.852481548+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:40:59.875491881+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:40:59.891758215+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:40:59.999994215+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:41:00.010220881+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x3C, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:41:00.061480881+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:41:00.067100881+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:41:00.072926881+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:41:00.079523548+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-05-08T19:41:00.097416215+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 1 value = true
2022-05-08T19:41:00.111628215+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:00.119530548+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:00.571183882+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:41:00.590214215+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x70, rssi: -72, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x3E, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-05-08T19:41:00.631889882+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:41:00.639199882+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:41:00.660577215+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:41:00.675218548+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-05-08T19:41:00.712536882+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 1 value = true
2022-05-08T19:41:00.735541882+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:00.749613215+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:01.882388216+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:41:01.903601882+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x10DF, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-05-08T19:41:01.925284549+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:02.120287216+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:41:02.127203549+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:41:02.133676216+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:41:02.151888216+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:02.881254549+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:41:02.932998883+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 2 Total >>> 2
2022-05-08T19:41:03.021188883+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All On”}}
2022-05-08T19:41:03.179976883+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:04.033473550+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:41:04.047595217+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x3D, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: false > > > >
2022-05-08T19:41:04.071656550+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:41:04.079397883+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:41:04.092854550+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:41:04.100745550+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-05-08T19:41:04.118673883+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 2 value = false
2022-05-08T19:41:04.139615217+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:04.145513217+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:41:04.158501883+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x3F, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: false > > > >
2022-05-08T19:41:04.173470550+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:04.179252883+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:41:04.190766883+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x40, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: false > > > >
2022-05-08T19:41:04.205945883+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:41:04.211285550+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:41:04.217238217+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:41:04.223754550+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-05-08T19:41:04.238597550+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 2 value = false
2022-05-08T19:41:04.250933883+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:04.256798550+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:41:04.266515217+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x78, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x41, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: false > > > >
2022-05-08T19:41:04.283095550+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:41:04.290108217+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:41:04.297158883+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:41:04.303740883+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-05-08T19:41:04.321119883+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 1 value = false
2022-05-08T19:41:04.334453550+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:04.342626550+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:04.350985550+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:41:04.356718883+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:41:04.362604883+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:41:04.369149217+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-05-08T19:41:04.383849550+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 2 value = false
2022-05-08T19:41:04.395168217+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:04.403920217+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:04.411773883+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:05.064297884+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:41:05.094457550+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, 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-05-08T19:41:05.113146217+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:41:05.123773884+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:41:05.138507217+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:41:05.146124550+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-05-08T19:41:05.161283217+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 1 value = false
2022-05-08T19:41:05.172214217+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:05.181028550+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:05.283347550+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:41:05.299404217+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, 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-05-08T19:41:05.329571884+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:41:05.336093217+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:41:05.342425884+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:41:05.348883884+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-05-08T19:41:05.366668217+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 2 value = false
2022-05-08T19:41:05.379887551+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:05.388756217+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:06.140227218+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:41:06.146980884+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 0 Total >>> 2
2022-05-08T19:41:06.153659218+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T19:41:06.170977218+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:06.260837551+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:41:06.266911884+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 0 Total >>> 2
2022-05-08T19:41:06.273500884+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T19:41:06.289352218+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:06.341463218+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:41:06.347523551+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 0 Total >>> 2
2022-05-08T19:41:06.354332884+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T19:41:06.370524884+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:06.425931884+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:41:06.433018218+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 0 Total >>> 2
2022-05-08T19:41:06.441844884+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T19:41:06.486663884+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:07.180947885+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:41:07.187696885+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 0 Total >>> 2
2022-05-08T19:41:07.194387218+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T19:41:07.211863551+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:07.389512551+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:41:07.396204218+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 0 Total >>> 2
2022-05-08T19:41:07.403116218+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T19:41:07.420606551+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:18.192891890+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:41:18.313918557+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, 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-05-08T19:41:18.447902890+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:41:18.464185557+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:41:18.470174890+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:41:18.476668890+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-05-08T19:41:18.508905890+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 1 value = false
2022-05-08T19:41:18.532809223+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:18.538711890+00:00 TRACE Zigbee Multi Switch Mc Received event with handler zigbee
2022-05-08T19:41:18.548435890+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x10DF, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, 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-05-08T19:41:18.575521557+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:18.586281223+00:00 TRACE Zigbee Multi Switch Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-05-08T19:41:18.594896223+00:00 INFO Zigbee Multi Switch Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-05-08T19:41:18.606138890+00:00 PRINT Zigbee Multi Switch Mc function: on_off_attr_handler
2022-05-08T19:41:18.612817890+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-05-08T19:41:18.646872557+00:00 PRINT Zigbee Multi Switch Mc src_endpoint = 2 value = false
2022-05-08T19:41:18.672653557+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:18.680971890+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:20.532760558+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:41:20.539697224+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 0 Total >>> 2
2022-05-08T19:41:20.546394558+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T19:41:20.564309891+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:20.670904558+00:00 PRINT Zigbee Multi Switch Mc all_switches_status >>>>>
2022-05-08T19:41:20.676868891+00:00 PRINT Zigbee Multi Switch Mc Total_on >>>>>> 0 Total >>> 2
2022-05-08T19:41:20.683458558+00:00 INFO Zigbee Multi Switch Mc <ZigbeeDevice: 1d30914e-938a-40eb-97e6-20a3e70e7aa2 [0x10DF] (TS0012 Switch)> emitting event: {“attribute_id”:“switchAllOnOff”,“capability_id”:“legendabsolute60149.switchAllOnOff1”,“component_id”:“main”,“state”:{“value”:“All Off”}}
2022-05-08T19:41:20.701595224+00:00 DEBUG Zigbee Multi Switch Mc TS0012 Switch device thread event handled
2022-05-08T19:41:23.860352559+00:00 DEBUG Zigbee Multi Switch Mc driver device thread event handled

Mariano_Colmenarejo · May 9, 2022, 11:41am

@amin300,

Hi Amin,

Leave the part of the code of that device as it was in the Test version

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Multi Switch Mc               │
│ Version     │ 2022-05-09T16:17:17.601559           │
└─────────────┴──────────────────────────────────────┘

amin300 · May 9, 2022, 12:30pm

Hi @Mariano_Colmenarejo

Thanks, I will test this and let you know.
BTW, Did you find anything in the reports which I sent to you (logs include once switch turned OFF/Last part)?
The reason why I am asking, because the switch turn OFF randomly, sometime stays On for 2 -3 hours, sometime 3 - 4 minutes
I am not sure what is triggering the switch to turn OFF!!

Mariano_Colmenarejo · May 9, 2022, 12:56pm

Does work fine eith driver Test?

I will look at it carefully, it may be that if the attribute reading does not arrive on time, due to some delay, the auto-off timer will start

amin300 · May 9, 2022, 12:59pm

It works very fine with driver Test except the OFFLINE issue which i reported before

Topic		Replies	Views
(EDGE Driver-Mc): Zigbee Light Multifunction Mc Community Created Device Types edge_lighting	1385	56718	June 28, 2025
Cleverio Motion sensor Connected Things	3	110	February 12, 2025
What is Mariano Shared Beta Driver? Community Created Device Types	126	8322	March 2, 2025
Https://community.smartthings.com/t/beta-zigbee-edge-driver-compatible-with-lidl-ecosmart-osram-smartthings-others/231689/30 Community Created Device Types	0	351	October 20, 2021
Edge Driver for Third Reality Zigbee Devices? Devices & Integrations	6	3522	June 13, 2023

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

Related topics