fix(api): fixes for tesla 20.49 API changes #17
Merged
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.
With the 20.49 firmware update by Tesla, the endpoints that previously
were open are no longer available without authentication. Unfortuantely,
the mechanism used for authentication is not HTTP basic, rather it's
cookie based. This change brings in an additional container that I
created called cookieproxy, that can be used to proxy the cookie based
requests through to the Powerwall gateway.
In contrast to previous versions, this requires no compilation of
containers on the local machine and no modifications to the more common
containers of influxdb, grafana, and telegraf. There is a small
customization that is required to store the password of your Powerwall
in the
.env.cookieproxy
file, but otherwise it should be plug and playwith the previous versions of mihailescu2m/powerwall_monitor.
Root issue: #14
This supersedes my previous attempts at a patch including #16