One thing I’ve seen a few times, usually when gps signal is low I think (phone in pocket, in the middle of a metal ferry, poor cell/gps reception for example), it’ll record a point or two thats way off the previous few points, like 1km+, so the tracks end up with jagged lines here and there. I’ve been able to fix this in the web app after by dragging those points into a plausible location on the route, or delete the points entirely. Would be nice to have some sort of filter on those type of points to help mitigate this. I know this could be a tough one to find a good balance. Maybe a settings to filter implausible points outside x distance/time from previous/next points?

hannes@homenas:/volume1/docker/dawarich$ sudo docker compose -f /volume1/docker/dawarich/docker-compose.yml up dawarich_db -d
validating /volume1/docker/dawarich/docker-compose.yml: (root) Additional property dawarich_db_pg_17 is not allowed
hannes@homenas:/volume1/docker/dawarich$

The yml file I posted cannot be read.

So I’m at a dead end.

Are there any current issues with passing data from Traccar into Dawarich?

Just asking so can maybe save my hair

Any nuances? Probably a Traccar problem but thought best to ask.

Cheers.

Compare your compose to the one from the next version and made appropriate adjustments, or just follow the updating guide, the changelogs always contain instructions on how to update in case of breaking changes

That is certainly an option; I can easily create a new backup.

But what should I enter in docker-compose.yml?

I currently have the following in there

version: '3'

services:
  dawarich_redis:
    image: redis:7.0-alpine
    container_name: dawarich_redis
    command: redis-server
    restart: unless-stopped
    volumes:
      - ./redis:/var/shared/redis

  dawarich_db_pg_17:
  image: postgis/postgis:17-3.5-alpine
  shm_size: 1G
  container_name: dawarich_db_pg_17
  volumes:
    - dawarich_db_data_pg_17:/var/lib/postgresql/data
    - dawarich_shared:/var/shared
  networks:
    - dawarich
  environment:
    POSTGRES_USER: postgres
    POSTGRES_PASSWORD: password
  restart: always
  healthcheck:
    test: [ "CMD-SHELL", "pg_isready -U postgres -d dawarich_development" ]
    interval: 10s
    retries: 5
    start_period: 30s
    timeout: 10s

volumes:
  dawarich_db_data:
  dawarich_shared:
  dawarich_public:
  dawarich_watched:
  dawarich_db_data_pg_17:

dawarich_db:
    image: postgis/postgis:14-3.5-alpine
    container_name: dawarich_db
    restart: unless-stopped
    environment:
      POSTGRES_USER: ${DATABASE_USERNAME}
      POSTGRES_PASSWORD: ${DATABASE_PASSWORD}
    volumes:
      - ./db_data:/var/lib/postgresql/data
      - ./db_shared:/var/shared

  dawarich_app:
    image: freikin/dawarich:0.25.8
    container_name: dawarich_app
    depends_on:
      - dawarich_db
      - dawarich_redis
    stdin_open: true
    tty: true
    entrypoint: web-entrypoint.sh
    command: ['bin/dev']
    restart: unless-stopped
    env_file:
      - .env
    volumes:
      - ./public:/var/app/public
      - ./app_storage:/var/app/storage
    ports:
      - 32568:3000

  dawarich_sidekiq:
    image: freikin/dawarich:0.25.8
    container_name: dawarich_sidekiq
    depends_on:
      - dawarich_db
      - dawarich_redis
      - dawarich_app
    entrypoint: sidekiq-entrypoint.sh
    command: ['sidekiq']
    restart: unless-stopped
    env_file:
      - .env
    volumes:
      - ./public:/var/app/public
      - ./app_storage:/var/app/storage

Should I leave the volumes and image entries or remove them?

Which version should I switch to? My initial plan was to go to 0.26.0.

Best regards

If you want to search by coordinates, try this:

points Point.where(lonlat: "POINT(0 0)")

Also, you can confirm your suggestion directly on the map: just select timeframe to include whole April of 2018, enable the Points layer and zoom the map out. The map also have selection tool which allows you to select an area and points inside it and bulk-delete them all.

Does anyone have any advice for me?

greetz dipsy

It appears to have been inconsequential, but the only way I found to clear the error was to restart the phone.

