Click here to Skip to main content
13,831,901 members
Click here to Skip to main content
Add your own
alternative version

Tagged as


2 bookmarked
Posted 24 Feb 2017
Licenced CPOL

Enable Amazon Alexa Voice Service on the Intel® NUC

, 24 Feb 2017
Rate this:
Please Sign up or sign in to vote.
This tutorial explains steps to port Amazon Alexa Voice Service onto the Intel® NUC with Wind River Linux operating system

Editorial Note

This article is for our sponsors at CodeProject. These articles are intended to provide you with information on products and services that we consider useful and of value to developers

Tutorial Steps

This tutorial explains steps to port Amazon* Alexa Voice Service* onto the Intel® NUC with Wind River Linux* operating system. This tutorial assumes you have already done some basic setup on an Intel® IoT Gateway and are familiar with its operation.

Setup Arduino 101* and Firmata

Clone the GitHub* repository onto your Intel® IoT Gateway by logging into the gateway and running: git clone

Wire up the sensors

Connect Grove* button to pin D8, one LED to pin D3 and other one to Pin D4 as shown in the following picture using the cables from the Grove* starter sensor kit box.

SensorPin Connection
Grove - Red LEDD3
Grove - Blue LEDD4
Grove - ButtonD8
Grove - LCD RGB BacklightI2C

Set Up Firmata* on Arduino 101*

  1. Download Arduino* IDE:
  2. Connect Arduino 101* (branded Genuino 101* outside the U.S.) to a host computer via USB
  3. Launch Arduino IDE
  4. Open boards manager:

  5. Search for "Arduino 101" and install the board definition:

  6. Select "Arduino/Genuino 101" from the Boards menu and the correct port. If you are unsure which port to use disconnect the Arduino 101 and see which port disappears.

  7. Load StandardFirmata Sketch:

  8. Click Upload and wait for "Sketch will execute about 5 seconds"

Setup Intel® IoT Gateway as Echo

  1. SSH onto the Intel® IoT Gateway: ssh root@IP.OF.GATE.WAY

    Where IP.OF.GATE.WAY is the IP address of your gateway

    Use "root" as the password

  2. CD into the Repo:
    cd ~/Alexa-on-Intel-NUC 
  3. Run chmod +x ./


    The script will ask you for confirmation to install a number of packages, enter "y" and hit enter for all.

    The setup script will install the dependencies needed for the project and will take around 5 minutes to finish.

    Reboot the Intel® IoT Gateway

Generate SSL Key for Intel® NUC

  1. Run these commands:
    openssl genrsa -out /root/privkey.pem 2048 
     openssl req -new -x509 -days 365 -key 
    /root/privkey.pem -out /root/cert.pem

    Fill out your information for the SSL certificate.

Create an AWS Account

Follow the instructions at this link to create an Amazon Web Services (AWS)* account and security profile:

Security profile setup for Intel® NUC on Amazon* Developer console

  1. Login to Amazon Developer Portal -
  2. Go to APPS & SERVICES -> Security Profile
  3. Click Web setting tab

  4. Click Edit button on Web settings tab.
  5. Get IP address of your Intel® NUC using "ifconfig" command.
  6. Add the URL in the form https://ip_address_for_NUC:5000/code to Allowed Return URLs
  7. e.g.

Add Your Credentials to

  1. Navigate to the General tab on the Security Profile Management page:

  2. Open using vi with: vi
  3. Hit "a" to enter insert mode
  4. Enter your information into ProductID, Client_ID, etc.
  5. Hit "esc", type ":wq", and hit enter to save the file

Create an AWS IoT Device

