Releases
TimescaleDB Module for Ignition 8.3
Every published version of the module, with the Ignition and TimescaleDB versions it has been verified against, plus a direct download for the .modl asset.
v1.0.18
v1.0.18 21 Aug 2026TimescaleDB Historian module for Ignition 8.3 with a TimescaleDB backend.
- Ignition:
- 8.3.0+
- TimescaleDB:
- 2.13+
Changes
- Fix: a historian whose password is a **Referenced secret served by a remote secret provider** recorded nothing after every Gateway restart, until someone disabled and re-enabled the profile by hand. The module resolved the secret while the historian was starting, which happens before the Gateway Network link to the Gateway holding the secret is up, so the read failed; the failure was then treated as an empty password and cached for the life of the profile. This is the standard OT/IT split — secrets on one Gateway, recording on another — so it affected every restart of the recording Gateway. The resolution is now retried (at most once every 5 seconds) and the credential is swapped into the live connection pool as soon as it can be read, so recording resumes on its own within seconds of the Gateway Network coming up. Data buffered by store-and-forward in the meantime is forwarded once it does
- A password secret that cannot be read is no longer reported as a database authentication error. Previously the only symptom was Postgres complaining that "the password is an empty string", which sends you looking at database credentials that are correct. The profile now says the secret could not be read and points at the secret provider and its Gateway Network connection, and no connection is attempted with a credential the module knows it does not have
- New: a self-contained demo of the module lives in `demo/`. One command builds a fictional brewery — a UDT-driven tag structure, five years of its history, a Power Chart page with a live query benchmark, an "About this module" page that reads the database as it describes it, and a historian administration view. Intended for evaluating the module without wiring up a plant first; see `demo/README.md` for what each part is meant to show
- The demo's admin chart now ships against the Embr Charts version the gateway actually runs, has its data labels turned off, and creates the tag group a new tag provider does not come with — without which OPC tags read `Tag Group Invalid` and look like a device fault
Known issues
- Two historian profiles pointing at the same database and schema with different compression or retention settings will contend: each profile applies its own settings, so the policies flip back and forth. Point each profile at its own schema or database
- annotation doesn't always appear, it works with just the manually made ones (annotation is always saved it is a rendering issue)
- It is possible to store NaN or Inf to the database correctly, but when aggregates are retrieved these values will distort the result
- Retrieved NULL values are transformed to 0.0 values
- It is not possible to change the data type of the tag (remove and create new one)
v1.0.14
v1.0.14 11 Jul 2026TimescaleDB Historian module for Ignition 8.3 with a TimescaleDB backend.
- Ignition:
- 8.3.0+
- TimescaleDB:
- 2.13+
Changes
- bug: Hikary pool is created with 'empty' password and keeps trying to connect. We don't let this to happen.
- tweak: timeout splitted with database insertion the timeout is longer (30sec), but it is not exposed to the user (do we need?)
Known issues
- annotation doesn't always appear, it works with just the manually made ones (annotation is always saved it is a rendering issue)
- It is possible to store NaN or Inf to the database correctly. But when aggregates are retrieved these values will distort the result.
- Retrieved NULL values are transformed to 0.0 values
- It is not possible to change the data type of the tag (remove and create new one)
v1.0.11
v1.0.11 3 Jul 2026TimescaleDB Historian module for Ignition 8.3 with a TimescaleDB backend.
- Ignition:
- 8.3.0+
- TimescaleDB:
- 2.13+
Changes
- rename tag
- tsdb_data format changed: intvalue, floatvalue, stringvalue, datevalue columns (sql historian like)
- tsdb_annotation like sqlth_annitation (sql historian)
- deleted+recreated tags: never un-retire; queries (raw/aggregated/annotations) now span the retired + active entries of the same path/type, so old history reappears automatically
- comments on datatype in the database
- is saving the quality covered with integration test
- user manual (docs/user_manual.md)
- system.historian.browse: tag is ignored in the tagpath
- auto-capture metadata doesn't work
- vendor name changed for the module (signing redone)
Known issues
- annotation doesn't always appear, it works with just the manually made ones (annotation is always saved it is a rendering issue)
- It is possible to store NaN or Inf to the database correctly. But when aggregates are retrieved these values will distort the result.
- Retrieved NULL values are transformed to 0.0 values
- It is not possible to change the data type of the tag (remove and create new one)