Release Notes

• 1: SPEKTRA Edge Release Notes
• 2: SPEKTRA Edge OS Release Notes

1 - SPEKTRA Edge Release Notes

Release notes for the SPEKTRA Edge platform services describe what changed for dashboard users and API developers since the previous production release.

For changes to the operating system running on your devices, see the SPEKTRA Edge OS release notes.

2 - SPEKTRA Edge OS Release Notes

SPEKTRA Edge OS is released separately from the platform services, and each device runs the version you select for it. These notes describe what changed for device operators in each version, newest first. They cover externally visible behavior only; build tooling and test changes are left out.

Devices do not patch themselves. Each release is built against current upstream packages, including their security updates, so upgrading a device is how it receives those fixes. To move a device to a newer version, see OS upgrades.

2.3.4

Released 31 August 2026.

• Security: Disabling the SSH server now takes full effect. On a device where you had turned SSH access off, the device could still accept connections on port 22 and start the server again on the next connection, because the socket that listens on the server’s behalf was left running. Disabling now stops that listener as well as the server itself, and enabling restores it. Devices running an earlier 2.3.x version with SSH disabled are affected and remain reachable over SSH; upgrade them to 2.3.4 to apply the fix.

2.3.3

Released 11 June 2026.

• Security: Refreshed the upstream packages the image is built from, picking up the security updates published since 2.3.2.

2.3.2

Released 12 May 2026.

• Networking: Docker now follows the device’s proxy settings. The proxy is written into the Docker daemon configuration and reapplied whenever it changes, so image pulls go through it.
• Upgrades: Downloading an OS image honors the configured proxy. It previously ignored the proxy, so upgrades could not complete on devices that reach the internet only through one.
• Networking: Everything that makes outbound connections — OS image downloads, health checks, and external address detection — now uses the proxy the device actually connected through rather than a fixed setting. If the device falls back to a different proxy, or to a direct connection, the rest of the system follows.
• Security: Proxy credentials are masked in device logs.
• Security: Dependency updates addressing known CVEs in the Go standard library, golang.org/x/net, pion/dtls, and xmlquery.

2.3.1

Released 20 February 2026.

• Networking: A wrong proxy address no longer strands a device. Fallback now also tries the default proxy the image was built with, and it no longer deletes the active configuration — which previously left devices that need a proxy unable to reach the platform at all.
• Networking: Devices with more than one Ethernet port boot reliably. Boot now waits for any interface to come online rather than all of them.
• Networking: Repeated invalid network configurations no longer fill the configuration partition. Each failure overwrites a single debug file instead of leaving a new one behind.
• Workloads: Workloads start on boot before the device connects to the platform, so containers come up even while the device is offline.
• Logging: Container logs reach the Logging service again on devices set up to export specific systemd units. Container entries were being filtered out before export.
• Logging: Less noise in device logs from Ethernet and modem state reporting and from the status LED daemon.
• Security: USB control rules that leave fields unset now render correctly.
• Time: Time synchronization no longer drops its sources in response to network manager events, which had caused intermittent sync failures.
• Provisioning: A provisioning approval request carries the device’s status, so you can see what you are approving.
• Devices: Raspberry Pi devices report their manufacturer and product name on firmware that does not supply them through DMI.
• Devices: Boot no longer stalls waiting for input when a TPM or other HAT module is attached.
• Remote access: SSH, SCP, log streaming, and port forwarding moved to the current platform protocol, and an SSH session now reports its exit status exactly once.
• Platform support: Jetson Linux updated from 36.4.0 to 36.4.4.

2.3.0

Released 17 July 2025.

• Platform: The base system moved to a newer Linux release, bringing an updated kernel and refreshed system packages.
• Monitoring: Devices report network interface metrics.
• Monitoring: Container metrics are reported for containers whose names do not follow the default naming scheme.
• Workloads: Compose files support environment variable substitution.
• Workloads: Containers report a Restarting state.
• Workloads: Pod status is reported even when Docker is not running, rather than going unreported.
• Workloads: Unused Docker images are no longer pruned on every run. Pruning happens once a day, and only when disk usage is above 75%.
• Networking: Uplink fallback can be turned off for devices that should stay on their primary uplink.
• Time: Time synchronization switched from ntp to chrony.
• Reliability: The hardware watchdog is enabled where the hardware provides one, with a software watchdog as fallback, so a hung device restarts itself.
• Upgrades: OS image downloads report their size so progress is accurate, are cached and verified by checksum, and allow more time to finish on slow links.
• Provisioning: Fixed the manual approval flow for devices awaiting approval.
• Security: Devices no longer crash when the fail2ban configuration is missing.
• Security: Encrypted devices return to Started once decryption finishes, instead of staying in the decrypting state.
• Logging: Empty log batches are no longer sent to the Logging service.
• Devices: Kernel warnings no longer clutter the device console.
• Devices: Shutdown hooks run on Fitlet3 hardware, because shutdown now goes through systemd instead of bypassing it.
• ZTNA: WireGuard is installed on the device to support ZTNA connectivity.