Repository navigation
Trndi 22.5
Trndi 22.5
Highlights
Dexcom Share sign-in works the way the other clients do. Both Dexcom drivers now sign in like pydexcom, xDrip+, Loop and nightscout-connect: authenticate the account first, then log in by account ID, with the old login-by-name kept only as a fallback. Newer Dexcom accounts answer the first step with an object rather than a bare ID, which the old code mangled; both shapes are read now. If you have been getting "Incorrect username or password" with a password that works in the Dexcom app, try again.
"Test connection" finds your Dexcom region. Dexcom reports an account on another region's server as a wrong password. After that error, Test connection now asks the other regions whether they accept the account and names the one that does.
Fewer requests and cleaner data from Dexcom. Every poll used to make an extra alert-settings request whose reply was thrown away; that is gone. Readings that Dexcom uploaded twice (G7 Direct-to-Watch) are dropped, and deltas are computed after the duplicates are removed. Asking for a larger window than Dexcom allows now clamps to the maximum instead of failing.
The range band shows its limits. The shaded high/low band behind the trend dots now has its two thresholds written as small figures at its left edge, so the band reads as "3.9 to 10" at a glance. The figures use your display unit, drop the decimal on whole numbers, move clear of the progress and account bars, and are hidden when the band is too shallow to hold both.
Everything else
Documentation
- The Dexcom guide gains a troubleshooting section: wrong region reported as wrong password, the 20-character password limit on Dexcom's sharing servers, sharer versus follower accounts, children's accounts, sharing with no followers, phone numbers as usernames, account lockouts after repeated attempts, and Dexcom Stelo not being readable.
- The manual describes the range band and its limit labels, and its "can't get readings" checklist points Dexcom users at the region note.
- The README screenshots are fresh 4:3 captures of the current build.
Under the hood
- The fake Dexcom Share server used by the tests serves the two-step login and the new account shapes, and the Dexcom helpers get their own unit tests.
- New CareLink tests, with matching support in the test server.
- CI builds with Lazarus 5.0RC1 on every platform. Linux amd64 and Windows stay on FPC 3.2.2; Linux arm64 and macOS move to FPC 3.2.4-rc2. The weekly toolchain drift scan keeps RC suffixes, so a partial bump shows up as two pinned releases.
📦 Important: Click "Show all X assets" at the bottom of this page to see all available files for download.
Linux (amd64 / x86_64)
Linux computers running on amd64 processors (Extensions supported)
- trndi_22.5.253_amd64.deb — Recommended for Ubuntu/Debian (best desktop integration)
- trndi-22.5.253-1.x86_64.rpm — Recommended for Fedora/RHEL (best desktop integration)
- Trndi-x86_64.AppImage — Universal AppImage (recommended for Arch, openSUSE, etc.)
- Trndi-linux-amd64.zip — Portable binary + languages
Linux (arm64 / aarch64)
Linux computers running on arm64 processors, including Raspberry Pi (Extensions supported)
- trndi_22.5.253_arm64.deb — Recommended for Ubuntu/Debian (best desktop integration)
- trndi-22.5.253-1.aarch64.rpm — Recommended for Fedora/RHEL (best desktop integration)
- Trndi-aarch64.AppImage — Universal AppImage (recommended for other distributions)
- Trndi-linux-arm64.zip — Portable binary + languages
macOS (Apple Silicon)
macOS computers with Apple processors (Extensions supported)
- Trndi-macos-silicon.dmg — Application (
.app) bundle for drag‑and‑drop install
Special requirements for macOS
- Open the .dmg and drag Trndi to Applications
- In Terminal, run:
xattr -c /path/to/Trndi.app - Replace
/path/to/...with the actual path - Now you can launch normally
Windows (x64)
Windows computers (Extensions supported)
- Trndi-windows-x64.zip — Portable binary + languages
- TrndiSetup.exe — Windows installer (recommended)
🔐 Package Verification
Linux packages (DEB/RPM) are cryptographically signed.
Verification:
- Download the signing key: trndi-signing-key.asc
- Import it:
gpg --import trndi-signing-key.asc - For DEB:
gpg --verify trndi_*.deb.asc trndi_*.deb - For RPM:
rpm --import trndi-signing-key.asc && rpm --checksig trndi-*.rpm
