ivmarkov
commented
4 months ago rs_matter::data_model::objects::encoder: Error invoking command: CmdStatus { path: CmdPath { path: GenericPath { endpoint: Some(0), cluster: Some(49), leaf: Some(2) } }, status: Status { status: UnsupportedCommand, cluster_status: 0 } }`I am a beginner with Matter but the way I understand the error message is that it points towards the (Root Node 0) Network Commissioning endpoint (49) Thread (2) is not implemented. Looking at the code I can't figure out with my HomePod tried to commission it as a Thread Device
It actually always points to Node 0 (which is not logged, as rs-matter currently supports only one node)
... then endpoint 0 (the root endpoint)
... then cluster 49 (dec) = 0x0031 (hex) = network commissioning
... then command = 2 (dec) = 0x02 (hec) = "AddOrUpdateWifiNetwork"
... so it calls what it should (which is very good news), but the fact that it fails means I probably regressed the code, because there were upstream merges in rs-matter, so a had to refactor a bit the code in esp-idf-matter (blush).
OK - let me try to first reproduce it locally, and then fix it tomorrow. I'll let you know my progress.
3wnbr1
Description
First of all, that's really awesome work, thank you so much for all your efforts to bring Rust and Matter to embedded devices. This is really exiting for hobby / smart home devices
I got really excited when I was able to "pair" the https://github.com/project-chip/rs-matter
onoff_lightexample with my HomePod / HomeKit.However I was not able to reproduce that success with the
esp-idf-matterlightexample. It fails about midway during the setup process and reports in the console the following errorI am a beginner with Matter but the way I understand the error message is that it points towards the (Root Node 0) Network Commissioning endpoint (49) Thread (2) is not implemented. Looking at the code I can't figure out with my HomePod tried to commission it as a Thread Device
I would be glad to help if you have some indications of where to start
Full log