VSG
Well-Known Member
As I said above:When I first read your post about all the things RA can't do, it seemed pretty bad. And then I realized most of those things are things I don't want RA to do while driving. In fact, some of them could be dangerous if RA could control them when the truck is moving.
Fold the mirrors: may be useful when parking, but not when driving. Definitely I don't want the mirrors folding when I am on the highway.
[...etc.]
Specifically, if you're allowed to fold the mirrors from the UI while driving, how can it possibly be a safety concern to perform that same action through voice commands? If anything, it's SAFER to do it by voice.It has been my often expressed opinion over many years that the voice assistant should be able to do everything that can be done through the UI and the physical buttons. The software already exists to control all these things within operating constraints (e.g. can't open the hood, by any means, while the car is in drive) so it's really just a matter of exposing this functionality through the voice interface in addition to the current controls.
Just because you can't imagine a need for this doesn't mean the voice command should be disabled. Perhaps other people would find this useful? And needlessly limiting the ability of the voice assistant to do things that can be done through physical buttons or the UI also greatly limits what can be done through automation.
I'm not going to go over each and every example, but let's consider folding the mirrors again. You don't need it, but if you spend any time reading this forum you will see that many other people have been asking Rivian for some form of geofenced mirror folding. For example, I might need the mirrors folded (and perhaps the ride height lowered) to fit in my garage. Why shouldn't I be able to say "Hey Rivian, prepare for docking" and have all those actions performed for me instead of having to fumble in various places of the UI to get it done, all the while turning into my driveway and trying to avoid kids and toys on the sidewalk? (I would have been able to do this for years, with Alexa routines, if Rivian had allowed Alexa access to more functions.)
Sure you may not find that useful, but others will. What possible reason is there to limit this arbitrarily? It's actually more work for Rivian to have a separate "list" of things that the UI can do vs. what the voice assistant can do, and if Rivian ever does decide in the future that folding the mirrors while driving presents a safety hazard, there are now two different places where they will have to enforce that (voice and UI separately) rather than just one unified means of authorizing actions. That means more opportunities for bugs, because you have different code for performing the action via UI vs. voice.
One of the ways I use Alexa is to "turn on the camera" when I am pulling into tight spots and need to be able to see more things. By definition, I only need to do this when I'm fully engaged turning and driving in a potentially busy situation - my hands are occupied. Being able to do this via voice makes this much safer for everyone.
But frankly, safety has nothing to do with most of these inconsistencies: "turn on defrost" works but "turn on defog" doesn't? - that's not a safety issue. It's just poor integration, whether it's Alexa or Rivian Assistant.
Sponsored