[Beta] Zigbee Edge Driver compatible with Lidl, Ecosmart, Osram, SmartThings & Others

Hey Mariano, greetings!

Could you please include this 3 gang multi switch zemismart?

Data
application: 43
endpointId: 01
manufacturer: _TYZB01_stv9a4gy
model: TS0013
onOff: catchall
zigbeeNodeType: SLEEPY_END_DEVICE

Raw Description 01 0104 0100 00 03 0000 0003 0006 01 0019

Thanks my friend! Have a great day.

Great dude!
Thanx

1 Like

Thanks, same for you

Added to this driver date version

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Multi Switch Mc               │
│ Version     │ 2022-02-03T16:31:37.739989           │
└─────────────┴──────────────────────────────────────┘
  - id: "TS0013/_TYZB01_stv9a4gy"
    deviceLabel: TS0013 Switch
    manufacturer: _TYZB01_stv9a4gy
    model: TS0013
    deviceProfileName: three-switch
1 Like

Can you please add driver for SmartThings Multipurpose sensor (2015)?
Thanks in advance.

Added to this version of the driver
I don’t know if the information of the 3 axes works well
I guess smartthings will have to edge this stock DTH that affects several smartthings devices and centralite

  - id: "CentraLite/3321-S"
    deviceLabel: Multipurpose Sensor
    manufacturer: CentraLite
    model: 3321-S
    deviceProfileName: st-multipurpose
┌─────────────┬──────────────────────────────────────┐
│ Name        │ SmartThings Multipurpose Sensor Mc   │
│ Version     │ 2022-02-04T18:24:38.471734           │
└─────────────┴──────────────────────────────────────┘
1 Like

A recent zigbee switch with power meter.

  • application: 45
  • endpointId: 01
  • manufacturer: _TZ3000_u5u4cakc
  • model: TS011F
  • zigbeeNodeType: ROUTER
    Raw Description 01 0104 010A 01 09 0000 0003 0004 0005 0006 0702 0B04 E000 E001 02 0019 000A

I am especially interested in utilizing the power meter function with your driver.
Thank you for your great work!

Added to this driver version
It is possible that there is an error in the power reading since it seems there is an error in the edge libraries of hub firmware 041.08, which will be corrected

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Switch Power Mc               │
│ Version     │ 2022-02-04T20:39:31.816834           │
└─────────────┴──────────────────────────────────────┘
  - id: "_TZ3000_u5u4cakc/TS011F"
    deviceLabel: TS011F Plug
    manufacturer: _TZ3000_u5u4cakc
    model: TS011F
    deviceProfileName: switch-power-energy-plug

Looks like it is a problem with the module, Ive added another 2 of these modules since with no problems.
Thanks for all of your help

1 Like

Hi
Do you know if this edge driver will work with this Lidl model led module.
If so can this one be added please.

  • manufacturer: _TZ3000_riwp3k79
  • model: TS0505A
    Raw Description 01 0104 010D 01 [08 0000 0003 0004](tel:08 0000 0003 0004) [0005 0006 0008 0300](tel:0005 0006 0008 0300) [1000 02 0019](tel:1000 02 0019) 000A

Added to this driver version

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Light Multifunction Mc        │
│ Version     │ 2022-02-05T11:14:15.400601           │
└─────────────┴──────────────────────────────────────┘
  - id: "_TZ3000_riwp3k79/TS0505A"
    deviceLabel: TS0505A RGBW
    manufacturer: _TZ3000_riwp3k79
    model: TS0505A
    deviceProfileName: rgbw-level-colortemp-2700-6500
1 Like

This error is indeed the case currently. I have 041.08 Hub firmware and power meter displays 1000x values. Otherwise perfect.

Hi
I changed the device to this one, The on and off work ok
The colour temperature works ok
The dimmer works ok
For some strange reason the colour wont operate on this one.
It stays white all the while so no RGB working on this at the min
Any ideas on this
This is the what it was using on groovy
Thanks in advance

I’m in the same situation as Amin300. Would be great to get the edge driver working without the timeout. Here are my logs with the latest test version 2022-01-25. Everything seem to be working apart from the timeout.
There is another referense to the IsOrvibo in the working (when modified) DTH for “refresh” if that is of some clue.

IsOrvibo reference

