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

amin300 · January 24, 2022, 5:21pm

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 · January 24, 2022, 6:17pm

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 · January 24, 2022, 7:05pm

@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 · January 24, 2022, 7:10pm

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.

Helder_Rodrigues · January 24, 2022, 10:16pm

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 · January 25, 2022, 12:29pm

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 Support

@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 · January 25, 2022, 1:01pm

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 · January 25, 2022, 3:24pm

@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 · January 25, 2022, 3:33pm

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 · January 25, 2022, 3:49pm

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

Mariano_Colmenarejo · January 25, 2022, 3:56pm

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

amin300 · January 25, 2022, 5:35pm

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 · January 25, 2022, 5:46pm

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

Mariano_Colmenarejo · January 25, 2022, 5:52pm

Here we have an answer, this device does not support attribute 0x0099 of cluster 0x0000.

I’m going to change to what I did yesterday, write 0xFFFF in the 0x4001 attribute, onTime so that it never turns off the switch with timer

make a change to this driver, you do not need to uninstall it.

Install this driver on your hub
prepare the logcat to capture the pairing log to the new driver

let’s see what we see

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Multi Switch Zemismart test   │
│ Version     │ 2022-01-25T17:51:16.900579           │
└─────────────┴──────────────────────────────────────┘

amin300 · January 25, 2022, 5:54pm

Thanks, I will as soon the new driver can be found in my hub
I will let you know

Mariano_Colmenarejo · January 25, 2022, 5:56pm

It’s on the channel now.
It is a different driver Zigbee Multi Switch Zemismart test, simply install it on your Hub from the app and follow the steps above

amin300 · January 25, 2022, 6:04pm

tested but still switched OFF after 2 mins

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 │
│ 2 │ 7d469ae2-4d8f-422e-9997-d77d67065b8d │ Zigbee Multi Switch Zemismart test │
└───┴──────────────────────────────────────┴────────────────────────────────────┘
? Select a driver. 2
2022-01-25T18:01:32.409020213+00:00 TRACE Zigbee Multi Switch Zemismart test Setup driver Zigbee_Multi_Switch with lifecycle handlers:
DeviceLifecycleDispatcher: Zigbee_Multi_Switch
default_handlers:
doConfigure:
init:
driverSwitched:
child_dispatchers:

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

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

