https://devzone.nordicsemi.com/f/nordic-q-a/128769/dect-nr-scheduling-latency-issues/570281Fri, 14 Aug 2026 18:44:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a0b0cbd0-c60b-4a64-b8d2-6407ddcbae9bAmanda HsiehThis is explained in the documentation DECT NR+ physical layer — nrfxlib 3.3.1 documentation , I hope well enough. Thus, if you schedule operations the first operation you need to take the t_{standby_to_idle} and t_{idle_to_active} into account depending on radio mode. The second operation needs only t_{min_sched_opr_trans_dly} also noted as t_m in the figures. The modem packet scheduler handles automatically whether it has time to go to IDLE or STANDBY between consecutively scheduled operations. If you have scheduled multiple operations in advance. If it goes to IDLE or STANDBY then the next operation always pays the t_{standby_to_idle} and t_{idle_to_active} delays. So if the modem knows what is going to happen after current radio command it is executing the delay between radio operations is < 1 slot. But if it does not know, or the command comes too late, i.e. modem is already transitioning to IDLE or to STANDBY, then you pay additional latency.https://devzone.nordicsemi.com/f/nordic-q-a/128682/softdevice-controller-assert-during-dtm-receiver-test-at-dead-marginal-rf-link-nrf52833/570280Fri, 14 Aug 2026 15:02:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:36f56295-58a4-405d-a45e-47a113ae38d9stakHi, Our team has created a fix. PR here: https://github.com/nrfconnect/sdk-nrfxlib/pull/2236 You should be able to update the nrfxlib manifest to pull/2236 already. However, if you wait until it’s merged, the new nrfxlib revision will be available instead. Stinehttps://devzone.nordicsemi.com/f/nordic-q-a/128925/nrf9151-dect-nr---nrf_modem_dect_phy_tx_harq-writes-outside-sram-when-a-spis-peripheral-is-active-bus-fault-both-modem-fw-1-1-0-and-2-0-0/570279Fri, 14 Aug 2026 14:49:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:543dd19f-d97a-4d1f-bf46-6cb4196e5175EWDEVHi Syed, Here's the reproducer. will run on 2 9151DK's All best Andy devzone.nordicsemi.com/.../nrf9151_2D00_tx_2D00_harq_2D00_spis_2D00_reproducer.ziphttps://devzone.nordicsemi.com/f/nordic-q-a/128946/wi-fi-fundamentals-v3-4-0---l4_e2-tfm_bss-is-not-within-region-ram/570278Fri, 14 Aug 2026 14:45:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:9def89f5-7f2b-4bcd-b15c-f53451834f3csteri0Yes, the issue was happening on l4_e2 and l5_e2 when I was adding prj.conf as base config but without adding extra config. So to resume the cases with nrf7002dk/nrf5340/cpuapp/ns: - when adding nothing (neither base config nor extra config) -> works - when adding prj.conf as base config and nrf7002dk_nrf5340_cpuapp_ns.conf as extra config -> works - when adding only nrf7002dk_nrf5340_cpuapp_ns.conf as extra config but not prj.conf -> works - when adding only prj.conf as base config but not nrf7002dk_nrf5340_cpuapp_ns.conf --> doesn't work for l4_e2 and l5_e5 but works for other exercises but anyway I'm not blocked anymore so thank youhttps://devzone.nordicsemi.com/f/nordic-q-a/126513/soft-uart-uart-bitbang-on-nrf52-dk-nrf52832-fails-with/570277Fri, 14 Aug 2026 14:16:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5a10fe59-7ec4-4cc6-831d-f63cb99ac05bChristian77Hi Nabeel. Do you have solved the issue already? I'm facing the same problem using the soft uart. It would be great if you can help me. Thanks BR Christianhttps://devzone.nordicsemi.com/f/nordic-q-a/128959/ncs-3-4-0---sysbuild---custom-overlay-for-mcuboot/570276Fri, 14 Aug 2026 13:38:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:80af73c9-ebfd-48f4-9479-3512d95efa68Achim Kraus> the build system resolves relative paths against MCUboot's own build director y That was my missing information :-), ../../../app/my.overlay works in my case.https://devzone.nordicsemi.com/f/nordic-q-a/128751/readback-protection-enabled-automatically-enables-on-nrf52840-rev3/570275Fri, 14 Aug 2026 13:13:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d303d527-b4e1-470f-b750-0f0e31099093Andrei H.Hi Swathy, Aside from migration from v17.1.0 to v17.0.2, is there anything in particular required to be ensured for the debug feature to be enabled? What if the Bootloader was built against an older version (v17.0.2) does it mean also Bootloader have to be upgraded to this new version or only the application? Best regards.https://devzone.nordicsemi.com/f/nordic-q-a/128771/suspending-uart-with-zephyr-console/570274Fri, 14 Aug 2026 13:06:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:995f586d-5c44-41d5-a1f7-a2007aeb9e00Amanda HsiehWhy is an adapter used instead of native async support in the UART driver? Our R&D thinks the adapter was mainly added to emulate the UART async API on devices that do not support it (primarily for USB CDC ACM). When using UART0, I would not use the adapter at all.https://devzone.nordicsemi.com/f/nordic-q-a/128769/dect-nr-scheduling-latency-issues/570273Fri, 14 Aug 2026 13:04:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8ad835d4-301f-4cce-9b87-aa72df827d23schnitzleinThanks a lot for the answer! :) Most of this is we figured already out. The we rely currently on the "scheduled_operation_transition" Is this the correct delay to be used than or idle_to_active + + active_to_idle ? It feels like that with low_latency mode we are already scheduling massive staying in ACTIVE somekind of and only the + scheduled_operation_transition + is necessary. Can you put some light into this darkness for me? kind regards Christophhttps://devzone.nordicsemi.com/f/nordic-q-a/128962/cellular-iot-fundamentals-lesson-5-exercise-1-does-not-compile-for-thingy-91x/570272Fri, 14 Aug 2026 12:51:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7958dc50-5f58-4336-90a9-e136a2a25ea9Marcus0123Hi I am new to this and don't know what NCS is. I've not tried any earlier versions of anything.https://devzone.nordicsemi.com/f/nordic-q-a/128769/dect-nr-scheduling-latency-issues/570271Fri, 14 Aug 2026 12:48:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:44bc87e3-adfd-403d-a07e-177ab6c4dc07Amanda HsiehCurrently each modem command is atomic thus modem goes after the operation to “idle/stand-by” state and next operation needs to get back “up” from idle state to “active” state. Fast, back-to-back tx-tx, rx-rx, tx-rx or rx-tx operations require some work from our side and new FW release. The delays in state transitions is inherent to modem RF resources ramping down and ramping up for next transmission/reception. Currently the gap you have to have is approximately single slot. The exact value is reported in API. This value in microseconds you can convert to ticks by multiplying the duration with 69.12MHz clock. Please also see the FW / NCS compatibility matrix.https://devzone.nordicsemi.com/f/nordic-q-a/128959/ncs-3-4-0---sysbuild---custom-overlay-for-mcuboot/570270Fri, 14 Aug 2026 12:44:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:08b9ab3e-5c06-43fb-957b-9618d633d62dAmanda HsiehWhen you pass -Dmcuboot_EXTRA_DTC_OVERLAY_FILE='my.overlay' , the build system resolves relative paths against MCUboot's own build director y, not your project directory. That's why a relative path doesn't work, but a full absolute path does.https://devzone.nordicsemi.com/f/nordic-q-a/128751/readback-protection-enabled-automatically-enables-on-nrf52840-rev3/570269Fri, 14 Aug 2026 12:30:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:816d0387-bad2-4d21-93d3-5f8e7d8f7e54SwRaHi Andrei, You will need to use nrf-5-sdk 17.1.0 for this. Support for newer versions of the the nRF52 devices were added only in that version. It won't work on v17.0.2. Regards, Swathyhttps://devzone.nordicsemi.com/f/nordic-q-a/128958/nrf52840-single--vs-dual-bank-behavior/570268Fri, 14 Aug 2026 12:28:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4e8140de-7b03-43b2-985c-c714ec168d8cEinar ThorsrudHi, This is the general normal case, yes. The exception is if you have NRF_DFU_SINGLE_BANK_APP_UPDATES set to 1. But this is not much used. And moreover, if you have BLE as transport for DFU the bootloader depend on the SoftDevice, and then the SoftDevice can also not be updated in single bank manner. Let me note that setting NRF_DFU_SINGLE_BANK_APP_UPDATES to 1 is not much used (and frankly I had forgot it existed), as for most products it makes sense to use dual bank whenever possible.https://devzone.nordicsemi.com/f/nordic-q-a/128958/nrf52840-single--vs-dual-bank-behavior/570267Fri, 14 Aug 2026 12:18:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3f024858-2d4f-4856-944e-9c3c4eb5766aDaniel Fedai LarsenThanks for the quick replies! But what about this statement from docs.nordicsemi.com/.../lib_bootloader_dfu_banks.htmlhttps://devzone.nordicsemi.com/f/nordic-q-a/128958/nrf52840-single--vs-dual-bank-behavior/570266Fri, 14 Aug 2026 12:03:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:edf294fe-702c-4044-8521-9d347b649549Einar ThorsrudHi, From what I can see NRF_DFU_SINGLE_BANK_APP_UPDATES set to 1 should make application and SoftDevice update always use single bank. Bootloader updates however will always be dual bank, as the bootloader cannot update itself in place.https://devzone.nordicsemi.com/f/nordic-q-a/128895/matter-over-wifi-intermittent-no-response-and-retransmission-failures-on-nrf54lm20-dk-nrf7002-eb-ii-ncs-v3-3-4/570265Fri, 14 Aug 2026 11:59:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:20d33b99-62ff-4560-bd5c-39c4f4a0eb0ancohenHi Syed, Problem: The nRF7002 WiFi radio connects to the access point successfully (association + DHCP complete), but after a short period (seconds to minutes), all WiFi communication stops silently. The radio appears connected from the host's perspective — no disconnect event, no error callback, no timeout reported. Data simply stops flowing. Detailed symptoms: Device boots, WiFi initializes, connects to AP — all normal Matter commissioning over BLE succeeds, device joins WiFi fabric WiFi data exchange works briefly (a few seconds to a few minutes) Radio goes silent — no more TX/RX, but no error is raised The host (nRF54LM20) still thinks WiFi is connected — net_if shows UP, no disconnect event fires The connection never recovers on its own — requires full power cycle What we tested: Multiple access points — home router (2.4GHz, WPA2), mobile hotspot — same failure on both CONFIG_NRF_WIFI_RPU_RECOVERY=y — enabled, but recovery never triggers because the RPU does not report any error condition. The watchdog inside the RPU firmware does not fire. Different SDK samples — Matter light bulb sample, WiFi station sample — same behavior Different channels, different security modes — no difference Checked SPI bus between nRF54LM20 and nRF7002 — communication is fine at init, appears to stop after the failure Root cause hypothesis: The nRF7002 RPU firmware enters an internal fault state that is not communicated back to the host over the SPI interface. The host-side recovery mechanism ( RPU_RECOVERY ) relies on the RPU reporting errors, but since the RPU is silently stuck, no recovery is ever triggered. This appears to be a firmware-level issue in the nRF7002 RPU binary, not a host driver issue. Questions: Is this a known issue with the nRF7002 RPU firmware when used with nRF54LM20? Is there a newer RPU firmware binary that addresses silent radio failures? Is there a way to implement a host-side timeout that forces RPU reset if no TX/RX activity occurs for N seconds (independent of RPU error reporting)? Are there any errata or known workarounds for this failure mode? I: 128292 [EM] >> [E:56302r S:27419 M:204082489] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 128343 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 1 null 0 0 I: 128350 [EM] >> [E:11579i S:27419 M:204082490 (Ack:65452698)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 128420 [IM]Received status response, status is 0x00 I: 128426 [EM] >> [E:56302r S:27419 M:204082491 (Ack:65452699)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 130536 [EM]>>> [E:56303r S:27419 M:204082492] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 130551 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 1 null 0 0 I: 130557 [ZCL]Setting on/off to OFF due to level change I: 130562 [ZCL]Endpoint 1 On/off already set to new value I: 130568 [EM] >> [E:56303r S:27419 M:204082493 (Ack:65452701)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 130782 [EM]>>> [E:56304r S:27419 M:204082494] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 130797 [ZCL]Toggle ep1 on/off from state 0 to 1 I: 130801 [ZCL]On Command - OffWaitTime : 0 I: 130805 [ZCL]On/Toggle Command - Stop Timer I: 130811 [ZCL]Cluster OnOff: attribute OnOff set to 1 I: Turn On Action has been initiated I: Turn On Action has been completed I: 130824 [EM] >> [E:56304r S:27419 M:204082495 (Ack:65452702)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 130922 [EM]>>> [E:56305r S:27419 M:204082496] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 130937 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF e7 null 0 0 I: 130943 [ZCL]Setting on/off to ON due to level change I: 130948 [ZCL]Endpoint 1 On/off already set to new value I: 130954 [EM] >> [E:11580i S:27419 M:204082497 (Ack:65452703)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 131033 [IM]Received status response, status is 0x00 I: 131039 [EM] >> [E:56305r S:27419 M:204082498 (Ack:65452704)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 131120 [EM]>>> [E:56306r S:27419 M:204082499] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 131135 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF fe null 0 0 I: 131141 [ZCL]Setting on/off to ON due to level change I: 131146 [ZCL]Endpoint 1 On/off already set to new value I: 131153 [EM] >> [E:11581i S:27419 M:204082500 (Ack:65452706)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 131231 [IM]Received status response, status is 0x00 I: 131236 [EM] >> [E:56306r S:27419 M:204082501 (Ack:65452707)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 131325 [EM]>>> [E:11582i S:27419 M:204082502 (Ack:65452709)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 131340 [IM]Received status response, status is 0x00 I: 131346 [EM] >> [E:56307r S:27419 M:204082503] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 134535 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF f1 null 0 0 I: 134542 [EM] >> [E:56307r S:27419 M:204082504 (Ack:65452711)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 134663 [EM]>>> [E:11583i S:27419 M:204082505 (Ack:65452712)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 134681 [IM]Received status response, status is 0x00 I: 134687 [EM] >> [E:56308r S:27419 M:204082506] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 134727 [ZCL]Toggle ep1 on/off from state 1 to 0 I: 134734 [EM] >> [E:56308r S:27419 M:204082507 (Ack:65452714)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 134844 [EM] >> [E:56309r S:27419 M:204082508] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 134893 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 1 null 0 0 I: 134901 [EM] >> [E:11584i S:27419 M:204082509 (Ack:65452715)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 134971 [IM]Received status response, status is 0x00 I: 134977 [EM] >> [E:56309r S:27419 M:204082510 (Ack:65452716)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 136580 [EM]>>> [E:56310r S:27419 M:204082511] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 136594 [ZCL]Toggle ep1 on/off from state 0 to 1 I: 136599 [ZCL]On Command - OffWaitTime : 0 I: 136603 [ZCL]On/Toggle Command - Stop Timer I: 136609 [ZCL]Cluster OnOff: attribute OnOff set to 1 I: Turn On Action has been initiated I: Turn On Action has been completed I: 136622 [EM] >> [E:56310r S:27419 M:204082512 (Ack:65452718)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 136722 [EM]>>> [E:56311r S:27419 M:204082513] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 136737 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 6 null 0 0 I: 136743 [ZCL]Setting on/off to ON due to level change I: 136748 [ZCL]Endpoint 1 On/off already set to new value I: 136754 [EM] >> [E:11585i S:27419 M:204082514 (Ack:65452719)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 136833 [IM]Received status response, status is 0x00 I: 136838 [EM] >> [E:56311r S:27419 M:204082515 (Ack:65452720)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 136918 [EM]>>> [E:56312r S:27419 M:204082516] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 136935 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF fe null 0 0 I: 136941 [ZCL]Setting on/off to ON due to level change I: 136946 [ZCL]Endpoint 1 On/off already set to new value I: 136952 [EM] >> [E:11586i S:27419 M:204082517 (Ack:65452722)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 137030 [IM]Received status response, status is 0x00 I: 137036 [EM] >> [E:56312r S:27419 M:204082518 (Ack:65452723)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 137117 [EM]>>> [E:11587i S:27419 M:204082519 (Ack:65452725)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 137132 [IM]Received status response, status is 0x00 I: 137137 [EM] >> [E:56313r S:27419 M:204082520] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 140080 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 99 null 0 0 I: 140087 [EM] >> [E:56313r S:27419 M:204082521 (Ack:65452727)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 140212 [EM]>>> [E:11588i S:27419 M:204082522 (Ack:65452728)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 140227 [IM]Received status response, status is 0x00 I: 140232 [EM] 2 I: 141668 [DIS]Lookup started for CCC10070EA402D1F-00000000BCDA9022 I: 141676 [IM]Skip resuming live subscriptionId 2159917505 I: 141867 [DIS]Checking node lookup status for CCC10070EA402D1F-00000000BCDA9022 after 200 ms I: 143399 [EM]>>> [E:56314r S:27419 M:204082523] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 143414 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF cb null 0 0 I: 143420 [ZCL]Setting on/off to ON due to level change I: 143425 [ZCL]Endpoint 1 On/off already set to new value I: 143431 [EM] >> [E:56314r S:27419 M:204082524 (Ack:65452730)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 143553 [EM]>>> [E:56315r S:27419 M:204082525] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 143568 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF dd null 0 0 I: 143574 [ZCL]Setting on/off to ON due to level change I: 143579 [ZCL]Endpoint 1 On/off already set to new value I: 143586 [EM] >> [E:11589i S:27419 M:204082526 (Ack:65452731)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 143665 [IM]Received status response, status is 0x00 I: 143671 [EM] >> [E:56315r S:27419 M:204082527 (Ack:65452732)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 143751 [EM]>>> [E:11590i S:27419 M:204082528 (Ack:65452734)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 143766 [IM]Received status response, status is 0x00 I: 143772 [EM] >> [E:56316r S:27419 M:204082529] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 143810 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF fe null 0 0 I: 143816 [ZCL]Setting on/off to ON due to level change I: 143821 [ZCL]Endpoint 1 On/off already set to new value I: 143827 [EM] >> [E:56316r S:27419 M:204082530 (Ack:65452736)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 143952 [EM]>>> [E:11591i S:27419 M:204082531 (Ack:65452737)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 143968 [IM]Received status response, status is 0x00 I: 143974 [EM] >> [E:56317r S:27419 M:204082532] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 144012 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF fe null 0 0 I: 144018 [ZCL]Setting on/off to ON due to level change I: 144023 [ZCL]Endpoint 1 On/off already set to new value I: 144029 [EM] >> [E:56317r S:27419 M:204082533 (Ack:65452739)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 159789 [EM]>>> [E:31890r S:0 M:9487168] (U) Msg RX from 0:5C2E322FD610A5C0 [0000] to 0000000000000000 --- Type 0000:30 (SecureChannel:CASE_Sigma1) (B:234) I: 159803 [IN]CASE Server received Sigma1 message . Starting handshake. EC 0x20012cc0 I: 159810 [EM] >> [E:31890r S:0 M:9487169 (Ack:219472618)] (U) Msg RX from 0:5C2E322FD610A5C0 [0000] to 0000000000000000 --- Type 0000:40 (SecureChannel:StatusReport) (B:34) I: 159927 [SC]Success status report received. Session was established I: 159965 [SC]SecureSession[0x20010280, LSID:27420]: State change 'kEstablishing' --> 'kActive' D: 159974 [IN]SecureSession[0x20010280]: Activated - Type:2 LSID:27420 D: 159980 [IN]New secure session activated for device , LSID:27420 PSID:45409! I: 159989 [IN]CASE Session established to peer: D: 159995 [IN]SecureSession[0x20010358]: Allocated Type:2 LSID:27421 I: 160001 [EM] >> [E:31891r S:27420 M:184507248] (S) Msg RX from 1:00000000BCDA9022 [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 160037 [ZCL]Toggle ep1 on/off from state 1 to 0 I: 160043 [EM] >> [E:31891r S:27420 M:184507249 (Ack:170611239)] (S) Msg RX from 1:00000000BCDA9022 [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 160801 [EM] 'kDefunct' E: 183278 [DMG]Time out! failed to receive status response from Exchange: 11592i I: 183285 [DMG]Subscription id 0x80bdb9c1 from node torn down I: 183293 [IM]Schedule subscription resumption when failing to establish session, Retries: 2 I: 186667 [DIS]Checking node lookup status for CCC10070EA402D1F-00000000BCDA9022 after 45000 ms E: 186676 [DIS]OperationalSessionSetup[1:00000000BCDA9022]: operational discovery failed: 32 E: 186684 [DMG]Failed to establish CASE for subscription-resumption with error '32' I: 188244 [SC]SecureSession[0x2000fff8, LSID:27419]: State change 'kDefunct' --> 'kActive' I: 188252 [EM]>>> [E:56318r S:27419 M:204082534] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 188267 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 66 null 0 0 I: 188274 [EM] >> [E:56318r S:27419 M:204082534] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 189598 [EM] >> [E:56318r S:27419 M:204082534] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 190759 [EM] 'kDefunct' D: 192800 [IN]Received a duplicate message with MessageCounter:204082534 on exchange 56318r I: 192808 [SC]SecureSession[0x2000fff8, LSID:27419]: State change 'kDefunct' --> 'kActive' I: 192816 [EM]>>> [E:56318r S:27419 M:204082534] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 192831 [EM] >> [E:56318r S:27419 M:204082534] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 196313 [EM] >> [E:56319r S:0 M:78565332] (U) Msg RX from 0:35DCBCE7A815924B [0000] to 0000000000000000 --- Type 0000:30 (SecureChannel:CASE_Sigma1) (B:234) I: 208886 [IN]CASE Server received Sigma1 message . Starting handshake. EC 0x20012cc0 I: 208897 [EM] >> [E:56319r S:0 M:78565333 (Ack:219472621)] (U) Msg RX from 0:35DCBCE7A815924B [0000] to 0000000000000000 --- Type 0000:40 (SecureChannel:StatusReport) (B:34) I: 209133 [SC]Success status report received. Session was established I: 209170 [SC]SecureSession[0x20010358, LSID:27421]: State change 'kEstablishing' --> 'kActive' D: 209179 [IN]SecureSession[0x20010358]: Activated - Type:2 LSID:27421 D: 209185 [IN]New secure session activated for device , LSID:27421 PSID:37729! I: 209194 [IN]CASE Session established to peer: D: 209200 [IN]SecureSession[0x20010430]: Allocated Type:2 LSID:27422 I: 209206 [EM] >> [E:56320r S:27421 M:48796888] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 209243 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 6e null 0 0 I: 209249 [ZCL]Setting on/off to ON due to level change I: 209254 [ZCL]Endpoint 1 On/off already set to new value I: 209260 [EM] >> [E:56320r S:27421 M:48796889 (Ack:63459747)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 209341 [EM]>>> [E:56321r S:27421 M:48796890] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 209356 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF fe null 0 0 I: 209362 [ZCL]Setting on/off to ON due to level change I: 209367 [ZCL]Endpoint 1 On/off already set to new value I: 209374 [EM] >> [E:56321r S:27421 M:48796891 (Ack:63459748)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 209454 [EM]>>> [E:56322r S:27421 M:48796892] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 209468 [ZCL]Toggle ep1 on/off from state 1 to 0 I: 209474 [EM] >> [E:56322r S:27421 M:48796893 (Ack:63459749)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 209580 [EM]>>> [E:56323r S:27421 M:48796894] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 209595 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 34 null 0 0 I: 209602 [EM] >> [E:56323r S:27421 M:48796895 (Ack:63459750)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 209694 [EM]>>> [E:56324r S:27421 M:48796896] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 209709 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 45 null 0 0 I: 209715 [ZCL]Setting on/off to ON due to level change I: 209720 [ZCL]Endpoint 1 On/off already set to new value I: 209727 [EM] >> [E:56324r S:27421 M:48796897 (Ack:63459751)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 209808 [EM]>>> [E:56325r S:27421 M:48796898] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 209822 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF fe null 0 0 I: 209828 [ZCL]Setting on/off to ON due to level change I: 209833 [ZCL]Endpoint 1 On/off already set to new value I: 209840 [EM] >> [E:56325r S:27421 M:48796899 (Ack:63459752)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 209964 [EM]>>> [E:56326r S:27421 M:48796900] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 209979 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF fb null 0 0 I: 209986 [EM] >> [E:56326r S:27421 M:48796901 (Ack:63459753)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 210067 [EM]>>> [E:56327r S:27421 M:48796902] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 210082 [ZCL]Toggle ep1 on/off from state 1 to 0 I: 210088 [EM] >> [E:56327r S:27421 M:48796903 (Ack:63459754)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 210192 [EM]>>> [E:56328r S:27421 M:48796904] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 210206 [ZCL]Toggle ep1 on/off from state 0 to 1 I: 210211 [ZCL]On Command - OffWaitTime : 0 I: 210215 [ZCL]On/Toggle Command - Stop Timer I: 210221 [ZCL]Cluster OnOff: attribute OnOff set to 1 I: Turn On Action has been initiated I: Turn On Action has been completed I: 210232 [ZCL]Cluster LevelControl: attribute CurrentLevel set to 1 I: 210240 [EM] >> [E:56328r S:27421 M:48796905 (Ack:63459755)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 210311 [EM]>>> [E:56329r S:27421 M:48796906] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 210325 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF f4 null 0 0 I: 210333 [EM] >> [E:56329r S:27421 M:48796907 (Ack:63459756)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 210459 [EM]>>> [E:56330r S:27421 M:48796908] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 210474 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF fe null 0 0 I: 210480 [ZCL]Setting on/off to ON due to level change I: 210485 [ZCL]Endpoint 1 On/off already set to new value I: 210491 [EM] >> [E:56330r S:27421 M:48796909 (Ack:63459757)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 210574 [EM]>>> [E:56331r S:27421 M:48796910] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 210589 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF fb null 0 0 I: 210596 [EM] >> [E:56331r S:27421 M:48796911 (Ack:63459758)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 210677 [EM]>>> [E:56332r S:27421 M:48796912] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 210691 [ZCL]Toggle ep1 on/off from state 1 to 0 I: 210697 [EM] >> [E:56332r S:27421 M:48796913 (Ack:63459759)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 210801 [EM]>>> [E:56333r S:27421 M:48796914] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 210815 [ZCL]Toggle ep1 on/off from state 0 to 1 I: 210820 [ZCL]On Command - OffWaitTime : 0 I: 210824 [ZCL]On/Toggle Command - Stop Timer I: 210830 [ZCL]Cluster OnOff: attribute OnOff set to 1 I: Turn On Action has been initiated I: Turn On Action has been completed I: 210842 [ZCL]Cluster LevelControl: attribute CurrentLevel set to 1 I: 210849 [EM] >> [E:56333r S:27421 M:48796915 (Ack:63459760)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 210991 [EM]>>> [E:56334r S:27421 M:48796916] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 211005 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF fe null 0 0 I: 211012 [ZCL]Setting on/off to ON due to level change I: 211017 [ZCL]Endpoint 1 On/off already set to new value I: 211023 [EM] >> [E:56334r S:27421 M:48796917 (Ack:63459761)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 211103 [EM]>>> [E:56335r S:27421 M:48796918] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 211118 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 1 null 0 0 I: 211126 [EM] >> [E:56335r S:27421 M:48796919 (Ack:63459762)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 211223 [EM]>>> [E:56336r S:27421 M:48796920] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 211238 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 1a null 0 0 I: 211244 [ZCL]Setting on/off to ON due to level change I: 211249 [ZCL]Toggle ep1 on/off from state 0 to 1 I: 211253 [ZCL]On Command - OffWaitTime : 0 I: 211257 [ZCL]On/Toggle Command - Stop Timer I: 211263 [ZCL]Cluster OnOff: attribute OnOff set to 1 I: Turn On Action has been initiated I: Turn On Action has been completed I: 211276 [EM] >> [E:56336r S:27421 M:48796921 (Ack:63459763)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 211357 [EM]>>> [E:56337r S:27421 M:48796922] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 211372 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 1 null 0 0 I: 211379 [EM] >> [E:56337r S:27421 M:48796923 (Ack:63459764)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 211547 [EM]>>> [E:56338r S:27421 M:48796924] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 211562 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF e null 0 0 I: 211568 [ZCL]Setting on/off to ON due to level change I: 211573 [ZCL]Toggle ep1 on/off from state 0 to 1 I: 211577 [ZCL]On Command - OffWaitTime : 0 I: 211581 [ZCL]On/Toggle Command - Stop Timer I: 211587 [ZCL]Cluster OnOff: attribute OnOff set to 1 I: Turn On Action has been initiated I: Turn On Action has been completed I: 211600 [EM] >> [E:56338r S:27421 M:48796925 (Ack:63459765)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 213096 [EM]>>> [E:56339r S:27421 M:48796926] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 213111 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 15 null 0 0 I: 213117 [ZCL]Setting on/off to ON due to level change I: 213122 [ZCL]Endpoint 1 On/off already set to new value I: 213129 [EM] >> [E:56339r S:27421 M:48796927 (Ack:63459766)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 213304 [EM]>>> [E:56340r S:27421 M:48796928] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 213319 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF fe null 0 0 I: 213325 [ZCL]Setting on/off to ON due to level change I: 213330 [ZCL]Endpoint 1 On/off already set to new value I: 213337 [EM] >> [E:56340r S:27421 M:48796929 (Ack:63459767)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 238401 [EM]>>> [E:56341r S:27421 M:48796930] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 238416 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF 66 null 0 0 I: 238423 [EM] >> [E:56341r S:27421 M:48796931 (Ack:63459768)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 239306 [EM]>>> [E:56342r S:27421 M:48796932] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 239321 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF cb null 0 0 I: 239327 [ZCL]Setting on/off to ON due to level change I: 239332 [ZCL]Endpoint 1 On/off already set to new value I: 239339 [EM] >> [E:56342r S:27421 M:48796933 (Ack:63459769)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 240055 [EM]>>> [E:56343r S:27421 M:48796934] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 240069 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF ce null 0 0 I: 240076 [ZCL]Setting on/off to ON due to level change I: 240080 [ZCL]Endpoint 1 On/off already set to new value I: 240087 [EM] >> [E:56343r S:27421 M:48796935 (Ack:63459770)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 240330 [EM]>>> [E:56344r S:27421 M:48796936] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:70) I: 240345 [ZCL]RX level-control: MOVE_TO_LEVEL_WITH_ON_OFF fe null 0 0 I: 240351 [ZCL]Setting on/off to ON due to level change I: 240356 [ZCL]Endpoint 1 On/off already set to new value I: 240363 [EM] >> [E:56344r S:27421 M:48796937 (Ack:63459771)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 242175 [EM]>>> [E:56345r S:27421 M:48796938] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 242190 [ZCL]Toggle ep1 on/off from state 1 to 0 I: 242196 [EM] >> [E:56345r S:27421 M:48796939 (Ack:63459772)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 243293 [DIS]Found an existing secure session to [1:00000000BCDA9022]! D: 243300 [DIS]OperationalSessionSetup[1:00000000BCDA9022]: State change 1 --> 5 I: 243307 [DMG]Registered a ReadHandler that will schedule a report between system Timestamp: 0x000000000003B66B and system Timestamp 0x00000000000CDE2B. I: 243350 [DIS]Found an existing secure session to [1:00000000086809DB]! D: 243356 [DIS]OperationalSessionSetup[1:00000000086809DB]: State change 1 --> 5 I: 243365 [DMG]Registered a ReadHandler that will schedule a report between system Timestamp: 0x000000000003B6A5 and system Timestamp 0x00000000000CDE65. I: 243433 [EM] >> [E:56346r S:27421 M:48796940] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 243532 [ZCL]Toggle ep1 on/off from state 0 to 1 I: 243536 [ZCL]On Command - OffWaitTime : 0 I: 243542 [ZCL]On/Toggle Command - Stop Timer I: 243548 [ZCL]Cluster OnOff: attribute OnOff set to 1 I: Turn On Action has been initiated I: Turn On Action has been completed I: 243560 [ZCL]Cluster LevelControl: attribute CurrentLevel set to 1 I: 243567 [EM] >> [E:11594i S:27421 M:48796941 (Ack:63459773)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 243636 [IM]Received status response, status is 0x00 I: 243689 [EM] >> [E:56346r S:27421 M:48796942 (Ack:63459774)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0000:10 (SecureChannel:StandaloneAck) (B:34) I: 243786 [EM]>>> [E:11594i S:27421 M:48796943 (Ack:63459775)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 243801 [IM]Received status response, status is 0x00 I: 243853 [EM] >> [E:11594i S:27421 M:48796944 (Ack:63459776)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 244030 [IM]Received status response, status is 0x00 I: 244065 [EM] >> [E:11594i S:27421 M:48796945 (Ack:63459777)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 244116 [IM]Received status response, status is 0x00 I: 244150 [EM] >> [E:11594i S:27421 M:48796946 (Ack:63459778)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 244224 [IM]Received status response, status is 0x00 I: 244262 [EM] >> [E:11594i S:27421 M:48796947 (Ack:63459779)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 244342 [IM]Received status response, status is 0x00 I: 244374 [EM] >> [E:11594i S:27421 M:48796948 (Ack:63459780)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 244563 [IM]Received status response, status is 0x00 I: 244590 [EM] >> [E:11594i S:27421 M:48796949 (Ack:63459781)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 244647 [IM]Received status response, status is 0x00 I: 244660 [EM] >> [E:11594i S:27421 M:48796950 (Ack:63459782)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 244724 [IM]Received status response, status is 0x00 I: 244730 [EM] >> [E:11595i S:27421 M:48796951 (Ack:63459784)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 244819 [IM]Received status response, status is 0x00 I: 244873 [EM] >> [E:11595i S:27421 M:48796952 (Ack:63459785)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 244960 [IM]Received status response, status is 0x00 I: 245014 [EM] >> [E:11595i S:27421 M:48796953 (Ack:63459786)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 245069 [IM]Received status response, status is 0x00 I: 245105 [EM] >> [E:11595i S:27421 M:48796954 (Ack:63459787)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 245156 [IM]Received status response, status is 0x00 I: 245192 [EM] >> [E:11595i S:27421 M:48796955 (Ack:63459788)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 245243 [IM]Received status response, status is 0x00 I: 245282 [EM] >> [E:11595i S:27421 M:48796956 (Ack:63459789)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 245341 [IM]Received status response, status is 0x00 I: 245375 [EM] >> [E:11595i S:27421 M:48796957 (Ack:63459790)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 245426 [IM]Received status response, status is 0x00 I: 245455 [EM] >> [E:11595i S:27421 M:48796958 (Ack:63459791)] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 245596 [IM]Received status response, status is 0x00 I: 245601 [EM] >> [E:11593i S:27420 M:184507250 (Ack:170611240)] (S) Msg RX from 1:00000000BCDA9022 [2D1F] to 00000000407AC4A6 --- Type 0001:01 (IM:StatusResponse) (B:42) I: 248505 [IM]Received status response, status is 0x7d I: 248532 [DMG]Subscription id 0xb8d9d2da from node torn down I: 248544 [EM] >> [E:56347r S:27421 M:48796959] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 273427 [ZCL]Toggle ep1 on/off from state 1 to 0 I: 273432 [EM] >> [E:56347r S:27421 M:48796959] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 274711 [EM] >> [E:56347r S:27421 M:48796959] (S) Msg RX from 1:00000000086809DB [2D1F] to 00000000407AC4A6 --- Type 0001:08 (IM:InvokeCommandRequest) (B:59) I: 275871 [EM] 'kDefunct' E: 277631 [EM] torn down I: 293857 [IM]Schedule subscription resumption when failing to establish session, Retries: 1 I: 313857 [DIS]Found an existing secure session to [1:00000000086809DB]! D: 313864 [DIS]OperationalSessionSetup[1:00000000086809DB]: State change 1 --> 5 I: 313871 [DMG]Registered a ReadHandler that will schedule a report between system Timestamp: 0x000000000004CA0F and system Timestamp 0x00000000000DF1CF. I: 313937 [EM] 'kDefunct' E: 337068 [DMG]Time out! failed to receive status response from Exchange: 11597i I: 337075 [DMG]Subscription id 0x80bdb9c1 from node torn down I: 337083 [IM]Schedule subscription resumption when failing to establish session, Retries: 1 D: 357084 [DIS]OperationalSessionSetup[1:00000000086809DB]: State change 1 --> 2 I: 357092 [DIS]Lookup started for CCC10070EA402D1F-00000000086809DB I: 357291 [DIS]Checking node lookup status for CCC10070EA402D1F-00000000086809DB after 200 ms E: 388092 [DIS]Timeout waiting for mDNS resolution. I: 402091 [DIS]Checking node lookup status for CCC10070EA402D1F-00000000086809DB after 45000 ms E: 402100 [DIS]OperationalSessionSetup[1:00000000086809DB]: operational discovery failed: 32 E: 402108 [DMG]Failed to establish CASE for subscription-resumption with error '32' I: 402116 [IM]Schedule subscription resumption when failing to establish session, Retries: 2https://devzone.nordicsemi.com/f/nordic-q-a/128962/cellular-iot-fundamentals-lesson-5-exercise-1-does-not-compile-for-thingy-91x/570264Fri, 14 Aug 2026 11:55:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7a8a1f30-555f-455d-8935-ed115b3940fcHakonHello, [quote user=""]When attempting to build Lesson 5 Exercise 1 we both get errors, see below.[/quote] Do you know if this issue happens on earlier versions of NCS?https://devzone.nordicsemi.com/f/nordic-q-a/123723/sdk-3-0-2-flash_area_image_secondary-returns-flash_area_image_primary-id/570263Fri, 14 Aug 2026 11:43:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:70f9f60e-b7a4-46fa-ab95-ea5304cd9f8cEinar ThorsrudThe partition manager has been deprecated and is being removed, so there will be no update/fix for this in the parition manager.https://devzone.nordicsemi.com/f/nordic-q-a/128948/npm1300-going-directly-into-trickle-charge-without-meeting-the-termination-voltage/570262Fri, 14 Aug 2026 11:30:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:517a2189-4537-4b3a-9956-7787138c3488adunk