Platform Version 6.0.0

Date: 11/03/20324
Component: Cloud Console
Release Note: CHANGELOG - Documentation


  • Property Forms :memo: : Allow creating custom forms for improving the user experience when setting values inside a property, i.e., when configuring a device. The form can be defined at Product level, and it is currently supported by Formly.


Property Forms


Device property editor using a form

  • Property Location :round_pushpin:: Location properties now display a map for picking the address directly from the map or via a search bar for using an address. Once an address is selected, it automatially fills the coordinates and timezone.


Property location editor


Property raw fields generated by location editor.

  • Dashboard Functions :zap:: Dashboard now supports creating custom functions for processing any data used in dashboard, i.e., for changing units, cropping decimals, or filtering values. Conversion functions can be selected on the data source configuration.


Dashboard Functions.


Source processing using Dashboard Function.

  • Dashboard Placeholders :label:: Dashboard now supports settings placeholders from a fixed value, or a device property. Placeholders can be used in a any string field on the dashboard, i.e., titles, units, or even inside functions to change the functions behaviour depending on current device configuration.


Dashboard Placeholders.


Dashboard Placeholder used inside a Unit Field.


Dashboard Placeholder used inside Dashboard Function.

  • Dashboard Property Button :new: : New “Property Button” widget for opening device properties for its modification, even if they have a Property Form defined.


Property Button Configuration.


Property Button on Dashboard.

  • Dashboard Group Widget (BETA) :capital_abcd: : New Group Widget that brings the possibility to add any number of widgets inside a parent widget.


Group Widget

  • Dashboard Property Table (BETA) :capital_abcd: : Introducing a new widget that enables quick editing of properties for a device or a set of devices. This widget includes various built-in controls such as text display, input text, input number, slider, color selection, switch, a save button, and an edit button. These elements can be configured in each column to patch a single property value.


Property Table


Property Table Configuration

  • Claiming Feature :point_up:: The Claiming Feature is a versatile and user-friendly tool designed for administrators to configure and expose a selected number of resources, such as devices, for end-user claiming. This feature enables administrators to effortlessly set up various resources which end-users can subsequently request. Upon a successful request, these resources, like specific devices, are automatically integrated into the end-users’ accounts. This streamlined process not only enhances user experience by simplifying resource acquisition but also provides administrators with efficient control over resource distribution and management.


Claim Configuration

One of the key strengths of this feature is its flexibility in claiming methods: users can initiate a claim through a directly generated URL, by scanning a QR Code, or by using a specific Claim Code:


Claim Details


Claim Process - Initial Step


Claim Process - Review

Once claim is completed, the process may request the configuration of the devices, i.e., via the Property Forms defined on the product.


Claim Process - Complete & Configure

  • Configurable Brand Accounts :man_office_worker:: We’ve introduced a new “Accounts” section for each brand. This enhancement allows more control over brand-specific behaviors, including:

    • Cross Sign-In Control: Decide whether users registered with one brand can log in to another, enhancing security and user management.

    • Public Sign-Up Options: Choose whether to allow public sign-up for each brand, providing flexibility in user onboarding.

    • Automated Role Assignment: Set specific account roles for users who register through public sign-up, such as automatically assigning ‘member’ status for device claiming purposes.

This update offers more customization to better align with your brand’s unique operational needs.


Brands Accounts Configuration

  • Configurable Brand Scripts :desktop_computer: : We’ve rolled out an exciting update: you can now configure custom scripts for your brand’s index.html. This enhancement is perfect for integrating tools like Google Tag Manager and monitor your customers traffic.


Brand Scripts Configuration

  • New Permissions :lock:: Console is introducing an array of specific new permissions, enhancing the granularity with which administrators can control member access and actions within the console. This update distinctly separates permissions for actions performed through the API from those executed directly on the console interface. In the current version, all existing permissions will continue to function as before. However, future updates will require the explicit assignment of ‘View’ permissions to maintain the access level. This change lays the groundwork for more precise and customizable user role management, ensuring enhanced security and efficiency in operation. At this moment they are partially released for Devices, but will be covering the whole console in future updates.


