> For the complete documentation index, see [llms.txt](https://help.tillit.cloud/tillit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tillit.cloud/tillit/tools/ignition-module/ignition-module-changelog.md).

# Ignition Module Changelog

### Changelog

{% hint style="info" %}
This changelog summarises the changes in the TilliT Ignition module since v1.4.2 (released February 2025).

The module ships as two parallel version lines built from a shared core: the **1.x.x** line targets **Ignition 8.1** and the **2.x.x** line targets **Ignition 8.3**. The two lines are released together and receive matching patch updates — the same bug fixes and features land in both — so a given release appears under both a 1.x.x and a 2.x.x version (for example, Ignition 8.1 **v1.6.2** and Ignition 8.3 **v2.1.3** are the same release). Except where an item is marked "(Ignition 8.1)" or "(Ignition 8.3)", every change below applies to both lines.
{% endhint %}

### v1.6.4 (Ignition 8.1) / v2.1.5 (Ignition 8.3) — August 2026

**Improvements**

* **The initial MQTT connection to TilliT now retries after a transient failure.** If the module's first attempt to connect to TilliT over MQTT when it starts fails — for example a brief TLS or DNS timeout while the network is still settling during gateway boot — the module now retries automatically with backoff (up to five attempts) instead of staying offline until the next restart or configuration change. Previously a single start-up failure could leave the module permanently disconnected.
* **(Ignition 8.3) The TilliT Historian integration is now optional.** The module no longer requires Ignition's Tag Historian module to be installed and licensed. A gateway that doesn't use the TilliT Historian can now run the module without it — previously the module would fail to load if the Historian module was absent or uninstalled. Where the Historian module is present, historian behaviour is unchanged.

### v1.6.3 (Ignition 8.1) / v2.1.4 (Ignition 8.3) — July 2026

**Bug fixes**

* **Restored and cloned gateways now stay offline until you re-enable them.** When a gateway is restored with Ignition's "Restore Disabled" option, the TilliT connection is now saved as disabled, so it stays offline across gateway restarts (previously the connection would come back on the next restart, where a restored or cloned backup could collide with the source gateway on the shared connection identity). Re-enable it from the configuration page once the gateway is ready to connect. This corrects the session-only behaviour noted under v1.6.2.

### v1.6.2 (Ignition 8.1) / v2.1.3 (Ignition 8.3) — July 2026

**New features**

* **Enable/disable the TilliT connection.** A new master switch in the module configuration turns the TilliT MQTT connection on or off without uninstalling the module. When disabled, the module opens no external connection — useful for standing a gateway down (for example, a restored or cloned backup) so it can't collide +with the original on the shared connection identity. The switch defaults to enabled, so normal installs and upgrades are unaffected.
* **Note on gateway restore:** in this release, if you use Ignition's "Restore Disabled" option the connection is held offline for that gateway session only — it is *not* saved to the Enable setting, so a restart without a configuration change brings it back online. To keep a restored or cloned gateway offline across restarts on v1.6.2, switch the connection off explicitly in the configuration and save. (Fixed in v1.6.3 / v2.1.4, where "Restore Disabled" is persisted automatically.)

**Improvements**

* **Data subscriptions reliably recover after a connection interruption.** Following an MQTT reconnection, the module now confirms its data subscription is re-established (retrying automatically if needed) and reports subscription health in the gateway connection status — so a connection that looks healthy always reflects live data flowing.
* **(Ignition 8.3) Configuration changes apply immediately.** Saving settings from the module's configuration page now takes effect without a module restart.

**Bug fixes**

* **No spurious production spike on start-up.** When the module starts with a count already present on the line, that starting value is no longer reported as newly-produced units on the first update.

### v2.1.2 (Ignition 8.3) — July 2026

> Ignition 8.3 only. The equivalent changes reach the 8.1 line in v1.6.2.

**Improvements**

* **TilliT Historian now supports remote store-and-forward.** History forwarded from remote edge gateways is accepted and published to TilliT, so a gateway that buffers data during a connectivity gap can hand it off once reconnected.

**Bug fixes**

* **Alarm Dashboard settings now save reliably.** The Alarm Dashboard's event-retention and context-lookback options save correctly.

### v1.6.1 (Ignition 8.1) / v2.1.1 (Ignition 8.3) — July 2026

**New features**

* **Raise an event with your own timestamp from scripting.** `system.tillit.raiseEvent(eventTypeId, assetId, timestamp)` is a new overload that lets a script supply the event's occurrence time as an ISO-8601 UTC string (e.g. `"2026-06-15T10:30:00Z"`) — useful for back-filling or store-and-forward after a connectivity gap. Available in gateway, Designer, and Vision client scripting. The supplied time also scopes the alarm context attached to the event, so a back-dated event correlates alarms around that past time. The existing two-argument call (stamped with the current time) is unchanged, and an invalid timestamp is rejected with a clear error.
* **(Ignition 8.1) Per-event Context tag.** Each event type now exposes a `Context` tag alongside `Trigger` and `Acknowledge`. Write a JSON object to it before firing the trigger and it is attached to the raised event. This brings 8.1 to parity with the 8.3 module, which already had it. Existing gateways gain the new tag automatically on the next tag-structure build (no action required).

**Improvements**

* **Events raised from scripting now carry alarm context.** When the causal-analysis module is active, events raised via `system.tillit.raiseEvent` are enriched with the same peer-asset alarm snapshot as tag-triggered events.
* **Activity forms can subscribe to process-variable updates.** Process-variable value changes are now published so an edge data item on an activity form can subscribe to them, with update volume throttled to avoid flooding.

**Bug fixes**

* **Scripted event timestamps are now correct.** Events raised from scripting are now stamped in UTC.
* **Control Parameter tag paths honour the site's UNS segment.** When a site has a UNS segment override configured, Control Parameter tags now follow the same path convention as the rest of the tag tree.

### v1.6.0 (Ignition 8.1) / v2.1.0 (Ignition 8.3) — June 2026

**New features**

* **Trigger a Wire Flow from scripting.** A new `system.tillit.triggerWireFlow(...)` function starts a Wire Flow from gateway, Designer, or Vision client scripting.

**Improvements**

* **Per-asset alarm tracking with local persistence.** Alarm triggered/cleared events are now captured per asset and queued to a local store, so alarm activity is retained across module restarts and attributed to the correct asset.

### v1.5.6 (Ignition 8.1) / v2.0.6 (Ignition 8.3) — May 2026

**New features**

* **(Ignition 8.3) TilliT Historian.** The 8.3 module can now act as an Ignition historian provider, publishing selected tag history to the TilliT cloud directly from Ignition.

**Bug fixes**

* **Process-variable values are now timestamped in UTC.**

### v1.5.5 (Ignition 8.1) / v2.0.5 (Ignition 8.3) — May 2026

**Behavioural changes**

* **Tag paths omit the tenant prefix when a site has a UNS segment.** If a site is configured with a UNS segment, its tag paths no longer include the tenant prefix. Verify any hard-coded tag references for sites that use a UNS segment.

**Bug fixes**

* **Asset names with special characters no longer disrupt start-up.** Characters that aren't valid in Ignition tag paths are now sanitised, so an asset's display name can no longer prevent the module from starting.

### v1.5.4 (Ignition 8.1) / v2.0.4 (Ignition 8.3) — May 2026

**Improvements**

* **Gateway online indicator reworked.** The edge online indicator now uses a retained heartbeat, so the gateway's online status is reported promptly and reliably to downstream systems.

**Bug fixes**

* **Order-progress data no longer stops during long-running orders.** Order progress continues to publish for the full duration of a long-running order.

### v1.5.3 — May 2026

**Improvements**

* **Tag paths now use the asset's UNS segment (when configured) and trim whitespace from every path segment.** This prevents tag-tree mismatches when an asset's display name contains stray whitespace or differs from its canonical UNS identifier — both sites and parents now respect the UNS segment too.

**Bug fixes**

* **Module no longer crashes on startup with large asset sets.** A new "module readiness" status tag is also exposed so external systems can wait for the module to finish loading before reading tag values.

### v1.5.2 — March 2026

**Improvements**

* **MQTT endpoint can now be driven from `config.json`,** giving you a config-file-based override instead of having to set the endpoint through the UI.

**Operational**

* IoT endpoint configuration corrected.

### v1.5.1 — March 2026

**Bug fixes**

* MQTT endpoints corrected after a regression.

### v1.5.0 — March 2026

This is the first release built on the new dual-module repository layout that supports Ignition 8.1 (this v1.5.x line) and Ignition 8.3 (the parallel v2.x line) from a shared core.

**New features**

* **"Current rate" is now reported on order progress.** The order's current run rate is published alongside other progress metrics.

### v1.4.9 — January 2026

**Improvements**

* **Order progress status changes are now pushed immediately** rather than waiting for the next scheduled cycle. Downtime detection is significantly more responsive on the dashboard side.

### v1.4.8 — October 2025

**New features**

* **EU region support** for tenants hosted on TilliT's European infrastructure.

### v1.4.7 (intermediate)

**Bug fixes**

* **Process variables are now correctly scoped to the asset they're allocated to.** Previously, every asset's tag tree contained every process variable in the tenant — fixed to only include the variables actually assigned to that asset.
* **Writing to Control Parameter "Write" tags now flows back to TilliT.** Before this release, Write-folder tags for control parameters were created but had no write handler attached, so writes silently failed (or were rejected as read-only). After this release, writes are persisted back to TilliT against the active recipe for that asset.

**Improvements**

* **Timeseries data is now guaranteed to publish at least every minute,** even when there's been no value change, ensuring continuous data on downstream historians.

### v1.4.5 (intermediate)

**Behavioural changes**

* **Control Parameter tag tree restructured to include Phases.** Read tags moved from `…/Read/ControlParameters/{name}/…` to `…/Read/ControlParameters/Phases/{phaseSequence}/{name}/…`. If you have Ignition tag references that hard-coded the previous path, they'll need updating.

### v1.4.3 (intermediate)

**New features**

* **Control Recipe support.** Control Parameters from running orders are now surfaced as Read tags in Ignition (`…/Read/ControlParameters/{name}/{Target,LowerLimit,UpperLimit}`). This is the initial implementation; see v1.4.5 and v1.4.7 for follow-up work.

**Improvements**

* Ignition module restart behaviour improved (faster recovery on configuration changes).

***

### Recommended upgrade path for tenants on v1.4.2

If you're upgrading from v1.4.2 directly to v1.6.3, the changes most likely to require attention on your side are:

1. **Control Parameter tag paths now include `/Phases/{phaseSequence}/`** — update any Vision/Perspective bindings or scripts that reference the older path shape.
2. **Control Parameter Write tags now actually write back** — this was effectively read-only before; verify any operator workflows you'd disabled in expectation of read-only behaviour are now intentionally enabled.
3. **Process Variable tag trees will be smaller per asset** — only allocated process variables now appear under each asset. If you previously had bindings to a process variable that wasn't actually assigned to the asset you read it from, those bindings will now resolve to a missing tag.
4. **Tag paths use UNS segment + whitespace-trimmed names** — assets whose names contain trailing/leading whitespace, or which have a `unsSegment` configured that differs from `name`, will appear under the trimmed/UNS path. Verify operator screens still resolve correctly.
5. **Sites with a UNS segment now drop the tenant prefix from tag paths, and Control Parameter tags follow the same convention** — if any sites use a `unsSegment`, re-check bindings against the new path shape.
6. **The TilliT connection can now be disabled, and a "Restore Disabled" restore now stays disabled across restarts** — the master switch defaults to enabled, so no action is needed on a normal upgrade. As of v1.6.3 / v2.1.4, restoring or cloning a gateway with Ignition's "Restore Disabled" option saves the connection as disabled so it stays offline across restarts (avoiding a collision with the source gateway on the shared connection identity); re-enable it from the configuration page once the gateway is ready.