(***) In notifications

Anton Tananaev2 days ago

What event type?

bravo.1232 days ago

telegram

Anton Tananaev2 days ago

Telegram is not an event type. It's a delivery channel.

bravo.1232 days ago

Geofence entered , and any other .

Anton Tananaev2 days ago

It should work if you're using the default templates.

bravo.1232 days ago

I tried a clean docker installation, I tried downloading templates from git and substituting them locally, still the asterisks..

Anton Tananaev2 days ago

You don't need to download anything.

bravo.1232 days ago

I'll try again tomorrow. But as I said, I completely deleted the image and did a clean install, and it still doesn't work. I don't understand how to track this down; there's nothing in the logs.

ftc2 days ago

I don't understand how to track this down

I tracked it down by debugging in source code. There is no other way I know of, since traccar does not produce log messages on missing templates.

Please provide the steps how you're testing if your notifications work. See also: https://github.com/traccar/traccar/issues/5702

bravo.123a day ago
  1. docker system prune
  2. docker-compose.yml :
services:

  database:
    image: timescale/timescaledb:latest-pg16
    restart: unless-stopped
    environment:
      POSTGRES_DB: $DB_USERNAME
      POSTGRES_USER: $DB_DATABASE_NAME
      POSTGRES_PASSWORD: $DB_PASSWORD
      TIMESCALEDB_TELEMETRY: "off"
    volumes:
      - /opt/traccar/data:/var/lib/postgresql/data

  traccar:
    image: traccar/traccar:latest
    restart: unless-stopped
    depends_on:
      - database
    environment:
      CONFIG_USE_ENVIRONMENT_VARIABLES: "true"
      DATABASE_DRIVER: org.postgresql.Driver
      DATABASE_URL: jdbc:postgresql://database:5432/traccar
      DATABASE_USER: $DB_USERNAME
      DATABASE_PASSWORD: $DB_PASSWORD
    healthcheck:
      test: [ "CMD", "wget", "-q", "--spider", "http://localhost:8082/api/health" ]
      interval: 2m
      timeout: 5s
      start_period: 1h
      retries: 3
    ports:
      - "8082:8082"
      - "5055:5055"
#      - "5000-5500:5000-5500"
    volumes:
      - /opt/traccar/logs:/opt/traccar/logs

  autoheal:
    image: willfarrell/autoheal:latest
    restart: always
    environment:
      AUTOHEAL_CONTAINER_LABEL: all
      AUTOHEAL_INTERVAL: 60
      AUTOHEAL_START_PERIOD: 3600
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro

3 . docker compose pull
4. docker compose up -d
5. docker exec -ti a365acd47d59 sh
6. cd conf
7. Add

    <entry key='notificator.types'>telegram,traccar,web</entry>
    <entry key='notificator.telegram.key'>XXXX:YYYYYYYYYYYYYYY</entry>
    <entry key='notificator.telegram.chatId'>-ZZZZZZZZZZZ</entry>

to traccar.xml
8. Restart container.
9. Add Notifications

2025-11-10_12-54.png
10 . Telegram

2025-11-10_12-55.png

bravo.123a day ago

11.
2025-11-10_13-00.png

Test button will return this and that's expected.

ftca day ago

Hi @bravo.123

Since 6.9.0 the content of the test message is now "(***)" instead of "Test message". With the change to the notification templates, the traccar developers decided to remove the test.vm template.

I was also tricked by the same change and spent several hours of debugging until I figured out, that simply, the test message template was removed without notice.

So there is no way to check with the "TEST MESSAGE" if the templates are configured correctly, at the moment.

You need to check by having a device triggering a real alarm or creating a mock alarm.

Tell me if you need further infos.
All the best

bravo.12313 hours ago

Oh, thank you so much! It's just that after the update, I also had real alerts with asterisks. That's why I started to figure it out. Not an obvious behavior in my opinion. It would be better if real messages were sent.