2022-01-25T18:01:32.472644213+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler _resync
2022-01-25T18:01:32.477961546+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler environment_info
2022-01-25T18:01:32.491356213+00:00 TRACE Zigbee Multi Switch Zemismart test Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:01:32.502850213+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:01:32.508581213+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler _resync
2022-01-25T18:01:32.515067879+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler environment_info
2022-01-25T18:01:32.521200879+00:00 DEBUG Zigbee Multi Switch Zemismart test Z-Wave hub node ID environment changed.
2022-01-25T18:01:32.534629213+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:01:32.540209213+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler device_lifecycle
2022-01-25T18:01:32.546039879+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received lifecycle event: added
2022-01-25T18:01:32.554192879+00:00 TRACE Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received unhandled lifecycle event: added
2022-01-25T18:01:32.561089213+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:01:32.566665546+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler device_lifecycle
2022-01-25T18:01:32.572534546+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received lifecycle event: driverSwitched
2022-01-25T18:01:32.580788213+00:00 TRACE Zigbee Multi Switch Zemismart test Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:01:32.603215546+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x4001, DataType: Uint16, data: 0xFFFF > > > >
2022-01-25T18:01:32.639467879+00:00 INFO Zigbee Multi Switch Zemismart test <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-25T18:01:32.653327213+00:00 INFO Zigbee Multi Switch Zemismart test <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-25T18:01:32.683849546+00:00 INFO Zigbee Multi Switch Zemismart test <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-25T18:01:32.702470546+00:00 INFO Zigbee Multi Switch Zemismart test <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-25T18:01:32.715734879+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:01:37.532456213+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T18:01:37.543330880+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received command: {“command”:“on”,“capability”:“switch”,“component”:“main”,“args”:,“positional_args”:}
2022-01-25T18:01:37.549334880+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:01:37.562178213+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-01-25T18:01:37.585024880+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-01-25T18:01:37.612803213+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:01:39.980367214+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T18:01:39.996867214+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received command: {“command”:“on”,“capability”:“switch”,“component”:“switch2”,“args”:,“positional_args”:}
2022-01-25T18:01:40.003504880+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:01:40.010795880+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-01-25T18:01:40.034066214+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-01-25T18:01:40.060488547+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:01:45.518097214+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T18:01:45.535310548+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received command: {“command”:“off”,“capability”:“switch”,“component”:“main”,“args”:,“positional_args”:}
2022-01-25T18:01:45.541343881+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:01:45.554352214+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < Off || > > >
2022-01-25T18:01:45.578548548+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-01-25T18:01:45.599608214+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:01:47.661947548+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T18:01:47.678707548+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received command: {“command”:“on”,“capability”:“switch”,“component”:“main”,“args”:,“positional_args”:}
2022-01-25T18:01:47.685353548+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:01:47.692451881+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-01-25T18:01:47.714339548+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-01-25T18:01:47.739366881+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:01:55.348557215+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T18:01:55.365639549+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received command: {“command”:“off”,“capability”:“switch”,“component”:“main”,“args”:,“positional_args”:}
2022-01-25T18:01:55.372096882+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:01:55.380797549+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < Off || > > >
2022-01-25T18:01:55.402913882+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-01-25T18:01:55.436620882+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:01:57.385010549+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T18:01:57.411631882+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received command: {“command”:“on”,“capability”:“switch”,“component”:“main”,“args”:,“positional_args”:}
2022-01-25T18:01:57.417661216+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:01:57.439319882+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-01-25T18:01:57.462512549+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-01-25T18:01:57.501409882+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:01:58.865877549+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T18:01:58.880920883+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x2C, rssi: -89, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x0D, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-01-25T18:01:58.900964549+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:01:58.906370216+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T18:01:58.915436549+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T18:01:58.925429216+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-01-25T18:01:58.947624216+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 false
2022-01-25T18:01:58.955489883+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:01:58.962778549+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T18:01:58.973900883+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x44, rssi: -83, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x29, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >
2022-01-25T18:01:58.990378549+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:01:59.001947549+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-01-25T18:01:59.011363549+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-01-25T18:01:59.026559883+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:01:59.469395549+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T18:01:59.478432549+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x48, rssi: -82, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x2A, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-01-25T18:01:59.509614883+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:01:59.518739216+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-01-25T18:01:59.528055216+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-01-25T18:01:59.546564549+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:01:59.554565549+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T18:01:59.564942883+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x48, rssi: -82, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x0E, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-01-25T18:01:59.585111216+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:01:59.595467549+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T18:01:59.601550883+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T18:01:59.613270883+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-01-25T18:01:59.638180883+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 true
2022-01-25T18:01:59.644340549+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:02:02.452937883+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-01-25T18:02:05.862518883+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T18:02:05.871954550+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received command: {“command”:“off”,“capability”:“switch”,“component”:“switch2”,“args”:,“positional_args”:}
2022-01-25T18:02:05.898430883+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:02:05.941901550+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < Off || > > >
2022-01-25T18:02:06.009859217+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-01-25T18:02:06.148584883+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:02:06.235813550+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T18:02:06.302244883+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x5C, rssi: -77, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x2E, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >
2022-01-25T18:02:06.368476550+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:02:06.415773217+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-01-25T18:02:06.457111550+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-01-25T18:02:06.587461883+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:02:06.602179550+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T18:02:06.626257550+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x5C, rssi: -77, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x10, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false > > > >
2022-01-25T18:02:06.653050884+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:02:06.661217217+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T18:02:06.677115884+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T18:02:06.693992884+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-01-25T18:02:06.728907550+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 false
2022-01-25T18:02:06.747695550+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:02:07.638556884+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T18:02:07.655879217+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> received command: {“command”:“on”,“capability”:“switch”,“component”:“switch2”,“args”:,“positional_args”:}
2022-01-25T18:02:07.662405884+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:02:07.671272550+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-01-25T18:02:07.695200217+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-01-25T18:02:07.715268884+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:02:07.948685550+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T18:02:07.959131550+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x5C, rssi: -77, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x2F, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-01-25T18:02:07.977060884+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:02:07.982669217+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-01-25T18:02:07.990775884+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-01-25T18:02:08.008459550+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:02:08.014881550+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-01-25T18:02:08.023605884+00:00 INFO Zigbee Multi Switch Zemismart test <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: 0x5C, rssi: -77, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x11, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-01-25T18:02:08.038413550+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:02:08.044012884+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-01-25T18:02:08.050696217+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-01-25T18:02:08.059630550+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: f0bd6ee5-d72c-4bc3-8a99-3b19b9182474 [0xAB84] (TS0012 Switch)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-01-25T18:02:08.074716884+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 true
2022-01-25T18:02:08.080898550+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:02:32.452749220+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-01-25T18:03:02.450965557+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-01-25T18:03:32.456099560+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-01-25T18:04:02.460330897+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
listening for logs… \

