1

Groups and Scenes

In the Ayla Software Development Kit (SDK), we added support for the new collections_2 API that supports different time zones, including Daylight Saving Time changes, and ensures that schedules trigger accordingly.

2

Logs

We added support for an anonymized debug log manager in the Ayla Software Development Kit (SDK); click here for more information on this feature.

3

Metrics

In the Ayla Software Development (SDK), we improved the ability to upload metrics using a serial versus concurrent queue policy. This helps to ensure metrics arrive to the Ayla Log Service in an ordered sequence.

4

Central Processing Unit

In this release of Ayla Aura, Foundry, and FastTrack, we added build support for the Apple M1 architecture.

5

Sign In

For Ayla Aura, Foundry, and FastTrack, we upgraded the Google Sign-In iOS Software Development Kit (SDK) to version 6.1.0.

6

User Interface

In Ayla Aura, we made the following improvements to the user interface:

• The Shares screen has a cleaner look and provides more details in the list of Owned Shares and Received Shares.

• In the header of the Device detail screen, we now specify whether the Connection Status (i.e., Online) of the App is to either to the cloud (Ayla Device Service) or the device (using LAN or BLE connect). For example, the Connection Status may show **Online (App -> Device via LAN)**.

7

User Interface

For Ayla Aura, we resolved issues with the following on the user interface:

• The Reset button on the password screen

• The ability to select a date while sharing a device on the Device Share screen

• The product names displayed on the Devices screen for the Device List

• Zeroing the seconds in the time picker for schedules in the edit view of the Schedule screen

8

Onboarding

In Ayla Aura, we resolved the issue with the discovery of the Phone as a Gateway (PaaG) thermostat devices during the onboarding process.

9

Onboarding

For Ayla Foundry and FastTrack, we improved location accuracy for the onboarding process.

10

User Interface

In Ayla FastTrack, we resolved the issue with button constraints for Sunrise/Sunset scheduling options on small screens.

11

Geofencing

For Ayla Foundry, we made the following improvements to Geofencing:

• We added unit tests for Geofence group triggers.

• The ability to check for location access is always available for the Geofence location.

• The Geofence action screen refreshes after a new action is created.

12

Sign In

For Ayla Foundry, we resolved an issue in which the Sign In screen crashed when users clicked items in the Drawers menu.

13

Notifications

In Ayla Foundry and FastTrack, we resolved an issue with the method access specifier for Notification methods in the SepiaAppDelete class.

14

Login

For Ayla Foundry, we improved the Face ID feature for logging in.

15

Bluetooth Low Energy (BLE)

When registering the demo board using Bluetooth Low Energy (BLE), you can now override the OEM model and subdevices.

16

Devices

In Ayla FastTrack, we added support for the following device types:

• Mono bulbs

• LED light strips

• Power outlets

1

Groups and Scenes

In the Ayla Software Development Kit (SDK), we added new test units and support for the new collections_2 API that supports different time zones, including Daylight Saving Time changes, and ensures that schedules trigger accordingly.

2

Logs

We added support for an anonymized debug log manager in the Ayla Software Development Kit (SDK); click here for more information on this feature.

3

Security

For the Ayla Software Development Kit (SDK), we removed the WRITE_EXTERNAL_STORAGE manifest permission; it has become a no-op and is often flagged by security checks for no reason.

4

Warnings

For Ayla Aura and the Software Development Kit (SDK), we resolved miscellaneous Android Studio static analysis issues.

5

Bluetooth Low Energy (BLE)

For the Ayla Software Development Kit (SDK), we resolved an issue with BleStartSession() crashes by adding the isBluetoothEnabled() check.

6

Facebook OAuth

We added the ability to save Facebook OAuth credentials in Ayla Aura by adding CachedAuthProvider() to fbNewAuthSignIn().

7

Login

In Ayla Aura, we added navigateSignIn() after handleSignOut() to ensure that the Login screen displays after logging off.

