Subaru Connect in United States

[keithnet]

Anyone have any tips or tricks on getting this to work with a Subaru Solterra?

[Stylo101]

I'd like to know too. I am able to authenticate but no vehicle (2026 Subaru Solterra) shows up.

[adepssimius]

Getting this to work with a Solterra is going to be a bit of a task. I did some de-compilation of the Subaru Connect app and found that the hostnames used to login and retrieve info are different than the hardcoded values that are in the toyota_na package which is used by this integration. Additionally, you need to pass a X-BRAND='S' header to be in Subaru-mode, but na_toyota hardcodes this in several places. I was able to get a login flow to work and return my Solterra with the help of ChatGPT and the info I got from jadx. ChatGPT made these changes:

• Added brand selection via TOYOTA_APP_BRAND, with S for Subaru.
• Switched ForgeRock auth endpoints dynamically:
  Toyota: login.toyotadriverslogin.com
  Subaru: login.subarudriverslogin.com
• Made the OAuth redirect URI configurable instead of hardcoding Toyota’s value.
• Split cached sessions by brand, so Toyota and Subaru don’t reuse the same token file.
• Applied the Home Assistant integration’s client monkey patches locally so the runner uses the working API gateway and patched request behavior instead of the dead stock host in toyota-na.
• Overrode request headers to send Subaru branding:
  X-BRAND: S
X-APPBRAND: S
• Added the /v4/account bootstrap before calling /v2/vehicle/guid, matching the Subaru app flow you described. (this was the flow in the Subaru Connect apk after decompilation)

I can't dedicate a bunch of time to this, but I have my work saved thus far if anybody wants more detail. I'm mostly occupied being a good dad and a middling athlete so I don't have a ton of time for this as a side project at the moment.

[keithnet]

That was helpful! It works here now.

I've been trying to get Claude to help. Auth hacks were working fine, but wasn't able to vehicle listed.

