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.

1. v1.0.14

   v1.0.14 11 Jul 2026

   TimescaleDB 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)
   Download TimescaleDB-Historian.modl (1.4 MB)

2. v1.0.11

   v1.0.11 3 Jul 2026

   TimescaleDB 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)
   Download TimescaleDB-Historian.modl (1.4 MB)