The client does not enter sleep mode as expected.

RE: The client does not enter sleep mode as expected.

Kenneth — Tue, 04 Nov 2025 11:56:05 GMT

Hi,

Did you also follow:

[quote user="Marte.M"]If you get any errors, you might have to increase CONFIG_ZVFS_OPEN_MAX and CONFIG_NET_SOCKETS_POLL_MAX. You should also remove CONFIG_NET_CONFIG_MY_IPV4_ADDR from prj.conf, as if you have this, zperf will try to use the address set there instead of the device's actual address. You can see the device's address in the log:[/quote]

Kenneth

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Thu, 30 Oct 2025 11:21:04 GMT

Hi Merte,

Any update on this, please?

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Tue, 28 Oct 2025 07:50:47 GMT

Hi Merte,

Any update on this, please?

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Fri, 24 Oct 2025 07:24:57 GMT

Hi Marte,

As you mentioned, we are getting logs in the TWT sample. However, in the Pcap capture, we are not able to see the client entering sleep mode. For your reference, I have attached the Pcap files

[quote userid="92402" url="~/f/nordic-q-a/124001/the-client-does-not-enter-sleep-mode-as-expected/551095"]

If you want to use the TWT sample I shared, you can enable zperf by adding the following in prj.conf:

Fullscreen

1
2
3
CONFIG_NET_SHELL=y
CONFIG_NET_ZPERF=y
CONFIG_ZVFS_OPEN_MAX=12
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

CONFIG_NET_SHELL=y
CONFIG_NET_ZPERF=y
CONFIG_ZVFS_OPEN_MAX=12

[/quote]

As per your suggestion, I added the three lines to the prj.conf file in the TWT sample. However, after making these changes, I encountered a new issue. Kindly find the logs below for your reference.

Please share the complete file with include these three lines.

Logs :-

:00:00.346,221] <inf> wifi_nrf: Management buffer offload enabled

*** Booting nRF Connect SDK v2.9.2-4ab7b98fc76f ***
*** Using Zephyr OS v3.7.99-aa34a5632971 ***
[00:00:00.475,280] <inf> net_config: Initializing network
[00:00:00.475,280] <inf> net_config: Waiting interface 1 (0x20001300) to be up...
[00:00:00.475,463] <inf> net_config: IPv4 address: 192.168.1.99
[00:00:00.475,494] <inf> net_config: Running dhcpv4 client...
[00:00:00.475,738] <inf> twt: Starting nrf7002dk with CPU frequency: 64 MHz
[00:00:00.477,386] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:00.512,420] <err> wifi_supplicant: Failed to initialize supplicant control interface
[00:00:01.475,860] <inf> twt: Static IP address (overridable): 192.168.1.99/255.255.255.0 -> 192.168.1.1
[00:00:01.475,982] <err> wifi_mgmt_ext: Connection request failed

[00:00:01.475,982] <err> twt: Connection request failed
[00:00:01.476,013] <inf> twt: Status request failed: -134

[00:00:01.776,092] <inf> twt: Status request failed: -134

[00:00:02.076,202] <inf> twt: Status request failed: -134

[00:00:02.376,312] <inf> twt: Status request failed: -134

[00:00:02.676,483] <inf> twt: Status request failed: -134

[00:00:02.976,593] <inf> twt: Status request failed: -134

[00:00:03.276,702] <inf> twt: Status request failed: -134

[00:00:03.576,812] <inf> twt: Status request failed: -134

[00:00:03.876,983] <inf> twt: Status request failed: -134

[00:00:04.177,062] <inf> twt: Status request failed: -134

[00:00:04.477,233] <inf> twt: Status request failed: -134

[00:00:04.777,313] <inf> twt: Status request failed: -134

[00:00:05.077,484] <inf> twt: Status request failed: -134

[00:00:05.377,593] <inf> twt: Status request failed: -134

[00:00:05.677,703] <inf> twt: Status request failed: -134

[00:00:05.977,813] <inf> twt: Status request failed: -134

[00:00:06.277,984] <inf> twt: Status request failed: -134

[00:00:06.578,094] <inf> twt: Status request failed: -134

[00:00:06.878,204] <inf> twt: Status request failed: -134

[00:00:07.178,314] <inf> twt: Status request failed: -134

[00:00:07.478,485] <inf> twt: Status request failed: -134

[00:00:07.778,594] <inf> twt: Status request failed: -134

[00:00:08.078,704] <inf> twt: Status request failed: -134

[00:00:08.378,814] <inf> twt: Status request failed: -134

https://drive.google.com/file/d/14Fs-UamPPC6dTh4ZYP61TrN7U21sawLM/view?usp=drive_link

Thanks & Regards,

Naveen P

RE: The client does not enter sleep mode as expected.

Marte Myrvold — Fri, 10 Oct 2025 09:30:46 GMT

Hi,

Based on the logs with the TWT sample, the device enters sleep mode as it should, so this is most likely also the case when you use the shell sample. In other words, you can chose to use the TWT sample I shared or the Wi-Fi shell sample in the SDK for TWT.

If you want to use the TWT sample I shared, you can enable zperf by adding the following in prj.conf:

CONFIG_NET_SHELL=y
CONFIG_NET_ZPERF=y
CONFIG_ZVFS_OPEN_MAX=12

This lets you use iperf/zperf as in the Wi-Fi Throughput sample, i.e., you can use the following command on the nRF7002:

zperf udp upload <ipaddress> 5001 10 1K 50M
zperf udp download 5001

If you get any errors, you might have to increase CONFIG_ZVFS_OPEN_MAX and CONFIG_NET_SOCKETS_POLL_MAX. You should also remove CONFIG_NET_CONFIG_MY_IPV4_ADDR from prj.conf, as if you have this, zperf will try to use the address set there instead of the device's actual address. You can see the device's address in the log:

Best regards,
Marte

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Thu, 09 Oct 2025 12:44:11 GMT

Hi Marte,

Any updates on this?

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Tue, 07 Oct 2025 05:40:34 GMT

Hi Marte,

[quote userid="147707" url="~/f/nordic-q-a/124001/the-client-does-not-enter-sleep-mode-as-expected/550712"]we want to run ping traffic on this client.[/quote]

And we want to run iperf or zperf.

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Mon, 06 Oct 2025 12:58:11 GMT

Hi Marte,

[quote userid="92402" url="~/f/nordic-q-a/124001/the-client-does-not-enter-sleep-mode-as-expected/550697"]

Did you set the credentials by changing these configs to the SSID and password for your network?

Fullscreen

1
2
CONFIG_WIFI_CREDENTIALS_STATIC_SSID="MySSID"
CONFIG_WIFI_CREDENTIALS_STATIC_PASSWORD="MyPassword"
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

