Dawarich - Package Updates

[Package Updates]

[1.8.2]

• Update dawarich to 1.3.2
• Full Changelog
• Lite plan for Dawarich Cloud. Lite includes core tracking, map visualization (routes, points), stats, and the read API. Data view is limited to the last 12 months older data is archived but can always be exported. Pro-only features: Heatmap, Fog of War, Scratch Map, Globe View, Immich/Photoprism integrations, public stats sharing, and write API (update/delete). Lite users can still create points via the API. Self-hosted instances are unaffected all features remain fully available regardless of plan.
• Timed layer previews for Lite users on the map. Toggling a Pro-only layer (Heatmap, Fog of War, Scratch Map) shows it for 20 seconds with a countdown, then auto-hides with an upgrade prompt.
• Per-plan API rate limiting via rack-attack. Lite: 200 requests/hour, Pro: 1,000 requests/hour. Self-hosted instances are exempt. Rate-limited responses return 429 with Retry-After header.
• Archival warning notifications for Lite users approaching the 12-month data window: in-app notification at 11 months, email at 11.5 months, archived confirmation at 12 months.
• GET /api/v1/plan endpoint returning the user's current plan and feature availability.
• X-Total-Points-In-Range and X-Scoped-Points response headers on the points API, allowing clients to detect when data is being windowed.
• Branded OAuth buttons for Google and GitHub on the login page.
• Numeric-only strings passed to timestamp API parameters (e.g. start_at, end_at) are now treated as Unix timestamps directly. Previously they were passed through Time.zone.parse, which could return unexpected results. If you were relying on the old behavior for numeric strings, update your API calls accordingly.
• The user serializer now includes plan in the subscription object.

[Package Updates]

[1.8.3]

• Update dawarich to 1.3.3
• Full Changelog
• Points table now converts speed from m/s to km/h (or mph) using the user's distance unit preference. Previously raw m/s values were displayed with a "km/h" label. #​2337
• Digest list API (GET /api/v1/digests) now returns distance as a structured object with meters, converted, and unit fields, matching the detail endpoint. Previously it returned raw meters, causing clients to display incorrect values. Breaking change: the distance field changed from an integer to an object. #​2336
• Dead documentation links in v0.26.0 changelog entry now point to the correct URLs. #​2344
• Filter out Immich and Photoprism api keys from logs to prevent accidental exposure. #​2368
• Fix foreign key violation when deleting users with place_visits referencing visits.
• Fix reverse geocoding job failing on points with nil timestamp or lonlat.
• Fix unsupported archive format generating Sentry noise instead of a user-friendly notification.
• Fix deadlock in reverse geocoding places upsert under concurrent Sidekiq workers.
• Reduce Redis disk I/O by relaxing RDB snapshot frequency. Previously the default save 60 10000 rule caused a snapshot every ~60 seconds due to Sidekiq polling, generating tens of terabytes of disk writes over weeks. New defaults: snapshots every 15 minutes (10+ changes) or 5 minutes (100+ changes).
• Reduce default Sidekiq concurrency from 10 to 5 threads. Most self-hosted instances don't need 10 workers and the extra threads increase Redis polling traffic.

[Package Updates]

[1.8.4]

• Update dawarich to 1.3.4
• Full Changelog
• Redesigned onboarding modal with two paths: "I have data" (inline file import) and "Start tracking" (app download + QR code). New users with existing location data can now start importing within 2 clicks of signing up.
• Onboarding completion is now persisted server-side (settings.onboarding_completed) instead of relying solely on localStorage, preventing the modal from reappearing after browser data clears.
• Route opacity data migration now runs as a background job instead of inline during migration, improving deployment reliability for large instances.
• Fix admin and supporter tooltip overflowing the page on narrow screens. #​1449
• Fix date navigation arrow tooltips overlapping with the navbar on map pages. #​2229 #​2100
• Fix infinite loading spinner when a trip has no points in its date range. #​2293
• Fix Insights monthly digest panels disappearing when switching months. #​2305
• Fix suggested visit confirm/decline not removing the visit from the list. #​2307
• Fix Stats page reloading when clicking "countries, cities" link. #​2270
• Fix map base layer selection not being restored after page reload (Maps v1). #​2093

