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

Interesting :thinking: maybe it also needs the yale fingerprint lock subdriver?Its a lock that have fingerprint/rfcard/pin unlock methods.

I saw that this sub driver limits the number of codes to 30. If you look in the lock manual you can see this:

If this doesn’t work i will try to create my own driver and see if i can figure out :sweat_smile:
Have to check what i need to install to be able to code. Any easy to intall next next finish framework? :sweat_smile:

I don’t have access to the cli until Friday and I can’t modify anything.

This is a tutorial on how to install the necessary tools in Windows

Thanks @Mariano_Colmenarejo! I’ll try that and see what i can do.
Very well explained, by the way :smiling_face:

1 Like

That would make a difference, wouldn’t it? :woman_facepalming:

Using the motion driver with aqara RTCGQ11LM motion sensor not working properly.
The lux is on 1 all the time, the battery meter doesn’t show anything.
Maybe this sensor not supported? :thinking:
I tried to set the zigbee thing MC driver to get information but not showing anything.

SmartThings changed something, now to get info from ZigBee Thing Mc you need to wait 30 minutes!


Also after 12 hours, there is nothing!
It’s strange.
I will look for another driver for this, which works good with it.

Data info is in device history

I know, But there is nothing there!
I tried with 2 sensors also tried with yakov’s smart things driver, also no info.
Anyway, this is the sensor I have.

Just found this amazing item on AliExpress. Check it out!
₪47.71 | Aqara Motion Sensor Smart Human Body Sensors Body Movement PIR Wifi Wireless ZigBee Connection For Aqara hub XiaoMi Home APP

This sensor exist in zigbee Motion Sensor Mc since August 2023

Follow the steps well to put the device in pairing mode, it can be a little tedious

- id: "LUMI/sensor_motion.aq2"
    deviceLabel: Aqara Motion Sensor RTCGQ11LM
    manufacturer: LUMI
    model: lumi.sensor_motion.aq2
    deviceProfileName: lumi-motion-illuminance

But when I set your driver with it, there is no battery indication also after 4 days, and the illumination stuck at 1 lux.
I changed to Yakov driver and I can see the battery % and the lux indicator move up and down.
Maybe there is any bugs in the driver? :thinking:

Driver changes do not configure the device and it may not work or work partially.

For the device to be configured correctly, it must be paired directly with the controller you want to use.

1 Like

But if I have more than 1 driver for this senor for example, how can I let it paired directly with the specific driver I want?

Well, you will have to delete one of the driver temporarily.

Devices that are already working well with a driver and you change them to zigbee thing Mc are not deconfigured.

Once you have passed to zigbee thing Mc, you can delete the driver that you do not want it to be paired with.

Pair the device and then you can install the deleted driver and switch devices again from zigbee thing Mc

1 Like


This is really anoying and something that samsung needs to address pretty quick. There is a plausible reason to not configure a device when you change a driver?? Driver change should be something simple to test things, without disrupting other working devices.

1 Like

I didn’t know it’s critical to pair the device with the specific driver I want.
I changed alot of drivers to learn more as new user! That’s mean I should start pairing all devices again with the drivers I want!?

On the old groovy platform, whenever you changed DTH in the IDE, the configuration was executed, but it also had its drawbacks.

Depending on the driver it was paired with the first time, it may or may not work.

If it was paired with a zigbee thing driver, these drivers do not configure any cluster or attribute, so if you later change to another driver, zigbee switch or contact, for example, cluster 0006, On/Off, or cluster 0500, IASZone, will not be configured.

In the case of a zigbee switch, which is powered by A/C and does not sleep, there would be no visible problem for users, since it would report manual state changes and although it does not report periodically every 5 minutes, the health check function would read the device every 8 minutes (5 min x 1.5) and since they don’t sleep then it would answer and it wouldn’t show up offline in app.

In the case of zigbee contact, it would depend on the type of device and how deeply it sleeps, but the normal thing is that it does not periodically report its status and does not respond to the healthCheck readings and would appear offline after about 2 hours.

If the initial pairing was with a similar driver and a very similar profile, there should be no problem, since this driver will configure the necessary clusters and attributes, for example if you paired with a stock zigbee switch and you change to a zigbee switch Mc or with stock zigbee Contact and you change to zigbee contact Mc.

There are more nuances, for example, my drivers do execute the device configuration with a driver change, but depending on the device it will accept it or not.

For example, tuya sensors with battery sleep deeply and do not accept the configuration when changing drivers, even if you try to configure. Samjin(Aeotec) accept new configuration in a driver change.

Some Tuya multi-switch devices require 7 attributes of cluster 0000 to be read at the first moment of pairing and the device to be in pairing mode.

There are more cases, but with these it is still clear that the procedure is not very clear!!! :grin:

If you are unsure what to do, then there is a process for zigbee devices that configures them without having to uninstall them.

All this explanation is for zigbee devices, for zwave it is different.


Hi @Mariano_Colmenarejo
This is a real newbie question but I have just purchased 5 Heiman zigbee model (HS1SA-E) smoke detectors.
The original post for these was back in 2021 when you wrote a custom DTH which worked with these devices. Since then I think you have written a universal EDGE driver which appears to work with smoke detectors as well as other sensors. Should I use this edge driver and how do I apply them. Do I sign up to your channel and how do I access your channel please.

model (HS1SA-E) I think it has this fingerprints and must works fine with
Zigbee Smoke/CO Detector Mc

I have three of this model

- id: "HEIMAN/SmokeSensor-N-3.0"
    deviceLabel: HEIMAN Smoke Detector
    manufacturer: HEIMAN
    model: SmokeSensor-N-3.0
    deviceProfileName: smoke-battery