Aqara Support on Hubitat

With the release of latest platform version you have a choice. You can use the Aqara hubs to connect Aqara devices using the Matter protocol OR you can pair Aqara devices directly to Hubitat Elevation hub (no Aqara hub required) using the Zigbee protocol.

17 Likes

oohh exciting.

The Native Curtain Driver E1 - Does that work with the Roller Shade E1? I believe the community driver I am using might be a slightly modified, or was at least derived from a Curtain Driver E1 from somewhere?

1 Like

I have no idea but never hurts to try the built in driver

1 Like

Hi @mike.maxwell

If I am reading correctly, the

Aqara RTCGQ11LM Motion Sensor
and
Aqara WSDCGQ11LM Temp & Humidity Sensor

did not make the list of supported devices?

That is the Weather Sensor, and did make the list. I have been using it in Beta for a bit now, and it seems to function fine.

4 Likes

I haven’t done the motion sensor as of yet

3 Likes

Thanks Mike. I am currently running a C5 as my “aqara only” zigbee hub with community drivers from Jonathan Michaelson. I very quickly looked for a built in driver when I saw the release notes and didn’t see one. I appreciate the reply.

Thank you @neonturbo for telling me to look for “Weather Sensor”. I found it and switched one device over to test.

It will be awesome to switch these devices over to my main zigbee mesh and to delete the second zigbee network.

1 Like

I have about 30 MCCGQ11LM that tend to drop off occasionally. I would like to try them out with the NEW builtin driver.

Is there anyway that I can mass-swap drivers or is it a one by one task?

There isn't, i would just try one or two and let them cook for a while and report anything obtuse...

4 Likes

The user drivers I've been using check for presence etc. so I needed to stop schedules.
I changed mine over one at a time by doing the following to make sure things were clean.
Changed driver to 'Device'.
Then used the buttons in this driver to delete states/schedules etc. etc.
Changed driver to new In Built driver.
Re-paired each device to ensure all parameters were checked/loaded.
This may be complete overkill on my part but the 4 'weather' devices and 2 'Contact Sensors' I have changed to these drivers are working perfectly :crossed_fingers: so far.

4 Likes

My understanding from experts like @kkossev is that drivers don't affect devices staying/leaving the hub. A really bad/spammy driver could mess w/your hub to the point where the device (and others) might slow or stop responding, but changing from one good driver to another good driver isn't going to help w/devices dropping off.

3 Likes

Unless we no longer need zigbee 3.0 repeaters (which @kkossev said).
Two test devices I have tried so far route direct per Zigbee Map app.

1 Like

@mike.maxwell I tried the built in driver on a Xiaomi device. (I've always assumed they were earlier versions of Aqara devices).
While the driver does work I do see this error in the logs.
I'm assuming the driver in not compatible with Xiaomi devices.
This is for a Contact Sensor.

dev:4202024-10-10 18:41:13.909errorjava.lang.StringIndexOutOfBoundsException: begin 0, end -2, length 42 on line 45 (method parse)

@mike.maxwell Getting error message “sometimes” on opening contact,

[dev:940] [info] _Aq2 is open

[dev:940] [debug] descMap: [raw:37D80100060800001001, dni:37D8, endpoint:01, cluster:0006, size:08, attrId:0000, encoding:10, command:0A, value:01, clusterInt:6, attrInt:0]

[dev:940] [debug] description: read attr - raw: 37D80100060800001001, dni: 37D8, endpoint: 01, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 01

[dev:940] [error] java.lang.StringIndexOutOfBoundsException: begin 2, end 20, length 18 on line 45 (method parse)

[dev:940] [debug] description: read attr - raw: 37D80100001801FF42090421A8330A2109C5, dni: 37D8, endpoint: 01, cluster: 0000, size: 18, attrId: FF01, encoding: 42, command: 0A, value: 090421A8330A2109C5

Which specific device is this?

Aqara Zigbee Contact Sensor (MCCGQ11LM)

1 Like

I think FF01 is reporting battery level and the value is in the two bytes following the 0x21. (Byte swapped integer?)

For anyone wondering, the built-in Curtain Driver E1 does NOT work with the Roller Shade Driver E1, so we are stuck with the part working modified/community driver for now...

Is the roller shade available on Amazon?

Yeah, I already have the battery value, it’s just that specific data string is too short and is blowing up the default parse, I didn’t see any short data in my testing, easy fix though