Live data not showing up

[digitalw0lf]

Until recently, I was able to get live data on the map from my Bolt.  I've updated my settings in Torque, and have it pointed to http://api.iternio.com/1/tlm/ampera60, which is what the setup says to use, to upload the data.  It used to actually have bolt in the URL, but now it's ampera.  When I was looking at the live data this morning, the only information coming through was my speed.  I know I have the correct PIDs because I can see all of the information in Torque.  Is the endpoint correct?

[EddieRT]

I am having the same problems. Worked last week then we took a trip on Sunday and it stopped working. After much fiddling i found out my car had changed to an ampera and had new instructions but they didn't work. Reset to bolt and it worked until yesterday when the instructions for bolt seem to have changed to the new web server. Only picks up speed. Would really like to have it working again since i am in the middle of my longest trip ever.

[digitalw0lf]

I feel your pain.  I'm planning a long trip in September, which is why I want it working.

[Jason-ABRP]

Huh, this is very strange, it worked for me last weekend as well on my own road trip.  We are having some server issues right now, which we're getting resolved as fast as we can, if that doesn't fix it I'll take a deeper look into why this may not be working.

[EddieRT]

What settings should we be putting for the Bolt? Should they be the same as Ampera?

35 minutes ago, Jason (ABRP) said:

Huh, this is very strange, it worked for me last weekend as well on my own road trip.  We are having some server issues right now, which we're getting resolved as fast as we can, if that doesn't fix it I'll take a deeper look into why this may not be working.

 

[EddieRT]

I changed the web server address to

http://api.iternio.com/1/tlm/bolt60

And i appear to be getting all the data now.

The instructions still list the wrong address of

http://api.iternio.com/1/tlm/ampera60

I'm not in a position to go on a trip right now but the data appears to populate in the "view live data" display now.

[Jason-ABRP]

1 hour ago, EddieRT said:

I changed the web server address to

http://api.iternio.com/1/tlm/bolt60

And i appear to be getting all the data now.

The instructions still list the wrong address of

http://api.iternio.com/1/tlm/ampera60

I'm not in a position to go on a trip right now but the data appears to populate in the "view live data" display now.

You are absolutely correct, it should be bolt60, I've corrected the webaddress, so you should see it correctly in the instructions.  Not sure how that one slipped past me.  Glad to hear it's working!

[TimP]

Glad I found this thread. I finally got an old android phone set up with Torque pro to use the real time data and ran into this problem.

ill try charging the web address this evening. 

Thanks

[digitalw0lf]

Once I changed the upload link back to the bolt link, live data started working.  However, now it only seems to work once.  I'll get it set up and have it work for 1 trip.  But, the next trip I try to use it, the live data doesn't show up.  I double check that the ID I have in Torque is the same as what I see in the setup dialog, and it always matches what it should be.  And I know Torque is getting the data, because I put a floating widget up over the browser window and see the data changing.  The only way I can get it to show up again is to clear the cache in Chrome, but that causes it to generate a new ID to use in Torque, so I have to reconfigure it.

Is anyone else experiencing anything like this?  I've gone so far as to turn off data syncing for the browser, just in case somehow my settings from my desktop Chrome were overwriting information on my mobile Chrome, but that hasn't helped.  I'd had this happen once before, but I only had to clear the cache one time, and I was fine for months after that.  Now, I have to do it daily.

[EddieRT]

1 hour ago, digitalw0lf said:

Once I changed the upload link back to the bolt link, live data started working.  However, now it only seems to work once.  I'll get it set up and have it work for 1 trip.  But, the next trip I try to use it, the live data doesn't show up.  I double check that the ID I have in Torque is the same as what I see in the setup dialog, and it always matches what it should be.  And I know Torque is getting the data, because I put a floating widget up over the browser window and see the data changing.  The only way I can get it to show up again is to clear the cache in Chrome, but that causes it to generate a new ID to use in Torque, so I have to reconfigure it.

Is anyone else experiencing anything like this?  I've gone so far as to turn off data syncing for the browser, just in case somehow my settings from my desktop Chrome were overwriting information on my mobile Chrome, but that hasn't helped.  I'd had this happen once before, but I only had to clear the cache one time, and I was fine for months after that.  Now, I have to do it daily.

Yes, I've started having problems the last two days similar to what you're describing. I've been unable to get it going again reliably, sounds like you're doing better than me in that respect. What I've noticed is the id changing almost every time i check it. I have a phone and tablet and i see a different id if i use the app shortcut vs the browser (so 4 different IDs that change). I hadn't tried to use the tablet until this started so i thought it was related but maybe not.

[Jason-ABRP]

This issue was my fault, was working on better integration between front and back on data.  The update passed all my tests, but there's some kind of unforeseen interaction between the two that's causing the issues.  Until I figure this out and solve the issue I've reverted the update and we should be back to the previous function.  

[EddieRT]

3 hours ago, Jason (ABRP) said:

This issue was my fault, was working on better integration between front and back on data.  The update passed all my tests, but there's some kind of unforeseen interaction between the two that's causing the issues.  Until I figure this out and solve the issue I've reverted the update and we should be back to the previous function.  

Thanks. Been low priority for me since my road trip is over. Worked great last week for the last two legs.

That is until Electrify America decided to shut down the only charger for 150 miles in any direction in Yuma, AZ and not inform their customer support.

[noradtux]

