Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Network Open Source Software The Internet Wireless Networking Build Hardware News Science Technology

Amazon's Raspberry Pi Guide Lets Coders Build An Echo (bbc.com) 47

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.
This discussion has been archived. No new comments can be posted.

Amazon's Raspberry Pi Guide Lets Coders Build An Echo

Comments Filter:
  • by hughbar ( 579555 ) on Saturday March 26, 2016 @05:01AM (#51781311) Homepage
    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/ [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.
  • by tomhath ( 637240 ) on Saturday March 26, 2016 @06:29AM (#51781413)

    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".

The explanation requiring the fewest assumptions is the most likely to be correct. -- William of Occam

Working...