Yes, I have the same switch
@smedberg, @amin300
In this version of the driver I have put back the writing of the cluster 0x0000 , attribute 0x0099 with value 0x01.
I have also changed the report settings to 1 minute instead of 5 min
See what happens
βββββββββββββββ¬βββββββββββββββββββββββββββββββββββββββ
β Name β Zigbee Multi Switch Zemismart Mc β
β Version β 2022-02-07T20:31:50.386539 β
βββββββββββββββ΄βββββββββββββββββββββββββββββββββββββββ
Same result
and switch cant be switched on/off from app
It is still turning off after 2min but is working in the app as it should for me.
I will try to dig deeper in the working DTH to understand what the difference is.
Itβs reporting temperatures now although custom reporting intervals are not working (but they do work within your Zigbee Motion Sensor Mc driver).
The garage door feature works functionally but the sensor itself needs to be offset 90 degrees. Stock DTH sensor was positioned lengthwise vertically but now needs to be oriented horizontally to work.
Thanks.
Reconfigure them in preferences and check in the CLI that the device responds SUCESS >>>, as can see in my logs, I changed the interval from 60 min to 61min and it answered sucess
There are some times that if the device is far away, the first time it does not reconfigure well
Summary
2022-02-07T22:16:59.018535039+00:00 INFO SmartThings Multipurpose Sensor Mc <ZigbeeDevice: d74ae15c-00d7-4a0e-a545-4c09c40ca642 [0x9E9C] (Puerta Casa)> received lifecycle event:
infoChanged
2022-02-07T22:16:59.028439706+00:00 TRACE SmartThings Multipurpose Sensor Mc Found DeviceLifecycleDispatcher handler in smartthingsMultipurposeSensor
2022-02-07T22:16:59.034159706+00:00 PRINT SmartThings Multipurpose Sensor Mc device.preferences[infoChanged]= 0.0 preferences: tempOffset
2022-02-07T22:16:59.040193706+00:00 PRINT SmartThings Multipurpose Sensor Mc device.preferences[infoChanged]= No preferences: garageSensor
2022-02-07T22:16:59.046304039+00:00 PRINT SmartThings Multipurpose Sensor Mc device.preferences[infoChanged]= 100 preferences: changeRep
2022-02-07T22:16:59.052541373+00:00 PRINT SmartThings Multipurpose Sensor Mc device.preferences[infoChanged]= 61 preferences: maxTime
2022-02-07T22:16:59.058805039+00:00 PRINT SmartThings Multipurpose Sensor Mc << Preference changed: name, old, new >> maxTime 60 61
2022-02-07T22:16:59.065258373+00:00 PRINT SmartThings Multipurpose Sensor Mc maxTime y changeRep: 3660 100
2022-02-07T22:16:59.076990373+00:00 INFO SmartThings Multipurpose Sensor Mc <ZigbeeDevice: d74ae15c-00d7-4a0e-a545-4c09c40ca642 [0x9E9C] (Puerta Casa)> sending Zigbee message: <
ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x9E9C, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 286D97000108ECDC, src_endpoint: 0x01, cluster: TemperatureMeasurement, dest_addr_mode: 0x03, dest_address: 286D97000204B680, dest_endpoint: 0x01 > > >
2022-02-07T22:16:59.104397706+00:00 INFO SmartThings Multipurpose Sensor Mc <ZigbeeDevice: d74ae15c-00d7-4a0e-a545-4c09c40ca642 [0x9E9C] (Puerta Casa)> sending Zigbee message: <
ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x9E9C, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Int16, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x0E4C, reportable_change: 100 > > > >
2022-02-07T22:16:59.120958706+00:00 PRINT SmartThings Multipurpose Sensor Mc device.preferences[infoChanged]= preferences: version
2022-02-07T22:16:59.126865706+00:00 DEBUG SmartThings Multipurpose Sensor Mc Puerta Casa device thread event handled
2022-02-07T22:17:05.129154709+00:00 TRACE SmartThings Multipurpose Sensor Mc Received event with handler zigbee
2022-02-07T22:17:05.137752376+00:00 INFO SmartThings Multipurpose Sensor Mc <ZigbeeDevice: d74ae15c-00d7-4a0e-a545-4c09c40ca642 [0x9E9C] (Puerta Casa)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x9E9C, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xC4, rssi: -51, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x29 >, < BindRequestResponse || status: 0x00 > > >
2022-02-07T22:17:05.159909042+00:00 DEBUG SmartThings Multipurpose Sensor Mc Puerta Casa device thread event handled
2022-02-07T22:17:05.165844042+00:00 TRACE SmartThings Multipurpose Sensor Mc Received event with handler zigbee
2022-02-07T22:17:05.179351376+00:00 INFO SmartThings Multipurpose Sensor Mc <ZigbeeDevice: d74ae15c-00d7-4a0e-a545-4c09c40ca642 [0x9E9C] (Puerta Casa)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x9E9C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, lqi: 0xC4, rssi: -51, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x76, ZCLCommandId: 0x07 >, < ConfigureReportingReponse || ZclStatus: SUCCESS > > >
Yes, the DTH has the axes changed for the Centralite sensor, I donβt know if I could do it.
If itβs important, Iβll try it when I have some more time, Iβm a bit busy right now
I changed settings again as suggested and confirmed with the CLI. Itβs working now.
No need. I just reoriented the sensor. More of a FYI. Thanks again.
Hi there,
I think I have the same device as this, but with a slightly different manufacturer code. Will that affect whether this is picked up on your driver? Iβve installed your drivers but it still only shows as a βThingβ when I pair
Added to this driver version
βββββββββββββββ¬βββββββββββββββββββββββββββββββββββββββ
β Name β Zigbee Motion Sensor Mc β
β Version β 2022-02-09T19:35:19.423736 β
βββββββββββββββ΄βββββββββββββββββββββββββββββββββββββββ
- id: "_TZ3000_mcxw5ehu/Motion"
deviceLabel: TS0202 Motion Sensor
manufacturer: _TZ3000_mcxw5ehu
model: TS0202
deviceProfileName: motion-battery
Perfect, worked straight away, thanks
Hi, Mariano.
Help me too, pls.
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
Added to this driver version
βββββββββββββββ¬βββββββββββββββββββββββββββββββββββββββ
β Name β Zigbee Switch Mc β
β Version β 2022-02-09T21:05:44.402598 β
βββββββββββββββ΄βββββββββββββββββββββββββββββββββββββββ
- id: "_TZ3000_pmz6mjyu/Switch"
deviceLabel: TS011F Switch
manufacturer: _TZ3000_pmz6mjyu
model: TS011F
deviceProfileName: single-switch
Iβm sorry, but this two-gang switch.
Added to this driver version
If not work well, tell me and change it to other different driver
βββββββββββββββ¬βββββββββββββββββββββββββββββββββββββββ
β Name β Zigbee Multi Switch Zemismart Mc β
β Version β 2022-02-10T15:51:41.373111 β
βββββββββββββββ΄βββββββββββββββββββββββββββββββββββββββ
Big thnx, my friend. Work well.
Can you add this contact sensor? Thanks.
Data
- application: 13
- endpointId: 01
- manufacturer: Sercomm Corp.
- model: SZ-DWS08
- zigbeeNodeType: SLEEPY_END_DEVICE
Raw Description 01 0104 0402 00 07 0000 0001 0003 0020 0402 0500 0B05 01 0019

