Show HN: Pi-C.A.R.D, a Raspberry Pi Voice Assistant
61–70 of 101 posts
Re: Show HN: Pi-C.A.R.D, a Raspberry Pi Voice Assistant
#62Re: Show HN: Pi-C.A.R.D, a Raspberry Pi Voice Assistant
#63I wanted to create a voice assistant that is completely offline and doesn't require any internet connection. This is because I wanted to ensure that the user's privacy is protected and that the user's data is not being sent to any third party servers. Props, and thank you for this.
Extra kudos for the name - and extra extra for using the good old "Picard facepalm" meme. But seriously - the name got my attention, then I read the introduction and thought "hey, Alexa without uploading everything you say to Amazon? This might actually be something for me!". > The default wake word is "hey assistant" - I would suggest "Computer" :) And of course it should have a voice that sounds like https://en.wik…
Re: Show HN: Pi-C.A.R.D, a Raspberry Pi Voice Assistant
#64Earlier quoted context omitted.
Just configure it to respond to "Computer" and you're good to go.
As a professional technology person I say “computer” about 1megatoken per day
That's a perfect opportunity to get better at cosplaying a Starfleet officer.
(Seriously though, a Federation-grade system would just recognize from context whether or not you meant to invoke the voice interface. Federation is full of near-AGI in simple appliances. Like the sliding doors that just know whether you want to go through them, or are just passing by.)
Re: Show HN: Pi-C.A.R.D, a Raspberry Pi Voice Assistant
#65> Why Pi-card? > Raspberry Pi - Camera Audio Recognition Device. Missed opportunity for LCARS - LLM Camera Audio Recognition Service, responding to the keyword "computer," naturally. I guess if this ran elsewhere from a Pi, it could be LCARS.
Or LLM Offline Camera, User Trained Understanding Speech LOCUTUS
Re: Show HN: Pi-C.A.R.D, a Raspberry Pi Voice Assistant
#66Why does Picard always have to specify temperature preference for his Earl Gray tea? Shouldn’t the super smart AI have learned his preference by now?
Most of Starfleet folks seem to not know how to use their replicators well anyway. For all the smarts they have, they use it like a mundane appliance they never bothered to read the manual for, miss 90% of its functionality, and then complain that replicated food tastes bad.
Re: Show HN: Pi-C.A.R.D, a Raspberry Pi Voice Assistant
#67I didn't see a mention of languages in the readme. Does this understand languages other than english?
Re: Show HN: Pi-C.A.R.D, a Raspberry Pi Voice Assistant
#68It would be cool to see some raspi hats you could plug a GPU into, though unsure of how practical or feasible that would be. Todays graphics cards are tomorrows e-waste, perhaps they could get a second life beefing up a diy raspi project like this
Re: Show HN: Pi-C.A.R.D, a Raspberry Pi Voice Assistant
#69Earlier quoted context omitted.
I would love for Apple/Google to introduce some tech that would make it provable/verifiable that the camera/mic on the device can only be captured when the indicator is on and that it isn't possible for apps or even higher layers of OS to spoof this
Thinkpads come with that, an unspoofable indicator that will tell you with 100% certainty that your image is not being recorded or even recordable unless the physical operator of the machine allows it. Can't beat a physical cover if you really want to be sure!
Re: Show HN: Pi-C.A.R.D, a Raspberry Pi Voice Assistant
#70Earlier quoted context omitted.
I watched the demo, to be honest if I saw it sooner I probably would have tried to start this as a fork from there. Any idea what the issue was?
No, but the core concept had changed so much, between the firmware version when I bought it, and what it is now, that I'm not surprised if the upgrade is a buggy process. It's a shame, because I only wanted a tenth of what it could do- I just wanted it to send text to a REST server. That's all! And I had it working! But I saw there was a major firmware update, and to make a long story short, KABOOM.
Early versions sent requests directly from devices and we found that to be problematic/inflexible for a variety of reasons.
Our new architecture uses the Willow Application Server (WAS) with a standard generic protocol to devices and handles the subtleties of the various command endpoints (Home Assistant, REST, OpenHAB, etc). This can be activated in WAS with the "WAS Command Endpoint" configuration option.
This approach also enables a feature we call Willow Auto Correct (WAC) that our users have found to be a game-changer in the open source voice assistant space.
I don't want to seem like I'm selling or shilling Willow, I just have a lot of experience with this application and many hard-learned lessons over the past two decades.