8

User Interface

We improved the look of the Shares screen, which includes providing more details in the list of Owned Shares and Received Shares.

9

Dynamic Linking in Emails

For Ayla Aura, we resolved an issue with linking to a "no active session."

10

OAuth Login

In Ayla Aura, we added an optional OAuth login callback for Google, Facebook, Apple, and TenCent.

11

Geofencing

For Ayla Foundry, we made the following enhancements to Geofencing:

• We added a new SepiaGeoRestartReceiver to register saved Android geofences.

• We upgraded to the latest Android Geofence API versions and APIs.

• We added ACCESS_FINE_LOCATION to the manifest, which allows the operating system to provide more accurate location details to the Android geofence class.

• We improved the permissions for checking and handling.

12

API

We added the setTitle() API to Ayla Foundry and FastTrack, which is used to set screen titles.

13

Onboarding

In Ayla Foundry and FastTrack, we added a new style to the existing setup wizards that support the device onboarding flow. The new style is setup wizard #2 with helper methods. This replaces the existing Add Device onboarding screen with a new screen design.

14

Sepia Framework

For Ayla Foundry and FastTrack, we added the following:

• A new SepiaDeviceHelper that returns a SepiaDevice for given AylaDevice.

• The ability to load a blank fragment in a sepiascreen.

15

Notifications

For Ayla Foundry and FastTrack, we added tag substitution for product device names in push notifications.

16

User Interface

For Ayla Foundry and FastTrack, we improved theming for radio buttons and updated the Spanish translations.

17

Logs

We cleaned up the logs in Ayla Foundry and FastTrack.

18

Devices

In Ayla FastTrack, we added support for the following device types:

• Mono bulbs

• LED light strips

• Power outlets

19

Dynamic Linking in Emails

For Ayla FastTrack, we resolved an issue in which an “invalid confirmation token” error occurred when the dynamic linking onboarding flow was not used.

20

Security

For Ayla FastTrack, we removed WRITE_CONTACTS and READ_CONTACTS permissions from the manifest; neither is being used.

21

User Interface

For Ayla FastTrack, we resolved an issue with restoring the color bulb screen.

22

User Interface

In Ayla FastTrack, we improved color handling on the backscreen and changed "disabledButtonBackgroundColor" to "inactiveColorDarker."

1

ESP32-C3

We added support for ESPRESSIF’s ESP32-C3. Click here for a description of this microcontroller unit (MCU).

2

Properties

We added support for datapoint acknowledgements (acks). This allows the host app to respond to new property values, confirming receipt and indicating any issues, such as out of range or invalid.

3

Properties

We added support for datapoint metadata. This allows additional data to be supplied to or from the device with each datapoint. The metadata consists of up to 4 flexible key/value strings.

4

Device Property Base Type

We added support for message properties used when sending large JSON, binary, or text datapoints to and from the device. Message properties can handle a datapoint size of 512 KB.

5

LAN Events

We added a new LAN event called PME_LAN_STATE_CHANGE that can communicate with any event handler to indicate whether the LAN session is active or inactive and whether the key-exchange has failed.

6

LAN Connection

We optimized the LAN connection to detect a wrong connection earlier. With this improvement, if the mobile app tries to connect to a device that may have had the same IP address in the past, the error is detected at the initial HTTP transaction, rather than when the key exchange fails.

7

Clock Source

We resolved an issue in which the clock_source variable was not being updated if the time last used to set the clock was around the same as the new time received from another source, making the time provided from the clock_source variable unreliable.

8

Security

With this release, we only support Transport Layer Security (TLS) 1.2 to ensure the best solution to security threats. Please note that the host app must be configured to disable TLS 1.0 and TLS 1.1, and to check for certificate expiration. Otherwise, the build will fail.

9

Evaluation Board