New View

  • Updated Editors


: Now editors are based on Monaco (the editor from Visual Studio Code) with support to maximize the editor and copy the contents:


New Code/Value editor in the console.

  • New Icon Picker


: There is a new icon picker with much more variety of icon and improved search capabilities.


New Icon Picker


  • Double click on Widget now opens the Widget editor!

  • Create and update properties performance

  • Time series data should not present data wraps anymore.

  • Internal Google Maps loader to potentially avoid multiple loads.

  • Buckets API query now supports “group_by” parameter.

  • Move Swagger to an Angular component. New url | Cloud Console

  • Initial deprecation of InfluxDB v1

  • Widget add time series automatically selects a different name and color for each series.

  • Dashboard source switching now allows switching between bucket tags, with minimum and maximum selected tags.

  • Dashboard internals.


  • Push button widget not working on mobile devices.

  • Real-time dashboards now work properly with project members and shared dashboards.

  • Fixed the issue where the dashboard widget with device resource data source was showing offline, despite the widget receiving data.

  • Deletion event not triggered for nested resources, i.e., device property.

  • Creation event not triggered for property resources.

  • Data bucket storage from Products using device resource with fixed interval randomly stop writing.

  • Add Syncs to the tokens actions.

  • Dashboard editing not being disabled on non-active tabs.

  • Token configuration was missing the description field.

  • Delete resource from console sending parameters like index, count…


  • Partial migration from AngularJs to Angular 17

  • Update OpenSSL to versión 3

  • Update Boost to 1.83.0

  • Update Mongoc to 1.25.1

  • Update Mongocxx to 3.9.0

  • Update Crypto++ to 8.9.0


Splendid update! :clap: :clap: :clap: :clap: :clap: :tada: :tada: :confetti_ball: :tada:
Many new and important features!
Congratulations to the Thinger team for this new version.



Many thanks for this, looks great. As part of a security review for a prospective client, we’ve been asked to harden all our internal systems to MFA by default. Could you please tell me if such feature is available and how to implement it? I asked some time ago about oauth2 clients (which could be a way I guess), but your documentation still has nothing on it. Please help if you can. Thanks!

1 Like

Hola Alvaro
Me pasa algo a partir de ésta version 6, en la cual luego de empezar a hacer un dashboard, a partir de la segunda modificación / agregado de widget que realizo, me aparece éste cartel, (SAVE DASHBOARD: ERROR: UNKNOWN) y ya no puedo avanzar, a menos que salga y vuelva a entrar a la edición del dash y vuelva a tener sólo una oportunidad de cambio, que será ? gracias!

Hi, sorry to be pushy but I would appreciate some news on this, or any news really. If we don’t get MFA or 2FA for our system we will sadly need to change provider soon, as our clients are becoming bigger and bigger and more stringent on the requirements. Besides, 2FA seems almost mandatory these days…

Many thanks

There is an open issue requesting this feature.

Yes, superb update.
The function is great to amplify/faint/move values in time series to make a better use of the room there.

Hi Antonio,

Thank you for reaching out and emphasizing the importance of Multi-Factor Authentication (MFA) and Two-Factor Authentication (2FA) for your operations. We understand the criticality of these security features, especially as your clients grow in size and their requirements become more stringent.

We are pleased to inform you that the implementation of MFA and 2FA is on our roadmap, with an expected release in the Q2-Q3 timeframe. However, we recognize the urgency you might be facing and are open to exploring options to accelerate this development. One such option could be a partnership where your company co-finances the accelerated development, ensuring that your needs are met in a timely manner.

We are committed to providing the security features that our clients need and would be happy to discuss this further to find a suitable solution for your organization.