Skip to main content

v1.1.1

2026 August 5

This release replaces the Data Engine's core data model.

  • Data Source and Data Object are merged in favor of a single unified entity, DataStream
  • Transfer Function renamed to Analyzer
  • Alert Rule is now an independent service with org-scoping, named Alert Policy
  • Data Stream Bridge is now generally available

Do review the Breaking Changes below and adjust integration accordingly — this is a substantial rework of the Data Engine API surface, not an additive release.

What's New in v1.1.1​

ModuleDetails
DataStream (replaces Data Source + Data Object)
  • Single entity for both device-originated (managedBy: System) and computed (managedBy: User) data — no more separate Data Source lookup step
  • New recordToDataLake per-stream toggle controlling whether history is persisted
  • DataStreams can now be created directly via the API (POST .../data-streams), not just auto-synced
Analyzer (replaces Transfer Function)
  • Renamed resource, org-scoped path (/orgs/{orgId}/devices/{deviceId}/analyzers)
  • This release ships one Analyzer type, TransferFunction — same one-to-one behavior as the v1.1.0 Transfer Function (one input, one output)
  • An Analyzer's output DataStream is claimed automatically on create/update — no separate claim call
Alert Policy (replaces Alert Rule)
  • Independent, org-scoped resource (/orgs/{orgId}/alert-policies) — no longer nested under a device/DataStream
  • A policy can attach to multiple DataStreams, and a DataStream can have multiple policies attached — the v1.1.0 limit of one rule per data point is lifted
  • New Alert Events endpoint (GET /orgs/{orgId}/alert-events) — queryable history of fired alerts
Data Stream Bridge (new — goes live)
  • One-way forwarding of DataStream values to a customer-hosted MQTT broker
  • Two resources: MqttBrokerConfig (connection profile) and Bridge (bindings + assembly policy)
  • Bindings reference a DataStream directly (dataStreamId), not a legacy data-point name
Notification Channels
  • Path becomes org-scoped (/orgs/{orgId}/notifications/...) — channel/template behavior and fields are unchanged

Breaking Changes​

Important

This version contains breaking changes across the entire Data Engine API surface. Review API Changes in v1.1.1 for the full endpoint-by-endpoint list and adjust integration accordingly.

ModuleDetails
Data Source / Data Object
  • GET /devices/{deviceId}/data-source is removed — a device's sensors are now returned directly in the DataStreams list
  • All /devices/{deviceId}/data-objects... endpoints are removed, replaced by /orgs/{orgId}/devices/{deviceId}/data-streams...
Transfer Functions
  • All /devices/{deviceId}/inputs/data-objects/transfer-functions... endpoints are removed, replaced by /orgs/{orgId}/devices/{deviceId}/analyzers...
Alert Rules
  • All /devices/{deviceId}/data-objects/{dataObjectId}/alert-rules... endpoints are removed, replaced by /orgs/{orgId}/alert-policies...
Notifications
  • /notifications/channels..., /notifications/templates..., and /notifications/messages... all move under /orgs/{orgId}/... — existing calls without the org path will fail
Identity & Access
  • PATCH /orgs/{orgId}/users/{userId} is removed — there is no replacement path. A member's Org role can no longer be changed through the API

Improvements / Bug Fixes​

AreaDetails
AI Model Management — Multi-Deployment Behavior
  • Coexistence is now evaluated by the combination of model name, model edition, and file name (together, the deployment path) — if any of the three differs from an existing deployment, the new one coexists alongside it instead of being rejected
  • If the deployment path and the file hash both match an existing deployment, the request is now rejected (unchanged)
  • If the deployment path matches but the file hash differs, the existing deployment is now replaced instead of rejected
  • Example: recreating a model with the same name/edition but a different file name → previously rejected, now coexists
  • Example: recreating a model with the same name/edition/file name but different file content → previously rejected, now replaces the existing deployment
AI Model Management — Deploy Actions
  • Deploy actions are trimmed to the ones that are tested: CHECK_DISK_USAGE, CHECKSUM_VERIFY, and ATOMIC_SWAP_AND_RESTART_CONTAINER
Resumable Uploads (tus)
  • Fixed: a tus request is now rejected when its URL doesn't match the upload's byte range
  • tusd hook errors now return problem+json, aligned with WEDA's standard REST error format
Authorization
  • orgId permission is now checked first — an unauthorized orgId returns 403 before other request validation runs
Last updated on Aug-5, 2026 | Version 1.1.1

On this page ...

Is this helpful?