In order for the gateway to communicate with the AWS* cloud we will create an AWS IoT Device to act as a bridge. Alexa* Voice Services will then push updates to the device shadow (a virtual persistent state) and the gateway will get updates from the device shadow.

  1. Create an AWS account:
  2. From Services select AWS IoT:

    Make sure that your region is selected as N. Virginia (us-east-1). The AWS services are not yet online for all regions.

    The dashboard should look like this:

  3. Go to: Registry -> Things and click "Create" to the right of the search bar. Follow the screens to create AWS IoT device.

  4. On the device page navigate to Interact and click on "Connect a Device"

  5. Choose your platform – Linux*/OSX* or Windows*, and choose Python*.

  6. Click "Getting Started" and download the connection kit for your selected OS. This package will contain a private key and certificate which we will use to connect the gateway to the AWS IoT service. It also contains a script which will run a basic connection test, install the SDK, and download the rootCA.crt.
  7. Transfer the zip file to the gateway using FTP from the command line, or FileZilla:
    1. Go to to download and install the FileZilla client
    2. Open Filezilla and connect to the IP of your gateway using "root" as username, "root" as password, and 22 as the port:

    3. When asked about unknown host key hit OK
    4. Navigate to the zip file on the left panel and the Alexa-on-Intel-NUC repository folder on the right panel. Double click the zip file to transfer it.

    Edit contains code for both sending voice commands to Alexa* and connecting to AWS IoT. Now that you have created a device you can add its connection details to

    1. Using VI open and replace AWS_IOT_ARN with the Thing arn from the Details section of the AWS IoT device console:

    2. Replace REST_API_ENDPOINT with the Rest API Endpoint under the HTTPS section of the Interact section of the AWS IoT Console:

    Create a Lambda Function

    The lambda function is a function that runs in a virtual run time environment in AWS. We will use it to do two things: set up a handler for requests coming from Alexa* Voice Services, and setup a connection to AWS IoT to update the gateway device shadow.

    The Github* repository contains /lambda/index.js which you will have to edit in order to connect to your AWS IoT Device.

    1. On line 4 of index.js replace REST_API_ENDPOINT with the endpoint of your IoT Device. The endpoint can be found in the AWS IoT device console under Interact

    2. Once you have edited index.js make a zip file containing index.js and /lambda/node_modules. You will upload this to Lambda later on.
    3. Navigate to the AWS Lambda service:
    4. Click ‘Create Function’ use the Blank Function blueprint:

    5. Select "Alexa Skills Kit" as the trigger:

    6. Give your function a name and description and choose "Upload a .ZIP file"

    7. Click Upload and select the zip file you made earlier.
    8. Enter index.handler for the Handler – this is the default handler for Lambda
    9. Choose "Create new role form template"
    10. Select "Simple Microservice Permissions" from "Policy Templates"

    11. Leave everything else as default and click next.
    12. Review the function on the next page and click "Create Function"

    Configure IAM access policy

    1. Navigate to AWS IAM console:
    2. Navigate to the Roles list form the left side menu:

    3. Select the role policy you created for your Lambda function
    4. Select "Attach Policy"

    5. Select "AWSIoTFullAccess" and click Attach Policy:

    Configure Custom Alexa Skill

    Finally, we will create a custom Alexa skill that will pass events to the handler running in the Lambda function.

    1. Navigate to the Alexa developer portal: and select "Get Started" under Alexa Skills Kit

    2. Select "Add a New Skill". On the following screen add a name for your skill and an invocation name. The invocation name is how you will call the skill from Alexa e.g "Alexa tell gateway to turn on blue LED" where "gateway" is the invocation name.

    3. Click "Next"
    4. On the next screen, we will configure the Intent Schema, add custom Slots, and set the utterance. The Intent Schema describes the events that are sent to Lambda and the slots associated with each. Slots can be thought of as variables for the device state, e.g. "blue led off" is a slot that describes the intended state of our gateway. The utterance is what people say to interact with your skill.
    5. In Custom_Skill/Intent_Schema you will find the intent schema that we will use for this project. This schema describes an intent called "DeviceStateIntent" with Slots called "DeviceState" of Type "Device_States". Note that DeviceStateIntent is the event name used in the handler lambda function for switching the state of the gateway – if you rename the event name in the handler function you must also rename it in the intent schema. There are also some default helper intents in the schema that send events to the handler function when the user says things like "help".

    6. Device States is not a standard slot type so we will have to define them. Select Add Slot Type, enter Device States as the type and add the values separated by line, i.e. hit enter between each value. These values are the different cases passes to the DeviceStateIntent handler function. On line 56 of the lambda function you can see case "all on": which defines what the function does when "all on" is passed by the DeviceStateIntent event. We will use "all on", "all off", "blue led on", "blue led off", "red led on", "red led off". You may add your own, but you must define what slot does in the lambda handler function.
    7. Finally add a Sample Utterance. The first term in the sample utterance defines which intent to tie the utterance to, i.e. the user does not say "DeviceStateIntent turn on blue led", only "turn blue led on" and then "blue led on" is passed as the slot for DeviceStateIntent. Any terms in curly braces are slot names defined in the intent schma. Use the simplest form for now "Device StateIntent turn {DeviceState}" Note: Alexa is clever enough to substitute "turn" with "switch" and other contextual terms, no need to explicitly define it.
    8. Much more info on intent schema setup can be found here: Sample Utterances File
    9. Click next to continue to the configuration.

    10. Here select AWS Lambda ARN (Amazon Resource Name) as the endpoint type, and enter the ARN found in your Lambda Function Dashboard in the upper right:

    11. Click next to go to test your new skill:

    12. Enter an utterance like "turn blue led on" and click Ask. IF everything is working correctly you should see the lambda request and response with "Turn Blue LED on" as the output speech.

    Run the program

    1. You are now ready to run the program. Launch "Python" from the root folder of the repository.
    2. Wait 15 seconds for everything to initialize.
    3. Click the button, say "Tell gateway to turn blue led on"
    4. The Blue LED should turn on and Alexa will respond with "Blue LED on"


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Intel Corporation
United States United States
You may know us for our processors. But we do so much more. Intel invents at the boundaries of technology to make amazing experiences possible for business and society, and for every person on Earth.

Harnessing the capability of the cloud, the ubiquity of the Internet of Things, the latest advances in memory and programmable solutions, and the promise of always-on 5G connectivity, Intel is disrupting industries and solving global challenges. Leading on policy, diversity, inclusion, education and sustainability, we create value for our stockholders, customers and society.
Group type: Organisation

43 members

You may also be interested in...


Comments and Discussions

GeneralProbably some great stuff here... Pin
James Hunter Ross28-Feb-17 15:01
memberJames Hunter Ross28-Feb-17 15:01 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Cookies | Terms of Use | Mobile
Web03 | 2.8.190114.1 | Last Updated 24 Feb 2017
Article Copyright 2017 by Intel Corporation
Everything else Copyright © CodeProject, 1999-2019
Layout: fixed | fluid