Anyway, hope this is helpful feedback. Thanks for creating this!

The reason I am asking is if you are importing individual variables, or importing the whole .env as environment variables?

 RailsPulse: Authentication is enabled but no authentication method is configured. This will deny all access.
[dawarich_app] 2026-03-05T20:26:40.617853028Z OIDC: Not configured (missing OIDC_CLIENT_ID or OIDC_CLIENT_SECRET)

.env file (edited for public) below:

DAWARICH_APP_PORT=3009
TIME_ZONE=America/New_York
APPLICATION_HOSTS=localhost,10.150.88.54,location.MYDOMAIN.com
RAILS_APPLICATION_CONFIG_HOSTS=localhost,10.150.88.54,location.MYDOMAIN.com
SELF_HOSTED=true
DATABASE_NAME=dawarich
POSTGRES_DB=dawarich

OIDC_CLIENT_ID=dawarich
OIDC_CLIENT_SECRET=gibberish
OIDC_ISSUER=https://auth.MYDOMAIN.com/realms/MYREALM
OIDC_REDIRECT_URI=https://location.MYDOMAIN.com/users/auth/openid_connect/callback
OIDC_PROVIDER_NAME="Sign in with Keycloak"
OIDC_AUTO_REGISTER=true
ALLOW_EMAIL_PASSWORD_REGISTRATION=false

Have you thought about a F-Droid release? That would be great

I started with dawarich 0.2xx.x and always selected the latest image in Container Manager. With the switch to 0.26.0, it is necessary to convert the PostgreSQL database from 14 to 17. I did not do this due to a lack of knowledge, and the containers no longer started. My approach at the time was to switch from the latest to 0.25.8. In hindsight, that was not a smart decision.

Now I wanted to take another look at the issue. I stopped the project and performed a complete backup of the four containers and the database. Then I opened docker-compose.yml and created the entry for the service and the volume. According to the instructions at Updating to PostgreSQL 17 with PostGIS | Dawarich , step 2 is to create a dump of the database via the console. Now don’t laugh at me, but which console do I have on the Synology?

Perhaps one option would be to set up a new project and re-upload the database, but to be honest, I want to manage the update.

greetz

dipsy

Is there anything else I can do?
(I actually would like to register a trip for that period, but it’s also polluted by mislocated points)

I’m new in this forum, but I’ve been using dawarich very successfully on my Synology NAS for about a year now.

Without this app, I would never have thought of tracking my location history. Unfortunately, I couldn’t get past version 0.25.8 because there were changes at the time that I couldn’t implement.

Now that so much has changed, family location, Android app, etc., I would like to try an update.

Unfortunately, the instructions refer to docker in the shell, which I cannot find in syno. I do have a Portainer.

Can anyone help me find the right approach to upgrade my version 0.25.8 to the current one?

greetz

dipsy

Let us know if it’s not working that way for you

This first shot is from 2 February. I alternated confirming and denying, to see if that changed anything.

The exact same ones have come back again, on 15 February.

Any chance of looking into this one please?

This is a good question, I do have to admit I kind of messed up the UX a bit in the app so I’ll have to fix that, but basically in Dawarich points, there is a property called track id, which is basically an id that can group points together, by pressing record, you’re not tracking, but it creates a new id and assigns it to the points the app makes, forming a 'track’. Then when you stop recording, it stops adding that track id to points. When you start recording again, it creates a new track id and forms a new track. I know it is really confusing so I’ll have to change it in the UI to not confuse users any further!

So to summarize, the record feature doesn’t actually record points, it just creates a track id for the points the app makes. I am honestly not sure how much this is actually used in Dawarich and whether Frey has plans to use it or not, but I just wanted to make sure my app supports it. But considering the feature is barely used, I might minimize it in the UI so it doesn’t look like the main tracker feature while all it does is create an ID for points to group together.

I hope this clarifies the use for the record feature.

Just a quick question. In the Tracker page, I have enabled Automatic Tracking in the Basic section, which I believe provides the same service GPSLogger did - uploading data points regularly - but what is the Recording section used for if I’m already using the Automatic Tracking feature?

Cheers

I do use Tail scale but that hasn’t stopped the others from working.

I am self hosting.