For ESPRESSIF’s ESP32-C3-Mini evaluation board or ESP32-C3-WROOM-02 evaluation board, we added support for the WS2812B LEDs, which enable communication using a one-wire interface. There is a multicolor LED on the board, which the demo can use instead of relying on external LEDs that are needed to connect.

10

Security

We resolved an issue related to ensuring that sensitive data is not logged to the debug/console port.

11

Client Health Check

We resolved an issue in which a warning and then a Watchdog abort occurred because the ESP32 Client Health Check was not enabled by default in the demo. The Client Health Check feature provides auto-recovery, which causes the system to reboot if the client cannot connect to the cloud or hangs for any reason.

12

Debugging

We added the client CLI command for debugging purposes.

13

CLI Command

We added the erase option to the core CLI command to provide the ability to erase core dumps.

14

Logs

We restricted the level of log messages coming from the ESP-IDF Wi-Fi subsystem to only messages of warning level or above.

15

BLE Local Control

When Bluetooth Low Energy (BLE) Local Control is disabled for the device, the Ayla device agent will shutdown the Bluetooth (BT) controller to free up memory. If BLE Local Control is later enabled for the device via the cloud, the device must be reset to restart the BT controller.

16

ESP-IDF

We updated ESP-IDF to version 4.3.2. Please refer to Espressif’s site for the fixes in this version.

17

Demo App

We resolved an issue in which the demo app build from the ESP32 binary embedded agent release failed to link due to missing multicast Domain Name System (mDNS) components.

18

Security

To ensure that expiration dates for Transport Layer Security (TLS) certificates are checked, we now require that the build configuration option called MBEDTLS_HAVE_DATE_TIME is set in all Software Development Kit configurations (sdkconfigs).

19

CLI

We resolved an issue with software-initiated reboots (i.e., after a crash or factory reset), in which the Command Line Interface (CLI) reset was intermittently resulting in errors.

20

Clock Source

We resolved an issue with the clock in which the time was not accurate after a software reset. With this fix, you no longer need to use the previous workaround to sync the real-time clock to the high-resolution timer before software resets.

21

BLE

We resolved an issue in which when the BLE Connect setting was disabled, crashes occurred after a factory reset if Bluetooth Low Energy (BLE) was executed during the Wi-Fi setup.

22

BLE Local Control

We resolved an issue in which the Bluetooth Low Energy (BLE) Local Control feature was not working because the pairing/bonding step did not complete.

23

Connectivity

We resolved an issue in which the ESP32 C3 agent failed to establish a reliable LAN connection with Ayla Aura.

24

Logs

We resolved an issue with core-dump summaries that save log snapshots, in which it seemed like multiple log snapshots could not be recorded.

25

Clock Source

We resolved an issue in which the clock was hours ahead of the actual time after entering the reset command or issuing a factory reset.

1

BLE Local Control

For the Ayla Software Development Kit (SDK), Aura, and Foundry, we added the new BLE Local Control platform feature, which includes a new AylaDevice listener called didUpdateBleState:error. BLE Local Control enables you to control and monitor devices using your mobile app over a Bluetooth Low Energy (BLE) connection. For configuration details, please refer to the App Note.

2

Messages

We added support for the V2 Messaging protocol in the Ayla Software Development Kit (SDK).

3

Connectivity

To improve AylaConnectivity in the Ayla Software Development Kit (SDK), we replaced AFNetworkReachabilityManager with NWPathMonitor (NetworkPathMonitor).

4

Caching

We improved caching in the Ayla Software Development Kit (SDK) as follows:

• We now use NSArchiving and NSUnArchiving APIs.

• We migrated NSCoding to NSSecureCoding.

5

Onboarding

For the Ayla Software Development Kit (SDK), we did the following:

• Improved refreshing authToken when network connectivity fluctuates.

• Improved Wi-Fi onboarding to address devices returning a 400 error (bad request).

6

Logging

