Skip to main content

OBD support for 2026+ Toyota bZ / bZ4X

Live Data Requests

I moved from a 2023 Subaru Solterra to a new 2026 Toyota BZ. I was using live data connected to my OBD dongle VeePeak BLE+. I get an error message ‘OBD Connection Failed”

What type of vehicle connection is this?
Posted by Mike Hoevenaars ·
Status: Awaiting Clarification23 comments

Log in to comment and vote

Comments23

  • Katya S. changed status to Awaiting Clarification
    Team•

    Mar 3

    Pinned

    Hi,

    We need the OBD PID commands and how to interpret the returned data. Since this is not easily available for most vehicles there is not possibility for us to provide a time estimate.

    You can check our telemetry API for relevant properties:
    documenter.getpostman.com/view/7396339/SWTK5a8w

    Also, you can check our (partially outdated) OBD repository to see what other cars report:
    https://www.github.com/iternio/ev-obd-pids

    If you find that an existing vehicle profile reads data correctly, please let us know, but please DO NOT keep using the incorrect vehicle model with live data.

    • Katya S.

      Team•

      Mar 3

      Could be that the PIDs we use for an already supported vehicle model could work. Here’s what you can do once you have access to the vehicle and a dongle;

      1. Select the actual model of your car, save it

      2. In vehicle settings, change the model of the saved vehicle to one that you suspect has compatible OBD commands (just any model will not work, it needs to be compatible)

      3. Link the vehicle via OBD (details here; OBD Connection )

      4. Select the correct vehicle model again

      5. After verifying that the data is read correctly (or even partially correctly) notify us that the OBD commands for vehicle model X also works for vehicle model Y.

      • Thomas Ripley

        •

        Apr 16

        Is there any update on this? Is there currently work being done to get the new ODB protocol supported?

        • Katya S.

          Team•

          Apr 21

          We currently do not have access to the updated PIDs for this vehicle model.

          • Thomas Ripley

            •

            Apr 22

            Is there a plan to gain access to the PIDs for this vehicle? The app is quite inaccurate without direct connection to ODB.

      • ABRP User #2727589

        •

        May 21

        I tried for my Canadian 2026 Toyota BZ XLE AWD but doesn't work

    • Mike Hoevenaars

      •

      Mar 3

      I’m not sure how to get that. I’m not that technical. I did manage to get the Enode connection to work with my BZ as a workaround. On another note…. When do you expect to get the 2026 BZ configurations updated? You still show BZ4x and not BZ. And the ranges are not correct for the NA BZ’s

      • Katya S.

        Team•

        Mar 4

        That’s understandable. Hopefully, someone else can help out.

        We added the North American bZ models just yesterday: 2026+ Toyota bZ (North America)

    • Jonathan Gifford

      •

      Mar 11

      I do not see any Toyota or Subaru cars in the OBD repository, otherwise I would have been happy to give it a shot. I too am not able to get data to ABRP from my 2026 Toyota Bz and am hoping to resolve this as soon as possible! Thank you!

  • Jonathan Gifford

    •

    Mar 24

    Any progress on this!? Still shows as “Awaiting Clarification” but the users in this thread have no way to clarify anything that I’m aware of. We need ABRP to update the software to support the J1979-3 protocol now being used for most new EVs. A few weeks back I noticed a new version of ABRP and installed it. All it did was remove the “link to OBD” option. Is there a timetable for this to get fixed soon? If not I’ll probably cancel my subscription seeing as it doesn’t work currently (Enode also stopped working and no longer pulls SoC from the Toyota servers so I seem to be paying for nothing currently).

  • Alex Riehl

    •

    Mar 10

    Issue is likely due to new J1979-3 OBDII protocol.

    • Jonathan Gifford

      •

      Mar 11

      It is 100% the J1979-3 OBDII protocol and all new EVs will be using this going forward so I’m hoping it gets fixed very soon!!! The protocol is published so I’m still confused as to why this has seemly caught ABRP off guard considering their business model is EV route planning. It’s not an optional step going forward and new cars started using it back in 2025!

  • John Tvedte

    •

    May 28

    CarScanner with profiles database 2.1.35 can read the 2026 bZ SoC. The commands I believe can be exported under the adapter export log function. I’d be happy to help facilitate sending a log to you if you can let me know what parameters you would need monitored. I have the OBDLink CX.

    • Alex Riehl

      •

      Jun 1

      From Iternio Telemetry API:

      Telemetry parameters

      The required parameters (and expected units) in the tlm JSON object are the following, in order of priority. Nothing is strictly required, but many features in ABRP will only be usable with enough data.

      High priority parameters:

      • utc [s]: UTC timestamp of the data (epoch) in seconds (note, not milliseconds!)

      • soc [SoC %]: State of Charge of the vehicle (what's displayed on the dashboard of the vehicle is preferred)

      • power [kW]: Instantaneous power output/input to the vehicle. Power output is positive, power input is negative (charging)

      • speed [km/h]: Vehicle speed

      • lat [°]: Current vehicle latitude

      • lon [°]: Current vehicle longitude

      • is_charging [bool or 1/0]: Determines vehicle state. 0 is not charging, 1 is charging

      • is_dcfc [bool or 1/0]: If is_charging, indicate if this is DC fast charging

      • is_parked [bool or 1/0]: If the vehicle gear is in P (or the driver has left the car)

      The lower priority parameters (and expected units) are:

      • capacity [kWh]: Estimated usable battery capacity (can be given together with soh, but usually not)

      • soe [kWh]: Present energy capacity of the battery, equal to SoC * capacity

      • soh [%]: State of Health of the battery. 100 = no degradation

      • heading [°]: Current heading of the vehicle. This will take priority over phone heading, so don't include if not accurate.

      • elevation [m]: Vehicle's current elevation. If not given, will be looked up from location (but may miss 3D structures)

      • ext_temp [°C]: Outside temperature measured by the vehicle

      • batt_temp [°C]: Battery temperature

      • voltage [V]: Battery pack voltage

      • current [A]: Battery pack current (similar to power: output is positive, input (charging) is negative.)

      • odometer [km]: Current odometer reading in km.

      • est_battery_range [km]: Estimated remaining range of the vehicle (according to the vehicle)

      • hvac_power [kW]: power usage by heating and cooling

      • hvac_setpoint [°C]: current setpoint of the HVAC system

      • cabin_temp [°C]: current temperature of the cabin

      • tire_pressure_fl [kPa]: Front Left tire pressure

      • tire_pressure_fr [kPa]: Front Right tire pressure

      • tire_pressure_rl [kPa]: Rear Left tire pressure

      • tire_pressure_rr [kPa]: Rear Right tire pressure

      To enable vehicle individual consumption calibration, we need at least speed, power and is_charging at a rate of at least once per 10 seconds (the faster the better).

      If you can get PIDs for these parameters I bet it would help out the ABRP team. I am NOT a team member, I just want my car to work too!

  • User

    •

    Mar 8

    If OBD is supported, can this be updated on the Live Data Comparison page? If I’m understanding it correctly, at least the Toyota BZ 2026 isn’t showing ABRP OBD support.

  • User

    •

    Apr 21

    •

    Merged request

    •

    1 vote

    Live data from my 2026 Toyota bz

    • Linda ABRP

      Team•

      Apr 14

      Hi

      You need to save the car to see the live data options.

  • Dan Leavitt

    •

    May 7

    26 Subaru Solterra too

  • ABRP User #1724861

    •

    May 15

    Is there any update on the 2026 Toyota/Lexus vehicles? ABRP was working well with my previous 2024 Toyota bZ4x and now upgraded to 2026 Lexus RZ350e and now receive the “ODB Connection Failed” message. Is there an update?

  • ABRP User #2727589

    •

    May 20

    •

    Merged request

    •

    1 vote

    Can't connect with my 2026 Toyota BZ XLE AWD with ABRP app on my Android phone. I tried on iPhone but no luck. Getting following error messages