Release Notes - thingsHub Product Development - 8.6.0 - Jun 17 23:15

TH-6262

Predictable Login Page Language Behaviour

Story

The login page currently has two independent problems that together make language behaviour feel unpredictable to users.

Problem 1: The login page overwrites the user's saved language preference. Any language change made via the login page dropdown is treated as a permanent account update. This means a user who switches the login page to their preferred language just to read it will have their account silently updated to that language the moment they authenticate — even if their profile already had a different language saved.

Problem 2: The login page ignores available language signals. Before a user logs in, the system has access to two useful signals: the user's browser language setting, and the tenant's configured default language. Currently both are ignored. The login page always displays in English regardless of context, so users from German-speaking tenants always encounter an English screen on their first visit.

TH-6084 TH-6261

TH-6261

Support Tenant Default Language & Preferences in Login Response

Story

New users are currently defaulted to English (en) regardless of the tenant context. Additionally, after a successful login the frontend must separately get user’s preference request to learn the user's language, adding a network round-trip that delays UI rendering.

TH-6084 TH-6262

TH-6257

Clean up legacy standard asset view from Asset Status Component

Task

With the recent introduction of the kendo-asset-detail-overview page, the standard asset details are now handled in a dedicated view. The asset-status component previously served a dual purpose (handling both standard and shipment assets). Now that standard assets have migrated, the asset-status component contains unused legacy logic, map configurations, and UI templates that should be removed to reduce technical debt.

Acceptance Criteria

• Code Cleanup: All unused logic, state variables, map configurations, and conditional UI blocks previously dedicated to standard assets in the asset-status component are removed.

• Shipment Asset Integrity: The asset-status component functions correctly for shipment-asset entities without any regressions. The shipment map, status tracking, and information cards must continue to load and update as expected.

• Live Updates: MQTT live updates for shipment locations continue to function normally without throwing errors.

• No Dead Code: Unused templates, map rendering fallbacks, and unused import statements related to the legacy implementation are completely removed.

• Successful Build: The application builds successfully without any TypeScript or Angular compiler warnings related to these removals.

TH-6245

Search field loses focus and blocks typing during asset filtering in Assets View

Bug

Environment:

• Affected Version: TH 8.2+

• Observed on: Fischer, Lab

• URL: [Add affected Assets View URL]

Description:
When typing in the search field within any Assets View, the filtering starts automatically while the user is still typing. During the filtering process, the input field temporarily loses focus, preventing further typing. After the filtering completes, the cursor is no longer active in the search field, requiring the user to manually click the field again to continue typing.

This creates a disruptive and frustrating search experience, especially for slower typing speeds or larger datasets where filtering takes longer.

Steps to Reproduce:

1. Open any Assets View

2. Click on the search/filter input field

3. Start typing slowly or pause briefly between characters

4. Wait for the automatic filtering to trigger

5. Try continuing typing immediately after filtering starts/completes

Additional Information:

• Behaviour introduced from TH 8.2 onwards

• Jam recording: Jam Recording

TH-6218

Device Labels: Display usage counts for Data Tables and Tracking Algorithms on the delete confirmation modal

Bug

1. Source

• Source Link: https://smartmakersiot.slack.com/archives/C1Z1TA09F/p1777624545346229?thread_ts=1777624478.299719&cid=C1Z1TA09F

2. Context & Objective:

• What is the problem: Currently, when a user attempts to delete a label, the confirmation modal only warns them if the label is actively used in an Integration. Because the modal does not show if the label is tied to Data Tables or Tracking Algorithms.

• Objective: Expand the delete confirmation modal to provide full visibility by showing usage counts across Integrations, Data Tables, and Tracking Algorithms.

3. Environment & Prerequisites

• Reproducible Environments: DEV, QA

• Browser/OS/Viewport: Any

4. Current State (User Perspective) The delete label modal only displays the usage count for Integrations, omitting all other system dependencies.

5. Acceptance Criteria (Definition of Done)

• The delete label modal must display usage rows/indicators for three distinct categories: Integrations, Data Tables, and Tracking Algorithms.

• The total aggregated usage count must be clearly visible on the modal.

• The usage counts must reflect real-time data. If a label is assigned to or removed from an entity elsewhere in the platform, the respective count on the delete modal must accurately increment or decrement.

• If a label is completely unused across all three categories, the modal must default to displaying a count of 0.

TH-6199

Rename or delete labels from devices overview sidebar

Story

As a thingsHub user maintaining my device labels, I want to rename or delete a label directly from where I see it, so that I can keep my label taxonomy clean without disproportionate effort and with full awareness of downstream impact.