amin300 · January 25, 2022, 6:17pm

Update…
Tested again by uninstalling device and driver from Hub and pairing device again using the new (Test) driver
It seems is working and switch dosent switch OFF for more than 10 mins so far
but i cant control switch from app any more, pressing ON/OFF dosent do anything

the last lines of logs below due to post limitation

2022-01-25T18:16:35.809198379+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:16:35.816549720+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x034D, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-01-25T18:16:35.839245729+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“component_id”:“switch2”,“capability_id”:“switch”,“attribute_id”:“switch”}
2022-01-25T18:16:35.867738635+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:16:39.469919085+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T18:16:39.485935085+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> received command: {“args”:,“capability”:“switch”,“positional_args”:,“command”:“off”,“component”:“main”}
2022-01-25T18:16:39.492414418+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:16:39.500989085+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x034D, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < Off || > > >
2022-01-25T18:16:39.528014085+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> emitting event: {“state”:{“value”:“off”},“component_id”:“main”,“capability_id”:“switch”,“attribute_id”:“switch”}
2022-01-25T18:16:39.548014752+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:16:40.084906085+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T18:16:40.102290752+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> received command: {“args”:,“capability”:“switch”,“positional_args”:,“command”:“off”,“component”:“switch2”}
2022-01-25T18:16:40.108722752+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:16:40.117146752+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x034D, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < Off || > > >
2022-01-25T18:16:40.130703752+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> emitting event: {“state”:{“value”:“off”},“component_id”:“switch2”,“capability_id”:“switch”,“attribute_id”:“switch”}
2022-01-25T18:16:40.164912752+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:16:41.326594086+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T18:16:41.346854419+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> received command: {“args”:,“capability”:“switch”,“positional_args”:,“command”:“on”,“component”:“main”}
2022-01-25T18:16:41.354290752+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:16:41.364757086+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x034D, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-01-25T18:16:41.380206752+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“component_id”:“main”,“capability_id”:“switch”,“attribute_id”:“switch”}
2022-01-25T18:16:41.415061419+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-01-25T18:16:41.838996086+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-01-25T18:16:41.855716419+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> received command: {“args”:,“capability”:“switch”,“positional_args”:,“command”:“on”,“component”:“switch2”}
2022-01-25T18:16:41.862415419+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-01-25T18:16:41.871250753+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x034D, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-01-25T18:16:41.893160086+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 07ec17e4-eb9f-412e-b8d8-859f88221e13 [0x034D] (TS0012 Switch)> emitting event: {“state”:{“value”:“on”},“component_id”:“switch2”,“capability_id”:“switch”,“attribute_id”:“switch”}
2022-01-25T18:16:41.921231753+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
listening for logs… \

Mariano_Colmenarejo · January 25, 2022, 6:22pm

I see that the write message of attribute 0x4001 of cluster 0x0006 has been sent, but I do not see the response, neither sucess nor not supported.

It may have been spelled right.

Try to reboot the hub from the IDE.
To see the logs you have to reconfigure them in CLI, if you want to see them when rebooting the hub

Mariano_Colmenarejo · January 25, 2022, 6:30pm

@amin300,
I see in the logs that while the device is being installed in the driver you perform several on-off-ons in a row several times.

This is not a good thing to do during installation.

If you look at the logs, the installation has a process that is slower than it seems in the app.

In the app it seems that everything is done and the driver is performing configuration tasks and waiting for responses from the device.

Be more patient when installing devices with edge drivers, it may interrupt the process or make it incorrect

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

Customers

Developers

Download the SmartThings App