Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Initially, an “GATT operation failed” error log appeared even when the Wi-Fi connection was good, because nmcli was blocking the main thread for 6 seconds, causing a timeout on the BLE client, which is waiting for WriteValue to return.
Now:
Server: WriteValue launches the command in a thread and returns immediately. When the thread finishes, it sends a BLE signal (PropertiesChanged) to notify the client.
Client: Instead of waiting a fixed 200 ms and then reading, it subscribes to notifications and waits for the event until a 35-second timeout