Is that something set via preferences?
1 Like
Got a good battery reading for one of my two on your driver. No error with this one.
_Aq2 battery is 100%
descMap: [raw:37D80100004201FF421D0121170C0328200421A83305213C00062405000000000A2109C5641001, dni:37D8, endpoint:01, cluster:0000, size:42, attrId:FF01, encoding:42, command:0A, value:! ( !¨3!<�$
! Åd, clusterInt:0, attrInt:65281]
1 Like
Found it here in Home Assistant from a quick Google. Looks "preferency" to me. 
Quick press, after leaving alone overnight, gives
37D801000076050042166C756D692E73656E736F725F6D61676E65742E61713201FF421D01210D0C03281B0421A83305213C00062400000000000A2109C5641000
I’m speculating that the battery is in bold
01FF -> FF01
42
1D
01
21
0D0C -> 0C0D -> 3085 -> 3.085 volts
Well darn, I was hoping with all of the changes to the Aqara integration, my Aqara Cube would finally pair with my C8 but no dice! When I first got it, I was able to get it to work on my C7 but never C8. I only have Zigbee running on the D8 so the Cube has been living on HA.
Thanks @danabw, that's what I meant. Aqara switches have the ability to be set as ''wireless'' switches, and that's a big plus when installed along smart bulbs to keep them powered. Read right and there some calling it decoupled mode, wireless mode, smart bulb mode or disconnected mode...The future is supported by US switches, D1, H1, E1, H1M... so I guess it is standard for aqara switches.
@kkossev can help explaining the feature to @mike.maxwell, as he helped in another thread related to aqara switches.
3 Likes
Did you try the double-secret-probation pairing trick that @kkossev has talked about? (The "trick" was possibly created by someone else, can't remember...)
Found it!
…the ‘double luck’ procedure worked for me and for some other HE users who tried it. I was able to pair and keep connected some very problematic Zigbee devices that never worked before on my C-8 hubs.
From https://community.hubitat.com/t/2-3-9-157-zigbee-plugs-are-found-but-do-not-function/139919/35
1. Bring the device right next to the hub
2. Go to Settings->Zigbee Details and click the 'Rebuild Network' button.
3. Wait for the process to finish (the button will become enabled again)
4. Click the same 'Rebuild Network' button again, and wait for the process to finish.
5. Go to Devices -> Add Device -> Zigbee and click on the 'Pair while trying to avoid Zigbee 3.0 repeaters ' link, confirm.
6. Start the Zigbee pairing on the device (press the pairing button for 4-5 seconds).
Please follow the steps 1..5 precisely, not skipping and not adding anything else.
From
1 Like
I understand the feature now,I just need to know what bits to send the device to change this setting
3 Likes
This is a collection of community drivers that support almost all popular Aqara/Xiaomi Zigbee devices :
You can look for an example of Aqara relays decoupled mode (smart bulb mode) configuration in @dandanache 's 'Aqara Dual Relay Module T2 (DCM-K01)' driver code.
Aqara/Xiaomi Zigbee devices use a TLV (Tag-Length-Value) encoding data structure to report a set of parameters specific to each device periodically. BTW, TLV encoding is also used in the Matter protocol. The big difference between the Matter TLV and Aqara TLV is that the latest is not officially documented ...
The community drivers contain various custom implementations of the Aqara TLV decoding. Jonathan's 'Aqara Human Presence Sensor FP1' driver provides an excellent code example.
4 Likes
Will we see support for their locks like the u200?
1 Like
It's not currently possible to join the Zigbee units directly to the hub as inclusion is only triggered via Bluetooth using the Aqara mobile app, now if someone knows a secret way to get the device to enter join mode, I'm all ears.
1 Like
With the latest platform update on the C-8, the Aqara MCCGQ11LM still cannot be brought directly in via zigbee pairing? I would have to purchase the Aqara Door-Window sensor P2?
Aqara MCCGQ11LM:
We can connect the locks through the (cloud) Aqara hub correct?
In My case an Aqara U100 lock.
Currently connected through Alexa but Alexa routines do not allow automated unlocking only locking (unless thats changed recently).
No - you don't need anything, you can pair the Aqara MCCGQ11LM contact sensors directly to the hub. They actually have been unofficially supported for years via custom community drivers, now you can choose between the new built-in Aqara driver and the community drivers.
I think you were confused by this below - Mike was referring specifically to the Aqara locks.
In the future you will be able to connect the lock via Matter (local) using the Aqara hub as a Matter bridge for the lock that is connected to the Aqara hub using Zigbee. All local > Zigbee lock to Aqara Hub via Zigbee then Aqara lock to Hubitat via Matter. There is no driver for the locks over Matter bridge, yet.
1 Like
I did add the device and after time it stops responding. This issue was happening when I had my C-7.
Isn't the U200 lock Matter over Thread?
1 Like
Yes, but I was talking about the U100 model. The U200 just needs the Hubitat Matter lock driver (not currently available), and the lock commissioned to a Matter controller with Thread, then it could be added to Hubitat without the need for Aqara hub.
2 Likes
This has been a long-term issue w/Aqara devices, they have had problems "sticking" to the hub for years. Their performance is much better now than before, and they seem to do best when connected to repeaters rather than to the hub directly.
1 Like
Any possible ETA on a matter lock driver?
