1

Login

We resolved the issue with logging in to Ayla Aura on Android devices using Facebook credentials.

1

Connectivity

We resolved a corner-case issue in which when a property update occurred at the same time as the LAN mode client disconnected, the property update to the Cloud was reported to the application as having failed even though the update succeeded.

1

Wi-Fi Connection

We resolved an issue in which the output of wifi show provided a value of 56 dBm when it was actually -200 dBm (which indicates an unknown signal strength).

2

iOS Onboarding

We resolved an onboarding issue with Ayla Aura in which after logging in from a hotspot, the page would hang and display, “Error Opening Page.”

3

Wi-Fi Connection

We resolved an issue in which the adap_net_get_signal() was returning the incorrect value of the Received Signal Strength Indicator (RSSI). The adap_net_get_signal() now uses the RSSI provided by the ESP IDF API, which is esp_wifi_sta_get_ap_info(), instead of relying on CSI (Channel State Information) messages for RSSI values.

4

Debugging

We added support for the diag command to the ayla_demo application to facilitate debugging and optimize memory utilization.

1

Factory Actions

We resolved a corner-case issue in which some devices had null values for the private key in the Ayla Device Service (ADS) database, causing the factory provisioning scripts to fail. Consequently, those devices failed authentication in the Cloud.

1

BLE Local Control

This release includes the Bluetooth Low Energy (BLE) Local Control feature, which provides local control and monitoring of devices by mobile applications over BLE.

2

Logging

We added log snapshot support.

3

Logging

We added Bluetooth Low Energy (BLE) client bonding information to the log messages for debugging purposes.

4

Logging

We now have the ability to summarize core dumps (that were not previously in the log snapshot) and then to add those summaries to the log snapshot.

5

Logging

We added the BT command to provide Bluetooth Low Energy (BLE) statistics, such as:

• Number of bonded connections

• Number of active connections

• Statistics on BLE operations

6

Property Manager

We added echo handling to prop_mgr for scheduled property updates.

7

Utilities

We changed to the standard implementation of snprintf.

1

Device Connectivity

We added the capability to enable and disable either Bluetooth Low Energy (BLE) or LAN (Local Area Network), depending on which connection mode is configured for the device. These new settings are called BLE Connect and LAN Connect and are located on the Available Connects tab for the device in the Ayla Customer Dashboard.

2

BLE Device Onboarding

We added a timeout capability for the Bluetooth Low Energy (BLE) onboarding process.

3

Bluetooth Low Energy (BLE) Local Control

We enabled an enforcement of authentication in the Bluetooth Low Energy (BLE) Local Control feature.

4

Bluetooth Low Energy (BLE) Local Control

To improve debugging capabilities, we added the LAN IP key ID to the following:

• Relevant local control log messages to facilitate debugging.

• Authentication failure messages.

• Log messages when generating a new Ayla randomized ID.

5

Log Snapshot

We improved the output of the log-snap command.

6

Logging

We modified the log client to use the Ayla Device Service (ADS) connection instead of a separate connection to send logs. This eliminates a second Transport Layer Security (TLS) connection to the Cloud, thereby reducing the RAM required by the device.

7

Logging, Bluetooth Low Energy (BLE) Local Control

We added the connection handle to the BLE (Bluetooth Low Energy) characteristic read/write debug messages. This makes it easy to identify which client was responsible for each operation in the log messages when there are multiple mobile clients actively using the BLE Local Control feature.

8

Command Line Interface (CLI) Debugging

We added the device address to the output of the BT command.

9

Integrated Agent

We resolved a corner-case issue with a recurring error that caused the Ayla Integrated Agent devices to lose connection to the Cloud.

10

Integrated Agent

We resolved an issue in which after a timeout or HTTP error, the Ayla Integrated Agent devices were requesting all to-device properties.

11

Event Handler

We resolved an issue in which the ADS_UP event was posting twice after a reset.

12

iOS Onboarding

We resolved an onboarding issue with Ayla Aura in which after logging in from a hotspot, the page would hang and display, “Error Opening Page.”

13

Bluetooth Low Energy (BLE), Wi-Fi Setup

We resolved an issue in which when using Bluetooth Low Energy (BLE), the devices were accepting attempts to configure Wi-Fi even though it was already configured.

14

Security, Bluetooth Low Energy (BLE) Onboarding

We added Bluetooth Low Energy (BLE) access control checks to onboarding processes that require a PIN code. This ensures that unauthenticated clients are prevented from connecting to and receiving notifications from the device.

15

Dynamic Host Configuration Protocol (DHCP)

We resolved an issue in which the devices did not send the correct Dynamic Host Configuration Protocol (DHCP) name.

16

Integrated Agent

We added an exponential backoff algorithm to prevent the Cloud from being inundated with requests from devices when the Cloud encounters a problem that affects multiple devices.

1

Groups and Scenes

We added support for Daylight Savings Time to ensure that actions continue to trigger per the settings in the schedules.

1

Devices

We resolved an intermittent 401 error related to a corner case in which devices were randomly going offline and taking a while to recover.

1

Operating System Support

In this release of Ayla Aura, Foundry, FastTrack, and the Software Development Kit (SDK), we support Apple’s iOS 15 features, and changed the minimum version supported to iOS 13.

2

File Logs

In this release of the Ayla Software Development Kit (SDK), we made “error” the default setting for the iOS mobile app file logs, and provided an option to override this default in config/settings.

3

Metrics

In this release of the Ayla Software Development Kit (SDK), the AppBackground and AppTerminated metric types are now part of metric sample ratio.

4

Rules

We added the following Rule-Based Notification methods to the Ayla Software Development Kit (SDK):

• Fetch rules by DSN.

• Push notification support for new iOS devices.

• Delete orphaned actions.

• Delete orphaned destinations.

5

Rules

In this release of the Ayla Software Development Kit (SDK), we renamed dssManager to dsManager and rulesEngine to rulesService for consistency among all operating systems.

6

Library

In this release of the Ayla Software Development Kit (SDK), we resolved an issue with the Universal Static Library, and included an App Note on building and using this library.

7

User Interface

In this release of Ayla Aura, FastTrack, and Foundry, we resolved an issue with the UINavigationBar background color. For Ayla Aura, we also resolved the issue with textAttributes.

8

File Logs

In this release of Ayla Aura, FastTrack, and Foundry, the default setting for the iOS mobile app file logs is “error” when doing release builds, and the default setting is “debug” when doing Debug builds.

9

Device

In this release of Ayla Aura, we now use the UIDevice.getModelName() method to get the iOS device name instead of getDeviceModel().

10

User Interface

In this release of Ayla FastTrack, we resolved an issue with nil and index out-of-range crashes in the Timers, Schedules, and History screens.

11

File Logs

For both Ayla Foundry and FastTrack, you can now override the log level in the JSON Config file.

12

Notifications

In this release of Ayla Foundry, we improved configurations for device notifications as follows:

• Moved to default configurations.

• Changed the deviceProperties JSON object name to deviceNotifications.

• Changed the JSON action type called on_connect to online.

• Changed the JSON action type called on_connection_lost to offline.

13

User Interface

In this release of Ayla FastTrack, we resolved an issue with the appearance of the UINavigationBar backbutton, and the issue in the UITableView section header for smart bulb controls, device settings, and Support screens.

1

Factory Actions

We resolved the issues with slow queries that were affecting the performance of factory actions.

2

Notifications

We resolved an issue in which the email subject was formatted as [property name] of [dsn] instead of [display_name] of [dsn].

3