We made the following improvements related to logging in the Ayla Software Development Kit (SDK):

• Added the ability to upload metric logs serially in a background queue to avoid 429 errors (which occur when the default ip_address rate limit is triggered).

• Improved the debug console and logging information to aid in troubleshooting.

7

User Interface
Groups and Scenes
Bluetooth Low Energy (BLE) Local Control

In the Ayla Software Development Kit (SDK):

• NSLocalizedDescriptionKey is now used to describe NSError instead of a custom key.

• We resolved a sharing crash in Groups and Scenes that was occuring when there was no user_profile.

• We resolved an issue in which fetchProperties from Local Control mode was not updating the user interface.

8

Onboarding

In Ayla Aura, Foundry, and FastTrack, we improved the process of creating user accounts with our new Dynamic Linking in Emails feature. Please refer to the App Note for configuration information on this new feature.

9

User Interface

We improved the ability to create and view datapoints with metadata on Ayla Aura’s user interface.

10

Caching

For Ayla Aura, Foundry, and FastTrack, we updated Archiver class methods to improve caching.

11

Rules

In Ayla Aura, we implemented Rules support to use SwiftUI (a next generation user interface) versus the existing Storyboard.

12

Properties

In Ayla Aura, we added String, Integer, Decimal, and Float base types to manage device properties for Ayla DevKits.

13

Test Runner

In Ayla Aura, we added Bluetooth Low Energy (BLE) Local Control mode to support Aura Test Runner.

14

Logging

In Ayla Aura, we added a new helper method called AylaLogManager.getAppInfo, which assists in creating basic info (i.e., app version, sdk version, device model, country, build number, etc.) to add in log files or in the email body when sending email logs.

15

User Interface

In Ayla Aura, we now display the device name in the About screen using a Software Development Kit utility method.

16

Over-the-Air (OTA) Jobs

We resolved an issue for Ayla Aura in which an error message displayed when checking OTA jobs if there was no Internet connectivity.

17

API

In Ayla Foundry and FastTrack, we resolved static analysis issues and updated deprecated APIs as well as their dependencies.

18

User Interface

In Ayla Foundry, we now display the title of the back button for all screens, and display the connection status in the Device Details screen for device status updates.

19

Rules

In Ayla FastTrack, we added a new Rules-based property notification for managing properties.

1

BLE Local Control

For the Ayla Software Development Kit (SDK) and Aura, we added the new BLE Local Control platform feature, which includes a new AylaDevice listener called deviceBleStateChanged. BLE Local Control enables you to control and monitor devices using your mobile app over a Bluetooth Low Energy (BLE) connection. For configuration details, please refer to the App Note.

2

Onboarding

In Ayla Aura, Foundry, and FastTrack, we improved the process of creating user accounts with our new Dynamic Linking in Emails feature. Please refer to the App Note for configuration information on this new feature.

3

Onboarding

In the Ayla Software Development Kit (SDK), Aura, Foundry, and FastTrack, we improved the on-boarding experience when auto-connect is disabled in Wi-Fi network settings.

4

Phone as a Gateway (PaaG)

For the Ayla Software Development Kit (SDK), Aura, Foundry, and FastTrack, PaaG support is now bifurcated between the application and SDK layers, making PaaG applications easier to create and support.

5

HTTP Server

In the Ayla Software Development Kit (SDK), we optimized the behavior of the HTTP server, as follows:

• HTTPd starts upon a network change or when the Local Control LAN mode is established.

• HTTPd pauses when the Local Control LAN mode is not active.

6

Onboarding

For the Ayla Software Development Kit (SDK), we removed the authToken from the refresh token request for API consistency.

7

Metrics

For the Ayla Software Development Kit (SDK), we optimized the process of creating and uploading metrics as follows:

• Included support for complex primitives.

• Added a sampling ratio.

8

Logging

For Ayla Aura, we added the ability to retrieve and email device logs using Bluetooth Low Energy (BLE).

