Thinger.io IoT Platform reaches version 6.2.0. In this update we are introducing some important improvements and new features to enhance the user experience and provide more granular control over various aspects of our platform.
From more precise permission settings, to enhancements in device and bucket data management, this update aims to make navigation and control over the IoT Platform more intuitive and efficient. We also worked on fixing some identified issues to ensure a smoother and more reliable user experience. We believe these changes will significantly contribute to the effectiveness and usability of our thinger.io IoT platform.
New Features
Added
- Devices associated with a Product can now display bucket data directly from their pages, under the menu option called “Buckets” 📊. Each device can now list all the associated buckets and will filter out its data in the Data view. Additionally, in future IoT Platform releases, we will add options for exporting, importing, and clearing data. Consequently, this opens the possibility to avoid sharing raw bucket data with project members, and effectively grant access only to their device data. This feature grants permissions at the device level, allowing actions such as ViewDeviceBuckets, ReadDeviceBucket, ReadDeviceBucketTag, and ListDeviceBucketTags.
- Introduced two new specific permissions for listing and reading bucket tags 🔖; ListBucketTags: Allows listing of bucket tags. ReadBucketTag: Allows reading of individual bucket tags. Previously, these operations required the more general ReadBucketConfig permission. This change provides more granular control over permissions on the IoT Platform.
- Claims now support including additional projects on the claim process 📑: This way, claimed resources can be added automatically to parent “global” projects that can be used to manage the resources with different profiles.
- Projects can be configured to limit bucket data access based on project devices 📋. This functionality enhances the project dashboard by displaying aggregated data and restricts data access to project members. You can activate this option in the claim settings, thus automatically creating member projects with these access limitations.
- Device Tokens are now available for MQTT and HTTP devices 📡🌐, as they can have regular API resources over a product.
Improved
- Templating system (used on products or endpoints) can now process placeholders with spaces.
- Internal LRU cache with a modern and safer implementation.
- Removed unused ‘curl’ dependency on the base image, slightly reducing image size.
Bug Fixes
- MQTT and HTTP devices can now also Device tokens via GUI, as they can define API resources over Products.
- Problem when removing nested resources, i.e., Bucket exports, Project Members.
- Bucket exports should not display set projects and clone context actions.
- Bucket exports not loading by default.
- Previewing the Apex Chart Widget prevents saving the dashboard.
- Apex Chart Widget fails to update series colors when the widget includes titles.
- Problem when updating device locations.
Community
Check out our Thinger.io community or our Discord Channel to propose improvements, report bugs, or request help for the Thinger.io IoT Platform.
Conclusion
In conclusion, the Thinger.io IoT Platform in its 6.2.0 release, brings significant improvements to our platform, focusing on enhancing the user experience and providing more granular control over various aspects.
The introduction of new features such as device-specific bucket data, new bucket tag permissions, additional project inclusion in the claim process, and the limitation of bucket data access based on project devices extends the IoT Platform capabilities and provides users with more precise control. Improvements to the templating system and the internal LRU cache further streamline the IoT Platform operation.
Finally, the addressed issues ensure a smoother and more reliable user experience. We are confident that these changes will greatly contribute to the effectiveness and usability of our platform.
We look forward to receiving user feedback on these enhancements.