Minor 2
New Features to Dynamic Dashboard
- Optimize the Dynamic dashboard by doing structural changes to make it faster to load
- Added new widget to dynamic dashboard to show latest value of device sensor
- Allows user to share the dynamic dashboard, this will allow end user to view dashboard without even login into platform, user without platform account can able to see the dashboard
Support New Device Types
- Azure Edge Device: Platform now allows user to create Azure Edge Device, with future update it will allow to add custom modules and routes
- Binary Data Device: Platform is now capable to parse binary data and extract valid information defined in device template and do further process for rule engine and store in big data store
- Low Bandwidth Device: Platform is now allows device to send minimal information in telemetry by sending simple string. Data will be extracted information defined in device template and do further process for rule engine and store in big data store
- Unassociated Device: Platform is now allows device to be created without template. This will help on-boarding devices like Sphere which are using Device Provision Service to get it provisioned and created. However device will not be useful until valid Template is associated with device. You can associate template to single device or multiple devices at a same time
Capture Device Telemetry Size
Platform will capture the device telemetry message size. This feature will be available on demand. The telemetry message size consumption will be shown in dashboard widget.
Snooze Rule Once Triggered
Platform will now provide to snooze the rule once its triggered on device. Snooze time will 1, 2, 5, 10, 15, 20 and 30 mins. If rule triggered in the configured snooze time then rule wont be evaluated again.
Integration of Azure DPS
Platform is globally enabled for now Azure Device Provisional Service enabled. DPS can be applied to tenant and added required information in the configuration section of company. With DPS integration now device which directly get acquired like Sphere Device, TPM devices… Specifically Sphere device on-boarding on scale will be feasible now. All these device will be created/registered without template. In later stage template association can be done on scale for device to use end to end functionality of platform.
Platform Minor Enhancements
- Provided ability to configure TO and From email address and enable BCC feature of Email Client
- Telemetry API will now include the child device data in historical API
- Removed device type drop-down form the Batch Import
- Command Execute API returns batch guid to pull all batch commands
Issue Fixes
- Password fields was missing on device connection information for Key base authentication type
- Fixed announcement display issue after changing expiry date
- Fixed Gauge chart to show last value when its get load rather to show 0
- Simulator stop working on second attempt
- Notification on UI was getting display twice for some of the notifications
- Device twin desired property was not getting updated
- TPM device was not getting acquired once deleted form portal
- UI keeps showing connection lost toast notification frequently
- While editing dynamic dashboard some of the widget where not getting loaded
Minor 1
Earlier, users were not able to add custom properties to the company. Now, you can add custom properties to the company. These custom properties are available to solutions built on top of IoTConnect using a data sync feature for the system integrator.
Solution Template
The solution integrator can now create a template that will be automatically shared with the company as a read-only copy while creating the solution. Though the company cannot make any changes to this template, they can use it to create new devices.
Enhanced the email provider of the platform to support the SMTP server to send emails.
Notification on device disconnection
New rule has been added which will allows you to receive notification if device get disconnected. It will allow you to define audience based on time frame, maximum three time frame can be defined for this notification.
Performance & Improvements
We made some performance improvements to provide a seamless user experience and to upgrade the IoTConnect capabilities:
- Device Twin update process
- Process of updating the latest data value of the device
- Dynamic Dashboard widget loading improvement
- Various optimizations have been made to minimize minimum response time to APIs and make them error-free. We have also made some structural changes to support scalability
- We have added more details on request and response objects in the API documentation to help system integrators build solutions
- Device OTA list will now automatically refresh if there is an OTA update form device
- Databases have merged to improve performance and avoid cross-database queries
UI Enhancements
- Added user-friendly messages on the portal to data export. Minor design changes have also been made to add more information to export functionality
- Enhanced quota widget to provide clear information on subscription plan expiry or auto-renewal. We also added a feature to show the device message size
- Data ingestion configuration is now only supported for Key authentication type
- Removed support of SignalR and MQTT form rule notification type. However, we will be adding these features shortly
- Removed frequent MQTT connection lost messages and made it auto-connect
Issue Fixes
- Restrict Twin property to be only added and deleted, update functionality has been removed
- OTA command was not considered in device metering
- The platform was showing MQTT connection details for the released gateway device as well
- Password update was not kicking off logged in user
- The platform was taking invalid/non-existing announcements for getting details
- Fixed design issues in the dynamic dashboard
- Twin update was not working as expected for sphere devices
- Device SDK for JAVA was not storing data in offline storage
- Quick template creation form solution API was missing twin, command and edge feature configurations
- Firmware upgrade was not saving description in the database