thingsHub Public Documentation
Breadcrumbs

2024-04-25 - thingsHub 5.5


5.5 Release Patches

  • The Google Maps API key can be configured via tenant settings to enhance security.

  • The issue with Grafana user creation failing when the username includes uppercase letters has been resolved

  • A parameter in the tenant configuration file’s identity provider block enables overriding the open configuration path for Keycloak OIDC

  • The issue causing TSDB to crash when the data table failed to handle a malformed internal message has been resolved.

  • Access to Things flow when deployed without a domain in the tenant configuration has been resolved

  • The issue where the notifier could not connect to NATS when both security and JetStream were enabled has been resolved.

  • The issue resulting in the loss of new HA NATS connections due to high number of connections from the thingsFlow service has been resolved.

  • The issue with incorrect timestamps when a device collects and sends multiple data points in a single uplink has been resolved.

  • The resource requested by the thingsflows service has been optimized.

  • The tracked asset metadata field has been enhanced by using updated_at in place of moved_at.


5.5.13 Release Notes

  • Incorrect timestamp field usage onSpeaking Location Card and Map Tooltip has been resolved

  • Wrong driver description for a single driver drivers has been fixed

  • The issue with services losing MQTT connections after update has been resolved.

  • The issue with device configuration hangs for multiple seconds when the driver configuration schema contains a lot of fields has been resolved.

  • The missing device deletion message as been added.

  • The missing info message when guest user intends to remove or update device has been resolved

  • The validation on field mapping field with at least 2 characters

5.5.14 Release Notes

  • The data exchange table connection button UI permissions have been improved for both users and guest users.

  • The redundant error message "Please stop the tracking algorithm to reconfigure it" has been removed.

  • The issue with the user email field not accepting a range of valid email formats has been addressed.

  • Node Affinity options to the thingsHub helm charts are added for more control over scheduling deployments in a kubernetes cluster.

  • In network connectors that use websocket, the payload size limit has been increased from 4kb to 1mb.

5.5.15 Release Notes

  • Support for self signed certificate in keycloak identity provider has been added.

5.5.16 Release Notes

  • The issue with duplicate tracked assets appearing on different pages in the tracking map has been resolved.

  • The issue with incorrect cluster window data in the tracked asset journey has been resolved.

  • The issue with exporting tracked assets from Site Analytics, which was previously not exporting, has now been fixed.

  • The issue with the tracked asset count on the homepage not syncing with the tracking map has been resolved.

  • The issue with the alert email, where clicking on the tracked asset link did not navigate to the tracked asset detail page, has been resolved.

5.5.17 Release Notes

  • The issue with the incorrect header text in the dashboard removal modal has been resolved.

  • The nil pointer issue while clearing geolocation of an eddystone tracked asset has been resolved.

  • The issue with German text displaying as "Website" on the Tracked Asset List page has been resolved.

  • The success message displayed after updating the label from label management has been enhanced to provide more meaningful feedback.

  • The unnecessary spaces in the device automation type and notification tab have been removed.

  • The issue with the info window not appearing when hovering over the "11+" count on the Driver Detail page has been resolved.


5.5.18 Release Notes

  • The inverted direction visible in the tracked asset journey opened in the Firefox browser has been resolved.

  • While signing out from the Grafana, the user navigating to the login page instead of the relogin page has been resolved.