-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BTHome: New feature #20996
Draft
miri64
wants to merge
8
commits into
RIOT-OS:master
Choose a base branch
from
miri64:bthome/feat/initial
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
BTHome: New feature #20996
+2,056
−11
Conversation
This file contains 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
github-actions
bot
added
Area: network
Area: Networking
Area: doc
Area: Documentation
Area: build system
Area: Build system
Area: drivers
Area: Device drivers
Area: BLE
Area: Bluetooth Low Energy support
Area: sys
Area: System
Area: examples
Area: Example Applications
labels
Nov 16, 2024
miri64
added
State: WIP
State: The PR is still work-in-progress and its code is not in its final presentable form yet
Type: new feature
The issue requests / The PR implemements a new feature for RIOT
labels
Nov 16, 2024
This was referenced Nov 21, 2024
After talking to @BOZHENG001, I think the problem is that Skald is implementing an older BLE version than BTHome expects and thus fields (such as TXAdd which is used as part of the nonce for encryption) are not in the place Home Assistant expects them to be. Will try to confirm this somehow. |
miri64
force-pushed
the
bthome/feat/initial
branch
from
November 26, 2024 20:36
adea8cd
to
5d6f27b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: BLE
Area: Bluetooth Low Energy support
Area: build system
Area: Build system
Area: doc
Area: Documentation
Area: drivers
Area: Device drivers
Area: examples
Area: Example Applications
Area: network
Area: Networking
Area: sys
Area: System
State: WIP
State: The PR is still work-in-progress and its code is not in its final presentable form yet
Type: new feature
The issue requests / The PR implemements a new feature for RIOT
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.
Contribution description
Little weekend (or rather Thursday and Friday night) project of mine. This extends Skald, who advertises to the world with BTHome, "an energy efficient but flexible BLE format for devices to broadcast their sensor data and button presses". The main use case is to integrate BLE-powered devices into Home Assistant.
Most of the spec is supported, except "Trigger based advertisements" (since Skald at the moment only advertises periodically). For encryption, I was able to confirm with the spec examples that at least from the generated output
is the expected one, given the example input, but Home Assistant is for some reason not able to decrypt the message (even the one in the examples)... So further investigation is needed.
TODOs:
Testing procedure
So far only tested by flashing a node and seeing the device pop-up in Home Assistant:
Issues/PRs references
None