Fix ciphertext length handling in BLE advertisement - #2
Open
catsimple wants to merge 1 commit into
Open
Conversation
|
exactly the problem i ran into. confirm @catsimple fix to work now. until merged you can use: external_components:
|
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
2 participants
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 current implementation appends the 4-byte Counter after the MIC. The resulting structure was [DeviceInfo] + [Ciphertext] + [MIC] + [Counter].
According to the BTHomeV2 specification and the official Python implementation, the Counter must precede the MIC. The correct structure for the Service Data should be [DeviceInfo] + [Ciphertext] + [Counter] + [MIC].