[Package Updates]

[1.9.0]

• Update dawarich to 1.4.0
• Full Changelog
• Family page now contains a map with family members markers on it.
• Visits page now have "Confirm all" and "Decline all" buttons to quickly confirm or decline all visit suggestions at once.
• Updated look and feel
• The point counting was changed to be more efficient on bigger accounts.
• Redesigned raw data archival system for large instances (10M+ points). Archival now runs per-user via Sidekiq jobs instead of a single sequential process, uses PK cursor-based queries instead of full table scans, and processes in 50K-point chunks with 5K-batch flag updates to minimize DB lock contention. Inline verification removed in favor of daily spot-checks. FK constraint changed from ON DELETE nullify to ON DELETE RESTRICT to prevent cascading updates on large tables.
• • Fix Lite plan archival warnings sending all three notifications (11-month, 11.5-month, and 12-month) simultaneously when a user's oldest data already exceeds all thresholds. Now only the most severe warning is sent, and lower thresholds are marked as already notified.
• • Fix intermittent 502/504 errors caused by User.reset_counters(:points) running synchronously during OwnTracks, Overland, and API point creation. The full COUNT(*) query blocked web workers for 60500+ seconds on large accounts, starving all other requests. Counter reset now runs as a background job.
• • Misconfigured Prometheus settings will no longer litter logs with error messages, it will make multiple attempts to connect instead and then stop.
• • One of previous versions removed a database index making points upload very slow. The index is now added back to fix the issue.

[Package Updates]

[1.10.0]

• Update dawarich to 1.5.1
• Full Changelog
• Fix points and tracks interactions on Map v2 being unresponsive after the latest update.
• Fix creating demo data from the onboarding modal.
• Fix navbar for cloud trial users.
• Reset months stats instead of deleting when there is no data.
• GPS noise filtering. An automatic system to detect ahd filter out points with unrealistic speeds, altitudes, or sudden jumps.
• Support for signing in via web view using our Android app.
• On the map settings page user now can enable and disable map layers.
• Onboarding modal now offers a third option to load demo data (3 days in Berlin, ~1000 points) so new users can instantly see what the map looks like. Demo imports bypass trial limits, are clearly labeled with a "Demo" badge, and can be deleted from a banner on the map page or from the imports list.
• New tool to the Map V2 tools: The "Day per Country" button will open a modal showing a breakdown of how many days the user has spent in each country, based on their points data. This is calculated by grouping points by country and counting unique days with at least one point in that country.
• [Cloud] The point creation API endpoints are being excluded from the default Lite/Pro rate limits (200/1,000 requests/hour). They now have general rate limits of 10,000 requests/hour.

[Package Updates]

[1.11.0]

• Update dawarich to 1.6.0
• Full Changelog
• Immich users can now enrich their photos with geodata.
• Users can now optionally enable two-factor authentication (2FA) for their accounts in Settings > Two-Factor Authentication. Supported methods: TOTP apps (Google Authenticator, Authy, etc.) and backup codes. Once enabled, users will be prompted for a 2FA code on login. This adds an extra layer of security to protect your location data.
• Fix OIDC account linking failing when the email from the identity provider has different casing than the existing Dawarich account #​1983.
• Fix confirmation dialogs being ignored when clicking "Cancel" destructive actions (account deletion, import/export deletion, place deletion) fired regardless of user choice due to Rails UJS and Turbo both handling the same click #​1978.
• Fix Year in Review share link being empty when toggling public access #​2418.
• Fix address field on Points page being empty when geodata properties are unavailable #​2419.
• Fix Stats API returning the same country/city count for every year instead of per-year counts #​2280.
• Fix flyover countries (with no visited cities) still showing in monthly stats views #​2423.
• Fix importing Google Timeline files. #​2427

[Package Updates]

[1.11.1]

• Update dawarich to 1.6.1
• Full Changelog
• Info badge on import form suggesting users zip large files (200MB+) before uploading.
• Missing SVG icons for activity breakdown (ship, circle).
• Fix compressed zip files failing to import with "No such file or directory" error. Rubyzip needs to re-open the source zip for compressed entries, but the temp file could be garbage collected before extraction completes #​2446.
• Fix anomaly filter crashing on large imports (millions of points) due to loading all points into memory at once. Speed-based filtering now processes data in monthly chunks.

