What's new in v0.4.1 – v0.5.2

Version	Build	Date
v0.5.2	168	October 17, 2026
v0.5.1	158	October 16, 2026
v0.5.0	157	October 16, 2026
v0.4.1	152	October 14, 2026

Sign-in (v0.4.1, v0.5.0)

• Sign in with Google and Microsoft for accounts that have been linked in the profile – in the browser and in the Android app. See sign-in and security and the configuration.
• New switches TOTP_ENABLED and PASSKEYS_ENABLED turn the methods off server-wide; GET /auth/methods tells clients what is offered.
• Passkeys in the Android app: the server publishes /.well-known/assetlinks.json and accepts the app's origin. Since v0.5.0 the official app from Google Play is allowed out of the box; other builds via ANDROID_APP_CERT_SHA256. See passkeys in the Android app.
• Gravatar profile pictures, switchable per user and per server.

Vehicle costs (v0.5.0, preview)

Fuel, charging and other costs per vehicle with yearly summary, cost per kilometre, share by trip type and consumption by the full-tank method, plus a CSV import that detects Spritmonitor exports. Since v0.5.2 this is a preview feature that is only enabled in the :dev image (FEATURE_EXPENSES).

Reliable recording (v0.5.0, v0.5.1)

• If the answer to a recording start got lost, starting the same trip again no longer ends in "recording already active" forever.
• The app sends a trip ID generated on the device (clientTripId) with POST /tracking/start, so a repeated start of the same trip is unambiguous. See known issues.

Geocoding and map matching (v0.5.2)

• New Geocoding tab in the administration: Photon via the public server, your own server or Dawarich Atlas; map matching via Valhalla, OSRM or Atlas – each with a connection test, plus a system check. See geocoding and map matching.
• Map matching as a background job (only unmatched trips, retry failed ones, or all trips). The road route is only applied when plausible; raw GPS data stays unchanged, closed periods are skipped. Long trips are matched in sections of at most 100 km.
• The dashboard shows the road route of matched trips and optionally the original route.
• Redis Insight moved into Background jobs, preconfigured, linkable via REDIS_INSIGHT_URL.

Fixes

• Trips of drivers a vehicle is shared with were missing from the owner's statistics and counted as "unexplained". They now count as other drivers – as a total only, without destinations or categories.
• Without geocoding, addresses are skipped and the home location falls back to coordinates.

Upgrade

Migrations run automatically. To use map matching, set up a routing service under Administration › Geocoding and start a map matching run under Background jobs. Details: server changelog.