matc 0.1.1

Matter protocol library (controller side)
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

# simple rust matter protocol library

![build](https://github.com/tom-code/rust-matc/actions/workflows/rust.yml/badge.svg)
[![doc](https://github.com/tom-code/rust-matc/actions/workflows/doc.yml/badge.svg)](https://tom-code.github.io/rust-matc/matc/)

This is prototype of matter protocol library in rust (controller side).

[API doc](https://tom-code.github.io/rust-matc/matc/)

[Examples](https://github.com/tom-code/rust-matc/tree/main/examples)

It supports controller side of:

* PASE - passcode authenticated session establishment
  * variant of [spake 2+](https://datatracker.ietf.org/doc/rfc9383/)
* CASE - certificate authenticated session establishment
  * variant of [SIGMA](https://www.iacr.org/cryptodb/archive/2003/CRYPTO/1495/1495.pdf)
* Commisioning procedure
  * sign and push certificates to device
* Basic interactions
  * Read attribute
  * Invoke command


Use of demo application:
* Compile demo application using cargo. Binary will be found usually in target/debug/examples/demo.\
  `cargo build --example demo`
* demo application uses clap. use --help to learn all supported parameters
* create CA certificates in directory pem:\
  `./demo ca-bootstrap`
* create key/certificate for controller with id 100:\
  `./demo ca-create-controller 100`
* discover all commissionable devices using mdns:\
  `./demo discover commissionable --timeout 3`
* discover all commissioned devices using mdns:\
  `./demo discover commissioned --timeout 3`
* if you have manual pairing code you need to extract passcode from it using following command:\
  `demo decode-manual-pairing-code 1577-384-0075`
* commission device (device ip address is 192.168.5.70, commissioning passcode is 123456, device id will be 300, device admin has id 100):\
  `./demo commission 192.168.5.70:5540 100 300 123456`
* update fabric label in device:\
  `./demo command invoke-command-update-fabric-label --device-address 192.168.5.70:5540 --controller-id 100 --device-id 300 "testfabric"`
* example how to use read command to read any attribute. This example lists all provisioned fabrics
  by reading attribute 1(fabrics) from cluster 62 (operational credentials) from endpoint 0:\
  `./demo command read --device-address 192.168.5.70:5540  --controller-id 100 --device-id 300 0 62 1`
* turn device on/off:\
  `demo command invoke-command-on --device-address 192.168.5.70:5540 --controller-id 100 --device-id 300`

  `demo command invoke-command-off --device-address 192.168.5.70:5540 --controller-id 100 --device-id 300`
* if you want to start from scratch remove directory pem