espressif/esp-matter
1
0
Fork 0
mirror of https://github.com/espressif/esp-matter.git synced 2026-04-27 19:13:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

esp_matter_rainmaker: Fix the rainmaker cluster_id

Browse Source 
docs: Corresponding changes
This commit is contained in:
Chirag Atal
2022-05-31 16:06:37 +05:30
parent 9a13e6684e
commit 0b555d3cf7
3 changed files with 8 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
components/esp_matter_rainmaker/esp_matter_rainmaker.cpp
+2 -1
View File
@@ -32,7 +32,8 @@ namespace cluster {
namespace rainmaker {
static constexpr chip::EndpointId endpoint_id = 0x00000000; /* Same as root node endpoint. This will always be
endpoint_id 0. */
static constexpr chip::ClusterId Id = 0x131B0000; /* 0x131B == manufacturer code */
static constexpr chip::ClusterId Id = 0x131BFC00; /* 0x131B == manufacturer code.
0xFCOO == start of manufacturer specific cluster_id */
namespace attribute {
namespace status {
docs/en/developing.rst
+1 -1
View File
@@ -528,7 +528,7 @@ Non-Standard/Custom clusters can also be created:
::
uint32_t custom_cluster_id = 0x131b0000;
uint32_t custom_cluster_id = 0x131bfc00;
cluster_t *cluster = cluster::create(endpoint, custom_cluster_id, CLUSTER_FLAG_SERVER);
2.4.3.3 Attributes and Commands
examples/rainmaker_light/README.md
+5 -5
View File
@@ -44,10 +44,10 @@ rainmaker.py claim --addr 0x3E0000 $ESPPORT
This needs to be done after commissioning.
Check if the device already has user node association done, using the
custom RainMaker cluster (cluster_id: 0x131b0000):
custom RainMaker cluster (cluster_id: 0x131bfc00):
```
chip-tool any read-by-id 0x131b0000 0x0 0x7283 0x0
chip-tool any read-by-id 0x131bfc00 0x0 0x7283 0x0
```
- If the above custom status attribute (attribute_id: 0x0) returns
@@ -59,7 +59,7 @@ chip-tool any read-by-id 0x131b0000 0x0 0x7283 0x0
Get the RainMaker node id (attribute_id: 0x1):
```
chip-tool any read-by-id 0x131b0000 0x1 0x7283 0x0
chip-tool any read-by-id 0x131bfc00 0x1 0x7283 0x0
```
RainMaker CLI:
@@ -83,7 +83,7 @@ Now use the payload to run the RainMaker configuration command from
chip-tool:
```
chip-tool any command-by-id 0x131b0000 0x0 '"<user-id>::<secret-key>"' 0x7283 0x0
chip-tool any command-by-id 0x131bfc00 0x0 '"<user-id>::<secret-key>"' 0x7283 0x0
```
The device/node should now be associated with the user.
@@ -132,7 +132,7 @@ User Node association is failing on my device:
- If the device prints "This command has reached a limit", reboot the
device to run the command again.
- Read the status attribute:
`chip-tool any read-by-id 0x131b0000 0x0 0x7283 0x0`. If this custom
`chip-tool any read-by-id 0x131bfc00 0x0 0x7283 0x0`. If this custom
status attribute (attribute_id: 0x0) returns true, the association
has already been done.
- If you are still facing issues, reproduce the issue on the default