Labels organize devices and are referenced by integrations and Data Tables to determine which devices feed into them. As tenants grow, taxonomies drift — typos, naming changes, project labels outliving their projects — but every correction today requires leaving the current view to navigate to the dedicated Manage Labels page. The friction is small per action but compounds: cleanup is deferred, taxonomies degrade, and misnamed labels stay in place even when they front production data flows.

See google mail label user experience

The capability already exists: the current Delete Label dialog surfaces affected devices, integrations, and Data Tables, and references are by ID, so renames are non-destructive. What is missing is proximity — comparable to Gmail's hover-revealed three-dot menu on labels.

TH-6172

[New Feature] Enable Copy of Field Names by Double-Clicking on the grid header in Kendo Time Series Grid

Improvement

This feature has been requested by the Delivery Team (requested by Pascal). It is intended to improve usability when working with device data, especially during troubleshooting, and data analysis activities where field names are frequently referenced.

Since the application uses the Kendo UI for Angular Grid time series grid in the Device Detail Data tab, this enhancement should be implemented at the kendo time series grid level to ensure consistency across all time series grids.

TH-6129

Validation error messages in Notifications tab are inconsistent and unclear

Improvement

Validation error messages in the Notifications settings are currently inconsistent in both placement and clarity, leading to poor user experience.

Observed issues:

• Error message is shown as a tooltip (“Invalid email”), instead of consistently inline with the input field

• No clear inline validation message below the field, which is the expected pattern across the platform

• Error messaging is generic and not user-friendly, lacking guidance on what is wrong (e.g., missing email format explanation)

• Placement of validation feedback is inconsistent with other forms in the system

This makes it harder for users to quickly understand and correct input errors.

Steps to Reproduce

1. Open the Notifications tab using the URL above

2. Enter an invalid email (e.g., afzal) in the email field

3. Observe the validation behavior

Actual Result

• Error appears as a tooltip

• No inline message under the field

• Message lacks clarity

• Validation behavior is inconsistent

Expected Result

• Error message is clearly visible under the input field

• Message is descriptive and user-friendly

• Validation behavior is consistent with other forms across the platform

  Unknown Attachment

TH-6128

Time Schedule dropdown shows empty space instead of placeholder in Device Automation

Bug

Environment

• QA8

• URL: https://qa8.thingshub.smartmakers.de/ui/en/device-automations/outdoor-devices-automation?tab=time-schedule

• Browser: Chrome

• OS: macOS
  

Description

In the Time Schedule tab of Device Automation, the time selection dropdown displays an empty blank area instead of a placeholder or default value when no time is selected.

This creates confusion for users, as it is unclear whether a value is missing, loading, or incorrectly rendered.

Steps to Reproduce

1. Open Device Automations

2. Open any automation (e.g., Outdoor devices automation)

3. Navigate to Time Schedule tab

4. Click on the time dropdown

5. Observe the top area of the dropdown list

TH-6107

[PUBLIC SHARING LINKS] Allow end users to change the language of the public asset page

Story

As an external user,

I want localized shared asset page,

So that I can understand shared tracking information clearly in my preferred language.

Live Figma Design

https://join-ozone-66722170.figma.site

Figma Make File

https://www.figma.com/make/Ej1XDPw1CAkC3QoCQdiZg6/Public-Asset-Page---opened-through-Sharing-Link?t=3STBrzhTVwrxJBGH-1

TH-6002

[STATE BASED BATTERY INFO] Show State-Based Battery Info on Device Detail page

Story

1. Read epic for general understanding:

TH-5909

2. Discuss with @User or the backend feature implementer which states have been implemented

TH-5883

Migrate asset journey view to the Advanced Map

Improvement

The asset journey feature shows users the path an asset travelled over time through directional arrows and event markers on a map, with filtering and detailed event information. Today this only works on the legacy map. Bring the same capability to the Advanced Map and switch the asset journey page over to it.

User value: Users tracking asset history see a consistent map experience with the rest of the app.

TH-5881

Migrate site floorplan editing to the Advanced Map

Improvement

Site administrators upload a floorplan image and position it on the map to align with the actual site layout. The process is: upload the image, see it appear on the map centered at the site with a bounding rectangle, then drag and resize it to the correct position and size. A transparency slider lets admins see both the floorplan and the underlying map at the same time (starting at fifty percent opacity) so they can align details accurately. Today this only works on the legacy map. Bring the same capability to the Advanced Map and switch the site floorplan page over to it.

User value: Site admins get a consistent floorplan editing experience across the app — same controls, same look — instead of switching to an older map that behaves differently.

TH-4868

Upgrade from Angular 19 to Angular Latest Stable Release (current is 21)

Story

TH-6408 TH-6409