engine_start fails for hybrid vehicles (2025 Sienna XLE AWD) - needs climate-start command

[EdFabre]

Description

Remote start via toyota_na.engine_start returns 500 Internal Server Error for the 2025 Toyota Sienna XLE AWD (hybrid-only platform). Remote start works correctly in the official MyToyota app, confirming the subscription is active and the account is properly authenticated.

Vehicle

• Model: 2025 Toyota Sienna XLE AWD
• Drivetrain: Hybrid only (no ICE option on this model)
• Integration version: latest (v2.6.7)
• HA version: 2026.1.2

Steps to Reproduce

service: toyota_na.engine_start
data:
  vehicle: <device_id>

Returns: 500 Internal Server Error

Expected Behavior

Remote start triggers, as it does via the MyToyota app.

Analysis

Based on the integration source, engine_start sends {"command": "engine-start"} to the Toyota API. For hybrid vehicles, Toyota's app appears to use a different command path (possibly climate-start or remote-climate). This matches the pattern reported in #116 (RAV4 Prime) and Discussion #132 (2025 RAV4 PHEV).

The Sienna XLE is hybrid-only — there is no ICE variant — so engine-start is never the correct command for this vehicle.

Related Issues

• Remote start does not work for Rav4 prime #116 RAV4 Prime remote start not working
• Discussion Start/stop motor on 2025 RAV4 Plugin Hybrid #132 Start/stop motor on 2025 RAV4 Plugin Hybrid

Request

Could the integration detect hybrid vehicles (or expose a separate climate_start service) and route to the appropriate API command? Happy to test any PRs against my 2025 Sienna.

[EdFabre]

Additional findings from deeper investigation

Vehicle: 2025 Toyota Sienna XLE AWD (VIN: 5TDJSKFC7SS199558, hybrid-only)
Integration version: 2.6.1 with toyota-na==2.1.1

The problem is broader than just the command string

After extracting the auth tokens from the running HA instance and testing directly against the API, I found that ALL v1/global/remote/* endpoints return 400 Bad Request for this vehicle, not just /remote/command. This includes:

• GET v1/global/remote/status → 400
• GET v1/global/remote/engine-status → 400
• POST v1/global/remote/command → 400/403

This is visible in the HA logs as a flood of 400s on every polling cycle:

ERROR [custom_components.toyota_na.patch_seventeen_cy_plus] 400, message='Bad Request', url='https://onecdn.telematicsct.com/oneapi/v1/global/remote/status'
ERROR [custom_components.toyota_na.patch_seventeen_cy_plus] 400, message='Bad Request', url='https://onecdn.telematicsct.com/oneapi/v1/global/remote/engine-status'

Telemetry endpoints (/v2/telemetry, /v1/one/vehicle) work fine — odometer, fuel, location, tire pressure all update correctly. Only the v1/global/remote/* path fails.

Hypothesis

The 2025 Sienna XLE hybrid may be on a newer API generation beyond 17CYPLUS that uses different remote endpoints entirely. Toyota may have migrated hybrid/newer model year vehicles to a different API path (possibly v2/global/remote/* or a generation-specific path).

Next step

I'm about to capture a network trace from the official MyToyota Android app using PCAPdroid to see exactly what API calls are made when Remote Start is triggered. Will post results here.

The good news: sensors, location, fuel, and door lock do work through the integration (lock uses v1/global/remote/command with door-lock command... actually let me verify that. If door-lock also returns 400, that means our lock automation in HA also isn't working as expected).

cc @widewing — is there any known newer API generation beyond 17CYPLUS for 2025 model year vehicles?

[widewing]

I own 2021 Sienna XLE Hybrid and the current API still works for me, so I guess the new generations are using different APIs.

[nelsonblaha]

Confirming this on a 2022 Toyota Prius Prime LE (PHEV)

Same engine-start vs climate-start problem. Adding a detailed data point in case it helps whoever cracks the payload.

What works

• All sensor/status reads are perfect — EV battery %, EV range, fuel, tire pressures, doors/locks, location, odometer, charging status, etc.
• toyota_na.door_lock / door_unlock work fine (they send door-lock / door-unlock).
• The official Toyota app's remote climate/AC works flawlessly on this exact vehicle (same account, active Remote Connect subscription). So account, subscription, and vehicle are all fine — this is specifically the HA command payload, not a permissions/vehicle issue.

What fails

toyota_na.engine_start fails every time. HA surfaces it as a 500, but the underlying error is a 400 Bad Request from Toyota's command endpoint:

Traceback (most recent call last):
  File "/config/custom_components/toyota_na/__init__.py", line 147, in async_service_handle
  File "/config/custom_components/toyota_na/patch_seventeen_cy_plus.py", line 191, in send_command
  File "/config/custom_components/toyota_na/patch_client.py", line 102, in remote_request_17cyplus
  File ".../site-packages/toyota_na/client.py", line 44, in api_post
  File "/config/custom_components/toyota_na/patch_client.py", line 248, in api_request
aiohttp.client_exceptions.ClientResponseError: 400, message='Bad Request',
    url='https://onecdn.telematicsct.com/oneapi/v1/global/remote/command'

[moelsaied88]

Same class of bug on a different vehicle: 2026 Lexus TX 500h AWD (hybrid), integration v2.7.0.
toyota_na.engine_start returns success with no error, unlike the 500 on the Sienna and RAV4 reports above. But the engine doesn't actually start. I called toyota_na.refresh right after and the remote_start binary_sensor stayed "off" with the same last_changed timestamp as before the call, so Toyota's backend isn't reporting it as running either.
Looks like some vehicle generations reject the wrong command outright (500) and others just accept it silently and do nothing. Might be worth checking if TX/Lexus platforms report a different generation flag than Sienna/RAV4 that's hitting a different code path. Happy to test anything against my TX 500h if it helps narrow this down.