Skip to main content

v1.1.0

2026 July 10

This release introduces one new capability — AI Model Management — and refines the API surface across Container, Device, and Data Point management, alongside a range of improvements and bug fixes. Review the Breaking Changes below before upgrading.

What's New in v1.1.0​

ModuleDetails
AI Model Management (New)
  • Full model lifecycle: create a model, register an edition, and upload the binary via the resumable TUS protocol (up to 50 GB)
  • SHA-based hash verification for upload integrity
  • Deploy an edition to one or more devices, with per-device deployment state tracking
Container Management
  • Deployment listing now returns real per-container state (previously always returned an empty array)
  • Registry access scope narrowed from Tenant-level to Org-level
Device Management
  • Device Name is now required at registration and must be unique within the same Org
  • New device-level query APIs for Data Sources and Data Objects
Data Points
  • Unified under the Generic Device architecture — physical and virtual devices share the same API path
  • data-source / data-object replace the earlier cPQ concept; Data Sources auto-sync into Data Objects, matched by name
  • New query APIs to read a specific data object's latest value, its historical values, and its binary data — such as captured images
  • Legacy /inputs/data-objects/... routes are deprecated for Data Object queries and Alert Rules — Transfer Functions (functionally unchanged) remain under /inputs/data-objects/transfer-functions
Management Console (MUI)
  • Device Management: new 4-tab detail page (Overview / Device Information / Container Deployments / Telemetry Configuration)
  • Registry Management: UI updated to reflect the Org-level scope change
  • Stack Management: full lifecycle UI — create, edit, deploy (including multi-device batch deploy), and delete

Breaking Changes​

Important

This version contains breaking changes. Review API Changes in v1.1.0 for details.

ModuleDetails
Authentication
  • The Identity service URL prefix is simplified to a fixed /identity; the previous /{tenant}/identity and /central/identity prefixes are no longer supported

Improvements​

ModuleDetails
Data Points
  • Alert rules are now validated on the server — rejected when the alert and reset thresholds are equal, or when the expression cannot be parsed
  • Latest-value queries fall back to IoTDB when the cache has no data yet, so recently written values are no longer missed
AI Model Management
  • Redeploying the identical model, edition, and file to the same device is now rejected as a conflict, preventing duplicate deployments
Organization Management
  • Deleting an Organization is now blocked while it still contains devices, preventing devices from being left orphaned and unmanageable

Bug Fixes​

ModuleDetails
Device Management
  • Deleting a device no longer floods the server with logs that could exhaust it and cause instability
  • Devices are no longer left as unmanageable orphans after their Organization is deleted
  • displayName and dataType no longer return as null when listing data objects
  • Updating a device with its existing name no longer returns a spurious error
  • Querying telemetry configurations for an offline device no longer returns a blank response
  • Device capability responses no longer show an invalid creation time
  • Fixed device-shadow sync issues, including offline sync, missing change events after a device restart, and DTDL serialization errors
Data Points
  • Creating an alert rule with an invalid threshold now returns a correct response
  • Creating a notification template no longer reports a false name conflict
  • Transfer Function creation timestamps and response examples are now consistent
Container Management
  • Deploying a stack to a device for the first time in a fresh environment no longer fails with a 500 error
  • Creating a registry with an invalid registry type now returns a clear error message
Remote Access - Tunnel
  • Tunnel sessions no longer return a null endpoint that prevented users from connecting
  • Session timestamps with no value now display as null instead of an invalid 0001 / 1970 date
Last updated on Jul-14, 2026 | Version 1.1.0

On this page ...

Is this helpful?