Rivian ABRP integration working (if you're motivated ?)

[shap]

Also, as far as I understand, per the documentation of the API:

"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)."

We do not have a 'power' sensor so I am not sure what ABRP will calculate.

Sponsored

 

[djsider2]

Is using ABRP better than using Rivian app (even though its ABRP) ?

Does integration require me to have ABRP Premium and pay?

 

[shap]

Rivian is not ABRP, they integrated only small part of it. As for benefits, it is all depends where are you live. ABRP is working better for me in some cases.

You do not need to have premium ABRP subscription IMHO

 

[bueller]

Thank you - quick question - you are using a speed sensor and multiply it by 1.609344. I think the sensor is a meter per second, so it needed to be converted to km/h, no?

I didn't change that from the gist and my speeds in ABRP are correct. The HASS component must somehow auto-convert m/s to mph, then that multiplication converts that to km/h ABRP units.

For instantaneous power, similarly the gist wasn't trying to provide that either, except when charging. Regardless ABRP does still calculate a reference calibration for me. I expect they should be able to get a rough estimate by watching changes to the odometer and the SoC.

 

[bueller]

Attached, to their version I added support to post to the ABRP endpoint no more often than every 5 seconds. Also sending up a rounded version of the bearing because it updates too often. One note, for some reason my home assistant entities for charging energy aren't consistently getting updated, so I commented out the charging energy updates.

Forgot another change I made. The gist timestamps the telemetry report to ABRP with the time HASS formatted the message Whereas I thought it could make any rough estimates ABRP makes more accurate to use the timestamp of the last change seen by HASS for any of the reported telemetry parameters.

 

[tobidogger]

Since my Rivian has been stuck in the service center for weeks with no sign of reappearing after a week of ownership...I've just trolling these forums seeing what's up.

I am looking this over and not understanding what the use case is - what problem are you trying to solve? You like ABRP and want to send live data to it? Can you elaborate on why? How is this better than Waze or the built in map and their route planners? Maybe this matters more in place with more roads - unlike western WA, HAHAHA!

 

[mindstormsguy]

There isn’t as much utility here anymore. The Rivian route planner in the car is very good. (No surprise, as they bought ABRP)

When I first set this up, that wasn’t the case.

 

[shap]

I didn't change that from the gist and my speeds in ABRP are correct. The HASS component must somehow auto-convert m/s to mph, then that multiplication converts that to km/h ABRP units.

For instantaneous power, similarly the gist wasn't trying to provide that either, except when charging. Regardless ABRP does still calculate a reference calibration for me. I expect they should be able to get a rough estimate by watching changes to the odometer and the SoC.

From what I see, ABRP is not calculating the consumption correctly. If you look at the REST API call, you will see that speed is very low (at least in my case). And Therefore consumption is incorrect as well. How your ABRP screens look like ?

I have only "Low speed" information, despite driving over 85 mph to Houston and back.

 

[ryunited]

There isn’t as much utility here anymore. The Rivian route planner in the car is very good. (No surprise, as they bought ABRP)

When I first set this up, that wasn’t the case.

HAS Rivian integrated ABRP tech since the acquisition into the experience?

I remember people celebrating when they made that acquisition but hasn't seen much since.

 

[mindstormsguy]

My guess is that some of the baseline IP has been pulled in. But I don’t think the Rivian route planning is ABRP exactly.

 

[shap]

There isn’t as much utility here anymore. The Rivian route planner in the car is very good. (No surprise, as they bought ABRP)

When I first set this up, that wasn’t the case.

There is one advantage for ABRp - I use it for planning purposes. It is much easier to create a route and include chargers you want/check with plugshare. And you can do it on your MAC/PC

 

[bueller]

How your ABRP screens look like ?

I have only "Low speed" information, despite driving over 85 mph to Houston and back.

I do see the same on that screen, I e. "Low speed" is the only non-zero number. But the speeds and consumptions that show up in drive history seem right, and the reference consumption number it seems to be converging to is basically the same as what the center display gauges app is showing.

Below is from today, starting out with a combo of rural and suburban roads, before getting on the freeway for 7-8 minutes and ending shortly after the off ramp. Looks correct to me.

 

[shap]

I do see the same on that screen, I e. "Low speed" is the only non-zero number. But the speeds and consumptions that show up in drive history seem right, and the reference consumption number it seems to be converging to is basically the same as what the center display gauges app is showing.

Below is from today, starting out with a combo of rural and suburban roads, before getting on the freeway for 7-8 minutes and ending shortly after the off ramp. Looks correct to me.

I see, thank you. I do not have a premium subscription, so I can not see the history. However, I doubt that information from telemetry is calculated correctly. I am now charging (7.7kW per Rivian), but ABRP still shows 6.6kW:

It also makes no sense that sending a meter per second multiplied by 1.6 is working correctly - I verified that my data is m/s. The funny part is that indeed sending m/s * 1.6 makes ABRP calculate consumption 'close' to the real one (2.2 instead of 2.4 in my case).

But in general, why Rivian can not just push car telemetry per owner request directly to ABRP is sad...

 

[bueller]

I do not have a premium subscription, so I can not see the history.

I don't have premium either, but I can still go to My Drives > View All and see data from drives over the last 24 hours. I can't see any drives older than that, and I can't export or save any data -- will get nagged to upgrade to premium if I try.

I am now charging (7.7kW per Rivian), but ABRP still shows 6.6kW:

I see the same, the charging power in ABRP is somewhat off. In my version of the REST API call, I never post power data, only a charging true/false flag and the SoC data. So ABRP must be guessing charging power from the rate of change in the SoC I am posting.

But in general, why Rivian can not just push car telemetry per owner request directly to ABRP is sad...

??

 

[shap]

I tried to push "power" but it made no difference. Seems power parameter is used for something else. I also set the charging speed parameter - but it also made no difference...

I have a feeling they are not really maintaining this rest api.

Sponsored