v1.1.2

2026 August 27

A maintenance release. No endpoint was added, removed, or renamed, and no request or response payload changed shape.

Most entries below correct the published specification to match what the API already returns. One change affects runtime behavior: root Organization name validation in single-tenant deployments.

---

Client Credentials

Documentation withdrawn

Documentation for Client Credentials and machine-to-machine access tokens is withdrawn while the feature is completed. Existing credentials keep working. Contact Advantech support if you need programmatic access.

---

Behavior Changes

Identity & Access. Root Organization names are now checked for duplicates in single-tenant deployments.

Deployment mode	Root Organization	Sub-Organization
Single-tenant	Duplicate names rejected (changed in this release)	Duplicate names rejected
Multi-tenant	Duplicate names allowed	Duplicate names rejected

A POST /orgs call that succeeded before may now be rejected.

---

Fixed

Module	Details
Device Tunnel	In multi-tenant deployments, sessions could hang in ESTABLISHING, or hang in TERMINATING and then move to FAILED. Both transitions now complete.
Device Management	GET /devices returned a stale name and type for a Sub Node's parent WEDA Node. Both now reflect current values. Bulk Sub Node sync failed silently when a Sub Node was still recorded under a different WEDA Node, discarding the whole batch with no retry. The Sub Node is now reassigned to its new parent, and the rest of the batch is unaffected.
Data Stream	Sensor displayName and description were always empty because the device data model could not be parsed. Both are now populated. Device data model lookup timeout raised from 10 to 30 seconds, so a slow response no longer skips the model.
Telemetry	Complex sensor value types from a Sub Node are now serialized to JSON instead of dropped.
Identity & Access	Disabling then re-enabling a user created a duplicate root Organization. The existing one is now reused.

---

API Specification Corrections

The API already behaved this way. No integration change is required.

Module	Details
Notifications	29 error responses (400, 404, 409, 503) across the Notification Channel, Template, and Message endpoints now publish a schema. The schema was empty before, so the API reference showed no field information.
Device Management	GET and PATCH /devices/{deviceId}/telemetry-configs now declare an array of device configurations, each with its sensor list. GET /devices/{deviceId}/custom-info now declares a key-value map instead of a list of objects. DELETE /devices/{deviceId}/custom-info/{key} now declares 204 No Content. POST /orgs/{orgId}/devices now declares 201 Created.
Container Management	List stacks, list stack deployments, and list stack revisions now declare the paged wrapper (items, totalCount) instead of the bare item type. Compare Stack Revisions declares its own diff result type instead of a container stack. Manage Container State declares the command response instead of a stack creation payload. Corrected the 403 example on the stack revision endpoints.

---

Last updated on Aug-27, 2026 | Version 1.1.2