[RELEASE] Aqara / Xiaomi Motion Sensors driver


Vote for the Linptech Human Presence Sensor with 24G mmWave Radar in the Product of the Year Elevated by Hubitat in 2023 !


This is a new thread for the older models of Aqara/Xiaomi motion sensors, that are supported in Hubitat by the custom Aqara P1 Motion Sensor driver initially published here. As this driver supports both the new models (P1, FP1) and the old motion sensors, mixing the updates and the comments for the different devices is somewhat confusing for most of the forum users. Moreover, the behavior of the old Aqara sensors in regards to how they are paired and stay connected to the Zigbee network differs slightly compared to the new sensors.

There are already several custom drivers in Hubitat that support Aqara/Xiaomi motion sensors by @veeceeoh (link), @markus (link), @chirpy (link) and other Hubitat community developers. All these existing drivers are working great, so there should be no reason to change the driver that works for you, except if you want to use one and the same driver for all the different Aqara models of motion and presence sensors.

The recommended method for installing this custom driver is to use the community Hubitat Package Manager (HPM), search for "Aqara P1 Motion Sensor" or by Tag 'Zigbee'.

For manual installation, the last stable version code is here: https://raw.githubusercontent.com/kkossev/Hubitat/main/Drivers/Aqara%20P1%20Motion%20Sensor/Aqara_P1_Motion_Sensor.groovy

Device Links
Aqara T1 Motion Sensor RTCGQ12LM
image
model:"lumi.motion.agl02"
Battery: CR2450
Supports: battery voltage/percentage, detection interval, illuminance, occupancy
FCC: link
Review: link
Aqara site (in Chinese): link
Manual (in Chinese) : link
Purchase link: n/a
Aqara E1 Motion Sensor RTCGQ15LM
image
model:"lumi.motion.acn001"
Battery: CR2450
Supports: battery voltage/percentage,illuminance, occupancy

Aqara site (in Chinese): link
Manual : link
Purchase link: n/a
Aqara Motion Sensor RTCGQ11LM
image
model:"lumi.sensor_motion.aq2"

Battery: CR2450
Supports: battery voltage/percentage, occupancy
Aqara site: link
Manual: link

Homedepot: link
Banggood: link
Xiaomi/Mijia Motion Sensor RTCGQ01LM
image
model:"lumi.sensor_motion"
Battery: CR2032
Supports: low battery warning; occupancy
Banggood: link
4 Likes

Versions history

  • ver. 1.0.0 2022-06-24 - first test version
  • ver. 1.1.0 2022-06-30 - decodeAqaraStruct; added temperatureEvent; RTCGQ13LM; RTCZCGQ11LM (FP1) parsing
  • ver. 1.1.1 2022-07-01 - no any commands are sent immediately after pairing!
  • ver. 1.1.2 2022-07-04 - PowerSource presence polling; FP1 pars
  • ver. 1.1.3 2022-07-04 - FP1 approachDistance and monitoringMode parameters update
  • ver. 1.1.4 2022-07-08 - aqaraReadAttributes()
  • ver. 1.1.5 2022-07-09 - when going offline the battery level is set to 0 (zero); when back online, the last known battery level is restored; when switching offline, motion is reset to 'inactive'; added digital and physical events type
  • ver. 1.1.6 2022-07-12 - aqaraBlackMagic;
  • ver. 1.2.0 2022-07-29 - FP1 first successful initializaiton; attr. 0142 presence bug fix; debug logs improvements; monitoring_mode bug fix; LED is null bug fix ;motionRetriggerInterval bugfix for FP1; motion sensitivity bug fix for FP1; temperature exception bug; monitoring_mode bug fix; approachDistance bug fix; setMotion command for tests/tuning of automations; added motion active/inactive simulation for FP1
  • ver. 1.2.1 2022-08-10 - code / traces cleanup; change device name on initialize();
  • ver. 1.2.2 2022-08-21 - added motionRetriggerInterval for T1 model; filter illuminance parsing for RTCGQ13LM
  • ver. 1.2.3 2022-12-11 - added internalTemperature option (disabled by default); added homeKitCompatibility option to enable/disable battery 100% workaround for FP1 (HomeKit); Approach distance bug fix; battery 0% bug fix; pollPresence after hub reboot bug fix; RTCGQ13LM battery fix; added RTCGQ15LM and RTCGQ01LM; added GZCGQ01LM and GZCGQ11LM illuminance sensors for tests; refactored setDeviceName(); min. Motion Retrigger Interval limited to 2 seconds.
  • ver. 1.2.4 2023-01-26 - renamed homeKitCompatibility option to sendBatteryEventsForDCdevices; aqaraModel bug fix;
  • ver. 1.2.5 2023-01-28 - (dev.branch) bug fixes for 'lumi.sen_ill.mgl01' light sensor';
  • ver. 1.3.0 2023-03-06 - (dev.branch) regions reports decoding; on SetMotion(inactive) a Reset presence command is sent to FP1; FP1 fingerprint is temporary commented out for tests; added aqaraVersion'; Hub model (C-7 C-8) decoding
  • ver. 1.3.1 2023-03-15 - (dev.branch) added RTCGQ01LM lumi.sensor_motion battery % and voltage; removed sendBatteryEventsForDCdevices option; removed lastBattery;
  • ver. 1.4.0 2023-03-16 - (dev.branch) ** breaking change ** replaced presence => roomState [unoccupied,occupied]; replaced presence_type => roomActivity ; added capability 'Health Check'; added add 'Works with ...'; added ping() and RTT
  • ver. 1.4.1 2023-04-21 - (dev.branch) exception prevented when application string is enormously long; italic font bug fix; lumi.sen_ill.agl01 initialization and bug fixes; light sensor delta = 5 lux; removed MCCGQ14LM
  • ver. 1.4.2 2023-05-21 - lumi.sen_ill.agl01 initializetion fixes; removed the E1 contact sensor driver code; trace logs cleanup; added reporting time configuration for the Lux sensors; Lux sensors preferences are NOT reset to defaults when paired again; removed powerSource manipulation; periodic job renamed to deviceHealthCheck()

