• State Not Answered
  • Replies 5 replies
  • Subscribers 75 subscribers
  • Views 111 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 344942
Options

Matter CASE resumption delayed 10+ minutes on nRF52840 due to BLE-first serial fabric fallback

brobin88

Hi everyone,

I'm developing a matter generic switch and I’ve run into a puzzling behavior when commissioning an nRF52840 DK with Apple Home via an Apple TV Thread border router. After the switch reboots, it takes over ten minutes before the device finally becomes responsive again. By contrast, a similar Silicon Labs EFR32MG24 demo re-establishes secure channels in under a minute.  I got ChatGPT to compare the serial output of the EFR32MG24 and NRF52840 and here is the summary of what it thinks the issue is:

1. Two Fabrics in Apple Home Commissioning

When you commission with Apple HomeKit (Matter), you actually end up with two fabrics on your accessory:

  1. iOS Fabric (Fabric 0)

    • Established via Matter-over-BLE (CHIPoBLE) when your iPhone pairs and commissions the device.

    • Allows your phone to issue commands, OTA updates, diagnostics, etc., over BLE.

  2. Apple TV Fabric (Fabric 1)

    • Established via Thread when the Apple TV (or HomePod mini) acts as a Thread border router.

    • Provides full home-wide connectivity and lets the TV/hub control the device over the mesh.

Each fabric gets its own CASE session keys and ACLs, so your accessory must securely handshake with both controllers.

2. What the nRF52840 Demo Does (Wrong)

On reboot, the nRF52840 sample app:

  1. Disables BLE advertising immediately (assumes “production” Thread-only mode once commissioned).

  2. Calls Resuming 2 subscriptions in 0 seconds:

    • First it tries the iOS/BLE fabric → fails to connect (no BLE adv!) → times out with error 32.

    • Only after exhausting the BLE back-off (minutes!) does it try the Thread fabric → succeeds.

This serial fallback (BLE → fail → Thread) blocks your accessory for the entire BLE timeout before Thread CASE can even begin.

3. How the EFR32MG24 Demo Does It (Right)

The Silicon Labs demo on the same network:

  • Keeps BLE advertising enabled for a window on boot, and immediately advertises over Thread once SRP is ready.

  • This effectively rings both iOS (BLE) and Apple TV (Thread) controllers in parallel, so whichever controller responds first wins the race.

  • As a result, CASE Sigma1 arrives in seconds, not minutes.

ChatGPT suggests turning on bluetooth extended advertising to ensure bluetooth is enabled to advertise to fabric 0 (iOS) but those settings are enabled by default in the matter template project. 

Any suggestions on what might fix this?

