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

[Markusjonsson (Markus Jönsson)]

Okey thanks anyway

[amin300 (Amin)]

Thanks @JDRoberts for your reply.

This issue is solved in DTH as explened in below post link:

UK Light switches – My experiences (2020)

Hello everyone, I also bought Yagusmart switches and was facing the 2 minute issue. Then I went through the handler for multi-swith and found two things - On line 238: it is checked if the manufacturer is Orvibo. private Boolean isOrvibo() { device.getDataValue("manufacturer") == "Orvibo" } And on line 217, in configure method, it is checked every 2 minutes, if the manufacturer is Orvibo, then its okay, or do a Refresh. So, anyone facing the issue, can simply return true from isOrvibo method to get rid of it. I am pasting my handler here for other’s usage.

Do you think is something useful to use and modify the driver for this device?

Thanks
Amin

[amin300 (Amin)]

This is the DTH which I am using and in line 271 I have changed to my device

SmartThingsCommunity/SmartThingsPublic/blob/master/devicetypes/smartthings/zigbee-multi-switch.src/zigbee-multi-switch.groovy

[Mariano_Colmenarejo]

@amin300

This is the DTH which I am using and in line 271 I have changed to my device

This is done by DTH:

	if (isOrvibo()) {
		//the orvibo switch will send out device anounce message at ervery 2 mins as heart beat,setting 0x0099 to 1 will disable it.
		def cmds = zigbee.writeAttribute(zigbee.BASIC_CLUSTER, 0x0099, 0x20, 0x01, [mfgCode: 0x0000])
		cmds += refresh()
		return cmds

This done by driver published yesterday, I publish now again:

local function do_configure(self,device)
  if device:get_manufacturer() == "_TZ3000_fvh3pjaz" then
    --- Configure basic cluster, attributte 0x0099 to 1
    local data_value = {value = 0x01, ID = 0x20}
    local cluster_id = {value = 0x0000}
    local attr_id = 0x0099
    write_attribute_function(device, cluster_id, attr_id, data_value)
  end
   device:configure()
end 

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Multi Switch Zemismart Mc     │
│ Version     │ 2022-01-23T19:15:03.670094           │
└─────────────┴──────────────────────────────────────┘

For it to works, you have to uninstall the device and re-pair it with this new driver to configure it correctly.

If you install it and send me the pairing CLI log, to see if the writing of the attribute is accepted, I will be able to analyze something, if it just tells me it doesn’t work, I can’t do anything.

[amin300 (Amin)]

Thanks @Mariano_Colmenarejo
I have Uninstalled the device and re-paired it again but it didnt pick the new driver
2022-01-23T19:15:03.670094
Still picking the version:
2022-01-22T17:23:29.327658
I tried 3 times
Are you sure it is puplished or I am doing something wrong?

[amin300 (Amin)]

@Mariano_Colmenarejo

send me the pairing CLI log

BTW @Mariano_Colmenarejo , how I can send you the pairing CLI Log?

[Mariano_Colmenarejo]

@amin300

Are you sure it is puplished or I am doing something wrong?

The automatic driver update can take up to 12 hours.

So you only have that device installed with the driver:

• Uninstall the device
• Remove the driver from your Hub
• Enter the channel and reinstall the driver, that will be the latest version. You can check it by clicking on the driver and see the date.
• Re-pair the device

[amin300 (Amin)]

Hi again @Mariano_Colmenarejo

I still can’t see the latest driver of 2022-01-23T19:15:03.670094
Still picking the version:
2022-01-22T17:23:29.327658

Even when device is paired and i go to select another driver, still can’t see latest one

Any other suggestion please?

[amin300 (Amin)]

Now i can see it, i had to remove old driver from hub and install again
Tested and issue still there

I tried to capture logs by going to IDE logs tab but i can’t see my device although it is installed!!

Can you please guide me to capture CLI logs please?

[joinwind]

@Mariano_Colmenarejo can you try to modify the driver : zigbee-window-treatment from samsung and add this info in fingerprint :

• application: 01
• endpointId: 0A
• manufacturer: Vimar
• model: Window_Cov_v1.0
• zigbeeNodeType: ROUTER

Thanks if you can publish !

[Mariano_Colmenarejo]

@amin300

Can you please guide me to capture CLI logs please?

It seems a bit complicated at first, but most of us get it done.

• You have to download from this link release 34 of the compressed file smartthings-win.zip, if you use windows or the one necessary for your operating system

• In that link you also have installation help, use and all the commands you can use

• Unzip it and move the smartthings.exe file to a folder on your computer from where it will be used. for example to a new folder in documents/CLI

• You have to open the windows powerShell terminal window and you have to go to the directory (folder) where the smarttings.exe file is.

• Use the DOS commands “cd…” to move down directory and “cd directory name” to move to that directory. This is an example of my folder for CLI

• the first time you type a CLI command it will take you to the smartthing page to authorize your account.
• type .\smartthings edge:drivers:logcat
• enter the IP of your HUB, you can see it in IDE
• It will show you the list of drivers installed on your HUB
• type the number corresponding to the driver you want to see
• It will show you the activity of the device connected to that driver.

To capture the pairing log:

• Uninstall the device with the app
• Open the terminal window with the CLI ready to see the log of the driver to which the device is going to be paired
• In the app, add new device and search nearby
• When paired in the app you will see information appear in the CLI window
• When it finishes pairing, select the data in the window, copy and paste it in the post
  Similar to this example:

? Select a driver. 23
2022-01-24T17:54:45.422836623+00:00 TRACE Zigbee Switch Power Mc Setup driver Zigbee_Switch with lifecycle handlers:
DeviceLifecycleDispatcher: Zigbee_Switch
default_handlers:
init:
infoChanged:
doConfigure:
driverSwitched:
removed:
child_dispatchers:

2022-01-24T17:54:45.433937838+00:00 TRACE Zigbee Switch Power Mc Setup driver Zigbee_Switch with Capability handlers:
CapabilityCommandDispatcher: Zigbee_Switch
default_handlers:
switchLevel:
setLevel
energyMeter:
resetEnergyMeter
switch:
on
off
legendabsolute60149.randomOnOff1:
setRandomOnOff
refresh:
refresh
child_dispatchers:

2022-01-24T17:54:45.443345539+00:00 TRACE Zigbee Switch Power Mc Setup driver Zigbee_Switch with Zigbee handlers:
ZigbeeMessageDispatcher: Zigbee_Switch
default_handlers:
attr:
ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ACPowerMultiplier
ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ACPowerDivisor
ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ActivePower
ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: InstantaneousDemand
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: Multiplier
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: Divisor
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: CurrentSummationDelivered
ZclClusterAttributeValueHandler: cluster: Level, attribute: CurrentLevel
global:
ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
cluster:
zdo:
child_dispatchers:

2022-01-24T17:54:45.511152092+00:00 TRACE Zigbee Switch Power Mc Received event with handler _resync
2022-01-24T17:54:45.516996346+00:00 TRACE Zigbee Switch Power Mc Received event with handler environment_info
2022-01-24T17:54:45.532995675+00:00 TRACE Zigbee Switch Power Mc Found DeviceLifecycleDispatcher handler in Zigbee_Switch
2022-01-24T17:54:45.538784902+00:00 PRINT Zigbee Switch Power Mc <<<< random_state >>>> Inactive
2022-01-24T17:54:45.545711363+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> emitting event: {“attribute_id”:“randomOnOff”,“capability_id”:“legendabsolute60149.randomOnOff1”,“component_id”:“main”,“state”:{“value”:“Inactive”}}
2022-01-24T17:54:45.565924465+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> emitting event: {“attribute_id”:“randomNext”,“capability_id”:“legendabsolute60149.randomNextStep”,“component_id”:“main”,“state”:{“value”:“Inactive”}}
2022-01-24T17:54:45.588026844+00:00 PRINT Zigbee Switch Power Mc device_running[id]= <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)>
2022-01-24T17:54:45.594267629+00:00 PRINT Zigbee Switch Power Mc device_running, random_Step= <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> 1
2022-01-24T17:54:45.602485736+00:00 PRINT Zigbee Switch Power Mc device_running, random_totalStep= <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> 2
2022-01-24T17:54:45.608596790+00:00 PRINT Zigbee Switch Power Mc device_running, random_timer= <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> 18
2022-01-24T17:54:45.614712513+00:00 PRINT Zigbee Switch Power Mc random_state >>>>> Inactive
2022-01-24T17:54:45.621036007+00:00 DEBUG Zigbee Switch Power Mc Caldera device thread event handled
2022-01-24T17:54:45.628412360+00:00 TRACE Zigbee Switch Power Mc Received event with handler _resync
2022-01-24T17:54:45.634823897+00:00 TRACE Zigbee Switch Power Mc Received event with handler environment_info
2022-01-24T17:54:45.640548091+00:00 DEBUG Zigbee Switch Power Mc Z-Wave hub node ID environment changed.
2022-01-24T17:54:45.655721674+00:00 TRACE Zigbee Switch Power Mc Received event with handler environment_info
2022-01-24T17:54:45.664314302+00:00 TRACE Zigbee Switch Power Mc Received event with handler environment_info
2022-01-24T17:54:45.672036494+00:00 TRACE Zigbee Switch Power Mc Received event with handler device_lifecycle
2022-01-24T17:54:45.677818717+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> received lifecycle event: added
2022-01-24T17:54:45.686320633+00:00 TRACE Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> received unhandled lifecycle event: added
2022-01-24T17:54:45.691853731+00:00 DEBUG Zigbee Switch Power Mc Caldera device thread event handled
2022-01-24T17:54:45.697675641+00:00 TRACE Zigbee Switch Power Mc Received event with handler device_lifecycle
2022-01-24T17:54:45.703458197+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> received lifecycle event: driverSwitched
2022-01-24T17:54:45.712275270+00:00 TRACE Zigbee Switch Power Mc Found DeviceLifecycleDispatcher handler in Zigbee_Switch
2022-01-24T17:54:45.722751839+00:00 DEBUG Zigbee Switch Power Mc Caldera device thread event handled
2022-01-24T17:54:45.730693808+00:00 DEBUG Zigbee Switch Power Mc Caldera device thread event handled
2022-01-24T17:54:50.750604509+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xCCC5, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody ||
< ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x050B > > >
2022-01-24T17:54:50.773669036+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 92d80935-27ff-4d7f-ba4d-70ac7c0db9e7 [0xCCC5] (Caldera)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xCCC5, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >

Don’t be in a hurry, take it patiently, it was hard for all of us the first time and if you have any problem, say so.

smartthings-cli/packages/cli at master · SmartThingsCommunity/smartthings-cli - smartthings edge:channels:update [ID]

[Helder_Rodrigues]

Hello @Mariano_Colmenarejo

can you create for this device?
Data * zigbeeNodeType: ROUTER

• firmwareManufacturerCode: 4417
• firmwareFullVersion: 00000043
• application: 43
• endpointId: 01
• firmwareImageType: 54179
• manufacturer: _TZ3000_tqlv4ug4
• model: TS0001
  Raw Description 01 0104 0100 01 07 0003 0004 0005 0006 E000 E001 0000 02 0019 000A

[Mariano_Colmenarejo]

@joinwind

can you try to modify the driver : zigbee-window-treatment from samsung and add this info in fingerprint :

• application: 01
• endpointId: 0A
• manufacturer: Vimar
• model: Window_Cov_v1.0
• zigbeeNodeType: ROUTER

Hello @joinwind,

I am not going to modify the official beta drivers to include fingerprints in them, since it would be impossible to serve it correctly.
There are more and more drivers and it would be impossible

I will continue to maintain the drivers that I have created or modified with different functions to official drivers.

I can help you to modify them, it is not very difficult, 3 months ago I did not know anything about CLI or lua.