The latest development branch version URL is here : https://github.com/kkossev/Hubitat/blob/development/Drivers/Aqara%20P1%20Motion%20Sensor/Aqara_P1_Motion_Sensor.groovy


I have placed the previous versions of this driver in a shared Google Drive folder: link
The version number of the old versions is included in the driver name, so different versions can be used with different devices if needed. The latest driver version is always using the default name, as in HPM.

4 Likes

Useful links :

Xiaomi & Aqara Devices - Pairing & Keeping them connected

1 Like

@kkossev
Some cosmetic issues with the light sensor GZCGQ01LM. Remnants of motion sensors in the presentation.

Unhandled Event PLEASE REPORT TO DEV

Summary

dev:27932023-01-29 04:40:57.946 AMwarnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 99D801FCC052F70041250121FC0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni: 99D8, endpoint: 01, cluster: FCC0, size: 52, attrId: 00F7, encoding: 41, command: 0A, value: 250121FC0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000 | msgMap:[raw:99D801FCC052F70041250121FC0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni:99D8, endpoint:01, cluster:FCC0, size:52, attrId:00F7, encoding:41, command:0A, value:0121FC0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, clusterInt:64704, attrInt:247]

dev:27932023-01-29 03:46:10.233 AMwarnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 99D801FCC052F70041250121FA0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni: 99D8, endpoint: 01, cluster: FCC0, size: 52, attrId: 00F7, encoding: 41, command: 0A, value: 250121FA0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000 | msgMap:[raw:99D801FCC052F70041250121FA0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni:99D8, endpoint:01, cluster:FCC0, size:52, attrId:00F7, encoding:41, command:0A, value:0121FA0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, clusterInt:64704, attrInt:247]

dev:27932023-01-29 02:51:22.513 AMwarnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 99D801FCC052F70041250121000C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni: 99D8, endpoint: 01, cluster: FCC0, size: 52, attrId: 00F7, encoding: 41, command: 0A, value: 250121000C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000 | msgMap:[raw:99D801FCC052F70041250121000C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni:99D8, endpoint:01, cluster:FCC0, size:52, attrId:00F7, encoding:41, command:0A, value:0121000C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, clusterInt:64704, attrInt:247]

dev:27932023-01-29 01:56:34.749 AMwarnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 99D801FCC052F70041250121FF0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni: 99D8, endpoint: 01, cluster: FCC0, size: 52, attrId: 00F7, encoding: 41, command: 0A, value: 250121FF0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000 | msgMap:[raw:99D801FCC052F70041250121FF0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni:99D8, endpoint:01, cluster:FCC0, size:52, attrId:00F7, encoding:41, command:0A, value:0121FF0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, clusterInt:64704, attrInt:247]

dev:27932023-01-29 01:01:46.913 AMwarnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 99D801FCC052F70041250121000C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni: 99D8, endpoint: 01, cluster: FCC0, size: 52, attrId: 00F7, encoding: 41, command: 0A, value: 250121000C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000 | msgMap:[raw:99D801FCC052F70041250121000C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni:99D8, endpoint:01, cluster:FCC0, size:52, attrId:00F7, encoding:41, command:0A, value:0121000C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, clusterInt:64704, attrInt:247]

