Skip to main content

2022 Backend Release

1.1.25 (29-Nov-2022)​

Please upgrade the Node Registration module to v11 after upgrading the backend.

  • Bug fixes
    • Fixed the issue of unformatted push notifications due to event_data not being sent in the payload

1.1.24 (07-Nov-2022)​

Please upgrade the Node Registration module to v11 after upgrading the backend.

  • New features
    • Support for MQTT-based OTA to avoid additional TLS connections for HTTPS, thereby optimising RAM usage
    • Node type and model wise node statistics
    • API for the super admin user to get the currently available license quota
    • Provision to send node alerts using node/+/alert
    • Support for an alternate OTA firmware image URL while OTA job creation
  • Bug fixes
    • Allow custom message body irrespective of event data status
    • Fixed verification code not sent for account delete request when message template is updated
    • Fixed node type getting ignored if the tags parameter is provided in the GET admin/nodes API
    • Ignore aggregation interval when raw aggregate is provided (Swagger). Upgrade to the latest version by following these steps.
  • Other changes
    • Removed some unnecessary parameters from the add-on SARs
    • Support for message type and additional information fields in the publish message API
    • Configure a common message title for all the supported event topics (Swagger)
    • Formatted the ESP API Rate Limiter and ESP Device Defender violation emails. Upgrade to the latest version by following these steps for ESP API Rate Limiter and ESP Device Defender respectively.
Important Updates:
  • OTA support for DigiCert S3 server certificates has been removed. OTA won't work if you had raised such a support case.
    - We have automated regrouping for Dynamic groups. The ability to manually do this will be unfunctional soon in this API.

1.1.23 (03-Oct-2022)​

Please upgrade the Node Registration module to v11 after upgrading the backend.

  • Bug fixes
    • Fixed node removed event notification getting triggered twice
    • Corrected missing automation triggers in the Get API when pagination parameters are given (Swagger)
    • Fixed the issue of node ota status events order getting swapped when received in quick succession
    • Fixed the issue of a node getting old OTA jobs after the latest one has succeeded or been rejected
    • Fixed RainMaker clean-up issues in case of non-empty S3 buckets
  • Other changes
    • Made all S3 objects private in RainMaker

1.1.22 (23-Aug-2022)​

Please upgrade the Node Registration module to v11 after upgrading the backend.

  • New features
    • Support to capture total MQTT messages in the Stats Service. Upgrade/Deploy the add-on service by following these steps. (Swagger)
    • Added support to upload pre-provisioned module's csv in node registration RainMaker Admin CLI
  • Bug fixes
    • Fixed the registered nodes, users with nodes and without nodes counts in the Stats Service
  • Other changes
    • Command/Response Feature - Handling data size greater than 255 bytes
    • Removed public access to all RainMaker S3 buckets
    • Added validation to check if the email ID is valid while deploying RainMaker

1.1.21 (26-Jul-2022)​

Please upgrade the Node Registration module to v10 after upgrading the backend.

  • New features
    • Added support for generating the list of existing node tags (Swagger)
    • Added support for capturing API count metrics in the Stats service. Deploy the add-on service by following these steps. (Swagger)
  • Bug fixes
    • Fixed the timeout for deleting admin node groups when it had a large number of nodes
    • Removed the quota field and added validation to the status parameter in the GET admin nodes' API
    • Handled leading and trailing spaces in the change password APIs
    • Fixed pagination and response in the GET admin users' API
  • Other changes
    • Added support for Alpha-numeric strings in tags

1.1.20 (05-Jul-2022)​

Please upgrade the Node Registration module to v10 after upgrading the backend.

  • Bug fixes
    • Added maximum character limit to the message body and title in push notifications
    • Added validation to the group name in the Node Group creation APIs
    • Added validation of request payload in case of WebHooks configuration
    • Fixed an issue in Common custom data APIs
    • Fixed the total count related issue in the get OTA Image API
    • Fixed the response payload in the Admin User get API
    • Fixed issues in RainMaker deployment related to CloudWatch Log groups

1.1.19 (22-Jun-2022)​

Please upgrade the Node Registration module to v10 after upgrading the backend.

  • New features
    • Added Apple push notifications' certificate expiry detection
    • PUT API for platform applications, used in configuring push notifications (Swagger)
  • Bug fixes
    • Added validation for node tag parameters
    • Fixed event-mapping removal on user deletion
  • Other changes
    • Optimised system-level WebHook filters
    • Time Series: Added support for back-dated data
    • Added support to view node tags for the associated nodes (Swagger)

1.1.18 (09-Jun-2022)​

Please upgrade the Node Registration module to v10 after upgrading the backend.

  • New features
    • Customisation of E-mail templates (Swagger)
  • Bug fixes
    • Fixed issues in the command response feature
    • Fixed an issue related to weekly timezone aggregation
    • Fixed issues related to updating and deleting node tags
  • Other changes
    • Modified the get automation triggers API to allow viewing the shared nodes
    • Made the verification code length consistent across RainMaker for various use cases like user Sign-up, forgot password, etc.
    • Added a limit for the number of invalid attempts for the user delete operation

1.1.17 (24-May-2022)​

Please upgrade the Node Registration module to v10 after upgrading the backend.
  • New features
    • Command Response (Swagger)
    • API to get your RainMaker deployment details (Swagger)
    • API to get the Android and iOS app build configurations (Swagger)
  • Bug fixes
    • Fixed issues in RainMaker upgrades related to CloudWatch logs
    • Fixed the issue in data ingestion for the Time Series data service. (Upgrade to the latest version by following these steps)
  • Other changes
    • Optimised WebHook filters to reduce costs
    • Added support for creating multiple Google and Apple push notification platforms
    • Enhanced Role-based access control: Multiple Admin users can access the nodes
    • Modified the approach for the generation of OTA Image URL, to support DigiCert as well as Amazon CA
