Slashdot Mirror
Amazon's Raspberry Pi Guide Lets Coders Build An Echo (bbc.com)
An anonymous reader quotes a report from BBC: Amazon has published an online guide explaining how to access its virtual assistant Alexa via a Raspberry Pi. The walkthrough includes access to the necessary app data and certificates in order to link the budget computer up to the tech giant's servers. Amazon says that users require at least the second-generation model, released in February 2015, as well as: a plug-in USB microphone, microSD card, ethernet cable, Wi-Fi wireless adapter, mouse, keyboard, and screen. The coding involved is limited to typing in sets of commands, but the guide explains the purpose of each one. Users also need to register for an Amazon Developer Account, which they can get for free.
I think no first generation boards is because they lack the power and ram necessary. It's a cool thing, I'm surprised frankly to see it but very excited at the possibilities.
I have a first generation (First run model) of the pi.
With only 256megs of ram, it is hard to do much with it. ;)
The second generation had 512meg and that made a lot of difference! I have a couple of them.
Then there was the second generation B+ with the extra ports, I have 3 or 4 of them laying around.
Now with the third generation having 4cores and 1g of ram, there is a lot you can do with it. That reminds me, I need to order a couple.
Just built one of these today actually. Only took me about 2 hours to get through setting up the Amazon keys/policies and the pi software and get it to successfully connect.
There are 3 things that do make it a little bit of a pain-
1- The setup is client/server with the client using Java and the server using Node.js. So there's multiple config files and dependencies to set up, hence multiple points of failure. This can make troubleshooting more difficult if there are issues.
2- you have to log onto Amazon.com via a web browser and generate a token EVERY time you start the Java client. This is noticeably awkward and an extra step. (I don't know how long the token lasts either.)
3- The license terms prohibit having the unit always listening like the Echo does. So you have to press a button or interact with the device somehow to activate 'listen' mode.
For the most part these are limitations that I can understand. Amazon is providing sample code for Alexa AVS to try to increase adoption. The github repo is designed for developers who want to incorporate Alexa into their products, not for end-users.
Not Microsoft's fault for developing an AI that accidentally imitated racist humans and ended up racist. In fact, this whole PC shit needs to end. You can't even tell the truth anymore if it offends anyone. Like the Harvard professor who mentioned true facts about women in mathematics and sciences. If the facts don't correspond to the feminist PC narrative, they must be suppressed.
Science is no longer about finding the truth, bit rather about just trying to justify whatever the fashionable progressive narrative is (equality, global warming, anti-war, anti-gun, CEOs and corporations are evil, and so on)
Oh, hey! Microsoft's Slashbot is still running!
"I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)
Not sure if troll or serious - but it appears to me that this is just a competitor to Siri and Cortana.
I'm starting to think GNU is the problem with "GNU/Linux" these days.
I'm a Raspberry Pi and an open source 'enthusiast'. I'm not a big Amazon fan, they don't really pay taxes here in the UK, for example and somewhat dominate the online retail space. I use http://www.hive.co.uk/ for books, because they also support local bookshops. So, I'm somewhat prejudiced.
That said, why on earth would I build my own Echo, using my own hardware, so that it can probably 'listen' or make use of my data in some way to further the march of Amazon? I don't think so, as they say. There's lots of non-Amazon home automation projects and, if there are none that suit, just buy some relays and ping the GPIO pins with your own programs. As they (we) say, if it's free, then you are the product.
On y va, qui mal y pense!
I think you have your timing off. Around 1995, 16MB was the high end. My dad was working in DTP since 1994 and had to shell out tons of money back then for 8MB RAM to run his Ventura smoothly.
It's not the fall that kills you. It's the sudden stop at the end. -Douglas Adams
Back before your were born, around 1995, 256MB was not only enough to run Windows 95 with PhotoShop smoothly; it would have been considered an excessive amount of memory.
And yet, it is not that time any more, and programming libraries include a great deal of memory-consuming cruft. 256MB is now a piffling little amount of RAM, and quite pathetic really. If you were only ever going to use the Pi embedded, it might be enough... but let's face it, even digital signage PCs regularly come with 2GB now.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
The coding involved is limited to typing in sets of commands
That's not "coding". That's typing a set of commands to run something that someone else "coded".