...

Release History

...

1. Initialize and download the code base
 - Example for RaspberryPi:
 (we can use rdkv.xml to build with external source method or rdkv-nosrc.xml to build without externalsrc)
 $ repo init -u https://code.rdkcentral.com/r/manifests -m rdkv-nosrc.xml -b thunderrdk-next
 $ repo sync

2. Download the meta-rdk-voice layer in project root
 $ git clone https://code.rdkcentral.com/r/rdk/components/generic/rdk-oe/meta-rdk-voice

3. Enable the below DISTRO feature to build AVS plugin
 $ vi meta-rdk-voice/conf/layer.conf
 - enable the below commented line
 #DISTRO_FEATURES_append = " alexa-plugin"

4. Optionally For the external source builds (such as some Broadcom platforms) add below line in manifest/auto.conf
 - In <Manifest>.xml
   <project name="components/generic/avs/alexa_skill_mapper" revision="rdk-next"/>
 - In auto.conf (where brcmexternalsrc is enabled)
   BRCMEXTERNALSRC_pn-wpe-alexaskillmapper += "rdk/components/generic/avs/alexa_skill_mapper"
   SRCPV_pn-wpe-alexaskillmapper = "${BRCMEXTERNAL-SRCPV-CMF}"
 $ repo sync

...

Mic input can be enable using below options , it will automatically add PORTAUDIO library as dependency.

KWD detector module will be required for MIC attached devices in order to wake-up Alexa & current implementation is only verified with pryonlite KWD detector.

4. if wanted to use MIC based implementation (Ignore if using BLE voice remote)
 $ vi meta-rdk-voice/conf/layer.conf
 - enable the below commented line
 #DISTRO_FEATURES_append = " alexa_ffv"

...

Keyword detector (KWD) support enables the device to wake-up & listen to input after receiving the hot word  "Alexa". It is used with devices that has on-board Microphone-board Microphone

This option need to be enabled along with "alexa_ffv" DISTRO for MIC based voice input

1. To use pryon lite KWD engine for devices with MIC input
 Note: Source code need to be obtained from amazon separately
2. Set the KWD support flag to "ON"
  $ vi meta-rdk-voice/recipes-wpe/wpeframework/include/avs.inc
    AVS_KWD_SUPPORT ?= "ON"
3. include the KWD detector recipe to build.
 - enable the commented line 
 #PREFERRED_PROVIDER_virtual/alexa-kwd-detector = "pryonlite"
4. Create a bbappend file in platform layer and provide artifact location
e.g. 
 $ vi meta-rdk-oem-<OEMNAME>/meta-<MACHINE>/recipes-avs/pryonlite/pryonlite_2.3.0.bbappend
   SRC_URI  = "file://pryon_lite_2.3.0-metrological-2019.12.23.2344.zip"

...

1.  Go to the controller web UI by typing http://<Device-IP> in a browser
2. Select the controller option from left pane menu
3. toggle the AVS option to activate the plugin

For systemd service (old implementation)

1. Login to the device with "ssh root@<Device-IP>
2. start the alexa service by invoking "systemctl start alexa.service"

Customization

Mapping to amazon developer account

...

1. Login to the device
 $ ssh root@<RDKV-Client-IP>

2. Edit the Configuration file
 $ cd /usr/share/WPEFramework/AVS
 $ vi AlexaClientSDKConfig.json
     "deviceInfo":{
        // Unique device serial number. e.g. 123456
        "deviceSerialNumber":"<SERIAL_NO>",
        // The Client ID of the Product from developer.amazon.com
        "clientId":"<CLIENT_ID>",
        // Product ID from developer.amazon.com
        "productId":"<PRODUCT_ID>",
        // The name of the device manufacturer.
        "manufacturerName": "<MANUFACTURER_NAME>",
        // The description of the device which should contain the manufacturer name or how the device is connected.
        "description": "<DESCRIPTION<DESCRIPTION>"
    },

Front

...

Panel LED Notifications

...

We can check the authorization code using below command:

...

:

$ systemctl status alexa

• In case of plugin implementation

$ tail -f /opt/logs/wpeframework.log

...

The Alexa Smart Screen SDK extends the AVS Device SDK to support visual display for screen-based Alexa Built-in products that . It complement Alexa voice responses with rich visual experiences.

...

Below are few screen shots which gives an idea about the smart screen integration for different scenarios:.

a) Weather Information:

• Smart screen overlay shown over the main UI
• Weather information displayed as a visual element inside overlay
• Voice chrome bar visible at bottom of the overlay indicating Alexa is in SPEAKING state.

b) Music Playback

• Smart screen overlay shown over the main UI
• Audio player interface occupying the full space of overlay window.

Example Usage

a) General Usage
ex:  1) User: what is the the time?
          Alexa: respond with current time
      2) User : what is the weather outside ?
          Alexa: it will ask for you location
          User: Provides the Location
          Alexa: respond with the climate in the current location.

...

AVS Integration with custom skills

Current Limitations

Roadmap