Module 1.95.12
Release metadata
Section titled “Release metadata”| Release | 1.95.12 |
| Supersedes | 1.95.10 (1.95.11 was not released) |
| Platform | Ignition 8.1 |
| Upgrade type | In-place upgrade, no data migration |
| Deployment modes | All four |
Summary
Section titled “Summary”A stability release centered on the path an uplink takes from the network server to an Ignition tag. Several defects there were losing readings or writing them twice without producing an error anyone could see. It also adds configuration-profile management from scripting and the first guards against two devices sharing a tag path.
The complete release notes are distributed with the module as RELEASE_NOTES_1.95.12.txt.
- Duplicate readings and duplicate Enterprise publishes. Every licence re-validation re-ran startup, leaving a second broker connection, tag writer, and forwarder live. The gateway reported one connection while two were delivering.
- Uplinks dropped on an EUI mismatch. A network server publishing a device EUI in a different form than the one on record discarded the reading outright, with no retry.
- Aloxy radio metrics stopped updating. Signal quality, spreading factor, and frame count were being discarded as duplicates of the Loriot feed they were built from, while decoded values kept flowing normally.
- Aloxy decode failures reported as successes. Real errors were overwritten with “No decode errors” — and separately, routine traffic was being recorded as errors.
- Aloxy check-ins lost on gateway shutdown. A race in message correlation could drop an uplink and then fail the following flush.
- Tag creation failures were never reported. The call returned success unconditionally, so a refused tag looked like a saved one.
- Downlink generation failing with a blank error. An encoder that omitted its port failed with an empty message; the cause is now named. A device with no tag path now logs one clear warning instead of a stack trace per uplink.
Behavior that changes
Section titled “Behavior that changes”- Uplink de-duplication runs everywhere. Previously Enterprise-only and off by default; now unconditional in all four modes. The
useMqttDeduplicationsetting no longer gates it. Aloxy traffic is exempt. - Message history ordering on upgraded gateways. Entries recorded before the upgrade sort after everything recorded since. Nothing is lost; fresh installs are unaffected.
- Tag paths must be unique. Two devices can no longer be pointed at the same path. Devices that already share one are preserved and stay editable.
- Duplicate device names are allowed. That rule guarded a field with no bearing on the tag path and never once fired; tag-path uniqueness replaces it.
- Loriot data rate is the bare spreading factor. The datarate tag now reads
9rather thanSF9 BW125 4/5, matching every other network server. Loriot only.
- Seven scripting endpoints. Create, edit, delete, and assign configuration profiles without touching the database, plus a read-only audit that reports every tag-path collision, orphaned row, and non-conforming name on the gateway.
- Profiles are validated when saved. Faults are caught at the write boundary with the exact path to the offending field, rather than surfacing later during downlink generation. A bad profile is skipped at startup instead of stopping the gateway.
- Two profiles ship with the module. Bearing Monitoring, a four-step TWTG vibration workflow, and Environmental Monitoring.