[ST Edge/Beta] Xiaomi/Aqara/Tuya zigbee sensors driver

I think may be it is required to read detection interval and sensitivity attributes under opple cluster to make the device to “bind” to the hub. This is how I made Aqara P1 sensor working. I hope it is the same for your device.
Anyway, please try 1.6.3 version

I still have 1.6.2, probably need to wait a bit.

The temperature is not updated on the Aqara Presence Detector FP1, most likely due to the Aqara report issue.

Can I ask you to make rssi, lqi optional, it makes quite a lot of noise in the history log. But it is useful mostly for debugging.

Is the problem only with unnecessary messages in the history log or also unuseful capabilities in the detailed view?
If it is only a history, I can easily make update interval configurable, perhaps once a day.

Basically both history and details , but don’t waste much time on this.
If it’s easier to suppress only history it is totally fine.

can you please Detection interval to the settings
, and make it as a number input. As far as i remember valid values are [2…max_uint16]

now it’s not possible to use the slider - even if i manage to put value <10 (you need to be very precise) the slider jumps back to 0

Detection sensitivity belongs to the settings as well.

Hi @veonua ,

Have you tried to double click on the slider?
It should allow entering the number directly.

I was considering to add those to settings. However, I wanted to show the values, reported by the device (i.e actual values) and not values, configured by a user.
Unfortunately, it is not possible to update settings in read attribute response callback.

If the slider goes back to zero, that probably means the device rejected configuration. This is most likely because it is a sleeping device.
Could you please provide logs?
I think I might need to implement delayed configuration to configure the device on the next message it sends.
Have you tried to wake up device by pressing pairing button when you try to change config?
Thanks

It helped but for a short period of time, after the following report, the slider went back to zero.

It seems like battery status never comes, the device has the Power{something} cluster, so most likely it supports the default Zigbee voltage report. at this moment both battery percentage and voltage are 0.


Also, can I ask to remove the temperature capability from the Presence device? It reports +5C* from the ambient temperature, and tricks my Google assistant?

Hi @ygerlovin ,

I have one of these sensors running my own DTH. My handler doesn’t get into all the proprietary clusters/messaging. I was just focused on cluster 0x0500 and attribute id 0x002d for vibration at that time and haven’t circled back for any further development.

I believe there are two parameters available for this sensor though, Reporting Interval and Sensitivity Level.

Raw Description 01 0104 0402 01 04 0000 0003 0001 0500 02 0003 0019

  • zigbeeNodeType: SLEEPY_END_DEVICE
  • firmwareManufacturerCode: 4447
  • firmwareFullVersion: 00000019
  • application: 19
  • endpointId: 01
  • firmwareImageType: 8968
  • manufacturer: LUMI
  • model: lumi.vibration.agl01

If you decide to give this a shot I can test. I believe ST may also have just a very basic Edge driver, so I’ll have to check. I know they do for the Aqara light sensor because I’m using that now just fine.

What is the best routine setup for switching lights off after no motion detected by the Aqara RTCGQ11LM Motion Sensor?

I have lights switch on if the Aqara is detecting motion and another routine for switching lights off when no detection for 5 minutes, set by the stock field of status held for how long.

But if I wave at the sensor when lights go off, the routine for switching lights on again doesn’t work, even if the sensor detects motion. Annoying if used in the bathroom for example.

What is the model of sensor you have?
Does the sensor detect motion and it is only the routine that does not work?

Aqara RTCGQ11LM.

It seems like the issue is when I both have motion identified (precondition) AND luminance (equals to or less than 400). With only motion identified it works alright.

Although the two sensors I have are brand new, they have showed battery 0% from the beginning (I installed them a few hours ago). I guess it COULD be that the included batteries are already more or less dead (although brand new sensors from Amazon…). But again, for at least one of the sensors it does work when using only motion detection.

I would suggest using illuminance as the precondition and motion as the trigger.

hi i have an aqara vibration sensor running on the dth would you be able to add it to this edge driver or something like that , if you need any info from the sensor let me know . thanks martin

The RTCGQ11LM only reports luminance with motion and I can’t remember in what order they appear. If it is illuminance first you might have the problem of the Routine running before motion has been reported. You might like to think about whether using motion as the condition works better, or if it wouldn’t do any harm for the Routine to run twice you might like to consider if you are better off not using a precondition at all.

The other issue you may have is in how the less than or equal condition is implemented. A lot of reports I’ve seen suggest that it is actually implementing a falls to or below condition (I use Rules rather than Routines and they give you the choice).

Like many Aqara devices, the RTCGQ11LM doesn’t start reporting battery usage for a few hours after being ‘reset’. Then it switches to roughly hourly.

1 Like

@westis

I also have RTCGQ11LM, but I don’t use preconditions. Instead, I have a rule with logical AND (when all conditions are met).

The battery is usually updated once in one or two hours. If it shows zero after 2 hours, then either the battery is empty or there is a problem with the driver. Would it be possible to provide a log with battery reporting?

Hi @montyfert

I don’t have vibration sensors and never looked at them.
Could you please provide a log, showing messages, sent by the device?
Thanks

1 Like

is this what your after
3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:23 PM: info vibration sensor [vibration sensor] [parse] [name:threeAxis, value:[0.7, -0.2, 89.3]]

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:23 PM: debug vibration sensor [vibration sensor] [readattr] Psi = 0.7°, Phi = -0.2°, Theta = 89.3°

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:23 PM: debug vibration sensor [vibration sensor] [readattr] X = 14, Y = -4, Z = 1195

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:23 PM: info vibration sensor [vibration sensor] [readattr]

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:23 PM: debug vibration sensor [vibration sensor] [parse] read attr - raw: 1069010101120805250E00FCFFAB04, dni: 1069, endpoint: 01, cluster: 0101, size: 18, attrId: 0508, result: success, encoding: 25, value: 04abfffc000e

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:18 PM: info vibration sensor [vibration sensor] [mapsensorevent] 4

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:18 PM: info vibration sensor [vibration sensor] [clearvibration]

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:15 PM: info vibration sensor [vibration sensor] [parse] [name:button, value:pushed, descriptionText:Drop (button)]

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:15 PM: info vibration sensor [vibration sensor] [mapsensorevent] 3

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:15 PM: info vibration sensor [vibration sensor] [readattr]

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:15 PM: debug vibration sensor [vibration sensor] [parse] read attr - raw: 10690101010A5500210300, dni: 1069, endpoint: 01, cluster: 0101, size: 10, attrId: 0055, result: success, encoding: 21, value: 0003

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:14 PM: info vibration sensor [vibration sensor] [parse] [name:acceleration, value:active, descriptionText:Vibration (acceleration)]

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:14 PM: info vibration sensor [vibration sensor] [mapsensorevent] 1

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:14 PM: info vibration sensor [vibration sensor] [readattr]

3fad5e39-dd69-4201-bba8-ae63fdff4be5 10:32:14 PM: debug vibration sensor [vibration sensor] [parse] read attr - raw: 10690101010A5500210100, dni: 1069, endpoint: 01, cluster: 0101, size: 10, attrId: 0055, result: success, encoding: 21, value: 0001

thanks

Hi @veonua

I added user configurable time update interval for signal strength.
Also, I tried to fix battery reporting for RTCGQ14LM (Aqara Motion P1).

Please let me know whether it works for you.

The

Thank you, now the voltage is displaying the value - 32.0 mV , I believe it must be 3.2V (2 batteries CR2450 )
but the battery percentage is missing now.

@veonua ,

Just to make sure, is it for RTCGQ14LM?