Draft implementation of NoiseClient #866
Draft
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.
Initial draft implementation of adding NoiseClient (Encryption) to the esphome-ts library.
This got all the way through the handshake, but then any subsequent messages would never get accepted by the server.
Unfortunately I ran into a few stumbling blocks with the actual implementation of
esphome-ts
mainly due to the inconsistent nature of howparseListResponse
would frequently drop entities (or not all entities would be received) before ListEntitiesDoneResponse was received. Once ListEntitiesDoneResponse was acknowledged no further entities would be added to the list, and therefore were never able to be added to HomeBridge.Due to this I instead switched out this implementation of the Esphome Native API esphome-native-api which already had encryption, and far more Entities implemented.