nRF7002 WiFi 6 review and building wifi 6 matter accessory

Name: Sign Up to Review the Nordic Wi-Fi 6 IC Dev Kit nRF7002 DK with WI-Fi 6 Router
Rating: 4.1833335 (5 reviews)

ss_shrenik over 1 year ago

RoadTest: Sign Up to Review the Nordic Wi-Fi 6 IC Dev Kit nRF7002 DK with WI-Fi 6 Router

Author: ss_shrenik

Creation date: 29 Jul 2023

Evaluation Type: Evaluation Boards

Did you receive all parts the manufacturer stated would be included in the package?: True

What other parts do you consider comparable to this product?: ESP32, RS9116 NCP or WF200

What were the biggest problems encountered?: Didn't encountered any major problem as such. Only needed to struggle removing access protection from the board. It would have been great if that would have been mentioned somewhere in getting started guide.

Detailed Review:

Introduction

The world of technology is ever-evolving, constantly pushing boundaries and redefining our digital experiences. In recent years, two groundbreaking innovations have captured the tech industry's attention: WiFi 6 and Matter accessories. These revolutionary advancements promise to enhance connectivity and interoperability in ways we've never seen before. In this blog, we'll explore what WiFi 6 and Matter accessories are, how they work together, and the exciting possibilities they bring to the table.

WiFi 6: Unleashing the Power of Connectivity

WiFi 6, also known as 802.11ax, represents the sixth generation of wireless technology. It builds upon its predecessor, WiFi 5 (802.11ac), with significant improvements in speed, capacity, and overall performance. The key features of WiFi 6 include:

a. Increased Speed: WiFi 6 offers faster data transfer speeds, making it ideal for handling bandwidth-intensive tasks like 4K streaming, online gaming, and large file downloads.

b. Enhanced Efficiency: The new technology utilizes Orthogonal Frequency Division Multiple Access (OFDMA) and Multi-User Multiple Input Multiple Output (MU-MIMO) to allow multiple devices to communicate simultaneously, thus reducing congestion and latency.

c. Improved Range: WiFi 6 includes a technology called Target Wake Time (TWT), which allows devices to schedule when and how often they wake up to communicate with the router. This feature leads to improved battery life for connected devices and better overall network range.

d. Backward Compatibility: While WiFi 6 brings exciting new capabilities, it is backward compatible with previous WiFi standards. This means that devices supporting older WiFi versions can still connect to a WiFi 6 router, albeit without experiencing the full benefits of WiFi 6.

Matter Accessories: Creating a Unified Smart Home Ecosystem

Matter, previously known as Project CHIP (Connected Home over IP), is an ambitious collaboration between major tech players like Apple, Google, Amazon, and others. This standard aims to create a unified and secure smart home ecosystem, allowing various smart devices to communicate seamlessly regardless of the manufacturer. Matter will cover a wide range of smart home products, including lighting, thermostats, door locks, and more.

The key benefits of Matter accessories include:

a. Interoperability: With Matter, consumers can mix and match smart devices from different manufacturers, knowing that they will work together effortlessly. This eradicates the issue of devices being locked into specific ecosystems.

b. Improved Security: Matter implements robust security measures, ensuring that all devices on the network are protected from potential cyber threats. This standardized approach raises the bar for smart home security.

c. Simplified Setup: Setting up smart home devices will become much easier with Matter's unified approach. Users will experience a streamlined setup process, reducing the frustration often associated with configuring various devices.

The Synergy Between WiFi 6 and Matter

When WiFi 6 and Matter join forces, they create a powerful duo that enhances the smart home experience. WiFi 6's faster speeds and increased capacity provide a solid foundation for handling numerous connected devices simultaneously. This, combined with Matter's interoperability, ensures that all smart devices, regardless of their brand, can communicate efficiently and seamlessly over the network.

Additionally, with Matter's focus on security, users can rest assured that their smart home devices are protected from potential vulnerabilities, providing peace of mind in the increasingly interconnected world.

The setup

Setting Development Environment for nRF7002

Setting up Dev environment was time consuming but was straight foward. I just followed set by step instruction from here - https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/installation/installing.html

Do not miss/skip any step from here including steps which has hyperlinks to Nordic's official website.

You also need to install nrfprogrammer.

After setting up this, you should be able to see following when creating new project for nRF7002

Build and flash steps

Refer here - https://nrfconnect.github.io/vscode-nrf-connect/get_started/build_app_ncs.html

Build configurator

Where you can configure the board and project configuration, following is what I did for hello work application

In order to program board for both network coprocessor and host, one need to disable access protection. Below was the error I was getting as by default access protection was enabled

-- runners.nrfjprog: /Users/shreniks/work/personal_hobby/nrf7002/matter_bulb/build/zephyr/merged_domains.hex targets both nRF53 coprocessors; splitting it into: /Users/shreniks/work/personal_hobby/nrf7002/matter_bulb/build/zephyr/GENERATED_CP_NETWORK_merged_domains.hex and /Users/shreniks/work/personal_hobby/nrf7002/matter_bulb/build/zephyr/GENERATED_CP_APPLICATION_merged_domains.hex
[error] [ Client] - Encountered error -90: Command read_memory_descriptors executed for 1 milliseconds with result -90
[error] [ Worker] - Can't read memory descriptors, ap-protection is enabled.
[error] [ Client] - Encountered error -90: Command erase_file executed for 27 milliseconds with result -90
[error] [ nRF53] - Failed while detecting device memory block protection status!
[error] [ nRF53] - Failed while erasing device. -90: Access protection is enabled, can't read block protection state.
[error] [ Worker] - Access protection is enabled, can't read block protection state.
ERROR: The operation attempted is unavailable due to readback protection in
ERROR: your device. Please use --recover to unlock the device.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
ERROR: runners.nrfjprog: Flashing failed because the target must be recovered.
To fix, run "west flash --recover" instead.
Note: your target is an nRF53; all flash memory for both the network and application cores will be erased prior to reflashing.
FATAL ERROR: command exited with status 24: nrfjprog --program /Users/shreniks/work/personal_hobby/nrf7002/matter_bulb/build/zephyr/GENERATED_CP_NETWORK_merged_domains.hex --sectorerase --verify -f NRF53 --coprocessor CP_NETWORK --snr 1050740957

I wasn't able to disable even after reading forums where Nordic had some suggestions to disable it. But following method worked for me

Disable access protection

ncs $ nrfjprog --recover --coprocessor CP_NETWORK -f NRF53
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.
Writing image to disable ap protect.
ncs $ nrfjprog --recover -f NRF53
Recovering device. This operation might take 30s.
Erasing user code and UICR flash areas.
Writing image to disable ap protect.

Then I could flash some example program which programs both host and network coprocessor, which worked as expected. Here, we can see wifi scanning worked perfectly and I could see two of my home APs listed in scan result.

Setting up AP

Setting up Sniffer

Since, I use Macbook, one can use Airtool - https://www.macupdate.com/app/mac/56809/airtool to capture Wi-Fi packets.

Testing Wi-Fi 6 connection

First and foremost I tried to understand given Asus AP’s Wifi 6 capabilities and nRF7002 association with Asus AP in WiFi 6 mode. Below is the most simplified diagram that explains how handshake happens between AP and STA

Now, I tried some Zephyr provided examples “sta” where we can configure AP SSID and PSK and it attempts to connect to AP. Following is the sniffer capture I could collect from my 11AC supported MacBook Air. Note that, all management frames can be captured from this since management frames are transmitted with basic rates. We do not need to have wifi6 supporting sniffer to capture them.

Below I marked the frames which captures complete conversation between AP and Nordic STA before it gets connected to AP. Which involves

Scanning AP
Authentication and Association
Aggregation setup

Scanning

In Wi-Fi 6 (802.11ax), station scanning, also known as passive scanning, is performed by client devices to discover and evaluate nearby Wi-Fi networks and access points. The scanning process allows clients to find the best available network to connect to based on factors such as signal strength, supported data rates, security protocols, and other network parameters.

Here's how station scanning typically happens in Wi-Fi 6:

1. Probe Request Frames: When a Wi-Fi 6 client device is not connected to any network and wants to find available networks, it initiates the scanning process by sending out Probe Request frames. These frames are broadcasted, requesting nearby access points to respond with Probe Response frames.

2. Probe Response Frames: Wi-Fi 6 access points that receive the Probe Request frames from the client respond with Probe Response frames. These frames contain information about the access point, such as SSID (mywifi6), supported data rates, security capabilities, channel information, and other relevant parameters.

3. Channel Scanning: The scanning process typically involves listening on all supported channels to find and evaluate nearby access points. Wi-Fi 6 operates in both 2.4 GHz and 5 GHz frequency bands, and the scanning process includes searching for networks in both bands.

4. BSS Coloring: In Wi-Fi 6, BSS Coloring is used to identify different Basic Service Sets (BSSs) operating on the same channel. This helps clients identify potential sources of interference and improves the efficiency of scanning in dense Wi-Fi environments.

5. Network Selection: Based on the information received in the Probe Response frames, the client device evaluates the available networks and decides which access point to connect to. The client considers factors like signal strength, security level (e.g., WPA3 support), and other network parameters to make the best connection decision.

Wi-Fi 6 introduces improvements in scanning efficiency to reduce the time it takes for clients to discover and evaluate available networks. The BSS Coloring feature helps alleviate the impact of overlapping networks, making it easier for devices to distinguish between different access points on the same channel.

Overall, the scanning process in Wi-Fi 6 aims to provide a faster and more efficient way for client devices to find and connect to the most suitable Wi-Fi network based on their preferences and requirements.

Beacon from WiFi 6 AP

HE capabilities show ax specification of AP

HE Capabilities are parts of IEEE802.11 Wireless Management header of Beason frame, and they include AP’s specification of IEEE802.11ax, there are a lot of fields, for example, supported HE-MCS and NSS Set with RX/TX MCS number with Spatial Streams and RU allocation.

Authentication and association

Wi-Fi 6 (802.11ax) enhances secure authentication and association processes to improve the overall security and efficiency of wireless networks. Here's a brief explanation of the typical Wi-Fi 6 secure authentication and association:

1. Authentication:

- Open System Authentication: When a client device wants to connect to a Wi-Fi 6 access point, it sends an association request frame with an empty authentication field. The access point responds with an acknowledgment frame, indicating that it received the request.

- Wi-Fi Protected Access 3 (WPA3): Wi-Fi 6 supports WPA3, which offers stronger security compared to the older WPA2 standard. WPA3 uses Simultaneous Authentication of Equals (SAE) for the authentication process, making it resistant to certain types of attacks, such as dictionary attacks.

2. Association:

- Extended Service Set (ESS): In Wi-Fi 6, the association process is similar to previous Wi-Fi standards. After successful authentication, the client sends an association request to the access point, containing information like supported data rates and capabilities. The access point responds with an association response, acknowledging the connection and providing essential information for communication.

- BSS Coloring: Wi-Fi 6 introduces BSS Coloring, which helps mitigate interference and improves spatial reuse in dense Wi-Fi environments. Access points and client devices use different color tags to distinguish between transmissions from different Basic Service Sets (BSSs) operating on the same channel. This way, devices can better identify potential sources of interference.

The combination of improved authentication methods (WPA3) and features like BSS Coloring enhances security and efficiency in Wi-Fi 6 networks. WPA3's SAE ensures that even if an attacker captures handshake messages, they cannot be used for offline brute-force attacks. BSS Coloring helps improve network performance by reducing co-channel interference and increasing the overall capacity in crowded Wi-Fi environments.

As with any wireless network, it's essential to configure Wi-Fi 6 networks securely with strong passwords and other recommended security settings to protect against un-authorized access and potential security risks. Additionally, regular firmware updates and staying informed about the latest security practices are crucial to maintaining a secure Wi-Fi environment.

Association request from STA

STA sends actual connection settings to AP.

Bandwidth <= 80 MHz
MCS 0-7

There are other many setting information in HE MAC Capabilities and HE PHY Capabilities, Supported Channels, SSID and so on.

- STA also supports Single User Beamformee (SU)- which involves focusing the transmission and reception of signals in specific directions to enhance the RSSI and quality between TX and RX device

STA also supports TWT requester support

TWT (Target Wake Time) is the new Wi-Fi6 mechanism that set individual sleep time between AP and STAs.STA set individual wake time in association. AP sends trigger packet to wake up the STA and STA sends back if needed.

Association response from AP

Here we can see the status code is successful and assoc ID as 0x000c. Association Response means AP determined setting configuration, confirmed connection from STA, and linked up and start actual data communication with STA.

These are actual connection configurations that are sent by AP

Aggregation setup

These ADDBA frames are responsible for setting up aggregation between AP<->STA. This can be unidirectional as well as bidirectional. In our case both AP and STA supports aggregation. AP uses 64 buffers for aggregation (AMPDU) and also supports A-MSDU. And nRF7002 uses 16 buffers for aggregation and does not support AMSDU, which is kind of expected considering its low memory device.

nRF7002 sent ADDBA requesting 64 buffer for its transmission which was accepted by AP

But in when nRF7002 is RX it can only accept upto 16 buffers and no AMSDU which is kind of expected considering the processing and memory capabilities it has.

This completes the handshake between AP and STA and now the data path is opened to Tx or Rx.

Testing the Matter based Light bulb accessory on my Echo show 5

What is matter?

Matter defines an application layer on top of the IPv6-based transport protocols. This allows for routing messages regardless of the underlying physical and link layers.

Without going into much details I will provide link to the documentation that Nordic has provided. You can find them here - https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.2.99-dev3/nrf/ug_matter_overview_architecture.html

How it works?

The IP-based protocol behind Matter isn't replacing existing smart home ecosystems as much as helping them work together. And while Matter's an open-source platform that any device maker can use, it must join the Connectivity Standards Alliance (CSA)—Matter's governing body—and submit products to authorized test labs as part of a certification program.

On the hardware side, Matter works using one or more wireless technologies:

Wi-Fi is available on practically every computer and smartphone, making it a natural choice for wireless communication between Matter devices—and, if necessary, the internet.
Ethernet uses a wired connection and offers many of the same benefits as Wi-Fi.
Thread is a low-power smart home protocol that creates a mesh network between devices—similar to Zigbee. Thread is an ideal choice for battery-powered devices.

Echo Show 5 as Matter controller and a Thread border router

Echo show 5 can act as a Matter controller or a thread border router to help commissioning matter based accessory device. Refer here - https://developer.amazon.com/en-US/docs/alexa/smarthome/matter-support.html#:~:text=Alexa%20supports%20the%20following%20connection,supports%20Matter%20over%20Wi%2DFi.

Matter commissioning flow

The commissioning process supports two potential starting points:

The device is already on the network
The device needs network credentials for Wi-Fi or Thread (requires Bluetooth LE (BLE) support)

Following diagram shows typical flow of Matter based device

Reference - https://docs.silabs.com/matter/1.0.3/matter-overview-guides/commissioning

nRF7002 as matter based light bulb

After able to flash both host and coprocessor, I explored some of the Zephyr's Matter based examples and then modified a little bit to have a Matter based light implemented

You can follow details steps provided here https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/matter/light_bulb/README.html to understand how to buld and flash matter based example applications on nRF7002.

This is how my VS setup look like with Matter application and nordic Dev environment

Once we compile and flash this application code, next step we need to do is commissioning the nRF7002 matter accessory

Showing screenshot on Alexa mobile app which takes you through a step-by-step process

Below is the log showing whole commissioning process happening on nRF7002

