I would like to see Aqara take a major step toward openness by exposing all device entities, configuration options, and advanced features to third‑party platforms like Home Assistant, instead of limiting users to the reduced feature set available through Matter. The goal is to be able to entirely bypass the Aqara app if using another platform. Let your products do the convincing, not artificial software barriers. I would like Aqara to build a full‑fidelity local API layer that mirrors every capability found in the Aqara app-multi‑endpoint controls, sensitivity adjustments, motion timeout settings, LED indicator options, child‑lock toggles, power monitoring, scene triggers, and multi‑tap events. I would like this API to be fully documented and accessible through local LAN, Zigbee, or Thread, with no cloud dependency, so integrators and Home Assistant users can configure devices with the same depth and precision offered in Aqara’s own interface. I would also like Aqara to adopt a capability‑parity policy, ensuring that any new feature added to the Aqara app is simultaneously exposed to third‑party controllers. This shift would position Aqara as a truly integrator‑friendly ecosystem, dramatically increasing adoption among advanced users and professional installers.
2 Likes
Yes 
Aqara is making big steps to open the connectivity to more protocols and Smarthome platforms! And I’m sure the team of Aqara engineers are going more and more steps in future ! So big probs 
2 Likes