RainMaker OTA server verification issue

What is this issue?​

Some time back AWS migrated their default TLS certificates from DigiCert to Amazon Trust Services. Since older RainMaker firmware used the Digicert certificate for OTA server validation, it would not work anymore, causing failures in OTA.

How do I know if I am affected?​

The certificates in the ESP RainMaker repository were updated in this commit on 1-Feb-2022. If your project is based on this or a later commit and uses the default certificate like the below snippet, then you would not be affected.

esp_rmaker_ota_config_t ota_config = {
.server_cert = ESP_RMAKER_OTA_DEFAULT_SERVER_CERT,
};

If you are using the older certificate, you will get the below error during OTA:

E (57062) esp-tls-mbedtls: mbedtls_ssl_handshake returned -0x2700
I (57062) esp-tls-mbedtls: Failed to verify peer certificate!
I (57062) esp-tls-mbedtls: verification info: ! The certificate is not correctly signed by the trusted CA

This is an indication that you will have to request AWS to temporarily change your server's certificate to support both, the Digicert as well Amazon Trust Services' certificates. The steps for that are given below. Note that this will work only for RainMaker backend release 1.1.17 and beyond, since, it also requires changes in the URL generation logic for OTA.

Raising support ticket with AWS​

Follow these steps to create a support case. Add the below text as the case description:

We have deployed the RainMaker IoT Platform in our AWS account. RainMaker uses S3 buckets to store the Firmware images required for the Over the Air Upgrades (OTA). We are aware that AWS had started migrating the S3 server certificates from Digicert to Amazon Trust Services and we have added the new certificate in our SDK. However, there already are devices in the field that had only the old certificate. If they try to do an OTA upgrade, it fails because of server validation failure. So can you enable the DigiCert certificate for the below S3 bucket - esp-rainmaker-ota-< AWS_Account_Number >.s3.us-east-1.amazonaws.com?

How to ensure that this never occurs again?​

On the firmware side, instead of using just one server certificate, we now support certificate bundles, which have the certificates of all standard certifying authorities. You can find the changes in this commit.

1.1.16 (10-May-2022)​

Please upgrade the Node Registration module to v9 after upgrading the backend.

  • Support for delayed and rejected statuses in OTA jobs
  • Changes to the common custom data APIs (Swagger)
  • Allow end-users to add tags for the nodes associated with them (Swagger)
  • API to fetch SES delivery status of Email from Database (Swagger)
  • Fixing a defect in the user node association process while adding tags
  • User node association - form tags from the user's custom data (all esp. keys under esp.location) (Swagger)
  • Fixing a defect in the Time Series data ingestion issue. Upgrade to the latest version by following these steps.
  • Enhancements to the bulk node generation API to return node group details

1.1.15 (21-Apr-2022)​

Please upgrade the Node Registration module to v9 after upgrading the backend.

  • Support for Time Zone parameter in Time Series DB Service (Swagger). Upgrade to the latest version by following these steps.
  • Optimising the AWS IoT cost by supporting basic ingest for the MQTT topics
  • Support for Alexa Asynchronous communication

1.1.13 and 1.1.14 (08-Apr-2022)​

Please upgrade the Node Registration module to v9 after upgrading the backend.

  • Fixes to the Role-Based Access Control (RBAC), for the Push Notification APIs
  • Fixes in the user custom data APIs
  • Push notification support for Automation triggers
  • Support for providing node tags and additional metadata during user-node association
  • Automatic addition to node group based on type, model, fw_version, at the time of node registration
  • Support to allow other Admin users to view/manage nodes registered by other Admin users, using RBAC
  • Sorting of OTA jobs based on timestamps
  • WebHook support when new tags are added to nodes
  • Enhancements to the stats service to address delete user event

1.1.12 (08-Mar-2022)​

Please upgrade the Node Registration module to v9 after upgrading the backend.
  • Enhancement to the node search API, based on tags and RBAC policies
  • Support for creating Role-Based Access Control policies based on tag filters

1.1.11 (25-Feb-2022)​

Please upgrade the Node Registration module to v8 after upgrading the backend.

  • Role-Based Access Control (RBAC) is introduced in this release for the admin APIs.
    • APIs to manage roles and policies for access control of RainMaker APIs
    • Added default policies applicable to RBAC
    • APIs to create additional users with admin rights
  • Added support for common custom data (Swagger API link)
  • Enhancement to support maximum OTA image size to 16 MB (Swagger API link)

1.1.10 (09-Feb-2022)​

Please upgrade the Node Registration module to v8 after upgrading the backend.

  • Added support for node tags and filtering based on these tags (Swagger API link)
  • Generate WebHook events when a new admin user is created and new nodes are registered
  • Time Series Service: Added a query parameter aggregation_interval. Currently, both time_interval and aggregation_interval query parameters are supported, but it is recommended to use aggregation_interval (Swagger API link) Upgrade to the latest version by following these steps.

1.1.9 (28-Jan-2022)​

  • Introduced new APIs to support uploading larger OTA Images, up to 16MB.
  • Added support for creating Node groups during node Registration.
  • Added support for sorting OTA Images by timestamp.
  • Optimisations for OTA status summary API.
  • Added support for Admin users to find nodes associated with users based on user_id or user_name.
  • Fixed defects in Node automation Trigger service.
  • Added support to persist the metadata received from the sharing request for the device groups.
  • Enhancements to the error message for Change password and Forgot password APIs.

On this page