Release 6.2.0

More granular control over devices, buckets and permissions

The Thinger.io IoT Platform reaches version 6.2.0. This update introduces important improvements and new features to enhance the user experience, and gives more granular control over various aspects of the platform.

From more precise permission settings to better device and bucket data management, the update aims to make navigation and control over the platform more intuitive and efficient. The team also fixed a number of identified issues, for a smoother and more reliable user experience.

Release 6.2 at a glance

Version
6.2.0
Focus
More granular control over devices, buckets and permissions
New features
Device bucketsBucket tag permissionsAdditional claim projectsLimit bucket dataDevice tokens for MQTT and HTTP
Improved
Placeholders with spacesInternal LRU cacheSmaller base image
Bug fixes in
Nested resourcesBucket exportsApex Chart WidgetDevice locations
Feedback
Discord channel

The improvements and bug fixes are listed at the end of this page.

Device data

Each device shows its own bucket data

Devices associated with a Product can now display bucket data directly from their pages, under a new menu option called Buckets.

Each device lists all its associated buckets and filters out its own data in the Data view. Project members can then be granted access to their device data only, without sharing the raw bucket data with them.

Device page menu opened from the toolbar next to Status, Properties and API, listing Buckets, Tokens, Terminal, Geofences, Inspector and Settings, with Buckets highlighted
The new Buckets option in the menu of a product device, first in the list.

The feature grants permissions at the device level, so a role can view the device buckets, read their data and read or list their tags:

New permissions in 6.2

Device level, for device buckets
ViewDeviceBucketsReadDeviceBucketReadDeviceBucketTagListDeviceBucketTags
Bucket tags
ListBucketTagsReadBucketTag

The device-level permissions of device buckets, and the two new bucket tag permissions described in the next section.

Future releases of the platform will add options for exporting, importing and clearing this data.

Permissions

Bucket tags get permissions of their own

Two new specific permissions list and read bucket tags. Previously, these operations required the more general ReadBucketConfig permission.

ListBucketTags

Allows listing of bucket tags.

ReadBucketTag

Allows reading of individual bucket tags.

A role can now read the tags of a bucket without being able to read its whole configuration: more granular control over permissions on the platform. More on roles and access control on the security page.

Claims and projects

Global projects for claimed resources, data limits per project

Claims can now add resources to more projects, and a project can limit the bucket data its members see to the project's devices.

Additional projects on claims

Claimed resources are added automatically to parent "global" projects, which can manage them with different profiles.

Limit bucket data

A project restricts bucket data access to the data of its own devices, while its dashboard shows aggregated data.

Additional projects in the claim process

Claims now support including additional projects in 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.

Additional Projects field of the claim settings, with projectB selected
Additional projects where claimed resources will be included in the claim process.

Bucket data limited to the project devices

Projects can be configured to limit bucket data access based on the project devices. The project dashboard displays aggregated data, and the access of project members to the data is restricted. You can activate this option in the claim settings, so that the member projects created automatically come with these access limitations.

Advanced Options of the project settings with the Limit Bucket Data switch turned on
The Limit Bucket Data option, under Advanced Options in the project settings.

Connectivity

Device tokens for MQTT and HTTP devices

Device tokens are now available for MQTT and HTTP devices, as they can have regular API resources over a product.

The same change appears among the fixes of this release for the GUI: MQTT and HTTP devices can now also have device tokens there, as they can define API resources over products.

Improvements

Templates, cache and a smaller image

  • Templating system: the templates used on products or endpoints can now process placeholders with spaces, such as this one.
template
{{ payload : FunctionName = 22 }}

Placeholders with spaces are now processed

  • Internal LRU cache: a modern and safer implementation.
  • Base image: the unused curl dependency is removed, slightly reducing the image size.

Bug fixes

Fixes in buckets, dashboards and devices

  • Problem when removing nested resources, such as bucket exports and project members.
  • Bucket exports no longer display the set projects and clone context actions.
  • Bucket exports not loading by default.
  • Previewing the Apex Chart Widget prevented saving the dashboard.
  • The Apex Chart Widget failed to update series colors when the widget included titles.
  • Problem when updating device locations.

Your feedback

Tell us how 6.2.0 works for you

Release 6.2.0 focuses on the user experience and on more granular control over the platform.

Device-specific bucket data, the new bucket tag permissions, additional projects in the claim process and bucket data limited to the project devices extend what the platform can do and give more precise control. The templating system and the internal LRU cache streamline its operation, and the fixes make the experience smoother and more reliable.

We look forward to your feedback on these enhancements. Propose improvements, report bugs or ask for help in the Thinger.io community or on our Discord channel.

Every server release is listed in the changelog of the documentation.

Propose improvements, report bugs or ask for help

The team and the community are on Discord; the changelog lists the changes of every release.

Join the Discord channelRead the server changelog