Add support for ShellyBLU Button1 encrypted advertisements #145
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
koenvervloesem
force-pushed
the
decrypt_advertisements
branch
2 times, most recently
from
240b10b
to
f5d6ed4
Compare
koenvervloesem
force-pushed
the
decrypt_advertisements
branch
from
f5d6ed4
to
3cb4037
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
Adds support for encrypted BTHome advertisements from the ShellyBLU Button1. This also adds a bindkeys argument to configure device addresses and their associated bindkeys. The code can be generalized in the future to support other encrypted advertisements.
Note: This requires changes in the Docker image, Home Assistant addon and snap to handle the new argument.
Checklist: