Fix intermittent protocol issues on Anker Prime 160w charger.#33
Open
Fix intermittent protocol issues on Anker Prime 160w charger.#33
Conversation
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
1 participant
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.
An issue was raised on the Home Assistant integration page for issues with the Anker Prime 250w charger but issues with the 160w charger were also reported there and the logs from it are quite strange. The logs show that the charger is sending unencrypted telemetry data for some reason. What is especially weird is that my unit does not do this despite running the same firmware version (1.6.0.6).
At the moment this PR adds support for reading unencrypted telemetry data but more may be added to deal with other strange things from the logs.