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

Hello, niquini, I hope you are well too
Added to this driver version

  - id: "TUYATEC-2gn2zf9e/Motion"
    deviceLabel: TUYATEC Motion Sensor
    manufacturer: TUYATEC-2gn2zf9e
    model: RH3040
    deviceProfileName: motion-battery
│ Name        │ Zigbee Motion Sensor Mc              │
│ Version     │ 2022-01-19T15:57:00.107161           │

Hey Mariano. Niquini introduced me your work and i would like to thank you a lot for the previous help for me and all community here in Brazil!

He also previously posted some info about this RH3040 Zemismart Zigbee Motion Sensor (battery) and my version was not recognized.

Here is the data:

Would you mind to add it?

Thank you again


1 Like

hello @Coelhorj,

If you already had the driver installed, you have to check and wait for the version date to be this or higher.

If you don’t want to wait, you can install it with the CLI or uninstall old driver of the Hub and reinstall it from the channel.

Thank you very much, now the temperature is displayed.

Another one to you. A Zigbee Switch, also Zemismart. An “old” model rounded touch button TS0001:


  • Last Hop LQI: 120
  • Last Hop RSSI: -70
  • Received Messages From Device: 267
  • Received Messages From Device (Duplicates): 2
  • Messages Transmitted to Device: 139
  • Messages Transmitted to Device (Failures): 0
  • Updated Time: 2022-01-19 4:43 PM BRT


  • application: 40
  • endpointId: 01
  • manufacturer: TUYATEC-dp5y39af
  • model: TS0001
  • onOff: catchall
  • zigbeeNodeType: ROUTER

Raw Description
01 0104 0100 00 05 0000 0003 0004 0005 0006 01 0019

Current States *

  • switch: off
  • checkInterval: 720 s

Added to this driver version

│ Name        │ Zigbee Switch Mc                     │
│ Version     │ 2022-01-19T21:08:03.562256           │
  - id: "TUYATEC-dp5y39af/TS0001"
    deviceLabel: TUYATEC Switch
    manufacturer: TUYATEC-dp5y39af
    model: TS0001
    deviceProfileName: single-switch


A new one. Again Tuya Based, Lumminance sensor, model TS0222

Processing: 16426278318704588366505657727119.jpg…




Raw Description
01 0104 0106 01 04 0000 0400 0001 0500 02 0019 000A

I don’t have any illuminance driver.
Ask to @Benjamin_Ginders, who made a driver to illuminance device to see if he can add your device fingerprints

1 Like

all right, just posted there. Thaks again!

Hallo ! Is it possible to do a edge driver to this smarthings siren ?

  • zigbeeNodeType: SLEEPY_END_DEVICE
  • firmwareManufacturerCode: 4401
  • firmwareFullVersion: 15006230
  • application: 15
  • endpointId: 01
  • firmwareImageType: 124
  • manufacturer: Sercomm Corp.
  • model: SZ-SRN12N
    Raw Description 01 0104 0403 00 05 0000 0003 0500 0502 0B05 01 0019

Best regards Markus

Added to this driver version

│ Name        │ Zigbee Siren Mc                      │
│ Version     │ 2022-01-22T16:43:50.441379           │
  - id : Sercomm/SZ-SRN12N
    deviceLabel : Sercomm Siren
    manufacturer : Sercomm Corp.
    model : SZ-SRN12N
    deviceProfileName : switch-alarm

Hi Mariano,
Did you get the time to check this?

Do you refer to this device?

For this manufacturer, I have write a 1 in the attribute 0x0099 of the cluster 0x0000, as a post that link to me says.

For it to take effect you have to uninstall and reinstall the device with the new version of the driver.

please tell me if it works or not

│ Name        │ Zigbee Multi Switch Zemismart Mc     │
│ Version     │ 2022-01-22T17:23:29.327658           │

Thank you @Mariano_Colmenarejo for your quick reply
Tested and still light goes OFF after 2 mins
I checked and device picked the new driver

Thank you :+1::+1: works great !


Hallo again !

Is it possible to do a edge driver to this aqara vibration / tilt sensor

  • application: 08
  • endpointId: 01
  • manufacturer: LUMI
  • model: lumi.vibration.aq1
  • zigbeeNodeType: SLEEPY_END_DEVICE
    Raw Description 01 0104 000A 01 04 0000 0003 0019 0101 06 0000 0004 0003 0005 0019 0101


Because of the clusters it has, I don’t think it will work with any of the drivers I have.
I don’t handle LUMI devices well, there are developers @veonua or @ygerlovin who have drivers for this manufacturer, I don’t know if they can help you with this

Test with this version.
I wrote 0X0000 in cluster 0x0006, atribute 0x04001 (onTime)

│ Name        │ Zigbee Multi Switch Zemismart Mc     │
│ Version     │ 2022-01-23T18:07:24.327887           │

That is a Tuya-made switch and the turning itself off after two minutes is a known issue for that model with many different brands of hubs, not just smartthings. It only seems to work well out of the box with a tuya-made Gateway.

For example, here’s a discussion over at openhab

The Zigbee standard allows companies to use some custom clusters, and Tuya does so. And they are not required to document those custom clusters. So it can be challenging to get those devices to work with other hubs.

Specifically, some of their switch models have a built in timer and it appears that that is being activated when the device joins the network unless you are using a tuya gateway. :disappointed_relieved:

I suggest you start a new thread with the model number in the topic title and hopefully if anybody else has it working with ST they will let you know how. :thinking:

If you find someone who has it working with a Groovy DTH than that information might be helpful to those who are trying to write edge Drivers.

1 Like