NUS bt_nus_send() returns -ENOTCONN (-128) after pairing with nRF Toolbox — client never subscribes to TX notifications (NCS v3.2.4)

RE: NUS bt_nus_send() returns -ENOTCONN (-128) after pairing with nRF Toolbox — client never subscribes to TX notifications (NCS v3.2.4)

Julian1999 — Thu, 07 May 2026 07:20:47 GMT

Hello Edvin,

Thank you for your message.

I’m already in contact with Aleksander from the mobile team via the GitHub issue on the Android-nRF-Toolbox repository.

Hopefully this can be addressed in a future update, as it would be very useful to test Nordic UART Service (NUS) functionality with security enabled directly through the Toolbox app.

Best regards,
Julian

RE: NUS bt_nus_send() returns -ENOTCONN (-128) after pairing with nRF Toolbox — client never subscribes to TX notifications (NCS v3.2.4)

Edvin — Wed, 06 May 2026 20:53:07 GMT

Hello,

I believe you found the source of the issue. I do also believe this application hasn't been changed since the nRF5 SDK (the NUS part at least). I see that there are commits coming from 10 months ago, but those are mainly migration of libraries, and not functional changes.

Back in the nRF5 SDK, the NUS sample didn't have security, and this is probably why it is not taken into consideration in the nRF Toolbox app.

I don't have read access to the issues for this repository, but I will let the mobile application group know about your issue report.

As a workaround, you could use the nRF Connect for Android (/iOS). It doesn't have a specific UI for the NUS Service, but it supports reading and writing for all services.

Best regards,

Edvin

RE: NUS bt_nus_send() returns -ENOTCONN (-128) after pairing with nRF Toolbox — client never subscribes to TX notifications (NCS v3.2.4)

Julian1999 — Tue, 05 May 2026 06:57:10 GMT

Update

Further investigation confirms that the issue originates from the nRF Toolbox app, not the peripheral firmware.

Diagnostic step

A send_enabled callback was added to the peripheral’s NUS service to detect when a client writes to the NUS TX CCCD:

static void on_send_enabled(enum bt_nus_send_status status)
{
if (status == BT_NUS_SEND_STATUS_ENABLED) {
LOG_INF("NUS TX notifications ENABLED by client");
} else {
LOG_INF("NUS TX notifications DISABLED by client");
}
}

Result

After a successful connection, pairing, and bonding sequence, the send_enabled callback is never triggered—even after waiting more than 5 minutes. This indicates that nRF Toolbox (v4.2.0) does not subscribe to NUS TX notifications after pairing.

Root cause (nRF Toolbox source: UARTManager.kt)

The app calls .subscribe() on the NUS TX characteristic immediately after service discovery:

remoteService.characteristics
.firstOrNull { it.uuid == UART_TX_CHARACTERISTIC_UUID.toKotlinUuid() }
?.subscribe()

With CONFIG_BT_NUS_SECURITY_ENABLED=y, CCCD writes require an encrypted link. If .subscribe() is executed before the security procedure completes, the CCCD write fails silently and is not retried.

Action taken

A GitHub issue has been opened in the nordicsemi/Android-nRF-Toolbox repository, including details and a proposed fix:

Defer subscription until security is established, or
Retry on CCCD write failure

GitHub ticket: NUS TX notifications not subscribed after pairing when CONFIG_BT_NUS_SECURITY_ENABLED=y on peripheral · Issue #184 · nordicsemi/Android-nRF-Toolbox

I’d appreciate any clarification, and hope this can be resolved in a future update.