[Package Updates]

[1.12.0]

• Update dawarich to 1.7.0
• Full Changelog
• Monthly digest emails. On the 2nd of each month users receive an email summarizing the previous month with an ASCII-rendered overview (distance, active days, countries, cities), a weekly pattern bar chart, a daily distance sparkline, top countries and cities by time spent, first-time visits, and a month-over-month trend comparison. Enabled by default; opt out at Settings Email Preferences.
• Visible, selectable family invitation URL under each pending invite on the family page, so self-hosted instances without SMTP can still share the link #2438.
• User-configurable GPS noise filtering in Map v2 Settings. The accuracy threshold (previously a hardcoded 100 m) is now adjustable from 501000 m, and the filter can be disabled entirely, so trips on trains or other weak-signal data sources no longer get their legitimate points stripped out. A "Re-evaluate past data" button clears existing anomaly flags, re-runs the filter with the new settings, and rebuilds tracks/stats/digests; a separate "Recalculate tracks & stats" button rebuilds derived data without touching anomalies. Fixes #2480.
• S3 storage can now be used in self-hosted mode. It's compatible with S3-like backends, such as MinIO, Ceph, or Cloudflare R2. To enable S3 storage, set STORAGE_BACKEND=s3 and provide AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION, and AWS_BUCKET. For S3-compatible backends, additionally set AWS_ENDPOINT_URL (or AWS_ENDPOINT).
• Fix yearly digest emails not being sent automatically. The scheduling job existed in the codebase but was never wired into config/schedule.yml, so no year-end emails went out. Yearly digests now fire on January 2nd at 06:00 UTC.
• Fix visit name being overwritten by the location name when updating a visit via the map popup. The custom name typed into the "Visit Name" field is now preserved; the place name is only used as a default when the user leaves the name blank #1915.
• Fix the Map v2 replay slider showing times in the browser's local timezone instead of the timezone configured in Settings. Day buckets and the minute-of-day index are now computed in the user's timezone so the replay scrubber matches the rest of the app #2457.
• Fix country name canonicalization on the Stats page producing wrong results (e.g., France showing as "Scarborough Reef") when the countries table has multiple rows sharing the same ISO code #2434.
• Fix Stats dashboard charts stuck on "Loading..." for some years due to duplicate Chartkick element IDs when rendered inside cached year partials #2453.
• Fix map date-navigation prev/next buttons always shifting by one day; they now shift by the currently selected interval #1736.

[Package Updates]

[1.12.1]

• Update dawarich to 1.7.1
• Full Changelog
• API endpoints for mobile authentication.
• New ingest endpoint POST /api/v1/traccar/points for the Dawarich mobile client and any compatible Traccar-style tracker. Accepts a single nested-JSON location payload, upserts the point, refreshes the points counter, and triggers anomaly filtering, realtime track regeneration, and the live broadcaster exactly like the OwnTracks and Overland endpoints.

[Package Updates]

[1.12.2]

