Sink

Scrobble sink modules that send playback events to trackers (Trakt, SIMKL, MDBList).

These pages document scrobble sinks.

Sinks send normalized playback events to trackers.

End users

If you want setup steps, use Watcher.

Supported sinks

• Sink: Trakt

• Sink: SIMKL

• Sink: MDBList

How sinks are used

1. A watch provider emits a ScrobbleEvent.

2. The dispatcher filters and dedupes it.

3. Each sink gets send(event).

Sinks should stay policy-free.

The dispatcher owns filtering decisions.

Configuration touchpoints

User-facing config lives in Settings → Scrobbler.

In config.json, selection typically uses:

• scrobble.mode (watch or webhook)

• scrobble.watch.sink (Watcher mode)

Reference: Configuration (config.json).

Common failure modes

Auth failures

Fix auth in Settings → Authentication.

Then restart scrobbling.

Matching failures

Missing external IDs cause “skip” behavior.

Fix metadata on the media server.

Rate limits

You may see gaps during API outages.

Events resume on the next playback changes.

Power users