Bluetooth control functions #12
Open
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.
The main addition here is a server that uses Bluetooth RFCOMM to expose the cedar grpc service. The server only runs when use_bluetooth is set to true in preferences.
A smaller addition is the exposure of the RPI's Bluetooth address in the GetBluetoothName API (I thought renaming this isn't a good idea for backwards compatibility). The address can be used to initiate pairing from an Android phone to the RPI in Cedar Aim directly (using the flutter_blue_classic package), without requiring the user to leave Cedar Aim to start Bluetooth pairing in their phone's settings.