CONFIG_WIFI_CREDENTIALS_STATIC_SSID="MySSID"
CONFIG_WIFI_CREDENTIALS_STATIC_PASSWORD="MyPassword"

What kind of security does the network use? In prj.conf, in the sample I shared, I set

[/quote]

Now the client is connected to the SSID and working as expected, but we want to run ping traffic on this client.

Please find the attached logs below for your reference:

*** Booting nRF Connect SDK v2.9.2-4ab7b98fc76f ***
*** Using Zephyr OS v3.7.99-aa34a5632971 ***
[00:00:00.486,999] <inf> net_config: Initializing network
[00:00:00.486,999] <inf> net_config: Waiting interface 1 (0x20001080) to be up...
[00:00:00.487,182] <inf> net_config: IPv4 address: 192.168.1.99
[00:00:00.487,213] <inf> net_config: Running dhcpv4 client...
[00:00:00.487,457] <inf> twt: Starting nrf7002dk with CPU frequency: 64 MHz
[00:00:00.489,349] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:01.487,579] <inf> twt: Static IP address (overridable): 192.168.1.99/255.255.255.0 -> 192.168.1.1
[00:00:03.419,860] <inf> wifi_mgmt_ext: Connection requested
[00:00:03.419,891] <inf> twt: Connection requested
[00:00:03.419,952] <inf> twt: ==================
[00:00:03.419,982] <inf> twt: State: SCANNING
[00:00:03.720,123] <inf> twt: ==================
[00:00:03.720,153] <inf> twt: State: SCANNING
[00:00:04.020,324] <inf> twt: ==================
[00:00:04.020,355] <inf> twt: State: SCANNING
[00:00:04.320,495] <inf> twt: ==================
[00:00:04.320,495] <inf> twt: State: SCANNING
[00:00:04.620,666] <inf> twt: ==================
[00:00:07.322,296] <inf> twt: State: AUTHENTICATING
[00:00:07.622,436] <inf> twt: ==================
[00:00:07.622,467] <inf> twt: State: AUTHENTICATING
[00:00:07.940,948] <inf> twt: ==================
[00:00:07.940,979] <inf> twt: State: ASSOCIATED
[00:00:07.941,009] <inf> twt: Interface Mode: STATION
[00:00:07.941,009] <inf> twt: Link Mode: WIFI 6 (802.11ax/HE)
[00:00:07.941,040] <inf> twt: SSID: TWT
[00:00:07.941,070] <inf> twt: BSSID: 00:33:58:AB:81:82
[00:00:07.941,101] <inf> twt: Band: 5GHz
[00:00:07.941,101] <inf> twt: Channel: 64
[00:00:07.941,131] <inf> twt: Security: WPA2-PSK
[00:00:07.941,131] <inf> twt: MFP: Optional
[00:00:07.941,162] <inf> twt: RSSI: -56
[00:00:07.941,162] <inf> twt: TWT: Supported
[00:00:07.994,842] <inf> twt: Connected
[00:00:08.248,474] <inf> twt: ==================
[00:00:08.248,504] <inf> twt: State: COMPLETED
[00:00:08.248,535] <inf> twt: Interface Mode: STATION
[00:00:08.248,565] <inf> twt: Link Mode: WIFI 6 (802.11ax/HE)
[00:00:08.248,596] <inf> twt: SSID: TWT
[00:00:08.248,626] <inf> twt: BSSID: 00:33:58:AB:81:82
[00:00:08.248,626] <inf> twt: Band: 5GHz
[00:00:08.248,657] <inf> twt: Channel: 64
[00:00:08.248,657] <inf> twt: Security: WPA2-PSK
[00:00:08.248,687] <inf> twt: MFP: Optional
[00:00:08.248,687] <inf> twt: RSSI: -55
[00:00:08.248,718] <inf> twt: TWT: Supported
[00:00:09.273,620] <inf> net_dhcpv4: Received: 172.40.9.251
[00:00:09.273,803] <inf> net_config: IPv4 address: 172.40.9.251
[00:00:09.273,803] <inf> net_config: Lease time: 600 seconds
[00:00:09.273,864] <inf> net_config: Subnet: 255.255.240.0
[00:00:09.273,895] <inf> net_config: Router: 172.40.0.1
[00:00:09.273,986] <inf> twt: DHCP IP address: 172.40.9.251
[00:00:10.248,779] <inf> twt: AP is TWT capable, establishing TWT
[00:00:10.256,622] <inf> twt: TWT setup requested
[00:00:10.282,958] <inf> twt: TWT response: TWT accept
[00:00:10.282,958] <inf> twt: == TWT negotiated parameters ==
[00:00:10.282,989] <inf> twt: TWT Dialog token: 1
[00:00:10.282,989] <inf> twt: TWT flow ID: 1
[00:00:10.283,020] <inf> twt: TWT negotiation type: TWT individual negotiation
[00:00:10.283,020] <inf> twt: TWT responder: true
[00:00:10.283,050] <inf> twt: TWT implicit: true
[00:00:10.283,081] <inf> twt: TWT announce: false
[00:00:10.283,111] <inf> twt: TWT trigger: false
[00:00:10.283,111] <inf> twt: TWT wake interval: 65024 us
[00:00:10.283,111] <inf> twt: TWT interval: 524000 us
[00:00:10.283,111] <inf> twt: ========================
[00:00:10.283,264] <inf> twt: TWT sleep state: sleeping
[00:00:10.412,811] <inf> twt: TWT sleep state: awake
[00:00:10.477,783] <inf> twt: TWT sleep state: sleeping
[00:00:10.556,701] <inf> twt: TWT Setup success
[00:00:10.937,164] <inf> twt: TWT sleep state: awake
[00:00:11.002,258] <inf> twt: TWT sleep state: sleeping
[00:00:11.461,486] <inf> twt: TWT sleep state: awake
[00:00:11.526,672] <inf> twt: TWT sleep state: sleeping
[00:00:11.985,809] <inf> twt: TWT sleep state: awake
[00:00:12.051,086] <inf> twt: TWT sleep state: sleeping

Thanks & Regards,

Naveen P

RE: The client does not enter sleep mode as expected.

Marte Myrvold — Mon, 06 Oct 2025 12:13:28 GMT

Hi Naveen

[quote user="Naveen Pyda"]We also added the credentials in prj.conf, but the client is not connecting to the SSID.[/quote]

Did you set the credentials by changing these configs to the SSID and password for your network?

CONFIG_WIFI_CREDENTIALS_STATIC_SSID="MySSID"
CONFIG_WIFI_CREDENTIALS_STATIC_PASSWORD="MyPassword"

What kind of security does the network use? In prj.conf, in the sample I shared, I set CONFIG_WIFI_CREDENTIALS_STATIC_TYPE_PSK, which is used if a network uses a password and PSK security, which is the most standard. If your network uses something else, you need to change this config to match your network's configuration. Here you can see the different config options for this:

CONFIG_WIFI_CREDENTIALS_STATIC_TYPE_OPEN - Wi-Fi network uses no password.
CONFIG_WIFI_CREDENTIALS_STATIC_TYPE_PSK - Wi-Fi network uses a password and PSK security (default).
CONFIG_WIFI_CREDENTIALS_STATIC_TYPE_PSK_SHA256 - Wi-Fi network uses a password and PSK-256 security.
CONFIG_WIFI_CREDENTIALS_STATIC_TYPE_SAE - Wi-Fi network uses a password and SAE security.

[quote user="Naveen Pyda"]Could you please guide us on how to run the TWT setup command: wifi twt setup 0 0 2 2 0 1 1 1 2000 60000000?[/quote]

You do not need to run this command in the sample I shared, as the sample sets up TWT in the code itself:

static int setup_twt(void)
{
	struct net_if *iface = net_if_get_first_wifi();
	struct wifi_twt_params params = { 0 };
	int ret;

	twt_flow_id = 1;
	params.operation = WIFI_TWT_SETUP;
	params.negotiation_type = WIFI_TWT_INDIVIDUAL;
	params.setup_cmd = WIFI_TWT_SETUP_CMD_REQUEST;
	params.dialog_token = 1;
	params.flow_id = twt_flow_id;
	params.setup.responder = 0;
	params.setup.trigger = IS_ENABLED(CONFIG_TWT_TRIGGER_ENABLE);
	params.setup.implicit = 1;
	params.setup.announce = IS_ENABLED(CONFIG_TWT_ANNOUNCED_MODE);
	params.setup.twt_wake_interval = CONFIG_TWT_WAKE_INTERVAL;
	params.setup.twt_interval = CONFIG_TWT_INTERVAL;

	ret = net_mgmt(NET_REQUEST_WIFI_TWT, iface, &params, sizeof(params));
	if (ret) {
		LOG_INF("TWT setup failed: %d", ret);
		return ret;
	}

	LOG_INF("TWT setup requested");

	return 0;
}

When the device connects to the network, it will send a request to enable TWT on its own.

Best regards,
Marte

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Fri, 03 Oct 2025 12:57:31 GMT

Hi Marte,

First of all, thank you for explaining everything clearly.

As per your advice, we erased and flashed the new build provided by you in privacy twt.zip. We also added the credentials in prj.conf, but the client is not connecting to the SSID.

[quote userid="92402" url="~/f/nordic-q-a/124001/the-client-does-not-enter-sleep-mode-as-expected/550584"]Please build and test the application I shared (twt.zip), not the sample in the SDK. The only change you need to make is to set the credentials in prj.conf.[/quote]

Could you please guide us on how to run the TWT setup command: wifi twt setup 0 0 2 2 0 1 1 1 2000 60000000?

Please find the attached logs below:

*** Booting nRF Connect SDK v2.9.2-4ab7b98fc76f ***
*** Using Zephyr OS v3.7.99-aa34a5632971 ***
[00:00:00.271,972] <inf> net_config: Initializing network
[00:00:00.272,003] <inf> net_config: Waiting interface 1 (0x20001080) to be up...
[00:00:00.272,155] <inf> net_config: IPv4 address: 192.168.1.99
[00:00:00.272,216] <inf> net_config: Running dhcpv4 client...
[00:00:00.272,460] <inf> twt: Starting nrf7002dk with CPU frequency: 64 MHz
[00:00:00.274,291] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:00.277,221] <err> wifi_nrf: nrf_wifi_wpa_supp_set_key: rpu_ctx_zep is NULL
[00:00:00.277,252] <err> wifi_nrf: nrf_wifi_wpa_supp_set_key: rpu_ctx_zep is NULL
[00:00:00.277,282] <err> wifi_nrf: nrf_wifi_wpa_supp_set_key: rpu_ctx_zep is NULL
[00:00:00.277,313] <err> wifi_nrf: nrf_wifi_wpa_supp_set_key: rpu_ctx_zep is NULL
[00:00:00.277,313] <err> wifi_nrf: nrf_wifi_wpa_supp_set_key: rpu_ctx_zep is NULL
[00:00:00.277,343] <err> wifi_nrf: nrf_wifi_wpa_supp_set_key: rpu_ctx_zep is NULL
[00:00:01.272,583] <inf> twt: Static IP address (overridable): 192.168.1.99/255.255.255.0 -> 192.168.1.1
[00:00:03.191,375] <err> wifi_nrf: nrf_wifi_wpa_supp_scan2: RPU context not initialized
[00:00:03.192,871] <err> wifi_nrf: nrf_wifi_wpa_supp_scan2: RPU context not initialized
[00:00:03.193,145] <inf> wifi_mgmt_ext: Connection requested
[00:00:03.193,176] <inf> twt: Connection requested
[00:00:03.193,237] <inf> twt: ==================
[00:00:03.193,267] <inf> twt: State: DISCONNECTED
[00:00:03.493,408] <inf> twt: ==================
[00:00:03.493,438] <inf> twt: State: DISCONNECTED
[00:00:03.793,579] <inf> twt: ==================
[00:00:03.793,579] <inf> twt: State: DISCONNECTED
[00:00:04.093,750] <inf> twt: ==================
[00:00:04.093,750] <inf> twt: State: DISCONNECTED
[00:00:04.193,603] <err> wifi_nrf: nrf_wifi_wpa_supp_scan2: RPU context not initialized
[00:00:04.393,920] <inf> twt: ==================
[00:00:04.393,951] <inf> twt: State: DISCONNECTED
[00:00:04.694,122] <inf> twt: ==================
[00:00:04.694,152] <inf> twt: State: DISCONNECTED
[00:00:04.994,293] <inf> twt: ==================
[00:00:04.994,293] <inf> twt: State: DISCONNECTED
[00:00:05.194,305] <err> wifi_nrf: nrf_wifi_wpa_supp_scan2: RPU context not initialized
[00:00:05.294,464] <inf> twt: ==================
[00:00:05.294,494] <inf> twt: State: DISCONNECTED
[00:00:05.594,635] <inf> twt: ==================
[00:00:05.594,635] <inf> twt: State: DISCONNECTED
[00:00:05.894,836] <inf> twt: ==================
[00:00:05.894,866] <inf> twt: State: DISCONNECTED
[00:00:06.195,068] <err> wifi_nrf: nrf_wifi_wpa_supp_scan2: RPU context not initialized
[00:00:06.195,343] <inf> twt: ==================
[00:00:06.195,343] <inf> twt: State: DISCONNECTED
[00:00:06.495,513] <inf> twt: ==================
[00:00:06.495,513] <inf> twt: State: DISCONNECTED
[00:00:06.795,684] <inf> twt: ==================
[00:00:06.795,684] <inf> twt: State: DISCONNECTED
[00:00:07.095,886] <inf> twt: ==================
[00:00:07.095,916] <inf> twt: State: DISCONNECTED

