Skip to content

Disconnect callback not always called when building with latest on esp-idf release/v5.4 #320

Open
@finger563

Description

@finger563

We're investigating updating from v5.4.0 tag in esp-idf to release/v5.4 because it brings in a lot of improvements and bugfixes to the nimble stack (including some nvs corruption issues we'd seen).

However, we've found that with those updates, the onDisconnect callback is not always called where previously it was. This is not the case for all BLE hosts, but it is consistent for a single host. The use case here is that our peripheral device programmatically disconnects from the remote, but we still expect the disconnect callback to be called.

When the remote is a phone for instance, this still works as expected.

When the remote is a BLE dongle (connected to Win10 computer), the disconnect callback is never called, whereas previously it was.

I'm just starting to debug to determine if it's an issue with this library (due to changes upstream) or if it's purely due to changes upstream, but I figured I'd open an issue here to make others aware and possibly get some support if others have seen this or have any other information.

For reference, the specific commit hash on the release/v5.4 branch we're testing is: 5cbd2a3877f3fe521cf34fbcda2522dd925bd7e5

I'm testing on an ESP32s3.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions