I was wondering if the Climate Sensor W100 in the future would be updated to have the Thread Binding function?
With Thread Binding you can directly bind two Thread devices with each other, with no need of a hub.
This way you can also make more direct and lower latency connections.
For example, I would like to bind my W100 to a Thread radiator valve, so that the valve can use the W100 sensors instead of its own (so no temp offset settings are needed). And I could use the + and - buttons on the W100 to directly control the valve.
@almar Your query about the future update for the Climate Sensor W100 to potentially include Thread Binding is intriguing and highlights a great feature that many users would appreciate. As of now, the W100 supports both Zigbee and Thread protocols, but specific Thread Binding capabilities, like directly connecting two Thread devices without a hub for lower latency, are not mentioned in our current documentation.
Currently, the W100 can be directly added to third-party ecosystems using the Thread protocol by scanning the Matter code, assuming the ecosystem has a compatible Matter & Thread board router. However, the direct binding feature you are asking about isn’t explicitly covered in the available resources.
This is a fantastic idea that could enhance user experience, and I encourage you to share it with our development team or community forums for further discussion. Improvements often come from user insights like yours. If there are any updates or changes, they will likely be announced through Aqara’s official channels. Keep an eye on those for the latest features and updates!
Hello @almar
Perhaps this is possible in the future, now in Thread mode the settings are limited to the matter protocols themselves, perhaps in the future the settings can be added. My opinion.
Its really a bummer that binding Cluster 30 is optional. It looks like Matter is running into the same issue as Bluetooth Mesh protocol did. Every vendor has a different opinion of what a “Switch”, “Dimmer”, “Bulb”, “Motor” is. Without strictly defining what each of these NEEDs to be capable of its nearly impossible to have true interoperability between vendors. Bluetooth Mesh had to add on the NLC specification in attempt to solve this.