Thanks & Regards,

Naveen P

RE: The client does not enter sleep mode as expected.

Marte Myrvold — Fri, 03 Oct 2025 11:47:42 GMT

Hi Naveen,

[quote user="Naveen Pyda"]As you advised, we made the same changes in ncs/v2.9.2/nrf/samples/wifi/twt/src/main.c[/quote][quote user="Naveen Pyda"]All files were replaced with the twt.zip files in the path ncs/v2.9.2/nrf/samples/wifi/twt/. After that, we flashed the build using the commands below:[/quote]

Please build and test the application I shared (twt.zip), not the sample in the SDK. The only change you need to make is to set the credentials in prj.conf.

[quote user="Naveen Pyda"]but we are not receiving any logs from the client side. I had previously shared screenshots and logs for this issue.[/quote]

Just to make sure I understand correctly, do you not get any logs at all? With the TWT application I attached, you should get logs like this:

*** Booting nRF Connect SDK v2.9.2-4ab7b98fc76f ***
*** Using Zephyr OS v3.7.99-aa34a5632971 ***
[00:00:00.665,954] <inf> net_config: Initializing network
[00:00:00.665,954] <inf> net_config: Waiting interface 1 (0x20001080) to be up...
[00:00:00.666,107] <inf> net_config: IPv4 address: 192.168.1.99
[00:00:00.666,168] <inf> net_config: Running dhcpv4 client...
[00:00:00.666,412] <inf> twt: Starting nrf7002dk with CPU frequency: 64 MHz
[00:00:00.668,273] <inf> wifi_supplicant: wpa_supplicant initialized
[00:00:01.666,534] <inf> twt: Static IP address (overridable): 192.168.1.99/255.255.255.0 -> 192.168.1.1
[00:00:03.595,886] <inf> wifi_mgmt_ext: Connection requested
[00:00:03.595,916] <inf> twt: Connection requested
[00:00:03.595,977] <inf> twt: ==================
[00:00:03.596,008] <inf> twt: State: SCANNING
[00:00:03.896,148] <inf> twt: ==================
[00:00:03.896,179] <inf> twt: State: SCANNING
[00:00:04.196,350] <inf> twt: ==================
[00:00:04.196,350] <inf> twt: State: SCANNING
[00:00:04.496,520] <inf> twt: ==================
[00:00:04.496,520] <inf> twt: State: SCANNING
[00:00:04.796,691] <inf> twt: ==================
[00:00:04.796,722] <inf> twt: State: SCANNING
[00:00:05.096,862] <inf> twt: ==================
[00:00:05.096,893] <inf> twt: State: SCANNING
[00:00:05.397,033] <inf> twt: ==================
[00:00:05.397,064] <inf> twt: State: SCANNING
[00:00:05.697,204] <inf> twt: ==================
[00:00:05.697,235] <inf> twt: State: SCANNING
[00:00:05.997,375] <inf> twt: ==================
[00:00:05.997,406] <inf> twt: State: SCANNING
[00:00:06.297,576] <inf> twt: ==================
[00:00:06.297,607] <inf> twt: State: SCANNING
[00:00:06.597,747] <inf> twt: ==================
[00:00:06.597,778] <inf> twt: State: SCANNING
[00:00:06.897,918] <inf> twt: ==================
[00:00:06.897,949] <inf> twt: State: SCANNING
[00:00:07.198,089] <inf> twt: ==================
[00:00:07.198,120] <inf> twt: State: SCANNING
[00:00:07.498,291] <inf> twt: ==================
[00:00:07.498,321] <inf> twt: State: SCANNING
[00:00:07.798,461] <inf> twt: ==================
[00:00:07.798,492] <inf> twt: State: SCANNING
[00:00:08.098,632] <inf> twt: ==================
[00:00:08.098,663] <inf> twt: State: SCANNING
[00:00:08.398,803] <inf> twt: ==================
[00:00:08.398,834] <inf> twt: State: AUTHENTICATING
[00:00:08.631,469] <inf> twt: Connected
[00:00:08.706,115] <inf> twt: ==================
[00:00:08.706,146] <inf> twt: State: COMPLETED
[00:00:08.706,176] <inf> twt: Interface Mode: STATION
[00:00:08.706,207] <inf> twt: Link Mode: WIFI 6 (802.11ax/HE)
[00:00:08.706,207] <inf> twt: SSID: <SSID>
[00:00:08.706,237] <inf> twt: BSSID: FC:34:97:0B:F6:DC
[00:00:08.706,268] <inf> twt: Band: 5GHz
[00:00:08.706,268] <inf> twt: Channel: 44
[00:00:08.706,298] <inf> twt: Security: WPA2-PSK
[00:00:08.706,329] <inf> twt: MFP: Optional
[00:00:08.706,329] <inf> twt: RSSI: -64
[00:00:08.706,329] <inf> twt: TWT: Supported
[00:00:10.706,420] <inf> twt: AP is TWT capable, establishing TWT
[00:00:10.721,038] <inf> twt: TWT setup requested
[00:00:10.807,250] <inf> twt: TWT response: TWT accept
[00:00:10.807,250] <inf> twt: == TWT negotiated parameters ==
[00:00:10.807,250] <inf> twt: TWT Dialog token: 1
[00:00:10.807,281] <inf> twt: TWT flow ID: 0
[00:00:10.807,312] <inf> twt: TWT negotiation type: TWT individual negotiation
[00:00:10.807,312] <inf> twt: TWT responder: true
[00:00:10.807,342] <inf> twt: TWT implicit: true
[00:00:10.807,373] <inf> twt: TWT announce: false
[00:00:10.807,403] <inf> twt: TWT trigger: false
[00:00:10.807,403] <inf> twt: TWT wake interval: 65024 us
[00:00:10.807,403] <inf> twt: TWT interval: 524000 us
[00:00:10.807,434] <inf> twt: ========================
[00:00:10.807,556] <inf> twt: TWT sleep state: sleeping
[00:00:10.911,285] <inf> twt: TWT sleep state: awake
[00:00:10.976,074] <inf> twt: TWT sleep state: sleeping
[00:00:11.021,148] <inf> twt: TWT Setup success
[00:00:11.435,577] <inf> twt: TWT sleep state: awake
[00:00:11.500,457] <inf> twt: TWT sleep state: sleeping
[00:00:11.959,838] <inf> twt: TWT sleep state: awake
[00:00:12.024,871] <inf> twt: TWT sleep state: sleeping
[00:00:12.484,161] <inf> twt: TWT sleep state: awake
[00:00:12.549,255] <inf> twt: TWT sleep state: sleeping
[00:00:13.008,453] <inf> twt: TWT sleep state: awake
[00:00:13.028,564] <inf> net_dhcpv4: Received: 192.168.32.104
[00:00:13.028,747] <inf> net_config: IPv4 address: 192.168.32.104
[00:00:13.028,778] <inf> net_config: Lease time: 36000 seconds
[00:00:13.028,808] <inf> net_config: Subnet: 255.255.255.0
[00:00:13.028,839] <inf> net_config: Router: 192.168.32.1
[00:00:13.028,961] <inf> twt: DHCP IP address: 192.168.32.104
[00:00:13.077,911] <inf> twt: TWT sleep state: sleeping
[00:00:13.532,714] <inf> twt: TWT sleep state: awake
[00:00:13.598,052] <inf> twt: TWT sleep state: sleeping
[00:00:14.057,037] <inf> twt: TWT sleep state: awake
[00:00:14.122,467] <inf> twt: TWT sleep state: sleeping
[00:00:14.581,329] <inf> twt: TWT sleep state: awake
[00:00:14.646,881] <inf> twt: TWT sleep state: sleeping
[00:00:15.106,353] <inf> twt: TWT sleep state: awake
[00:00:15.171,264] <inf> twt: TWT sleep state: sleeping
[00:00:15.629,882] <inf> twt: TWT sleep state: awake
[00:00:15.695,648] <inf> twt: TWT sleep state: sleeping
[00:00:16.154,174] <inf> twt: TWT sleep state: awake
[00:00:16.220,001] <inf> twt: TWT sleep state: sleeping
[00:00:16.678,436] <inf> twt: TWT sleep state: awake
[00:00:16.744,628] <inf> twt: TWT sleep state: sleeping
[00:00:17.202,697] <inf> twt: TWT sleep state: awake
[00:00:17.268,737] <inf> twt: TWT sleep state: sleeping
[00:00:17.726,959] <inf> twt: TWT sleep state: awake