In this link I explained it to another user who wants to do the same

Setting Up Edge Development Environment

@Jake_Mohl, I don’t know exactly where you are, but I’ll try to explain how I did it How to edit the LUA and yml code of the Edge drivers I’m going to explain the steps I did, that I’m not a developer and I started from scratch, without knowing the CLI or Lua. First I read the Edge Drivers tutorials and CLI in the community Download a multilanguage code editor, I opted for Visual Studio since they recommended it in some thread of the tutorials. Visual Studio: IDE y Editor de código para desarrolladores de software y Teams Once installed, the Windows version in my case, this window appears [Visual studio] Click on extensions to install the extensions to work with the LUA language, with syntax fixes and programming errors. With these that you see are enough for me [visua…

[Mariano_Colmenarejo]

@Helder_Rodrigues

can you create for this device?
Data * zigbeeNodeType: ROUTER

• firmwareManufacturerCode: 4417
• firmwareFullVersion: 00000043
• application: 43
• endpointId: 01
• firmwareImageType: 54179
• manufacturer: _TZ3000_tqlv4ug4
• model: TS0001
  Raw Description 01 0104 0100 01 07 0003 0004 0005 0006 E000 E001 0000 02 0019 000A

Added to this driver version

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Switch Mc                     │
│ Version     │ 2022-01-25T12:57:40.013495           │
└─────────────┴──────────────────────────────────────┘

  - id: "_TZ3000_tqlv4ug4/Switch"
    deviceLabel: TUYATEC Switch
    manufacturer: _TZ3000_tqlv4ug4
    model: TS0001
    deviceProfileName: single-switch

[damohabir (Daniel)]

@Mariano_Colmenarejo, thanks for the instructions for CLI. I am running Powershell as Admin, but all I get is a string of dots, Then it returns to the prompt. What am I doing wrong?

PS C:\Windows> cd …
PS C:> cd users
PS C:\users> cd .\damoh
PS C:\users\damoh> cd .\Downloads
PS C:\users\damoh\Downloads> cd .\SmartThings
PS C:\users\damoh\Downloads\SmartThings> ./smartthings edge:drivers:logcat
? Enter hub IP address with optionally appended port number: 192.168.1.xxx
…
PS C:\users\damoh\Downloads\SmartThings>

[Mariano_Colmenarejo]

@damohabir

am running Powershell as Admin, but all I get is a string of dots, Then it returns to the prompt. What am I doing wrong?

If this is your first time using the cli, a Smartthings web page will open for you to identify yourself and authorize your account

open the browser to see it

[damohabir (Daniel)]

Thank you. It opened a tiny browser window and I did not see it at first. It works now.

[Mariano_Colmenarejo]

@damohabir

It opened a tiny browser window and I did not see it at first. It works now.

Remember this, every x time you will be asked for authorization again

[amin300 (Amin)]

Thank you so much @Mariano_Colmenarejo

Please find below my logs which includes auto switch OFF after 2 mins at the end of logs:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

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

PS C:\WINDOWS\system32> cd c:
PS C:> cd users
PS C:\users> cd aminhsm
PS C:\users\aminhsm> cd documents
PS C:\users\aminhsm\documents> cd CLI
PS C:\users\aminhsm\documents\CLI> .\smartthings edge:drivers:logcat
? Enter hub IP address with optionally appended port number: 192.168.1.58
┌───┬──────────────────────────────────────┬──────────────────────────────────┐
│ # │ Driver Id │ Name │
├───┼──────────────────────────────────────┼──────────────────────────────────┤
│ 1 │ 950d769e-5e53-4cb9-aad7-b7b6023f20d2 │ Zigbee Multi Switch Zemismart Mc │
└───┴──────────────────────────────────────┴──────────────────────────────────┘
? Select a driver. 1
2022-01-25T17:32:06.625339070+00:00 TRACE Zigbee Multi Switch Zemismart Mc Setup driver Zigbee_Multi_Switch with lifecycle handlers:
DeviceLifecycleDispatcher: Zigbee_Multi_Switch
default_handlers:
driverSwitched:
doConfigure:
init:
child_dispatchers:

2022-01-25T17:32:06.633354403+00:00 TRACE Zigbee Multi Switch Zemismart Mc Setup driver Zigbee_Multi_Switch with Capability handlers:
CapabilityCommandDispatcher: Zigbee_Multi_Switch
default_handlers:
switch:
on
off
refresh:
refresh
child_dispatchers:

2022-01-25T17:32:06.643440403+00:00 TRACE Zigbee Multi Switch Zemismart Mc Setup driver Zigbee_Multi_Switch with Zigbee handlers:
ZigbeeMessageDispatcher: Zigbee_Multi_Switch
default_handlers:
attr:
ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
global:
ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
cluster:
zdo:
child_dispatchers:

2022-01-25T17:32:06.705503070+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler _resync
2022-01-25T17:32:06.710939070+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler environment_info
2022-01-25T17:32:06.726440737+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-01-25T17:32:06.738352403+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:06.744719403+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler _resync
2022-01-25T17:32:06.750051737+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler environment_info
2022-01-25T17:32:06.755913737+00:00 DEBUG Zigbee Multi Switch Zemismart Mc Z-Wave hub node ID environment changed.
2022-01-25T17:32:06.769906403+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:06.776845070+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler device_lifecycle
2022-01-25T17:32:06.783030070+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received lifecycle event: added
2022-01-25T17:32:06.790645070+00:00 TRACE Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received unhandled lifecycle event: added
2022-01-25T17:32:06.796444070+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:06.802714070+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler device_lifecycle
2022-01-25T17:32:06.808201404+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received lifecycle event: doConfigure
2022-01-25T17:32:06.819022737+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-01-25T17:32:06.854355404+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAB84, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x0099, DataType: Uint8, data: 0x01 > > > >
2022-01-25T17:32:06.890119070+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAB84, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 60A423FFFE651394, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D97000200C8A4, dest_endpoint: 0x01 > > >
2022-01-25T17:32:06.905658737+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAB84, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-01-25T17:32:07.260234070+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAB84, dest_endpoint: 0x02, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 60A423FFFE651394, src_endpoint: 0x02, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D97000200C8A4, dest_endpoint: 0x01 > > >
2022-01-25T17:32:07.274843070+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAB84, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-01-25T17:32:07.296123404+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:07.313990404+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:07.319721737+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-01-25T17:32:07.351052404+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAB84, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0x54, rssi: -79, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x79, ZCLCommandId: 0x04 >, < WriteAttributeReponse || < WriteAttributeResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, AttributeId: 0x0099 > > > >
2022-01-25T17:32:07.367991404+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:07.374208404+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-01-25T17:32:07.385099070+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAB84, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0x58, rssi: -78, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x59 >, < BindRequestResponse || status: 0x00 > > >
2022-01-25T17:32:07.400121404+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:07.405863404+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-01-25T17:32:07.419904070+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAB84, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x58, rssi: -78, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7A, ZCLCommandId: 0x07 >, < ConfigureReportingReponse || ZclStatus: SUCCESS > > >
2022-01-25T17:32:07.437673404+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:07.597662737+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-01-25T17:32:07.606017404+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAB84, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0x58, rssi: -78, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x5B >, < BindRequestResponse || status: 0x00 > > >
2022-01-25T17:32:07.621444071+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:07.627392737+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-01-25T17:32:07.637729404+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAB84, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x58, rssi: -78, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7B, ZCLCommandId: 0x07 >, < ConfigureReportingReponse || ZclStatus: SUCCESS > > >
2022-01-25T17:32:07.655433737+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:07.889015737+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler device_lifecycle
2022-01-25T17:32:07.906143071+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received lifecycle event: infoChanged
2022-01-25T17:32:07.914077404+00:00 TRACE Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received unhandled lifecycle event: infoChanged
2022-01-25T17:32:07.919451071+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:18.888882096+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-01-25T17:32:18.955298955+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAB84, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x54, rssi: -79, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0C, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-01-25T17:32:19.032179710+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T17:32:19.041347958+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T17:32:19.069635095+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-01-25T17:32:19.112559213+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“state”:{“value”:“on”},“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T17:32:19.227463970+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 1 true
2022-01-25T17:32:19.259847820+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:19.419142428+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-01-25T17:32:19.471298159+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAB84, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x54, rssi: -79, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0D, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-01-25T17:32:19.501150745+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T17:32:19.511311156+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T17:32:19.527125059+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-01-25T17:32:19.548676829+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“state”:{“value”:“on”},“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T17:32:19.594362327+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 2 true
2022-01-25T17:32:19.609545582+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:22.017929173+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-01-25T17:32:22.027866472+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAB84, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x54, rssi: -79, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0E, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-01-25T17:32:22.044558814+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T17:32:22.051099083+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T17:32:22.057106752+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-01-25T17:32:22.066135931+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“state”:{“value”:“off”},“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T17:32:22.084506778+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 1 false
2022-01-25T17:32:22.092430071+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:22.582739770+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-01-25T17:32:22.593868999+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAB84, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x48, rssi: -82, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0F, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-01-25T17:32:22.611338729+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T17:32:22.616561339+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T17:32:22.622794121+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-01-25T17:32:22.630754432+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“state”:{“value”:“off”},“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T17:32:22.648492630+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 2 false
2022-01-25T17:32:22.656356227+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:25.498278141+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-01-25T17:32:25.509483808+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAB84, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x50, rssi: -80, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x10, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-01-25T17:32:25.525549141+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T17:32:25.530849141+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T17:32:25.536997808+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-01-25T17:32:25.546234808+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“state”:{“value”:“on”},“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T17:32:25.569032808+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 1 true
2022-01-25T17:32:25.576309808+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:25.996157141+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-01-25T17:32:26.005383141+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAB84, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x4C, rssi: -81, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x11, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-01-25T17:32:26.022827475+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T17:32:26.028049475+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T17:32:26.033993141+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-01-25T17:32:26.042154475+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“state”:{“value”:“on”},“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T17:32:26.064572808+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 2 true
2022-01-25T17:32:26.071760808+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:32:36.665203813+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee health poll
2022-01-25T17:33:06.667487494+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee health poll
2022-01-25T17:33:36.671213842+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee health poll
2022-01-25T17:33:43.573376845+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-01-25T17:33:43.593759511+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAB84, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x30, rssi: -88, body_length: 0x0019, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x00, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 >, < AttributeRecord || AttributeId: 0x8001, DataType: Enum8, Enum8: 0x01 >, < AttributeRecord || AttributeId: 0x8002, DataType: Enum8, Enum8: 0x00 > > > >
2022-01-25T17:33:43.610263178+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T17:33:43.615882845+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T17:33:43.623578845+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-01-25T17:33:43.630621845+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“state”:{“value”:“off”},“component_id”:“main”,“attribute_id”:“switch”}
2022-01-25T17:33:43.649027845+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 1 false
2022-01-25T17:33:43.657644845+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-01-25T17:33:43.782721845+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-01-25T17:33:43.826674178+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xAB84, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x34, rssi: -87, body_length: 0x0011, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x01, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 > > > >
2022-01-25T17:33:43.931013845+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T17:33:43.958617845+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T17:33:43.988460178+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-01-25T17:33:44.048567845+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“state”:{“value”:“off”},“component_id”:“switch2”,“attribute_id”:“switch”}
2022-01-25T17:33:44.158361178+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 2 false
2022-01-25T17:33:44.190615845+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
listening for logs… /

[amin300 (Amin)]

Just to add…
after pairing the device, device Icon in mobile app showing “checking status”

and once i click the device icon, it opens and showing the “cloud image” for switch 1 and swithch 2 (no connected) and i cant control the switch from app

only Once i press the Physical swith from the wall switch (not from app), then the device icon shows it is connected and i can control then

then the device can be controlled normally but switch OFF after 2 mins