Release Notes¶

Newest first. For how to read a version number, see Versions & Seeq Compatibility. If you run the legacy connector (version 4.5.2), start with Upgrading from the Legacy Connector.

How often these appear. Every release is recorded here. A release that moves to a new Seeq Connector SDK line, or changes behavior you would notice, gets a full entry. A routine release gets a short one.

Next release (in preparation)¶

Credentials out of the configuration, and security options. An existing configuration keeps working: an installation that works on 100.35.137 keeps working after this upgrade with no configuration change. The connector then asks you to move its Knowledge Manager passwords into the new secrets store, which takes one command. The version number is assigned when it is released.

Added¶

Knowledge Manager credentials in the VForge secrets store, one file on the agent host (vforge/secrets/credentials.json), instead of in the connector configuration that Seeq administrators can view. Each connection's credential is found by its Id; VFORGE_SECRETS in UserName, Password and Domain means "use the store". Several connections can share one credential. Seeq's SECRETS_FILE: references are read, in the configuration or the store. See Credentials.
vf-agent, a command-line tool for the store, installed by the connector at vforge/bin/ and shipped in the package's bin/: set, list and check credentials, and move an installation's passwords out of its configuration with secrets migrate. Passwords are never taken on the command line or printed. See Move the credentials.
Configuration backups never contain a password. Values are written as ********; backups made by earlier versions are masked the next time the connector starts.
Optional certificate validation on https connections. A new per-connection setting, VForge.Http.Tls.Trust, chooses which server certificates to accept:
Any, the default and the only behavior of earlier releases
System, the agent host's trust store
File, certificates you supply, such as an internal CA or one pinned server certificate

System and File also check the host name. A setting the connector cannot honor stops that connection from connecting rather than falling back to accepting any certificate. See TLS certificate validation. - The certificate choice is logged once per connection at startup: a warning when an https connection runs without validation, or the trust source when it validates. - Retiring a connection's credential: vf-agent secrets remove and remove-shared, which refuse a credential a connection still uses. See Using vf-agent. - Connections without hand edits. vf-agent config check finds a formatting mistake in the configuration by line and column before Seeq loads it. vf-agent datasources lists, adds (from the connector's own defaults), enables, disables and deletes connections, keeping a masked copy of the file before each change and never removing the last connections. The connector describes its configuration for these commands in vforge/products/seeq-connector-abbkm/connector-profile.json, written at each start. See Using vf-agent. - A ready-to-run command for an empty credential. When a connection has no credential yet, the log gives the exact vf-agent secrets set command for it, with the connection's Id filled in. - vf-agent asks before removing or replacing anything. In scripts, add --yes; without it the command stops and changes nothing. This includes secrets migrate --apply. Every command and option is on the new vf-agent reference.

Changed¶

The generated default connection is now an inert example. When the configuration has no connections at all, the connector creates one that is disabled, with a placeholder server and VFORGE_SECRETS for its credential, matching the shipped template. Earlier releases created an enabled connection with leftover test values. Installations with a configured connection are not affected.
A Password starting with SECRETS_FILE: is now read from that file, as Seeq documents. Earlier releases sent such a value to Knowledge Manager as the literal password.
Up to 4 Knowledge Manager queries at once per connection, where earlier releases ran at most 2, so data returns faster. The connector still backs off by itself when Knowledge Manager slows or returns errors. To keep the earlier load, set "MaxConcurrentRequests": 2 on the connection; that also limits how many Seeq requests the connection works on at once.

Fixed¶

Trends going blank when paging through history. Seeq caches what a connector returns and treats a period with no sample at its edge as having nothing beyond it, so later views of that signal came up empty ("There is no data in your current display range") until the datasource cache was cleared. The legacy connector and earlier releases are affected. The connector now returns the nearest sample on each side of the requested period, looking further for signals with long gaps. Seeq still shows the gaps; it does not draw a line across them. Calculations over those periods also see the data again.

Deprecated¶

Passwords in the connector configuration. They still work in this release: the connector uses them, logs a warning, and copies them into the store. Support will be removed in a later release, announced here at least 30 days ahead.

Known limitations¶


Certificate validation is off by default	Validation is now available, per connection: set `VForge.Http.Tls.Trust` to `System` or `File`, which checks the certificate chain and the host name. The default stays `Any`, the behavior of every earlier release, so existing `https` installations with self-signed servers keep working unchanged. See TLS certificate validation
The secrets store is plain text on the agent host	Protected by file permissions, so an administrator of the agent host can read it, the same boundary as Seeq's own secrets file. Options we would add with a customer who needs more: Credentials
A null value from Knowledge Manager is stored as `0.0`, not as a gap	Unchanged from `4.5.2` on purpose. EEI will change it only after confirming with customers
No condition (capsule) support	Unchanged from `4.5.2`. A possible future addition
Full index only	Knowledge Manager offers no change feed, so each index is a full one

