This week we added release notes for Cloud Platform.

Cloud Platform

Release typeEnvironmentFeatureSummary
1FixedOwlet-FieldAyla Message ServiceAdditional phone number validations are added to identify invalid phone numbers provided by users for receiving SMS notifications.

This week we added release notes for Cloud Platform.

Cloud Platform

Release typeEnvironmentFeatureSummary
1FixedUS-Dev
US-Field
EU-Field
User ServiceFixed an issue wherein Service Grant was not getting updated during Revoke Role/Update Role.
2EnhancedUS-Dev
US-Field
EU-Field
Shark-Field
Owlet-Dev
Ayla Customer Dashboard – Command Center
  • In Command Center job creation flows, we have added a Job Summary section (Step 5: Review and Create) to review all details before creating the job.

  • For a specific component job, in the HOST OTA page, in the OTA Attributes tab, under the UPGRADE To section, the text "Image host software version" is changed to "Image Component Software Version".
  • 3FixedUS-Dev
    US-Field
    EU-Field
    Ayla Factory ServiceOptimised the data sent to Ayla Factory Service (AFS) by the proxy Factory Service for displaying on the Ayla Customer Dashboard. This fix, avoids sending wrong/unwanted data to AFS.
    4FixedShark-Field
    Owlet-Dev
    Message ServiceTo fix invalid phone numbers entered by the users, we enabled we enabled a mechanism to add prefix to country code if it is not present.
    5FixedShark-Field
    Owlet-Dev
    Rule ServiceAdditional phone number validations are added to identify invalid phone numbers provided by users for receiving SMS notifications.
    6FixedUS-Dev
    US-Field
    EU-Field
    Data SearchFixed the datapoint search issue caused because of the "is_host_sw_version" value not getting updated while posting the datapoint value for devices.

    This week we added release notes for Cloud and Mobile Platforms.

    Cloud Platform

    Release typeEnvironmentFeatureSummary
    1FixedUS-FieldAyla Rule ServiceAdditional phone number validations are added to identify invalid phone numbers provided by users for receiving SMS notifications.
    2FixedUS-FieldMessage ServiceAs a part of phone number validation, we enabled a mechanism to add prefix to country code if it is not present.
    3EnhancedUS-Dev
    US-Field
    Shark-Field
    OTA Service
    ICC Service
    We improved the security around S3 access.
    4EnhancedUS-Dev
    US-Field
    Shark-Field
    Ayla Customer DashboardIn Ayla Customer Dashboard, we implemented paginations in the Properties page.

    Mobile Platform

    Following are the v6.9.05 release for Android:

    Release typeFeatureSummary
    1EnhancedLocal CachingIn SDK and Aura, enhanced Ayla local caching mechanism (allowCaching).
    2EnhancedLocal ModeIn 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)
    3EnhancedDevice SetupAdded a new API to get fresh Wi-Fi scan results and to ignore cached results during setup.
    4EnhancedDevice ShareIn SDK, FastTrack, and Aura, added support for device product name as tag parameter while sharing a device with new email template.
    5EnhancedRule Based NotificationsAdded support for Repeat Frequency for Ayla Destinations in Rules Based Notifications.
    6New FeatureCopilotAdded support for Copilot Events.
    7FixedRule Based NotificationsFixed an issue faced during updating actions with existing destinations for Rules Based Notifications.
    8FixedBLE SetupAdded timeout while connecting device to AP during BLE setup.
    9EnhancedRules Based NotificationsIn Aura added support for Priority, TTL, and Repeat Frequency in Ayla Destinations for Rules Based Notifications.
    10EnhancedDevice SetupWe 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

    Following are the v6.9.5 release for iOS:

    Release typeFeatureSummary
    1EnhancedLocal CachingIn SDK and Aura, enhanced Ayla local caching mechanism (allowCaching).
    2EnhancedLocal ModeIn 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)
    3EnhancedDevice ShareIn SDK, FastTrack, and Aura, added support for device product name as tag parameter while sharing a device with new email template.
    4EnhancedRules Based NotificationsIn SDK, added support for Repeat Frequency for Ayla Destinations in Rules Based Notifications.
    5New FeatureCopilotAdded support for Copilot event.
    6EnhancedRules Based NotificationsIn Aura, added support for Priority, TTL, and Repeat Frequency in Ayla Destinations for Rules Based Notifications.
    7EnhancedWi-Fi signalIn Aura, added support to indicate RSSI value while displaying Wi-Fi results during setup.
    8EnhancedNotificationsIn Aura, added support for rich notifications (Image).
    9SDK, Aura, Sepia, Sepia App, and FastTrack are built using Xcode 14.3 on macOS 13.5
    10Aura and Sepia are built using iOS_AylaSDK_Public v6.9.5
    11Sepia App and FastTrack are built using iOS_AylaSDK_Public & iOS_Sepia_Public v6.9.5

    This week we added release notes for Cloud Platform.

    Cloud Platform

    Release typeEnvironmentFeatureSummary
    1FixedUS-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
    2FixedShark-FieldOTA 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
    3FixedUS-FieldUser 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.
    4EnhancedUS-FieldUser Service
    • Added configurations to support OpenTelemetry.

    • Enhanced SSO provider configuration for the Salt parameter.
    5EnhancedUS-Dev
    US-Field
    Groups and ScenesFor 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
    6EnhancedUS-Dev
    EU-Field
    DataSearch ServiceAdded the “sw_version” parameter in DataSearch API (DSAPI) response which will be consumed by ICC service.

    This week we added release notes for Cloud Platform.

    Cloud Platform

    Release typeEnvironmentFeatureSummary
    1FixedOwlet-FieldAyla Message ServiceFixed 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.
    2FixedUS-Field
    EU-Field
    Mobile ApplicationFixed an issue wherein newly introduced date format caused applications to crash. This fix corrected the date format.
    3EnhancedUS-Field
    EU-Field
    User ServiceFixed the default logo display error in the authorization (Oauth) flow.
    4FixedUS-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.
    5FixedUS-Field
    EU-Field
    Device ServiceWe optimized device onboarding for the re-registration flow.
    6FixedShark-FieldMessage ServiceThere 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.
    7FixedShark-FieldRule 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”.
    8FixedShark-FieldICC ServiceWe 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.

    This week we added release notes for Cloud Platform.

    Cloud Platform

    Release typeEnvironmentFeatureSummary
    1FixedUS-Dev
    US-Field
    EU-Field
    Owlet-Dev
    Ayla Message ServiceFixed 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.
    2FixedOwlet-FieldAyla Customer Dashboard - Command CenterFixed a user interface issue that caused error while uploading the host OTA image.
    3FixedOwlet-FieldAyla Customer Dashboard - Command CenterUpdated 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.
    4EnhancedOwlet-DevAyla 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.

    No release notes added this week.

    This week we added release notes for Cloud Platform.

    Cloud Platform

    Release typeEnvironmentFeatureSummary
    1FixedUS-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.
    2FixedUS-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.
    3FixedUS-Dev
    US-Field
    EU-Field
    Image ServiceFixed an issue wherein logs were not getting printed to STDOUT (Console). With this fix, now the logs will be returned to STDOUT.
    4FixedUS-Dev
    US-Field
    EU-Field
    Device ServiceImplemented phone number validations to restrict invalid numbers in database through trigger apps.
    5FixedUS-Dev
    US-Field
    EU-Field
    All ServicesFixed an issue wherein log levels were not getting printed to STDOUT (console). After the fix, appropriate log levels are printed in STDOUT.

    This week we added release notes for Cloud Platform.

    Cloud Platform

    Release typeEnvironmentFeatureSummary
    1FixedUS-Dev
    US-Field
    EU-Field
    ICC ServiceWe 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.
    2FixedUS-Dev
    US-Field
    EU-Field
    Ayla Customer DashboardFixed a user interface issue that caused error while uploading the host OTA image.
    3FixedUS-Dev
    US-Field
    EU-Field
    Ayla Customer Dashboard - Command CenterUpdated 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.