3rd Party Integrations: Use main profile or create a new "driver"?

[emroch]

My R2 will be my first Rivian (and EV), so I'm looking for advice on the best practices for data collection. I have set up an account on Rivian Roamer and also installed the (Unofficial) Rivian Home Assistant integration.

Both of these have account linking guides that mention creating a secondary driver profile for linking the integration. It sounds like this won't impact the data collection or functionality of either integration, but I'd like to confirm that.

What are the real risks/tradeoffs for using my primary account vs a backup account?

• CON: cluttered vehicle UI showing extra "drivers"
• CON: more emails/passwords to keep track of
  • I own my own domain and use a password manager, so its won't be an issue to create email aliases or unique passwords, its just more stuff to manage.
• PRO?: If Rivian retaliates against unauthorized use of the API, my main account presumably won't be affected.
• PRO?: If RR or HA are somehow compromised, my main account would be safe.
  • Seems like neither integration stores my password, so the only leak would be a temporary login token.
  • Is this actually a valid concern? Is there other PII that could be leaked that a compromised dummy account would not also leak?

What are other folks doing? Is it common to set up a dummy account? If so, should I create separate ones for RR and HA, or just have one fake account?

Sponsored

 

[Rivian Roamer]

My R2 will be my first Rivian (and EV), so I'm looking for advice on the best practices for data collection. I have set up an account on Rivian Roamer and also installed the (Unofficial) Rivian Home Assistant integration.

Both of these have account linking guides that mention creating a secondary driver profile for linking the integration. It sounds like this won't impact the data collection or functionality of either integration, but I'd like to confirm that.

What are the real risks/tradeoffs for using my primary account vs a backup account?

• CON: cluttered vehicle UI showing extra "drivers"
• CON: more emails/passwords to keep track of
  • I own my own domain and use a password manager, so its won't be an issue to create email aliases or unique passwords, its just more stuff to manage.
• PRO?: If Rivian retaliates against unauthorized use of the API, my main account presumably won't be affected.
• PRO?: If RR or HA are somehow compromised, my main account would be safe.
  • Seems like neither integration stores my password, so the only leak would be a temporary login token.
  • Is this actually a valid concern? Is there other PII that could be leaked that a compromised dummy account would not also leak?

What are other folks doing? Is it common to set up a dummy account? If so, should I create separate ones for RR and HA, or just have one fake account?

From a security standpoint there isn't much different. You cannot control a vehicle without pairing a key which requires your own action to accomplish. At any point you can invalidate all generated tokens via the sign-in process by changing your password. Not only that, even if your password were somehow compromised (most, if not all 3P services never store your password)... it still requires 2FA to sign in.

It comes down to mostly convenience. Using your primary account means one password to track, you get vehicle delivery dates and future enhancements that only the "Primary owner" has access to.

The primary risk is throttling. Rivian limits the numbers of connected clients by account. So you could in theory impact your primary app account if you start signing up to a bunch of services. I don't know what the exact limit is.

Rivian Roamer specifically is deeply optimized to support Rivian App + RR without impact. Beyond that is unknown.

 

[emroch]

Thanks, Chad!

The primary risk is throttling. Rivian limits the numbers of connected clients by account. So you could in theory impact your primary app account if you start signing up to a bunch of services. I don't know what the exact limit is.

What would this look like? API requests being rejected? App functions failing to load?

Sounds like there are more pros than cons to keep RR on the primary account. Unless anyone else has feedback about the HA side, I'll probably start with my main account there too and keep an eye out for issues.

 

[Rivian Roamer]

Thanks, Chad!

What would this look like? API requests being rejected? App functions failing to load?

Sounds like there are more pros than cons to keep RR on the primary account. Unless anyone else has feedback about the HA side, I'll probably start with my main account there too and keep an eye out for issues.

Yeah, subtle failures in the Rivian app though they're generally transient.

Rivian Roamer also offers an easy transfer mechanism to switch accounts if you ever to decide to.

Sponsored