[quote user="Naveen Pyda"]We have a little bit of confusion about this. Actually, we are connecting the Nordic device through the terminal in VS Code. You can see below attached screenshot.[/quote]

My question was related to which sample you built and flashed to your board, not how you connect to the serial port on the device.

[quote user="Naveen Pyda"]We flashed the build in both the shell and twt paths.[/quote]

Are you flashing both the TWT sample and shell sample to the nRF7002 DK? These are two separate samples, and you should only flash one at a time. If you flash one sample first and then the other, the last sample will overwrite the first sample you flashed.

[quote user="Naveen Pyda"]2.westflash[/quote]

Please use this to make sure you erase everything on the device:

west flash --recover

Best regards,
Marte

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Wed, 01 Oct 2025 10:07:03 GMT

Hi Marte,

[quote userid="92402" url="~/f/nordic-q-a/124001/the-client-does-not-enter-sleep-mode-as-expected/550217"]

However, we are still not seeing the expected logs.

Was this with the Wi-Fi TWT sample or the Wi-Fi shell sample?

[/quote]

We have a little bit of confusion about this. Actually, we are connecting the Nordic device through the terminal in VS Code. You can see below attached screenshot.

[quote userid="147707" url="~/f/nordic-q-a/124001/the-client-does-not-enter-sleep-mode-as-expected/550296"]We will try the twt.zip. If we find any solution or face any issue, I will let you know.[/quote]

All files were replaced with the twt.zip files in the path ncs/v2.9.2/nrf/samples/wifi/twt/. After that, we flashed the build using the commands below:

1.west build -p always -b nrf7002dk/nrf5340/cpuapp

2.westflash

We flashed the build in both the shell and twt paths.

Still, we are not able to see the logs as expected. You can see below attached screenshot.

Thanks & Regards,

Naveen P

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Wed, 01 Oct 2025 07:56:48 GMT

Hi Marte,

As you mentioned, the details of the AP are: Ruckus-R770, SSID: TWT, Password: naveen123. The AP supports TWT power save.

As you advised, we made the same changes in ncs/v2.9.2/nrf/samples/wifi/twt/src/main.c, but we are not receiving any logs from the client side. I had previously shared screenshots and logs for this issue.

[quote userid="147707" url="~/f/nordic-q-a/124001/the-client-does-not-enter-sleep-mode-as-expected/549181"]

As you advised, we followed the steps to collect the logs, but we are still not able to see the logs as expected.Please find the attached screenshot for your reference.

[/quote]

The version of the nRF7002 DK is 1.0.2.

We will try the twt.zip. If we find any solution or face any issue, I will let you know.

Thanks & Regards,

Naveen P

RE: The client does not enter sleep mode as expected.

Marte Myrvold — Tue, 30 Sep 2025 13:59:55 GMT

Hi,

[quote user="Naveen Pyda"]However, we are still not seeing the expected logs. [/quote]

Was this with the Wi-Fi TWT sample or the Wi-Fi shell sample?

[quote user="Naveen Pyda"]I tried with another AP as well, but we are still facing the same issue I mentioned earlier.[/quote]

Please provide the details of the AP you tested with. Additionally, make sure that TWT is enabled in the AP settings.

I have attached a version of the TWT sample without the traffic generator and TWT teardown. Can you test this and send the logs?

Please also share which version of the nRF7002 DK you are using. The version is the line under "PCA10143" on the sticker on the DK.

Best regards,
Marte

devzone.nordicsemi.com/.../twt.zip

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Mon, 29 Sep 2025 09:32:48 GMT

Hi Marte,

Any updates on this?

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Fri, 26 Sep 2025 04:42:42 GMT

Hi Merta,

Any updates on this?

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Thu, 25 Sep 2025 06:09:26 GMT

Hi Merta,

I tried with another AP as well, but we are still facing the same issue I mentioned earlier.

Please find the attached the client-side logs and screenshot for your reference.

uart:~$ wifi status
Status: successful
==================
State: COMPLETED
Interface Mode: STATION
Link Mode: WIFI 6 (802.11ax/HE)
SSID: TWT
BSSID: 00:33:58:6B:81:82
Band: 2.4GHz
Channel: 1
Security: WPA2-PSK
MFP: Optional
RSSI: -40
Beacon Interval: 100
DTIM: 1
TWT: Supported
Current PHY rate : 1000