dev:27932023-01-29 12:06:59.135 AMwarnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 99D801FCC052F70041250121FD0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni: 99D8, endpoint: 01, cluster: FCC0, size: 52, attrId: 00F7, encoding: 41, command: 0A, value: 250121FD0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000 | msgMap:[raw:99D801FCC052F70041250121FD0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni:99D8, endpoint:01, cluster:FCC0, size:52, attrId:00F7, encoding:41, command:0A, value:0121FD0B0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, clusterInt:64704, attrInt:247]

dev:27932023-01-28 11:12:11.304 PMwarnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 99D801FCC052F70041250121000C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni: 99D8, endpoint: 01, cluster: FCC0, size: 52, attrId: 00F7, encoding: 41, command: 0A, value: 250121000C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000 | msgMap:[raw:99D801FCC052F70041250121000C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni:99D8, endpoint:01, cluster:FCC0, size:52, attrId:00F7, encoding:41, command:0A, value:0121000C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, clusterInt:64704, attrInt:247]

dev:27932023-01-28 10:17:23.576 PMwarnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 99D801FCC052F70041250121010C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni: 99D8, endpoint: 01, cluster: FCC0, size: 52, attrId: 00F7, encoding: 41, command: 0A, value: 250121010C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000 | msgMap:[raw:99D801FCC052F70041250121010C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, dni:99D8, endpoint:01, cluster:FCC0, size:52, attrId:00F7, encoding:41, command:0A, value:0121010C0328190421A81305211B0006240100000000082115010A213F3C0C200164210000, clusterInt:64704, attrInt:247]

dev:27932023-01-28 09:22:35.817 PMwarnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 99D801FCC052F70041250121020C0328190421A81305211B0006240200000000082115010A213F3C0C200164210000, dni: 99D8, endpoint: 01, cluster: FCC0, size: 52, attrId: 00F7, encoding: 41, command: 0A, value: 250121020C0328190421A81305211B0006240200000000082115010A213F3C0C200164210000 | msgMap:[raw:99D801FCC052F70041250121020C0328190421A81305211B0006240200000000082115010A213F3C0C200164210000, dni:99D8, endpoint:01, cluster:FCC0, size:52, attrId:00F7, encoding:41, command:0A, value:0121020C0328190421A81305211B0006240200000000082115010A213F3C0C200164210000, clusterInt:64704, attrInt:247]

dev:27932023-01-28 08:27:47.980 PMwarnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 99D801FCC052F70041250121030C0328190421A81305211B0006240200000000082115010A213F3C0C200164210900, dni: 99D8, endpoint: 01, cluster: FCC0, size: 52, attrId: 00F7, encoding: 41, command: 0A, value: 250121030C0328190421A81305211B0006240200000000082115010A213F3C0C200164210900 | msgMap:[raw:99D801FCC052F70041250121030C0328190421A81305211B0006240200000000082115010A213F3C0C200164210900, dni:99D8, endpoint:01, cluster:FCC0, size:52, attrId:00F7, encoding:41, command:0A, value:0121030C0328190421A81305211B0006240200000000082115010A213F3C0C200164210900, clusterInt:64704, attrInt:247]

dev:27932023-01-28 07:33:00.138 PMwarnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 99D801FCC052F70041250121010C0328190421A81305211B0006240500000000082115010A213F3C0C200164210D00, dni: 99D8, endpoint: 01, cluster: FCC0, size: 52, attrId: 00F7, encoding: 41, command: 0A, value: 250121010C0328190421A81305211B0006240500000000082115010A213F3C0C200164210D00 | msgMap:[raw:99D801FCC052F70041250121010C0328190421A81305211B0006240500000000082115010A213F3C0C200164210D00, dni:99D8, endpoint:01, cluster:FCC0, size:52, attrId:00F7, encoding:41, command:0A, value:0121010C0328190421A81305211B0006240500000000082115010A213F3C0C200164210D00, clusterInt:64704, attrInt:247]

dev:27932023-01-28 06:38:12.307 PMwarnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 99D801FCC052F70041250121010C0328190421A81305211B0006240300000000082115010A213F3C0C200164212800, dni: 99D8, endpoint: 01, cluster: FCC0, size: 52, attrId: 00F7, encoding: 41, command: 0A, value: 250121010C0328190421A81305211B0006240300000000082115010A213F3C0C200164212800 | msgMap:[raw:99D801FCC052F70041250121010C0328190421A81305211B0006240300000000082115010A213F3C0C200164212800, dni:99D8, endpoint:01, cluster:FCC0, size:52, attrId:00F7, encoding:41, command:0A, value:0121010C0328190421A81305211B0006240300000000082115010A213F3C0C200164212800, clusterInt:64704, attrInt:247]