def refresh() {
if (isOrvibo()) {
zigbee.readAttribute(zigbee.ONOFF_CLUSTER, 0x0000, [destEndpoint: 0xFF])
} else {
def cmds = zigbee.onOffRefresh()
def x = getChildCount()
for (i in 2…x) {
cmds += zigbee.readAttribute(zigbee.ONOFF_CLUSTER, 0x0000, [destEndpoint: i])
}
return cmds
}
}

Logs

`Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell Install PowerShell on Windows, Linux, and macOS - PowerShell | Microsoft Docs

PS C:\Users\tomas> cd C:\Temp\ST
PS C:\Temp\ST> .\smartthings.exe edge:drivers:logcat
? Enter hub IP address with optionally appended port numbe5 can’t be established. Certificate fingerprint is75
? Are you sure you want to continue connecting? Yes
» Warning: Permanently added to the list of known hubs.
┌───┬──────────────────────────────────────┬───────────────────────────────────┐
│ # │ Driver Id │ Name │
├───┼──────────────────────────────────────┼───────────────────────────────────┤
│ 1 │ 8a5a5586-aa12-4cbb-b7ed-fa3ad735df0d │ Zigbee Aqara Water Leak Sensor Mc │
└───┴──────────────────────────────────────┴───────────────────────────────────┘
? Select a driver. (all)
PS C:\Temp\ST> .\smartthings.exe edge:drivers:logcat
? Enter hub IP address with optionally appended port number: 10.10.10.50
┌───┬──────────────────────────────────────┬────────────────────────────────────┐
│ # │ Driver Id │ Name │
├───┼──────────────────────────────────────┼────────────────────────────────────┤
│ 1 │ 8a5a5586-aa12-4cbb-b7ed-fa3ad735df0d │ Zigbee Aqara Water Leak Sensor Mc │
│ 2 │ 7d469ae2-4d8f-422e-9997-d77d67065b8d │ Zigbee Multi Switch Zemismart test │
└───┴──────────────────────────────────────┴────────────────────────────────────┘
? Select a driver. 2
2022-02-05T15:09:01.864051910+00:00 TRACE Zigbee Multi Switch Zemismart test Setup driver Zigbee_Multi_Switch with lifecycle handlers:
DeviceLifecycleDispatcher: Zigbee_Multi_Switch
default_handlers:
driverSwitched:
doConfigure:
init:
child_dispatchers:

2022-02-05T15:09:01.868147278+00:00 TRACE Zigbee Multi Switch Zemismart test Setup driver Zigbee_Multi_Switch with Capability handlers:
CapabilityCommandDispatcher: Zigbee_Multi_Switch
default_handlers:
switch:
off
on
refresh:
refresh
child_dispatchers:

2022-02-05T15:09:01.873474446+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-02-05T15:09:01.905314810+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler _resync
2022-02-05T15:09:01.908539988+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler environment_info
2022-02-05T15:09:01.916546650+00:00 TRACE Zigbee Multi Switch Zemismart test Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:09:01.922704819+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:01.926074133+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler _resync
2022-02-05T15:09:01.929243631+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler environment_info
2022-02-05T15:09:01.932255458+00:00 DEBUG Zigbee Multi Switch Zemismart test Z-Wave hub node ID environment changed.
2022-02-05T15:09:01.939866067+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:01.943380518+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler device_lifecycle
2022-02-05T15:09:01.946877143+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received lifecycle event: added
2022-02-05T15:09:01.951306261+00:00 TRACE Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received unhandled lifecycle event: added
2022-02-05T15:09:01.954384263+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:01.957828707+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler device_lifecycle
2022-02-05T15:09:01.961064671+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received lifecycle event: doConfigure
2022-02-05T15:09:01.966644172+00:00 TRACE Zigbee Multi Switch Zemismart test Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:09:01.975849317+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 2C1165FFFE3AD443, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x03, dest_address: D052A835AEAD0001, dest_endpoint: 0x01 > > >
2022-02-05T15:09:01.997358598+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, 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-02-05T15:09:02.006195844+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, dest_endpoint: 0x02, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 2C1165FFFE3AD443, src_endpoint: 0x02, cluster: OnOff, dest_addr_mode: 0x03, dest_address: D052A835AEAD0001, dest_endpoint: 0x01 > > >
2022-02-05T15:09:02.013995401+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, 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-02-05T15:09:02.023167604+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, 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-02-05T15:09:02.031699170+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x4002, DataType: Uint16, data: 0xFFFF > > > >
2022-02-05T15:09:02.045892736+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:02.055309525+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:02.263790774+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:02.269488257+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xFF, rssi: -53, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x38 >, < BindRequestResponse || status: 0x00 > > >
2022-02-05T15:09:02.278705230+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:02.335986283+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler device_lifecycle
2022-02-05T15:09:02.344579776+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received lifecycle event: infoChanged
2022-02-05T15:09:02.350069447+00:00 TRACE Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received unhandled lifecycle event: infoChanged
2022-02-05T15:09:02.353139869+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:02.439962478+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:02.447731924+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -53, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x11, ZCLCommandId: 0x07 >, < ConfigureReportingReponse || ZclStatus: SUCCESS > > >
2022-02-05T15:09:02.456322169+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:02.470408747+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:02.474599692+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xFF, rssi: -53, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x39 >, < BindRequestResponse || status: 0x00 > > >
2022-02-05T15:09:02.482238287+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:02.550405145+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:02.554943458+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -53, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x12, ZCLCommandId: 0x07 >, < ConfigureReportingReponse || ZclStatus: SUCCESS > > >
2022-02-05T15:09:02.563828347+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:06.888984813+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:06.899613121+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -53, 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-02-05T15:09:06.908746302+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:09:06.911859953+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T15:09:06.915373945+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-02-05T15:09:06.919604745+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-02-05T15:09:06.928925333+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 false
2022-02-05T15:09:06.932961314+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:07.160742783+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:07.165972458+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -53, 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-02-05T15:09:07.174549876+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:09:07.177590146+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T15:09:07.186183889+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-02-05T15:09:07.190212457+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-02-05T15:09:07.203151859+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 false
2022-02-05T15:09:07.206638990+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:11.510216792+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:11.521397074+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -54, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x13, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2022-02-05T15:09:11.533451627+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:11.543079686+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:11.548005388+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -54, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x03, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 > > > >
2022-02-05T15:09:11.559981148+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:11.563885861+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:11.568378905+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -54, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x14, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2022-02-05T15:09:11.577307272+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:11.708694004+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:11.715924262+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -54, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x04, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x2000 > > > >
2022-02-05T15:09:11.724785038+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:15.695987861+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:15.746603082+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: DeviceTemperatureConfiguration >, lqi: 0xFF, rssi: -54, body_length: 0x0003, < ZDOMessageBody || < ZDOHeader || seqno: 0x82 >, GenericBody: 00 00 > >
2022-02-05T15:09:15.780863277+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:21.011411945+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:21.022021596+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -55, body_length: 0x0019, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x05, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x2000 >, < AttributeRecord || AttributeId: 0x8001, DataType: Enum8, Enum8: 0x01 >, < AttributeRecord || AttributeId: 0x8002, DataType: Enum8, Enum8: 0x00 > > > >
2022-02-05T15:09:21.036977156+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:09:21.042200210+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T15:09:21.045681719+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-02-05T15:09:21.053079976+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-02-05T15:09:21.062644108+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 false
2022-02-05T15:09:21.066640817+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:21.180348810+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:09:21.185660278+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -55, body_length: 0x0011, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x06, 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-02-05T15:09:21.195822486+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:09:21.198870211+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T15:09:21.202284295+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-02-05T15:09:21.206410772+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-02-05T15:09:21.215927928+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 false
2022-02-05T15:09:21.219922138+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:09:31.887831268+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-02-05T15:10:01.894820025+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-02-05T15:10:31.896560783+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-02-05T15:10:53.023724047+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-02-05T15:10:53.029687897+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received command: {“capability”:“switch”,“args”:,“command”:“on”,“component”:“main”,“positional_args”:}
2022-02-05T15:10:53.033079034+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch

Log Part 2

2022-02-05T15:10:53.039756901+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-02-05T15:10:53.047002610+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-02-05T15:10:53.067106012+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:10:53.209946014+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:10:53.215323616+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -53, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x21, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-02-05T15:10:53.224528095+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:10:53.227490987+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-02-05T15:10:53.232795834+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-02-05T15:10:53.241736278+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:10:53.245333895+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:10:53.250138158+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -53, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x07, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-02-05T15:10:53.259085099+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:10:53.262541162+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T15:10:53.265789245+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-02-05T15:10:53.269638361+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-02-05T15:10:53.277778164+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 true
2022-02-05T15:10:53.281135443+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:10:56.247437718+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler capability
2022-02-05T15:10:56.256640697+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received command: {“capability”:“switch”,“args”:,“command”:“on”,“component”:“switch2”,“positional_args”:}
2022-02-05T15:10:56.260029002+00:00 TRACE Zigbee Multi Switch Zemismart test Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:10:56.263775087+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4EB5, dest_endpoint: 0x02, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2022-02-05T15:10:56.278103627+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-02-05T15:10:56.294257338+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:10:56.531761110+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:10:56.536423361+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -53, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x22, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-02-05T15:10:56.545172484+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:10:56.548218127+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-02-05T15:10:56.551957923+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-02-05T15:10:56.560735824+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:10:57.019937983+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:10:57.024497910+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -53, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x08, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-02-05T15:10:57.032284556+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:10:57.035183106+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T15:10:57.039429232+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-02-05T15:10:57.043422027+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“on”}}
2022-02-05T15:10:57.051572782+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 true
2022-02-05T15:10:57.054869383+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:11:01.906676351+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-02-05T15:11:31.904286716+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-02-05T15:12:01.913978621+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-02-05T15:12:31.916132464+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee health poll
2022-02-05T15:12:55.354224769+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:12:55.361739468+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -54, 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-02-05T15:12:55.370839333+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:12:55.373843330+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T15:12:55.377468766+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-02-05T15:12:55.381505622+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-02-05T15:12:55.391053262+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 1 false
2022-02-05T15:12:55.395065464+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled
2022-02-05T15:12:55.591238745+00:00 TRACE Zigbee Multi Switch Zemismart test Received event with handler zigbee
2022-02-05T15:12:55.596737952+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EB5, src_endpoint: 0x02, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -54, 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-02-05T15:12:55.605694263+00:00 TRACE Zigbee Multi Switch Zemismart test Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T15:12:55.608717001+00:00 INFO Zigbee Multi Switch Zemismart test Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T15:12:55.612880418+00:00 PRINT Zigbee Multi Switch Zemismart test function: on_off_attr_handler
2022-02-05T15:12:55.617060827+00:00 INFO Zigbee Multi Switch Zemismart test <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {“capability_id”:“switch”,“attribute_id”:“switch”,“component_id”:“switch2”,“state”:{“value”:“off”}}
2022-02-05T15:12:55.626923935+00:00 PRINT Zigbee Multi Switch Zemismart test src_endpoint , value: 2 false
2022-02-05T15:12:55.630311157+00:00 DEBUG Zigbee Multi Switch Zemismart test TS0012 Switch device thread event handled

From what I see in the DTH, it seems that this device uses the current x (0x0003), y(0x0004) attributes instead of Hue (0x0000) and saturation (0x0001) which are the ones used by the default edge libraries and therefore not it works.

Sorry, I don’t know how to integrate that in this driver

1 Like

Thanks for looking anyway, think i will have to leave this one for now till another driver becomes available, do you think it might be better to remove this fingerprint for this device for now.
Im about half way though my devices on hub, did not realise how many different types i have.
Thanks for your help up to now
Dave

Yes, I remove it
EDIT:
removed in this version

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Light Multifunction Mc        │
│ Version     │ 2022-02-05T17:41:57.334537           │
└─────────────┴──────────────────────────────────────┘
1 Like

I have made some changes in this version of the driver.

  • Download this aversion in your hub
  • With the switches in the ON state, change the driver to this other one.

If you have the CLI let it install and fully configure

let’s see what happens

┌─────────────┬──────────────────────────────────────┐
│ Name        │ Zigbee Multi Switch Zemismart Mc     │
│ Version     │ 2022-02-05T17:46:06.814992           │
└─────────────┴──────────────────────────────────────┘

If it works fine with that DTH, could you capture the IDE configuration live logging when you install it with the DTH? so we can see what he sends and what he answers

One question Please, how do you attach the logs that way? I would like to be able to do it like this

I’m not able to pair to the driver. It keeps pairing to the stock DTH. I’ve tried deleting and reinstalling the drivers as well as rebooting the hub to no avail.

Have this date Your installed driver?

┌─────────────┬──────────────────────────────────────┐
│ Name        │ SmartThings Multipurpose Sensor Mc   │
│ Version     │ 2022-02-04T18:24:38.471734           │
└─────────────┴──────────────────────────────────────┘