A few different ways:
1) Easiest is to use
https://testmycode.cc/. It was set up by
@segbrk to help us define some of the fields in the gRPC API [0]. You put in your Lucid Motors credentials, it authenticates with the real Lucid Motors API (that we reversed) and returns a lot of info.
That info is cleaned for anything sensitive [1], and then you can optionally submit the info to us so we can glean anything useful from it to expand the API. The last step is helpful to us, but not required to view your own info. Your credentials are not stored anywhere, and the sensitive info that is cleaned isn’t either.
Of course, you may not trust it (which I get - again, I am a security wonk), so…
2) Under the hood it is running
https://github.com/nshp/python-lucidmotors. The second easiest option is to clone / download that GitHub repo, follow the instructions there, and get the data on your terminal locally - assuming you’re comfortable with the terminal and running some Python.
3) The third easiest option [2] is to use the Home Assistant integration:
https://github.com/borski/ha-lucidmotors
Follow the instructions there after you have installed Home Assistant and you’ll see all the info show up as entities that update in real time. [3]
[0] Since, unlike the older REST API, gRPC fields are just unlabeled integers - mapping those was a pain, and mostly involved getting tons of data from different cars and comparing the results of the gRPC API call and the REST API call.
[1] I think it includes the avatar, if you’ve selected one, which is a fix we haven’t made yet - sorry about that.
[2] If you are already running Home Assistant somewhere, this is actually the easiest option, by far. It’s only harder if you don’t already have HA set up - but HA gets you a ton of benefit, if you do choose.
[3] Not actually real time, but close enough. It updates regularly.