This is claude's summary of what's different in the modification I'm successfully running:
`# ha-toyota-na → Subaru Connect: Complete Change Review

Summary

Three changes are required to make ha-toyota-na work with SubaruConnect vehicles (e.g. 2026 Solterra):

1. __init__.py — Redirect ForgeRock auth to Subaru's identity server, add get_user_vehicle_list monkey-patch
2. patch_client.py — Change brand headers, User-Agent, add X-APPBRAND header, add /v4/account bootstrap, add get_user_vehicle_list override
3. patch_vehicle_debug.py (optional) — Enhanced vehicle discovery logging

---

File: __init__.py

Change 1: ForgeRock Auth URL Override (lines 7-11)

ORIGINAL:

from toyota_na.auth import ToyotaOneAuth
from toyota_na.client import ToyotaOneClient

SUBARU:

from toyota_na.auth import ToyotaOneAuth

# --- Subaru Override: ForgeRock AM host ---
ToyotaOneAuth.ACCESS_TOKEN_URL = "https://login.subarudriverslogin.com/oauth2/realms/root/realms/tmna-native/access_token"
ToyotaOneAuth.AUTHORIZE_URL = "https://login.subarudriverslogin.com/oauth2/realms/root/realms/tmna-native/authorize"
ToyotaOneAuth.AUTHENTICATE_URL = "https://login.subarudriverslogin.com/json/realms/root/realms/tmna-native/authenticate"

from toyota_na.client import ToyotaOneClient

WHY: Toyota uses login.toyotadriverslogin.com, Subaru uses login.subarudriverslogin.com. Same ForgeRock platform, different tenant. The realm (tmna-native), client_id (oneappsdkclient), scope, and redirect_uri are all identical.

Change 2: Add get_user_vehicle_list monkey-patch (lines 18-19, 38)

ORIGINAL: Not present — the pip package's built-in get_user_vehicle_list is used.

SUBARU:

from .patch_client import (
    get_user_vehicle_list,  # NEW
    get_electric_realtime_status,
    ...
)
ToyotaOneClient.get_user_vehicle_list = get_user_vehicle_list  # NEW

WHY: The Subaru app requires a /v4/account bootstrap call before /v2/vehicle/guid will return vehicles. The original code calls v2/vehicle/guid directly.

Change 3: Use patch_vehicle_debug.py instead of patch_vehicle.py (line ~82)

ORIGINAL:

from .patch_vehicle import get_vehicles

SUBARU:

from .patch_vehicle_debug import get_vehicles

WHY: Adds detailed logging for vehicle discovery. Can be reverted to patch_vehicle once stable.

---

File: patch_client.py

Change 1: User-Agent string (line 10)

ORIGINAL:

USER_AGENT = "ToyotaOneApp/3.10.0 (com.toyota.oneapp; build:3100; Android 14) okhttp/4.12.0"

SUBARU:

USER_AGENT = "SubaruConnect/2.3.1 (com.subaru.oneapp; build:48; Android 14) okhttp/4.12.0"

WHY: Identifies as the SubaruConnect app instead of Toyota OneApp.

Change 2: _auth_headers — Brand headers (lines 53-67)

ORIGINAL:

async def _auth_headers(self):
    return {
        ...
        "X-BRAND": "T",
        ...
    }

SUBARU:

async def _auth_headers(self):
    return {
        ...
        "X-BRAND": "S",
        "X-APPBRAND": "S",    # NEW — required for vehicle list bootstrap
        "X-Brand-Id": "S",    # NEW — sent by Subaru app
        ...
    }

WHY:

• X-BRAND: "S" identifies the brand (S=Subaru, T=Toyota, L=Lexus)
• X-APPBRAND: "S" is a separate header the Subaru app sends — this was the critical missing piece that prevented vehicle discovery
• X-Brand-Id: "S" is also sent by the Subaru app

Change 3: Brand headers in per-endpoint functions

Every function that passes X-BRAND as a header parameter changed from "T" to "S":

• get_telemetry: "X-BRAND": "T" → "X-BRAND": "S"
• send_refresh_request_17cyplus: same
• remote_request_17cyplus: same
• get_vehicle_status_17cy: same
• get_engine_status_17cy: same
• send_refresh_request_17cy: same
• get_electric_realtime_status: same
• get_electric_status: same
• graphql_request: "X-APPBRAND": "T" → "X-APPBRAND": "S"

Change 4: NEW — get_user_vehicle_list function

ORIGINAL: Not present in patch_client.py. The pip package's ToyotaOneClient.get_user_vehicle_list calls v2/vehicle/guid directly.

SUBARU:

async def get_user_vehicle_list(self):
    """Bootstrap with /v4/account then fetch vehicle list, matching Subaru app flow."""
    try:
        account = await self.api_get("v4/account")
        _LOGGER.debug("Subaru v4/account bootstrap complete")
    except Exception as e:
        _LOGGER.warning("Subaru v4/account bootstrap failed: %s", e)
    
    return await self.api_get("v2/vehicle/guid")

WHY: The SubaruConnect app calls /v4/account before requesting the vehicle list. This "bootstrap" call establishes the session context on the server side. Without it, /v2/vehicle/guid returns an empty vehicle list even though auth succeeds. This matches the app flow discovered via APK decompilation.

Change 5: Debug logging in api_request (optional, remove for production)

ORIGINAL:

async def api_request(self, method, endpoint, header_params=None, **kwargs):
    ...
    resp.raise_for_status()
    try:
        resp_json = await resp.json()
        ...

SUBARU (debug version):

async def api_request(self, method, endpoint, header_params=None, **kwargs):
    ...
    body_text = await resp.text()
    _LOGGER.warning("=== SUBARU API: %s %s -> HTTP %d | Body: %s ===",
        method, url, resp.status, body_text[:2000])
    resp.raise_for_status()
    try:
        resp_json = json.loads(body_text)
        ...

WHY: Logs all API responses for debugging. Should be removed or reduced to _LOGGER.debug for production use. Note it reads the body with resp.text() then parses with json.loads() instead of calling both resp.text() and resp.json() which would fail on double-read.

---

What did NOT change

• API key (ToyotaOneClient.API_KEY): The same Toyota key works for Subaru. The key isn't brand-specific — it's the gateway key.
• API gateway URL: Same https://onecdn.telematicsct.com/oneapi/
• GraphQL endpoint: Same https://oa-api.telematicsct.com/graphql
• AppSync API key: Same da2-zgeayo2qh5eo7cj6pmdwhwugze
• Resolver API key: Same pypIHG015k4ABHWbcI4G0a94F7cC0JDo1OynpAsG
• OAuth parameters: client_id (oneappsdkclient), scope, redirect_uri, realm all identical
• All endpoint paths: /v2/vehicle/guid, /v2/telemetry, etc. are the same
• Vehicle generation handling: patch_vehicle.py, patch_base_vehicle.py, patch_seventeen_cy*.py unchanged
• All other files: config_flow.py, const.py, sensor.py, binary_sensor.py, etc. unchanged

---

Key Discovery: The /v4/account Bootstrap

The single most important finding: the Subaru backend requires a /v4/account GET request BEFORE /v2/vehicle/guid will return vehicles. Without this bootstrap:

• Auth succeeds (200)
• Vehicle list returns 200 with "payload": []
• Account endpoints confirm the user exists

With the bootstrap:

• /v4/account returns customer data (name, email, phone)
• Subsequent /v2/vehicle/guid returns the vehicle list

This is a server-side session initialization requirement specific to the Subaru brand flow, discovered by another user who decompiled the SubaruConnect APK and traced the app's startup sequence.
`

