Skip to main content

No longer able to pair to my car

Bug Reports

I have a Subaru Trailseeker Touring. I also bought an OBDLink CX to pair to with ABRP.

That was all working well.

It's now no longer pairing and I can't even find the setting to try and re-pair it. When it wasn’t working I tried unlinking the bluetooth pairing and relinking it. I can see it in the OBDLink app but not in ABRP. I've tried removing the ABRP data and reinstalling the app. That didn't help.

The one thing I'm wondering that may have created the problem is that when I got the car, it wasn't a listed model so I used the closely related Soltera model. Recently the Trailseeker was added so I changed my car to that. I don't know if there pairing stopped after that. It was only a day or two later I noticed it was no longer pairing.

Also, here in Australia, the Trailseeker had no modem to “phone home”, one of these selling points for me. I raise this because the page where I thought I should link it, only wants to offer me a developer API key.

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by ABRP User #2556676 ·
Status: Completed7 comments

Log in to comment and vote

Comments7

  • Samuel_ABRP

    Team•

    Oct 16

    Should work now. Please try it.

  • ABRP User #1652736

    •

    Aug 1

    The same thing is happening for us and our Trailseeker. Given we can connect, we’re using ODB via the BZ4X Touring currently.

  • ABRP User #2556676

    •

    Jul 20

    A quick update. Ignore the comment about the difference n values between what ABRP displayed and what the dashboard was showing. When I went out after the previous post I noticed the values are now aligned.

    • ABRP User #2556676

      •

      Jul 28

      I’ve been tracking the SoC between what ABRP shows and what my Trailseeker dashboard shows. As the SOC of charge drops I’ve found it’s becoming more and more inaccurate. The earlier comment of them being equal, was when the car was close to fully charged. As the charge has dropped, the values have become further and further apart. I presume there’s some differences in the SoC PID formula between the 2026 Soltera that I’m currently pretending my car to be and the values required for a Trailseeker.

      I don’t need to charge very frequently, and won’t be using my car for a month between mid August and mid September, But when I next charge, I’ll gather some data points comparing Dash Soc vs ABRP SoC.

  • ABRP User #2556676

    •

    Jul 20

    [The following I sent as a reply to the email I received, but the info@featurebase.app address bounced. Not sure if that’s what should happen. This is a cut and paste of that email]

    Hi Samuel,

    Thanks for your reply.

    That makes sense as I did some further testing today and came to a similar conclusion. You beat me in updating my bug report with what I found.

    🙂

    The test I did was to create a "new" car, which was the 2026 Soltera and was able to pair that. I was then able to get SoC data into ABRP via Bluetooth. One thing I noticed was that there was about a 3% difference between what my dash showed as the SoC and what ABRP was reporting. ABRP was higher. But apart from that it seems to be working. Is there any test I can do to confirm it's getting all the data you need?

    Related to that, is there any further testing or diagnostic information you'd like me to gather to assist you? I'm happy to try and assist getting the data you need to use ABRP with my car to the fullest.

    Also, to save wasting everyone's time, could I suggest rather than not providing the OBD pairing, provide a message saying something to the effect of "We don't yet know the correct OBD PIDs for this car so Bluetooth pairing is not possible". That would be the minimum to avoid others going through what I went through. Ideally, after giving a suitably scary warning message, provide a mechanism for people to either simply enable OBD pairing, or at least gather the data you require to enable OBD paring. I understand the whole OBD data stuff is a bit of a mess and I'm a newby to the whole subject. I appreciate its possible there some risks is simply allowing people to randomly enable this.

    Thanks

    Andrew

  • Samuel_ABRP

    Team•

    Jul 20

    Hi, we usually do not enable every car by default with OBD, as we never know, if it’ll work or not. But if you confirm the Trailseeker worked with the Solterra commands, we can enable it. Did you try it with the 26+ model order the <= 25 model?

  • ABRP User #2556676

    •

    Jul 16

    I've just uploaded a bug report maybe two) via the button at 14:26 GMT+10.