Data Streaming Service

As part of an improvement to AWS Kinesis, we added support for New Relic Application Performance Monitoring (APM) to optimize the performance of Ayla’s Data Streaming Service (DSS).

4

Notifications

We now have alphanumeric sender IDs for notifications sent using the Short Message Service (SMS). This is for countries that do not support numeric sender IDs.

5

Notifications

We resolved a corner case issue in which multiple copies of an email for the same trigger were being sent when the frequency time interval in the trigger app was exceeded due to slowness during high traffic times.

1

Devices

We optimized device authentication to increase stability and performance during surges in activity.

1

Rules

We made Redis cache optional to increase the overall stability of Rules and the speed of evaluating events.

2

Rules

We added support for cooperative rebalancing, which optimizes the performance and stability of Rules.

1

Groups and Scenes

We resolved a corner-case issue with Scenes in which schedules were not triggering per the specified time.

2

Command Center

For a simple, efficient user experience, we updated the user interface for the Set Property job with the same step-by-step approach as the Host OTA job.

1

Metrics

In the 6.7.2 release of the Ayla Software Development Kit (SDK) for iOS, we improved the following:

• The Cloud Latency metric for the URL parts and to include the Device Serial Number (DSN) in the metric logs.

• SetupMetric to include the Device Serial Number (DSN) in the metric logs.

2

Metrics

For the 6.7.2 release of Ayla's iOS Software Development Kit (SDK), we resolved an issue in which the app version number was sent to the metric logs instead of the build number.

3

Metrics

In the 6.7.2 release of Ayla Foundry and the Software Development Kit (SDK), metrics are enabled by default, and we added the ability to control the metric logs using the metric sample ratio feature.

4

Metrics

For the 6.7.2 release of Ayla's iOS Software Development Kit (SDK), we resolved an issue with the Cloud Latency logs in which AFNetworking 4.0.1 was not using the latest method.

5

Onboarding

In the 6.7.2 release of Ayla's iOS Software Development Kit (SDK), we improved Bluetooth Low Energy (BLE) scanning for the set-up process.

6

Rules

In the 6.7.2 release of Ayla's iOS Software Development Kit (SDK), we added the ability to create a destination object with parameters associated to each destination type (email, SMS, push).

7

SDK Core

In the 6.7.2 release of the Ayla Software Development Kit (SDK) for iOS, we added the getModelName method in the UIDevice utility class, providing the ability to get the iOS device name.

8

Rules

In the 6.7.2 release of Ayla Aura, we resolved an intermittent issue with crashes when deleting a rule.

9

Properties

In the 6.7.2 release of Ayla Aura for iOS, we improved integer data types to accept hexadecimal values.

10

Groups and Scenes

In the 6.7.2 release of Ayla Aura, we resolved issues with the settings class message and the Groups and Scenes .auraconfig URL for Ayla Cloud Services.

11

Onboarding

In FastTrack 6.7.2 for iOS, we improved unhappy path flows to enhance the Wi-Fi setup and Bluetooth Low Energy (BLE) process during onboarding.

12

User Interface

Ayla Foundry and FastTrack now support Spanish language in the 6.7.2 release for iOS.

13

User Interface

In the 6.7.2 release of Ayla Foundry and FastTrack for iOS, we improved the localization keys

14

Groups and Scenes

In the 6.7.2 release of Ayla Foundry, we resolved the issues with intermittent crashes when the user selects a gateway from the Drawer menu.

15

User Interface

In Ayla Foundry 6.7.2 for iOS, we now display the build and version number on the About screen.

16

User Interface

In the 6.7.2 release of Ayla FastTrack for iOS:

• The device list now refreshes when a user registers or unregisters a device.

• We improved the error messages for owned shares.

17

Onboarding

In the 6.7.2 release of Ayla FastTrack for iOS, we removed the duplicate Wi-Fi Service Set Identifiers (SSIDs) that appeared during the onboarding process.

18

User Interface

In the 6.7.2 release of Ayla FastTrack for iOS, we corrected the label on Time Zone screen, which was showing “Remove Device” as the screen name.

1

User Interface

Ayla Foundry and FastTrack now support Spanish language in the 6.7.02 release for Android.

2

Onboarding

In FastTrack 6.7.02 for Android, we improved unhappy path flows to enhance the Wi-Fi setup and Bluetooth Low Energy (BLE) process during onboarding.

3

Security
Rules
Metric

In the 6.7.02 release of Ayla’s Software Development Kit (SDK) for Android, we added the following:

• A new cryptography utility class that provides simple, secure storage for SharedPreferences.

• Device rules to support IPCHANGE, ON_CONNECTION_LOST, and ON_CONNECTION_RESTORE.

• The Device Serial Number (DSN) to the metrics core record.

4

SDK Core

In the 6.7.02 release of Ayla’s Software Development Kit (SDK) for Android, we resolved the ArrayIndexOutOfBounds exception error in the DateUtils formatter, and the reentrancy issue causing the null pointer exception for AylaConnectivity Manager disconnect().

5

Application Lifecycle

In the 6.7.02 release of Ayla Aura, Foundry, and FastTrack for Android, we upgraded compileOptions to allow JAVA 11 to be used. In the 6.7.02 release of the Ayla Software Development Kit (SDK) for Android, we removed the compileOptions section to allow JAVA 8 or 11 to be used.

6

Security

In the 6.7.02 release of Ayla Aura, Foundry, and FastTrack for Android, we added a secure root detection and alerting feature.

7

Security

The 6.7.02 release of Ayla Aura for Android has encryption/decryption of the Service Set Identifier (SSID) and passphrase in SharedPreferences.

8

Login

In the 6.7.02 release of Ayla Foundry and FastTrack for Android, you can now use the BiometricManager instead of the FingerprintManager.

9

Schedules

In Ayla FastTrack 6.7.02 for Android, the repeating timers execute every day of the week by default.

10

Login

We are currently working on the issue with logging in to the Android mobile app using your Facebook credentials.

1

Command Center

We optimized the load time when navigating to the Job Summary, Job Report, Job Details, OTA Attributes, Filter, and Schedule pages for an OTA job.

2

Rules

We resolved a corner-case issue with the Destination API in which the action did not trigger and instead returned a null pointer exception error.

1

Rules

We added enhancements to Rules that increase uptime and strengthen the resilience of the Ayla Cloud services.

2

Rules

We did code refactoring to improve the maintainability.

1

OEM Migration

We refined the options list in the Source Environment settings to include only the relevant environments for the selected target.

2

Command Center

We improved the performance of Over-the-Air (OTA) jobs by implementing a configurable 2-hour time limit for devices to acknowledge the update command. After 2 hours, the devices that have not acknowledged the update command are marked as "Failed." Users can retry the OTA update for Failed devices from the Job Reports tab in Ayla’s IoT Command Center.

3

Devices

We resolved an issue in which some new devices were failing the device authentication with a 401 error code.

1

Rules

We decoupled the Data Streaming Service from the Rules Service to improve the performance of both.

2

Gateway

We optimized the load time of the Nodes page for gateway devices in the Ayla Customer Dashboard. This eliminates the delays and timeouts that were occurring.

3

Users

We resolved an issue in which the user was not returned to the End Users page in the Ayla Customer Dashboard after clicking the Back button to decline the Access Personally Identifiable Information (PII) message.

4

Users

We resolved an issue in which a few countries were missing from the Country drop-down lists on the Sign Up, Create End User, and Create OEM User dialog boxes in the Ayla Customer Dashboard.

5

Intelligent OTA

