Live data from Hacker News

Using Google Assistant with AutoPi to enable voice control of a car

autopi.io

21–30 of 40 posts

Re: Using Google Assistant with AutoPi to enable voice control of a car

#21
When is AutoPi going to add the option to go keyless through facial, voice, optical, or fingerprint recognition?

I guess Ford already patented something like this but it would be nice to have it open source too.

http://www.biometricupdate.com/201502/ford-granted-patent-fo...

Re: Using Google Assistant with AutoPi to enable voice control of a car

#22
post #14

First off this looks cool. But these 4G connected smart ODB dongles scare the crap out of me. You are giving an IOT device the ability to disable breaks, the transmission, and lock you inside. I'm not really worried about a Maximum Overdrive type situation, giving this much control to a category of devices that was able to take down Dyn because so many of these devices used a subset of 60 common factory default usern…

OBD2 is incapable of doing any of those things. It is a diagnostic interface to read out information about important systems. There is a standard set of data streams, and vendors add customizations on top. So any OBD2 scanner should work on any car, but it may not be able to parse/display non-standard data streams.

There is some danger of control over the interface, but the interface does not specify any control operations beyond resetting diagnostic codes. The vulnerabilities in the interface stem from automakers repurposing the protocol, and are model/maker specific.

It seems like another protocol would only help if it defined control mechanisms so that carmakers would stop abusing OBD2.

Re: Using Google Assistant with AutoPi to enable voice control of a car

#23
It looks like a promising piece of hardware (though I am not sure if it's an RPi Zero they're adding BT and Wifi to, or actually an RPi Zero W - which would be easier, you'd think). My last two cars both put their OBD II ports exactly where my left leg is under the steering wheel, so I hope they ship it with a short right-angle extension cable (I use a much shorter BT dongle to connect to my phone current, it doesn't project too far).

Re: Using Google Assistant with AutoPi to enable voice control of a car

#24
I didn't see Dashbot (https://www.kickstarter.com/projects/1598272670/dashbot-a-49...) mentioned here: it's pretty much the same thing but instead using Alexa and not using (potentially scary) OBD port connection. With Ford announcing Alexa integration coming this summer to SYNC3 (https://media.ford.com/content/fordmedia/fna/us/en/news/2017...) it seems devices such as these will be more commonplace.

Question to HN: What can Alexa/GA integration enable in a car other than the mundane music search, ask directions, etc. scenarios? How many of you would want to use it to send short messages (e.g. "Sorry!" after cutting someone off) to a small LED display mounted on your rear bumper?

Re: Using Google Assistant with AutoPi to enable voice control of a car

#25
Be it Google Assistant SDK or Amazon AVS, these SDKs are mainly used for voice services. If you add an additional layer on top to customize the wake word/initial trigger, won't these systems/setups be something like : Custom wake word processing Engine -> IFTTT Maker or Amazon skills -> Underlying subsystem that perform action -> IFTTT Maker or Amazon skills -> Custom wake word processing Engine == Custom wake word processing Engine -> Google Assistant SDK or Amazon AVS SDK -> Underlying subsystem that perform action -> Google Assistant SDK or Amazon AVS SDK -> Custom wake word processing Engine ?

Re: Using Google Assistant with AutoPi to enable voice control of a car

#26
post #6

Earlier quoted context omitted.

I've seen people use Google Voice in a loud bar. It seemed to be effective. I can't get Siri to work under those conditions, however. The noise should be a solvable problem.

Yeah, Google's voice recognition has worked for me everywhere, even loud clubs. It's quite magical. I'm sure it would work in the car. Now, whether I would trust Google with that data is a different question. (Spoiler: no.)

Inside the car is a bit of a different since the device won't be handheld and you may not even be directing your voice toward the microphone.

If you have a phone with a high-quality mic, mount it in the right spot, and speak loudly, it can usually get the job done though.

Performance in general has gotten a lot better in recent years, though it's tough to call it a "solved problem".

Re: Using Google Assistant with AutoPi to enable voice control of a car

#27
post #3

Cool, and no offense, but let me know when a third party reviews it. Voice recognition and personal assistants are annoying enough in a quiet house (but arguably useful). I would be surprised if it is useful yet in a noisy moving car.

Your cautious optimism is well-founded. Having worked in the space for a few years, I've found voice tech in the car isn't quite the promised land I was hoping it would be.

The experience is still uneven. There are times when I'm amazed the recognition and language models could pick out proper names of friends and other times when I'm red in the face shouting "I SAID 'PLEASE GET CELERY', NOT 'PLEASE SELL TO ME!'"

For the time being, we still need analog button backups to handle the cases where speech rec fails or routinely misinterprets. The long tail of error cases can actually be even more dangerous for the driver than a simple button press, since they can take your mind off the road for several seconds.

Re: Using Google Assistant with AutoPi to enable voice control of a car

#28
post #14

First off this looks cool. But these 4G connected smart ODB dongles scare the crap out of me. You are giving an IOT device the ability to disable breaks, the transmission, and lock you inside. I'm not really worried about a Maximum Overdrive type situation, giving this much control to a category of devices that was able to take down Dyn because so many of these devices used a subset of 60 common factory default usern…

Actually OBD on moderns cars is pretty much useless, it only reports the basic federally mandated emissions info for e-checks and that's it. All the fun stuff is on CAN and other often proprietary buses.

Re: Using Google Assistant with AutoPi to enable voice control of a car

#29
post #17

Earlier quoted context omitted.

This is not equivalent. The key distinction in the device from OP's post is that it actually connects to the OBD port in your car, giving you a direct connection the cars systems. The one you linked does not seem to do that at all.

Indeed but one has to question whether you actually want that level of control exposed given the dangers it presents. There's a lot to be said for air gapping critical systems.

Given how the most sought-after car today literally receives driving instructions through an OTA update, I've got a feeling we've all collectively decided we're ok with the dangers this brings, even if we didn't actually take part in that discussion :-/

Re: Using Google Assistant with AutoPi to enable voice control of a car

#30
post #17

Earlier quoted context omitted.

Indeed but one has to question whether you actually want that level of control exposed given the dangers it presents. There's a lot to be said for air gapping critical systems.

Given how the most sought-after car today literally receives driving instructions through an OTA update, I've got a feeling we've all collectively decided we're ok with the dangers this brings, even if we didn't actually take part in that discussion :-/

Driving instructions via OTA are fine as long as your in car entertainment system is separate from the cars engine control et al. Which is the air gapped point I was making.

Some cars are built this way too, thankfully.

Post reply on HN