Can you add this contact sensor? Thanks.
Data
- application: 13
- endpointId: 01
- manufacturer: Sercomm Corp.
- model: SZ-DWS08
- zigbeeNodeType: SLEEPY_END_DEVICE
Raw Description 01 0104 0402 00 07 0000 0001 0003 0020 0402 0500 0B05 01 0019
Added to this driver version as contact, temperature and battery
βββββββββββββββ¬βββββββββββββββββββββββββββββββββββββββ
β Name β Zigbee Contact Mc β
β Version β 2022-02-11T15:22:07.474828 β
βββββββββββββββ΄βββββββββββββββββββββββββββββββββββββββ
- id: "Sercomm Corp./SZ-DWS08"
deviceLabel: Sercomm Open/Closed Sensor
manufacturer: Sercomm Corp.
model: SZ-DWS08
deviceProfileName: contact-profile
Mariano,

Added to this driver version as contact, temperature and battery
βββββββββββββββ¬βββββββββββββββββββββββββββββββββββββββ β Name β Zigbee Contact Mc β β Version β 2022-02-11T15:22:07.474828 β βββββββββββββββ΄βββββββββββββββββββββββββββββββββββββββ
Not sure why but sensor is not pairing with your driver. Itβs defaulting to groovy βThingβ still and only works if I assign a custom DTH such as Tyco Door/Window Sensor or SmartSense Open/Closed Sensor.
The latest version driver Zigbee Contact Mc is installed correctly on my hub, fingerprints match but itβs just not pairing to the edge driver and nothing on CLI logcat as expected. Thanks.

Not sure why but sensor is not pairing with your driver. Itβs defaulting to groovy βThingβ still and only works if I assign a custom DTH such as Tyco Door/Window Sensor or SmartSense Open/Closed Sensor.
If you have a custom DTH then it wonβt pair with the driver.
You have to delete the custom DTH or edit it and write // begore of the fingerprint of this sensor and publish agains

If you have a custom DTH then it wonβt pair with the driver.
I donβt have a custom DTH for the device. It is listed as βThingβ after pairing which has no configurable settings and no data displayed. I can get it to work if I change the type to one of the custom DTHs previously mentioned within the IDE. Then it will display contact, temp, battery. Am I missing something else? Thanks.