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

Checking with CLI, I seem to have an older driver version installed. I’m not sure how to update to latest driver. I thought it would automatically download latest version? Thanks for your help.

Tried the other driver with same result.

I will try to get some logging for the working DTH
Log below and next post. I add it using Hide Details under the gear.

Device on - New driver - Off

β”Œβ”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ # β”‚ Driver Id β”‚ Name β”‚
β”œβ”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ 1 β”‚ 8a5a5586-aa12-4cbb-b7ed-fa3ad735df0d β”‚ Zigbee Aqara Water Leak Sensor Mc β”‚
β”‚ 2 β”‚ 950d769e-5e53-4cb9-aad7-b7b6023f20d2 β”‚ Zigbee Multi Switch Zemismart Mc β”‚
β”‚ 3 β”‚ 7d469ae2-4d8f-422e-9997-d77d67065b8d β”‚ Zigbee Multi Switch Zemismart test β”‚
β””β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
? Select a driver. 2
2022-02-05T19:42:43.809872433+00:00 TRACE Zigbee Multi Switch Zemismart Mc Setup driver Zigbee_Multi_Switch with lifecycle handlers:
DeviceLifecycleDispatcher: Zigbee_Multi_Switch
default_handlers:
driverSwitched:
init:
doConfigure:
child_dispatchers:

2022-02-05T19:42:43.813211975+00:00 TRACE Zigbee Multi Switch Zemismart Mc Setup driver Zigbee_Multi_Switch with Capability handlers:
CapabilityCommandDispatcher: Zigbee_Multi_Switch
default_handlers:
refresh:
refresh
switch:
off
on
child_dispatchers:

