Aggregating the multi-endpoint devices to a combined one in HE (temperature and humidity sensor with battery status) is possible, but at this stage of Hubitat implementation of the Matter protocol is not worth the efforts… I will be waiting for the next HE major platform update that includes improvements related to the Matter. The major issue at the moment is that no error codes are returned, but HE calls unconditionally the initialize () method next time a matter method is used. This makes troubleshooting the matter drivers extremely difficult and time-consuming.
2 Likes
Whoever uses Aqara M3 hub with this package - please hold on with the Aqara firmware update to version 4.1.17_xxxx .
This Aqara update added something that breaks the device discovery. I will post again when the problem is found and fixed.
2 Likes
Version 1.1.2 is now pushed via HPM. It fixes the Aqara M3 firmware update issue.
Thanks to @iEnam for the notification and for the tests!
1 Like
NEW - Aqara FP1E improved mmWave sensor is now available on Amazon!
Amazon .com : (link)
Amazon .co.uk : (link)
Amazon .de : (link)
Requires Aqara hub, it is expected to work OK in Hubitat via the Advanced Matter Bridge.
Update: tested and confirmed to work with this driver.
3 Likes
Things have gone south for me recently. I’m using an Aqara hub which has three contact sensors attached. Whenever one of the changes, some 20+ refresh events get triggered which causes some of my automatically me to overload.
Is this an issue in the driver or am I somehow triggering those refresh events?
Minor additional issue: there is a typo (missing “c” in sendSubscribeList()) in one of the messages being logged:
initialize(): calling sendSubsribeList()! (last unsubscribe was more than 902 seconds ago)
Hi,
I suppose you are on the latest driver version 1.1.2 and that the bridged Aqara contact sensors have worked OK initially?
Also, do you have other Matter devices in use paired to the same HE hub?
The possibility for these multiple subscriptions to the Matter events are the biggest problem in HE Matter implementations at the moment - not only for this package, but also for all other Matter drivers. They are caused by calling the initialize() method not only on the HE hub reboot, but also when the Matter device (a bridge or any 'native' Matter device) returns an error response to the last command that was sent by the driver. I haven't found a reliable way to distinguish between the case when the driver must obligatory re-subscribe the events (such as when the HE hub was rebooted, but also when the Aqara hub was rebooted!) and the problematic re-subscriptions result of a Matter communication / commands errors. Hopefully, the issue with this automatic call of the initialize() method will be mitigated somehow in a future HE platform update; I suppose it won't be an easy fix.
Could be a driver issue - the 'refresh' flag not being cleared after a timeout, although at first reading I couldn't find something obvious in the code. I will continue searching for the possible reason(s).
Meanwhile, you should be able to quickly fix the issue by clicking on the "Re Subscribe" button in the Bridge device page. Wait until you see the 'Status' attribute as 'completed'. Then you can click on the 'Refresh' button - you should see only one 'contact is open/closed' log per device. Does this work in your environment?
Thank you for catching the typo - it will be fixed in the next package update.
Thanks for the reply.
Yes, running the latest and the Aqara hub is also paired with an AppleTV
I did the re-subscribe (I swear I tried that before) and it seemed to have improved things. The refresh after that however called refresh twice for each of the contact sensors:
You can enable the Debug logging for several hours and send me the logs in a DM for further analysis... It is still strange that the contact events are duplicated after a forced Re-Subscribe.
What is the Aqara GW model and what is the contact sensor model?
Thanks for offering to look into this. It is actually behaving right now with no more spurious refreshes so the logs at this time will probably not be useful. I’ll keep your offer in mind though when the issue resurfaces.
Aqara Hub M1S
Aqara Door and Window Sensor
1 Like
Seen this?
1 Like
I have one and it's working.
2 Likes
Yep, this is a Matter over Thread device and it should work using the Hubitat inbuilt Matter driver.
@kkossev - I think the importURL is incorrect for the Door Lock child driver. Nothing urgent, obviously, but a little annoying for users who prefer to not use HPM… 
metadata {
definition(name: 'Matter Generic Component Door Lock', namespace: 'kkossev', author: 'Daniel Segall', importUrl: 'https://raw.githubusercontent.com/kkossev/Hubitat---Matter-Advanced-Bridge/main/Components/Matter_Generic_Component_Switch.groovy') {
capability 'Sensor'
capability 'Actuator'
1 Like
Thank you for noticing that - now fixed in the component 'Matter Generic Component Door Lock' driver version 1.1.2.
1 Like
Hi, I don't understand if the FP1E will work as a standard ZigBee device directly with Hubitat or not?
The Aqara FP1E presence sensor uses Aqara specific Zigbee clusters, so it will not work when paired directly to a non-Aqara Zigbe hub.... except, someone writes a dedicated driver for it, reverse-engineering the custom commands...
Matter bridges allow these new devices to be used out of the box, as soon as they are released - all you need is a $30 stick (Aqara E1 hub).
1 Like
The new Aqara FP1E was discovered and works without any problems via Aqara M3 hub! 
5 Likes
Hi
I’m using MAB v1.1.3 with Aqara M3 hub firmware 4.1.8_0016.
I have 2 questions.
I have a aqara Wireless Remote Switch double rocker.
The battery reading works.
I can see that the 0x003B matter event is commented out in the driver.
is it going to enabled soon? The Aqara M3 supports for the wireless remote is
single/double/long click of left and right and also "press both buttons"
if You need a tester for the code I can test it.
Second question
I also have I aqra temperature and humidity T1 sensor.
It work grate , battery/humidity/temp works as expected.
I can se in the code that pressure cluster is missing (0x0403)
Is there any plans to add that, if you do, please add hPa in the settings
Thanks for a good a good implementation for matter bridge
1 Like
Hi Andreas,
When this package was in active development (the first months of this year), the subscription for Matter Events was not working. Subscription for Matter attributes is OK, but not for the events that I expect to be received from buttons (cluster 0x003B). I don't know if anything has changed lately, last update on this topic that I am aware of is this one.
At that time, Aqara hubs were not exposing the Pressure cluster 0x0403 via their Matter bridges (I have E1 and M3). Do you know if this has changed? Do you have your Aqara Bridge also paired to another system (Apple Home, ST, etc...) to check whether the Pressure is reported there?
1 Like
Hi kkossev
I have the M3 matter bridge paired to the HA
The 0x0403 is also missing there .
But the 2 buttons have separat entities, and it receives events from the wireless switch
i assume its from the 003B
1 Like