100.35.137 — 2026-09-24¶

The first release of the re-architected connector, replacing the legacy connector 4.5.2. The core behavior has not changed: the same tags, the same asset tree, the same signals. What changed is everything underneath, and that is why this upgrade takes more care than the ones after it.

What stays the same¶

For a well-formed tag list, the connector's index output is identical to 4.5.2:


Asset tree shape and asset identities, in all four hierarchy modes	Identical
Signal identities, names, descriptions and interpolation	Identical
Stored sample values and timestamps	Identical
Datasource class (`ABBKM-V3`)	Identical
Signal properties	One addition: `Group Number` and `Channel Number` now appear (see Fixed)

So existing worksheets, analyses, calculations and annotations keep resolving after the upgrade, with no re-index, migration or rework. EEI verified this three ways: 1. A line-by-line comparison against the legacy source. 2. A frozen corpus of real, anonymized Knowledge Manager data, checked on every build. 3. A comparison that re-indexes through Seeq and reads the result back.

Fixed¶

Each of these is a defect in 4.5.2:

Tags with extended characters now index. Names with Cyrillic characters or umlauts failed to index, and the workaround was renaming the tag. Responses are now read as UTF-8. Tags that already indexed are unaffected.
Signals no longer fail across a daylight-saving change. A read spanning the spring-forward boundary could fail outright in Workbench, because samples arrived out of order. They are now sorted, so the read returns data.
One bad tag no longer stops the index. A tag name that does not parse, for example one containing a \, could abort the whole index run. Such tags are now skipped and logged by name, and the rest index normally.
An error from the Knowledge Manager server is no longer mistaken for data or for health. An error page or failed sign-in is now rejected, and an unhealthy server shows as disconnected.
An empty data response no longer fails. It returns an empty result.
Signal properties now reach Seeq. Group Number and Channel Number were built but never attached. This is the only addition to index output.

New¶

Built on EEI's shared connector foundation. The same foundation as every EEI connector, so a change on the Seeq side is absorbed once, for all of them. See What an EEI Connector Does on Your Seeq Agent.
Resilient calls to Knowledge Manager. Bounded concurrency, retries with back-off, timeouts and a circuit breaker, adjustable per connection. A slow or unstable server slows the connector down instead of stalling an index run. Index runs also respect a maximum duration. See How EEI Connectors Behave on Your Network.
Connector health in Seeq Workbench, optional and off by default. Each index run's metrics are published as signals you can trend and alert on. A report of each run is also written on the agent host.
Licensing. The connector checks a signed license bound to its host, and serves up to the licensed number of datasources. See Licensing.
Configuration protection. The configuration is saved before each load, so a configuration reset can be recovered.
A supported release path. Each release is built and tested automatically, published as one verified bundle, and recorded with its test evidence.

What it needs¶


Java on the agent host	Java 21
Seeq Link agent	`100.14.16186` or newer. The release is built on the `100.35` Connector SDK line, and supports agents from `100.14`
Seeq platform API built against	`66.188.1`
A license	Issued for the agent host. Without one, the connector registers no datasources
Knowledge Manager	The ExtDataAccess WebAPI (`/ExtDataAccess/api`), with NTLM or Kerberos sign-in

Known limitations¶

Stated plainly, because they affect what to expect:


A null value from Knowledge Manager is stored as `0.0`, not as a gap	Unchanged from `4.5.2` on purpose: changing it alongside this upgrade could shift results in analyses that rely on it. EEI will change it in a later release only after confirming with customers
Certificates are not validated on `https` connections	Unchanged from `4.5.2`. Resolved in the next release: validation is available per connection (see Known limitations above)
The generated default connection carries leftover test values	Only when the configuration has no connections. The shipped template is correct. Fixed in the next release (above)
No condition (capsule) support	Unchanged from `4.5.2`. A possible future addition
Full index only	Knowledge Manager offers no change feed, so each index is a full one

Earlier: the legacy connector¶

Releases before the re-architecture were built from a separate code base and versioned against the Seeq release they targeted, the last being 4.5.2. It was built for Seeq R60 and receives no further development. See Upgrading from the Legacy Connector.