Notifications

hdtracker can tell you when something from your library comes out: a new episode or season, a cinema or home release, a game release – exactly what shows up under Recently released on the dashboard that day. Available from version 0.7.0.

Everything is set under Settings → Notifications. Notifications are off until you switch them on.

What and when

• Notify me: One by one sends a message per title, Together one summary a day. Off sends nothing, whatever targets you have.
• From: the hour of the day from which the messages go out. Only the day of a release is known, not the time.
• A single title can be muted with the bell on its page.

Targets

Targets is the list of where the messages go. Every target has a name and a switch – switched off, it keeps all its settings. Tap a target to change it, to send a test to exactly this target, or to remove it. You can have several targets of a kind.

This device

Push messages straight from hdtracker, without any other service.

• Needs HTTPS – see HTTPS and installing as an app.
• Android, computer: works in the browser and in the installed app. Installed as an app, the messages are shown as coming from hdtracker instead of from the browser.
• iPhone, iPad: only in the installed app (iOS 16.4 or newer): add hdtracker to the home screen, open it from there and add the device. iOS always shows the app icon, not the picture of the title.
• Add it on every device that should get messages. Tapping a message opens the title in hdtracker.

Pushover

Through your Pushover account – useful for devices that cannot get push messages from the app, or if you use Pushover anyway.

1. Log in at pushover.net. Your user key is at the top right of the page.
2. Create an application (Create an Application/API Token; name it e.g. “hdtracker”). Its API token is the app token hdtracker asks for.
3. In hdtracker: Add a target → Pushover, enter both and save. hdtracker checks them at Pushover right away.

Only to these devices is optional. Left empty, the message goes to all devices of your Pushover account; otherwise enter one device name, or several separated by commas. After saving, the names of your devices at Pushover are listed below the field – tap one to add it, tap again to take it out. Careful with typing: a name Pushover does not know means to all devices there.

The message carries the picture of the title and a link Open in hdtracker. Tapping the notification itself opens the Pushover app – that is how Pushover works and cannot be changed from outside.

ntfy

Through ntfy – the public service ntfy.sh or an ntfy server of your own. The message carries the picture of the title, the icon of hdtracker and a link to the title.

1. Install the ntfy app on your phone and subscribe to a topic there. Pick a long name nobody can guess (e.g. hdtracker-k3v9x2mq7p): on ntfy.sh a topic is open to everyone who knows its name – to read and to write.
2. In hdtracker: Add a target → ntfy, enter the same topic and save. Server stays https://ntfy.sh unless you run your own.
3. Use Test.

• Access token (optional): for a protected topic on your own server or with an ntfy account (tk_…). It is stored but never shown again.
• Attach the picture: the picture is uploaded to the ntfy server, so it also arrives where your phone cannot reach hdtracker. ntfy.sh deletes attachments after 3 hours – the text stays. On a server of your own, attachments have to be switched on; if they are not, the message arrives without the picture.
• Icon address (optional): ntfy only passes on the address of the icon, the phone loads it by itself. Left empty, it is the icon of your hdtracker – fine if your phone can reach hdtracker. If it cannot (hdtracker only in your home network), enter an address that is public, e.g. https://raw.githubusercontent.com/dvnkln/hdtracker/main/static/icons/icon-192.png.

Tapping the notification opens the title in hdtracker – which works wherever your phone can reach it.

Tried against real ntfy servers and ntfy.sh: message, picture, link and token arrive as described. How the notification looks in the ntfy app (icon next to the picture) was not checked on a phone.

Webhook

Sends every message as an HTTP POST to an address of your choice, with content you write yourself. That reaches Gotify, Home Assistant and anything else that accepts such a request.

• Address: where to send it (http:// or https://).

• Content: what is sent. These placeholders are filled in:

  Placeholder	Becomes
  {{title}}	the title of the message (the name of the title, or “New today: 3 titles”)
  {{message}}	the text, e.g. “S02E03” or the list of the day
  {{url}}	the address of the title (or the dashboard) in your hdtracker
  {{image}}	the address of the picture of the message; empty if there is none
  {{count}}	how many titles the message is about
  {{test}}	true for a test message, otherwise false

  If the content is JSON, the values are escaped for you – a quote in a title cannot break it – and it is sent as application/json; anything else is sent as plain text.

• Header (optional): one extra line such as Authorization: Bearer … for services that want a key. It is stored but never shown again.

{{url}} and {{image}} use the first https:// address of ORIGIN (otherwise the first address). The picture can be loaded without a login, through an address that opens only this one picture.

A template, tried against the real service:

Gotify – address: https://gotify.example.com/message, header: X-Gotify-Key: <application token>, content:

{
  "title": "{{title}}",
  "message": "{{message}}",
  "priority": 5
}

Other services work the same way: look up what their API expects and put the placeholders where title and text belong. Use Test – it shows what the other side answered if it refuses.

Who sees what

• This device: the message travels encrypted through the push service of your browser's maker, which cannot read it.
• Pushover: Pushover receives title, text, link and picture in readable form.
• ntfy: the ntfy server (ntfy.sh, or yours) receives title, text, link and picture in readable form – and so does anyone who knows the topic, unless it is protected.
• Webhook: whoever runs the address you entered receives what you put into the content.

Details: Privacy and security.