uart:~$ wifi twt setup 0 0 1 0 0 0 1 1 10000 1000000 100
TWT operation TWT setup with dg: 1, flow_id: 0 requested
TWT response: TWT accept
== TWT negotiated parameters ==
TWT Dialog token: 1
TWT flow ID: 1
TWT negotiation type: TWT individual negotiation
TWT responder: true
TWT implicit: true
TWT announce: true
TWT trigger: false
TWT wake interval: 9984 us
TWT interval: 1000000 us

Thanks & Regards,

Naveen P

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Thu, 25 Sep 2025 05:26:53 GMT

Hi Merta,

Any updates on this?

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Wed, 24 Sep 2025 05:34:10 GMT

Hi Marte,

Please respond. We are waiting for your reply.

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Tue, 23 Sep 2025 08:08:05 GMT

Hi Mate,

As per your advice, we made the same changes in the script, and the flash build completed successfully. However, we are still not seeing the expected logs. After enabling TWT power save, the client only sends PS-Poll frames.

The following command was used:

wifi twt setup 0 0 1 0 0 0 1 1 10000 1000000 100

Please find the attached PCaps for your reference.

https://drive.google.com/file/d/1H2-U1TbJMtUYYoJxIF3my1jbIpdYBWpn/view?usp=sharing

Thanks & Regards,

Naveen P

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Mon, 22 Sep 2025 12:51:02 GMT

Hi Marte,

As you advised, we made the same changes in the script, but when we tried to flash, it failed with an error. Please find the attached logs for your reference.

