Easily configure and run rs-matter

Overview

Configuring the rs-matter crate is not trivial, as it is more of a toolkit rather than a monolitic all-in-one runtime.

Furthermore, operating the assembled Matter stack is also challenging, as various features might need to be switched on or off depending on whether Matter is running in commissioning or operating mode, and also depending on the current network connectivity (as in e.g. Wifi signal lost).

This crate addresses these issues by providing an all-in-one MatterStack assembly that configures rs-matter for reliable operation.

Instantiate it and then call MatterStack::<...>::run(...).

OK, but what would I sacrifice?

Flexibility.

The Matter stack is assembled as one large future which is not Send. Using an executor to poll that future together with others is still possible, but the executor should be a local one (i.e. Embassy's embassy-executor, Tokio's LocalSet, async_executor::LocalExecutor and so on).

The examples are STD-only?

The core of rs-matter-stack is no_std and no-alloc.

You need to provide platform-specific implementations of the following traits for your embedded platform:

• KvBlobStore - non-volatile key-value storage abstraction.
  • For STD, rs-matter-stack provides DirKvBlobStore.
• NetifDiag - network interface abstraction (i.e. monitoring when the network interface is up or down, and what is its IP configuration).
  • For Unix-like OSes, rs-matter provides UnixNetifs, which uses a simple polling every 2 seconds to detect changes to the network interface.
  • Note that For IP (TCP & UDP) IO, the stack uses the edge-nal crate, and is thus compatible with STD and Embassy out of the box. You only need to worry about networking IO if you use other platforms than these two.
• Implementation of the UDP traits from edge-nal.
  • There are out-of-the-box implementations for Rust STD BSD sockets as well as for embassy-net and for OpenThread.
• GattPeripheral - BLE GATT peripheral abstraction of the device radio. Not necessary for Ethernet connectivity
  • For Linux, rs-matter provides BluerGattPeripheral, which uses the Linux BlueZ BT stack.
• NetCtl - Wifi controller implementation when using Wifi connectivity (Thread has a built-in one in OpenThread).
  • NoopWirelessNetCtl is a no-op wireless implementation of a Wifi controller that is useful for testing. I.e. on Linux, one can use PreexistingWireless + NoopWirelessNetCtl together with BluerGattPeripheral and UnixNetifs to test the stack in wireless mode. For production embedded Linux use-cases, you'll have to provide a true NetCtl implementation, possibly based on WPA Supplicant, or NetworkManager (which are in the meantime both available from upstream rs-matter).

Embassy

The rs-matter-embassy crate provides implementations for KvBlobStore, NetifDiag, NetCtl, GattPeripheral and others for the embassy framework.

ESP-IDF

The esp-idf-matter crate provides implementations for KvBlobStore, NetifDiag, GattPeripheral and others for the ESP-IDF SDK.

Example

(See also All examples)

//! An example utilizing the `EthMatterStack` struct.
//! As the name suggests, this Matter stack assembly uses Ethernet as the main transport,
//! as well as for commissioning.
//!
//! Notice that it might be that rather than Ethernet, the actual L2 transport is Wifi.
//! From the POV of Matter - this case is indistinguishable from Ethernet as long as the
//! Matter stack is not concerned with connecting to the Wifi network, managing
//! its credentials etc. and can assume it "pre-exists".
//!
//! The example implements a fictitious Light device (an On-Off Matter cluster).
#![recursion_limit = "256"]

use core::pin::pin;

use env_logger::Target;
use log::info;

use rs_matter::dm::clusters::on_off::test::TestOnOffDeviceLogic;
use rs_matter::dm::clusters::on_off::OnOffHooks;
use rs_matter_stack::eth::EthMatterStack;
use rs_matter_stack::matter::dm::clusters::desc;
use rs_matter_stack::matter::dm::clusters::desc::ClusterHandler as _;
use rs_matter_stack::matter::dm::clusters::on_off;
use rs_matter_stack::matter::dm::devices::test::{TEST_DEV_ATT, TEST_DEV_COMM, TEST_DEV_DET};
use rs_matter_stack::matter::dm::devices::DEV_TYPE_ON_OFF_LIGHT;
use rs_matter_stack::matter::dm::networks::unix::UnixNetifs;
use rs_matter_stack::matter::dm::{Async, Dataver, Endpoint, Node};
use rs_matter_stack::matter::dm::{EmptyHandler, EpClMatcher};
use rs_matter_stack::matter::error::Error;
use rs_matter_stack::matter::utils::init::InitMaybeUninit;
use rs_matter_stack::matter::{clusters, devices};
use rs_matter_stack::mdns::ZeroconfMdns;
use rs_matter_stack::persist::DirKvBlobStore;

