1

Fixed

US-Field

Ayla Rule Service

Additional phone number validations are added to identify invalid phone numbers provided by users for receiving SMS notifications.

2

Fixed

US-Field

Message Service

As a part of phone number validation, we enabled a mechanism to add prefix to country code if it is not present.

3

Enhanced

US-Dev
US-Field
Shark-Field

OTA Service
ICC Service

We improved the security around S3 access.

4

Enhanced

US-Dev
US-Field
Shark-Field

Ayla Customer Dashboard

In Ayla Customer Dashboard, we implemented paginations in the Properties page.

1

Enhanced

Local Caching

In SDK and Aura, enhanced Ayla local caching mechanism (allowCaching).

2

Enhanced

Local Mode

In SDK and Aura, local mode is improved with 2048 RSA key negotiation:

• Added support for different key sizes (1024, 2048) for local mode communications (cryptoRSAKeySize)

3

Enhanced

Device Setup

Added a new API to get fresh Wi-Fi scan results and to ignore cached results during setup.

4

Enhanced

Device Share

In SDK, FastTrack, and Aura, added support for device product name as tag parameter while sharing a device with new email template.

5

Enhanced

Rule Based Notifications

Added support for Repeat Frequency for Ayla Destinations in Rules Based Notifications.

6

New Feature

Copilot

Added support for Copilot Events.

7

Fixed

Rule Based Notifications

Fixed an issue faced during updating actions with existing destinations for Rules Based Notifications.

8

Fixed

BLE Setup

Added timeout while connecting device to AP during BLE setup.

9

Enhanced

Rules Based Notifications

In Aura added support for Priority, TTL, and Repeat Frequency in Ayla Destinations for Rules Based Notifications.

10

Enhanced

Device Setup

We show alert to users if location is disabled while initializing device setup.

SDK, Aura, Sepia, Foundry, and FastTrack are built using Android Studio Giraffe | 2022.3.1 Patch 1, Java 11, Gradle 7.4 & AGP 7.3.0

Aura and Sepia are built using Android_AylaSDK_Public v6.9.05

Foundry and FastTrack are built using Android_AylaSDK_Public v6.9.05 & Android_Sepia_Public v6.9.05

1

Enhanced

Local Caching

In SDK and Aura, enhanced Ayla local caching mechanism (allowCaching).

2

Enhanced

Local Mode

In SDK and Aura, local mode is improved with 2048 RSA key negotiation:

• Added support for different key sizes (1024, 2048) for local mode communications (cryptoRSAKeySize)

3

Enhanced

Device Share

In SDK, FastTrack, and Aura, added support for device product name as tag parameter while sharing a device with new email template.

4

Enhanced

Rules Based Notifications

In SDK, added support for Repeat Frequency for Ayla Destinations in Rules Based Notifications.

5

New Feature

Copilot

Added support for Copilot event.

6

Enhanced

Rules Based Notifications

In Aura, added support for Priority, TTL, and Repeat Frequency in Ayla Destinations for Rules Based Notifications.

7

Enhanced

Wi-Fi signal

In Aura, added support to indicate RSSI value while displaying Wi-Fi results during setup.

8

Enhanced

Notifications

In Aura, added support for rich notifications (Image).

9

SDK, Aura, Sepia, Sepia App, and FastTrack are built using Xcode 14.3 on macOS 13.5

10

Aura and Sepia are built using iOS_AylaSDK_Public v6.9.5

11

Sepia App and FastTrack are built using iOS_AylaSDK_Public & iOS_Sepia_Public v6.9.5

1

Fixed

US-Dev
EU-Field

Ayla Rule Service

• Additional phone number validations are added to identify invalid phone numbers provided by users for receiving SMS notifications.


• We enabled a mechanism to add prefix to country code if it is not present

2

Fixed

Shark-Field

OTA Service

• Implemented S3 authentication through access key and secret key, instead of web token. This provides enhanced security as well as URL size optimisation.


• Image/File download issue is fixed

3

Fixed

US-Field

User Service

• Fixed an issue wherein OEM logo was missing from the account linking page.


• Fixed an issue wherein the API to download PEM gave corrupt data. This fix involves API upgradation for upload/download of PEM file as a part of ruby and rails upgrade.


• Fixed an issue wherein the APIs with content type as XML were throwing errors.


• Fixed the end-user metadata display issues in the Ayla Customer Dashboard.


• Fixed an issue wherein log levels were not printed to STDOUT. With this fix, now the log levels are returned to STDOUT as expected.

4

Enhanced

US-Field

User Service

• Added configurations to support OpenTelemetry.


• Enhanced SSO provider configuration for the Salt parameter.

5

Enhanced

US-Dev
US-Field

Groups and Scenes

For the Activate scene based on schedule, Upgrade Schedule, and Create Scene APIs, added validations (made mandatory) for the following parameters under the ["collection"]["schedule"] object:

• months_of_year
• end_date
• start_date
• days_of_week

6

Enhanced

US-Dev
EU-Field

DataSearch Service

Added the “sw_version” parameter in DataSearch API (DSAPI) response which will be consumed by ICC service.

1

Fixed

Owlet-Field

Ayla Message Service

Fixed an issue wherein alert history wrongly displayed status as “Delivered” when push notifications failed. This issue occurred in the following scenarios:

• *Apple Push Notification service (APNs)** 
• Unrelated APNs certificate

• Corrupt APNs certificate

• Invalid mobile device token


Firebase Cloud Messaging (FCM)