We formally deprecated the Intelligent OTA feature set in the Ayla Customer Dashboard. These OTA features have been greatly enhanced and incorporated into Ayla’s IoT Command Center.

6

Rules

We externalized configurations in the Rules Service to enable better control of latency and polling.

1

Wi-Fi Security

We improved security by checking the signature on Wi-Fi firmware from external flash.

2

Onboarding

We resolved a Wi-Fi setup issue on iOS 14.x mobile devices.

3

ADA Client

We resolved an issue in which the client stopped acknowledging any properties sent to the MCU (Microcontroller Unit) after the Ayla Cloud returned an HTTP status 500 error. This 500 error occurred when the cloud attempted to get the location for a file property.

1

Groups and Scenes

We resolved an issue in which adding new devices to collections failed with a 422 error code.

2

Logs

We improved the logging mechanism on the mobile app.

3

Groups and Scenes

We resolved the issues that were causing errors when creating scenes, adding scenes as a child collection, and fetching any Household information (i.e., child collections or devices).

4

Groups and Scenes

We resolved the following:

• When fetching all collections associated with the Household owner, deleted collections are no longer included in the user collections that are retrieved.

• Guest members with sharing permissions no longer have issues accessing groups and scenes in the Household.

1

Rules

We added the ability to temporarily suspend (for 10 minutes) HTTP GET and POST requests to unstable endpoints. This improves performance, avoiding bottlenecks and potential outages.

2

Rules

We resolved an issue in which the action for any destination type (e.g., email, push, etc.) was not triggering per the value set for the repeat frequency parameter (which defines the minimum time between triggers).

3

Rules

We improved the evaluation algorithm, which removed latencies on Ayla's Data Streaming Service (DSS) and increased the speed of evaluating events (pertaining to rules).

4

Command Center

We resolved a corner-case issue with editing OTA attributes in Multi-Component OTA Host jobs.

5

Command Center

