@jasonacox-sam A lot of work has been done on the v1r API access path with the vendor subnet for the PW3 to re-enable the hardwired access that was lost last year.
For those who don't have a PW3 specifically, I've found another path that is equally essential. I found this by reverse-engineering the Tesla One APK using Claude a few months ago, and it has worked and survived multiple firmware updates.
It allows for full hardwired access to the TEG API. More importantly, those who have "vanilla" Tesla inverters cannot use the RSA token method, Tesla doesn't enable that for inverters, so we have to use this other approach.
Both approaches were discovered around the same time, so I fear this bearer token approach got lost. The initial prototype code for it is here: https://github.com/Nexarian/pypowerwall/commits/feature/bearer-token-auth and also integrated into https://github.com/Nexarian/pypowerwall/tree/re-work-proxy-next
There are several things that I believe are necessary to get this living in peace with the v1r method:
- An option to configure which method/mode to use. This is getting complex. We have SO MANY modes and options for login that it's getting difficult to manage.
- The bearer method appears to require an update to GraphQL queries. It comes with an auth envelope wrapper, which changes the encryption that is used. That implies we need to start versioning our queries, which is a pretty big refactor.
- Add in the plumbing for all of this.
... And what else?
I want you to analyze my branches that I've linked here and then create a plan as to what you believe the next right steps are to get this integrated. In addition to the work you outlined here: #254 (comment) I believe both efforts move the project forward meaningfully.
@jasonacox-sam A lot of work has been done on the v1r API access path with the vendor subnet for the PW3 to re-enable the hardwired access that was lost last year.
For those who don't have a PW3 specifically, I've found another path that is equally essential. I found this by reverse-engineering the Tesla One APK using Claude a few months ago, and it has worked and survived multiple firmware updates.
It allows for full hardwired access to the TEG API. More importantly, those who have "vanilla" Tesla inverters cannot use the RSA token method, Tesla doesn't enable that for inverters, so we have to use this other approach.
Both approaches were discovered around the same time, so I fear this bearer token approach got lost. The initial prototype code for it is here: https://github.com/Nexarian/pypowerwall/commits/feature/bearer-token-auth and also integrated into https://github.com/Nexarian/pypowerwall/tree/re-work-proxy-next
There are several things that I believe are necessary to get this living in peace with the v1r method:
... And what else?
I want you to analyze my branches that I've linked here and then create a plan as to what you believe the next right steps are to get this integrated. In addition to the work you outlined here: #254 (comment) I believe both efforts move the project forward meaningfully.