2017-05-18 05:02:48 +00:00
|
|
|
{
|
Version 1.7.0 of the avs-device-sdk
Changes in this update:
**Enhancements**
* `AuthDelegate` and `AuthServer.py` have been replaced by `CBLAUthDelegate`, which provides a more straightforward path to authorization.
* Added a new configuration property called [`cblAuthDelegate`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L2). This object specifies parameters for `CBLAuthDelegate`.
* Added a new configuration property called [`miscDatabase`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L34), which is a generic key/value database to be used by various components.
* Added a new configuration property called [`dcfDelegate`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L17) This object specifies parameters for `DCFDelegate`. Within this object, values were added for the 'endpoint' and `overridenDcfPublishMessageBody`. 'endpoint' is the endpoint to connect to in order to send device capabilities. `overridenDcfPublishMessageBody`is the message that will get sent out to the Capabilities API. Note: values within the `dcfDelegate` object will only work in `DEBUG` builds.
* Added a new configuration property called [`deviceInfo`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L9) which specifies device-identifying information for use by the Device Capability Framework (DCF), and for authorization (CBLAuthDelegate).
* Updated the Directive Sequencer to support wildcard directive handlers. This allows a handler for a given AVS interface to register at the namespace level, rather than specifying the names of all directives within that namespace.
* Updated the Raspberry Pi installation script to include `alsasink` in the configuration file.
* Added `audioSink` as a configuration option. This allows users to override the audio sink element used in `Gstreamer`.
* Added an interface for monitoring internet connection status: `InternetConnectionMonitorInterface.h`.
* The Alexa Communications Library (ACL) is no longer required to wait until authorization has succeeded before attempting to connect to AVS. Instead, `HTTP2Transport` handles waiting for authorization to complete.
* Added the Device Capabilities Framework (DCF) delegate. Device capabilities can now be sent for each capability interface using DCF publish messages.
* The sample app has been updated to send DCF publish messages, which will automatically occur when the sample app starts. Note: a DCF publish message must be successfully sent in order for communication with AVS to occur.
* The SDK now supports HTTP PUT messages.
* Added support for opt-arg style arguments and multiple configuration files. Now, the sample app can be invoked by either of these commands: `SampleApp <configfile> <debuglevel>` OR `SampleApp -C file1 -C file2 ... -L loglevel`.
**Bug Fixes**
* Issues [447](https://github.com/alexa/avs-device-sdk/issues/447) and [553](https://github.com/alexa/avs-device-sdk/issues/553) Fixed the `AttachmentRenderSource`'s handling of `BLOCKING` `AttachmentReaders`.
* Updated the `Logger` implementation to be more resilient to `nullptr` string inputs.
* Fixed a `TimeUtils` utility-related compile issue.
* Fixed a bug in which alerts failed to activate if the system was restarted without network connection.
* Fixed Android 64-bit build failure issue.
**Known Issues**
* The `ACL` may encounter issues if audio attachments are received but not consumed.
* `SpeechSynthesizerState` currently uses `GAINING_FOCUS` and `LOSING_FOCUS` as a workaround for handling intermediate state. These states may be removed in a future release.
* Some ERROR messages may be printed during start-up event if initialization proceeds normally and successfully.
* If an unrecoverable authorization error or an unrecoverable DCF error is encountered, the sample app may crash on shutdown.
* If a non-CBL `clientId` is included in the `deviceInfo` section of `AlexaClientSDKConfig.json`, the error will be reported as an unrecoverable authorization error, rather than a more specific error.
2018-04-18 22:17:28 +00:00
|
|
|
"cblAuthDelegate":{
|
|
|
|
// Path to CBLAuthDelegate's database file. e.g. /home/ubuntu/Build/cblAuthDelegate.db
|
|
|
|
// Note: The directory specified must be valid.
|
|
|
|
// The database file (cblAuthDelegate.db) will be created by SampleApp, do not create it yourself.
|
|
|
|
// The database file should only be used for CBLAuthDelegate (don't use it for other components of SDK)
|
|
|
|
"databaseFilePath":"${SDK_CBL_AUTH_DELEGATE_DATABASE_FILE_PATH}"
|
|
|
|
},
|
|
|
|
"deviceInfo":{
|
2017-11-17 02:49:28 +00:00
|
|
|
// Unique device serial number. e.g. 123456
|
2017-05-18 05:02:48 +00:00
|
|
|
"deviceSerialNumber":"${SDK_CONFIG_DEVICE_SERIAL_NUMBER}",
|
2017-11-17 02:49:28 +00:00
|
|
|
// The Client ID of the Product from developer.amazon.com
|
2017-05-18 05:02:48 +00:00
|
|
|
"clientId":"${SDK_CONFIG_CLIENT_ID}",
|
2017-11-17 02:49:28 +00:00
|
|
|
// Product ID from developer.amazon.com
|
2017-10-02 22:59:05 +00:00
|
|
|
"productId":"${SDK_CONFIG_PRODUCT_ID}"
|
2018-02-12 23:31:53 +00:00
|
|
|
},
|
Version 1.7.0 of the avs-device-sdk
Changes in this update:
**Enhancements**
* `AuthDelegate` and `AuthServer.py` have been replaced by `CBLAUthDelegate`, which provides a more straightforward path to authorization.
* Added a new configuration property called [`cblAuthDelegate`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L2). This object specifies parameters for `CBLAuthDelegate`.
* Added a new configuration property called [`miscDatabase`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L34), which is a generic key/value database to be used by various components.
* Added a new configuration property called [`dcfDelegate`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L17) This object specifies parameters for `DCFDelegate`. Within this object, values were added for the 'endpoint' and `overridenDcfPublishMessageBody`. 'endpoint' is the endpoint to connect to in order to send device capabilities. `overridenDcfPublishMessageBody`is the message that will get sent out to the Capabilities API. Note: values within the `dcfDelegate` object will only work in `DEBUG` builds.
* Added a new configuration property called [`deviceInfo`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L9) which specifies device-identifying information for use by the Device Capability Framework (DCF), and for authorization (CBLAuthDelegate).
* Updated the Directive Sequencer to support wildcard directive handlers. This allows a handler for a given AVS interface to register at the namespace level, rather than specifying the names of all directives within that namespace.
* Updated the Raspberry Pi installation script to include `alsasink` in the configuration file.
* Added `audioSink` as a configuration option. This allows users to override the audio sink element used in `Gstreamer`.
* Added an interface for monitoring internet connection status: `InternetConnectionMonitorInterface.h`.
* The Alexa Communications Library (ACL) is no longer required to wait until authorization has succeeded before attempting to connect to AVS. Instead, `HTTP2Transport` handles waiting for authorization to complete.
* Added the Device Capabilities Framework (DCF) delegate. Device capabilities can now be sent for each capability interface using DCF publish messages.
* The sample app has been updated to send DCF publish messages, which will automatically occur when the sample app starts. Note: a DCF publish message must be successfully sent in order for communication with AVS to occur.
* The SDK now supports HTTP PUT messages.
* Added support for opt-arg style arguments and multiple configuration files. Now, the sample app can be invoked by either of these commands: `SampleApp <configfile> <debuglevel>` OR `SampleApp -C file1 -C file2 ... -L loglevel`.
**Bug Fixes**
* Issues [447](https://github.com/alexa/avs-device-sdk/issues/447) and [553](https://github.com/alexa/avs-device-sdk/issues/553) Fixed the `AttachmentRenderSource`'s handling of `BLOCKING` `AttachmentReaders`.
* Updated the `Logger` implementation to be more resilient to `nullptr` string inputs.
* Fixed a `TimeUtils` utility-related compile issue.
* Fixed a bug in which alerts failed to activate if the system was restarted without network connection.
* Fixed Android 64-bit build failure issue.
**Known Issues**
* The `ACL` may encounter issues if audio attachments are received but not consumed.
* `SpeechSynthesizerState` currently uses `GAINING_FOCUS` and `LOSING_FOCUS` as a workaround for handling intermediate state. These states may be removed in a future release.
* Some ERROR messages may be printed during start-up event if initialization proceeds normally and successfully.
* If an unrecoverable authorization error or an unrecoverable DCF error is encountered, the sample app may crash on shutdown.
* If a non-CBL `clientId` is included in the `deviceInfo` section of `AlexaClientSDKConfig.json`, the error will be reported as an unrecoverable authorization error, rather than a more specific error.
2018-04-18 22:17:28 +00:00
|
|
|
"dcfDelegate":{
|
|
|
|
// The endpoint to connect in order to send device capabilities.
|
|
|
|
// This will only be used in DEBUG builds.
|
|
|
|
// e.g. "endpoint": "https://api.amazonalexa.com"
|
|
|
|
// Override DCF Publish message to be sent out.
|
|
|
|
// This will only be used in DEBUG builds.
|
|
|
|
// e.g. "overridenDcfPublishMessageBody": {
|
|
|
|
// "envelopeVersion":"20160207",
|
|
|
|
// "capabilities":[
|
|
|
|
// {
|
|
|
|
// "type":"AlexaInterface",
|
|
|
|
// "interface":"Alerts",
|
|
|
|
// "version":"1.1"
|
|
|
|
// }
|
|
|
|
// ]
|
|
|
|
// }
|
|
|
|
},
|
|
|
|
"miscDatabase":{
|
|
|
|
// Path to misc database file. e.g. /home/ubuntu/Build/miscDatabase.db
|
|
|
|
// Note: The directory specified must be valid.
|
|
|
|
// The database file (miscDatabase.db) will be created by SampleApp, do not create it yourself.
|
|
|
|
"databaseFilePath":"${SDK_MISC_DATABASE_FILE_PATH}"
|
|
|
|
},
|
2018-02-12 23:31:53 +00:00
|
|
|
"alertsCapabilityAgent":{
|
2017-11-17 02:49:28 +00:00
|
|
|
// Path to Alerts database file. e.g. /home/ubuntu/Build/alerts.db
|
|
|
|
// Note: The directory specified must be valid.
|
|
|
|
// The database file (alerts.db) will be created by SampleApp, do not create it yourself.
|
|
|
|
// The database file should only be used for alerts (don't use it for other components of SDK)
|
2017-12-09 00:07:37 +00:00
|
|
|
"databaseFilePath":"${SDK_SQLITE_DATABASE_FILE_PATH}"
|
2018-02-12 23:31:53 +00:00
|
|
|
},
|
|
|
|
"settings":{
|
2017-11-17 02:49:28 +00:00
|
|
|
// Path to Settings database file. e.g. /home/ubuntu/Build/settings.db
|
|
|
|
// Note: The directory specified must be valid.
|
|
|
|
// The database file (settings.db) will be created by SampleApp, do not create it yourself.
|
|
|
|
// The database file should only be used for settings (don't use it for other components of SDK)
|
2017-10-02 22:59:05 +00:00
|
|
|
"databaseFilePath":"${SDK_SQLITE_SETTINGS_DATABASE_FILE_PATH}",
|
|
|
|
"defaultAVSClientSettings":{
|
2017-11-17 02:49:28 +00:00
|
|
|
// Default language for Alexa.
|
|
|
|
// See https://developer.amazon.com/docs/alexa-voice-service/settings.html#settingsupdated for valid values.
|
2017-10-02 22:59:05 +00:00
|
|
|
"locale":"${SETTING_LOCALE_VALUE}"
|
2018-02-12 23:31:53 +00:00
|
|
|
}
|
2017-10-02 22:59:05 +00:00
|
|
|
},
|
2018-02-12 23:31:53 +00:00
|
|
|
"certifiedSender":{
|
2017-11-17 02:49:28 +00:00
|
|
|
// Path to Certified Sender database file. e.g. /home/ubuntu/Build/certifiedsender.db
|
|
|
|
// Note: The directory specified must be valid.
|
|
|
|
// The database file (certifiedsender.db) will be created by SampleApp, do not create it yourself.
|
|
|
|
// The database file should only be used for certifiedSender (don't use it for other components of SDK)
|
|
|
|
"databaseFilePath":"${SDK_CERTIFIED_SENDER_DATABASE_FILE_PATH}"
|
2017-12-09 00:07:37 +00:00
|
|
|
},
|
2018-01-12 23:45:42 +00:00
|
|
|
"notifications":{
|
|
|
|
// Path to Notifications database file. e.g. /home/ubuntu/Build/notifications.db
|
|
|
|
// Note: The directory specified must be valid.
|
|
|
|
// The database file (notifications.db) will be created by SampleApp, do not create it yourself.
|
|
|
|
// The database file should only be used for notifications (don't use it for other components of SDK)
|
|
|
|
"databaseFilePath":"${SDK_NOTIFICATIONS_DATABASE_FILE_PATH}"
|
|
|
|
},
|
2017-12-09 00:07:37 +00:00
|
|
|
"sampleApp":{
|
|
|
|
// To specify if the SampleApp supports display cards.
|
|
|
|
"displayCardsSupported":true
|
2018-02-12 23:31:53 +00:00
|
|
|
// The firmware version of the device to send in SoftwareInfo event.
|
|
|
|
// Note: The firmware version should be a positive 32-bit integer in the range [1-2147483647].
|
|
|
|
// e.g. "firmwareVersion": 123
|
|
|
|
// The default endpoint to connect to.
|
|
|
|
// See https://developer.amazon.com/docs/alexa-voice-service/api-overview.html#endpoints for regions and values
|
|
|
|
// e.g. "endpoint": "https://avs-alexa-na.amazon.com"
|
2018-03-09 00:55:39 +00:00
|
|
|
|
|
|
|
// Example of specifying suggested latency in seconds when openning PortAudio stream. By default,
|
|
|
|
// when this paramater isn't specified, SampleApp calls Pa_OpenDefaultStream to use the default value.
|
|
|
|
// See http://portaudio.com/docs/v19-doxydocs/structPaStreamParameters.html for further explanation
|
|
|
|
// on this parameter.
|
|
|
|
//"portAudio":{
|
|
|
|
// "suggestedLatency": 0.150
|
|
|
|
//}
|
2017-10-02 22:59:05 +00:00
|
|
|
}
|
2018-03-09 00:55:39 +00:00
|
|
|
|
Version 1.7.0 of the avs-device-sdk
Changes in this update:
**Enhancements**
* `AuthDelegate` and `AuthServer.py` have been replaced by `CBLAUthDelegate`, which provides a more straightforward path to authorization.
* Added a new configuration property called [`cblAuthDelegate`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L2). This object specifies parameters for `CBLAuthDelegate`.
* Added a new configuration property called [`miscDatabase`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L34), which is a generic key/value database to be used by various components.
* Added a new configuration property called [`dcfDelegate`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L17) This object specifies parameters for `DCFDelegate`. Within this object, values were added for the 'endpoint' and `overridenDcfPublishMessageBody`. 'endpoint' is the endpoint to connect to in order to send device capabilities. `overridenDcfPublishMessageBody`is the message that will get sent out to the Capabilities API. Note: values within the `dcfDelegate` object will only work in `DEBUG` builds.
* Added a new configuration property called [`deviceInfo`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L9) which specifies device-identifying information for use by the Device Capability Framework (DCF), and for authorization (CBLAuthDelegate).
* Updated the Directive Sequencer to support wildcard directive handlers. This allows a handler for a given AVS interface to register at the namespace level, rather than specifying the names of all directives within that namespace.
* Updated the Raspberry Pi installation script to include `alsasink` in the configuration file.
* Added `audioSink` as a configuration option. This allows users to override the audio sink element used in `Gstreamer`.
* Added an interface for monitoring internet connection status: `InternetConnectionMonitorInterface.h`.
* The Alexa Communications Library (ACL) is no longer required to wait until authorization has succeeded before attempting to connect to AVS. Instead, `HTTP2Transport` handles waiting for authorization to complete.
* Added the Device Capabilities Framework (DCF) delegate. Device capabilities can now be sent for each capability interface using DCF publish messages.
* The sample app has been updated to send DCF publish messages, which will automatically occur when the sample app starts. Note: a DCF publish message must be successfully sent in order for communication with AVS to occur.
* The SDK now supports HTTP PUT messages.
* Added support for opt-arg style arguments and multiple configuration files. Now, the sample app can be invoked by either of these commands: `SampleApp <configfile> <debuglevel>` OR `SampleApp -C file1 -C file2 ... -L loglevel`.
**Bug Fixes**
* Issues [447](https://github.com/alexa/avs-device-sdk/issues/447) and [553](https://github.com/alexa/avs-device-sdk/issues/553) Fixed the `AttachmentRenderSource`'s handling of `BLOCKING` `AttachmentReaders`.
* Updated the `Logger` implementation to be more resilient to `nullptr` string inputs.
* Fixed a `TimeUtils` utility-related compile issue.
* Fixed a bug in which alerts failed to activate if the system was restarted without network connection.
* Fixed Android 64-bit build failure issue.
**Known Issues**
* The `ACL` may encounter issues if audio attachments are received but not consumed.
* `SpeechSynthesizerState` currently uses `GAINING_FOCUS` and `LOSING_FOCUS` as a workaround for handling intermediate state. These states may be removed in a future release.
* Some ERROR messages may be printed during start-up event if initialization proceeds normally and successfully.
* If an unrecoverable authorization error or an unrecoverable DCF error is encountered, the sample app may crash on shutdown.
* If a non-CBL `clientId` is included in the `deviceInfo` section of `AlexaClientSDKConfig.json`, the error will be reported as an unrecoverable authorization error, rather than a more specific error.
2018-04-18 22:17:28 +00:00
|
|
|
// Example of specifying output format and the audioSink for the gstreamer-based MediaPlayer bundled with the SDK.
|
|
|
|
// Many platforms will automatically set the output format correctly, but in some cases where the hardware requires
|
|
|
|
// a specific format and the software stack is not automatically setting it correctly, these parameters can be used
|
|
|
|
// to manually specify the output format. Supported rate/format/channels values are documented in detail here:
|
2018-03-09 00:55:39 +00:00
|
|
|
// https://gstreamer.freedesktop.org/documentation/design/mediatype-audio-raw.html
|
|
|
|
//
|
Version 1.7.0 of the avs-device-sdk
Changes in this update:
**Enhancements**
* `AuthDelegate` and `AuthServer.py` have been replaced by `CBLAUthDelegate`, which provides a more straightforward path to authorization.
* Added a new configuration property called [`cblAuthDelegate`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L2). This object specifies parameters for `CBLAuthDelegate`.
* Added a new configuration property called [`miscDatabase`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L34), which is a generic key/value database to be used by various components.
* Added a new configuration property called [`dcfDelegate`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L17) This object specifies parameters for `DCFDelegate`. Within this object, values were added for the 'endpoint' and `overridenDcfPublishMessageBody`. 'endpoint' is the endpoint to connect to in order to send device capabilities. `overridenDcfPublishMessageBody`is the message that will get sent out to the Capabilities API. Note: values within the `dcfDelegate` object will only work in `DEBUG` builds.
* Added a new configuration property called [`deviceInfo`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L9) which specifies device-identifying information for use by the Device Capability Framework (DCF), and for authorization (CBLAuthDelegate).
* Updated the Directive Sequencer to support wildcard directive handlers. This allows a handler for a given AVS interface to register at the namespace level, rather than specifying the names of all directives within that namespace.
* Updated the Raspberry Pi installation script to include `alsasink` in the configuration file.
* Added `audioSink` as a configuration option. This allows users to override the audio sink element used in `Gstreamer`.
* Added an interface for monitoring internet connection status: `InternetConnectionMonitorInterface.h`.
* The Alexa Communications Library (ACL) is no longer required to wait until authorization has succeeded before attempting to connect to AVS. Instead, `HTTP2Transport` handles waiting for authorization to complete.
* Added the Device Capabilities Framework (DCF) delegate. Device capabilities can now be sent for each capability interface using DCF publish messages.
* The sample app has been updated to send DCF publish messages, which will automatically occur when the sample app starts. Note: a DCF publish message must be successfully sent in order for communication with AVS to occur.
* The SDK now supports HTTP PUT messages.
* Added support for opt-arg style arguments and multiple configuration files. Now, the sample app can be invoked by either of these commands: `SampleApp <configfile> <debuglevel>` OR `SampleApp -C file1 -C file2 ... -L loglevel`.
**Bug Fixes**
* Issues [447](https://github.com/alexa/avs-device-sdk/issues/447) and [553](https://github.com/alexa/avs-device-sdk/issues/553) Fixed the `AttachmentRenderSource`'s handling of `BLOCKING` `AttachmentReaders`.
* Updated the `Logger` implementation to be more resilient to `nullptr` string inputs.
* Fixed a `TimeUtils` utility-related compile issue.
* Fixed a bug in which alerts failed to activate if the system was restarted without network connection.
* Fixed Android 64-bit build failure issue.
**Known Issues**
* The `ACL` may encounter issues if audio attachments are received but not consumed.
* `SpeechSynthesizerState` currently uses `GAINING_FOCUS` and `LOSING_FOCUS` as a workaround for handling intermediate state. These states may be removed in a future release.
* Some ERROR messages may be printed during start-up event if initialization proceeds normally and successfully.
* If an unrecoverable authorization error or an unrecoverable DCF error is encountered, the sample app may crash on shutdown.
* If a non-CBL `clientId` is included in the `deviceInfo` section of `AlexaClientSDKConfig.json`, the error will be reported as an unrecoverable authorization error, rather than a more specific error.
2018-04-18 22:17:28 +00:00
|
|
|
// By default the "autoaudiosink" element is used in the pipeline. This element automatically selects the best sink
|
|
|
|
// to use based on the configuration in the system. But sometimes the wrong sink is selected and that prevented sound
|
|
|
|
// from being played. A new configuration is added where the audio sink can be specified for their system.
|
2018-03-09 00:55:39 +00:00
|
|
|
// "gstreamerMediaPlayer":{
|
|
|
|
// "outputConversion":{
|
|
|
|
// "rate":16000,
|
|
|
|
// "format":"S16LE",
|
|
|
|
// "channels":1
|
Version 1.7.0 of the avs-device-sdk
Changes in this update:
**Enhancements**
* `AuthDelegate` and `AuthServer.py` have been replaced by `CBLAUthDelegate`, which provides a more straightforward path to authorization.
* Added a new configuration property called [`cblAuthDelegate`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L2). This object specifies parameters for `CBLAuthDelegate`.
* Added a new configuration property called [`miscDatabase`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L34), which is a generic key/value database to be used by various components.
* Added a new configuration property called [`dcfDelegate`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L17) This object specifies parameters for `DCFDelegate`. Within this object, values were added for the 'endpoint' and `overridenDcfPublishMessageBody`. 'endpoint' is the endpoint to connect to in order to send device capabilities. `overridenDcfPublishMessageBody`is the message that will get sent out to the Capabilities API. Note: values within the `dcfDelegate` object will only work in `DEBUG` builds.
* Added a new configuration property called [`deviceInfo`](https://github.com/alexa/avs-device-sdk/blob/master/Integration/AlexaClientSDKConfig.json#L9) which specifies device-identifying information for use by the Device Capability Framework (DCF), and for authorization (CBLAuthDelegate).
* Updated the Directive Sequencer to support wildcard directive handlers. This allows a handler for a given AVS interface to register at the namespace level, rather than specifying the names of all directives within that namespace.
* Updated the Raspberry Pi installation script to include `alsasink` in the configuration file.
* Added `audioSink` as a configuration option. This allows users to override the audio sink element used in `Gstreamer`.
* Added an interface for monitoring internet connection status: `InternetConnectionMonitorInterface.h`.
* The Alexa Communications Library (ACL) is no longer required to wait until authorization has succeeded before attempting to connect to AVS. Instead, `HTTP2Transport` handles waiting for authorization to complete.
* Added the Device Capabilities Framework (DCF) delegate. Device capabilities can now be sent for each capability interface using DCF publish messages.
* The sample app has been updated to send DCF publish messages, which will automatically occur when the sample app starts. Note: a DCF publish message must be successfully sent in order for communication with AVS to occur.
* The SDK now supports HTTP PUT messages.
* Added support for opt-arg style arguments and multiple configuration files. Now, the sample app can be invoked by either of these commands: `SampleApp <configfile> <debuglevel>` OR `SampleApp -C file1 -C file2 ... -L loglevel`.
**Bug Fixes**
* Issues [447](https://github.com/alexa/avs-device-sdk/issues/447) and [553](https://github.com/alexa/avs-device-sdk/issues/553) Fixed the `AttachmentRenderSource`'s handling of `BLOCKING` `AttachmentReaders`.
* Updated the `Logger` implementation to be more resilient to `nullptr` string inputs.
* Fixed a `TimeUtils` utility-related compile issue.
* Fixed a bug in which alerts failed to activate if the system was restarted without network connection.
* Fixed Android 64-bit build failure issue.
**Known Issues**
* The `ACL` may encounter issues if audio attachments are received but not consumed.
* `SpeechSynthesizerState` currently uses `GAINING_FOCUS` and `LOSING_FOCUS` as a workaround for handling intermediate state. These states may be removed in a future release.
* Some ERROR messages may be printed during start-up event if initialization proceeds normally and successfully.
* If an unrecoverable authorization error or an unrecoverable DCF error is encountered, the sample app may crash on shutdown.
* If a non-CBL `clientId` is included in the `deviceInfo` section of `AlexaClientSDKConfig.json`, the error will be reported as an unrecoverable authorization error, rather than a more specific error.
2018-04-18 22:17:28 +00:00
|
|
|
// },
|
|
|
|
// "audioSink":"autoaudiosink"
|
2018-03-09 00:55:39 +00:00
|
|
|
// },
|
|
|
|
|
2018-02-12 23:31:53 +00:00
|
|
|
// Example of specifying a default log level for all ModuleLoggers. If not specified, ModuleLoggers get
|
|
|
|
// their log level from the sink logger.
|
|
|
|
// "logging":{
|
|
|
|
// "logLevel":"INFO"
|
|
|
|
// },
|
|
|
|
|
|
|
|
// Example of overriding a specific ModuleLogger's log level whether it was specified by the default value
|
|
|
|
// provided by the logging.logLevel value (as in the above example) or the log level of the sink logger.
|
|
|
|
// "acl":{
|
|
|
|
// "logLevel":"DEBUG9"
|
|
|
|
// }
|
2017-10-02 22:59:05 +00:00
|
|
|
}
|
2017-11-17 02:49:28 +00:00
|
|
|
|
|
|
|
|
|
|
|
// Notes for logging
|
|
|
|
// The log levels are supported to debug when SampleApp is not working as expected.
|
|
|
|
// There are 14 levels of logging with DEBUG9 providing the highest level of logging and CRITICAL providing
|
|
|
|
// the lowest level of logging i.e. if DEBUG9 is specified while running the SampleApp, all the logs at DEBUG9 and
|
|
|
|
// below are displayed, whereas if CRITICAL is specified, only logs of CRITICAL are displayed.
|
|
|
|
// The 14 levels are:
|
2017-12-09 00:07:37 +00:00
|
|
|
// DEBUG9, DEBUG8, DEBUG7, DEBUG6, DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, DEBUG0, INFO, WARN, ERROR, CRITICAL.
|
2017-11-17 02:49:28 +00:00
|
|
|
|
|
|
|
// To selectively see the logging for a particular module, you can specify logging level in this json file.
|
|
|
|
// Some examples are:
|
|
|
|
// To only see logs of level INFO and below for ACL and MediaPlayer modules,
|
|
|
|
// - grep for ACSDK_LOG_MODULE in source folder. Find the log module for ACL and MediaPlayer.
|
|
|
|
// - Put the following in json:
|
|
|
|
|
|
|
|
// "acl":{
|
|
|
|
// "logLevel":"INFO"
|
|
|
|
// },
|
|
|
|
// "mediaPlayer":{
|
|
|
|
// "logLevel":"INFO"
|
|
|
|
// }
|
|
|
|
|
|
|
|
// To enable DEBUG, build with cmake option -DCMAKE_BUILD_TYPE=DEBUG. By default it is built with RELEASE build.
|
|
|
|
// And run the SampleApp similar to the following command.
|
2018-02-12 23:31:53 +00:00
|
|
|
// e.g. ./SampleApp /home/ubuntu/.../AlexaClientSDKConfig.json /home/ubuntu/KittAiModels/ DEBUG9"
|