Minor 2
Audit Logs
Platform provides you a single interface to view all errors or issues generated by device message. You can view invalid device to cloud messages or invalid twin update or OTA Command acknowledgement and many more. This will help you identifying the root cause and help you to fix the issue. This feature is based on Role. User having access to Audit Log can only access/view this feature.
SignalR for Real Time Refreshing data
We are moving from RabbitMQ to SignalR Gradually and as a first step we have replaced RabitMQ with SignalR to show alerts and auto-refresh contents. RabbitMQ support is still there for Solutions but we will replace it with SignalR soon. Service Integrator(s) who are currently using RabbitMQ have to migrate to SignalR.
Dynamic Dashboard
Provided seamless interface to manage your dashboard. You can use default dashboard of IoTConnect (read only) or you can create your own dashboard and use as your primary one. Introduced a feature where user can import/export dashboard along with sharing a dashboard. Dashboard can be created as private or shared among user’s entity. Added restriction to update dashboard of user’s entity. One can not update dashboard of other entity.
Widget Timeframe
Modified time frame of D2C, Command, Twin, Rule and Notification Widget and added new Hourly timeframe. It will work like, Hourly (last 24 hours), Daily (last days), Weekly (last 7 weeks) and Monthly (last 3 months)
Enabled Push for Edge & Gateway Device data to PowerBI Dashboard
Enhanced the PowerBI Push to support edge device data and gateway device data, you can now build powerful dashboard on your Edge and Gateway devices
Support Ticket enhancements
Support ticket is the way of sharing your concerns, bug, making suggestion etc. We have added couple of new features in support ticket modules
- Enable Feature – Allows you to enable features like Azure Sphere, Unassociated device etc
- You can now add attachment while writing your comment
- You can see the Closure date – Date by which you can expect your support ticket get completed
We have made some performance improvements to provide a seamless user experience and, of course, to upgrade IoTConnect capabilities constantly.
- Improved custom properties management, provided interface to company owner to manage custom properties of company.
- Added device sync failure into device as diagnostic to identify device status issues or other unknown issues.
- Improved template listing by adding solution name for solution template.
- Added solution code while creating new solution. Old solution will automatically assigned unique code.
- Improved OTA Update for type 2 device by stripping out duplication information.
- Enhance puling historical data to support sid supported message for Sphere.
Issue Fixes
- Invalid empty list message on device life cycle tab
- Access issue to developer.iotconnect.io in IE browser, user was not able to login before
- D2C Widget was showing floating values on axis
- Fixed device status update API status code issue
- Fixed issue of pulling historical telemetry data for company
- Fixed issue of showing invalid message size for some devices
- Fixed issue on deleting device for inactive company
- Fixed issue on adding extra character to Device Direct method
- Fixed device template export issue not to include new setting for device frequency
- Fixed reporting database ingestion issue for not storing gateway device with sid format
- Fixed dynamic dashboard crash on first data receive and other minor issues
Minor 1
Enabling Support User
Provides an option for company user to enable support user to login into company and access company data and verify settings to resolve support ticket. Company admin can allow access to support user for certain time limit.
Telemetry on MQTT broker
Added new connector to divert telemetry on MQTT broker. You can enable this setting from the Live Data Streaming option in Configuration. All device data will be routed to a specific topic of MQTT broker with QoS 1.
Dedicated Instance of Data Ingestion API
Provides dedicated processing area for data ingestion. Form configuration when this feature is enabled, The platform will create a new Azure App Service to host REST API of Data Ingestion. This can be scaled up or down based on performance.
OTA Update for Type 2
Revised OTA update for Type 2 devices. The firmware will have the ability to associate the OTA files with specific device tag. OTA will be sent out with multiple files and device tags. The firmware will update the child’s device based on the tag and update file. OTA acknowledgment for the child will be maintained separately.
Device Data Frequency
Provides a way to control the data frequency of the device at a template level. While creating a template you can set this frequency. The default frequency will be 60 seconds. You can increase as per requirement. To decrease you need to generate a support ticket. Platform Device SDK will work based on this setting, custom Device SDK have to welcome this setting and change its data sending behaviour.
Skip offline data process
Platform Device SDK will mark messages with a specific tag to skip the processing of offline data. No rule will be evaluated on this, Also this will not save as recent value as these are past data. Custom Device SDK needs to set this value while sending offline data.
Performance & Improvements
We have made some performance improvements to provide a seamless user experience and, of course, to upgrade IoTConnect capabilities constantly.
- Improved Quota Widget to highlight in case of data exhausted.
- Added sample format for batch import of a Gateway device.
- Added Revised support ticket UI & notification emails.
- Added Support to delete vague device form platform.
- Added Updated device landing age text for each device type.
- Welcome email on a new user was missing login URL and made the strong temporary password. Removed additional fields on the Reset password screen.
- Device Twin property was missing order while pushing the desired property of the device.
Issue Fixes
- Sending email notification on rule triggered to all users not selected ones Recent OTA Update API was not returning acknowledgment id Telemetry API was giving internal server error while pulling historical data.
- Deletion of the certificate was failed due to inconsistent data.
- Permission issue on a device group, The user was not able to acquire the device even if valid permission is existing.
- Deletion of user’s custom property was giving Internal server error.
- Dynamic dashboard issues. Loading improvements, Switching dashboard breaks the UI, etc
- Rule validation gives an internal server error when an attribute is used as a string, int (primitive data types).
- Template attribute changes give internal server error if the template is not used by any device.
- Device twin update was giving internal server error if the format of an incoming message is not valid.