What are the limitations of our own build Echo using Raspberry Pi?

Mad
  • What are the limitations of our own build Echo using Raspberry Pi? Mad

    I'm trying to build my own Echo device. I found the GitHub repository here and some YouTube tutorials. I would like to know what are the limitation of this.

    Will this allow me similar functions that are available with Echo or Echo Dot available in the market?

    If there are known limitations what are they?

  • I see at least three different aspects that may be limiting the use:

    1. There is a 120 days limitation of the usage of the library due to the prototype nature of it.

    2. it uses 3rd party voice recognitions, which in production needs cash in table to continue the usage.

    3. the whole library is by rules a prototyping library, you have separate instructions in Readme file notes.

  • There aren't many limitations to what the Alexa Voice Service can provide, when compared to the official Echo units.

    One major difference is that Alexa Voice service devices currently do not support Alexa-to-Alexa calling (sending and receiving) as of September 2017. This feature is only available to the official Echo devices (Echo, Echo Dot, Echo Show). This includes the 'Drop In' feature (which is often used as an intercom).

    Messaging also seems to not be supported.

    Some features are region-locked with the AVS. As of writing, the following are not available outside the US (i.e. in the UK and Germany):

    • iHeartRadio
    • Kindle
    • Traffic Reports

    Skills and most other interactions are still available as normal with the Echo. In general, I'd expect that your home-build Echo, while losing some features, will still be pretty functional. If you have a display, you can also go beyond the original Echo's features by integrating Display Cards, which would normally only be available for the Echo Show.

  • Another notable deficiency is that unlike Amazon's official clients, AVS does not (as of early September 2017) support direct local network interaction with smart home devices, but rather only those where the device is in contact with a vendor server which is then in turn in contact with Amazon's servers.

    This means local-only devices like the Belkin WeMo sockets cannot be controlled.

    It may not be particularly clear to a consumer which devices work locally vs. server-mediated, until a 3rd party Alexa client fails to discover or command them - and when that does happen, it may not be clear why this has failed.

Tags
alexa raspberry-pi
Related questions and answers
  • I'm trying to build my own Echo device. I found the GitHub repository here and some YouTube tutorials. I would like to know what are the limitation of this. Will this allow me similar functions that are available with Echo or Echo Dot available in the market? If there are known limitations what are they?

  • into a specific state. So how can I make Alexa to switch between its states using another device? It all comes down to what are the possibilities to interface an Amazon Echo / Dot (and Alexa...I want to have custom wake-word for Alexa so I want to interface this Amazon Echo with an external device. I am wondering if it is possible to create a proxy device that would wake up Alexa if I give... back to Idle the proxy should automatically switch it to Microphone Off state. What I need in general are: The proxy should know Alexa's current state. Won't be the best solution but I may can

  • into a specific state. So how can I make Alexa to switch between its states using another device? It all comes down to what are the possibilities to interface an Amazon Echo / Dot (and Alexa...I want to have custom wake-word for Alexa so I want to interface this Amazon Echo with an external device. I am wondering if it is possible to create a proxy device that would wake up Alexa if I give... back to Idle the proxy should automatically switch it to Microphone Off state. What I need in general are: The proxy should know Alexa's current state. Won't be the best solution but I may can

  • ; Proximity sensors. I only found these from what seems to be a start-up but they are not available and it seems to be proprietary for only their IoT-Gateway and IoT-Platform. Is there anything on the free market that I can buy, so I don't have to build my own sensors using an Arduino? Or alternatively, what are the smallest possible sensors to build with integrated battery & bluetooth? EDIT: Alright. Am I right that those "all-in-one" sensors are just called "beacons" and therefor I didn't find them earlier? EDIT2: And what is the difference between the iBeacon/Eddystone protocols

  • ; Proximity sensors. I only found these from what seems to be a start-up but they are not available and it seems to be proprietary for only their IoT-Gateway and IoT-Platform. Is there anything on the free market that I can buy, so I don't have to build my own sensors using an Arduino? Or alternatively, what are the smallest possible sensors to build with integrated battery & bluetooth? EDIT: Alright. Am I right that those "all-in-one" sensors are just called "beacons" and therefor I didn't find them earlier? EDIT2: And what is the difference between the iBeacon/Eddystone protocols

  • I am trying to configure the newly released Alexa for Business module for my Echo Device. I followed all the steps suggested in the videos released by Alexa. However I keep running into the problem "Sync in progress" for the Echo device settings and end up not getting any kind of sync done. The Echo Dot has latest version updated. Nothing is clearly mentioned in the forums of Amazon for Business to trouble shoot. Anyone has run into this issue? Any suggestions regarding what to do?

  • I am trying to configure the newly released Alexa for Business module for my Echo Device. I followed all the steps suggested in the videos released by Alexa. However I keep running into the problem "Sync in progress" for the Echo device settings and end up not getting any kind of sync done. The Echo Dot has latest version updated. Nothing is clearly mentioned in the forums of Amazon for Business to trouble shoot. Anyone has run into this issue? Any suggestions regarding what to do?

  • Is it possible to build a custom skill that would be equivalent to pressing the microphone on/off button on the top of the Amazon Echo? I know from this article on How-To Geek that such voice command is not available by default: One feature we found missing, and surprisingly so given that the whole appeal of the Echo is voice control, is the inability to turn off the microphone via voice... to set up the connected home features of the Alexa/Echo system. Does this mean this feature is also unavailable via API calls as well? And if it's not possible, why does Amazon not support

  • Is it possible to build a custom skill that would be equivalent to pressing the microphone on/off button on the top of the Amazon Echo? I know from this article on How-To Geek that such voice command is not available by default: One feature we found missing, and surprisingly so given that the whole appeal of the Echo is voice control, is the inability to turn off the microphone via voice... to set up the connected home features of the Alexa/Echo system. Does this mean this feature is also unavailable via API calls as well? And if it's not possible, why does Amazon not support

Data information