FAILED: CMakeFiles/app.dir/src/main.c.obj
C:\ncs\toolchains\b620d30767\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe -DKERNEL -DK_HEAP_MEM_POOL_SIZE=213024 -DMBEDTLS_CONFIG_FILE=\"nrf-config.h\" -DMBEDTLS_PSA_CRYPTO_CONFIG_FILE=\"nrf-psa-crypto-config.h\" -DMBEDTLS_PSA_CRYPTO_USER_CONFIG_FILE=\"nrf-psa-crypto-user-config.h\" -DNRF52_ERRATA_215_ENABLE_WORKAROUND=0 -DNRF5340_XXAA_APPLICATION -DNRF53_ERRATA_159_ENABLE_WORKAROUND=0 -DNRF53_ERRATA_43_ENABLE_WORKAROUND=0 -DNRF70_ANT_GAIN_2G=0 -DNRF70_ANT_GAIN_5G_BAND1=0 -DNRF70_ANT_GAIN_5G_BAND2=0 -DNRF70_ANT_GAIN_5G_BAND3=0 -DNRF70_BAND_2G_LOWER_EDGE_BACKOFF_DSSS=0 -DNRF70_BAND_2G_LOWER_EDGE_BACKOFF_HE=0 -DNRF70_BAND_2G_LOWER_EDGE_BACKOFF_HT=0 -DNRF70_BAND_2G_UPPER_EDGE_BACKOFF_DSSS=0 -DNRF70_BAND_2G_UPPER_EDGE_BACKOFF_HE=0 -DNRF70_BAND_2G_UPPER_EDGE_BACKOFF_HT=0 -DNRF70_BAND_UNII_1_LOWER_EDGE_BACKOFF_HE=0 -DNRF70_BAND_UNII_1_LOWER_EDGE_BACKOFF_HT=0 -DNRF70_BAND_UNII_1_UPPER_EDGE_BACKOFF_HE=0 -DNRF70_BAND_UNII_1_UPPER_EDGE_BACKOFF_HT=0 -DNRF70_BAND_UNII_2A_LOWER_EDGE_BACKOFF_HE=0 -DNRF70_BAND_UNII_2A_LOWER_EDGE_BACKOFF_HT=0 -DNRF70_BAND_UNII_2A_UPPER_EDGE_BACKOFF_HE=0 -DNRF70_BAND_UNII_2A_UPPER_EDGE_BACKOFF_HT=0 -DNRF70_BAND_UNII_2C_LOWER_EDGE_BACKOFF_HE=0 -DNRF70_BAND_UNII_2C_LOWER_EDGE_BACKOFF_HT=0 -DNRF70_BAND_UNII_2C_UPPER_EDGE_BACKOFF_HE=0 -DNRF70_BAND_UNII_2C_UPPER_EDGE_BACKOFF_HT=0 -DNRF70_BAND_UNII_3_LOWER_EDGE_BACKOFF_HE=0 -DNRF70_BAND_UNII_3_LOWER_EDGE_BACKOFF_HT=0 -DNRF70_BAND_UNII_3_UPPER_EDGE_BACKOFF_HE=0 -DNRF70_BAND_UNII_3_UPPER_EDGE_BACKOFF_HT=0 -DNRF70_BAND_UNII_4_LOWER_EDGE_BACKOFF_HE=0 -DNRF70_BAND_UNII_4_LOWER_EDGE_BACKOFF_HT=0 -DNRF70_BAND_UNII_4_UPPER_EDGE_BACKOFF_HE=0 -DNRF70_BAND_UNII_4_UPPER_EDGE_BACKOFF_HT=0 -DNRF70_DATA_TX -DNRF70_LOG_VERBOSE -DNRF70_MAX_TX_PENDING_QLEN=18 -DNRF70_MAX_TX_TOKENS=10 -DNRF70_PCB_LOSS_2G=0 -DNRF70_PCB_LOSS_5G_BAND1=0 -DNRF70_PCB_LOSS_5G_BAND2=0 -DNRF70_PCB_LOSS_5G_BAND3=0 -DNRF70_REG_DOMAIN=00 -DNRF70_RPU_PS_IDLE_TIMEOUT_MS=10 -DNRF70_RX_MAX_DATA_SIZE=1600 -DNRF70_RX_NUM_BUFS=48 -DNRF70_STA_MODE -DNRF70_SYSTEM_MODE -DNRF70_TCP_IP_CHECKSUM_OFFLOAD -DNRF_SKIP_FICR_NS_COPY_TO_RAM -DNRF_WIFI_AP_DEAD_DETECT_TIMEOUT=20 -DNRF_WIFI_IFACE_MTU=1500 -DNRF_WIFI_LOW_POWER -DNRF_WIFI_MGMT_BUFF_OFFLOAD -DNRF_WIFI_PS_INT_PS=y -DNRF_WIFI_RPU_RECOVERY -DNRF_WIFI_RPU_RECOVERY_PS_ACTIVE_TIMEOUT_MS=50000 -DPICOLIBC_LONG_LONG_PRINTF_SCANF -DUSE_PARTITION_MANAGER=1 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR__=1 -IC:/ncs/v2.9.2/zephyr/subsys/net/ip -IC:/ncs/v2.9.2/nrf/samples/wifi/twt/modules/traffic_gen/inc -IC:/ncs/v2.9.2/nrf/samples/wifi/twt/build/twt/zephyr/include/generated/zephyr -IC:/ncs/v2.9.2/zephyr/include -IC:/ncs/v2.9.2/nrf/samples/wifi/twt/build/twt/zephyr/include/generated -IC:/ncs/v2.9.2/zephyr/soc/nordic -IC:/ncs/v2.9.2/zephyr/include/zephyr/posix -IC:/ncs/v2.9.2/zephyr/soc/nordic/nrf53/. -IC:/ncs/v2.9.2/zephyr/soc/nordic/common/. -IC:/ncs/v2.9.2/zephyr/subsys/net/l2 -IC:/ncs/v2.9.2/zephyr/drivers/wifi/nrf_wifi/inc -IC:/ncs/v2.9.2/nrf/include -IC:/ncs/v2.9.2/nrf/samples/wifi/twt/build/twt/zephyr/misc/generated -IC:/ncs/v2.9.2/modules/lib/hostap/port/mbedtls -IC:/ncs/v2.9.2/nrf/tests/include -IC:/ncs/v2.9.2/modules/hal/cmsis/CMSIS/Core/Include -IC:/ncs/v2.9.2/zephyr/modules/cmsis/. -IC:/ncs/v2.9.2/modules/hal/nordic/nrfx -IC:/ncs/v2.9.2/modules/hal/nordic/nrfx/drivers/include -IC:/ncs/v2.9.2/modules/hal/nordic/nrfx/mdk -IC:/ncs/v2.9.2/zephyr/modules/hal_nordic/nrfx/. -IC:/ncs/v2.9.2/zephyr/modules/hostap/src -IC:/ncs/v2.9.2/modules/lib/hostap -IC:/ncs/v2.9.2/modules/lib/hostap/wpa_supplicant -IC:/ncs/v2.9.2/modules/lib/hostap/src -IC:/ncs/v2.9.2/modules/lib/hostap/src/common -IC:/ncs/v2.9.2/modules/lib/hostap/src/eap_common -IC:/ncs/v2.9.2/modules/lib/hostap/src/eap_server -IC:/ncs/v2.9.2/modules/lib/hostap/src/radius -IC:/ncs/v2.9.2/modules/lib/hostap/src/crypto -IC:/ncs/v2.9.2/modules/lib/hostap/src/ap -IC:/ncs/v2.9.2/modules/lib/hostap/src/drivers -IC:/ncs/v2.9.2/modules/lib/hostap/src/rsn_supp -IC:/ncs/v2.9.2/nrf/samples/wifi/twt/build/twt/generated/library_nrf_security_psa -IC:/ncs/v2.9.2/nrf/subsys/nrf_security/include -IC:/ncs/v2.9.2/nrf/subsys/nrf_security/src/threading/include -IC:/ncs/v2.9.2/nrf/subsys/nrf_security/src/utils -IC:/ncs/v2.9.2/modules/crypto/oberon-psa-crypto/oberon/drivers -IC:/ncs/v2.9.2/modules/crypto/oberon-psa-crypto/include -IC:/ncs/v2.9.2/modules/crypto/oberon-psa-crypto/library -IC:/ncs/v2.9.2/modules/crypto/mbedtls/library -IC:/ncs/v2.9.2/modules/crypto/mbedtls/include -IC:/ncs/v2.9.2/modules/crypto/mbedtls/include/library -IC:/ncs/v2.9.2/nrfxlib/crypto/nrf_oberon/include -IC:/ncs/v2.9.2/nrfxlib/crypto/nrf_oberon/include/mbedtls -IC:/ncs/v2.9.2/zephyr/modules/nrf_wifi/os -IC:/ncs/v2.9.2/zephyr/modules/nrf_wifi/os/../bus -IC:/ncs/v2.9.2/modules/lib/nrf_wifi/utils/inc -IC:/ncs/v2.9.2/modules/lib/nrf_wifi/os_if/inc -IC:/ncs/v2.9.2/modules/lib/nrf_wifi/bus_if/bus/qspi/inc -IC:/ncs/v2.9.2/modules/lib/nrf_wifi/bus_if/bal/inc -IC:/ncs/v2.9.2/modules/lib/nrf_wifi/fw_if/umac_if/inc -IC:/ncs/v2.9.2/modules/lib/nrf_wifi/fw_load/mips/fw/inc -IC:/ncs/v2.9.2/modules/lib/nrf_wifi/hw_if/hal/inc -IC:/ncs/v2.9.2/modules/lib/nrf_wifi/hw_if/hal/inc/fw -IC:/ncs/v2.9.2/modules/lib/nrf_wifi/fw_if/umac_if/inc/fw -IC:/ncs/v2.9.2/modules/lib/nrf_wifi/fw_if/umac_if/inc/default -isystem C:/ncs/v2.9.2/zephyr/lib/libc/common/include -isystem C:/ncs/v2.9.2/nrfxlib/crypto/nrf_cc312_platform/include -Os -DNDEBUG -fno-strict-aliasing -Os -imacros C:/ncs/v2.9.2/nrf/samples/wifi/twt/build/twt/zephyr/include/generated/zephyr/autoconf.h -fno-printf-return-value -fno-common -g -gdwarf-4 -fdiagnostics-color=always -mcpu=cortex-m33 -mthumb -mabi=aapcs -mfp16-format=ieee -mtp=soft --sysroot=C:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi -imacros C:/ncs/v2.9.2/zephyr/include/zephyr/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wdouble-promotion -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -Werror=implicit-int -fno-pic -fno-pie -fno-asynchronous-unwind-tables -ftls-model=local-exec -fno-reorder-functions --param=min-pagesize=0 -fno-defer-pop -fmacro-prefix-map=C:/ncs/v2.9.2/nrf/samples/wifi/twt=CMAKE_SOURCE_DIR -fmacro-prefix-map=C:/ncs/v2.9.2/zephyr=ZEPHYR_BASE -fmacro-prefix-map=C:/ncs/v2.9.2=WEST_TOPDIR -ffunction-sections -fdata-sections -specs=picolibc.specs -D_POSIX_THREADS -std=c99 -MD -MT CMakeFiles/app.dir/src/main.c.obj -MF CMakeFiles\app.dir\src\main.c.obj.d -o CMakeFiles/app.dir/src/main.c.obj -c C:/ncs/v2.9.2/nrf/samples/wifi/twt/src/main.c
C:/ncs/v2.9.2/nrf/samples/wifi/twt/src/main.c: In function 'main':
C:/ncs/v2.9.2/nrf/samples/wifi/twt/src/main.c:426:25: warning: implicit declaration of function 'traffic_gen_init'; did you mean 'traffic_gen_stop'? [-Wimplicit-function-declaration]
426 | traffic_gen_init(&tg_config);
| ^~~~~~~~~~~~~~~~
| traffic_gen_stop
C:/ncs/v2.9.2/nrf/samples/wifi/twt/src/main.c:428:29: error: void value not ignored as it ought to be
428 | ret = traffic_gen_start(&tg_config);
| ^
C:/ncs/v2.9.2/nrf/samples/wifi/twt/src/main.c:434:31: warning: implicit declaration of function 'traffic_gen_wait_for_report' [-Wimplicit-function-declaration]
434 | ret = traffic_gen_wait_for_report(&tg_config);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
C:/ncs/v2.9.2/nrf/samples/wifi/twt/src/main.c:439:25: warning: implicit declaration of function 'traffic_gen_get_report'; did you mean 'traffic_gen_start'? [-Wimplicit-function-declaration]
439 | traffic_gen_get_report(&tg_config);
| ^~~~~~~~~~~~~~~~~~~~~~
| traffic_gen_start
[244/457] Building C object zephyr/subsys/net/ip/CMakeFiles/subsys__net__ip.dir/tcp.c.obj
ninja: build stopped: subcommand failed.
FAILED: _sysbuild/sysbuild/images/twt-prefix/src/twt-stamp/twt-build C:/ncs/v2.9.2/nrf/samples/wifi/twt/build/_sysbuild/sysbuild/images/twt-prefix/src/twt-stamp/twt-build
cmd.exe /C "cd /D C:\ncs\v2.9.2\nrf\samples\wifi\twt\build\twt && C:\ncs\toolchains\b620d30767\opt\bin\cmake.exe --build ."
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\b620d30767\opt\bin\cmake.EXE' --build C:/ncs/v2.9.2/nrf/samples/wifi/twt/build