We added the from_version parameter to the GET /icc/v1/jobs/{job_id API to provide additional pertinent details about the job.

1

Command Center

We improved the performance of Over-the-Air (OTA) jobs by increasing the threshold for simultaneous device updates from 500 to 1000.

2

Command Center

We added the Host Software Version to the Device List for device filters. This gives you a view of all pertinent information on the target devices for a specific filter in the same place.

3

Command Center

We added a Cancelled status to the Job Reports tab. This shows all devices that were cancelled before receiving the OTA update.

4

Command Center

We resolved an issue in which the job status was imprecise when upgrading a specific component on multi-component devices. Now, the status for specific-component jobs accurately provides all details on the upgraded component, including the devices that succeeded and failed.

5

Device Properties

We added the ability for OEMs to allow their partners to manage specific device properties in the Ayla Platform. This enables the OEM’s partners to make changes to “allowed” properties for security or performance needs.

1

Groups and Scenes

We improved performance by optimizing the GET connection calls for faster queries and responses to and from the devices in a collection.

2

Command Center

For invalid jobs, we disabled the Start, Stop, Clone, and Refresh Job Count buttons on the Jobs tab to prevent users from trying to perform these actions on those jobs.

3

Command Center

On the Job Report tab, we provide options to remove queued devices from the OTA job and to retry the OTA update for failed devices only when there are Queued and Failed devices listed for the job.

4

Command Center

We improved the performance of the Jobs tab by removing a duplicate call that was sent when a page was loading for the first time.

5

Device Connection Status

We fixed an issue in which the Connection History in the Ayla Customer Dashboard was listing the online and offline statuses of the device out of order.

1

Groups and Scenes

We resolved an issue in which the collections were associated with the device instead of the user. This was causing schedules from the collection to trigger even after the device ownership changed.

2

Rules

We added the following connectivity events to Ayla Rules to provide users with the precise connection status of their devices:

• Online (which replaces on_connect)

• Offline

• IpChange (which is the original ip_change event and is triggered when a device calls GET /dsns and the IP is changed.)

• OnConnectionLost

• OnConnectionRestore

• Initializing

• PollingOnline

1

iOS SDK Utility

In the 6.7.1 release, the Ayla Software Development Kit (SDK) includes the NSDictionary utility method to sort by keys and return sorted keys.

2

Local Privacy Network

In the iOS 6.7.1 release of the Ayla Software Development Kit (SDK), we resolved a local privacy issue by enabling retries for fetching new devices upon failed attempts.

3

Device Sharing

In the iOS 6.7.1 release of Ayla Aura, we corrected the error message that displays when a device attempts to re-share with the same user.

4

User Profile

In the Ayla Aura 6.7.1 release for iOS, we resolved an issue in which the user profile would perform an unnecessary refresh while the user signed in and out of the app.

5

User Interface
Device Configuration
Rules

In both the 6.7.1 iOS and 6.7.01 Android releases of Ayla Mobile Foundry, developers can choose to show or hide devices used during development.

In Ayla Mobile Foundry 6.7.1 for iOS, we also added the following:

• The isDevelopmentDevice flag in device config to indicate whether the AylaDevice is a development device.

• A notification-only flow in Rules.

6

Rules

In the iOS 6.7.1 release of Ayla Mobile Foundry, we resolved an issue in which the activity indicator continued to spin even if an error occurred while creating the rule.

7

User Interface
Device
Analytics

In the iOS 6.7.1 release of Ayla FastTrack, we now display the build number in the FastTrack support screen and added support for the following:

• Firebase analytics

• The Ayla Smart Plug

8

Device
User Interface

In the iOS 6.7.1 release of Ayla FastTrack, you can configure your developmentDevice setting in the device config file to enable you to do the following by tapping three times on the screen title:

• Show or hide all devices in the Device List.

• Add devices.

• Share devices.

9

Device Sharing

In the iOS 6.7.1 release of Ayla FastTrack, we resolved an issue with the device sharing status in which it was not enabled or disabled when selecting or unselecting the checkbox.

10

Onboarding

In the iOS 6.7.1 release of Ayla FastTrack, we resolved an onboarding issue in which the onboarding flow stopped at the progress screen (unable to change to the personalization screen) if the device was registered but not connected to the Ayla Device Service.

11

Mobile App

In the iOS 6.7.1 release of Ayla FastTrack, we resolved issue in which the mobile app crashed when the smart bulb model was being swapped.

12

Configuration Settings

We added auraconfig support for EU and CN abbreviations in the 6.7.01 release of the Ayla Software Development Kit (SDK) for Android.

13

Test Runner

In the 6.7.01 release of Ayla Aura for Android, we added the following to improve Test Runner:

• Support for managing properties.

• Connectivity checks before starting.

• Better reporting on single-and multi-test results.

14

FastTrack Smart Plug
FastTrack Color Smart Bulb

In the Ayla Aura and FastTrack 6.7.01 release for Android, we added support for the FastTrack Smart Plug and Color Bulb.

15

WeChat
Baidu

In Ayla Aura 6.7.01 for Android, we moved the Baidu and WeChat OAuth code out of the US default, making it available to other regions globally.

16

Login

In the 6.7.01 Android release of Ayla Aura, Mobile Foundry, Fast Track, and AMAP, we refactored Google Sign-In options for all variants and deprecated code to improve the log-in process for users.

17

Notifications
Login

In the 6.7.01 Android release, we now support the following for Ayla Mobile Foundry:

• Simplified rule-based device and property notifications

• Biometrics class (which replaces fingerprint)

18

Device

In the 6.7.01 release of Ayla FastTrack for Android, we resolved an issue in which the Device List did not refresh, particularly when the list was empty.

19

User Interface

In the Ayla FastTrack 6.7.01 release for Android, the Device List filter option now shows new entries at the top of the list upon a refresh.

20

User Profile

In the 6.7.01 release of AMAP for Android, we resolved issue in which profile information was still showing after deleting the account.

21

Permissions

In the AMAP 6.7.01 release for Android, we resolved an issue in which there was a missing call to super in the onRequestPermissionsResult() method.

1

Groups and Scenes

We added real-time monitoring for Groups and Scenes to continually check all aspects of performance and quickly respond to any issues.

2

Devices

OEM Admin users can now access the “Remote Client” and send commands from the Device Control tab in the Ayla Customer Dashboard.

3

Device Search

We resolved an issue with slow response times when searching for devices by the Device Serial Number (DSN) in the Ayla Customer Dashboard.

4

Rules

We resolved intermittent performance issues (i.e., network lag) by improving the routing algorithm to reduce CPU utilization.

5

Device Connectivity

We resolved an issue in which the Connection History in the Ayla Customer Dashboard was showing the same timestamp for "offline" as when the device was online.

6

Device Schedules

We added an option to clear the End Time setting in Device Schedules. This enables users to change the schedule from a specific time range to continuous.

7

Command Center

We resolved an issue with deleting jobs that had a large number of devices (more than 1000).

8

Command Center

We improved the performance of Over-the-Air (OTA) jobs by increasing the threshold for simultaneous device updates from 100 to 500.

1

Command Center

To keep you abreast of each stage during your Host OTA job, we added new statuses for Downloading and Downloaded to the Job Reports tab in the Ayla Customer Dashboard.

2

Command Center

From the Device Filters tab in the Ayla Customer Dashboard, you can now open a new browser tab to view, edit, and configure a device when you click its DSN in the Device List.

1

Device Onboarding

We resolved an intermittent device provisioning issue that occurred when registering devices between 1 - 2 AM EST using the AP-Mode Registration Method.

2

Command Center

We resolved an issue with deleting filters configured for a large number of device serial numbers (DSNs).

3

Datapoints

We resolved a date parsing issue occurring in daylight savings time zones. The Update At Cloud date displayed for the datapoint in the Ayla Customer Dashboard did not match the backend response value.

1

Remote Device Management

The 2.9.10 release of the Ayla Production Agent for the Murata 1LD model has been improved as follows:

• Upon receiving notifications, the device now requests commands (not property updates) from the Cloud even if listen was not enabled by the microcontroller unit (MCU).

• To facilitate troubleshooting, the platform now supports enabling the client listen command from the Command Line Interface (CLI).

• The device now has an auto-recovery process in which the device makes sure it is able to get commands from the Cloud at least once every 24 hours and if the device cannot do this, it resets itself.

2

Device Connectivity

The 2.9.9 release of the Ayla Production Agent for the Murata 1LD model provides the following improvements:

• Domain Name System (DNS) cache entries are not deleted when the device loses connectivity to the plaftform.

• We added statistics to the notification mechanism to enhance the troubleshooting process.

• We added enhancements to reduce memory usage.

3

Device Connectivity
Wi-Fi Connectivity
Wi-Fi Setup

In the 2.9.9 release of the Ayla Production Agent for the Murata 1LD model, we resolved various issues related to performance, Wi-Fi connectivity, and Wi-Fi setup. Following are some examples:

• LAN mode no longer crashes after an MCU response timeout.

• When disconnected for a short time, the device no longer expects listen to be enabled if the MCU was not notified of the outage.

• In LAN mode, the first request for a property no longer times out.

• We resolved an issue in which under some conditions, multiple simultaneous accesses to the Wi-Fi chip would cause the chip to become unresponsive, and the module would reset to recover.

• We resolved an intermittent issue in which responses from the device to the Cloud were taking too long to time out if the network connection was lost. We now have a 25-second timer on all property sends to the Cloud, which cancels the send operation if any underlying network issues arise.

• We reduced memory usage to use module resources more efficiently, and prevent memory exhaustion errors.

• When an invalid URL for a file datapoint is received, the module now recognizes the error, terminates the file property operation, and continues to fetch other commands or post properties.

• There is no longer a memory leak after the final probe timeout.

1

Message Templates

We resolved an issue with email templates in which the customized email was configured to show the product name, but incorrectly included the property name instead.

1

Debugging

For both the iOS and Android 6.7.0 release of the Ayla Software Development Kit (SDK), we resolved several issues with static code analysis.

2

Bluetooth

In the iOS 6.7.0 release of the Ayla Software Development Kit (SDK), we added support for Received Signal Strength Indicators (RSSI) and Basic Service Set Identifiers (BSSID).

3

Schedules

For the iOS 6.7.0 release of the Ayla Software Development Kit (SDK), we included a new AylaSchedule method that has initialization support.

4

Groups and Scenes

For the iOS and Android 6.7.0 release of the Ayla Software Development Kit (SDK), we added custom email support for sharing with a top-level group.

5

PaaG

For the iOS 6.7.0 release of the Ayla Software Development Kit (SDK) and Mobile Foundry, we added a new Connect Local Device method that has configurable timeout for PaaG (Phone as a Gateway) devices.

6

Rules

For the iOS release of the Ayla Software Development Kit (SDK), we resolved the following:

• The Ayla Rule formatDatapointExpression no longer returns the wrong expression for the Number type.

• There are no longer any issues with XCode 12.5 unit test build when “new” is used to create objects.

7

Device Logs

In the 6.7.0 release of Ayla Aura for iOS, we added support for log levels in the auraconfig file.
In the 6.7.0 release of Ayla Aura for Android, we created an app note on how to change log level settings.

8

Properties

In the 6.7.0 release of Ayla Aura for iOS, you can use default properties for the Ayla Shield Dev Kit if the managed properties are omitted.

9

Test Runner

In the 6.7.0 release of Ayla Aura for iOS, we added a Cloud-mode test to Test Runner.
For Ayla Aura on both iOS and Android, we improved the device and property support for Test Runner.

10

FastTrack Color Smart Bulb

In the iOS 6.7.0 release of Ayla FastTrack and Mobile Foundry, we added the following support and features for FastTrack Color Smart Bulb:

• A new device onboarding flow that provides the option to configure the Wi-Fi Access Point over Bluetooth Low Energy.

• White mode and color mode support.

• Preset values for white temperature and color modes.

• Custom control for dynamic white temperature and color mode selection.

• Device listeners to reflect external changes in the UI.

11

Schedules

We are currently working on bug fixes and enhancements related to displaying and triggering device schedules.

12

Onboarding

In the iOS 6.7.0 release of Ayla FastTrack, we modified the AP mode Wi-Fi icons.

13

Onboarding

In the iOS 6.7.0 release of Ayla FastTrack, we resolved an issue in which the sign-up fields were not clearing after clicking the links for the Terms and Conditions and Privacy Policy.

14

Groups and Scenes

In the 6.7.0 release of the Ayla Software Development Kit (SDK) for Android, we added support for schedules.

15

SDK

In the 6.7.0 release of the Ayla Software Development Kit (SDK) for Android, we made the following improvements:

• Upgraded the unit test framework to use InstrumentationRegistry.

• Updated the pre-AndroidX libraries, API calls, and import statements.

• Upgraded the WeChat SDK to the latest version, 6.6.23.

• Removed allowBackup="true" from all AndroidManifest files.

• Added ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION permissions to allow BLE scanning.

16

Onboarding
Properties

In the 6.7.0 release of the Ayla Software Development Kit (SDK) for Android, we resolved issues with the following:

• The ScanResults RSSI (Received Signal Strength Indicators) value in the Bluetooth Low Energy (BLE) /Wi-Fi onboarding flow.

• The handling of the AylaCollectionProperty basetype.

17

Ayla Aura (General Updates)

In the 6.7.0 release of Ayla Aura for Android, we updated the pre-AndroidX libraries, API calls, and import statements.

1

Command Center

We removed the option to include additional devices in a filter to simplify the UI. Customers were not using this option, according to feedback and usage data.

1

Command Center

We resolved an issue in which confirmation messages displayed even when an error occurred. Now, if there is an error, only the error message banner displays.

2

Insights

We resolved an issue with “Active” device counts in which the number of active devices was not calculated properly.

1

Command Center

We resolved an issue with schedules in which the start time for OTA jobs did not work as expected in certain scenarios.

1

Message Templates

We updated our customizable email templates. You can now specify a different "From Address" in the email header as an alternative to the default email address.

2

Groups and Scenes

We resolved an issue with the Sunrise/Sunset schedules triggering outside the user’s settings.

1

Ack-Enabled Properties

We resolved an issue in which the Ayla cloud was not reflecting an ack-enabled property change when responding to GETs, even though the device had echoed this property change to update the cloud (via HTTP POST).

2

Rules

We resolved an isolated caching issue in which there was a rule triggering outside the date range setting for the datapoint.

1

Command Center

We resolved two issues with Multi-Component OTA jobs:

1. An error with the Time Since Activation setting for the Lifecycle/Status filter.
2. An error related to a corner case where two components had the same firmware target value.

1

Groups and Scenes

We resolved an issue in which shared users were not able to fetch group information using the device serial number (DSN).

2

Groups and Scenes

We resolved an issue in which users still had access to shared devices after the sharing access was removed.

1

Schedules

This release of the Integrated Agent includes the ability for users to define device schedules based on local sunrise and sunset times.

2

ESP-IDF

We added support for the latest ESP-IDF 4.1 to improve signed binaries and encrypted flash.

3

ESP-IDF

In this release of the Integrated Agent, we resolved various bugs related to performance issues, Wi-Fi connectivity, and Wi-Fi setup.

4

Wi-Fi Security

We added WPA3 support to enable customers to meet the latest requirement for the Wi-Fi Alliance Certification.

5

CLI

We added support to enable CLI commands to be sent remotely by Ayla Admins from the Ayla Customer Dashboard to aid in troubleshooting.

6

Wi-Fi Connectivity

We added auto-recovery from connectivity issues so that Ayla devices reset themselves if they are unable to get a command from the Cloud within a 24-hour period.

7

Wi-Fi Setup Over BLE

We added the option to disable the BLE passkey authentication.

8

OTA

We allow applications to request larger OTA chunks to improve the overall OTA time.

9

ESP-IDF

We provide additional power-saving modes as supported by the latest ESP-IDF.

1

User Interface

We resolved an issue with loading the following pages in the Ayla Customer Dashboard:

• The Profile page for the logged-in user.

• All of the tabs when viewing or editing the end user’s details.

1

User Interface

When you save, update, and delete configurations in the Ayla Customer Dashboard, a success message banner displays across the top of the page when the action is completed successfully, or an error message message banner displays if there is an issue. Both banners remain on the page until the user closes the message or leaves the page.

2

Command Center

The OEM::SupportManager role now has complete access to Host OTA jobs in the Command Center, which includes privileges to schedule, stop, start, and delete jobs. Previously, this role only had the ability to create, edit, and clone jobs. Click here for information on Roles in the Ayla Platform

1

Groups and Scenes

For both the iOS 6.6.6 and Android 6.6.07 releases of the Ayla Software Development Kit (SDK), we made the following enhancements:

• Added support for base types in the scene properties.

• Added base type support to the init method for the AylaCollectionProperty.

For iOS 6.6.6, we also updated the application notes for using the mobile SDK.

For Android 6.6.07, we also changed the default for pagination to False.

2

Groups and Scenes

In the Android 6.6.07 release of the Ayla Software Development Kit (SDK), we fixed the Uniform Resource Identifier (URI) for Ayla Groups and Scenes services.

3

Command Center

In the 6.6.6 release of Ayla Aura for iOS, we improved the filters for OTA jobs in the Command Center.

4

Device Logs

In the 6.6.6 release of Ayla Aura for iOS, we added log levels to auraconfig.

In the 6.6.07 release of Ayla Aura for Android, we added the following support for file and console logs:

• auraconfig support for consoleLogLevel and fileLoglevel.

• file and console level configurations to the App Settings screen.

5

Schedules

In the 6.6.07 release of Ayla Aura for Android, we improved the schedule datepicker.

6

Command Center

In the 6.6.07 release of Ayla Aura for Android, we improved the User Consent delivery option for OTA jobs in the Command Center.

7

User Interface

In both the 6.6.07 release of Ayla Aura and AMAP for Android, we added pull to refresh the Device List filter option.

1

Notifications

We resolved an issue in which some notifications were sent via SMS but none were sent via email when the SMTP Settings were not configured. If the SMTP settings are not configured, the notifications will be sent using the default Ayla SMTP configuration. Click here for information on configuring SMTP settings.

2

Groups and Scenes

We added the following enhancements to the Groups and Scenes feature:

• When you share a collection with another user, that user has access to all devices in the collection, including those in the child collection. A child collection is a particular type of devices that may be associated with more than one collection. For example, you may have a collection called Living Room, which contains a group of various devices, and then associate a child collection called Ceiling Fans that is also associated with other collections. Click here for a description of Groups and Scenes.

• Users now automatically have access to any new devices that you add to your shared collection.

3

Dealers

We resolved the issue in which APIs (specifically /api/v1/users/index_by_label and /api/v1/users/index_by_role) were not returning the customers' phone numbers when logged in as a Dealer User. All of the following APIs contain phone numbers in the response schema:

• /api/v1/users/index_by_label

• /api/v1/users/index_by_oem

• /api/v1/users/index_by_role

Click here for information on Dealers.

1

Insights

We added a Billing Data tab to Ayla Insights. This new feature enables you to stay up to date with and analyze platform consumption and usage for billing purposes. When you log in to the Insights Dashboard, the Billing Data tab is accessible from the main Insights menu.

2

Devices

We resolved an issue in which some gateway devices in the US field environment were showing duplicate offline events in the device’s connection history while the device was actually still online.

1

Command Center

We added a number of indexes to address slow queries that lead to random and intermittent errors during Over-the-Air (OTA) jobs in the Command Center.

2

Groups and Scenes

We added Collection Share support for message templates in the Groups and Scenes feature. This enables you to create and update notifications for collection sharing. For example, you can send a notification to tell a family member that they can view and activate one of your Groups and Scenes configurations in the household. Click here for a description of Groups and Scenes.

1

Groups and Scenes

We resolved an issue affecting the iOS Software Development Kit (SDK) in which when trying to fetch all groups (owned and shared) using the GSS-Groups API, the SDK only returned the owned groups, not the shared groups.

2

Dealers

We updated the Role Based Access Control (RBAC) to broaden data access for dealers. Dealers with OEM::Admin and OEM::Staff roles can use the oems/{oem_id}/end_users API to view all end users’ phone numbers. This enables dealers to robustly gather data on their end users. Click here for more information on roles/privileges.

3

Message Templates

We added a subject.txt file to the custom email samples. Users should provide the subject of the email in this new subject.txt file for security reasons. Click here for more information on message templates and using the custom email samples.

4

Properties

We resolved an issue in which the device received the wrong file property datapoint for the file. The user was able to upload a new file/create a new file property datapoint even though the previous file property datapoint was not closed (marked as fetched). As a result, the device was receiving the incorrect file property datapoint (the previous one that was not closed) for the new file. File property datapoints must be marked as fetched to allow for subsequent file uploads/downloads. Refer to the tech note on Ayla File Properties for more information on how they work.

1

Command Center

We applied a user filter to resolve a user access issue with the device_job API. This issue occurred when the GET user devices API was called to fetch DSNs (Device Serial Numbers) only.

2

Command Center

When the device_job API is used without any query parameters (i.e. oem_model, device_status, dsns, etc.), the query times out and returns a 500 error code.

3

Command Center

We improved the formatting in the Excel file for the downloaded Job Report, e.g. removed unnecessary columns in sections where they were not needed. Click here for more information on the Job Report in Ayla’s IoT Command Center.

4

Data Streaming Service

In Ayla’s Data Streaming Service (DSS), we deprecated all older DSS functionality, which has been added to and improved in our robust event-based DSS. Click here for user documentation on DSS.

5

Command Center

We added statuses for Activated At dates/times to the Filter Preview in the Create Using Query filter option. This enables you to review the before and after activation dates/times of devices that should be included in the Host OTA job. Click here for more information on creating host OTA jobs in Ayla’s IoT Command Center.

1

Groups and Scenes

For iOS 6.6.5 and Android 6.6.06 releases of the Ayla Software Development Kit (SDK), we did the following:

• Improved and added unit tests for scheduling and sharing.

• Added CRUD (Create, Read, Update, Delete) support for Group Sharing.

• Added CRUD (Create, Read, Update, Delete) support for Scheduled Scene triggering, but does not include SQL Server Reporting Services (SSRS).

• Updated the application notes for using the mobile SDK.

For iOS 6.6.5, we updated AppleDoc from in-line comments.

For Android 6.6.06, we updated JavaDoc from in-line comments.

2

OTA

For iOS 6.6.5 and Android 6.6.06 releases of the Ayla Software Development Kit (SDK), we included the following to improve User Consent jobs:

• Support for multiple job status filters.

• Device statuses for OTA jobs: PENDING, CONSENT, SCHEDULED, PROCESSING, SUCCEED, FAILED, PARTIALY_FAILED, CANCELLED, QUEUED, WAITING, RETRY.

• Updates to OTA test units.

3

OTA
Groups and Scenes

Both the iOS 6.6.5 and Android 6.6.06 releases of the Ayla Software Development Kit (SDK) have the following issues:

For OTA:

• The oem_model and dsns parameters are marked as optional, but if either is omitted, a 500 error code is returned.

• Device statuses for DOWNLOADING and DOWNLOADED are not implemented yet.

For Groups and Scenes Collection Shares:

• Updating a Share without devices fails.

• Fetching owned shares and receiving shares are not filtered by collection type.

• Share all Collections is not implemented yet.

• Collection Share support for the OEM message template is not implemented yet.

For Groups and Scenes:

• The ability to retrieve groups or scenes based on matching a custom_attribute keyword or value is not implemented yet.

• When updating or setting [devices/child collections] states in a collection, the property value returns the wrong type.

• You cannot add a scene under a group.

4

User Interface

In the iOS 6.6.5 release of the Ayla Aura, we resolved the following issues:

• Displaying start and end times for schedules.

• Selecting the dark theme when the app is in the foreground.

5

Device Shares

In the iOS 6.6.5 release of Ayla Mobile Foundry, we improved the ability to display shares by grouping based on the user.

6

User Interface

In the iOS 6.6.5 release of Ayla Mobile Foundry, we resolved the issue with displaying the device LAN IP address in the Device Info screen.

7

Cryptography

In the Android 6.6.06 release of the Ayla Software Development Kit (SDK), Ayla Aura, Mobile Foundry, and AMAP, we upgraded the cryptography library to Bouncy Castle version 1.68, which requires the following additions to the application gradle.properties file:

• android.jetifier.blacklist = bcprov-jdk15on-1.68.jar

• android.jetifier.ignorelist with AGP 4.2

8

OTA

In the Android 6.6.06 release of Ayla Aura, we included multi-filter options in our OTA support.

9

Sepia Framework

In the Android 6.6.06 release of Mobile Foundry, we added a new method to push a SepiaScreen that was already created.

10

FastTrack

In the Android 6.6.06 release of Mobile Foundry, we made backport improvements for FastTrack.

1

Data Streaming Service

We added two connectivity events to Ayla’s Data Streaming Service (DSS):

• Initializing - STATUS_INITIALIZING = "initializing";

• Polling Online - STATUS_POLLING_ONLINE = "pollingOnline";

You can use the new connection statuses to know when specific devices enter the initialization or polling online states. For example, you may want to tell end users the most up-to-date status, like when devices are in the polling online state, in case the devices are experiencing latency for control events.

2

Command Center

We added a Job Report tab to Ayla’s IoT Command Center so that you can review your host OTA jobs, as well as modify some aspects of jobs that are in progress. This tab provides the ability to:

• Review the operational status of a specific device or all devices for the selected host OTA job.

• Remove devices queued to receive the OTA update from the selected host OTA job.

• Retry to download the OTA update to devices that failed to complete the last update.

• Download the entire OTA Job Report.

Click here for information on how to use this tab.

1

Reports

We updated the reports API to support the End User role so that end users can issue calls to access the get_raw_data_points report and retrieve historic data. Previously, only the OEM Admin role was allowed to complete these actions.

2

ICC Host OTA

We refined our OTA features to ensure a robust and stable delivery of all firmware OTA updates configured in Ayla’s IoT Command Center (ICC). Some of our main focus areas have been:

• Continuous OTA

• Scheduling

• Editing

Click here for more information on the Command Center in the Ayla Customer Dashboard.

1

Sunrise/Sunset Schedules

The iOS 6.6.4 and Android 6.6.05 releases of the Ayla Software Development Kit (SDK) support the sunrise and sunset settings in Ayla schedules. If your device and its firmware version support the ability to execute schedules based on sunrise and sunset times, you can configure these settings. Refer to the Ayla Developer Portal User’s Guide for more information on enabling and configuring Sunrise/Sunset setting in your schedules.

2

Groups and Scenes

In the iOS 6.6.4 and Android 6.6.05 releases of the Ayla Software Development Kit (SDK), we improved and added unit tests for the alpha release of Groups and Scenes. For iOS 6.6.4, we also added the following:

• Corrections to APIs and their documentation

• Metrics for create collection

• Custom attributes for CRUD (Create, Read, Update, Delete) support

• Groups and Scenes developer’s application note in /doc folder

For Android 6.6.05, we also added the following:

• Updates to CRUD (Create, Read, Update, Delete) APIs to match the Groups and Scenes Service APIs

• Triggering API for Groups and Scenes

• JavaDoc and AppleDoc from in-line comments

• Application notes for using the mobile SDK

3

Device Onboarding
Messages
Metrics

For the iOS 6.6.4 release of the Ayla Software Development Kit (SDK):

• We improved unhappy path flows to enhance the device onboarding experience.

• We added CreateDestinations() helper API support for message services.

• We have additional metrics support for feature usage.

4

Location Privacy

In the iOS 6.6.4 release, we improved location privacy for iOS 14 in Aura and Mobile Foundry.

5

FastTrack

For Mobile Foundry, we improved the user interface (UI) for FastTrack schedules with SQL Server Reporting Services (SSRS) in the iOS 6.6.4 release, and added the following UI support in both the iOS 6.6.4 and Android 6.6.05 releases:

• FastTrack Timer

• FastTrack Usage

• FastTrack History

• FastTrack Device Share

In the Android 6.6.05 release, we also made the following backport improvements for FastTrack:

• A new method to theme a table layout

• A new radio button using the current theme

• Better toolbar color theming

6

Localization
Device Onboarding

In the iOS 6.6.4 release of Mobile Foundry, we improved the localization text and added the following to improve the on-boarding process:

• Support for registration via cellular data

• Showing progress during Wi-Fi disconnections

7

Local Privacy Network

In the iOS 6.6.4 release, local network privacy does not have an API to check for allowed or denied, which may cause the on-boarding process to fail. Refer to the iOS 14 Privacy Changes document for details.

8

Rules

In the Android 6.6.05 release of the Software Development Kit, we fixed a bug in the rule integer expression.

9

Sepia Framework

In the Android 6.6.05 release of Mobile Foundry, we reverted AllDevicesScreen to AllSepiaDevicesScreen.

1

Command Center

We resolved a Command Center issue in which devices that came online after the OTA job was started (and still active) did not receive the OTA update until the job was stopped and restarted.

1

Rules

We resolved the issue with slow responses and timeouts when issuing calls to the message service, e.g. GET /messageservice/v1/destinations.

2

Migration

We resolved the issue in which migrating templates from the US Development to US Field environment were failing with a 422 error code. Click here for more information on Template Migration in the Ayla Customer Dashboard.

1

Triggers

We resolved the following trigger notification issues:

• Trigger notifications configured for email and SMS (Short Message Service) using contact_id were missing rules from the configuration. This was occurring because the contact_id was referenced instead of the email or SMS.

• Trigger notifications configured to be sent to 2 or more destinations (i.e. email or SMS) were only sent to one of the destinations.

2

Templates

We resolved a template property issue in which a mime_type error occurred while configuring a property in the Ayla Developer Portal when the base type was set to message, and either of the first two MIME types were selected: application/json or application/octet-stream.

3

Users

We resolved the latency issues with database queries when issuing User Service API calls (particularly /api/v1/users/index_by_oem.json and /oems/293/end_user ).

1

Groups and Scenes

For both the iOS 6.6.3 and Android 6.6.04 release of the Ayla Software Development Kit (SDK), an alpha release of device Groups and Scenes is available for US Development. Groups enable the user to view and control (perform a single action on) a collection of similar devices (i.e. lights) as a single entity. Scenes enable the user to activate different types of actions to a group of different devices at the same time (e.g. the action might be “morning” and when activated the coffee machine starts, the thermostat is set to a different temperature, and the window shades are raised.) This first phase includes:

• CRUD (Create, Read, Update, Delete) APIs

• Triggering API for Groups

• Unit tests for Groups and Scenes

• AppleDoc generated from inline comments

2

Local Privacy Network

In the iOS 6.6.3 release, local network privacy does not have an API to check for allowed or denied, which may cause the on-boarding process to fail. Refer to the iOS 14 Privacy Changes document for details.

3

Device Onboarding
Notifications
LAN Mode

For the iOS 6.6.3 release, in the Ayla Software Development Kit (SDK):

• We improved unhappy path flows to enhance the device onboarding experience.

• We updated rules-based notifications and inline documentation to address onboarding errors.

• We optimized property retrieval in LAN Mode.

In Aura, we improved the error handling of unhappy paths on BLE (Bluetooth Low Energy) and Wi-Fi.

4

Social Login

In the iOS 6.6.3 release, Ayla Mobile Foundry also includes user interface improvements, such as the ability to add and remove the social login using Foundry.json.

5

Device Setup

In iOS 6.6.3, we fixed the issue causing Ayla Mobile Foundry to crash when launching the advance setup on the iPad.

6

Notifications

In the iOS 6.6.3 release, we added rules-based notifications for email, SMS (Short Message Service), and push.

7

Trigger Notifications

In the Android 6.6.04 release of the Ayla Software Development Kit (SDK) and Ayla Aura, we deprecated trigger-based notifications for email, SMS (Short Message Service), and push.

8

Device Onboarding

The Android 6.6.04 release provides improvements to the user interface, user experience, and Wi-Fi setup for Ayla Aura, such as a larger tap region for advanced set-up flows and the ability to cancel and close BLE (Bluetooth Low Energy) and Wi-Fi set-up processes.

9

Setup Token

In the Android 6.6.04 release, we fixed the issue in which the set-up token for Wi-Fi and BLE (Bluetooth Low Energy) was not sent and returned an error.

10

Registration

In the Android 6.6.04 release, AMAP has the following issues:

• The legacy DevKit fails when using the Same LAN registration method.

• The Play Store release is still in review.

1

Schedules

We fixed the issue in which there were duplicate scheduled actions appearing in Over-the-Air (OTA) jobs. This occurred after associating a new template, which was then used for OTA jobs created and started on the Ayla Customer Dashboard.

2

OTA

Based on an intermittent issue in which the success or failed status_update call was not propagated in the Over-the-Air (OTA) services, we changed to an asynchronous process making status updates more robust and stable.

3

Schedules

We improved the Schedule API to use a JSON metadata object to confirm that the device supports the Sunrise/Sunset feature. This feature enables you to configure local sunrise and sunset times in Ayla schedules if your device and its firmware version support the ability to execute schedules based on sunrise and sunset settings. The new metadata object ("metadata":{ "sunrise_sunset":true}) can be returned via GET APIs or set by the client application. If your device does not support sunrise/sunset settings, the sunrise_sunset key value pair is omitted; it is not necessary to use a sunrise_sunset:false key value pair.

4

Triggers

We fixed an issue in which device property triggers were not completely removed from the platform when deleting the trigger notification.

5

Devices

We fixed an issue in which the getRules endpoint ignored the input parameters for specific DSNs (Device Serial Numbers) or UUIDs (Universally Unique Identifiers) and instead returned all rules for devices/users mapped to the DSN or UUID specified.

6

Triggers

We fixed the issue in which changing notification preferences caused the trigger notification to fail.

7

Command Center

We increased the OTA image size limitation to 512 MB in Ayla’s IoT Command Center.

1

Users

We resolved an issue with signing in to a newly created account when the primary contact is set to email. The email and username were not syncing and did not update properly.

2

Schedules

We resolved the issue in which all of the schedule settings except the scheduled actions were lost when associating a new template to a device.

3

Data Streaming Service

Datapoint Acknowledgement Events (datapoint_ack) are now supported in Ayla’s Data Streaming Service (DSS). When the device sends a datapoint acknowledgement message, this event is also sent to the DSS streams.

1

Properties

We resolved a file property delivery issue in which the file property was marked as fetched before the file property datapoint was marked complete, and the error logs showed 500 status codes. This was seen when delivering the set_zone property, and when the device was cycling (switching) between two template versions. Click here for more information on File Properties.

2

Data Streaming Service

We resolved an issue in which all datastreams that the user created in Ayla’s Data Streaming Service (DSS) were removed after deleting the OEM user. Only personally identifiable information should be removed upon deleting an OEM user; all of the OEM user’s configurations that affect other users should not be removed.

3

Devices

We resolved an issue in which the devices Search | By Property feature in the Ayla Customer Dashboard was failing with a 401 response. To use this feature, in the dashboard, click Devices in the left navigational panel, click SEARCH DEVICES on the All Devices tab, click the By Properties tab.

1

Command Center

We resolved an API issue when using the OTA Job Details feature (Icc_JobDetails) in Ayla’s IoT Command Center. When creating an OTA job with host_ota for a single or multi-component image, after updating the host_ota action, the property_name either no longer showed as null, or displayed the previous property name instead of the new one.

2

Data Streaming Service

We added a datastream option for datapoint acknowledgements to Ayla’s Data Streaming Service (DSS). This enables you to stream data on acknowledgments that confirm whether or not property values were updated. Click here for the user documentation on this feature.

1

Devices

We resolved the issue in which the local time was not updating properly on some devices after doing a factory reset or when the initial provisioning process failed. With regard to the factory reset, the device did not sync the timezone after 36 hours.

2

Schedules

We resolved the issue in which schedule actions kept duplicating when you cloned a private device template more than two times and then re-associated the second (or subsequent) cloned template to a device. This issue was also occurring on Over-the-Air (OTA) jobs that were using cloned private templates.

3

Feeds

We changed the SQS (Simple Queue Service) configuration to fix the issue in which weather feed properties (e.g. outdoor temperature) were not being updated per their configured data feed update intervals (e.g. 1 hour).

4

Feeds

We fixed an incorrect queue name in the SQS (Simple Queue Service) configuration to resolve the issue in which inconsistent datapoint values were posted for weather feed properties.

5

Feeds

We found and updated an incorrect mapping in the feed-processor code to resolve the issue with missing data for air quality properties (such as Ozone-O3).

1

Notifications
IOS Update

The iOS 6.6.2 release included the following:

• Support for both trigger and rules-based notifications

• iOS 14.2 support
  

2

Local Network Privacy

In the iOS 6.6.2 release, local network privacy does not have an API to check for allowed or denied, which may cause the on-boarding process to fail. Refer to the iOS 14 Privacy Changes document for details.

3

User Interface

In the iOS 6.6.2 release, Ayla Mobile Foundry also includes user interface improvements, such as the ability to add and remove the social login using Foundry.json.

4

Device Onboarding

For iOS 6.6.2, we fixed the issue causing Ayla Mobile Foundry to crash when launching the advance setup on the iPad.

5

Notifications

For the iOS 6.6.2 release, we added rules-based notifications for email, SMS (Short Message Service), and push.

6

Notifications

In the Android 6.6.03 release of the Ayla Software Development Kit (SDK) and Ayla Aura, we deprecated trigger-based notifications for email, SMS (Short Message Service), and push.

7

Device Onboarding

The Android 6.6.03 release provides improvements to the user interface, user experience, and Wi-Fi setup for Ayla Aura, such as a larger tap region for advanced set-up flows and the ability to cancel and close BLE (Bluetooth Low Energy) and Wi-Fi set-up processes.

8

Device Onboarding

For Android 6.6.03, we fixed the issue in which the setup token for Wi-Fi and BLE (Bluetooth Low Energy) was not sent and returned an error.

9

Registration

In the Android 6.6.03 release, AMAP has the following issues:

• The legacy DevKit fails when using the Same LAN registration method.

• The Play Store release is still in review.

1

Data Streaming Service

We resolved the issue in which an error occurred when attempting to edit or view an existing datastream in the Ayla Customer Dashboard and when sending a GET request on an existing datastream.

2

Notifications

We resolved the issue in which multiple device notifications (SMS, push, and email) were sent for a single datapoint event.

3

Gateway Device

We resolved the issue in which the connectivity status of the nodes were incorrectly reported when a gateway device went offline and online. This was occurring when the event_time was the same for both the offline and online status.

4

Device Properties

We resolved the issue in which multiple property values were sent when only changing one device property. When a device property was changed (in the to-device direction), the GET command (GET /devices//commands.xml) showed multiple property datapoints were received.

1

WPA3 Security

In the iOS 6.6.1 and Android 6.6.02 releases, for customers who want to obtain Wi-Fi certification for their devices, we added WPA3 Support and updated Wi-Fi Security type strings to the Ayla Software Development Kit (SDK) and Ayla applications.

2

Local Network Privacy

In the iOS 6.6.1 release, local network privacy does not have an API to check for allowed or denied, which may cause the on-boarding process to fail. Refer to the iOS 14 Privacy Changes document for details.

3

FastTrack
Sepia Framework

In the iOS 6.6.1 release, Ayla Mobile Foundry also includes the following enhancements:

• User interface support for Ayla FastTrack.
  

• Improved Sepia themes support. Sepia is a cross-platform framework for Android and iOS that allows developers to quickly create Ayla IoT mobile applications with very little effort. Sepia themes are used, for example, in configuring colors and fonts for multi-color mode). For more information, click here.

• Build improvements for fastlane, a tool for iOS and Android developers to automate simple tasks like generating screenshots, dealing with provisioning profiles, and releasing your application.

4

Device Onboarding

In the Android 6.6.02 release of Ayla Aura, we improved the user experience for advanced device on-boarding.

5

Device Onboarding

In the Android 6.6.02 release of the Ayla Software Development Kit (SDK) and Ayla Mobile Foundry, we improved unhappy path errors reported during the onboarding process.

6

Registration

In the Android 6.6.02 release, AMAP has the following issues:

• The legacy DevKit fails when using the Same LAN registration method.

• The Play Store release is still in review.

1

Properties

We improved the processing of batch properties (batch_datapoints API) to drive better platform scalability and performance.

1

Data Streaming Service

In a recent update, we implemented a deactivated status to be sent to the Data Streaming Service (DSS) to fix the issue in which nodes were not deactivated or removed after issuing the following:
DELETE /dev/v1/dsns/<gateway_device_dsn>/nodes/<node_dsn>.json
PUT /apiv1/devices/{devId}/cmds/factory_reset

1

OTA

The POST datapoint to oem_host_version API (/dev/v1/dsns/:dsn /properties/oem_host_version/datapoints) is no longer returning a 500 error to gateway devices when you attempt to update a template with new properties (for new features) after OTA (Over-the-Air) updates.

2

OTA

A recent update resolves the issue in which software version events (host_sw_version) and OTA reporting events (for host version updates) were not triggered/updated.

3

Rules

Recent enhancements to Ayla’s Rule Service have greatly reduced latencies and improved delivery speeds of events, for example, when using Ayla DataStream Service. This enables you to react to your fleet’s events quicker than before.

4

Dealers

We resolved the issue in which users were receiving a 406 error after clicking the link in the confirmation email for a new dealer account that was created in the dashboard.

1

Properties

When implementing to-device message properties for the Ayla Portable Agent, the Ayla Cloud apiv1 API no longer returns a 422 error when the size of the message property is larger than 1024 bytes. The maximum size of a message property is 512 KB.

2

Users

End users can sign in to Ayla mobile and web applications using their Apple credentials. This includes the ability to create, update, delete, and manage Apple log-in accounts for your Ayla applications using the Ayla Customer Dashboard. Click here for the user documentation on this new feature.

3

Devices

We fixed the issue in which the Ayla Customer Dashboard was not showing devices shared with the end user.

4

Maps

We fixed the issue with users not being able to see maps in their application after sending the HTTP GET request.

5

Profile

When creating or editing an application in the Ayla Customer Dashboard, you will no longer experience spinning issues while uploading a PEM (Privacy Enhanced Mail) file for the Apple Push Notification Service (APNS). Click here for the steps to create or edit applications in the dashboard.