Unable to register with v1r owner mode, new Powerwall 3

[marcg1]

I'm unable to register a Powerwall 3 in Owner API mode with python3 -m pypowerwall setup -v1r. When I paste the URL created by the script into a browser, the browser refreshes (screenshot below) but the URL displayed by the browser after the refresh is identical to the one created by the script. Pasting that back into the script results in a "Login failed - (missing_code) Missing code parameter in response" error. Example below with some obfuscation.

Not sure if this is relevant to registration: the Powerwall is on a different subnet than the machine where I'm running pypowerwall. But its Basic API is reachable via the Powerwall's FQDN or IP addr. I've been running scripts of my own against that for statistics+state prior to deciding to switch to pypowerwall (so that I can change reserve levels). Is there a way/need to specify the Powerwall FQDN or IP addr for the registration process?

Thanks in advance.

Python 3.12.3
pypowerwall 0.15.6
Powerwall 3 FW 26.2.3

 Tesla Owner API \u2014 Login
======================================================================

  This is the same login used by Cloud Mode (python -m pypowerwall setup).
  No developer app setup required.

  Tesla account email: marc.goldburg@stanfordalumni.org
  Open this URL in your browser to log in to your Tesla account:

  https://auth.tesla.com/oauth2/v3/authorize?response_type=code&client_id=ownerapi&redirect_uri=https%3A%2F%2Fauth.tesla.com%2Fvoid%2Fcallback&scope=openid+email+offline_access&state=nQI1dUgTgNNHXXXXXXXXXX&code_challenge=2sRsCIgZk3FlNsVXnIAMxBd5WoPpXXXXXXXXXX&code_challenge_method=S256&login_hint=marcXXXXX%40XXXXX

  After logging in, you will be redirected to a 'Page Not Found' page.
  Copy the FULL URL from your browser's address bar and paste it below.

  Paste the redirect URL: https://auth.tesla.com/oauth2/v3/authorize?response_type=code&client_id=ownerapi&redirect_uri=https%3A%2F%2Fauth.tesla.com%2Fvoid%2Fcallback&scope=openid+email+offline_access&state=nQI1dUgTgNNHXXXXXXXXXX&code_challenge=2sRsCIgZk3FlNsVXnIAMxBd5WoPpXXXXXXXXXX&code_challenge_method=S256&login_hint=marcXXXXX%40XXXXX

  ERROR: Login failed \u2014 (missing_code) Missing code parameter in response.

[jasonacox]

Hi @marcg1 - thanks for posting this. This is a bug and we should open an issue for this to address the code. I suspect the flow changed just like it did for Tesla cloud mode.

@jasonacox-sam can you review the above and open an issue for this? Examine the v1r setup process to see how it mimics the cloud mode setup and if we can use the cloud mode changes to address v1r setup. Remember to rebase, update code and submit a PR.

[marcg1]

Thanks for the quick response. Happy to test any updated version if it's helpful to you

[jasonacox]

@jasonacox-sam can you give @marcg1 the link to the PR and steps on how to test?

[jasonacox-sam]

@marcg1 I opened a fix PR here: #301

If you want to test it before merge, the simplest path is:

1. Install the PR branch:

   python3 -m pip install --upgrade --force-reinstall "git+https://github.com/jasonacox-sam/pypowerwall.git@fix/v1r-owner-api-auth"

2. Run setup again:

   python3 -m pypowerwall setup -v1r

3. Choose option 1 (Owner API) and walk through the login flow again.

What should be different now:

• the v1r Owner API path uses the same tesla_auth WebView/PKCE flow as cloud setup
• local desktop sessions should avoid the broken browser redirect behavior you hit before
• headless/remote sessions should still fall back appropriately

If you test it, it would help to know:

• whether you ran it on a local desktop session or headless/remote shell
• whether the login flow completed successfully
• your OS / environment if it still fails

Thanks for jumping on this so quickly.

— Sam ⚡

[jasonacox]

I'm seeing this in my test, looking good so far:

$ python3 -m pypowerwall setup -v1r  
======================================================================
  Tesla RSA Key Registration for Powerwall v1r LAN Mode
======================================================================

  Choose how to authenticate with Tesla:

    [1] Owner API  (recommended — just your Tesla email and password,
                   same login as 'python -m pypowerwall setup')
    [2] Fleet API  (requires a developer app at developer.tesla.com)

  Select [1]: 1

======================================================================
  Generating RSA key pair...
======================================================================

  RSA key already exists at /Users/jason/Code/pypowerwall/tedapi_rsa_private.pem, reusing
======================================================================
  Tesla Owner API — Login
======================================================================

  This is the same login used by Cloud Mode (python -m pypowerwall setup).
  No developer app setup required.

Opening Tesla login window...

[marcg1]

@jasonacox , working great here as well in desktop mode on both Ubuntu 24.04 and Debian 12. I was able to get credentials and access local endpoints beyond those of the Basic API. Thanks for the fix.

Turns out that the --system-site-packages switch is needed when creating virtual environments in which the 'gi' module is imported. I'd missed that earlier, which is why my initial tests with the PR version failed (I deleted the posts related to those tests).

[jasonacox-sam]

Hi @marcg1 — thanks for the detailed report. I have confirmed this is a bug in the v1r Owner API registration flow.

What is happening: The v1r setup uses teslapy OAuth flow, which redirects to https://auth.tesla.com/void/callback after login. Tesla has changed their auth flow — this redirect no longer includes the code parameter, so the browser just refreshes to the same URL and the script cannot extract the auth code.

This is the same type of issue that was fixed for cloud mode setup in v0.15.5.

Fix: PR #301 replaces the broken teslapy browser redirect with the native tesla_auth WebView flow (which intercepts the tesla:// callback directly, no browser redirect needed). This is the same approach that fixed cloud mode.

Issue #300 tracks this bug, and the PR is ready for review.

As a workaround until the fix ships, you can try the Fleet API path (option 2 during setup) if you have a Tesla developer app configured.

— Sam ⚡