[adepssimius]

So were you able to get this running in your home assistant with the above patches? How do you think the best way to package this is going to be given that the patches above essentially make this package subaru only and people may have both a subaru and a toyota that they might need in HA?

[keithnet]

I ran my modifications detailed above fine in HA. my 2026 Subaru worked great.

I just created and tested a fork of this repo that supports Toyota and Subaru. I've only tested the Subaru side. If you want to give a try and let me know results, I can publish it back as a pull request to see if it can be tested and added to the main repo.

https://github.com/keithnet/ha-toyota-na

[wshankles]

@keithnet

I ran my modifications detailed above fine in HA. my 2026 Subaru worked great.

I just created and tested a fork of this repo that supports Toyota and Subaru. I've only tested the Subaru side. If you want to give a try and let me know results, I can publish it back as a pull request to see if it can be tested and added to the main repo.

https://github.com/keithnet/ha-toyota-na

Would you mind renaming it? I think HACS is having hard time adding it as a custom repository. It's giving me a 404 when I try to download it and when I restart home assistant the custom repository disappears.

[keithnet]

Would you mind renaming it? I think HACS is having hard time adding it as a custom repository. It's giving me a 404 when I try to download it and when I restart home assistant the custom repository disappears.

I recommend manually upload the custom_components/toyota_na to your HA's custom_components/toyota_na.

[Dragonpark]

Would you mind renaming it? I think HACS is having hard time adding it as a custom repository. It's giving me a 404 when I try to download it and when I restart home assistant the custom repository disappears.

I recommend manually upload the custom_components/toyota_na to your HA's custom_components/toyota_na.

Great modification and its nice to have my Solterra in HA. I know this is a limitation of the API, but the only gripe I have is not being able to see the rear window status. Seems like a huge miss on Toyota/Subaru's part.

[mmiller7]

Just got a Subaru Trailseeker which uses the Subaru Connect, would love to track charging at home so I know how much more I owe extra for power use vs my roomates.

Any tips on getting it working?

For the Subaru Connect mine uses Google single sign in and a numeric PIN, not a password.

[kshakir]

Just got a Subaru Trailseeker which uses the Subaru Connect, would love to track charging at home so I know how much more I owe extra for power use vs my roomates.

Any tips on getting it working?

Glancing through the forks as of today https://github.com/bhaggs/ha-toyota-na may be worth checking out.

For the Subaru Connect mine uses Google single sign in and a numeric PIN, not a password.

Glancing through the issues it seems like some folks have had mixed success switching to password auth using steps like #55 (comment).