9

Onboarding

For the Ayla Software Development Kit (SDK) and Aura, we removed the sessionManager dependency during device onboarding to support those who do not have users on their tenancy.

10

Facebook OAuth

We updated the Facebook OAuth documentation for Ayla Aura. Click here for this document.

11

Bluetooth Low Energy (BLE) / Wi-Fi

In Ayla Aura and FastTrack, we resolved an issue with the BLE/Wi-Fi cancellation process.

12

Devices

In Ayla Aura, we now display the set-up token when adding a device.

13

Devices

For Ayla Aura, we added the ability to override the connection priority for all devices in Aylanetworks.settings.

14

Connectivity

For Ayla Aura, we replaced AylaConnectivity listener in DevKitSetupFragment with the shared instance listener to increase reliability.

15

Notifications

For Ayla Foundry, we added support for FastTrack notifications.

16

Connectivity

In Ayla Foundry, we improved the retrieval and secure storage of the Firebase Cloud Messaging (FCM) token.

17

Phone as a Gateway (PaaG)

For Ayla Foundry, we removed Schedules from the PaaG Device Details menu.

18

Properties

In Ayla FastTrack, we added a new device property notifications feature.

19

Connectivity

In Ayla Foundry, we improved the ability to check permissions to access the precise location for Android 12.

20

Devices

In Ayla FastTrack, we resolved an issue with a device sharing crash by checking for null devices.

1

Authorization

We resolved a corner-case issue with the refresh_token API method in which a 401 error occurred if the Authorization header had an expired auth_token.

1

Security

We made all the necessary upgrades and changes for the Log4j security vulnerability.

2

Ayla Notification Service

We added the ability to debug specific devices within the Ayla Notification Service (ANS) instance, without requiring an ANS restart.

3

Groups and Scenes

We added a system to monitor whether the Scenes triggered as scheduled, and to obtain additional performance information (i.e., successes, failures, and latency alerts).

1

ESP-IDF

We added support for the 4.3.1 version of the Espressif IoT Development Framework (ESP-IDF) and its latest toolchain. This requires a new build procedure as described in the ESP-IDF documentation.

2

Wi-Fi

We included all Wi-Fi regions supported in Espressif ESP-IDF 4.3.1. Refer to Espressif’s documentation for the list of supported regions.

3

Onboarding

We added support for the new PUT oem_info API, which provides better feedback on template association and registration type for Wi-Fi setup.

4

File Properties

We resolved an issue in which after downloading a file property from the Cloud, the LAN code tried to echo this to the LAN client and was receiving errors when formatting the value.

1

Command Center

In keeping with a simple, efficient user experience, we updated the edit workflow for Set Property jobs to be consistent with the other job types in Ayla’s IoT Command Center.

2

Groups and Scenes

We resolved a corner-case issue in which some actions in the Scene were not triggering on time after the Daylight Saving Time change.

3

Command Center

We resolved an issue in which the Over-the-Air (OTA) commands sent to the device were not deleted after the device was marked as “Failed” and in the queued state for more than 7 days.

4

Groups and Scenes

We resolved a corner-case issue with a connection error that occurred when there were too many concurrent connections.

5

Datapoint Service

We resolved a slow performance issue by moving to a new message datapoint table with a Time-to-Live (TTL) configuration.

1

Production Agent

We are pleased to announce the Ayla Production Agent for the ESP32-C3-MINI-1 module. Contact Ayla Customer Success to obtain a Development Kit with this production agent. For more information on the ESP32-C3-MINI-1 module, click here to review Espressif Systems’ datasheet.

1

Device Properties

We resolved a corner-case issue in which the Cloud was not reflecting the property change from the device when echo was set to true (echo=true) and consequently kept returning the previous property value.

1

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.”

1

API

