Sponsored

Data logger?

duessell

Well-Known Member
Joined
Nov 24, 2020
Threads
19
Messages
240
Reaction score
272
Location
Syracuse, NY
Vehicles
R1T and Chrysler Pacifica PHEV
Anyone know of a data logger for Rivian or one maybe in the works? I'd enjoy digging into all the sensor data. Something like Teslafi perhaps.

I saw this post on Reddit:
Sponsored

 

Arky

Well-Known Member
Joined
Oct 6, 2021
Threads
5
Messages
294
Reaction score
366
Location
Colorado
Vehicles
Subaru WRX STI
+1 - frankly I'd love if they can just show us some of this info. Battery/motor temps or more detailed failure info if the truck says something is wrong.

RIght now users see things like regen not working or battery charge not maintaining high rate but no real indication of why, temps would be useful here.
 

OverZealous

Well-Known Member
Joined
Oct 19, 2021
Threads
8
Messages
592
Reaction score
1,477
Location
Louisville, Kentucky
Vehicles
2022 R1T LE, 2023 R1S Quad-Adventure
Occupation
Product Manager / Front-End Developer
Clubs
 
So there's an amazing integration for HomeAssistant already. It's built on this Python library.

However, literally last night there was a big hiccup, as Rivian suddenly retired the API that was being used, which means the entire integration is currently busted. The whole thing needs to get migrated over to using the GraphQL endpoint, but I'm not sure how long that will take.

If anyone has time to help out on that, it would be great. I'm not a Python developer (at all), so I'm of little-to-no use for helping here. (I mostly just report issues and feel guilty about not being able to assist.)
 
OP
OP
duessell

duessell

Well-Known Member
Joined
Nov 24, 2020
Threads
19
Messages
240
Reaction score
272
Location
Syracuse, NY
Vehicles
R1T and Chrysler Pacifica PHEV
So there's an amazing integration for HomeAssistant already. It's built on this Python library.

However, literally last night there was a big hiccup, as Rivian suddenly retired the API that was being used, which means the entire integration is currently busted. The whole thing needs to get migrated over to using the GraphQL endpoint, but I'm not sure how long that will take.

If anyone has time to help out on that, it would be great. I'm not a Python developer (at all), so I'm of little-to-no use for helping here. (I mostly just report issues and feel guilty about not being able to assist.)
I hope 1) Rivian makes data from more sensors available and 2) someone builds a tool for non-programmers. :)
 

Dark-Fx

Well-Known Member
First Name
Brian
Joined
Jul 15, 2020
Threads
148
Messages
13,553
Reaction score
27,353
Location
Michigan
Vehicles
R1T, R1S, Livewire One, Sierra EV, R1S
Occupation
Engineering
Clubs
 

Sponsored

OverZealous

Well-Known Member
Joined
Oct 19, 2021
Threads
8
Messages
592
Reaction score
1,477
Location
Louisville, Kentucky
Vehicles
2022 R1T LE, 2023 R1S Quad-Adventure
Occupation
Product Manager / Front-End Developer
Clubs
 
I hope 1) Rivian makes data from more sensors available and 2) someone builds a tool for non-programmers. :)
But first, 0) I hope that Rivian decides to release an official API instead of forcing its customers to reverse-engineer the API the way Tesla has.

It’s frustratingly anti-consumer how many companies lock our own data behind obfuscation, leading to less secure products because it encourages 3rd-parties to tinker with the API in ways that we’re never intended.
 
Last edited:

NY_Rob

Well-Known Member
First Name
Rob
Joined
Feb 9, 2022
Threads
23
Messages
5,400
Reaction score
7,977
Location
long island
Vehicles
Model 3 LR AWD, BMW i3 REX, 2024 Rubicon 4xe
Occupation
IT
But first, 0) I hope that Rivian decides to release and official API instead of forcing its customers to reverse-engineer the API the way Tesla has.

It’s frustratingly anti-consumer how many companies lock our own data behind obfuscation, leading to less secure products because it encourages 3rd-parties to tinker with the API in ways that we’re never intended.
Rivian doesn't even publish the names of the circuits on it's fuse boxes (they claim it's IP) and if you look in the current owners manual the word "fuse" is not even mentioned at all. And, that is information that potentially every single customer could use because blown fuses do happen.

With that in mind... assume 0.0000% chance of them ever declassifying their API.
 
Last edited:

OverZealous

Well-Known Member
Joined
Oct 19, 2021
Threads
8
Messages
592
Reaction score
1,477
Location
Louisville, Kentucky
Vehicles
2022 R1T LE, 2023 R1S Quad-Adventure
Occupation
Product Manager / Front-End Developer
Clubs
 

the_mace

Well-Known Member
First Name
Rob
Joined
Apr 8, 2022
Threads
11
Messages
414
Reaction score
343
Location
Boston, MA
Vehicles
Tesla Model S75D, Ford F350 Diesel, Mercedes GLC30
Occupation
CTO
Don't have my R1T yet so there's a limit to what I can poke at from the API. Here's where i'm at right now:

./rivian_cli.py --privacy
Order ID: xxxx2477
Order ID: ORDERED
Status: READY_FOR_FULFILLMENT
Item: R1T
Customer flow complete: No
VIN: xxxx7FCT
ID: Not available yet
Carrier: RIVIAN
Delivery date: Not available yet
Seems like I need the Vehicle ID before I can do much else. I can get my delivery address etc but I know all that.

Using https://rivian-api.kaedenb.org/ for docs and calling into https://github.com/bretterer/rivian-python-client for bits.

I worked on TezLabApp, EVTripping, and some other things so looking forward to playing with it more when I have some data.
 
 








Top