dev:27932023-01-28 05:43:24.286 PMwarnUnhandled Event PLEASE REPORT TO DEV - description:read attr - raw: 99D801FCC052F70041250121010C0328190421A81305211B0006240800000000082115010A213F3C0C200164213300, dni: 99D8, endpoint: 01, cluster: FCC0, size: 52, attrId: 00F7, encoding: 41, command: 0A, value: 250121010C0328190421A81305211B0006240800000000082115010A213F3C0C200164213300 | msgMap:[raw:99D801FCC052F70041250121010C0328190421A81305211B0006240800000000082115010A213F3C0C200164213300, dni:99D8, endpoint:01, cluster:FCC0, size:52, attrId:00F7, encoding:41, command:0A, value:0121010C0328190421A81305211B0006240800000000082115010A213F3C0C200164213300, clusterInt:64704, attrInt:247]

Please use the latest version 1.2.5 ( just click on the Import button within HE driver code editor.

And the logs seems to be from Markus’s driver?

Thanks, the "Motion Reset Timer" Preference is now gone.

You are right about the logs. I'm doing to much at once, I changed motion sensors and light sensors, I had problems with the motion sensors and ended up restoring and forgot that restored the light sensors as well. BTW, no issues found with the motion detector.

Under State Variables perhaps you could change motionStarted to eventStarted, eventTm, eventTimestamp etc. to make more sense for both devices. Picky, I know.

1 Like

I will check later whether the 'motionStarted' state is used at all for the GZCGQ01LM light sensor It will be more beneficial to add settings for the minimum time between illuminance reports and the lux threshold settings. With the current version, if you pair the light sensor again with this driver, the reporting period will be too frequent...

But before doing this, I have to add the healthCheck online/offline attribute first.

Hey, I don't need the 'motionStarted' state at all for the GZCGQ01LM.

While the 'motionStarted' can be hidden/removed for the light sensor, the custom commands ( like the 'Set Motion' ) can not be hidden from the device web UI. This is a Hubitat limitation for the drivers code.

With the background information you have provided I'm happy with the UI as it stands.

@kkossev something has happened to the motion sensor RTCGQ01LM.

Summary

dev:63602023-01-30 07:10:00.117 AMerrorjava.lang.RuntimeException: java.sql.SQLException: NULL not allowed for column "NAME"; SQL statement: UPDATE DEVICE SET VERSION = ?, DEVICE_NETWORK_ID = ?, LABEL = ?, NAME = ?, ZIGBEE_ID = ?, DEVICE_TYPE_ID = ?, HT_GROUP_ID = ?, UPDATE_TIME = ?, LAN_ID = ?, DISPLAY_AS_CHILD = ?, MAX_EVENTS = ?, MAX_STATES = ?, DISABLED = ?, MESH_ENABLED = ?, MESH_FULL_SYNC = ?, COLLECTION_ID = ?, SPAMMY_THRESHOLD = ?, COMPATIBLE_DEVICE_ID = ? WHERE ID = ? AND VERSION = ? [23502-214] Query: UPDATE DEVICE SET VERSION = ?, DEVICE_NETWORK_ID = ?, LABEL = ?, NAME = ?, ZIGBEE_ID = ?, DEVICE_TYPE_ID = ?, HT_GROUP_ID = ?, UPDATE_TIME = ?, LAN_ID = ?, DISPLAY_AS_CHILD = ?, MAX_EVENTS = ?, MAX_STATES = ?, DISABLED = ?, MESH_ENABLED = ?, MESH_FULL_SYNC = ?, COLLECTION_ID = ?, SPAMMY_THRESHOLD = ?, COMPATIBLE_DEVICE_ID = ? WHERE ID = ? AND VERSION = ? Parameters: [6, BB54, Foyer motion (Aqara) new, null, 00158D0006F24724, 2875, 0, Mon Jan 30 07:10:00 EST 2023, null, false, 11, 30, false, false, false, 0, 300, null, 6360, 5] on line 1053 (method parse)

dev:63602023-01-30 07:10:00.099 AMwarnFoyer motion (Aqara) new unknown model lumi.sensor_motion.aq2 manufacturer null

dev:63602023-01-30 07:10:00.096 AMinfoFoyer motion (Aqara) new InitializeVars... fullInit = false (driver version 1.2.5 2023/01/28 2:54 PM)

dev:63602023-01-30 07:10:00.094 AMinfoFoyer motion (Aqara) new updating the settings from driver version null to 1.2.5 2023/01/28 2:54 PM

dev:63602023-01-30 07:10:00.091 AMdebugFoyer motion (Aqara) new parse: description is read attr - raw: BB540104000A0000210300, dni: BB54, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: 0300

The context, these errors appeared after the last update. I noticed in the logs this morning. However I removed all traces is the device and mesh links. Did a fresh add off the device and this is the error produced.
The device page has no state variables or current states.

1 Like

Can you check the Data section and confirm that the model field is missing?

Then update to the new version timestamp "2023/01/30 2:31 PM", the error message should not be there, but replaced with a warning .

Before the update:
image
After the update:
image

The motion sensor functioning again, picked up 2 warnings:


1 Like

The reason why the manufacturer ( "LUMI") is missing from the Data section is not very clear to me... Once the manufacturer value is missed during the first pairing to HE, it will not be filled in by HE if you pair the device again... Except you switch temporary to the inbuilt 'Device' driver, click on GetInfo button, make sure the fingerprint is shown in the live logs (you may need to wake up the sensor at the same time) and then switch back to the P1 driver.

Is this motion sensor a new device that you just paired to HE, or it is an old one that was using another driver until now?

This is an old sensor using another unsupported driver up till now. I still have 2 other sensors still using the old driver running on HE. I checked those sensors and they don't have the manufacturer filled in either. A one time Warning during pairing is no big deal to me.

These devices pair easily to the old drivers. I have been around enough to understand to go into the old driver and comment out the fingerprint for the sensor. I then deleted the device from HE. Upon pairing your driver is used for pairing. This is what I did to pair with your latest driver.

1 Like

Sadly, on the C-8 hub, my old RTCGQ01LM ("lumi.sensor_motion") fell off the network 24 hours after it was joined as a new device. It was connected directly to the C-8 hub.

Lucky, after I rebuild my C-8 network and paired it again to C-8, The old Xiaomi/LUMI motion sensor chose a repeater! (Tuya pug) :

Summary
Parent child parameters
EzspGetParentChildParametersResponse [networkId=0, childCount=2, parentEui64=0000000000000000, parentNodeId=FFFF]

Child Data
child:[null, 7542, type:UNKNOWN]
child:[null, B96E, type:UNKNOWN]

Neighbor Table Entry
[Extension _TZ3000_cfnprab5, 00A7], LQI:243, age:3, inCost:1, outCost:1
[Plug Nous _TZ3000_2putqrmw, 37F1], LQI:238, age:4, inCost:1, outCost:1
[Plug _TZ3000_okaz9tjs, 4358], LQI:255, age:3, inCost:1, outCost:1
[Light Sensor GZCGQ01LM , 941F], LQI:255, age:9, inCost:1, outCost:0
[Contact DS01 eWeLink MyRoom Door, 9AF7], LQI:252, age:9, inCost:1, outCost:0

Route Table Entry
status:Active, age:64, routeRecordState:0, concentratorType:None, [FP1 My Room, 59D4] via [Plug Nous _TZ3000_2putqrmw, 37F1]
status:Active, age:64, routeRecordState:0, concentratorType:None, [SNZB-02D, 0C9A] via [Plug _TZ3000_okaz9tjs, 4358]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Motion Sensor lumi.sensor_motion myRoom, DE06] via [Plug Nous _TZ3000_2putqrmw, 37F1]

Hope it will stay connected, will continue monitoring it in the next few days.
Platform version 2.3.5.110

2 Likes

The development branch was updated to ver. 1.4.2, adding support for both the older model GZCGQ01LM (lumi.sen_ill.mgl01) and the new T1 model GZCGQ11LM (lumi.sen_ill.agl01) Xiaomi/Aqara Light Sensors.

In the Preferences section it is possible to fine-tune the illuminance sensors reporting periods :

The threshold setting is a relative value (does not represent Lux) !

When changing the preferences, you need to press shortly the pairing button on the sensor.

3 Likes

Should the documentation not mention this driver (dev) is also working for the Aqara GZCGQ11M Lux Sensor?
image

@kkossev when will the dev version move to the last stable version? I think my dev version was overwrite by HPM (after some problems with HPM), suddenly I saw a "presence" state :scream: :slight_smile:

This weekend, I promise! :slight_smile:

Other than showing up the old "presence" :sob: state , were there any other problems flipping between the two rather different versions?

1 Like