• Invalid FCM Key

• Invalid mobile device token

This fix helps the customers (OEMs) by rightly reporting the errors occurring while sending push notifications.

• *NOTE**: This has no impact on endusers.

2

Fixed

US-Field
EU-Field

Mobile Application

Fixed an issue wherein newly introduced date format caused applications to crash. This fix corrected the date format.

3

Enhanced

US-Field
EU-Field

User Service

Fixed the default logo display error in the authorization (Oauth) flow.

4

Fixed

US-Field
EU-Field

Factory Service

Device Service

Fixed an issue wherein third-party device onboarding failed due to unsuccessful signature verification by the Provision Device API. This fix enabled smooth onboarding of the third-party devices into Ayla Platform.

5

Fixed

US-Field
EU-Field

Device Service

We optimized device onboarding for the re-registration flow.

6

Fixed

Shark-Field

Message Service

There was no alert of the actions that are rate limited (not executed) due to the set Repeat Frequency. To address this, an alert history is generated with "Action has been rate limited" error message.

7

Fixed

Shark-Field

Rule Service

• Fixed an issue wherein Get actions API was producing error when “is_internal= true” and “paginated=true”. Also, now by default the API result is displayed in descending order.


• For Get actions and Get rules APIs, the response parameter “totalPages” is changed to “total_pages”.

8

Fixed

Shark-Field

ICC Service

We streamlined the from_version for OTA jobs:

• When both job and filter have version data, we consider the job's version as the from_version.


• If neither job nor filter has version data, we consider the from_version as ALL versions.


• If either job or filter has version data, we consider that as the from_version.

1

Fixed

US-Dev
US-Field
EU-Field
Owlet-Dev

Ayla Message Service

Fixed an issue wherein alert history wrongly displayed status as “Delivered” when push notifications failed. This issue occurred in the following scenarios:

• *Apple Push Notification service (APNs)** 
• Unrelated APNs certificate

• Corrupt APNs certificate

• Invalid mobile device token


Firebase Cloud Messaging (FCM)

• Invalid FCM Key

• Invalid mobile device token

This fix helps the customers (OEMs) by rightly reporting the errors occurring while sending push notifications.

• *NOTE**: This has no impact on endusers.

2

Fixed

Owlet-Field

Ayla Customer Dashboard - Command Center

Fixed a user interface issue that caused error while uploading the host OTA image.

3

Fixed

Owlet-Field

Ayla Customer Dashboard - Command Center

Updated privileges for the following roles in the Command Center service:

• OEM::Staff
• OEM::Support Engineer
• OEM::Support Manager

For more information on the roles and their privileges, please refer User Roles.

4

Enhanced

Owlet-Dev

Ayla Notification Service (ANS)

We enhanced Ayla Notification Service by adding additional error counters to enable detection of issues in early stages and take necessary action.

1

Fixed

US-Dev
US-Field
EU-Field

Rule Service
Ayla

Message Service

There was no alert of the actions that are rate limited (not executed) due to the set Repeat Frequency. To address this, an alert history is generated with "Action has been rate limited" error message.

2

Fixed

US-Dev
US-Field
EU-Field

ICC Service

OTA Service

Security Enhancements

Implemented S3 authentication through access key and secret key, instead of web token. This provides enhanced security as well as URL size optimisation.

3

Fixed

US-Dev
US-Field
EU-Field

Image Service

Fixed an issue wherein logs were not getting printed to STDOUT (Console). With this fix, now the logs will be returned to STDOUT.

4

Fixed

US-Dev
US-Field
EU-Field

Device Service

Implemented phone number validations to restrict invalid numbers in database through trigger apps.

5

Fixed

US-Dev
US-Field
EU-Field

All Services

Fixed an issue wherein log levels were not getting printed to STDOUT (console). After the fix, appropriate log levels are printed in STDOUT.

1

Fixed

US-Dev
US-Field
EU-Field

ICC Service

We streamlined the from_version for OTA jobs:

• When both job and filter have version data, we consider the job's version as the from_version.


• If neither job nor filter has version data, we consider the from_version as ALL versions.


• If either job or filter has version data, we consider that as the from_version.

2

Fixed

US-Dev
US-Field
EU-Field

Ayla Customer Dashboard

Fixed a user interface issue that caused error while uploading the host OTA image.

3

Fixed

US-Dev
US-Field
EU-Field

Ayla Customer Dashboard - Command Center

Updated privileges for the following roles in the Command Center service:

• OEM::Staff


• OEM::Support Engineer


• OEM::Support Manager

1

Enhanced

US-Dev
US-Field
EU-Field

ICC Service

DataStream Service

We enabled pagination in device property list in the following scenarios in Ayla Customer Dashboard:

• In DataStream page: Creating Stream
• In Command Center page: Creating Device Filter
• In Command Center page: HOST OTA image - Uploading Specific Component OTA Images

2

Data Retention update

US-Field
EU-Field

Data Retention

Data retention policy has been updated to retain the Data Export files for 1 year. Our updated Data Retention and Cloud Platform Usage Policy can be viewed at Cloud Platform Usage Policy.

3

Enhanced

US-Field
EU-Field
US-Dev

Message Service

Trigger App

We have moved away from a 10 Digit Long Code number to a Toll-free number for sending SMS. This will ensure better success rate and lesser screening from telecom carriers.

4

Fixed

Shark
Owlet-Dev

Weather/feed service

Fixed an issue wherein the temperature data remained stagnant. After the fix, the data is updated and displayed correctly.