ABRP V5.7.5 Establishing the OBD BLE connection on Smart #1 almost never succeeds, error “could not find SOC in the car data response” and others

iPhone 12 Pro iOS 18.4.1

Smart #1 SmartOS 1.5.2

Veepeak OBDCheck BLE+ / Vgate vLinker MC+ (BLE)

ABRP V5.7.5 (3343)

I’m using Smart #1 with CarPlay. The dongle is only connected to ABRP.

The BLE connection for Smart #1 didn't work for months. By chance, I tried the BLE connection for the Smart again on April 19, 2025, and lo and behold, it worked perfectly with ABRP V5.7.4 (3338). I then drove several longer distances over several hours on April 20 and April 21 with two different OBD BLE dongles. Both worked perfectly, including the transmission of the SoC, current and voltage values, and I was delighted:

I then enquired who helped fixing this, a user from the German Smart-1-forum had created log files for you in the last few weeks, so your team was able to significantly improve the BLE connection for the Smart #1, not to say make it error-free. Many thanks for that.

But already on April 22, the BLE connection is only briefly established and then does not work for minutes, until it establishes itself again very briefly, and then does not work again, and so on.

The myDrive graph looks like this: Only sporadic power and SoC values:

When setting up the BLE connection, I select my Veepeak dongle, for example:

Then this error message appears:

After I press Retry, this error message appears:

After I press Retry again, all values ​​seem to be successfully received, but the current is zero (the current of the car is indeed always higher then zero):

Then I save, remove the BLE link, and relink it again.

This error message appears again:

After I press Retry, now some values ​​are coming, but only SoC and current. Voltage is missing and current is zero again which it isn’t in reality.

About a week ago (the App Store doesn't show the exact date), I installed ABRP V5.7.4 (3338). Therefore, I can say that the BLE connection with ABRP V5.7.4 (3338) worked reliably for the first time in months. Unfortunately, it only worked for the first three days after installation, and then it stopped working. I installed ABRP V5.7.5 (3343) later on April 24th, but unfortunately, the problems haven't gone away.

I have already reset the PID editor for my Smart #1 several times, but that did not solve the problem.

It's not just me who has this problem, but also many users from the German Smart Emotion forum and the Smart 1 forum.

Did ABRP distribute a hotfix between April 21 and 22 that could be causing this?

I took all the screenshots on April 26 around 2pm German time, with the debug button switched on.

Please let me know how I can help you with additional log files and screenshots so that it works again like it did from April 19th to 21st.

Thank you very much!