Thanks & Regards,

Naveen P

RE: The client does not enter sleep mode as expected.

Marte Myrvold — Fri, 19 Sep 2025 12:05:45 GMT

Hi Naveen,

The ifdef for CONFIG_SCHEDULED_TX should not have been included in the previous function, so I apologize for that.
Please try this instead:

static void wifi_mgmt_event_handler(struct net_mgmt_event_callback *cb,
				     uint32_t mgmt_event, struct net_if *iface)
{
	switch (mgmt_event) {
	case NET_EVENT_WIFI_CONNECT_RESULT:
		handle_wifi_connect_result(cb);
		break;
	case NET_EVENT_WIFI_DISCONNECT_RESULT:
		handle_wifi_disconnect_result(cb);
		break;
	case NET_EVENT_WIFI_TWT:
		handle_wifi_twt_event(cb);
		break;
	case NET_EVENT_WIFI_TWT_SLEEP_STATE: {
		int *twt_state;

		twt_state = (int *)(cb->info);
		LOG_INF("TWT sleep state: %s", *twt_state ? "awake" : "sleeping" );
		if (*twt_state == WIFI_TWT_STATE_SLEEP) {
			traffic_gen_pause(&tg_config);
		} else if (*twt_state == WIFI_TWT_STATE_AWAKE)  {
			traffic_gen_resume(&tg_config);
		} else {
			LOG_INF("UNKNOWN TWT STATE %d", *twt_state);
		}
	}
		break;
	default:
		break;
	}
}

You can also remove the traffic_gen_pause() and traffic_gen_resume() functions. The most important part is to log the sleep state:

static void wifi_mgmt_event_handler(struct net_mgmt_event_callback *cb,
				     uint32_t mgmt_event, struct net_if *iface)
{
	switch (mgmt_event) {
	case NET_EVENT_WIFI_CONNECT_RESULT:
		handle_wifi_connect_result(cb);
		break;
	case NET_EVENT_WIFI_DISCONNECT_RESULT:
		handle_wifi_disconnect_result(cb);
		break;
	case NET_EVENT_WIFI_TWT:
		handle_wifi_twt_event(cb);
		break;
	case NET_EVENT_WIFI_TWT_SLEEP_STATE: {
		int *twt_state;

		twt_state = (int *)(cb->info);
		LOG_INF("TWT sleep state: %s", *twt_state ? "awake" : "sleeping" );
	}
		break;
	default:
		break;
	}
}

Best regards,
Marte

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Thu, 18 Sep 2025 12:41:01 GMT

Hi Marte,

As you advised, we followed the steps to collect the logs, but we are still not able to see the logs as expected.Please find the attached screenshot for your reference.

Additionally, we do not have a PPK2 device available to measure power consumption.

Thanks & Regards,

Naveen P

RE: The client does not enter sleep mode as expected.

Marte Myrvold — Thu, 18 Sep 2025 07:52:21 GMT

Hi Naveen,

If you add logging inside NET_EVENT_WIFI_TWT_SLEEP_STATE you should be able to see if it enters sleep state. For example, you can add this line after retrieving the twt_state:

LOG_INF("TWT sleep state: %s", *twt_state ? "awake" : "sleeping" );

So the full function will look like this:

static void wifi_mgmt_event_handler(struct net_mgmt_event_callback *cb,
				     uint32_t mgmt_event, struct net_if *iface)
{
	switch (mgmt_event) {
	case NET_EVENT_WIFI_CONNECT_RESULT:
		handle_wifi_connect_result(cb);
		break;
	case NET_EVENT_WIFI_DISCONNECT_RESULT:
		handle_wifi_disconnect_result(cb);
		break;
	case NET_EVENT_WIFI_TWT:
		handle_wifi_twt_event(cb);
		break;
#ifdef CONFIG_SCHEDULED_TX
	case NET_EVENT_WIFI_TWT_SLEEP_STATE: {
		int *twt_state;

		twt_state = (int *)(cb->info);
		LOG_INF("TWT sleep state: %s", *twt_state ? "awake" : "sleeping" );
		if (*twt_state == WIFI_TWT_STATE_SLEEP) {
			traffic_gen_pause(&tg_config);
		} else if (*twt_state == WIFI_TWT_STATE_AWAKE)  {
			traffic_gen_resume(&tg_config);
		} else {
			LOG_INF("UNKNOWN TWT STATE %d", *twt_state);
		}
	}
		break;
#endif
	default:
		break;
	}
}

With this, you should see log similar to this, which shows that the device enters sleep state:

TWT sleep state: sleeping
TWT sleep state: awake
TWT sleep state: sleeping
TWT sleep state: awake
TWT sleep state: sleeping

However, the best way to test whether it goes into sleep mode is to measure power consumption. If you have a PPK2 or another tool for measuring power consumption, I recommend doing so. The power consumption should look similar to this if it enters sleep mode:

Best regards,
Marte

RE: The client does not enter sleep mode as expected.

Naveen Pyda — Thu, 18 Sep 2025 05:03:12 GMT

Hi Marte,

Please find the attached screenshot for your reference .