Live data still doesn't seem to work for me. I use the telemtry rest-api.

[digitalw0lf]

13 hours ago, Jason (ABRP) said:

This issue was my fault, was working on better integration between front and back on data.  The update passed all my tests, but there's some kind of unforeseen interaction between the two that's causing the issues.  Until I figure this out and solve the issue I've reverted the update and we should be back to the previous function.  

It did work for me yesterday afternoon, and based on the time this reply was posted, the revert happened after I used it.  This morning, it did not work for me again.  Would the revert have reset the keys?  If so, I'll clear my cache again and hopefully everything is straightened out.  Otherwise, the revert did not appear to correct the problem.

[edwinth]

same issue here: 

 

[digitalw0lf]

Just as an update, after I did a cache clear, the app has been working for me with no issues.

[noradtux]

I did an extended trip last weekend and it worked perfectly

[edwinth]

I keep getting this message in live data "Missing telemetry: soc, is_charging,"

How can I fix this ?

 

[Jason-ABRP]

On 8/20/2019 at 4:20 AM, edwinth said:

I keep getting this message in live data "Missing telemetry: soc, is_charging,"

How can I fix this ?

 

What car / data system are you using? That message means that your setup isn't providing two key pieces of information to ABRP - Charging Status and State of Charge.  Those two are very important, as without them we can't provide a live data mode for you.  If you're using Torque, double check that you've downloaded and imported all the right files, and selected all of the right PIDs that the setup instructions call out.

On 8/19/2019 at 2:03 PM, noradtux said:

I did an extended trip last weekend and it worked perfectly

Glad to hear my fix right before my vacation worked!  Ended up rolling back the update that caused the issue, seemed to be a timing issue between front and back, asynchronous processing is always hinky!

[jcgillespie]

On 8/20/2019 at 4:20 AM, edwinth said:

I keep getting this message in live data "Missing telemetry: soc, is_charging,"

How can I fix this ?

 

I've got the exact same problem with a 2018 Bolt EV. This was working before, but stopped recently when I went to use it for a longer trip. I re-imported the custom PIDs and reset all the logged information per the ABRP prompt. The screenshot below was taken when the car was charging (L1 AC) and is at 87.8% charged per Torque.

 

[digitalw0lf]

I'm seeing this same problem. I have a 2019 Bolt EV. I recently took a long trip. On September 15th, on my trip down to my vacation,it was working fine. However, when heading home yesterday, it gives me this same screen. It is always reporting my SoC at 20%. I have tried every trick I know, clearing Chrome's cache, clearing Torque's cache, restarting my phone, even unplugging and plugging in the reader, and it is always reporting 20% and showing those same errors on the live data screen.

[Jason-ABRP]

12 hours ago, jcgillespie said:

I've got the exact same problem with a 2018 Bolt EV. This was working before, but stopped recently when I went to use it for a longer trip. I re-imported the custom PIDs and reset all the logged information per the ABRP prompt. The screenshot below was taken when the car was charging (L1 AC) and is at 87.8% charged per Torque.

That's very strange, Torque reports reading the PID correctly, but it's not being reported to ABRP.  Have you double checked the Data Logging and Upload > Choose what to Log list? Perhaps it somehow got unselected?

I went ahead and removed @jcgillespie's and @digitalw0lf's telemetry entries, in case old data was somehow interfering.  If you try again, it should repopulate with whatever you're sending ABRP from Torque.

[digitalw0lf]

At least for me, I know it was selected because when I cleared the cache for Torque, I had to go through the setup process again, so I had to select all of the different PIDs to send. 

 

It's strange to me because after clearing Chrome's cache, so I got a new ID to use in Torque, and clearing Torque's cache, so I had to reset the server address and ID, plus reselect all of the PIDs, it was still showing a 20% state of charge. It seems like somehow it got my account locked to the old information.

 

I've got another drive in the morning, so I'll try it again and see if it's working.

[Jason-ABRP]

I tried it out this morning on my commute with Torque (been working on a more plug and play solution that requires less setup than torque), and I got the same result, so something isn't right. Probably something I did when adding support for the Spark, since they share PIDs. Will troubleshoot and fix tonight when I get home from work.

[Jason-ABRP]

I believe the problem was in my backfill code, where it would fill in missing telemetry if it existed in the previous set.  For now I've disabled that code, and will troubleshoot and restore that function later this weekend.

It seems to work as expected now.

[TomTomZoe]

I‘m driving a 2017 Ampera-e and used the bolt60 upload URL without errors till some days. I could see live data on ABRP website and in the app.

After I discovered that that there’s a special ampera60 upload URL meanwhile, I changed the upload address from bolt60 to ampera60 to be more accurate. But this didn‘t worked for me, I got no more live data. Every time I checked the Live data Setup help, I got a new GUID style password. I didn‘t know why. So I always used the newest password which is shown to me. 

The ampera60 upload still did not work, so I changed back to bolt60, but bolt60 doesn‘t work either now. I also get the SOC-missing and is_charging missing errors in the live data screen. The live data now shows only old values from the past and the age field display 40+ hours. It seems that something stucks.

I didn‘t change any Torque Pro Upload Settings, I can see all necessary data displayed within Torque Pro.

I won‘t like to register with a second email address to check if things go all right with a new account.

Can you please reset the recorded data of my account in your database like you did that for other people? I hope this may also help in my case.

Thank you very much!