use static_cell::StaticCell;

const BUMP_SIZE: usize = 20000;

fn main() -> Result<(), Error> {
    env_logger::Builder::from_env(
        env_logger::Env::default().filter_or(env_logger::DEFAULT_FILTER_ENV, "info"),
    )
    .target(Target::Stdout)
    .init();

    info!("Starting...");

    // Initialize the Matter stack (can be done only once),
    // as we'll run it in this thread
    let stack = MATTER_STACK
        .uninit()
        .init_with(EthMatterStack::init_default(
            &TEST_DEV_DET,
            TEST_DEV_COMM,
            &TEST_DEV_ATT,
        ));

    // Our "light" on-off cluster.
    // It will toggle the light state every 5 seconds
    let on_off = on_off::OnOffHandler::new_standalone(
        Dataver::new_rand(stack.matter().rand()),
        LIGHT_ENDPOINT_ID,
        TestOnOffDeviceLogic::new(true),
    );

    // Chain our endpoint clusters with the
    // (root) Endpoint 0 system clusters in the final handler
    let handler = EmptyHandler
        .chain(
            EpClMatcher::new(
                Some(LIGHT_ENDPOINT_ID),
                Some(TestOnOffDeviceLogic::CLUSTER.id),
            ),
            on_off::HandlerAsyncAdaptor(&on_off),
        )
        // Each Endpoint needs a Descriptor cluster too
        // Just use the one that `rs-matter` provides out of the box
        .chain(
            EpClMatcher::new(Some(LIGHT_ENDPOINT_ID), Some(desc::DescHandler::CLUSTER.id)),
            Async(desc::DescHandler::new(Dataver::new_rand(stack.matter().rand())).adapt()),
        );

    // Create the persister & load any previously saved state
    let persist = futures_lite::future::block_on(
        stack.create_persist_with_comm_window(DirKvBlobStore::new_default()),
    )?;

    // Run the Matter stack with our handler
    // Using `pin!` is completely optional, but reduces the size of the final future
    let matter = pin!(stack.run_preex(
        // The Matter stack needs UDP sockets to communicate with other Matter devices
        edge_nal_std::Stack::new(),
        // Will try to find a default network interface
        UnixNetifs,
        // Will use the mDNS implementation based on the `zeroconf` crate
        ZeroconfMdns,
        // Will persist in `<tmp-dir>/rs-matter`
        &persist,
        // Our `AsyncHandler` + `AsyncMetadata` impl
        (NODE, handler),
        // No user task future to run
        (),
    ));

    // Schedule the Matter run
    futures_lite::future::block_on(matter)
}

/// The Matter stack is allocated statically to avoid
/// program stack blowups.
static MATTER_STACK: StaticCell<EthMatterStack<BUMP_SIZE, ()>> = StaticCell::new();

/// Endpoint 0 (the root endpoint) always runs
/// the hidden Matter system clusters, so we pick ID=1
const LIGHT_ENDPOINT_ID: u16 = 1;

/// The Matter Light device Node
const NODE: Node = Node {
    id: 0,
    endpoints: &[
        EthMatterStack::<0, ()>::root_endpoint(),
        Endpoint {
            id: LIGHT_ENDPOINT_ID,
            device_types: devices!(DEV_TYPE_ON_OFF_LIGHT),
            clusters: clusters!(desc::DescHandler::CLUSTER, TestOnOffDeviceLogic::CLUSTER),
        },
    ],
};

All examples

To build all examples, use:

cargo build --examples --features examples