https://devzone.nordicsemi.com/f/nordic-q-a/124990/set-get-tx-power-failEnvironment : nRF52833, NCS v3.1.1 Hi. I evaluate PAwR project in my Solution. PAwR is Fine. But get/set Tx Power is issue. before add PAwR, My solution used common Advertising. In this Time. before start advertising, get/set Tx Power is availableen-USTelligent Community 13Thu, 16 Oct 2025 08:29:36 GMThttps://devzone.nordicsemi.com/thread/551675?ContentTypeID=1Thu, 16 Oct 2025 08:29:36 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ff71b1e9-03ba-425f-87c0-e8ea7f52de14BEN_HBC<p>Thank you! . Issue is solved.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/551660?ContentTypeID=1Thu, 16 Oct 2025 06:49:47 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a8dd47d9-cf88-4194-be83-1808fc8d6cedSusheel Nuguru<p>Hi Ben,&nbsp;</p> <p>When PAwR gets enabled, the stack switches over to extended advertising, and that changes how the controller handles the advertising identifiers. In the old setup, legacy advertising always used handle 0 by default, so anything referring to that handle worked without any extra steps.</p> <p>With extended advertising, there is no built-in handle anymore. Each advertising set gets its own handle once you create it with bt_le_ext_adv_create(). If the TX power command runs before that set exists, or if it still tries to use handle 0, the controller&nbsp;would not know which advertising set you’re referring to and replies with status 0x42 (“Unknown Advertising Identifier”).</p> <p>The fix is to create the extended advertising set first, get the handle that the controller gives you, and use that when setting or reading the TX power.</p><div style="clear:both;"></div>