2022-02-05T19:42:43.818485100+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-02-05T19:42:43.848878600+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler _resync
2022-02-05T19:42:43.851876433+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler environment_info
2022-02-05T19:42:43.860065183+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-02-05T19:42:43.866862516+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:42:43.870140183+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler _resync
2022-02-05T19:42:43.873117891+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler environment_info
2022-02-05T19:42:43.876194850+00:00 DEBUG Zigbee Multi Switch Zemismart Mc Z-Wave hub node ID environment changed.
2022-02-05T19:42:43.883818183+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:42:43.887370350+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler device_lifecycle
2022-02-05T19:42:43.890591391+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received lifecycle event: added
2022-02-05T19:42:43.894801183+00:00 TRACE Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received unhandled lifecycle event: added
2022-02-05T19:42:43.897932350+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:42:43.901223683+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler device_lifecycle
2022-02-05T19:42:43.904359183+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received lifecycle event: driverSwitched
2022-02-05T19:42:43.910161308+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found DeviceLifecycleDispatcher handler in Zigbee_Multi_Switch
2022-02-05T19:42:43.918635058+00:00 INFO Zigbee Multi Switch Zemismart Mc <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-05T19:42:43.935803725+00:00 INFO Zigbee Multi Switch Zemismart Mc <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-05T19:42:43.944128933+00:00 INFO Zigbee Multi Switch Zemismart Mc <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-05T19:42:43.953861516+00:00 INFO Zigbee Multi Switch Zemismart Mc <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-05T19:42:43.962275141+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x0000 > > > >
2022-02-05T19:42:43.978870183+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x0000 > > > >
2022-02-05T19:42:43.985540808+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:42:44.249541183+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:42:44.255172266+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: -55, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x45 >, < BindRequestResponse || status: 0x00 > > >
2022-02-05T19:42:44.263837058+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:42:44.280595100+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:42:44.289933683+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x26, ZCLCommandId: 0x07 >, < ConfigureReportingReponse || ZclStatus: SUCCESS > > >
2022-02-05T19:42:44.297853850+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:42:44.302416433+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:42:44.307486225+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: -55, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x46 >, < BindRequestResponse || status: 0x00 > > >
2022-02-05T19:42:44.316135141+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:42:44.320992058+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:42:44.325946058+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x27, ZCLCommandId: 0x07 >, < ConfigureReportingReponse || ZclStatus: SUCCESS > > >
2022-02-05T19:42:44.333803183+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:42:44.337038266+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:42:44.351136141+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x28, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2022-02-05T19:42:44.361940974+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:42:44.365570433+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:42:44.373233474+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x09, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 > > > >
2022-02-05T19:42:44.383241974+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:42:44.389957683+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:42:44.394407099+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x29, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2022-02-05T19:42:44.403542558+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:42:44.466415266+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:42:44.474178724+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0A, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 > > > >
2022-02-05T19:42:44.483723849+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:43:13.842028842+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee health poll
2022-02-05T19:43:43.853811335+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee health poll
2022-02-05T19:44:13.867071411+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee health poll
2022-02-05T19:44:33.475919782+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:44:33.483784948+00:00 INFO Zigbee Multi Switch Zemismart Mc <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-05T19:44:33.492981073+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T19:44:33.496023990+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T19:44:33.499632532+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-02-05T19:44:33.503402240+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {β€œcapability_id”:β€œswitch”,β€œcomponent_id”:β€œmain”,β€œstate”:{β€œvalue”:β€œoff”},β€œattribute_id”:β€œswitch”}
2022-02-05T19:44:33.513012615+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 1 false
2022-02-05T19:44:33.516913032+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:44:33.590393907+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:44:33.596734948+00:00 INFO Zigbee Multi Switch Zemismart Mc <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-05T19:44:33.605662573+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T19:44:33.608683073+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T19:44:33.611839032+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-02-05T19:44:33.615851115+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {β€œcapability_id”:β€œswitch”,β€œcomponent_id”:β€œswitch2”,β€œstate”:{β€œvalue”:β€œoff”},β€œattribute_id”:β€œswitch”}
2022-02-05T19:44:33.625037365+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 2 false
2022-02-05T19:44:33.629111573+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:44:41.856083071+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:44:41.866177363+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: -55, body_length: 0x0003, < ZDOMessageBody || < ZDOHeader || seqno: 0x82 >, GenericBody: 00 00 > >
2022-02-05T19:44:41.876231530+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:44:43.870469988+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee health poll
2022-02-05T19:44:47.415184820+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:44:47.421813612+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x03, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 >, < AttributeRecord || AttributeId: 0x8001, DataType: Enum8, Enum8: 0x01 >, < AttributeRecord || AttributeId: 0x8002, DataType: Enum8, Enum8: 0x00 > > > >
2022-02-05T19:44:47.431225403+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T19:44:47.434208487+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T19:44:47.437866778+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-02-05T19:44:47.441700153+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {β€œcapability_id”:β€œswitch”,β€œcomponent_id”:β€œmain”,β€œstate”:{β€œvalue”:β€œoff”},β€œattribute_id”:β€œswitch”}
2022-02-05T19:44:47.451280653+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 1 false
2022-02-05T19:44:47.455652070+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:44:47.491323987+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:44:47.497119945+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x04, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 > > > >
2022-02-05T19:44:47.506766987+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T19:44:47.509852153+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T19:44:47.513071695+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-02-05T19:44:47.517125237+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {β€œcapability_id”:β€œswitch”,β€œcomponent_id”:β€œswitch2”,β€œstate”:{β€œvalue”:β€œoff”},β€œattribute_id”:β€œswitch”}
2022-02-05T19:44:47.526610612+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 2 false
2022-02-05T19:44:47.530663112+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
listening for logs… done

Next log, just turning it on and it turns off

Off - On - Off

