RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Platform status
| Platform | Build support | Push-to-talk | Hands Free | Wake-Word-Engine (Supported) | Alert Sounds | LED | General Skill | RDK Specific Skill |
|---|---|---|---|---|---|---|---|---|
| RaspberryPi | Complete | T4H BLE RCU | USB MIC | Kitt.Ai | Available | Traffic Light LED | Integrated | Integrated |
Video accelerator (VIP5202w) | Complete | T4H BLE RCU | N/A | Not required | Available | Onboard | Integrated | Integrated |
Feature List
| Feature | Handler | How to? |
|---|---|---|
| General skills | Alexa | Audio will be played for generic skills such as time, news and weather |
| Youtube | Alexa → Cobalt | Voice command will be routed to thunder |
| App Launch | Alexa → UX | Voice command will be routed to thunder |
| Google search | Alexa → UX | Interactive command handled by Alexa and routed to thunder |
| Player controls | Alexa → App | Play/pause/back commands routed to app |
Build instructions
Alexa related recipes are bundled inside recipes-alexa and contains below build targets
| Recipe | Functionality | Current status |
|---|---|---|
| wpe-openblas | Recipe required in case of Wake-word-engine mode is selected. | Locally hosted |
| wpe-alexa.bb | Main recipe for downloading the AVS SDK and its compilation, linking it with RDK skill mapping module. | Locally hosted |
1. copy recipes-alexa to meta-cmf-raspberrypi or to a similar OEM layer 2. Add above 2 recipes to the appropriate package-group 3. bitbake rdk-generic-wpe-thunder (or the image where alexa is packaged)
Customization
Mapping the developer account
Modify below section and map with relevant developer account.
$ vi Alexa_SDK/Integration/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"
},
LED Support
Prerequisite : Alexa Client uses IOConnector plugin to set different LED notifications, so IOConnector need to be enabled for the platform
https://github.com/rdkcentral/ThunderNanoServices/tree/master/IOConnector
$ vi Alexa_SDK/Integration/AlexaCurl.json Set below GPIO to appropriate value "PinOne":"115", "PinTwo":"122", "PinThree":"115"
Architecture & Flow diagram
Advantages
- Configurable to support different device profiles (FFV, Push-to-talk).
- Most of the new skills can be dynamically added without modifying the client code.
Scope of improvement
| Feature | Status |
|---|---|
| Context specific functionalities | In progress |
| Multi room Music | Open |
| Integration with other Alexa products | Open |
| Smart Screen integration | Open |
Overview
Community Forums
Content Tools
Tasks