• Update dawarich to 1.7.2
• Full Changelog
• rails_pulse performance monitoring has been removed entirely. The gem, its initializer (config/initializers/rails_pulse.rb), the /rails_pulse route mount, the scheduled RailsPulse::SummaryJob and RailsPulse::CleanupJob cron entries, and all rails_pulse_* tables are gone. A new migration DropRailsPulseTables cleans up existing installations on upgrade. This resolves a class of upgrade failures where the rails_pulse_* tables ended up missing/half-applied on production. (#2549)
• Swagger docs for all the recent API additions and changes, improving API discoverability and client generation. The full OpenAPI spec is available at /api-docs.
• Map v2: Delete button on the point info card. Selecting a point now offers an immediate Delete action (with confirm dialog), matching the long-standing Map v1 behavior. The deleted point is removed from the points layer in place without a full reload.
• Monthly and yearly digest emails now convert distance from stored meters to the user's preferred unit (km/mi). Previously the raw meter value was shown next to the unit label (e.g. 500000 km instead of 500 km).
• Map (Leaflet): route lines no longer revert to their pre-move shape when an unrelated point is deleted after dragging another point. The dragend handler was failing to update the marker array because it looked for the controller in the wrong place. (#1797)
• Track creation now caps a single track's distance at 100,000 km (with a logged warning) instead of silently truncating at the legacy 999,999 m limit. Long-haul journeys are no longer collapsed to ~1000 km. (#1693)
• Dev container: bind-mount the project root into the container so bundle install can locate the Gemfile. Previously only sub-paths were mounted, leaving /var/app/Gemfile missing. (#1804)
• Map v2: photos without GPS metadata (latitude/longitude null) no longer render as markers at Null Island (0, 0) they are now correctly excluded from the photos layer. (#2464, #2465)

[Package Updates]

[1.12.3]

• Update dawarich to 1.7.4
• Full Changelog
• Cloud Trial users are no longer limited to 10 MB import files.
• Self-hosted instances no longer need to set JWT_SECRET_KEY. #2570
• QR sizes are fixed. #2479
• Family owners can now remove other members directly from the family page. #2555
• Insights and statistics now agree on the number of countries visited per month. #2581
• The default password for the demo account has been changed to safepassword. The old default password prevented seeds from running due to the new 12-character minimum password length validation. Existing users were not affected. #2593
• Polarsteps support locations.json and segment-array exports now import directly.
• /metrics endpoint: if you scrape Prometheus metrics, set METRICS_USERNAME and METRICS_PASSWORD in your environment. With them unset, /metrics now returns 503.
• Google Phone Takeout location-history.json now imports reliably. (#2437, #2587)
• Upgrades from older versions ( 1.3.1) no longer crash during db:migrate. (#2576)

[Package Updates]

[1.12.4]

• Update dawarich to 1.7.5
• Full Changelog
• Manual transportation-mode correction per segment in the map view, with a one-click reset to auto-detection. Manually-corrected segments are preserved across re-classification. #2405
• Per-user transportation-mode allowlist in the map settings panel. Disabled modes are excluded from auto-detection going forward; existing tracks stay as they are until you press "Re-classify my history". #2405
• Track duration and average speed are now refreshed whenever a track's path is rebuilt (e.g. after a merge), instead of keeping their pre-merge values. To heal tracks already affected, click Map v2 Settings Recalculate tracks & stats once after upgrading.
• Visited-country statistics no longer count countries that were merely flown over. Points moving faster than 500 km/h are now excluded from the country and city aggregation. Trains and high-altitude cities (Denver, Mexico City, La Paz, Lhasa, ) continue to count as visited. Previously-saved monthly stats are not recomputed automatically re-run stats calculation to refresh historic months. #1917
• Server-rendered timestamps (Points, Places, Imports, Exports, account settings, trial banner) now display in the user's profile timezone, matching the Maps tab. Previously, the time and tooltip could fall back to the server's default zone, drifting by hours. Invalid stored timezones no longer raise. #1824
• "Start Reverse Geocoding" now actually re-runs for every point in your database previously it silently skipped any point that had already been geocoded, even though the button promised a full re-run. #2141
• Map v2 date-navigation arrows (< / >) now shift the time window by exactly one day, matching Map v1. Previously they shifted by the current window width, so a 00:0023:59 selection paged back by 23h59m instead of 24h. #2548
• Visit suggestions are now generated from live tracking (Dawarich iOS app, OwnTracks, Overland, Traccar), not just from imports. Previously, only imported data triggered visit detection. Visit suggestion still requires a configured reverse geocoder (Photon, Geoapify, Nominatim, or LocationIQ). #1749, #1966
• "Start Reverse Geocoding" and "Continue Reverse Geocoding" now enqueue Sidekiq jobs in bulk batches of 1,000 instead of one round-trip per point. For large databases (millions of points) this drops the enqueue phase from minutes to seconds. Per-point geocoder rate-limit behavior is unchanged. #2141
• Trips that cross midnight in the user's timezone now contribute distance and time to both calendar days, instead of being attributed entirely to the day they started. The timeline day summary, the calendar heat grid, and adjacent-day km totals all reflect the trip on each day it actually spans. #2544, #2546

[Package Updates]

[1.12.5]

• Update dawarich to 1.7.7
• Full Changelog
• Prometheus metrics backend migrated to Yabeda.
• Fixed monthly stats failing with a "Stats update failed" notification when the month's distance exceeded the int4 limit (2,147,483,647 m 2.15M km). Affected months stayed stuck on the prior value until recalculated. #1996
• 500 error on the imports page. #2683
• Redis no longer balloons (multi-GB) when browsing photos with Immich or Photoprism connected. Photo thumbnails are no longer copied into the server-side Redis cache; the browser caches them directly via Cache-Control instead. #1609
• Map v2 timeline: bulk Confirm and Decline in selection mode, capped at 500 visits per request.
• Trip Recalculate button: refresh path, distance, and visited countries on demand. The page updates automatically when it finishes; repeat clicks within 60 seconds are ignored. #2478
• Google's "Timeline Edits.json" type of Takeout export is now recognized and imported directly.
• Monthly stats now bucket points by your local timezone instead of UTC fixes phantom day-1 spikes from overnight imports and undercounts near month boundaries. #2546
• Track generation no longer creates duplicate tracks multiple background jobs (daily, realtime, recalc, import) could previously produce the same track per time window, leaving 23 copies on your map. Run Map v2 Settings Recalculate tracks & stats once after upgrading to recompute from the merged points. #2677
• Transactional emails now build links with HTTPS, fixing reset links that arrived as http:// even when the site was served over HTTPS via reverse proxy. #1469

[Package Updates]

[1.12.6]

• Update dawarich to 1.7.8
• Full Changelog
• Self-hosters running OIDC-only sign-in: the ALLOW_EMAIL_PASSWORD_REGISTRATION env var no longer doubles as a login gate. Email/password sign-in is now controlled by the new ALLOW_EMAIL_PASSWORD_LOGIN env var (defaults to true). To preserve OIDC-only sign-in after upgrade, set ALLOW_EMAIL_PASSWORD_LOGIN=false.
• Visit detection now uses PostGIS spatial clustering for faster, more accurate stops; the iteration-based detector is removed.
• Places are now strictly per-user. Suggestion, photo-geotagging, and reverse-geocoding all use your own place catalogue exclusively; no places are shared across users. Existing shared places have been backfilled to their most-active owner. Self-hosted single-user instances see no behaviour change.
• "Re-run detection on full history" button under Settings Visits. Confirmed visits and named places are preserved.
• Account lockout after 10 failed 2FA attempts (30-minute auto-unlock or password reset). Applies to both the mobile API (POST /api/v1/auth/otp_challenge) and the web sign-in flow. Backup codes still work during a lockout so users with one stored can recover immediately. A notification email is sent to the account owner when a lockout is triggered. #2575
• Fix support of FIT files from Garmin Connect. #2686
• Email/password login is now shown alongside the OIDC button on self-hosted instances by default, instead of being hidden whenever OIDC is configured. Operators who want to enforce OIDC-only sign-in can set ALLOW_EMAIL_PASSWORD_LOGIN=false. See the upgrade note above. #2495
• GPX import now streams the file rather than loading the entire XML into memory, so multi-hundred-MB GPX files (e.g. long-running activity exports) no longer OOM the Sidekiq worker. #2296
• Tracks recorded by multiple devices on the same account (phone + watch + GPS unit) no longer get merged into one zigzagging track on the map. Each device's points are kept on their own track, and Map v2 draws routes per-device. #337, #1726
• Importing a Google Records.json export with positions from more than one device no longer "teleports" between devices and inflates distance travelled; points are scoped per-device using Google's deviceTag. #337

[Package Updates]

[1.12.7]

• Update dawarich to 1.7.9
• Full Changelog
• Run Settings Recalculate tracks & stats to merge pre-existing overlapping tracks. #2463
• Visit detection now creates one Place per visit (was up to 25 candidates). Use GET /api/v1/visits/:id/possible_places and POST /api/v1/visits/:id/select_place for alternatives. The place_visits table will be dropped in a follow-up release.
• Map v2 Hexagons layer (Pro) H3 cell heatmap, zoom-adaptive resolution. #2568
• Download a trip's points as GPX or GeoJSON from the trip page. #2400
• OIDC PKCE support via OIDC_PKCE_ENABLED=true (off by default). #2282
• Self-hosted instances no longer 500 on Stats/Insights when JWT_SECRET_KEY is unset; /trial/upgrade now redirects home. #2682
• Family members' positions update in real time instead of every 60 s. #2733
• Immich/Photoprism photos reappear after a transient empty response (no more 30-minute hidden window). #1071, #784
• Tracks no longer split into overlapping segments when points arrive late/out of order; same-device overlaps auto-merge on the next run. #2463
• Insights "Top Visited Locations" no longer underreports days for multi-month totals (e.g. 133 days rendered as "4 days"). #2743

[Package Updates]

[1.12.8]

• Update dawarich to 1.7.10
• Full Changelog
• Stops shorter than 5 minutes are no longer suggested as visits by default. Change the threshold under Map V2 ->Settings -> Visit detection if you want shorter stops included.
• Smart density fill now works correctly (it was broken in 1.7.81.7.9). You may see more visit suggestions, especially on days when your tracker recorded points unevenly.
• Map v2 family member markers show name + last-seen datetime on hover.
• Map v2 area info card exposes an Edit button that opens the area modal pre-filled rename and resize existing areas without redrawing. Backed by a new PATCH /areas/:id route.
• Map v2 selection tool: Delete N Anomaly Points button appears when the selection contains anomaly points, so you can clean up GPS noise without touching real points.
• New Minimum visit duration setting under Settings Visit detection (160 minutes, default 5). Raise it to ignore short drive-bys; lower it to catch brief errands. Replaces the hardcoded 3-minute floor that was the same for everyone in 1.7.81.7.9.
• Stats page no longer 500s after deleting an import or recalculating a month with no points. #2682
• New tracks now honor the user's enabled transportation modes during initial detection. Previously only the Recalculate path respected disabled modes, so a user who turned off (e.g.) cycling still saw cycling assigned to freshly built tracks. #2787
• Visit detection no longer suggests stops at places you only drove past. Clusters where the device was moving faster than walking pace between real GPS points are rejected, so road centerlines on busy arterials stop showing up as "visits" to Kent Street / Leach Highway / etc. #2736 #2775
• Visit detection now respects your Visit time threshold setting when deciding where one visit ends and the next begins. The setting was previously ignored and always treated as 30 minutes.

[Package Updates]

[1.12.9]

• Update dawarich to 1.7.11
• Full Changelog
• Onboarding "Load demo data" now seeds a fully populated /map/v2 instantly: 30 days of Berlin + a Prague-weekend trip, ~80 visits with tags and places, and stats anchored to the current calendar month. "Remove demo data" wipes everything in one click while preserving anything you've confirmed, edited, or built on top of (visits, trips, places, tags adopted by user action stay).
• Visits can now be manually assigned to one of your saved areas. When you do, the visit takes the area's name automatically unless you've already given it a custom name, or you've also picked a place (a place name wins over an area name). Available via API now; UI to follow. #2577
• Two unused indexes on the points table are dropped on upgrade; on large self-hosted instances this frees several GB of disk.
• Areas now validate their geometry: radius must be greater than 0, latitude must be within -9090, and longitude within -180180. Invalid values are rejected instead of silently saved.
• Bumped bundled gems (aws-sdk, devise, jwt, httparty, and others) to close 9 known CVEs. Self-hosters get the security fixes by upgrading.
• Map v2 Timeline calendar now lights up days that have raw points even before Track or Visit generation has caught up, matching the Insights Activity Overview calendar. #2579
• Reverse-geocoding flood: duplicate per-point enqueues are now coalesced for 24 h via a Redis dedup key, retries are capped at 3, and the nightly sweep bypasses (and clears) the dedup so points whose retries were exhausted or whose key still lingers are picked up on the next run.
• Map v2 visits layer now honours the selected date range. Since 1.7.10 the viewport-bounded visits fetch silently dropped the start_at/end_at filter on the backend, so all visits inside the viewport were rendered regardless of the date filter. #2817
• POST /api/v1/visits no longer links a new visit to a place owned by another user. Passing a foreign place_id is ignored the visit gets a place owned by the requester at the requested coordinates, and the response no longer echoes the other user's place id or coordinates.
• Map v2 settings panel: "Apply Settings" now actually saves your changes. Points rendering mode, speed-colored routes, live mode, and fog-of-war toggles all persist on click and reload. Apply/Reset buttons moved above the Transportation Mode section so they sit inside the outer form. #2680

[Package Updates]

[1.13.0]

• Update dawarich to 1.8.0
• Full Changelog
• "What's New" changelog notices in the navbar. Self-hosted users are asked once before any external request and the widget loads only after opt-in; Cloud users see it automatically. Toggle anytime in Settings General, or point it at your own instance with CHIBICHANGE_WIDGET_HOST and CHIBICHANGE_SLUG. ChibiChange will be open-sourced soon.
• Sign in with Apple on the web (Dawarich Cloud only)
• Opt-in non-ML "stay-point" visit detection, behind the per-user stay_point_detection flag (default off). A single-pass dwell detector that fixes the old clusterer's slow-stay false-rejects and dead-battery gap splits, and stores a 0100 confidence score per suggested visit (exposed via the API). #2832
• Map v2 Timeline: every visit now has a search icon to find the real place by name a type-as-you-go geocoder (Photon) lookup biased to the visit's location, each result showing category, distance, and nearby saved Areas. Pick a result to label the visit or create a new place on the spot; choosing a far-away place asks before relocating it.
• Declining a visit is now deleting a visit. Decline (per-visit, "Delete all" for a day, the bulk bar, and the Map v2 area-selection card) is replaced by Delete, which confirms and removes the visit entirely; your location points are always kept. The "Declined" filter and Restore action are removed.
• Globe view is enabled by default for Pro and self-hosted users.
• The map's Places layer no longer floods with a marker for every suggested visit it now shows only places you created manually, attached to a confirmed visit, or tagged. GET /api/v1/places accepts a filter parameter to override: all, manual, confirmed, or tagged.
• Deleting a single point on the map (via its info card) now redraws the connecting route immediately instead of leaving a stale line until reload. (#2844)
• The official Traccar client app is now supported directly. Its payload nests coordinates, battery and activity one level deeper than Dawarich's own client, so its points were silently dropped; both shapes are now accepted. #2741
• Deleting an import now also removes any tracks left with no points, instead of leaving empty "ghost" tracks on the map and timeline. Connected maps drop the removed track right away. #2825

[Package Updates]

[1.13.1]

• Update dawarich to 1.8.1
• Full Changelog
• Fog of War (Map v2) can now reveal explored areas per hexagon instead of per point, using precalculated monthly statistics. Switch between "Per point" and "Per hexagon" in the map settings panel. (#2899)
• The suggested-visit card no longer promises alternative suggestions that never arrive; it now points to the visit's search button for picking a different place (#2852)
• Bumped the oauth2 gem to 2.0.22 to close a known credential-leak advisory (GHSA-pp92-crg2-gfv9) on the Google/GitHub sign-in path
• Globe view is enabled by default for Pro and self-hosted users.
• Deleting an import no longer gets stuck on an endless spinner: failed deletions revert to a retriable state, and imports stalled in "Deleting" for over an hour show a retry button (#2835)
• Insights no longer report a "new country visited" for border-crossing geocoding blips that the statistics pages already filter out; the yearly digest now applies the same rule as the monthly one (#2727)
• OIDC login no longer fails with "undefined method 'with_indifferent_access'" when OIDC_ISSUER is set to the full discovery URL the trailing /.well-known/openid-configuration is now stripped automatically (#2056)
• Importing files containing invalid UTF-8 bytes (e.g. Windows-encoded degree signs in Google Timeline phone exports) no longer fails with "invalid byte sequence in UTF-8". Applies to the JSON-based importers as well as OwnTracks and TCX (#2772)
• Deleting a family no longer fails with a 500 error when location-sharing requests exist for it (#2916)
• Self-hosted: the /admin/flipper feature-flag UI is no longer rate-limited, which made it unusable after a few clicks (#2897)