β”Œβ”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ # β”‚ Driver Id β”‚ Name β”‚
β”œβ”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ 1 β”‚ 8a5a5586-aa12-4cbb-b7ed-fa3ad735df0d β”‚ Zigbee Aqara Water Leak Sensor Mc β”‚
β”‚ 2 β”‚ 950d769e-5e53-4cb9-aad7-b7b6023f20d2 β”‚ Zigbee Multi Switch Zemismart Mc β”‚
β”‚ 3 β”‚ 7d469ae2-4d8f-422e-9997-d77d67065b8d β”‚ Zigbee Multi Switch Zemismart test β”‚
β””β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
? Select a driver. 2
2022-02-05T19:48:23.570002996+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler capability
2022-02-05T19:48:23.575773913+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> received command: {β€œcommand”:β€œon”,β€œpositional_args”:,β€œcapability”:β€œswitch”,β€œcomponent”:β€œswitch2”,β€œargs”:}
2022-02-05T19:48:23.579297329+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found CapabilityCommandDispatcher handler in Zigbee_Multi_Switch
2022-02-05T19:48:23.583884538+00:00 INFO Zigbee Multi Switch Zemismart Mc <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-05T19:48:23.598297496+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {β€œcapability_id”:β€œswitch”,β€œcomponent_id”:β€œswitch2”,β€œstate”:{β€œvalue”:β€œon”},β€œattribute_id”:β€œswitch”}
2022-02-05T19:48:23.609565371+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:48:23.860226704+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:48:23.864847954+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x46, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-02-05T19:48:23.874815746+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T19:48:23.879351787+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-02-05T19:48:23.883151162+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {β€œcapability_id”:β€œswitch”,β€œcomponent_id”:β€œswitch2”,β€œstate”:{β€œvalue”:β€œon”},β€œattribute_id”:β€œswitch”}
2022-02-05T19:48:23.892889662+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:48:23.897001954+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:48:23.901700704+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x05, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: true > > > >
2022-02-05T19:48:23.911425412+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T19:48:23.914526996+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T19:48:23.918025912+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-02-05T19:48:23.921910079+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {β€œcapability_id”:β€œswitch”,β€œcomponent_id”:β€œswitch2”,β€œstate”:{β€œvalue”:β€œon”},β€œattribute_id”:β€œswitch”}
2022-02-05T19:48:23.930355579+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 2 true
2022-02-05T19:48:23.934507787+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:48:43.922635116+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee health poll
2022-02-05T19:49:13.928890401+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee health poll
2022-02-05T19:49:43.935681102+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee health poll
2022-02-05T19:50:13.943348386+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee health poll
2022-02-05T19:50:26.166236258+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:50:26.173325050+00:00 INFO Zigbee Multi Switch Zemismart Mc <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-05T19:50:26.182927592+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T19:50:26.186046050+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T19:50:26.189764758+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-02-05T19:50:26.193604300+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {β€œcapability_id”:β€œswitch”,β€œcomponent_id”:β€œmain”,β€œstate”:{β€œvalue”:β€œoff”},β€œattribute_id”:β€œswitch”}
2022-02-05T19:50:26.203011467+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 1 false
2022-02-05T19:50:26.206987383+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:50:26.280193175+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:50:26.286630050+00:00 INFO Zigbee Multi Switch Zemismart Mc <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-05T19:50:26.295674800+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T19:50:26.298704842+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T19:50:26.301879717+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-02-05T19:50:26.305898592+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {β€œcapability_id”:β€œswitch”,β€œcomponent_id”:β€œswitch2”,β€œstate”:{β€œvalue”:β€œoff”},β€œattribute_id”:β€œswitch”}
2022-02-05T19:50:26.315368967+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 2 false
2022-02-05T19:50:26.319478008+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:50:34.566173715+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:50:34.571466381+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: -55, body_length: 0x0003, < ZDOMessageBody || < ZDOHeader || seqno: 0x82 >, GenericBody: 00 00 > >
2022-02-05T19:50:34.580784131+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:50:40.096458467+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:50:40.103354768+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x03, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 >, < AttributeRecord || AttributeId: 0x8001, DataType: Enum8, Enum8: 0x01 >, < AttributeRecord || AttributeId: 0x8002, DataType: Enum8, Enum8: 0x00 > > > >
2022-02-05T19:50:40.113962170+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T19:50:40.117296168+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T19:50:40.120958128+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-02-05T19:50:40.124939137+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {β€œcapability_id”:β€œswitch”,β€œcomponent_id”:β€œmain”,β€œstate”:{β€œvalue”:β€œoff”},β€œattribute_id”:β€œswitch”}
2022-02-05T19:50:40.134857966+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 1 false
2022-02-05T19:50:40.138953626+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled
2022-02-05T19:50:40.159705287+00:00 TRACE Zigbee Multi Switch Zemismart Mc Received event with handler zigbee
2022-02-05T19:50:40.164777166+00:00 INFO Zigbee Multi Switch Zemismart Mc <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: 0x04, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false >, < AttributeRecord || AttributeId: 0x4001, DataType: Uint16, OnTime: 0x0000 >, < AttributeRecord || AttributeId: 0x4002, DataType: Uint16, OffWaitTime: 0x0000 > > > >
2022-02-05T19:50:40.175510422+00:00 TRACE Zigbee Multi Switch Zemismart Mc Found ZigbeeMessageDispatcher handler in Zigbee_Multi_Switch
2022-02-05T19:50:40.178940039+00:00 INFO Zigbee Multi Switch Zemismart Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-02-05T19:50:40.182240888+00:00 PRINT Zigbee Multi Switch Zemismart Mc function: on_off_attr_handler
2022-02-05T19:50:40.186090379+00:00 INFO Zigbee Multi Switch Zemismart Mc <ZigbeeDevice: 1e053e47-2b50-466a-b50b-c6a8065dcde3 [0x4EB5] (TS0012 Switch)> emitting event: {β€œcapability_id”:β€œswitch”,β€œcomponent_id”:β€œswitch2”,β€œstate”:{β€œvalue”:β€œoff”},β€œattribute_id”:β€œswitch”}
2022-02-05T19:50:40.197125942+00:00 PRINT Zigbee Multi Switch Zemismart Mc src_endpoint , value: 2 false
2022-02-05T19:50:40.200367695+00:00 DEBUG Zigbee Multi Switch Zemismart Mc TS0012 Switch device thread event handled

Just checked, all removed for me now
Thanks

Hi, I have a lonsonho one gang switch. In the hub, it is defined as thing. How can I add it? The same two gang works fine. Model x711 (tyzs3)

I’m not sure how to get the response from the device in the DTH but this is the command that I believe is sent, the added refresh part in bold. See the DTH snip.

zcl mfg-code 0x0000, delay 200, zcl global write 0x0000 0x0099 0x20 {01}, delay 200, send 0x0F70 0x01 0x01, delay 2000, st rattr 0x0F70 0xFF 0x0006 0x0000, delay 2000

DTH snip

def refresh() {
if (isOrvibo()) {
zigbee.readAttribute(zigbee.ONOFF_CLUSTER, 0x0000, [destEndpoint: 0xFF])


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

Hi, Please could you add the devices below:

Yagusmart Zigbee Smart Wall Light Switch (2 gang) Found here

Data * application: 50

  • endpointId: 01
  • firmwareFullVersion: 00000050
  • firmwareImageType: 54179
  • firmwareManufacturerCode: 4417
  • manufacturer: _TZ3000_atp7xmd9
  • model: TS0002
  • onOff: catchall
  • zigbeeNodeType: ROUTER
    Raw Description 01 0104 0100 01 07 0003 0004 0005 0006 E000 E001 0000 02 0019 000A

Yagusmart Zigbee Smart Wall Light Switch (3 gang) Found here

Data * application: 41

  • endpointId: 01
  • manufacturer: _TZ3000_wyhuocal
  • model: TS0013
  • onOff: catchall
  • zigbeeNodeType: SLEEPY_END_DEVICE
    Raw Description 01 0104 0100 01 04 0000 0004 0005 0006 02 0019 000A

This is sent in the device configuration write 1 in attribute 0x0099 of cluster 0x0000 and reads the state of the switch, attribute 0x0000 of 0x0006 cluster.

The write response should be seen a few seconds after the attribute write is sent.

With the edge driver, I already sent the value 1 to the attribute 0x0099 of the cluster 0x0000 and the device responded Attribute not supported.

The exact model and manufacturer of the device, which appear in the IDE page, are necessary to add them to the driver

@Mariano_Colmenarejo please add this motion sensor, Thanks !
Is a Tuya Motion Sensor

01 0104 0402 01 04 0001 0500 0003 0000 04 1000 0006 0019 000A

Hi
Can you add this device in for me on
SmartThings multiportuse sensor Mc:

endpointId: 01
firmwareFullVersion: 1F075310
firmwareImageType: 14
firmwareManufacturerCode: 4174
manufacturer: CentraLite
model: 3321-S
zigbeeNodeType: SLEEPY_END_DEVICE
Raw Description 01 0104 0402 00 08 0000 0001 0003 0020 0402 0500 0B05 FC02 01 0019

Thanks in advance

Next HopUnknown Device
(0)Dataapplication: 41
endpointId: 01
manufacturer: _TYZB01_xfpdrwvc
model: TS0011
zigbeeNodeType: SLEEPY_END_DEVICE
Raw Description01 0104 0100 00 04 0000 0004 0005 0006 01 0019

And this

Data * zigbeeNodeType: ROUTER

  • application: 41
  • endpointId: 01
  • manufacturer: _TZ3000_pmz6mjyu
  • model: TS011F
    Raw Description 01 0104 0009 01 04 0000 0004 0005 0006 02 0019 000A

Was adde two days after with this driver version

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Name        β”‚ SmartThings Multipurpose Sensor Mc   β”‚
β”‚ Version     β”‚ 2022-02-04T18:24:38.471734           β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
1 Like

Added to this driver version

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Name        β”‚ Zigbee Switch Mc                     β”‚
β”‚ Version     β”‚ 2022-02-06T18:10:26.237378           β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
  - id: "_TYZB01_xfpdrwvc/Switch"
    deviceLabel: TZ3000 Switch
    manufacturer: _TYZB01_xfpdrwvc
    model: TS0011
    deviceProfileName: single-switch

Added to this driver version

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Name        β”‚ Zigbee Multi Switch Mc               β”‚
β”‚ Version     β”‚ 2022-02-06T18:23:01.146605           β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
  - id: "TS0013/_TZ3000_wyhuocal"
    deviceLabel: TS0013 Switch
    manufacturer: _TZ3000_wyhuocal
    model: TS0013
    deviceProfileName: three-switch
  - id: "TS0002/_TZ3000_atp7xmd9"
    deviceLabel: TS0002 Switch
    manufacturer: _TZ3000_atp7xmd9
    model: TS0002
    deviceProfileName: two-switch

Has it been been published? I couldn’t get my driver to install either.

Added to this driver version

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Name        β”‚ Zigbee Motion Sensor Mc              β”‚
β”‚ Version     β”‚ 2022-02-06T18:27:27.648589           β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
  - id: "_TZ3000_msl6wxk9/Motion"
    deviceLabel: TS0202 Motion Sensor
    manufacturer: _TZ3000_msl6wxk9
    model: TS0202
    deviceProfileName: motion-battery

Pls, add this too… Big thnx

Data * zigbeeNodeType: ROUTER

  • application: 41
  • endpointId: 01
  • manufacturer: _TZ3000_pmz6mjyu
  • model: TS011F
    Raw Description 01 0104 0009 01 04 0000 0004 0005 0006 02 0019 000A

This afternoon, 1/2 hour ago or so I republished it in case I did it wrong the other day

Got it finally working. Thanks. I was going crazy wondering what I was doing wrong. :grin:

1 Like