Hopefully someone else will figure it out. I do appreciate you responding and all that you’ve done for the community. Thank you.
I need the fingerprint device model too
until Monday or Tuesday I will not be able to modify or add anything
Hi, @Mariano_Colmenarejo thanks for contributing to smartthings.
I’m using THIS kind of zigbee switches. Can you please add fingerprint to edge driver because the switch is not recognized. It worked before with these two different DHTs
Fingerprint device models:
hi quick question i have a couple of sonoff contact sensors (snzb-04) im using the zigbee contact sensor mc driver but for the last week every couple of days i have to re pair them to get them to work.
the app show them as connected but does not do anything when they are opened or closed i have tried rebooting my hub but only re pairing works , how can they become deteched.i know some contact sensors sleep but they work when woken not these .
thanks
martin
These devices work like buttons, I don’t have any drivers that work with them.
Maybe @ygerlovin has a working driver
Hi @montyfert
The ewelink model DS01, that is in this driver, was detected with the logs of several users, that the periodic reports of 300 sec of IASZone were not configured correctly, and therefore the driver marked it as offline after a while without receiving messages.
I don’t know if the problem is in all devices of this model or in some specific firmware versions.
The stock driver also has this same problem, smartthings chose another way to fix it, which is to set the battery reports every 600 sec instead of 21600 sec.
I don’t know if this has solved the problem with the stock driver, I haven’t seen comments about it.
With my driver, you won’t see the device offline, but it can lose connection if the zigbee network has problems.
You can try the stock driver and see if it no longer stays offline after a while.
Keep in mind that for the device to be configured you have to pair it directly with the stock driver, it is not worth making a driver change. (I have never agreed with the fact that doConfigure is not performed in a change lifecycle driver and my drivers generally do, not all, just the ones where the configuration is critical for proper functioning)
If the stock driver works fine for you, I can implement the solution from the stock driver to my driver
I need see the last character of manufacturer, is a 6?
You can see data in device history too
thank you i will give the stock driver a go .
martin
Thank you,
@ygerlovin your edge driver “Zigbee Button Remote Driver [YG] 1.3.8” works for one button remote but not for 2 and 3 buttons. Can you please add it?
Added to this driver version
───────────────────────────────────────────────────
Name Zigbee Multi Switch and Child Mc
Version 2022-12-06T11:51:05.488169248
───────────────────────────────────────────────────
- id: "Yagusmart/_TZ3000_hlwm8e96"
deviceLabel: Yagusmart 3 Switch
manufacturer: _TZ3000_hlwm8e96
model: TS0013
deviceProfileName: three-switch
Hi @gpliats
If it is disconnected, it may be that the signal of your zigbee network does not reach the device with good quality or power.
It may also be that it has not been configured correctly in the pairing and does not send periodic reports.
You can try to uninstall and re-pair it near the Hub
Hi @muro
Added to this driver version
───────────────────────────────────────────────────
Name Zigbee Contact Mc
Version 2022-12-06T12:06:20.031298232
───────────────────────────────────────────────────
- id: "TUYATEC-rkqiqvcs/Close Sensor"
deviceLabel: RH3001 Open/Close Sensor
manufacturer: TUYATEC-rkqiqvcs
model: RH3001
deviceProfileName: contact-battery-profile
Hello.
Thank you. I have already paired it at least 3 times and the result still the same. It goes online for a while without fetching any results and after a few minutes it goes offline.
As for the signal strength it replaced a TS0002 which had no problem.
I will move it closer to the hub just in case but I don’t think that’s a problem.
Thank you in advance
Yiannis
I don’t know what can happen.
If you want, you can send me the pairing CLI logs to see if any error is occurring that causes it to not configure correctly
Hi @dotan_shai
Added signal metrics read from messages received in Hub
───────────────────────────────────────────────────
Name Zigbee Range Extender Mc
Version 2022-12-06T13:55:53.052640078
───────────────────────────────────────────────────
1 Like
Will do so.
smartthings edge:drivers:logcat brings all drivers logs.
How can I bring only logs from a specific device?
Thank you
You can select the number of the driver.
All devices paired with this driver will appears
Select the driver in logcat
Unistall device with App
Re-install device with search nerby option
Pairing logs appears after several seconds
Capture 30 sec logs or more
Hello again.
I include the logs from the pairing process.
It is strange that the led light of the device was still blinking even after the device was discoverd, like that the pairing process didn’t finish.
The device is connected but says “coudn’t get device status” and inside under singal metrics, “Waiting Zigbee Message”
Thank you.
2022-12-06T16:32:48.395188933+00:00 DEBUG Zigbee Multi Switch and Child Mc Bathroom Lights device thread event handled
2022-12-06T16:33:24.402633646+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler device_lifecycle
2022-12-06T16:33:24.423670062+00:00 TRACE Zigbee Multi Switch and Child Mc Zigbee Device: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8
Manufacturer: _TZ3000_ltt60asa Model: TS0004
[1]: Identify, Groups, Scenes, OnOff, SimpleMetering, ElectricalMeasurement, 0xE000, 0xE001, Basic [2]: Groups, Scenes, OnOff [3]: Groups, Scenes, OnOff [4]: Groups, Scenes, OnOff [242]:
2022-12-06T16:33:24.427202812+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received lifecycle event: added
2022-12-06T16:33:24.437889271+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler device_lifecycle
2022-12-06T16:33:24.441439729+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received lifecycle event: doConfigure
2022-12-06T16:33:24.448467354+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-12-06T16:33:24.452709104+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:24.458458479+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-12-06T16:33:24.461747312+00:00 PRINT Zigbee Multi Switch and Child Mc device_network_id >>> 853F
2022-12-06T16:33:24.464833729+00:00 PRINT Zigbee Multi Switch and Child Mc label >>> TS0004 Switch
2022-12-06T16:33:24.468054771+00:00 PRINT Zigbee Multi Switch and Child Mc parent_device_id >>> 1dadffbd-df61-4ef7-88a7-a9879403efd5
2022-12-06T16:33:24.471131562+00:00 PRINT Zigbee Multi Switch and Child Mc manufacturer >>>
2022-12-06T16:33:24.476035771+00:00 PRINT Zigbee Multi Switch and Child Mc model >>>
2022-12-06T16:33:24.479275104+00:00 PRINT Zigbee Multi Switch and Child Mc vendor_provided_label >>>
2022-12-06T16:33:24.484274729+00:00 PRINT Zigbee Multi Switch and Child Mc Parent_devices[cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8]>>>>>> <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)>
2022-12-06T16:33:24.487500562+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch3Child Preference value: No
2022-12-06T16:33:24.491314646+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch1Child Preference value: No
2022-12-06T16:33:24.494244354+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch2Child Preference value: No
2022-12-06T16:33:24.497568062+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> version Preference value:
2022-12-06T16:33:24.500579979+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> changeProfileFourSw Preference value: Single
2022-12-06T16:33:24.508033854+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> restoreState Preference value: 255
2022-12-06T16:33:24.511627854+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> switch4Child Preference value: No
2022-12-06T16:33:24.514550979+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference name: >> signalMetricsVisibles Preference value: No
2022-12-06T16:33:24.517588521+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Read Basic clusters attributes >>>
2022-12-06T16:33:24.521187729+00:00 PRINT Zigbee Multi Switch and Child Mc <<<< attr_id >>>> {4, 0, 1, 5, 7, 65534}
2022-12-06T16:33:24.525210979+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0004, AttributeId: 0x0000, AttributeId: 0x0001, AttributeId: 0x0005, AttributeId: 0x0007, AttributeId: 0xFFFE > > >
2022-12-06T16:33:24.533132896+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138A736258B8B, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x03, dest_address: D052A8A7F1D60001, dest_endpoint: 0x01 > > >
2022-12-06T16:33:24.548235562+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-12-06T16:33:24.564876896+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x02, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138A736258B8B, src_endpoint: 0x02, cluster: OnOff, dest_addr_mode: 0x03, dest_address: D052A8A7F1D60001, dest_endpoint: 0x01 > > >
2022-12-06T16:33:24.572635229+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-12-06T16:33:24.586674562+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x03, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138A736258B8B, src_endpoint: 0x03, cluster: OnOff, dest_addr_mode: 0x03, dest_address: D052A8A7F1D60001, dest_endpoint: 0x01 > > >
2022-12-06T16:33:24.595865312+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-12-06T16:33:24.604442229+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x04, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138A736258B8B, src_endpoint: 0x04, cluster: OnOff, dest_addr_mode: 0x03, dest_address: D052A8A7F1D60001, dest_endpoint: 0x01 > > >
2022-12-06T16:33:24.613873187+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x04, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-12-06T16:33:24.631379396+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“Waiting Zigbee Message”},“visibility”:{“displayed”:false}}
2022-12-06T16:33:24.643379062+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:24.649162354+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-12-06T16:33:24.659397479+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138A736258B8B, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x03, dest_address: D052A8A7F1D60001, dest_endpoint: 0x01 > > >
2022-12-06T16:33:24.666925938+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-12-06T16:33:24.681056354+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x02, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138A736258B8B, src_endpoint: 0x02, cluster: OnOff, dest_addr_mode: 0x03, dest_address: D052A8A7F1D60001, dest_endpoint: 0x01 > > >
2022-12-06T16:33:24.689510979+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-12-06T16:33:24.698240854+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x03, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138A736258B8B, src_endpoint: 0x03, cluster: OnOff, dest_addr_mode: 0x03, dest_address: D052A8A7F1D60001, dest_endpoint: 0x01 > > >
2022-12-06T16:33:24.707442188+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-12-06T16:33:24.716010396+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x04, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138A736258B8B, src_endpoint: 0x04, cluster: OnOff, dest_addr_mode: 0x03, dest_address: D052A8A7F1D60001, dest_endpoint: 0x01 > > >
2022-12-06T16:33:24.734158271+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x04, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-12-06T16:33:24.763297313+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:24.766443438+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-12-06T16:33:24.781480354+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853F, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: DeviceTemperatureConfiguration >, lqi: 0xFF, rssi: -54, body_length: 0x0003, < ZDOMessageBody || < ZDOHeader || seqno: 0x0F >, GenericBody: 00 00 > >
2022-12-06T16:33:24.795755396+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:24.801353771+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:25.150061979+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler device_lifecycle
2022-12-06T16:33:25.159172354+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received lifecycle event: infoChanged
2022-12-06T16:33:25.174871313+00:00 TRACE Zigbee Multi Switch and Child Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-12-06T16:33:25.184401938+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]= No
2022-12-06T16:33:25.187366646+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: switch3Child oldPreferenceValue: nil newParameterValue: >> No
2022-12-06T16:33:25.190217729+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]= No
2022-12-06T16:33:25.193368354+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: switch1Child oldPreferenceValue: nil newParameterValue: >> No
2022-12-06T16:33:25.196877604+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]= No
2022-12-06T16:33:25.200768604+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: switch2Child oldPreferenceValue: nil newParameterValue: >> No
2022-12-06T16:33:25.203788979+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]=
2022-12-06T16:33:25.207211813+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: version oldPreferenceValue: nil newParameterValue: >>
2022-12-06T16:33:25.210097604+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]= Single
2022-12-06T16:33:25.213338563+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: changeProfileFourSw oldPreferenceValue: nil newParameterValue: >> Single
2022-12-06T16:33:25.221428104+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]= 255
2022-12-06T16:33:25.225265729+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: restoreState oldPreferenceValue: nil newParameterValue: >> 255
2022-12-06T16:33:25.228171146+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Write restore state >>>
2022-12-06T16:33:25.232873938+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Write restore state >>>
2022-12-06T16:33:25.236021854+00:00 PRINT Zigbee Multi Switch and Child Mc <<<< Componente, end_point >>>> main 1
2022-12-06T16:33:25.240846771+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x4003, DataType: Enum8, data: 0xFF > > > >
2022-12-06T16:33:25.248397604+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x8002, DataType: Enum8, data: 0x02 > > > >
2022-12-06T16:33:25.261015813+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Write restore state >>>
2022-12-06T16:33:25.264241396+00:00 PRINT Zigbee Multi Switch and Child Mc <<< Write restore state >>>
2022-12-06T16:33:25.267821521+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]= No
2022-12-06T16:33:25.281058396+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: switch4Child oldPreferenceValue: nil newParameterValue: >> No
2022-12-06T16:33:25.284524479+00:00 PRINT Zigbee Multi Switch and Child Mc device.preferences[infoChanged]= No
2022-12-06T16:33:25.287638313+00:00 PRINT Zigbee Multi Switch and Child Mc << Preference changed name: signalMetricsVisibles oldPreferenceValue: nil newParameterValue: >> No
2022-12-06T16:33:25.290686938+00:00 PRINT Zigbee Multi Switch and Child Mc Device ID <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)>
2022-12-06T16:33:25.295601979+00:00 PRINT Zigbee Multi Switch and Child Mc Manufacturer >>> _TZ3000_ltt60asa Manufacturer_Len >>> 16
2022-12-06T16:33:25.298831229+00:00 PRINT Zigbee Multi Switch and Child Mc Model >>> TS0004 Model_len >>> 6
2022-12-06T16:33:25.302182938+00:00 PRINT Zigbee Multi Switch and Child Mc Memory >>>>>>> 1550.5537109375 Kbytes
2022-12-06T16:33:25.305818479+00:00 PRINT Zigbee Multi Switch and Child Mc <<<<< Firmware Version >>>>> Unknown
2022-12-06T16:33:25.308723896+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:25.312586063+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-12-06T16:33:25.316839979+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853F, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xFF, rssi: -54, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x21 >, < BindRequestResponse || status: 0x00 > > >
2022-12-06T16:33:25.326022896+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:25.395006313+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-12-06T16:33:25.399256854+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853F, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xFF, rssi: -54, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x22 >, < BindRequestResponse || status: 0x00 > > >
2022-12-06T16:33:25.409648771+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:25.915348771+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-12-06T16:33:25.920634521+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853F, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xFF, rssi: -54, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x25 >, < BindRequestResponse || status: 0x00 > > >
2022-12-06T16:33:25.936534104+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:26.036537438+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-12-06T16:33:26.041291229+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853F, src_endpoint: 0x03, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -54, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x30, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: SUCCESS, direction: 0x00, attr_id: 0x0000 > > > >
2022-12-06T16:33:26.050592896+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:26.053788396+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-12-06T16:33:26.058626396+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853F, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xFF, rssi: -83, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x26 >, < BindRequestResponse || status: 0x00 > > >
2022-12-06T16:33:26.070109229+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:26.254813563+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-12-06T16:33:26.259354271+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853F, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -61, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x32, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x4003 > > > >
2022-12-06T16:33:26.269800396+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:26.375090104+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-12-06T16:33:26.382658438+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853F, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xFF, rssi: -61, body_length: 0x0037, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x29, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0004, ZclStatus: SUCCESS, DataType: CharString, ManufacturerName: “_TZ3000_ltt60asa” >, < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Uint8, ZCLVersion: 0x03 >, < AttributeRecord || AttributeId: 0x0001, ZclStatus: SUCCESS, DataType: Uint8, ApplicationVersion: 0x46 >, < AttributeRecord || AttributeId: 0x0005, ZclStatus: SUCCESS, DataType: CharString, ModelIdentifier: “TS0004” >, < AttributeRecord || AttributeId: 0x0007, ZclStatus: SUCCESS, DataType: Enum8, PowerSource: PowerSource[SINGLE_PHASE_MAINS] >, < AttributeRecord || AttributeId: 0xFFFE, ZclStatus: SUCCESS, DataType: Enum8, Enum8: 0x00 > > > >
2022-12-06T16:33:26.391997854+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:26.614619854+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-12-06T16:33:26.619251854+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853F, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -73, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2A, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: SUCCESS, direction: 0x00, attr_id: 0x0000 > > > >
2022-12-06T16:33:26.629592479+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:26.715145521+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-12-06T16:33:26.720275521+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853F, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -49, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x2B, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: SUCCESS, direction: 0x00, attr_id: 0x0000 > > > >
2022-12-06T16:33:26.730589271+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:27.229125229+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-12-06T16:33:27.234607979+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853F, src_endpoint: 0x03, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -65, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x30, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: SUCCESS, direction: 0x00, attr_id: 0x0000 > > > >
2022-12-06T16:33:27.246392563+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:31.991418772+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
2022-12-06T16:33:40.292088398+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x853F, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xFF, rssi: -54, body_length: 0x000F, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xEC, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0001, DataType: Uint8, ApplicationVersion: 0x46 >, < AttributeRecord || AttributeId: 0xFFE2, DataType: Uint8, Uint8: 0x36 >, < AttributeRecord || AttributeId: 0xFFE4, DataType: Uint8, Uint8: 0x01 > > > >
2022-12-06T16:33:40.302698148+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:33:57.741111858+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-12-06T16:33:57.746299191+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“main”,“positional_args”:{}}
2022-12-06T16:33:57.749849066+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-12-06T16:33:57.753098150+00:00 PRINT Zigbee Multi Switch and Child Mc <<<< On command Handler >>>>
2022-12-06T16:33:57.787948025+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:34:47.501224156+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler zigbee
Also I get the following logs when I refresh
2022-12-06T16:46:21.131511155+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-12-06T16:46:21.175792322+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received command: {“args”:{},“capability”:“refresh”,“command”:“refresh”,“component”:“main”,“positional_args”:{}}
2022-12-06T16:46:21.192053864+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-12-06T16:46:21.201823780+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.232518822+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x04, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.249436364+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.263936530+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.274139947+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:46:21.281892280+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-12-06T16:46:21.291747322+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received command: {“args”:{},“capability”:“refresh”,“command”:“refresh”,“component”:“switch2”,“positional_args”:{}}
2022-12-06T16:46:21.297555197+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-12-06T16:46:21.316351280+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.328829072+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x04, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.348701364+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.387508405+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.412512447+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:46:21.422870155+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-12-06T16:46:21.469690405+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received command: {“args”:{},“capability”:“refresh”,“command”:“refresh”,“component”:“switch3”,“positional_args”:{}}
2022-12-06T16:46:21.484434530+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-12-06T16:46:21.498591280+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.531394364+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x04, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.546083572+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.562674114+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.572657489+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
2022-12-06T16:46:21.576200155+00:00 TRACE Zigbee Multi Switch and Child Mc Received event with handler capability
2022-12-06T16:46:21.582435072+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> received command: {“args”:{},“capability”:“refresh”,“command”:“refresh”,“component”:“switch4”,“positional_args”:{}}
2022-12-06T16:46:21.585854739+00:00 TRACE Zigbee Multi Switch and Child Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-12-06T16:46:21.590781364+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x03, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.598460239+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x04, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.615380072+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.631307405+00:00 INFO Zigbee Multi Switch and Child Mc <ZigbeeDevice: cdc2d38d-6a6a-4ab6-ac73-4ee4f89761e8 [0x853F] (TS0004 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x853F, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-12-06T16:46:21.637882155+00:00 DEBUG Zigbee Multi Switch and Child Mc TS0004 Switch device thread event handled
1 Like