Hello, I have a M2 hub working like a charm with more than 15 connected devices. Although my M2 is matter compatible, I wonder why to complicate our life with so many protocols when ZigBee is more than enough. An Aqara connected device does not need so much complicated protocols, despite that Matter compatibility will add considerable 
on the cost.
I wonder if Aqara will not consider having Matter and ZigBee compatible option on Hub models. Tough to manage for sure but up to the consumer to decide and pay the add-on feature if required.
Just a thought 
1 Like
Matter is really useful when you need to connect a third party device. You gain the ability to use this device in Aqara automations, and I actually use third party devices in Aqara automations (for example I dim the third party lights in my bedroom when the P1 detects motion). That being said, I pair all my Aqara devices in Zigbee mode, because it give me more possibilities.
Another use case is: you want to share an Aqara Matter device (like the P2 sensor) directly to another ecosystem.
Matter allows the device to be paired to many hubs, so there is no lag when you connect it to many ecosystems at once. While Zigbee devices can only pair with one network (one hub) and when you share via ecosystem integration, then the hub acts as a “proxy” which adds latency.
Both Zigbee and Matter have their use cases and I believe it’s great we have the choice and the hubs both support Zigbee and Matter over WiFi/Thread (because it’s the official name, for example if your Matter device uses WiFi then it’s “Matter over WiFi”, but many Aqara devices use Thread)
2 Likes