- The following driver is available in this release:
|
- Asset Hierarchy path and metadata: Digital Twin instances managed by Litmus Edge Manager (LEM) store their hierarchy context in two static attributes. Both are read-only in LE and update only when LEM pushes a change:
- hierarchyPath contains the asset's full path withspaces and special characters replaced by underscores.
- hierarchyMetadata contains a set of key-value pairs, for example enterprise, region, site, plant, area, work center, and work unit.
- Nested models: A new dynamic Nested Model attribute type lets one Digital Twin instance reference another. For example, a production line instance can point to each of its machine instances. You pick the target model when you define the attribute and the specific instance when you configure it. LE resolves the topic for you. Transformations do not apply to this attribute type.
- Static attributes in dynamic attributes publish: When a dynamic attribute payload publishes on digitaltwins.<modelName>.<instanceName>.<DynamicAttributeName>, the message now includes the Instance's static attributes alongside the value in a static_attributesobject.
|
- Analytics AI Suite
Manage all your AI resources on the new AI Suite page: models, instructions, skills, context files, tool definitions, MCP server registrations, memory, and agent files.
- Processors configuration allows user to select desired AI resources to be used for specific processor and/or Analytics logic.
- MCP and Tool management supports validation, test connection, tool list view.
- LE exports the resource tree as a ZIP file for backup or transfer to another instance, and imports a ZIP to restore it.
- LE stores, lists, and includes agent files in an export. Processor support for agents is planned for a future release
- Import and export for scaling and backup.
|
- The following new connectors are available in this release:
- SQL Gen 2 connectors now support JSONPath field mapping. Column mapping can read values from anywhere in a nested payload. This applies to the PostgreSQL, MySQL, and MS SQL connectors, so you no longer need to flatten nested telemetry upstream. Select Enable JSONPath on the connector configuration to switch mapping values from first-level payload keys to JSONPath expressions such as $.factory.line.machine.sensors.temperature.
|
- Litmus Edge now includes Solution Templates, which capture the complete configuration of a Litmus Edge system as a JSON file that you can apply to other systems. You can parameterize a template, choose how it merges with existing configuration, and roll back to a snapshot taken before it was applied.
- Parameters: A template can contain parameters so one template serves many sites or devices without being edited. You enter the values when you apply the template. LE fills them into the settings and validates them before writes to the device.
- Apply modes: Three modes control what happens to configuration already on the device. Reset & Apply clears the existing configuration and replaces it entirely with the template. Merge & Apply combines the template with the current configuration. Items with new IDs are added, and items whose IDs already exist are overwritten after you confirm. Apply uses system logic, where each component decides individually whether to overwrite or keep an existing item.
- Snapshots and rollback: LE captures a configuration snapshot before a template is applied. You can browse snapshot history, capture a snapshot manually, and roll back to any earlier snapshot. A rollback is itself snapshotted, so it can be undone in turn.
|