We upgraded to API level 31 for Android 12 in Ayla Aura, Foundry, FastTrack, and the Software Development Kit (SDK), which included upgrading minSdkVersion from API level 25 to 27 (Android 7.1x to Android 8.1). Following are examples of other improvements that were part of this upgrade.

For the Ayla SDK, we added:

• Permissions for BLUETOOTH_SCAN and BLUETOOTH_CONNECT.

• Flags for PendingIntent MUTALBLE and IMMUTABLE.

For Ayla Aura, we improved the on-boarding flow to support the new permissions requirements.

2

Rules

In the Ayla Software Development Kit (SDK), we added support for batch rules.

3

Rules

In the Ayla Software Development Kit (SDK), we added helper methods for rules-based notifications, and unit tests for the helper methods. These rules-based notification helper methods facilitate the following, for example:

• Fetch rules by DSN (Device Serial Number).

• Provide push notification support for new Android devices.

• Delete orphaned actions.

• Delete orphaned destinations.

4

Utils

In the Ayla Software Development Kit (SDK), we added the AylaStringUtils helper class, which is used to anonymize AylaLog instances. Refer to the AylaStringsUtil - Anonymize.pdf in the AylaSDK/doc folder.

5

Facebook OAuth

In Ayla Aura, Foundry, FastTrack, and the Software Development Kit (SDK), we resolved the Android issue with logging in to Ayla Aura and via WebView using Facebook credentials. This was the known issue in the 6.7.02 release for Android, which was published the week of September 27, 2021.

For details during migration, refer to [the Facebook Authentication on Android documentation in Aura/doc](https://github.com/AylaNetworks/Android_Aura_Public/tree/master/doc).

6

Wi-Fi Scanning

In the Ayla Software Development Kit (SDK), we resolved the issue with .auraconfig default initialization that was causing Wi-Fi scanning issues.

7

Utils

In the Ayla Software Development Kit (SDK), we added utils.CryptoUtils for encoding and decoding strings to shared preferences. We also provided unit tests for this new CryptoUtils class.

8

OTA

Ayla Aura no longer checks for OTA updates when the user does not have registered devices.

9

Test Runner

In Ayla Aura, we added a new feature to Aura Test Runner, which when a property is marked as “Acknowledged,” provides e2e latency statistics for the complete datapoint flow (that is, from the mobile to the Cloud to the device and this same flow back to the mobile).

10

Geofencing

For Ayla Foundry, we removed the EVB (evaluation board) only restriction on geofencing support, and we improved the handling of permissions for background location access.

11

User Interface

For Ayla Foundry and FastTrack, we improved toolbar theming, and the support for the dark mode user interface (UI) theme.

12

Sepia Framework

In Ayla Foundry and FastTrack, we resolved the issue with the version code that was returned for the Sepia framework.

13

Login

In Ayla FastTrack, we improved the sign-in flow so that the bottom toolbar is always shown.

14

User Interface

In Ayla FastTrack, we optimized the color picker to provide a faster response for users.

15

Onboarding

In Ayla FastTrack, we improved the Ayla DevKit on-boarding and display support.

16

Security

In Ayla FastTrack, we encrypted the optional storage of Wi-Fi passwords to local preferences using aSDK.utils.CryptoUtils.

17

Rules

In Ayla Foundry and FastTrack, we resolved an issue with crashes when creating rules.

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 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 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 the Ayla Software Development Kit (SDK), the AppBackground and AppTerminated metric types are now part of metric sample ratio.

4

Rules

In the Ayla Software Development Kit (SDK), we added helper methods for rules-based notifications to facilitate the following:

• Fetch rules by DSN.

• Push notification support for new iOS devices.

• Delete orphaned actions.

• Delete orphaned destinations.

5

Rules

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

6

Library

In 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 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 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 Ayla Aura, we now use the UIDevice.getModelName() method to get the iOS device name instead of getDeviceModel().

10

User Interface

In 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 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 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

Facebook OAuth

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