Parents Reply Children
  • 0 in reply to Simonr

    It definitely was working for a while in v2.9.1 of the SDK. If you have a look at my other ticket here:

    https://devzone.nordicsemi.com/f/nordic-q-a/120060/matter-generic-switch-not-working-on-reset

    Turning on persistent subscriptions did work for a while (sadly I didn't capture the logs) but then suddenly it wasn't working. Then I found some guidance on the Silicon Labs forum that said to restart the Apple TV, which again worked for a while and then wasn't working. Now nothing seems to make a difference.

    My Code is quite small so I'll put it in below:

    app_task.cpp

    #include "app_task.h"

#include "app/matter_init.h"
#include "app/task_executor.h"
#include "board/board.h"
#include "lib/core/CHIPError.h"
#include "lib/support/CodeUtils.h"


#include <setup_payload/OnboardingCodesUtil.h>
#include <app/clusters/identify-server/identify-server.h>
#include <app/clusters/switch-server/switch-server.h>
#include <app-common/zap-generated/attributes/Accessors.h>

#include <zephyr/logging/log.h>

LOG_MODULE_DECLARE(app, CONFIG_CHIP_APP_LOG_LEVEL);

using namespace ::chip;
using namespace ::chip::app;
using namespace ::chip::DeviceLayer;

namespace 
{
constexpr EndpointId kSwitchEndpointId = 1;
constexpr EndpointId kSwitchEndpointId2 = 2;

Identify sIdentify = { kSwitchEndpointId, AppTask::IdentifyStartHandler, AppTask::IdentifyStopHandler,
		Clusters::Identify::IdentifyTypeEnum::kVisibleIndicator };


#define SWITCH_BUTTON_1 DK_BTN2_MSK
#define SWITCH_BUTTON_2 DK_BTN4_MSK

}

void AppTask::IdentifyStartHandler(Identify *)
{
	Nrf::PostTask(
		[] { Nrf::GetBoard().GetLED(Nrf::DeviceLeds::LED2).Blink(Nrf::LedConsts::kIdentifyBlinkRate_ms); });
}

void AppTask::IdentifyStopHandler(Identify *)
{
	Nrf::PostTask([] { Nrf::GetBoard().GetLED(Nrf::DeviceLeds::LED2).Set(false); });
}

void AppTask::ButtonEventHandler(Nrf::ButtonState state, Nrf::ButtonMask hasChanged)
{
	uint8_t currentPosition = 1;
    // Check if the application button (e.g., DK_BTN2) has been released.
    // The button is considered released when its bit is cleared in the current state.
    if ((SWITCH_BUTTON_1 & hasChanged) && !(state & SWITCH_BUTTON_1))
    {
		DeviceLayer::SystemLayer().ScheduleLambda([currentPosition] {
			Clusters::Switch::Attributes::CurrentPosition::Set(kSwitchEndpointId, currentPosition);
			Clusters::SwitchServer::Instance().OnInitialPress(kSwitchEndpointId, currentPosition);
		}); 
    }

    if ((SWITCH_BUTTON_2 & hasChanged) && !(state & SWITCH_BUTTON_2))
    {
		DeviceLayer::SystemLayer().ScheduleLambda([currentPosition] {
			Clusters::Switch::Attributes::CurrentPosition::Set(kSwitchEndpointId2, currentPosition);
			Clusters::SwitchServer::Instance().OnInitialPress(kSwitchEndpointId2, currentPosition);
		}); 
    }
}

CHIP_ERROR AppTask::Init()
{
	/* Initialize Matter stack */
	ReturnErrorOnFailure(Nrf::Matter::PrepareServer());

	if (!Nrf::GetBoard().Init(ButtonEventHandler)) {
		LOG_ERR("User interface initialization failed.");
		return CHIP_ERROR_INCORRECT_STATE;
	}

	/* Register Matter event handler that controls the connectivity status LED based on the captured Matter network
	 * state. */
	ReturnErrorOnFailure(Nrf::Matter::RegisterEventHandler(Nrf::Board::DefaultMatterEventHandler, 0));

	return Nrf::Matter::StartServer();
}

CHIP_ERROR AppTask::StartApp()
{
	ReturnErrorOnFailure(Init());

	while (true) {
		Nrf::DispatchNextTask();
	}

	return CHIP_NO_ERROR;
}

    prj.conf

    # Enable CHIP
CONFIG_CHIP=y
CONFIG_CHIP_PROJECT_CONFIG="src/chip_project_config.h"
# 32768 == 0x8000 (example Product ID added temporaly,
# but it must be changed with proper PID from the list:
# https://github.com/project-chip/connectedhomeip/blob/482e6fd03196a6de45465a90003947ef4b86e0b1/docs/examples/discussion/PID_allocation_for_example_apps.md)
CONFIG_CHIP_DEVICE_PRODUCT_ID=32768
CONFIG_STD_CPP17=y

# Enable Matter pairing automatically on application start.
CONFIG_CHIP_ENABLE_PAIRING_AUTOSTART=y

# Enable Matter extended announcement and increase duration to 1 hour.
CONFIG_CHIP_BLE_EXT_ADVERTISING=y
CONFIG_CHIP_BLE_ADVERTISING_DURATION=60

# Add support for LEDs and buttons on Nordic development kits
CONFIG_DK_LIBRARY=y

# Bluetooth Low Energy configuration
CONFIG_BT_DEVICE_NAME="MatterTemplate"

# Other settings
CONFIG_THREAD_NAME=y
CONFIG_MPU_STACK_GUARD=y
CONFIG_RESET_ON_FATAL_ERROR=n
CONFIG_CHIP_LIB_SHELL=y
CONFIG_NCS_SAMPLE_MATTER_TEST_SHELL=y

# Disable NFC commissioning
CONFIG_CHIP_NFC_COMMISSIONING=n

# Reduce application size
CONFIG_USE_SEGGER_RTT=n

# Enable Factory Data feature
CONFIG_CHIP_FACTORY_DATA=y
CONFIG_CHIP_FACTORY_DATA_BUILD=y

###############
# Issue occurs with or without persistent subscriptions, 
# power management or ICD config
###############
# Persistent Subscriptions
CONFIG_CHIP_PERSISTENT_SUBSCRIPTIONS=y

# Configure Power Management
CONFIG_PM_DEVICE=y
CONFIG_RAM_POWER_DOWN_LIBRARY=y
CONFIG_POWEROFF=y

# Settings for ICD with LIT
CONFIG_OPENTHREAD_MTD=y
CONFIG_OPENTHREAD_NORDIC_LIBRARY_MTD=y

CONFIG_CHIP_ENABLE_ICD_SUPPORT=y
CONFIG_CHIP_ICD_LIT_SUPPORT=y
CONFIG_CHIP_ICD_IDLE_MODE_DURATION=900
CONFIG_CHIP_ICD_ACTIVE_MODE_DURATION=500
CONFIG_CHIP_ICD_SLOW_POLL_INTERVAL=30000
CONFIG_CHIP_ICD_FAST_POLLING_INTERVAL=1000
CONFIG_CHIP_ICD_ACTIVE_MODE_THRESHOLD=5000
CONFIG_CHIP_ICD_CLIENTS_PER_FABRIC=2

    Here are the logs from the nrf52840 when the device is rebooted:

    Fullscreen 3630.nrf52.log Download 
    *** Using nRF Connect SDK v3.0.0-3bfc46578e42 ***
*** Using Zephyr OS v4.0.99-3e0ce7636fa6 ***
I: 54 [DL]BLE address: D2:A8:94:EC:58:4E
I: 63 [DL]CHIP task running
I: Init CHIP stack
I: 103 [DL]OpenThread ifconfig up and thread start
I: 108 [DL]OpenThread started: OK
I: 114 [DL]Setting OpenThread device type to SLEEPY END DEVICE
D: Registered new test event: 0xffffffff00000000
D: Registered new test event: 0xffffffff10000000
I: 129 [SVR]Subscription persistence not supported
I: 134 [SVR]Server initializing...
I: 138 [TS]Last Known Good Time: 2025-05-06T09:16:17
I: 147 [FP]Fabric index 0x1 was retrieved from storage. Compressed FabricId 0xBF3EABE8BCEC00C9, FabricId 0x0000000027BEB782, NodeId 0x00000000E72692B5, VendorId 0x1349
I: 165 [FP]Fabric index 0x2 was retrieved from storage. Compressed FabricId 0xE5C463F8148D9844, FabricId 0x00000000BD2EB1F1, NodeId 0x00000000BDC914FC, VendorId 0x1384
I: 181 [DMG]AccessControl: initializing
I: 185 [DMG]Examples::AccessControlDelegate::Init
I: 189 [DMG]AccessControl: setting
I: 192 [DMG]DefaultAclStorage: initializing
I: 200 [DMG]DefaultAclStorage: 2 entries loaded
D: 205 [IN]UDP::Init bind&listen port=5540
E: 210 [IN]IPV6_PKTINFO failed: 109
D: 213 [IN]UDP::Init bound to port=5540
D: 217 [IN]BLEBase::Init - setting/overriding transport
D: 229 [IN]TransportMgr initialized
D: 240 [DL]Using Thread extended MAC for hostname.
I: 248 [ZCL]Using ZAP configuration...
I: 253 [DMG]AccessControlCluster: initializing
D: 257 [DL]Boot reason: 1
I: 260 [ZCL]Initiating Admin Commissioning cluster.
I: 264 [SVR]Fabric already commissioned. Disabling BLE advertisement
D: 270 [DL]CHIPoBLE advertising set to off
I: 274 [DIS]Updating services using commissioning mode 0
E: 279 [DIS]Failed to remove advertised services: 3
D: 284 [DL]Using Thread extended MAC for hostname.
I: 289 [DIS]Advertise operational node BF3EABE8BCEC00C9-00000000E72692B5
E: 295 [DIS]Failed to advertise operational node: 3
E: 300 [DIS]Failed to finalize service update: 3
I: 305 [IN]CASE Server enabling CASE session setups
D: 310 [IN]SecureSession[0x20003768]: Allocated Type:2 LSID:45415
I: 337 [DL]SRP Client was started, detected server: fdfa:ccdd:eab3:0000:0000:00ff:fe00:fc11
I: 345 [SVR]Joining Multicast groups
I: 350 [SVR]Server Listening...
I: 353 [DL]Device Configuration:
I: 356 [DL]  Serial Number: 11223344556677889900
I: 360 [DL]  Vendor Id: 65521 (0xFFF1)
I: 364 [DL]  Product Id: 32768 (0x8000)
I: 367 [DL]  Product Name: not-specified
I: 371 [DL]  Hardware Version: 0
I: 374 [DL]  Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
I: 379 [DL]  Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
I: 386 [DL]  Manufacturing Date: 2022-01-01
I: 390 [DL]  Device Type: 65535 (0xFFFF)
I: 393 [SVR]SetupQRCode: [MT:Y.K9042C00KA0648G00]
I: 398 [SVR]Copy/paste the below URL in a browser to see the QR Code:
I: 404 [SVR]https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3AY.K9042C00KA0648G00
I: 413 [SVR]Manual pairing code: [34970112332]
E: 417 [DL]Long dispatch time: 352 ms, for event type 2
D: 423 [DL]OpenThread State Changed (Flags: 0x00001000)
D: 431 [DL]OpenThread State Changed (Flags: 0x00001000)
D: 439 [DL]OpenThread State Changed (Flags: 0x00001000)
D: 449 [DL]OpenThread State Changed (Flags: 0x00000001)
D: 454 [DL]   Thread Unicast Addresses:
D: 458 [DL]        fd13:a8f:dd50:0:c65:c716:5689:44e3/64 valid preferred
D: 464 [DL]        fdfa:ccdd:eab3::ff:fe00:f408/64 valid preferred rloc
D: 471 [DL]        fdfa:ccdd:eab3:0:4686:c6ad:4022:f0d9/64 valid preferred
D: 477 [DL]        fe80::34c7:b498:9d23:3cec/64 valid preferred
D: 546 [DL]OpenThread State Changed (Flags: 0x00000008)
D: 556 [DL]OpenThread State Changed (Flags: 0x01000000)
D: 567 [DL]OpenThread State Changed (Flags: 0x00000004)
D: 573 [DL]   Device Role: CHILD
D: 580 [DL]OpenThread State Changed (Flags: 0x00000001)
D: 585 [DL]   Thread Unicast Addresses:
D: 589 [DL]        fd13:a8f:dd50:0:c65:c716:5689:44e3/64 valid preferred
D: 595 [DL]        fdfa:ccdd:eab3::ff:fe00:f408/64 valid preferred rloc
D: 601 [DL]        fdfa:ccdd:eab3:0:4686:c6ad:4022:f0d9/64 valid preferred
D: 608 [DL]        fe80::34c7:b498:9d23:3cec/64 valid preferred
D: 617 [DL]OpenThread State Changed (Flags: 0x00001000)
D: 624 [DL]OpenThread State Changed (Flags: 0x00001000)
D: 632 [DL]OpenThread State Changed (Flags: 0x00000020)
D: 640 [DL]OpenThread State Changed (Flags: 0x00000084)
D: 645 [DL]   Device Role: CHILD
D: 648 [DL]   Partition Id: 0x170DC6B9
D: 654 [DL]OpenThread State Changed (Flags: 0x00000200)
D: 661 [DL]OpenThread State Changed (Flags: 0x00000001)
D: 666 [DL]   Thread Unicast Addresses:
D: 670 [DL]        fd13:a8f:dd50:0:c65:c716:5689:44e3/64 valid preferred
D: 676 [DL]        fdfa:ccdd:eab3::ff:fe00:f408/64 valid preferred rloc
D: 683 [DL]        fdfa:ccdd:eab3:0:4686:c6ad:4022:f0d9/64 valid preferred
D: 690 [DL]        fe80::34c7:b498:9d23:3cec/64 valid preferred
D: 752 [DL]SRP update succeeded
I: 755 [SVR]Server initialization complete
I: 759 [DIS]Updating services using commissioning mode 0
D: 764 [DL]Using Thread extended MAC for hostname.
I: 769 [DIS]Advertise operational node BF3EABE8BCEC00C9-00000000E72692B5
I: 776 [DL]advertising srp service: BF3EABE8BCEC00C9-00000000E72692B5._matter._tcp
D: 783 [DL]Using Thread extended MAC for hostname.
I: 788 [DIS]Advertise operational node E5C463F8148D9844-00000000BDC914FC
I: 794 [DL]advertising srp service: E5C463F8148D9844-00000000BDC914FC._matter._tcp
I: 807 [SWU]Stopping the watchdog timer
I: 811 [SWU]Starting the periodic query timer, timeout: 86400 seconds
D: 1256 [DL]SRP update succeeded
I: 1095398 [EM]>>> [E:3716r S:0 M:163889762] (U) Msg RX from 0:B7786DE10796619A [0000] to 0000000000000000 --- Type 0000:30 (SecureChannel:CASE_Sigma1) (B:234)
I: 1095413 [IN]CASE Server received Sigma1 message . Starting handshake. EC 0x20005540
I: 1095421 [EM]<<< [E:3716r S:0 M:153121403 (Ack:163889762)] (U) Msg TX from 0000000000000000 to 0:B7786DE10796619A [0000] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0000:10 (SecureChannel:StandaloneAck) (B:26)
I: 1095442 [SC]Received Sigma1 msg
I: 1095451 [EM]<<< [E:3716r S:0 M:153121404 (Ack:163889762)] (U) Msg TX from 0000000000000000 to 0:B7786DE10796619A [0000] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0000:33 (SecureChannel:CASE_Sigma2Resume) (B:100)
I: 1095473 [EM]??1 [E:3716r S:0 M:153121404] (U) Msg Retransmission to 0:0000000000000000 in 2866ms [State:Active II:500 AI:300 AT:4000]
I: 1096397 [EM]>>> [E:3716r S:0 M:163889763 (Ack:153121404)] (U) Msg RX from 0:B7786DE10796619A [0000] to 0000000000000000 --- Type 0000:40 (SecureChannel:StatusReport) (B:34)
I: 1096417 [SC]Success status report received. Session was established
I: 1096528 [SC]SecureSession[0x20003768, LSID:45415]: State change 'kEstablishing' --> 'kActive'
D: 1096537 [IN]SecureSession[0x20003768]: Activated - Type:2 LSID:45415
D: 1096544 [IN]New secure session activated for device <0000000023E32436, 1>, LSID:45415 PSID:37973!
I: 1096556 [IN]CASE Session established to peer: <0000000023E32436, 1>
D: 1096563 [IN]SecureSession[0x20003840]: Allocated Type:2 LSID:45416
I: 1096570 [EM]<<< [E:3716r S:0 M:153121405 (Ack:163889763)] (U) Msg TX from 0000000000000000 to 0:B7786DE10796619A [0000] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0000:10 (SecureChannel:StandaloneAck) (B:26)
I: 1096594 [EM]>>> [E:3717r S:45415 M:96429865] (S) Msg RX from 1:0000000023E32436 [00C9] to 00000000E72692B5 --- Type 0001:03 (IM:SubscribeRequest) (B:361)
D: 1096608 [IM]Received Subscribe request
I: 1096617 [DMG]Final negotiated min/max parameters: Min = 0s, Max = 900s
I: 1096640 [EM]<<< [E:3717r S:45415 M:61492928 (Ack:96429865)] (S) Msg TX from 00000000E72692B5 to 1:0000000023E32436 [00C9] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0001:05 (IM:ReportData) (B:1182)
I: 1096662 [EM]??1 [E:3717r S:45415 M:61492928] (S) Msg Retransmission to 1:0000000023E32436 in 2877ms [State:Active II:500 AI:300 AT:4000]
I: 1097555 [EM]>>> [E:3717r S:45415 M:96429866 (Ack:61492928)] (S) Msg RX from 1:0000000023E32436 [00C9] to 00000000E72692B5 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 1097570 [IM]Received status response, status is 0x00
I: 1097591 [EM]<<< [E:3717r S:45415 M:61492929 (Ack:96429866)] (S) Msg TX from 00000000E72692B5 to 1:0000000023E32436 [00C9] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0001:05 (IM:ReportData) (B:1209)
I: 1097612 [EM]??1 [E:3717r S:45415 M:61492929] (S) Msg Retransmission to 1:0000000023E32436 in 2879ms [State:Active II:500 AI:300 AT:4000]
I: 1098555 [EM]>>> [E:3717r S:45415 M:96429867 (Ack:61492929)] (S) Msg RX from 1:0000000023E32436 [00C9] to 00000000E72692B5 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 1098570 [IM]Received status response, status is 0x00
I: 1098590 [EM]<<< [E:3717r S:45415 M:61492930 (Ack:96429867)] (S) Msg TX from 00000000E72692B5 to 1:0000000023E32436 [00C9] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0001:05 (IM:ReportData) (B:1184)
I: 1098611 [EM]??1 [E:3717r S:45415 M:61492930] (S) Msg Retransmission to 1:0000000023E32436 in 2856ms [State:Active II:500 AI:300 AT:4000]
I: 1099556 [EM]>>> [E:3717r S:45415 M:96429868 (Ack:61492930)] (S) Msg RX from 1:0000000023E32436 [00C9] to 00000000E72692B5 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 1099571 [IM]Received status response, status is 0x00
I: 1099589 [EM]<<< [E:3717r S:45415 M:61492931 (Ack:96429868)] (S) Msg TX from 00000000E72692B5 to 1:0000000023E32436 [00C9] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0001:05 (IM:ReportData) (B:1192)
I: 1099610 [EM]??1 [E:3717r S:45415 M:61492931] (S) Msg Retransmission to 1:0000000023E32436 in 2836ms [State:Active II:500 AI:300 AT:4000]
I: 1100554 [EM]>>> [E:3717r S:45415 M:96429869 (Ack:61492931)] (S) Msg RX from 1:0000000023E32436 [00C9] to 00000000E72692B5 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 1100569 [IM]Received status response, status is 0x00
I: 1100588 [EM]<<< [E:3717r S:45415 M:61492932 (Ack:96429869)] (S) Msg TX from 00000000E72692B5 to 1:0000000023E32436 [00C9] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0001:05 (IM:ReportData) (B:1203)
I: 1100609 [EM]??1 [E:3717r S:45415 M:61492932] (S) Msg Retransmission to 1:0000000023E32436 in 2887ms [State:Active II:500 AI:300 AT:4000]
I: 1101553 [EM]>>> [E:3717r S:45415 M:96429870 (Ack:61492932)] (S) Msg RX from 1:0000000023E32436 [00C9] to 00000000E72692B5 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 1101568 [IM]Received status response, status is 0x00
I: 1101580 [EM]<<< [E:3717r S:45415 M:61492933 (Ack:96429870)] (S) Msg TX from 00000000E72692B5 to 1:0000000023E32436 [00C9] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0001:05 (IM:ReportData) (B:684)
I: 1101601 [EM]??1 [E:3717r S:45415 M:61492933] (S) Msg Retransmission to 1:0000000023E32436 in 2848ms [State:Active II:500 AI:300 AT:4000]
I: 1102554 [EM]>>> [E:3717r S:45415 M:96429871 (Ack:61492933)] (S) Msg RX from 1:0000000023E32436 [00C9] to 00000000E72692B5 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 1102569 [IM]Received status response, status is 0x00
I: 1102575 [EM]<<< [E:3717r S:45415 M:61492934 (Ack:96429871)] (S) Msg TX from 00000000E72692B5 to 1:0000000023E32436 [00C9] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0001:04 (IM:SubscribeResponse) (B:49)
I: 1102596 [EM]??1 [E:3717r S:45415 M:61492934] (S) Msg Retransmission to 1:0000000023E32436 in 2877ms [State:Active II:500 AI:300 AT:4000]
I: 1102609 [DMG]Registered a ReadHandler that will schedule a report between system Timestamp: 0x000000000010D311 and system Timestamp 0x00000000001E8EB1.
I: 1103554 [EM]>>> [E:3717r S:45415 M:96429872 (Ack:61492934)] (S) Msg RX from 1:0000000023E32436 [00C9] to 00000000E72692B5 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34)
I: 1109837 [ZCL]SwitchServer: OnInitialPress
I: 1109847 [EM]<<< [E:33830i S:45415 M:61492935] (S) Msg TX from 00000000E72692B5 to 1:0000000023E32436 [00C9] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0001:05 (IM:ReportData) (B:111)
I: 1109867 [EM]??1 [E:33830i S:45415 M:61492935] (S) Msg Retransmission to 1:0000000023E32436 in 3156ms [State:Idle II:500 AI:300 AT:4000]
I: 1110867 [EM]>>> [E:33830i S:45415 M:96429873 (Ack:61492935)] (S) Msg RX from 1:0000000023E32436 [00C9] to 00000000E72692B5 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 1110882 [IM]Received status response, status is 0x00
I: 1110888 [EM]<<< [E:33830i S:45415 M:61492936 (Ack:96429873)] (S) Msg TX from 00000000E72692B5 to 1:0000000023E32436 [00C9] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34)
I: 1111025 [ZCL]SwitchServer: OnInitialPress
I: 1111035 [EM]<<< [E:33831i S:45415 M:61492937] (S) Msg TX from 00000000E72692B5 to 1:0000000023E32436 [00C9] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0001:05 (IM:ReportData) (B:111)
I: 1111054 [EM]??1 [E:33831i S:45415 M:61492937] (S) Msg Retransmission to 1:0000000023E32436 in 2863ms [State:Active II:500 AI:300 AT:4000]
I: 1111868 [EM]>>> [E:33831i S:45415 M:96429874 (Ack:61492937)] (S) Msg RX from 1:0000000023E32436 [00C9] to 00000000E72692B5 --- Type 0001:01 (IM:StatusResponse) (B:42)
I: 1111883 [IM]Received status response, status is 0x00
I: 1111889 [EM]<<< [E:33831i S:45415 M:61492938 (Ack:96429874)] (S) Msg TX from 00000000E72692B5 to 1:0000000023E32436 [00C9] [UDP:[fd13:a8f:dd50:0:5bc2:4c35:4a6d:a60e]:57209] --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34)

    Here are the logs from the EFR32MG24 when the device is rebooted:

    silabs2.log

Related
Terms of service