@joshk995 You seem to be experiencing an issue with wanting Matter Bindings Cluster (30) implemented and firmware updates via DCL for your Aqara H2 EU Dimmer Switch. You can contact customer support for assistance. Contact the Aqara Home App Customer Service Team (Profile> Help & Feedback > Customer Service) or scan the QR code:
I’d like to strongly support this request. I’m running 10 H2 dimmers and around 30 Matter-enabled bulbs on a Thread network, and the current limitation is quite frustrating.
Matter was supposed to move us away from ‘hub-dependent’ logic, yet without Binding Cluster (0x001E) support, we are forced to route every single switch press through Home Assistant. This is inefficient and, more importantly, a huge reliability issue. Just yesterday, while updating Home Assistant, I was left in total darkness for 20 minutes because the switches rely entirely on the server.
Furthermore, the current push towards hub-centric management creates an unnecessary vendor lock-in. Matter was designed to ensure that devices function within any Matter-compliant ecosystem, not just the one provided by the manufacturer. By withholding advanced features like Binding Clusters, Aqara is effectively trying to force power users into their own hub ecosystem, which goes against the core mission of the Connectivity Standards Alliance (CSA). We chose Matter specifically to avoid this type of proprietary fragmentation.
I don’t need a fancy UI for this. Just expose the Binding Cluster in the device’s Matter data model, so we can configure direct bindings using standard controller tools like chip-tool or through the Home Assistant interface.
It’s worth noting that the matterjs-server in HA is already capable of handling bindings. The infrastructure on the controller side is ready; we just need Aqara to implement the cluster in the device firmware. This is not just about the H2 series—we need this across the entire lineup, including P2 sensors. Please push this to the development team.
