From 1da1c4643fcd45d31497dc7f3f2f5f46f1f29be4 Mon Sep 17 00:00:00 2001
From: ivmarkov <ivan.markov@gmail.com>
Date: Sat, 5 Oct 2024 20:21:25 +0000
Subject: [PATCH] Fix the README

---
 README.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md
index 1001977..d94278f 100644
--- a/README.md
+++ b/README.md
@@ -10,7 +10,7 @@
 
 Everything necessary to run [`rs-matter`](https://github.com/project-chip/rs-matter) on the ESP-IDF:
 * Bluedroid implementation of `rs-matter`'s `GattPeripheral` for BLE comissioning support.
-* [`rs-matter-stack`](https://github.com/ivmarkov/rs-matter-stack) support with `Netif`, `KvBlobStore` and `Modem` implementations.
+* [`rs-matter-stack`](https://github.com/ivmarkov/rs-matter-stack) support with `Netif`, `Ble`, `Wireless` and `KvBlobStore` implementations.
 
 Since ESP-IDF does support the Rust Standard Library, UDP networking just works.
 
@@ -19,7 +19,7 @@ Since ESP-IDF does support the Rust Standard Library, UDP networking just works.
 (See also [All examples](#all-examples))
 
 ```rust
-//! An example utilizing the `EspNCWifiMatterStack` struct.
+//! An example utilizing the `EspWifiNCMatterStack` struct.
 //!
 //! As the name suggests, this Matter stack assembly uses Wifi as the main transport,
 //! (and thus BLE for commissioning), where `NC` stands for non-concurrent commisisoning
@@ -36,7 +36,7 @@ use core::pin::pin;
 use embassy_futures::select::select;
 use embassy_time::{Duration, Timer};
 
-use esp_idf_matter::{init_async_io, EspMatterBle, EspMatterWifi, EspWifiMatterStack};
+use esp_idf_matter::{init_async_io, EspMatterBle, EspMatterWifi, EspWifiNCMatterStack};
 
 use esp_idf_svc::eventloop::EspSystemEventLoop;
 use esp_idf_svc::hal::peripherals::Peripherals;
@@ -72,7 +72,7 @@ fn main() -> Result<(), anyhow::Error> {
     // confused by the low priority of the ESP IDF main task
     // Also allocate a very large stack (for now) as `rs-matter` futures do occupy quite some space
     let thread = std::thread::Builder::new()
-        .stack_size(55 * 1024)
+        .stack_size(75 * 1024)
         .spawn(|| {
             // Eagerly initialize `async-io` to minimize the risk of stack blowups later on
             init_async_io()?;
@@ -104,7 +104,7 @@ async fn matter() -> Result<(), anyhow::Error> {
     // as we'll run it in this thread
     let stack = MATTER_STACK
         .uninit()
-        .init_with(EspWifiMatterStack::init_default(
+        .init_with(EspWifiNCMatterStack::init_default(
             &BasicInfoConfig {
                 vid: 0xFFF1,
                 pid: 0x8000,
@@ -204,7 +204,7 @@ async fn matter() -> Result<(), anyhow::Error> {
 /// The Matter stack is allocated statically to avoid
 /// program stack blowups.
 /// It is also a mandatory requirement when the `WifiBle` stack variation is used.
-static MATTER_STACK: StaticCell<EspWifiMatterStack<()>> = StaticCell::new();
+static MATTER_STACK: StaticCell<EspWifiNCMatterStack<()>> = StaticCell::new();
 
 static DEV_ATT: dev_att::HardCodedDevAtt = dev_att::HardCodedDevAtt::new();
 
@@ -216,7 +216,7 @@ const LIGHT_ENDPOINT_ID: u16 = 1;
 const NODE: Node = Node {
     id: 0,
     endpoints: &[
-        EspWifiMatterStack::<()>::root_metadata(),
+        EspWifiNCMatterStack::<()>::root_metadata(),
         Endpoint {
             id: LIGHT_ENDPOINT_ID,
             device_types: &[DEV_TYPE_ON_OFF_LIGHT],