Skip to main content

New bZ4X, error when receiving battery soc by using bt ble obd

Hi,i got attached error while connecting to OBD BLE with my 2026 bZ4X. Previous model worked fine. Is there fix for that?

Where does this happen?
ABRP version number (found at bottom of settings menu)
Status: Awaiting Clarification14 comments

Log in to comment and vote

Comments14

  • Mahde - ABRP changed status to Awaiting Clarification
    Team•

    Jan 20

    Pinned

    Hello @Hybridelicious,


    To help us figure out what happen we need you to send a bug report. First you need to enable the bug button in the settings. Go to the settings and scroll all the way down. The bug button will show on your screen.

    When the OBD is connected to your car and the car is in drive mode click at the button. Then let me know when you have done this.

  • F.A. Peeters

    •

    Mar 1

    Is there an update for this issue? Can confirm it is not yet fixed, using ABRP 7.0.3 with an OBDLink CX and latest firmware.

  • Patrick Echers

    •

    Feb 10

    I’d like to +1 on this one.
    Could you please provide an update on the ETA for fixing this? Thanks.

  • Patrick Echers

    •

    Mar 22

    @Linda ABRP @Bo (ABRP) @Mahde @Matt (ABRP)
    I’m just tagging someone so we can hopefully get an update.

    Hi,

    It has now been several months without any response on this issue.

    As paying Premium users, we expect clear communication and transparency. At this point, we are not just asking for a status update, but a proper explanation of the underlying problem.

    This does not appear to be related to Enode or API access.

    The issue is specifically that OBD BLE dongles are no longer able to retrieve battery SOC data on the new Toyota bZ4X (2026 model). The connection is established, but ABRP fails to read the necessary data from the vehicle.

    This is also confirmed by other users, where ABRP reports errors when processing OBD data and is unable to detect battery state of charge.

    Additionally:
    • The issue persists on the latest version of ABRP
    • It occurs on iOS as well.
    • Previous model years worked without issues

    Given this, we would like clear answers to the following:
    • What has changed in the new bZ4X that prevents ABRP from reading OBD data?
    • Is this a limitation in ABRP, or a change in how Toyota exposes data over OBD?
    • Is this something you are actively working on fixing?
    • If so, what is the expected timeline?

    At the moment, a core Premium feature is effectively unusable for this vehicle, and the lack of communication is concerning.

    Could someone from the team please provide a proper and detailed update?

    Thank you.

    • Bo (ABRP)

      Team•

      Mar 25

      Hello Patrick,

      Unfortunately, a couple of car manufacturers have started encrypting their CAN bus communications on later model years (like the Ford Mach-e 2025+). We are not yet sure if this is the case for the bZ4X but we are investigating it and will get back to you.

      • Patrick Echers

        •

        Apr 27

        Hi @Bo (ABRP)

        Any news? I mean, it can’t take that long to reach out to Toyota and ask… I did to the Danish Toyota department and they said that they are not aware of any encryption of the CAN bus.

        • Bo (ABRP)

          Team•

          Apr 27

          Hello Patryk - unfortunately getting in touch with someone who is willing to share information on CAN messages from a car manufacturer is not an easy task. If you are able to find some enthusiast forum or similar with more information on the new way to read out data from the newer bZ4X we would be happy to use it.

          • Patrick Echers

            •

            May 5

            Hi Bo.

            A guy here in Denmark made it work partially using info from your guides.

            It does only tell SoC though, but perhaps you know more and can do more with it.

            Here is a link for the pdf guide.

            https://echers.fromsmash.com/JEHaGzvxwG-dt

            It is in danish but a quick translation using any AI like ChatGPT should make it easy for you to understand.

            Please update if this is of help for you or if you want the file sent through another platform or anything.

            • Bo (ABRP)

              Team•

              May 6

              That’s great input! We should have received that updated PID config from the user but maybe we have lost it somewhere. Anyhow, we will look at it and try to create an OBD config for the 2026 bZ4X.

              • Patrick Echers

                •

                Jun 11

                Hi Bo.

                I’m reaching out to ask for an update on this.

                We are leaving for summer holiday (driving 1400km both ways) in just shy of a month and was hoping to use ABRP for this. We have paid for ABRP in this time it has not worked in the hopes of helping development for this.

                Thanks.

                /Patrick

                • Bo (ABRP)

                  Team•

                  Jun 15

                  Hello Patrick - we have released very basic support for OBD for the 2026 Toyota/Subaru/Lexus, but it is SoC only and there seems to be some offset issue. However, we are working with owners on it.

                  If you are technical you can play with the SoC equation in the PID editor in ABRP.