well that can be the nature of a Beta. It’s not the goal, but if a significant change happens it can upset the balance in a complex system… and this is a complex system.
I gave up on DB for this reason.
well that can be the nature of a Beta. It’s not the goal, but if a significant change happens it can upset the balance in a complex system… and this is a complex system.
I gave up on DB for this reason.
Well I installed the beta because ios26.5 for me was an pain also to buggy on my iphone15 pro but the beta one of ios27 was great also the beta 2 but this last one horrible batterie draining and just 2 dats ago not so sure what happen but all my Apple home devices were unresponsive and Apple home app notified me that my main hub is offline very weird stuff and not so sure if was the update that was for Deco app witch changed all my settings in the app or beta 3 witch is going nuts from no we’re ![]()
![]()
![]()
No idea what Apple’s plans are for Matter camera, but I did notice that the updated “ HomeKit Secure Video Open Source CompatibilityGuide” allows for WebRTC in addition to RTP. I think that’s new, but I honestly haven’t looked at this spec in the last few years.
Anyway, the relevance is that Matter cameras apparently use WebRTC, so that sets the stage without necessarily having to wait until next year’s 28 OS releases.
Just checked the Thread Version of my TBR devices using the “Discovery” app on iOS. Looks like a recent M3 hub firmware upgrade must have included Thread v1.4, as that is what is now showing up. I had recently also updated all of my Apple devices to iOS/tvOS Public Beta 27. So, it appears now all of my TBRs are running Thread v1.4. Hopefully Thread v1.4 improves things. ![]()
I am unfortunately of a different opinion. I have migrated my smart home to matter over thread as much as I can. I today have over 70 thread devices. I started using Apple Home as the “base” and then shared the devices to Aqara and Home Assistant. It worked most of the times but after some weeks months devices stared to become unavailable. During the early summer I took a different approach as Home Assistant has Thread 1.4 implemented and migrated all my devices to a new thread network owned by Home Assistant instead. I then let the Aqara M3 and Apple products join that thread network and shared the devices via matter to Apple Home and Aqara. It is now very stable and since may/June I have only got one powered devices that needed a manual power off/power on to be available again.
I have a lot of IKEA products (25+) via matter over thread.
It might be different in your setup of course but this is my experience.
Any update on Thread 1.4 support for the M3 (and other Aqara hubs)?
This thread was started several months ago, and the M3 was still running Thread 1.3 at the time. Since then, we’ve seen other ecosystems move to Thread 1.4, while Aqara still hasn’t provided a clear timeline.
Could you please give us a concrete update on:
A simple roadmap or ETA would already be very helpful.
Thanks!
@ludovic_boue Hey ludovic_boue, totally get the anticipation — Thread 1.4’s “one mesh network” vision and commissioning-at-scale are genuinely exciting for anyone building out a serious setup.
Unfortunately, I don’t have any concrete roadmap or ETA for Thread 1.4 on the M3 (or other Aqara hubs) that I can share right now. The reference info I have access to mentions that the team’s working on new firmware versions for Thread devices, but notes it’ll still take time before those are available. That’s about as specific as it gets on my end.
For a definitive answer on whether it’s in internal testing, beta, or targeted for a particular quarter, your best bet is to reach out directly:
Contact the Aqara Home App Customer Service Team (Profile > Help & Feedback > Customer Service) or scan the QR code:
If you do get any timelines back, would love if you shared them here — I’m sure plenty of folks in this thread are watching closely.