uart:~$ *** Booting Zephyr OS build v3.3.99-ncs1 ***
I: Init CHIP stack
I: 254 [DL]BLE address: D5:77:AA:3F:17:7A
D: 292 [DL]WiFiManager has been initialized
I: 297 [SVR]Subscription persistence not supported
I: 301 [SVR]Server initializing...
I: 305 [TS]Last Known Good Time: 2023-07-06T18:52:25
I: 310 [DMG]AccessControl: initializing
I: 314 [DMG]Examples::AccessControlDelegate::Init
I: 318 [DMG]AccessControl: setting
I: 321 [DMG]DefaultAclStorage: initializing
I: 325 [DMG]DefaultAclStorage: 0 entries loaded
D: 330 [IN]UDP::Init bind&listen port=5540
E: 333 [IN]SO_REUSEPORT failed: 109
D: 337 [IN]UDP::Init bound to port=5540
D: 340 [IN]BLEBase::Init - setting/overriding transport
D: 345 [IN]TransportMgr initialized
I: 351 [ZCL]Using ZAP configuration...
I: 357 [DMG]AccessControlCluster: initializing
D: 361 [DL]Boot reason: 1
I: 364 [ZCL]Initiating Admin Commissioning cluster.
I: 369 [ZCL]Endpoint 1 On/off already set to new value
I: 374 [ZCL]Cluster LevelControl: attribute CurrentLevel set to 254
D: 382 [IN]SecureSession[0x200041d0]: Allocated Type:1 LSID:40614
D: 388 [DL]CHIPoBLE advertising set to on
I: 391 [DIS]Updating services using commissioning mode 1
I: 397 [DIS]CHIP minimal mDNS started advertising.
D: 402 [DL]Using wifi MAC for hostname
I: 405 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
D: 415 [DIS]Responding with _matterc._udp.local
D: 419 [DIS]Responding with E09F51D83F119A4B._matterc._udp.local
D: 425 [DIS]Responding with F4CE36001534.local
D: 429 [DIS]Responding with F4CE36001534.local
D: 433 [DIS]Responding with _V65521._sub._matterc._udp.local
D: 439 [DIS]Responding with _S15._sub._matterc._udp.local
D: 444 [DIS]Responding with _L3840._sub._matterc._udp.local
D: 449 [DIS]Responding with _CM._sub._matterc._udp.local
D: 454 [DIS]Responding with E09F51D83F119A4B._matterc._udp.local
I: 460 [DIS]CHIP minimal mDNS configured as 'Commissionable node device'; instance name: E09F51D83F119A4B.
I: 470 [DIS]mDNS service published: _matterc._udp
I: 474 [DIS]Updating services using commissioning mode 1
I: 479 [DIS]CHIP minimal mDNS started advertising.
D: 484 [DL]Using wifi MAC for hostname
I: 488 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=1
D: 497 [DIS]Responding with _matterc._udp.local
D: 501 [DIS]Responding with E09F51D83F119A4B._matterc._udp.local
D: 507 [DIS]Responding with F4CE36001534.local
D: 511 [DIS]Responding with F4CE36001534.local
D: 516 [DIS]Responding with _V65521._sub._matterc._udp.local
D: 521 [DIS]Responding with _S15._sub._matterc._udp.local
D: 526 [DIS]Responding with _L3840._sub._matterc._udp.local
D: 532 [DIS]Responding with _CM._sub._matterc._udp.local
D: 537 [DIS]Responding with E09F51D83F119A4B._matterc._udp.local
I: 543 [DIS]CHIP minimal mDNS configured as 'Commissionable node device'; instance name: E09F51D83F119A4B.
I: 552 [DIS]mDNS service published: _matterc._udp
I: 557 [IN]CASE Server enabling CASE session setups
D: 562 [IN]SecureSession[0x20004288]: Allocated Type:2 LSID:40615
I: 568 [SVR]Joining Multicast groups
I: 571 [SVR]Server Listening...
I: 574 [DL]Device Configuration:
I: 577 [DL] Serial Number: 11223344556677889900
I: 582 [DL] Vendor Id: 65521 (0xFFF1)
I: 585 [DL] Product Id: 32773 (0x8005)
I: 589 [DL] Product Name: not-specified
I: 593 [DL] Hardware Version: 0
I: 596 [DL] Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
I: 602 [DL] Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
I: 608 [DL] Manufacturing Date: (not set)
I: 612 [DL] Device Type: 65535 (0xFFFF)
I: 617 [SVR]SetupQRCode: [MT:6FCJ142C00KA0648G00]
I: 621 [SVR]Copy/paste the below URL in a browser to see the QR Code:
I: 627 [SVR]https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A6FCJ142C00KA0648G00
I: 636 [SVR]Manual pairing code: [34970112332]
I: 646 [DL]CHIP task running
I: 654 [DL]CHIPoBLE advertising started
I: 658 [ZCL]Cluster OnOff: attribute OnOff set to 0
I: 663 [ZCL]Cluster LevelControl: attribute CurrentLevel set to 254
I: 669 [DL]NFC Tag emulation started
I: 23244 [DL]BLE connection established (ConnId: 0x00)
I: 23249 [DL]Current number of connections: 1/1
I: 23254 [DL]CHIPoBLE advertising stopped
I: 23257 [DL]NFC Tag emulation stopped
I: 28294 [DL]BLE GAP connection terminated (reason 0x08)
I: 28299 [DL]Current number of connections: 0/1
I: 28306 [DL]CHIPoBLE advertising started
I: 28311 [DL]NFC Tag emulation started
I: 28688 [DL]BLE connection established (ConnId: 0x00)
I: 28693 [DL]Current number of connections: 1/1
I: 28697 [DL]CHIPoBLE advertising stopped
I: 28701 [DL]NFC Tag emulation stopped
I: 33739 [DL]BLE GAP connection terminated (reason 0x08)
I: 33744 [DL]Current number of connections: 0/1
I: 33751 [DL]CHIPoBLE advertising started
I: 33756 [DL]NFC Tag emulation started
I: 63756 [DL]CHIPoBLE advertising mode changed to slow
I: 63764 [DL]CHIPoBLE advertising started
I: 140835 [DL]BLE connection established (ConnId: 0x00)
I: 140841 [DL]Current number of connections: 1/1
I: 140845 [DL]CHIPoBLE advertising stopped
I: 140849 [DL]NFC Tag emulation stopped
D: 141360 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 141368 [BLE]local and remote recv window sizes = 5
I: 141372 [BLE]selected BTP version 4
I: 141376 [BLE]using BTP fragment sizes rx 244 / tx 244.
D: 141381 [DL]ConnId: 0x00, New CCCD value: 0x0002
D: 141386 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 6)
D: 141393 [IN]BLE EndPoint 0x2000ae58 Connection Complete
I: 141399 [DL]CHIPoBLE connection established (ConnId: 0x00, GATT MTU: 247)
D: 141415 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 141443 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 141451 [EM]>>> [E:57397r S:0 M:21601676] (U) Msg RX from 0:AC59A553400B6C3F [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)
I: 141464 [EM]<<< [E:57397r S:0 M:198592031] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:21 (SecureChannel:PBKDFParamResponse)
I: 141476 [IN](U) Sending msg 198592031 to IP address 'BLE'
D: 141481 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 140)
D: 141511 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 141636 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 141643 [EM]>>> [E:57397r S:0 M:21601677] (U) Msg RX from 0:AC59A553400B6C3F [0000] --- Type 0000:22 (SecureChannel:PASE_Pake1)
I: 143033 [EM]<<< [E:57397r S:0 M:198592032] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:23 (SecureChannel:PASE_Pake2)
I: 143044 [IN](U) Sending msg 198592032 to IP address 'BLE'
D: 143049 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 132)
E: 143057 [DL]Long dispatch time: 1421 ms, for event type 16388
D: 143119 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 143254 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 143262 [EM]>>> [E:57397r S:0 M:21601678] (U) Msg RX from 0:AC59A553400B6C3F [0000] --- Type 0000:24 (SecureChannel:PASE_Pake3)
I: 143274 [EM]<<< [E:57397r S:0 M:198592033] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
I: 143286 [IN](U) Sending msg 198592033 to IP address 'BLE'
D: 143291 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 35)
I: 143299 [SC]SecureSession[0x200041d0]: Moving from state 'kEstablishing' --> 'kActive'
D: 143307 [IN]SecureSession[0x200041d0]: Activated - Type:1 LSID:40614
D: 143314 [IN]New secure session activated for device <FFFFFFFB00000000, 0>, LSID:40614 PSID:34883!
I: 143322 [SVR]Commissioning completed session establishment step
I: 143329 [DIS]Updating services using commissioning mode 0
I: 143334 [DIS]CHIP minimal mDNS started advertising.
D: 143339 [DL]Using wifi MAC for hostname
I: 143343 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=0
D: 143353 [DIS]Responding with _matterc._udp.local
D: 143357 [DIS]Responding with E09F51D83F119A4B._matterc._udp.local
D: 143363 [DIS]Responding with F4CE36001534.local
D: 143368 [DIS]Responding with F4CE36001534.local
D: 143372 [DIS]Responding with _V65521._sub._matterc._udp.local
D: 143378 [DIS]Responding with _S15._sub._matterc._udp.local
D: 143384 [DIS]Responding with _L3840._sub._matterc._udp.local
D: 143390 [DIS]Responding with E09F51D83F119A4B._matterc._udp.local
I: 143396 [DIS]CHIP minimal mDNS configured as 'Commissionable node device'; instance name: E09F51D83F119A4B.
I: 143406 [DIS]mDNS service published: _matterc._udp
D: 143410 [DIS]Scheduling extended discovery timeout in 900s
D: 143416 [DL]CHIPoBLE advertising set to off
I: 143420 [SVR]Device completed Rendezvous process
E: 143424 [DL]Long dispatch time: 170 ms, for event type 16388
D: 143430 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 143479 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 143487 [EM]>>> [E:57398r S:40614 M:176012748] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:0a (IM:TimedRequest)
I: 143499 [EM]<<< [E:57398r S:40614 M:102513059] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:01 (IM:StatusResponse)
I: 143510 [IN](S) Sending msg 102513059 on secure session with LSID: 40614
D: 143517 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 43)
D: 143614 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 143659 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 143667 [EM]>>> [E:57398r S:40614 M:176012749] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 143680 [FS]GeneralCommissioning: Received ArmFailSafe (80s)
I: 143686 [EM]<<< [E:57398r S:40614 M:102513060] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 143698 [IN](S) Sending msg 102513060 on secure session with LSID: 40614
D: 143705 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
D: 143839 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 143929 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 143937 [EM]>>> [E:57399r S:40614 M:176012750] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
D: 143948 [IM]Received Read request
I: 143953 [EM]<<< [E:57399r S:40614 M:102513061] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I: 143964 [IN](S) Sending msg 102513061 on secure session with LSID: 40614
D: 143971 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 72)
D: 144064 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 144199 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 144207 [EM]>>> [E:57400r S:40614 M:176012751] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
D: 144218 [IM]Received Read request
I: 144223 [EM]<<< [E:57400r S:40614 M:102513062] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I: 144234 [IN](S) Sending msg 102513062 on secure session with LSID: 40614
D: 144241 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
D: 144379 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 144514 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 144522 [EM]>>> [E:57401r S:40614 M:176012752] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:02 (IM:ReadRequest)
D: 144533 [IM]Received Read request
I: 144539 [EM]<<< [E:57401r S:40614 M:102513063] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:05 (IM:ReportData)
I: 144550 [IN](S) Sending msg 102513063 on secure session with LSID: 40614
D: 144557 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
D: 144649 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 144829 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 144837 [EM]>>> [E:57402r S:40614 M:176012753] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:0a (IM:TimedRequest)
I: 144849 [EM]<<< [E:57402r S:40614 M:102513064] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:01 (IM:StatusResponse)
I: 144860 [IN](S) Sending msg 102513064 on secure session with LSID: 40614
D: 144867 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 43)
D: 144964 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 144972 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 144980 [EM]>>> [E:57402r S:40614 M:176012754] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 144994 [EM]<<< [E:57402r S:40614 M:102513065] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 145006 [IN](S) Sending msg 102513065 on secure session with LSID: 40614
D: 145013 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
D: 145099 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 145234 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 145242 [EM]>>> [E:57403r S:40614 M:176012755] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:0a (IM:TimedRequest)
I: 145254 [EM]<<< [E:57403r S:40614 M:102513066] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:01 (IM:StatusResponse)
I: 145265 [IN](S) Sending msg 102513066 on secure session with LSID: 40614
D: 145272 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 43)
D: 145369 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 145377 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 145385 [EM]>>> [E:57403r S:40614 M:176012756] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 145397 [ZCL]OpCreds: Certificate Chain request received for DAC
I: 145407 [EM]<<< [E:57403r S:40614 M:102513067] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 145419 [IN](S) Sending msg 102513067 on secure session with LSID: 40614
D: 145425 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
D: 145504 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 145512 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
D: 145594 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 145602 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 77)
D: 145729 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 145864 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 145872 [EM]>>> [E:57404r S:40614 M:176012757] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:0a (IM:TimedRequest)
I: 145884 [EM]<<< [E:57404r S:40614 M:102513068] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:01 (IM:StatusResponse)
I: 145895 [IN](S) Sending msg 102513068 on secure session with LSID: 40614
D: 145902 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 43)
D: 146044 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 146052 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 146060 [EM]>>> [E:57404r S:40614 M:176012758] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 146072 [ZCL]OpCreds: Certificate Chain request received for PAI
I: 146082 [EM]<<< [E:57404r S:40614 M:102513069] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 146093 [IN](S) Sending msg 102513069 on secure session with LSID: 40614
D: 146100 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
D: 146179 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 146187 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
D: 146314 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 146322 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 48)
D: 146449 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 146584 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 146592 [EM]>>> [E:57405r S:40614 M:176012759] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:0a (IM:TimedRequest)
I: 146604 [EM]<<< [E:57405r S:40614 M:102513070] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:01 (IM:StatusResponse)
I: 146615 [IN](S) Sending msg 102513070 on secure session with LSID: 40614
D: 146622 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 43)
D: 146719 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 146765 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 146773 [EM]>>> [E:57405r S:40614 M:176012760] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 146785 [ZCL]OpCreds: Received an AttestationRequest command
I: 146820 [ZCL]OpCreds: AttestationRequest successful.
I: 146829 [EM]<<< [E:57405r S:40614 M:102513071] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 146841 [IN](S) Sending msg 102513071 on secure session with LSID: 40614
D: 146848 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
D: 146944 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 146952 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
D: 147034 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 147042 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 235)
D: 147124 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 147979 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 147987 [EM]>>> [E:57406r S:40614 M:176012761] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:0a (IM:TimedRequest)
I: 147999 [EM]<<< [E:57406r S:40614 M:102513072] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:01 (IM:StatusResponse)
I: 148010 [IN](S) Sending msg 102513072 on secure session with LSID: 40614
D: 148017 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 43)
D: 148114 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 148205 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 148213 [EM]>>> [E:57406r S:40614 M:176012762] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 148225 [ZCL]OpCreds: Received a CSRRequest command
I: 148372 [ZCL]OpCreds: AllocatePendingOperationalKey succeeded
I: 148407 [ZCL]OpCreds: CSRRequest successful.
I: 148413 [EM]<<< [E:57406r S:40614 M:102513073] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 148425 [IN](S) Sending msg 102513073 on secure session with LSID: 40614
D: 148432 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 244)
E: 148440 [DL]Long dispatch time: 236 ms, for event type 16388
D: 148519 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 148527 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 138)
D: 148609 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 149870 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 149878 [EM]>>> [E:57407r S:40614 M:176012763] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:0a (IM:TimedRequest)
I: 149889 [EM]<<< [E:57407r S:40614 M:102513074] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:01 (IM:StatusResponse)
I: 149901 [IN](S) Sending msg 102513074 on secure session with LSID: 40614
D: 149907 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 43)
D: 150004 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 150141 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 150319 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 150329 [EM]>>> [E:57407r S:40614 M:176012764] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 150341 [ZCL]OpCreds: Received an AddTrustedRootCertificate command
I: 150402 [ZCL]OpCreds: AddTrustedRootCertificate successful.
I: 150408 [EM]<<< [E:57407r S:40614 M:102513075] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 150420 [IN](S) Sending msg 102513075 on secure session with LSID: 40614
D: 150427 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 68)
E: 150435 [DL]Long dispatch time: 116 ms, for event type 16388
D: 150499 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 150634 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 150642 [EM]>>> [E:57408r S:40614 M:176012765] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:0a (IM:TimedRequest)
I: 150654 [EM]<<< [E:57408r S:40614 M:102513076] (S) Msg TX to 0:FFFFFFFB00000000 [0000] --- Type 0001:01 (IM:StatusResponse)
I: 150665 [IN](S) Sending msg 102513076 on secure session with LSID: 40614
D: 150672 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 43)
D: 150814 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 150861 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 150906 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 151040 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 151051 [EM]>>> [E:57408r S:40614 M:176012766] (S) Msg RX from 0:FFFFFFFB00000000 [0000] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 151063 [ZCL]OpCreds: Received an AddNOC command
I: 151070 [FP]Validating NOC chain
I: 151183 [FP]NOC chain validation successful
I: 151187 [FP]Added new fabric at index: 0x1
I: 151191 [FP]Assigned compressed fabric ID: 0x84B487F9D11741E5, node ID: 0x01A30FC938AA4630
I: 151199 [TS]Last Known Good Time: 2023-07-06T18:52:25
I: 151204 [TS]New proposed Last Known Good Time: 2023-07-23T10:52:41
I: 151211 [TS]Updating pending Last Known Good Time to 2023-07-23T10:52:41
I: 151225 [ZCL]OpCreds: ACL entry created for Fabric index 0x1 CASE Admin Subject 0xFFFFFFFD0011002A
D: 151234 [DL]Using wifi MAC for hostname
I: 151238 [DIS]Advertise operational node 84B487F9D11741E5-01A30FC938AA4630
D: 151245 [DIS]Responding with _matter._tcp.local
D: 151249 [DIS]Responding with 84B487F9D11741E5-01A30FC938AA4630._matter._tcp.local
D: 151257 [DIS]Responding with 84B487F9D11741E5-01A30FC938AA4630._matter._tcp.local
D: 151264 [DIS]Responding with F4CE36001534.local
D: 151269 [DIS]Responding with F4CE36001534.local
D: 151273 [DIS]Responding with _I84B487F9D11741E5._sub._matter._tcp.local
I: 151280 [DIS]CHIP minimal mDNS configured as 'Operational device'; instance name: 84B487F9D11741E5-01A30FC938AA4630.
I: 151290 [DIS]mDNS service published: _matter._tcp
I: 151295 [ZCL]OpCreds: successfully created fabric index 0x1 via AddNOC
I: 151302 [EM]<<< [E:57408r S:40614 M:102513077] (S) Msg TX to 1:FFFFFFFB00000000 [41E5] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 151314 [IN](S) Sending msg 102513077 on secure session with LSID: 40614
D: 151321 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
E: 151329 [DL]Long dispatch time: 288 ms, for event type 16388
D: 151399 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 151534 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 151542 [EM]>>> [E:57409r S:40614 M:176012767] (S) Msg RX from 1:FFFFFFFB00000000 [41E5] --- Type 0001:0a (IM:TimedRequest)
I: 151554 [EM]<<< [E:57409r S:40614 M:102513078] (S) Msg TX to 1:FFFFFFFB00000000 [41E5] --- Type 0001:01 (IM:StatusResponse)
I: 151565 [IN](S) Sending msg 102513078 on secure session with LSID: 40614
D: 151572 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 43)
D: 151669 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 151714 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 151723 [EM]>>> [E:57409r S:40614 M:176012768] (S) Msg RX from 1:FFFFFFFB00000000 [41E5] --- Type 0001:08 (IM:InvokeCommandRequest)
D: 151737 [DL]WiFi scanning started...
D: 154222 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 154279 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
I: 156459 [DL]Wi-Fi scan done (0)
I: 156464 [EM]<<< [E:57409r S:40614 M:102513079] (S) Msg TX to 1:FFFFFFFB00000000 [41E5] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 156476 [IN](S) Sending msg 102513079 on secure session with LSID: 40614
D: 156482 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 217)
D: 156619 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 156754 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 156762 [EM]>>> [E:57410r S:40614 M:176012769] (S) Msg RX from 1:FFFFFFFB00000000 [41E5] --- Type 0001:0a (IM:TimedRequest)
I: 156774 [EM]<<< [E:57410r S:40614 M:102513080] (S) Msg TX to 1:FFFFFFFB00000000 [41E5] --- Type 0001:01 (IM:StatusResponse)
I: 156785 [IN](S) Sending msg 102513080 on secure session with LSID: 40614
D: 156792 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 43)
D: 156889 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 156897 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 156905 [EM]>>> [E:57410r S:40614 M:176012770] (S) Msg RX from 1:FFFFFFFB00000000 [41E5] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 156918 [FS]GeneralCommissioning: Received ArmFailSafe (300s)
I: 156924 [EM]<<< [E:57410r S:40614 M:102513081] (S) Msg TX to 1:FFFFFFFB00000000 [41E5] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 156936 [IN](S) Sending msg 102513081 on secure session with LSID: 40614
D: 156943 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
D: 157024 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 157519 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 157527 [EM]>>> [E:57411r S:40614 M:176012771] (S) Msg RX from 1:FFFFFFFB00000000 [41E5] --- Type 0001:0a (IM:TimedRequest)
I: 157539 [EM]<<< [E:57411r S:40614 M:102513082] (S) Msg TX to 1:FFFFFFFB00000000 [41E5] --- Type 0001:01 (IM:StatusResponse)
I: 157550 [IN](S) Sending msg 102513082 on secure session with LSID: 40614
D: 157557 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 43)
D: 157654 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 157662 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 157671 [EM]>>> [E:57411r S:40614 M:176012772] (S) Msg RX from 1:FFFFFFFB00000000 [41E5] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 157684 [EM]<<< [E:57411r S:40614 M:102513083] (S) Msg TX to 1:FFFFFFFB00000000 [41E5] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 157696 [IN](S) Sending msg 102513083 on secure session with LSID: 40614
D: 157702 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 71)
D: 157789 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 157879 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 157887 [EM]>>> [E:57412r S:40614 M:176012773] (S) Msg RX from 1:FFFFFFFB00000000 [41E5] --- Type 0001:0a (IM:TimedRequest)
I: 157899 [EM]<<< [E:57412r S:40614 M:102513084] (S) Msg TX to 1:FFFFFFFB00000000 [41E5] --- Type 0001:01 (IM:StatusResponse)
I: 157910 [IN](S) Sending msg 102513084 on secure session with LSID: 40614
D: 157917 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 43)
D: 158014 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 158022 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
I: 158030 [EM]>>> [E:57412r S:40614 M:176012774] (S) Msg RX from 1:FFFFFFFB00000000 [41E5] --- Type 0001:08 (IM:InvokeCommandRequest)
D: 158043 [DL]Connecting to WiFi network: mywifi6
D: 158049 [DL]WiFi scanning started...
D: 160529 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 160624 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
I: 162689 [DL]Wi-Fi scan done (0)
I: 164260 [DL]Connection to mywifi6 requested [RSSI=-33]
E: 164265 [DL]Long dispatch time: 1576 ms, for event type 3
D: 164270 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 166778 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 166879 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
I: 168550 [DL]Connected to WiFi network
I: 168554 [EM]<<< [E:57412r S:40614 M:102513085] (S) Msg TX to 1:FFFFFFFB00000000 [41E5] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 168566 [IN](S) Sending msg 102513085 on secure session with LSID: 40614
D: 168573 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 69)
D: 168580 [DL]Using wifi MAC for hostname
I: 168584 [DIS]Advertise operational node 84B487F9D11741E5-01A30FC938AA4630
D: 168591 [DIS]Responding with _matter._tcp.local
D: 168596 [DIS]Responding with 84B487F9D11741E5-01A30FC938AA4630._matter._tcp.local
D: 168604 [DIS]Responding with 84B487F9D11741E5-01A30FC938AA4630._matter._tcp.local
D: 168612 [DIS]Responding with F4CE36001534.local
D: 168617 [DIS]Responding with F4CE36001534.local
D: 168621 [DIS]Responding with _I84B487F9D11741E5._sub._matter._tcp.local
I: 168629 [DIS]CHIP minimal mDNS configured as 'Operational device'; instance name: 84B487F9D11741E5-01A30FC938AA4630.
I: 168640 [DIS]mDNS service published: _matter._tcp
I: 168645 [SVR]Operational advertising enabled
I: 168651 [SWU]Stopping the watchdog timer
I: 168655 [SWU]Starting the periodic query timer, timeout: 86400 seconds
E: 168661 [SVR]Server initialization complete
I: 168665 [DIS]Updating services using commissioning mode 0
E: 168671 [IN]SO_REUSEPORT failed: 109
I: 168676 [DIS]CHIP minimal mDNS started advertising.
D: 168716 [DL]Using wifi MAC for hostname
I: 168720 [DIS]Advertise operational node 84B487F9D11741E5-01A30FC938AA4630
D: 168727 [DIS]Responding with _matter._tcp.local
D: 168735 [DIS]Responding with 84B487F9D11741E5-01A30FC938AA4630._matter._tcp.local
D: 168744 [DIS]Responding with 84B487F9D11741E5-01A30FC938AA4630._matter._tcp.local
D: 168752 [DIS]Responding with F4CE36001534.local
D: 168756 [DIS]Responding with F4CE36001534.local
D: 168761 [DIS]Responding with _I84B487F9D11741E5._sub._matter._tcp.local
I: 168767 [DIS]CHIP minimal mDNS configured as 'Operational device'; instance name: 84B487F9D11741E5-01A30FC938AA4630.
I: 168782 [DIS]mDNS service published: _matter._tcp
D: 168788 [DL]Using wifi MAC for hostname
I: 168792 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=0
D: 168801 [DIS]Responding with _matterc._udp.local
D: 168806 [DIS]Responding with E09F51D83F119A4B._matterc._udp.local
D: 168812 [DIS]Responding with F4CE36001534.local
D: 168816 [DIS]Responding with F4CE36001534.local
D: 168821 [DIS]Responding with _V65521._sub._matterc._udp.local
D: 168827 [DIS]Responding with _S15._sub._matterc._udp.local
D: 168835 [DIS]Responding with _L3840._sub._matterc._udp.local
D: 168841 [DIS]Responding with E09F51D83F119A4B._matterc._udp.local
I: 168847 [DIS]CHIP minimal mDNS configured as 'Commissionable node device'; instance name: E09F51D83F119A4B.
I: 168873 [DIS]mDNS service published: _matterc._udp
E: 168879 [DL]Long dispatch time: 218 ms, for event type 32784
D: 168884 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
I: 168892 [DIS]Updating services using commissioning mode 0
E: 168898 [IN]SO_REUSEPORT failed: 109
I: 168901 [DIS]CHIP minimal mDNS started advertising.
D: 168947 [DL]Using wifi MAC for hostname
I: 168953 [DIS]Advertise operational node 84B487F9D11741E5-01A30FC938AA4630
D: 168960 [DIS]Responding with _matter._tcp.local
D: 168965 [DIS]Responding with 84B487F9D11741E5-01A30FC938AA4630._matter._tcp.local
D: 168972 [DIS]Responding with 84B487F9D11741E5-01A30FC938AA4630._matter._tcp.local
D: 168980 [DIS]Responding with F4CE36001534.local
D: 168984 [DIS]Responding with F4CE36001534.local
D: 168989 [DIS]Responding with _I84B487F9D11741E5._sub._matter._tcp.local
I: 168995 [DIS]CHIP minimal mDNS configured as 'Operational device'; instance name: 84B487F9D11741E5-01A30FC938AA4630.
I: 169010 [DIS]mDNS service published: _matter._tcp
D: 169017 [DL]Using wifi MAC for hostname
I: 169022 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=0
D: 169031 [DIS]Responding with _matterc._udp.local
D: 169037 [DIS]Responding with E09F51D83F119A4B._matterc._udp.local
D: 169043 [DIS]Responding with F4CE36001534.local
D: 169047 [DIS]Responding with F4CE36001534.local
D: 169052 [DIS]Responding with _V65521._sub._matterc._udp.local
D: 169058 [DIS]Responding with _S15._sub._matterc._udp.local
D: 169063 [DIS]Responding with _L3840._sub._matterc._udp.local
D: 169069 [DIS]Responding with E09F51D83F119A4B._matterc._udp.local
I: 169075 [DIS]CHIP minimal mDNS configured as 'Commissionable node device'; instance name: E09F51D83F119A4B.
I: 169101 [DIS]mDNS service published: _matterc._udp
E: 169109 [DL]Long dispatch time: 215 ms, for event type 32784
D: 169309 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 171817 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 171874 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
I: 173979 [EM]>>> [E:57413r S:0 M:21601679] (U) Msg RX from 0:A4B8019CBA93A83C [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
I: 173990 [IN]CASE Server received Sigma1 message . Starting handshake. EC 0x20005b90
I: 173998 [IN]CASE Server disabling CASE session setups
I: 174003 [EM]<<< [E:57413r S:0 M:198592034 (Ack:21601679)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 174016 [IN](U) Sending msg 198592034 to IP address 'UDP:[fe80::1209:f9ff:fe19:54c9]:5541'
I: 174025 [SC]Received Sigma1 msg
I: 174032 [SC]CASE matched destination ID: fabricIndex 1, NodeID 0x01A30FC938AA4630
I: 174216 [EM]<<< [E:57413r S:0 M:198592035 (Ack:21601679)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:31 (SecureChannel:CASE_Sigma2)
I: 174228 [IN](U) Sending msg 198592035 to IP address 'UDP:[fe80::1209:f9ff:fe19:54c9]:5541'
I: 174238 [SC]Sent Sigma2 msg
I: 174244 [EM]>>> [E:57413r S:0 M:21601680 (Ack:198592035)] (U) Msg RX from 0:A4B8019CBA93A83C [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 174490 [EM]>>> [E:57413r S:0 M:21601681 (Ack:198592035)] (U) Msg RX from 0:A4B8019CBA93A83C [0000] --- Type 0000:32 (SecureChannel:CASE_Sigma3)
I: 174503 [EM]<<< [E:57413r S:0 M:198592036 (Ack:21601681)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 174516 [IN](U) Sending msg 198592036 to IP address 'UDP:[fe80::1209:f9ff:fe19:54c9]:5541'
I: 174525 [SC]Received Sigma3 msg
E: 174534 [SC]The device does not support GetClock_RealTimeMS() API: 3. Falling back to Last Known Good UTC Time
D: 174544 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
E: 174717 [DL]Long dispatch time: 166 ms, for event type 2
I: 174728 [EM]<<< [E:57413r S:0 M:198592037 (Ack:21601681)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:40 (SecureChannel:StatusReport)
I: 174741 [IN](U) Sending msg 198592037 to IP address 'UDP:[fe80::1209:f9ff:fe19:54c9]:5541'
I: 174752 [SC]SecureSession[0x20004288]: Moving from state 'kEstablishing' --> 'kActive'
D: 174760 [IN]SecureSession[0x20004288]: Activated - Type:2 LSID:40615
D: 174766 [IN]New secure session activated for device <018D35CA746E8D51, 1>, LSID:40615 PSID:34884!
I: 174780 [IN]CASE Session established to peer: <018D35CA746E8D51, 1>
I: 174786 [IN]CASE Server enabling CASE session setups
D: 174792 [IN]SecureSession[0x20004340]: Allocated Type:2 LSID:40616
I: 174799 [EM]>>> [E:57414r S:40615 M:235692712] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:02 (IM:ReadRequest)
D: 174810 [IM]Received Read request
I: 174815 [EM]<<< [E:57414r S:40615 M:149881592 (Ack:235692712)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 174827 [IN](S) Sending msg 149881592 on secure session with LSID: 40615
I: 174836 [EM]>>> [E:57413r S:0 M:21601682 (Ack:198592037)] (U) Msg RX from 0:A4B8019CBA93A83C [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 174852 [EM]>>> [E:57414r S:40615 M:235692713 (Ack:149881592)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 174950 [EM]>>> [E:57415r S:40615 M:235692714] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:02 (IM:ReadRequest)
D: 174961 [IM]Received Read request
I: 174966 [EM]<<< [E:57415r S:40615 M:149881593 (Ack:235692714)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 174979 [IN](S) Sending msg 149881593 on secure session with LSID: 40615
I: 174995 [EM]>>> [E:57415r S:40615 M:235692715 (Ack:149881593)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 175098 [EM]>>> [E:57416r S:40615 M:235692716] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:06 (IM:WriteRequest)
D: 175109 [IM]Received Write request
I: 175117 [EM]<<< [E:57416r S:40615 M:149881594 (Ack:235692716)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:07 (IM:WriteResponse)
I: 175130 [IN](S) Sending msg 149881594 on secure session with LSID: 40615
I: 175146 [EM]>>> [E:57416r S:40615 M:235692717 (Ack:149881594)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 175248 [EM]>>> [E:57417r S:40615 M:235692718] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:02 (IM:ReadRequest)
D: 175259 [IM]Received Read request
I: 175264 [EM]<<< [E:57417r S:40615 M:149881595 (Ack:235692718)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 175276 [IN](S) Sending msg 149881595 on secure session with LSID: 40615
I: 175344 [EM]>>> [E:57417r S:40615 M:235692719 (Ack:149881595)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 175403 [EM]>>> [E:57418r S:40615 M:235692720] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:0a (IM:TimedRequest)
I: 175415 [EM]<<< [E:57418r S:40615 M:149881596 (Ack:235692720)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:01 (IM:StatusResponse)
I: 175428 [IN](S) Sending msg 149881596 on secure session with LSID: 40615
I: 175477 [EM]>>> [E:57418r S:40615 M:235692721 (Ack:149881596)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 175492 [FS]GeneralCommissioning: Received CommissioningComplete
I: 175500 [FP]Metadata for Fabric 0x1 persisted to storage.
I: 175519 [TS]Committing Last Known Good Time to storage: 2023-07-23T10:52:41
I: 175528 [ZCL]OpCreds: Fabric index 0x1 was committed to storage. Compressed Fabric Id 0x84B487F9D11741E5, FabricId 018D35C9FCF3BFE2, NodeId 01A30FC938AA4630, VendorId 0x1217
I: 175544 [FS]GeneralCommissioning: Successfully commited pending fabric data
I: 175551 [FS]Fail-safe cleanly disarmed
I: 175556 [EM]<<< [E:57418r S:40615 M:149881597 (Ack:235692721)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 175569 [IN](S) Sending msg 149881597 on secure session with LSID: 40615
I: 175577 [SWU]Device commissioned, schedule a default provider query
I: 175584 [SVR]Commissioning completed successfully
I: 175588 [DIS]Updating services using commissioning mode 0
E: 175598 [IN]SO_REUSEPORT failed: 109
I: 175601 [DIS]CHIP minimal mDNS started advertising.
D: 175641 [DL]Using wifi MAC for hostname
I: 175645 [DIS]Advertise operational node 84B487F9D11741E5-01A30FC938AA4630
D: 175652 [DIS]Responding with _matter._tcp.local
D: 175657 [DIS]Responding with 84B487F9D11741E5-01A30FC938AA4630._matter._tcp.local
D: 175664 [DIS]Responding with 84B487F9D11741E5-01A30FC938AA4630._matter._tcp.local
D: 175672 [DIS]Responding with F4CE36001534.local
D: 175676 [DIS]Responding with F4CE36001534.local
D: 175681 [DIS]Responding with _I84B487F9D11741E5._sub._matter._tcp.local
I: 175687 [DIS]CHIP minimal mDNS configured as 'Operational device'; instance name: 84B487F9D11741E5-01A30FC938AA4630.
I: 175711 [DIS]mDNS service published: _matter._tcp
D: 175716 [DL]Using wifi MAC for hostname
I: 175720 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=0
D: 175730 [DIS]Responding with _matterc._udp.local
D: 175734 [DIS]Responding with E09F51D83F119A4B._matterc._udp.local
D: 175740 [DIS]Responding with F4CE36001534.local
D: 175745 [DIS]Responding with F4CE36001534.local
D: 175749 [DIS]Responding with _V65521._sub._matterc._udp.local
D: 175755 [DIS]Responding with _S15._sub._matterc._udp.local
D: 175761 [DIS]Responding with _L3840._sub._matterc._udp.local
D: 175766 [DIS]Responding with E09F51D83F119A4B._matterc._udp.local
I: 175772 [DIS]CHIP minimal mDNS configured as 'Commissionable node device'; instance name: E09F51D83F119A4B.
I: 175802 [DIS]mDNS service published: _matterc._udp
D: 175807 [IN]Expiring all PASE sessions
D: 175811 [IN]SecureSession[0x200041d0]: MarkForEviction Type:1 LSID:40614
I: 175818 [SC]SecureSession[0x200041d0]: Moving from state 'kActive' --> 'kPendingEviction'
D: 175826 [IN]SecureSession[0x200041d0]: Released - Type:1 LSID:40614
D: 175832 [IN]Clearing BLE pending packets.
I: 175836 [BLE]Releasing end point's BLE connection back to application.
I: 175842 [DL]Closing BLE GATT connection (ConnId 00)
E: 175850 [DL]Long dispatch time: 273 ms, for event type 32781
I: 175856 [EM]>>> [E:57418r S:40615 M:235692722 (Ack:149881597)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 175871 [EM]>>> [E:57419r S:40615 M:235692723] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:02 (IM:ReadRequest)
D: 175882 [IM]Received Read request
I: 175887 [EM]<<< [E:57419r S:40615 M:149881598 (Ack:235692723)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 175902 [IN](S) Sending msg 149881598 on secure session with LSID: 40615
I: 175924 [DL]BLE GAP connection terminated (reason 0x16)
I: 175929 [DL]Current number of connections: 0/1
I: 175997 [EM]>>> [E:57419r S:40615 M:235692724 (Ack:149881598)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 176022 [EM]>>> [E:57420r S:40615 M:235692725] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:02 (IM:ReadRequest)
D: 176033 [IM]Received Read request
I: 176038 [EM]<<< [E:57420r S:40615 M:149881599 (Ack:235692725)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 176050 [IN](S) Sending msg 149881599 on secure session with LSID: 40615
I: 176072 [EM]>>> [E:57420r S:40615 M:235692726 (Ack:149881599)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 176175 [EM]>>> [E:57421r S:40615 M:235692727] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:02 (IM:ReadRequest)
D: 176186 [IM]Received Read request
I: 176191 [EM]<<< [E:57421r S:40615 M:149881600 (Ack:235692727)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 176203 [IN](S) Sending msg 149881600 on secure session with LSID: 40615
I: 176221 [EM]>>> [E:57421r S:40615 M:235692728 (Ack:149881600)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 176322 [EM]>>> [E:57422r S:40615 M:235692729] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:02 (IM:ReadRequest)
D: 176333 [IM]Received Read request
I: 176338 [EM]<<< [E:57422r S:40615 M:149881601 (Ack:235692729)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 176350 [IN](S) Sending msg 149881601 on secure session with LSID: 40615
I: 176369 [EM]>>> [E:57422r S:40615 M:235692730 (Ack:149881601)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 176468 [EM]>>> [E:57423r S:40615 M:235692731] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:02 (IM:ReadRequest)
D: 176479 [IM]Received Read request
I: 176485 [EM]<<< [E:57423r S:40615 M:149881602 (Ack:235692731)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 176497 [IN](S) Sending msg 149881602 on secure session with LSID: 40615
I: 176513 [EM]>>> [E:57423r S:40615 M:235692732 (Ack:149881602)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 176615 [EM]>>> [E:57424r S:40615 M:235692733] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:02 (IM:ReadRequest)
D: 176626 [IM]Received Read request
I: 176631 [EM]<<< [E:57424r S:40615 M:149881603 (Ack:235692733)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 176644 [IN](S) Sending msg 149881603 on secure session with LSID: 40615
I: 176666 [EM]>>> [E:57424r S:40615 M:235692734 (Ack:149881603)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 176765 [EM]>>> [E:57425r S:40615 M:235692735] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:02 (IM:ReadRequest)
D: 176776 [IM]Received Read request
I: 176781 [EM]<<< [E:57425r S:40615 M:149881604 (Ack:235692735)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 176793 [IN](S) Sending msg 149881604 on secure session with LSID: 40615
I: 176812 [EM]>>> [E:57425r S:40615 M:235692736 (Ack:149881604)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 176912 [EM]>>> [E:57426r S:40615 M:235692737] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:02 (IM:ReadRequest)
D: 176924 [IM]Received Read request
I: 176929 [EM]<<< [E:57426r S:40615 M:149881605 (Ack:235692737)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 176941 [IN](S) Sending msg 149881605 on secure session with LSID: 40615
I: 176961 [EM]>>> [E:57426r S:40615 M:235692738 (Ack:149881605)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 177062 [EM]>>> [E:57427r S:40615 M:235692739] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:02 (IM:ReadRequest)
D: 177073 [IM]Received Read request
I: 177078 [EM]<<< [E:57427r S:40615 M:149881606 (Ack:235692739)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 177091 [IN](S) Sending msg 149881606 on secure session with LSID: 40615
I: 177108 [EM]>>> [E:57427r S:40615 M:235692740 (Ack:149881606)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 179558 [EM]>>> [E:57428r S:40615 M:235692741] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:06 (IM:WriteRequest)
D: 179569 [IM]Received Write request
I: 179575 [EM]<<< [E:57428r S:40615 M:149881607 (Ack:235692741)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:07 (IM:WriteResponse)
I: 179589 [IN](S) Sending msg 149881607 on secure session with LSID: 40615
I: 179605 [EM]>>> [E:57428r S:40615 M:235692742 (Ack:149881607)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 180253 [EM]>>> [E:57429r S:40615 M:235692743] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:03 (IM:SubscribeRequest)
D: 180265 [IM]Received Subscribe request
I: 180269 [DMG]Final negotiated min/max parameters: Min = 1s, Max = 300s
E: 180279 [DMG]Error retrieving data from clusterId: 0x0000_0008, err = b
I: 180291 [EM]<<< [E:57429r S:40615 M:149881608 (Ack:235692743)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 180305 [IN](S) Sending msg 149881608 on secure session with LSID: 40615
I: 180345 [EM]>>> [E:57429r S:40615 M:235692744 (Ack:149881608)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:01 (IM:StatusResponse)
I: 180358 [IM]Received status response, status is 0x00
I: 180367 [EM]<<< [E:57429r S:40615 M:149881609 (Ack:235692744)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:05 (IM:ReportData)
I: 180380 [IN](S) Sending msg 149881609 on secure session with LSID: 40615
I: 180407 [EM]>>> [E:57429r S:40615 M:235692745 (Ack:149881609)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:01 (IM:StatusResponse)
I: 180420 [IM]Received status response, status is 0x00
I: 180425 [DMG]Refresh Subscribe Sync Timer with min 1 seconds and max 300 seconds
I: 180433 [EM]<<< [E:57429r S:40615 M:149881610 (Ack:235692745)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:04 (IM:SubscribeResponse)
I: 180446 [IN](S) Sending msg 149881610 on secure session with LSID: 40615
I: 180464 [EM]>>> [E:57429r S:40615 M:235692746 (Ack:149881610)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 187478 [EM]>>> [E:57430r S:40615 M:235692747] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:0a (IM:TimedRequest)
I: 187490 [EM]<<< [E:57430r S:40615 M:149881611 (Ack:235692747)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:01 (IM:StatusResponse)
I: 187502 [IN](S) Sending msg 149881611 on secure session with LSID: 40615
I: 187520 [EM]>>> [E:57430r S:40615 M:235692748 (Ack:149881611)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 187534 [SWU]OTA Requestor received AnnounceOTAProvider
D: 187539 [SWU] FabricIndex: 1
D: 187542 [SWU] ProviderNodeID: 0x018D35CA746E8D51
D: 187547 [SWU] VendorID: 0xfff1
D: 187550 [SWU] AnnouncementReason: 0
D: 187553 [SWU] MetadataForNode: 0
D: 187557 [SWU] Endpoint: 1
I: 187560 [EM]<<< [E:57430r S:40615 M:149881612 (Ack:235692748)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 187575 [IN](S) Sending msg 149881612 on secure session with LSID: 40615
I: 187584 [SWU]Stopping the Periodic Query timer
I: 187588 [SWU]Starting the watchdog timer, timeout: 21600 seconds
D: 187597 [SWU]Establishing session to provider node ID 0x018D35CA746E8D51 on fabric index 1
I: 187605 [DIS]Found an existing secure session to [1:018D35CA746E8D51]!
D: 187612 [DIS]OperationalSessionSetup[1:018D35CA746E8D51]: State change 1 --> 5
I: 187621 [EM]<<< [E:46032i S:40615 M:149881613] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0001:08 (IM:InvokeCommandRequest)
I: 187633 [IN](S) Sending msg 149881613 on secure session with LSID: 40615
I: 187642 [EM]>>> [E:57430r S:40615 M:235692749 (Ack:149881612)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 187989 [IN](S) Sending msg 149881613 on secure session with LSID: 40615
I: 188384 [IN](S) Sending msg 149881613 on secure session with LSID: 40615
I: 189029 [IN](S) Sending msg 149881613 on secure session with LSID: 40615
I: 189963 [IN](S) Sending msg 149881613 on secure session with LSID: 40615
E: 191387 [EM]Failed to Send CHIP MessageCounter:149881613 on exchange 46032i sendCount: 4 max retries: 4
I: 192661 [EM]>>> [E:46032i S:40615 M:235692750 (Ack:149881613)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 192675 [DMG]Received Command Response Data, Endpoint=1 Cluster=0x0000_0029 Command=0x0000_0001
D: 192684 [SWU]QueryImageResponse:
D: 192687 [SWU] status: 1
D: 192689 [SWU] delayedActionTime: 0 seconds
D: 192695 [SWU] userConsentNeeded: 1
D: 192698 [SWU] metadataForRequestor: 0
I: 192702 [SWU]Scheduling a retry; delay: 120
I: 192707 [EM]<<< [E:46032i S:40615 M:149881614 (Ack:235692750)] (S) Msg TX to 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
I: 192720 [IN](S) Sending msg 149881614 on secure session with LSID: 40615
I: 192730 [EM]>>> [E:46032i S:40615 M:235692751 (Ack:149881613)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
E: 192743 [EM]OnMessageReceived failed, err = 70
I: 192748 [EM]>>> [E:46032i S:40615 M:235692752 (Ack:149881613)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
E: 192762 [EM]OnMessageReceived failed, err = 70
I: 192767 [EM]>>> [E:46032i S:40615 M:235692753 (Ack:149881613)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
E: 192781 [EM]OnMessageReceived failed, err = 70
I: 192786 [EM]>>> [E:46032i S:40615 M:235692754 (Ack:149881613)] (S) Msg RX from 1:018D35CA746E8D51 [41E5] --- Type 0000:10 (SecureChannel:StandaloneAck)
E: 192801 [EM]OnMessageReceived failed, err = 70

Demo video

This is a matter based light which is added to Alexa, and now it can be controlled through my Echo Show and Alexa mobile.

Conclusion

As technology surges forward, WiFi 6 and Matter accessories stand at the forefront of innovation, reshaping the way we interact with our devices and homes. WiFi 6 brings faster speeds, better capacity, and increased efficiency, while Matter creates a unified and secure smart home ecosystem. nRF7002 has great set of documentation, tools, examples, hardware support that helped me to build a matter based accessory within no time. I highly recommend this to those who are new to this wireless connectivity world.

ss_shrenik over 1 year ago in reply to Fred27

Did you update network co-processor image binary in your case?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Fred27 over 1 year ago

I nice road test. I'm not sure how you ended up with access protection problems though. Mine flashed just fine.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel