What's new in freddy: week of Aug 17, 2026
In short
- Suunto workouts now carry per-second speed, cadence, power, altitude, vertical speed and temperature, plus heart rate beat by beat.
- Garmin's running and cycling dynamics import from your data export, so ground contact time and vertical oscillation reach your older activities.
- New data no longer queues behind somebody else's large history import.
- The dashboard's “Latest data” tile reads your newest data day, and a separate row shows whether a sync is running.
Suunto workouts, second by second
Until last week a Suunto workout in freddy was a set of summary numbers and, since the week before that, the route you recorded. What was missing was everything that happened between the start and the finish.
That is now stored. Speed, cadence, power, altitude, vertical speed and temperature come through at roughly one reading a second, and heart rate comes through beat by beat rather than averaged into a tick. Suunto records these on three separate time bases, so freddy keeps them as three separate streams instead of forcing them onto a shared clock and misattributing values.
Workouts already synced come back once on their own to collect the streams, so there is nothing to re-import.
The practical difference is the kind of question you can ask. A summary tells your AI client that a run averaged a certain pace. The streams let it look at where that pace went, what your cadence did on the climb, and whether your heart rate was already drifting before the split you remember as the hard part.
Garmin activity dynamics, going backwards
Garmin records running and cycling detail inside the activity files themselves: ground contact time, vertical oscillation, vertical ratio, stride length, left and right balance, pedal smoothness, torque effectiveness. Garmin's API offers no way to hand those back for activities that already happened, so freddy could only collect them from the day you connected onwards.
The data export Garmin gives you does contain them. The Garmin source now has an Import activity dynamics button that reads that export ZIP and fills the detail in behind you, using the same file you may already have uploaded for the rest of your history.
The ZIP is opened in your browser, and only the running, cycling and swimming activity files are sent. The rest of the archive never leaves your machine.
Data stops waiting in line
Connecting a source with years of history produces a lot of data at once, and until last week all of it went into a single queue alongside everyone else's live data. If somebody started a large backfill, everything behind it waited. On the worst morning that meant a five hour delay before a night's sleep appeared.
Incoming data is now sorted by how old it is. Today's readings go first, and history fills in on whatever capacity is left over. Fresh data is back to arriving within seconds, and a large import no longer costs anybody else their morning.
A dashboard that agrees with itself
The Overview's Latest data tile was reading the last time a batch arrived rather than the newest day of data inside it. For sources that push from your phone the two are very different, so the tile could read “just now” directly above a coverage chart whose final bars were empty. Several people reported that as freddy lying to them, which is a fair description of it.
The tile now answers its own question: how old your newest data is, and which source it came from. Whether freddy is live or currently syncing moved to a row of its own, so neither figure has to stand in for the other.