sidebar_position	title	toc_max_heading_level
2	Overview	3

import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import CodeBlock from '@theme/CodeBlock'; import SchemaLink from "../../src/components/SchemaLink"; import AIOExample from "../../src/components/AIOExample";

import AIOConfig from '!!raw-loader!../../../config/config.json.example'; import ChromecastConfig from '!!raw-loader!../../../config/chromecast.json.example'; import DeezerConfig from '!!raw-loader!../../../config/chromecast.json.example'; import JellyfinConfig from '!!raw-loader!../../../config/jellyfin.json.example'; import JriverfinConfig from '!!raw-loader!../../../config/jriver.json.example'; import KodiConfig from '!!raw-loader!../../../config/kodi.json.example'; import LastfmConfig from '!!raw-loader!../../../config/lastfm.json.example'; import ListenbrainzConfig from '!!raw-loader!../../../config/listenbrainz.json.example'; import MalojaConfig from '!!raw-loader!../../../config/maloja.json.example'; import MopidyConfig from '!!raw-loader!../../../config/mopidy.json.example'; import MprisConfig from '!!raw-loader!../../../config/mpris.json.example'; import MusikcubeConfig from '!!raw-loader!../../../config/musikcube.json.example'; import MPDConfig from '!!raw-loader!../../../config/mpd.json.example'; import PlexConfig from '!!raw-loader!../../../config/plex.json.example'; import PlexWebhookConfig from '!!raw-loader!../../../config/plex.webhook.json.example'; import SpotifyConfig from '!!raw-loader!../../../config/spotify.json.example'; import SubsonicConfig from '!!raw-loader!../../../config/subsonic.json.example'; import TautulliConfig from '!!raw-loader!../../../config/tautulli.json.example'; import WebscrobblerConfig from '!!raw-loader!../../../config/webscrobbler.json.example'; import YTMusicConfig from '!!raw-loader!../../../config/ytmusic.json.example'; import VLCConfig from '!!raw-loader!../../../config/vlc.json.example';

Configuration

:::tip

Check the FAQ if you have any issues after configuration!

:::

Configuration Types

Sources and Clients are configured using:

environmental (ENV) variables
client/source specific json config files
an all-in-one json config file

MS will parse configuration from all configuration types. You can mix and match configurations but it is generally better to stick to one or the other.

This is done by passing environmental variables and so does not require any files to run MS.

    * Using a docker container EX `docker run -e "SPOTIFY_CLIENT_ID=yourId" -e "SPOTIFY_CLIENT_SECRET=yourSecret" ...`
    * Using a local installations by exporting variables before running MS EX `SPOTIFY_CLIENT_ID=yourId SPOTIFY_CLIENT_SECRET=yourSecret node index.js`

    Use ENV-based configuration if:

    * You are the only person for whom MS is scrobbling for
    * You have a very simple setup for MS such as one scrobble [Client](/#client) and one [Source](/#source) IE Plex -> Maloja
</TabItem>
<TabItem value="file" label="File">
    MS will parse configuration files located in the directory specified by the `CONFIG_DIR` environmental variable. This variable defaults to:

    * Local installation -> `PROJECT_DIR/config`
    * Docker -> `/config` (in the container) -- see the [install docs](../installation/installation.mdx#docker) for how to configure this correctly

    <details>

        <summary>Use File-based configuration if...</summary>

        * You have many [Sources](/#source)
        * You have many of each type of **Source** you want to scrobble from IE 2x Plex accounts, 3x Spotify accounts, 1x
        Funkwhale...
        * You have more than one scrobble **Client** you want to scrobble to IE multiple Maloja servers
        * You want only some **Sources** to scrobble to some **Clients** IE Fred's Spotify account scrobbles to Fred's Maloja
        server, but not Mary's Maloja server

    </details>

    :::tip
        * There are **example configurations** for all Source/Client types and AIO config located in the [`/config`](https://github.com/FoxxMD/multi-scrobbler/tree/master/config) directory of this project. These can be used as-is by renaming them to `.json`.
        * For docker/flatpak installations these examples are copied to your configuration directory on first-time use.
        * There is also a [**kitchensink example**](kitchensink.md) that provides examples of using all sources/clients in a complex configuration.
    :::

    Each file is named by the **type** of the Client/Source found in below sections. Each file as an **array** of that type of Client/Source.

    Example directory structure:

    ```
    /CONFIG_DIR
        plex.json
        spotify.json
        maloja.json
    ```

    <details>
        <summary>Config Example</summary>

        <CodeBlock title="CONFIG_DIR/spotify.json" language="json5">{SpotifyConfig}</CodeBlock>

    </details>
</TabItem>
<TabItem value="aio" label="File AIO">
    MS will parse an **all-in-one** configuration file located in the directory specified by the `CONFIG_DIR` environmental variable. This variable defaults to:

    * Local installation -> `PROJECT_DIR/config/config.json`
    * Docker -> `/config/config.json` (in the container) -- see the [install docs](../installation/installation.mdx#docker) for how to configure this correctly

    <details>

        <summary>Use AIO-based configuration if...</summary>

        * You have many [Sources](/#source)
        * You have many of each type of **Source** you want to scrobble from IE 2x Plex accounts, 3x Spotify accounts, 1x
        Funkwhale...
        * You have more than one scrobble **Client** you want to scrobble to IE multiple Maloja servers
        * You want only some **Sources** to scrobble to some **Clients** IE Fred's Spotify account scrobbles to Fred's Maloja
        server, but not Mary's Maloja server

    </details>

    **The AIO config also enables setting default options for sources/clients as well as global options for MS itself.**

    :::tip
        * An example AIO config files can be found in the project directory at [`/config/config.json.example`](https://github.com/FoxxMD/multi-scrobbler/tree/master/config/config.json.example)
        * For docker/flatpak installations this example is copied to your configuration directory on first-time use.
        * There is also a [**kitchensink example**](kitchensink.md) that provides examples of using all sources/clients in a complex configuration.
    :::

    [**Explore the schema for this configuration, along with an example generator and validator, here**](https://json-schema.app/view/%23?url=https%3A%2F%2Fraw.luolix.top%2FFoxxMD%2Fmulti-scrobbler%2Fmaster%2Fsrc%2Fbackend%2Fcommon%2Fschema%2Faio.json)

    <details>

        <summary>Config Example</summary>

        <CodeBlock title="CONFIG_DIR/config.json" language="json5">{AIOConfig}</CodeBlock>

    </details>
</TabItem>

Application Options

These options affect multi-scrobbler's behavior and are not specific to any source/client.

Base URL

Defines the URL that is used to generate default redirect URLs for authentication on spotify and lastfm -- as well as some logging hints.

Default => http://localhost:9078
Set with ENV BASE_URL or baseUrl all-in-one configuration
If protocol is http or no protocol is specified MS will try to use port 9078 -- to override this explicitly set the port or use https

Useful when running with docker so that you do not need to specify redirect URLs for each configuration.

<summary>Example</summary>

EX Lastfm Redirect Url is `BASE_URL:PORT/lastfm/callback` (when no other redirectUri is specified for [lastfm configuration](#lastfm))

| `BASE_URL`                          | Redirect URL                                             |
|-------------------------------------|----------------------------------------------------------|
| `192.168.0.101`                     | `http://192.168.0.101:9078/lastfm/callback`              |
| `http://my.domain.local`            | `http://my.domain.local:9078/lastfm/callback`            |
| `http://192.168.0.101/my/subfolder` | `http://192.168.0.101:9078/my/subfolder/lastfm/callback` |

| `BASE_URL`                        | Redirect URL                                             |
|-----------------------------------|----------------------------------------------------------|
| `my.domain.local:80`              | `http://192.168.0.101:80/lastfm/callback`                |
| `my.domain.local:9000`            | `http://my.domain.local:9000/lastfm/callback`            |
| `192.168.0.101:4000/my/subfolder` | `http://192.168.0.101:4000/my/subfolder/lastfm/callback` |
| `https://192.168.0.101`           | `https://192.168.0.101:443/lastfm/callback`              |

Disable Web

If you do not need the dashboard and/or ingress sources, or have security concerns about ingress and cannot control your hosting environment, the web server and API can be disabled.

:::warning

Any ingress-based sources will be unusable (Plex, Tautulli, etc...) if this is disabled.

:::

Disable using either:

ENV DISABLE_WEB=true
In All-in-One File use the top-level property "disableWeb": true

Source Configurations

Spotify

To access your Spotify history you must register an application to get a Client ID/Secret. Make sure to also whitelist your redirect URI in the application settings.

:::note

If your Spotify player has Automix enabled and Spotify uses it for your playlist/queue then MS cannot accurately determine when a track will end. This is because the track is "mixed" in your queue with a shorter play time than its actual length and Spotify does not report this modified play time in its API. This does not affect MS's ability to scrobble from Spotify but it will affect the accuracy of the duration MS reports was played.

:::

Configuration

| Environmental Variable | Required? | Default | Description | |----------------------------|-----------|----------------------------------|----------------------------------------------------| | `SPOTIFY_CLIENT_ID` | Yes | | | | `SPOTIFY_CLIENT_SECRET` | Yes | | | | `SPOTIFY_REDIRECT_URI` | No | `http://localhost:9078/callback` | URI must end in `callback` |

    <summary>Example</summary>

    <CodeBlock title="CONFIG_DIR/spotify.json" language="json5">{SpotifyConfig}</CodeBlock>

</details>

or <SchemaLink lower objectName="SpotifySourceConfig"/>

    <summary>Example</summary>

    <AIOExample data={SpotifyConfig} name="spotify"/>

</details>
or <SchemaLink lower objectName="SpotifySourceConfig"/>

Plex

Find your Plex Token and make note of the URL and Port used to connect to your Plex instance.

Allowed Users and Defaults

Multi-scrobbler will automatically scrobble for these users by default:

The User authenticated with the Plex Token
and the Local User

The Local User (PLEX_LOCAL_USER) is how Plex identifies anyone directly accessing the Plex UI from a local IP (who does not need to login).

To allow MS to scrobble for other users use usersAllow or PLEX_USERS_ALLOW (env) from the below configuration docs. However, because you are overriding the default settings you must also explicitly list the authenticated user and the Local User if you want them to also be able to scrobble.

Examples

Defaults

If usersallow and PLEX_USERS_ALLOW are not defined then the Plex Token authenticated User and Local User will be scrobbled for.

Only A Specific User

"usersallow": ["SomeUser"] or
PLEX_USERS_ALLOW: SomeUser

Only the Plex user SomeUser will be scrobbled for. The Plex Token authenticated user and the Local User will not be scrobbled for.

A Specific User + Defaults

(Assuming the plex authenticated user is FoxxMD)

"usersallow": ["FoxxMD", "PLEX_LOCAL_USER", "SomeUser"] or
PLEX_USERS_ALLOW: FoxxMD,PLEX_LOCAL_USER,SomeUser

The Plex user SomeUser, the Plex Token authenticated user (FoxxMD) and the Local User will be scrobbled for.

Allowed Libraries and Defaults

By default multi-scrobbler will only scrobble media found in Plex libraries that are labelled as Music.

librariesAllow or PLEX_LIBRARIES_ALLOW will override this

Configuration

| Environmental Variable | Required? | Default | Description | | ---------------------- | --------- | ------- | ---------------------------------------------------------------------- | | `PLEX_URL` | **Yes** | | The URL of the Plex server IE `http://localhost:32400` | | `PLEX_TOKEN` | **Yes** | | The **Plex Token** to use with the API | | `PLEX_USERS_ALLOW` | No | | Comma-separated list of usernames (from Plex) to scrobble for | | `PLEX_USERS_BLOCK` | No | | Comma-separated list of usernames (from Plex) to disallow scrobble for | | `PLEX_DEVICES_ALLOW` | No | | Comma-separated list of devices to scrobble from | | `PLEX_DEVICES_BLOCK` | No | | Comma-separated list of devices to disallow scrobbles from | | `PLEX_LIBRARIES_ALLOW` | No | | Comma-separated list of libraries to allow scrobbles from | | `PLEX_LIBRARIES_BLOCK` | No | | Comma-separated list of libraries to disallow scrobbles from |

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/plex.json" language="json5">{PlexConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="PlexApiSourceConfig"/>

</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={PlexConfig} name="plex"/>

    </details>

    or <SchemaLink lower objectName="PlexApiSourceConfig"/>
</TabItem>

:::warning[Deprecated]

Multi-scrobbler < 0.8.7 used webhooks to support Plex scrobbling. This approach has been deprecated in favor of using Plex's API directly which has many benefits including not requiring Plex Pass.

:::

<summary>Migrating to API</summary>

* Follow the instructions in the API tab
* The `user` (`PLEX_USER`) setting has been renamed `usersAllow` (`PLEX_USERS_ALLOW`)
  * If you were using this filter to ensure only scrobbles from yourself were registered then you no longer need this setting -- by default MS will only scrobble for the user the Plex Token is from.
* The `servers` setting is no longer available as MS only scrobbles from the server the Plex token is from.
  * If you need to scrobble for multiple servers set up each server as a separate Plex API source with a separate token.
* The `libraries` setting has been renamed to `librariesAllow`

In the Plex dashboard Navigate to your Account/Settings and find the Webhooks page
Click Add Webhook
URL -- http://localhost:9078/plex (substitute your domain if different than the default)
Save Changes

Configuration

| Environmental Variable | Required | Default | Description | |------------------------|----------|---------|-----------------------------------------------------------------------------------------------------------------------------------------| | `PLEX_USER` | No | | The a comma-delimited list of usernames to scrobble tracks for. No usernames specified means all tracks by all users will be scrobbled. |

    <details>

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/plex.json" language="json5">{PlexWebhookConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="PlexSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={PlexWebhookConfig} name="plex"/>

    </details>

    or <SchemaLink lower objectName="PlexSourceConfig"/>
</TabItem>

Tautulli

:::warning[Potentially Deprecated]

Multi-scrobbler >= 0.8.8 supports a Plex Source that directly uses the API and removes the need to use Tautulli since it does not require Plex Pass.

Please see this issue for discussion on deprecating Tautulli and provide your input.

:::

Check the instructions on how to setup a notification agent.

Configuration

| Environmental Variable | Required | Default | Description | |------------------------|----------|---------|-----------------------------------------------------------------------------------------------------------------------------------------| | `TAUTULLI_USER` | No | | The a comma-delimited list of usernames to scrobble tracks for. No usernames specified means all tracks by all users will be scrobbled. |

    <details>

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/tautulli.json" language="json5">{TautulliConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="TautulliSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={TautulliConfig} name="tautulli"/>

    </details>

    or <SchemaLink lower objectName="TautulliSourceConfig"/>
</TabItem>

Subsonic

Can use this source for any application that implements the Subsonic API and supports the getNowPlaying endpoint (such as Airsonic and Navidrome)

:::warning[Known Issues]

Multiple artists are reported as one value and cannot be separated
If using Airsonic Advanced the password used (under Credentials) must be Decodable

:::

Configuration

| Environmental Variable | Required? | Default | Description | |------------------------|-----------|---------|--------------------------------------| | `SUBSONIC_USER` | Yes | | | | `SUBSONIC_PASSWORD` | Yes | | | | `SUBSONIC_URL` | Yes | | Base url of your subsonic-api server |

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/subsonic.json" language="json5">{SubsonicConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="SubSonicSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={SubsonicConfig} name="subsonic"/>

    </details>

    or <SchemaLink lower objectName="SubSonicSourceConfig"/>
</TabItem>

Jellyfin

<summary>Migrating from Webhook (multi-scrobbler below `v0.8.4`) to API</summary>

In multi-scrobbler **below v0.9.0** communication with Jellyfin was done using Jellyfin's **Webhook** plugin.
This has been deprecated in favor of directly using Jeyllfin's API for a better experience in multi-scrobbler.

### To Migrate:

* Remove the **Webhook** plugin (if not using it for anything else)
* Follow the new instructions below (outside this section) to setup API usage
* The `servers` (`JELLYFIN_SERVERS`) setting is no longer available as MS only scrobbles from the server using the API anyways.
  * If you need to scrobble for multiple servers set up each server as a separate Jellyfin source
* The `users` (`JELLYFIN_USER`) setting has been renamed `usersAllow` (`JELLYFIN_USERS_ALLOWED`)
  * If you were using this filter to ensure only scrobbles from yourself were registered then you no longer need this setting -- by default MS will only scrobble for the user authenticated with Jellyfin's API.

Must be using Jellyfin 10.7 or greater

Create an API Key for multi-scrobbler
- In the Jellyfin desktop web UI Navigate to -> Administration -> Dashboard -> API Keys (http://YOUR_JELLYIN_URL/web/index.html#!/apikeys.html)
- Click + button and create a new key with App name multi-scrobbler
- Copy the created API Key value for use in configuration below

It is recommended to use API Key + username but if you are not an admin for your Jellyfin instance you can also authenticate with your Jellyfin username and password.

:::tip[Important Defaults]

By default...

multi-scrobbler will only scrobbling for the user authenticated with the API.
- Allowed Users (usersAllow or JELLYFIN_USERS_ALLOW) are only necessary if you want to scrobble for additional users.
multi-scrobbler will only scrobble media found in Jellyfin libraries that were labelled as Music.
- librariesAllow or JELLYFIN_LIBRARIES_ALLOW will override this
- OR use additionalAllowedLibraryTypes to allow more types (like mixed or book for audiobooks)
multi-scrobbler will only scrobble media Jellyfin detects as Audio.
- To force multi-scrobbler to scrobble when media is detected as Unknown use "allowUnknown": true in file/aio configuration.

:::

Configuration

| Environmental Variable | Required? | Default | Description | | -------------------------- | --------- | ------- | ------------------------------------------------------------------------------------------ | | `JELLYFIN_URL` | **Yes** | | The URL of the Jellyfin server IE `http://localhost:8096` | | `JELLYFIN_USER` | **Yes** | | The user to authenticate with the API | | `JELLYFIN_APIKEY` | No | | The API Key to use for authentication **(Must provide either apikey or password)** | | `JELLYFIN_PASSWORD` | No | | The password of the user to authenticate for. **(Must provide either apikey or password)** | | `JELLYFIN_USERS_ALLOW` | No | | Comma-separated list of usernames (from Jellyfin) to scrobble for | | `JELLYFIN_USERS_BLOCK` | No | | Comma-separated list of usernames (from Jellyfin) to disallow scrobble for | | `JELLYFIN_DEVICES_ALLOW` | No | | Comma-separated list of devices to scrobble from | | `JELLYFIN_DEVICES_BLOCK` | No | | Comma-separated list of devices to disallow scrobbles from | | `JELLYFIN_LIBRARIES_ALLOW` | No | | Comma-separated list of libraries to allow scrobbles from | | `JELLYFIN_LIBRARIES_BLOCK` | No | | Comma-separated list of libraries to disallow scrobbles from |

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/jellyfin.json" language="json5">{JellyfinConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="JellyApiSourceConfig"/>

</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={JellyfinConfig} name="jellyfin"/>

    </details>

    or <SchemaLink lower objectName="JellyApiSourceConfig"/>
</TabItem>

Last.fm (Source)

See the Last.fm (Client) setup for registration instructions.

Configuration

No support for ENV based for Last.fm as a client (only source)

Change `configureAs` to `source`

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/lastfm.json" language="json5">{LastfmConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="LastfmSourceConfig"/>
   </TabItem>
<TabItem value="aio" label="AIO">
    <details>
        Change `configureAs` to `source`

        <summary>Example</summary>

        <AIOExample data={LastfmConfig} name="lastfm"/>

    </details>

    or <SchemaLink lower objectName="LastfmSourceConfig"/>
</TabItem>

Listenbrainz (Source)

You will need to run your own Listenbrainz server or have an account on the official instance

On your profile page find your User Token to use in the configuration.

Configuration

:::note You cannot use ENV variables shown in the [Listenbrainz Client config](#listenbrainz) -- multi-scrobbler assumes Listenbrainz ENVs are always used for the **client** configuration. You must use the file-based config from below to setup Listenbrainz as a Source. :::

Change `configureAs` to `source`

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/listenbrainz.json" language="json5">{ListenbrainzConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="ListenBrainzSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>
        Change `configureAs` to `source`

        <summary>Example</summary>

        <AIOExample data={ListenbrainzConfig} name="listenbrainz"/>

    </details>

    or <SchemaLink lower objectName="ListenBrainzSourceConfig"/>
</TabItem>

Deezer

:::warning

This Source is DEPRECATED because Deezer has dropped official API support. This Source will not be removed but no further support or fixes will be given.

Users cannot create new applications on Deezer Developers and there is no guarantee existing applications will continue to work.

As a workaround consider integrating Deezer with last.fm and then using last.fm as a Source.

Users with existing Deezer applications in use with multi-scrobbler should consider this change as well to avoid future breaking issues with the unsupported API.

See this issue for more discussion.

:::

Create a new application at Deezer Developers

Application Domain must be the same as your multi-scrobbler domain. Default is localhost:9078
Redirect URL must end in deezer/callback
- Default would be http://localhost:9078/deezer/callback

After application creation you should have credentials displayed in the "My Apps" dashboard. You will need:

Application ID
Secret Key
Redirect URL (if not the default)

If no access token is provided...

After starting multi-scrobbler with credentials in-place open the dashboard (http://localhost:9078) and find your Deezer source. Click (Re)authenticate and (re)start polling to start the login process. After login is complete polling will begin automatically.

Configuration

| Environmental Variable | Required? | Default | Description | |------------------------|-----------|-----------------------------------------|-----------------------------------| | `DEEZER_CLIENT_ID` | Yes | | Your **Application ID** | | `DEEZER_CLIENT_SECRET` | Yes | | Your **Secret Key** | | `DEEZER_REDIRECT_URI` | No | `http://localhost:9078/deezer/callback` | URI must end in `deezer/callback` |

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/deezer.json" language="json5">{DeezerConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="DeezerSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={DeezerConfig} name="deezer"/>

    </details>

    or <SchemaLink lower objectName="DeezerSourceConfig"/>
</TabItem>

Youtube Music

:::warning

Communication with YT Music is unofficial and not supported or endorsed by Google. This means that this integration may stop working at any time if Google decides to change how YT Music works in the browser.

:::

:::tip[Scrobble Troubleshooting]

Due to monitoring being unofficial, listening history from YTM can be inconsistent and can cause missed scrobbles. See the FAQ for a detailed explanation of this and how to properly report an issue.

:::

Authentication

Only one of these methods needs to be used. Cookies are easier but OAuth Client may be more stable.

:::info

    If cookies stop working for you or are being invalidated often try switching to **OAuth Client** authentication.

    :::

    Use instructions from 
    
    * https://github.com/patrickkfkan/Volumio-YouTube.js/wiki/How-to-obtain-Cookie or 
    * https://ytmusicapi.readthedocs.io/en/stable/setup/browser.html#copy-authentication-headers 
    
    to get the **Cookie** value from a browser.

    It is highly recommended to [get the cookie from an Incognito/Private Session](https://github.com/LuanRT/YouTube.js/issues/803#issuecomment-2504032666) to limit the chance the session is invalidated from normal browsing.

    Add the cookie to your `ytmusic.json` config in `data`: 

    ```json
        {
        "type": "ytmusic",
        "enable": true,
        "name": "MyYTM",
        "data": {
            "cookie": "__Secure-1PSIDTS=sidts-CjEB3EgAEvCd-......"
        },
        "options": {
            "logAuthUpdateChanges": true,
            "logDiff": true
        }
    }
    ```

    If MS gives you authentication errors (session invalidated) at some point in the future follow the same instructions to get new cookies.

</TabItem>
<TabItem value="oauth" label="OAuth Client">
    :::note

    This is likely to be the most stable method and least likely to be blocked or have authentication invalidated after an extended period. It requires more setup but is worth the effort.
    
    :::

    [Based on the instructions from here...](https://github.com/LuanRT/YouTube.js/issues/803#issuecomment-2479689924)

    * Login to [Google Cloud console](https://console.cloud.google.com/) (create an account, if necessary)
      * [Create a new project](https://console.cloud.google.com/projectcreate)
    * Go to APIs and services.
        * Configure the OAuth consent screen
            * Use the old experience if possible
            * If new is unavoidable then do not fill out any branding and under Authorized Domains you can delete the empty one (in order to save)
            * Add yourself as an authorized user
        * Navigate to Credentials
            * Create Credentials -> choose "OAuth client ID"
                *  Application Type is **Web Application**
                * **Name** is whatever you want, leave Authorization Javascript origins blank
                * Authorized redirect URIs
                    * This must be **exactly** the same as what is displayed in MS! For now leave it blank so we can generate it from MS first
            * Create
                * In the newly created client popup save the **Client ID** and **Client Secret**, then copy them into `ytmusic.json`

    ```json
    {
        "type": "ytmusic",
        "enable": true,
        "name": "MyYTM",
        "data": {
            "clientId": "8910....6jqupl.apps.googleusercontent.com",
            "clientSecret": "GOCSPX-WGXL6BSuQ343..."
        },
        "options": {
            "logAuthUpdateChanges": true,
            "logDiff": true
        }
    }
    ```

    Now, start MS and during the YTMusic startup it will log something like this:

    ```
    Using Custom OAuth Client:
    Client ID: ...
    Client Secret: ...
    Redirect URI: http://localhost:9078/api/ytmusic/callback?name=MyYTM
    ```

    If the beginning of the URL (before `api`) is EXACTLY how you would reach the MS dashboard from your browser (EX `http://localhost:9078`) then edit your google oauth client section for `Authorized redirect URIs` and add the URL MS has displayed.

    If it is NOT EXACTLY the same you either need to set MS's [base url](https://foxxmd.github.io/multi-scrobbler/docs/configuration/#base-url) or you can provide your own (Custom) Redirect URI for MS to use by setting it in `ytmusic.json`.

    <details>

        <summary>Using a Custom Redirect URI</summary>

            The three parts of the URL that must be the same:

            * it must start with `api` (after domain or subdirectory IE `my.domain.tld/api...` or `whatever.tld/subDir/api...`
            * it must end in `ytmusic/callback`
            * It must include `name=[NameOfSource]` in the query string

            Remember to add your custom URL to the `Authorized redirect URIs`  section in the google oauth client!

            ```json
            {
                "type": "ytmusic",
                "enable": true,
                "name": "MyYTM",
                "data": {
                    "clientId": "8910....6jqupl.apps.googleusercontent.com",
                    "clientSecret": "GOCSPX-WGXL6BSuQ343...",
                    "redirectUri": "http://my.custom.domain/api/ytmusic/callback?name=MyYTM"
                },
                "options": {
                    "logAuthUpdateChanges": true,
                    "logDiff": true
                }
            }
            ```

    </details>

    AFTER changing the Authorized redirect URIs on Google Cloud console you may need to wait a few minutes for it to take affect. Then restart MS. From the dashboard click `(Re)authenticate` on the YTmusic source card and follow the auth flow:

    * On the screen about "testing" make sure you hit **Continue** (not Back To Safety)
    * Make sure to select ALL scopes/permissions/grants it asks you about
      * `Select what [YourAppName] can access` -> Select all

    Once the flow is finished MS will get the credentials and start polling automatically. You should not need to re-authenticate again after restarting MS as it saves the credentials to the `/config` folder.
        
</TabItem>
<TabItem value="ytt" label="YoutubeTV">

    :::warning

    Using the built-in YoutubeTV authentication is unlikely to work due to [Google restricting what permissions TV clients can have](https://github.com/yt-dlp/yt-dlp/issues/11462#issuecomment-2471703090). This authentication method should not be used.
    
    :::   

    To authenticate start multi-scrobbler with an empty YT Music configuration. An authentication URL/code will be logged in additon to being available from the dashboard.

    ```
    ERROR: Sign in with the code 'CLV-KFA-BVKY' using the authentication link on the dashboard or https://www.google.com/device
    ```

    Visit the authentication URL and enter the code that was provided (also available on the dashboard). After completing the setup flow MS will log `Auth success` and the YT Music dashboard card will display as **Idle** after refreshing. Click the **Start** link to begin monitoring.

</TabItem>

Configuration

Environmental Variable	Required?	Default	Description
YTM_COOKIE	No		Value for Cookie Authentication
YTM_CLIENT_ID	No		Client ID for OAuth Athentication
YTM_CLIENT_SECRET	No		Client Secret for OAuth Athentication
YTM_REDIRECT_URI	No		A custom redirect URI for OAuth Athentication
YTM_LOG_DIFF	No	false	Log YTM history changes

</TabItem>
<TabItem value="file" label="File">
    <details>

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/ytmusic.json" language="json5">{YTMusicConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="YTMusicSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={YTMusicConfig} name="ytmusic"/>

    </details>

    or <SchemaLink lower objectName="YTMusicSourceConfig"/>
</TabItem>

MPRIS

MPRIS is a standard interface for communicating with Music Players on linux operating systems.

If you run Linux and have a notification tray that shows what media you are listening to, you likely have access to MPRIS.

multi-scrobbler can listen to this interface and scrobble tracks played by any media player that communicates to the operating system with MPRIS.

:::note

multi-scrobbler needs to be running as a Local Installation in order to use MPRIS. This cannot be used from docker.

:::

Configuration

| Environmental Variable | Required? | Default | Description | |------------------------|-----------|---------|----------------------------------------------------------------------------------| | MPRIS_ENABLE | No | | Use MPRIS as a Source (useful when you don't need any other options) | | MPRIS_BLACKLIST | No | | Comma-delimited list of player names not to scrobble from | | MPRIS_WHITELIST | No | | Comma-delimited list of players names to ONLY scrobble from. Overrides blacklist |

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/mpris.json" language="json5">{MprisConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="MPRISSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={MprisConfig} name="mpris"/>

    </details>

    or <SchemaLink lower objectName="MPRISSourceConfig"/>
</TabItem>

Mopidy

Mopidy is a headless music server that supports playing music from many standard and non-standard sources such as Pandora, Bandcamp, and Tunein.

multi-scrobbler can scrobble tracks played from any Mopidy backend source, regardless of where you listen to them.

:::note

You must have Mopidy-HTTP extension enabled for this integration to work.

:::

Configuration {#mopidy-config}

No ENV support

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/mopidy.json" language="json5">{MopidyConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="MopidySourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={MopidyConfig} name="mopidy"/>

    </details>

    or <SchemaLink lower objectName="MopidySourceConfig"/>
</TabItem>

Configuration Options

URL

The URL used to connect to the Mopidy server, set in your file config as url. The URL used to connect ultimately must be formed like this:

Syntax  => [protocol]://[hostname]:[port]/[path]
Default =>         ws://localhost:6680/mopidy/ws

If any part of this URL is missing multi-scrobbler will use a default value. This also means that if any part of your URL is not standard you must explicitly define it.

:::tip[Mopidy Configuration]

Make sure the hostname and port number match what is found in the Mopidy configuration file mopidy.conf:

[http]
hostname = localhost
port = 6680

:::

URL Transform Examples

Examples of a given `url` in your file config and the final URL multi-scrobbler will use to connect to Mopidy:

| `url`                          | Transformed URL                            |
|--------------------------------|--------------------------------------------|
| (none set)                     | `ws://localhost:6680/mopidy/ws`            |
| `mopidy.mydomain.com`          | `ws://mopidy.mydomain.com:6680/mopidy/ws/` |
| `192.168.0.101:3456`           | `ws://192.168.0.101:3456/mopidy/ws/`       |
| `mopidy.mydomain.com:80/MOPWS` | `ws://mopidy.mydomain.com:80/MOPWS`        |

URI Blacklist/Whitelist

If you wish to disallow or only allow scrobbling from some sources played through Mopidy you can specify these using uriBlacklist or uriWhitelist in your config. multi-scrobbler will check the list to see if any string matches the START of the uri on a track. If whitelist is used then blacklist is ignored. All strings are case-insensitive.

Example

```json { "uriBlacklist": ["soundcloud"] } ```

Will prevent multi-scrobbler from scrobbling any Mopidy track that start with a `uri` like `soundcloud:song:MySong-1234`

Album Blacklist

For certain sources (Soundcloud) Mopidy does not have all track info (Album) and will instead use "Soundcloud" as the Album name. You can prevent multi-scrobbler from using this bad Album data by adding the fake Album name to this list. Multi-scrobbler will still scrobble the track, just without the bad data. All strings are case-insensitive.

Example

```json { "albumBlacklist": ["SoundCloud", "Mixcloud"] } ```

If a track would be scrobbled like
```
Album: Soundcloud, Track: My Cool Track, Artist: A Cool Artist
```
then multi-scrobbler will instead scrobble
```
Track: My Cool Track, Artist: A Cool Artist
```

JRiver

In order for multi-scrobbler to communicate with JRiver you must have Web Server Interface enabled. This can can be in the JRiver GUI:

Tools -> Options -> Media Network
- Check Use Media Network to share this library...
- If you have Authentication checked you will need to provide the Username and Password in the ENV/File configuration below.

Configuration {#jriver-config}

| Environmental Variable | Required | Default | Description | |------------------------|----------|---------------------------------|------------------------------------------------| | JRIVER_URL | Yes | http://localhost:52199/MCWS/v1/ | The URL of the JRiver server | | JRIVER_USERNAME | No | | If authentication is enabled, the username set | | JRIVER_PASSWORD | No | | If authenticated is enabled, the password set |

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/jriver.json" language="json5">{JriverfinConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="JRiverSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={JriverfinConfig} name="jriver"/>

    </details>

    or <SchemaLink lower objectName="JRiverSourceConfig"/>
</TabItem>

URL

The URL used to connect to JRiver, set in your file config as url. The URL used to connect ultimately must be formed like this:

Syntax  => [protocol]://[hostname]:[port]/[path]
Default =>       http://localhost:52199/MCWS/v1/

If any part of this URL is missing multi-scrobbler will use a default value. This also means that if any part of your URL is not standard you must explicitly define it.

:::tip[Jriver Settings]

Make sure the port number matches what is found in Advanced section in the Media Network options.
If your installation is on the same machine but you cannot connect using localhost try 0.0.0.0 instead.

:::

URL Transform Examples

Examples of a given `url` in your file config and the final URL multi-scrobbler will use to connect to JRiver:

| `url`                                    | Transformed URL                             |
|------------------------------------------|---------------------------------------------|
| (none set)                               | `http://localhost:52199/MCWS/v1/`           |
| `jriver.mydomain.com`                    | `http://jriver.mydomain.com:52199/MCWS/v1/` |
| `192.168.0.101:3456`                     | `http://192.168.0.101:3456/MCWS/v1/`        |
| `mydomain.com:80/jriverReverse/MCWS/v1/` | `mydomain.com:80/jriverReverse/MCWS/v1/`    |

Kodi

In order for multi-scrobbler to communicate with Kodi you must have the Web Interface enabled. This can be done in the Kodi GUI:

Settings -> Services -> Control
- Check Allow remote control via HTTP
- Ensure you have a Username and Password set, you will need to provide them in the ENV/File configuration below.

Configuration {#kodi-config}

| Environmental Variable | Required | Default | Description | |------------------------|----------|-------------------------------|----------------------------| | KODI_URL | Yes | http://localhost:8080/jsonrpc | The URL of the Kodi server | | KODI_USERNAME | No | | The username set | | KODI_PASSWORD | No | | The password set |

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/kodi.json" language="json5">{KodiConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="KodiSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={KodiConfig} name="kodi"/>

    </details>

    or <SchemaLink lower objectName="KodiSourceConfig"/>
</TabItem>

URL

The URL used to connect to Kodi, set in your file config as url. The URL used to connect ultimately must be formed like this:

Syntax  => [protocol]://[hostname]:[port]/[path]
Default =>       http://localhost:8080/jsonrpc

If any part of this URL is missing multi-scrobbler will use a default value. This also means that if any part of your URL is not standard you must explicitly define it.

:::tip[Kodi Settings]

Make sure the port number matches what is found in Port in the Control section mentioned above.
If your installation is on the same machine but you cannot connect using localhost try 0.0.0.0 instead.

:::

URL Transform Examples

Examples of a given `url` in your file config and the final URL multi-scrobbler will use to connect to Kodi:

| `url`                                 | Transformed URL                              |
|---------------------------------------|----------------------------------------------|
| (none set)                            | `http://localhost:8080/jsonrpc`              |
| `kodi.mydomain.com`                   | `http://kodi.mydomain.com:8080/jsonrpc`      |
| `192.168.0.101:3456`                  | `http://192.168.0.101:3456/jsonprc`          |
| `mydomain.com:80/kodiReverse/jsonrpc` | `http://mydomain.com:80/kodiReverse/jsonrpc` |

WebScrobbler

After installing the extension open the preferences/settings for it:

Under Accounts
- Add Webhook
  - API URL: [YourMultiScrobblerInstance]/api/webscrobbler EX http://localhost:9078/api/webscrobbler
  - Application name: (whatever you want)

Reload the extension after adding the webhook.

:::note

On Firefox - Only FQNs (domain.tld), localhost, and 127.0.0.1 are supported for API URL due to firefox requiring https
On Chromium-based Browsers - Any domain will work for API URL
All other browsers are untested

:::

:::warning

Multi-scrobbler is not designed to be publicly accessible from the internet. To use Webscrobbler outside your local network you should be accessing MS through a VPN or through a reverse proxy with some kind of authentication (though this is still not recommended).

:::

Configuration {#webscrobbler-config}

| Environmental Variable | Required? | Default | Description | |------------------------|-----------|---------|--------------------------------------------------------------------------| | WS_ENABLE | No | | Set to 'true' to enable WS without needing to define other ENVs | | WS_WHITELIST | No | | Only scrobble from these WebScrobbler Connectors. Comma-delimited list | | WS_BLACKLIST | No | | Do not scrobble from these WebScrobbler Connectors. Comma-delimited list |

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/webscrobbler.json" language="json5">{WebscrobblerConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="WebScrobblerSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={WebscrobblerConfig} name="webscrobbler"/>

    </details>

    or <SchemaLink lower objectName="WebScrobblerSourceConfig"/>
</TabItem>

Multiple Users

If you would like use multiple WebScrobbler sources they can be matched using a slug at the end of the API URL. This requires using a file-based config.

<summary>Example</summary>

```json title="webscrobbler.json"
[
  {
    "name": "aUserWS",
    "clients": [
      "client1Maloja"
    ],
    "data": {
      "slug": "usera"
    }
  },
  {
    "name": "bUserWS",
    "clients": [
      "client2Maloja"
    ],
    "data": {
      "slug": "userb"
    }
  }
]
```

* To use `aUserWS` source set **API URL** to `http://localhost:9078/api/webscrobbler/usera`
* To use `bUserWS` source set **API URL** to `http://localhost:9078/api/webscrobbler/userb`

:::tip

`http://localhost:9078/api/webscrobbler` is matched with the first source that _that does not have a slug defined._

:::

Connectors Black/Whitelist

MS can be configured to only scrobble, or NOT scrobble, from some WS connectors. Use the name of the website from the supported websites or from the Connectors tab in the extension.

:::note

This affects only MS's behavior and does not affect the general connector behavior you have configured within the WebScrobbler extension.

:::

Google Cast (Chromecast)

If your media device can be Cast to using this button on your phone/computer then multi-scrobbler can monitor it in order to scrobble music you play.

:::note

Google Cast support is experimental. You may experience crashes and errors while using this Source. Please open an issue if you experience problems and include all information detailed in the issue template to help debug your issue.

:::

:::note

This source relies on common, basic music data provided by the cast device which will always be less exhaustive than data parsed from full source integrations. If there is an existing Source it is recommended to configure for it and blacklist the app on Google Cast, rather than relying solely on Google Cast for scrobbling.

:::

Configuration

:::note [Manually configuring cast device connections](#connecting-devices) is only available through file-based config. :::

    | Environmental Variable | Required? | Default |                                     Description                                      |
    |------------------------|-----------|---------|--------------------------------------------------------------------------------------|
    | CC_ENABLE              | No        |         | Set to 'true' to enable Cast monitoring without needing to define other ENVs         |
    | CC_WHITELIST_DEVICES   | No        |         | Only scrobble from these Cast devices. Comma-delimited list. EX mini-home, family-tv |
    | CC_BLACKLIST_DEVICES   | No        |         | Do not scrobble from these Cast devices. Comma-delimited list                        |
    | CC_WHITELIST_APPS      | No        |         | Only scrobble from these casted Apps. Comma-delimited list. EX spotify, pandora      |
    | CC_BLACKLIST_APPS      | No        |         | Do not scrobble from these casted Apps. Comma-delimited list                         |
</TabItem>
<TabItem value="file" label="File">

    <details>

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/chromecast.json" language="json5">{ChromecastConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="ChromecastSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={ChromecastConfig} name="chromecast"/>

    </details>

    or <SchemaLink lower objectName="ChromecastSourceConfig"/>
</TabItem>

Connecting Devices

Cast devices can be manually configured using file-based configuration OR automatically discovered using mDNS.

mDNS Discovery

The host machine running multi-scrobbler must be configured to allow mDNS traffic on port 5353/UDP.

<summary>OS Specific Instructions</summary>

**Docker**

    The host machine must have [avahi-daemon](https://avahi.org/) running to circumvent limitations with DNS resolution due to musl in Alpine. Most major linux distributions package avahi and many have it built-in. Once avahi is running you must pass D-Bus and the avahi daemon socket to your container like so:

    ```
    docker run ... -v /var/run/dbus:/var/run/dbus -v  	/var/run/avahi-daemon/socket:/var/run/avahi-daemon/socket ... foxxmd/multi-scrobbler
    ```

    **Flatpak/Nodejs**

    No additional steps are required.
</TabItem>
<TabItem value="windows" label="Windows">
    **Docker**

    Unsupported at this time.

    **Nodejs**

    No additional steps are required.
</TabItem>

What Media Does MS Scrobble?

Cast devices report what type of media the current activity is (see metadata property here). The reported type is dependent on the application playing the media to correctly report it, the cast device does not magically know what the media is. If an application does not report a type it is always classified as unknown.

By default, MS will only track media that is reported as MusicTrack.

Allow Unknown Media Type

Media with an Unknown (Generic) media type can be explicitly allowed by setting "allowUnknownMedia": true in the file-based configuration. This can also be configured to only allow unknown media types for specific applications by using a list of application names.

<summary>Example</summary>

```json5 title="chromecast.json"
[
  {
    "name": "MyCast",
    "type": "chromecast",
    "data": {
      // only allow unknown if app name contains any of these phrases
      "allowUnknownMedia": ["smarttube", "default media receiver"]
    },
  }
]
```

Forcing Media Tracking

MS can be forced to track media from an application regardless of media type. This is useful if an application incorrectly reports a media type you are sure should be music. Set "forceMediaRecognitionOn" in the file-based configuration to a list of application names that should always be tracked.

<summary>Example</summary>

```json5 title="chromecast.json"
[
  {
    "name": "MyCast",
    "type": "chromecast",
    "data": {
      // media from applications that contains these phrases will always be tracked, regardless of media type reported
      "forceMediaRecognitionOn": ["smarttube", "default media receiver"]
    },
  }
]
```

Cast Troubleshooting

Please include any/all logs with raw output if there are any errors encountered as this is critical to diagnosing issues.

To diagnose bad/incomplete track information or strange MS player behavior please turn on payload logging and include log output of the source running to help diagnose this issue.

<summary>Example</summary>

```json5 title="chromecast.json"
[
  {
    "name": "MyCast",
    "type": "chromecast",
    "data": {
      //...
    },
    "options": {
      "logPayload": true
    }
  }
]
```

Musikcube

In order to use Musikcube configure it to accept websocket connections in server setup:

Enable the Metadata Server
Set a Password

Both of these settings are found in Musikcube -> (s)ettings -> server setup

The URL used by MS has the syntax:

[ws|wss]://HOST:[PORT]

The port is the same as shown in the server setup screenshot from above, under metadata server enabled. If no port is provided to MS it will default to 7905.

If no URL is provided to MS it will try to use ws://localhost:7905

Configuration

| Environmental Variable | Required? | Default | Description | |------------------------|-----------|-----------------------|--------------------------------------| | `MC_URL` | No | `ws://localhost:7905` | Use port set for **metadata server** | | `MC_PASSWORD` | Yes | | |

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/musikcube.json" language="json5">{MusikcubeConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="MusikcubeSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={MusikcubeConfig} name="musikcube"/>

    </details>

    or <SchemaLink lower objectName="MusikcubeSourceConfig"/>
</TabItem>

MPD (Music Player Daemon)

MS communicates with MPD using the TCP client connection.

You should uncomment/create the following settings in your mpd config:

bind_to_address	"any"   # or a specific ipv4/v6 address
port            "6600"

Configuration

| Environmental Variable | Required? | Default | Description | |------------------------|-----------|------------------|-------------| | `MPD_URL` | No | `localhost:6600` | | | `MPD_PASSWORD` | No | | |

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/mpd.json" language="json5">{MPDConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="MPDSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={MPDConfig} name="mpd"/>

    </details>

    or <SchemaLink lower objectName="MPDSourceConfig"/>
</TabItem>

VLC

MS communicates with VLC using the Web (http) interface module

Enable HTTP Interface

Open VLC:

Tools Menu -> Preferences
- In the bottom left change Show Settings from Simple to All
- In the updated window select Interface -> Main interfaces
  - In the Extra interface modules section enable Web and verify that http is shown in the textbox
- Select Interface -> Main interfaces -> Lua
  - In Lua HTTP -> Password -> set a password in this box
- Click Save at the bottom to persist your changes
Restart VLC
Verify the HTTP interface is accessible by navigating to http://localhost:8080 in your browser

If the interface is accessible, after typing in your password, VLC is now ready to be used by MS.

Setting VLC Interface and Port

These can be set by starting VLC from command line with specific options:

vlc --http-host yourHostIp:yourPort or
vlc --http-port yourPort or
modify the configuration file for VLC by editing keys with the same values as from the command line (http-host and http-port)

Configuration

| Environmental Variable | Required? | Default | Description | |------------------------|------------|------------------|-------------| | `VLC_URL` | No | `localhost:8080` | | | `VLC_PASSWORD` | Yes | | |

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/vlc.json" language="json5">{VLCConfig}</CodeBlock>

    </details>

    or <SchemaLink lower objectName="VLCSourceConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample data={VLCConfig} name="vlc"/>

    </details>

    or <SchemaLink lower objectName="VLCSourceConfig"/>
</TabItem>

Filename Parsing

If the file being played in VLC does not have ID3 tags/metadata information multi-scrobbler can attempt to extract artist, title, and album information from the raw filename using regular expressions. Mutli-scrobbler will only do this if there is no other information reported by VLC about these fields.

To extract this information use named capture groups in your expression matching the field that should be extracted: artist title and/or album. MS accepts multiple expressions, the first one that matches a filename will be used.

Example usage in a file-based config:

[
  {
    "name": "MyVlc",
    "enable": true,
    "data": {
      // ...
    },
    "options": {
      "filenamePatterns": [
          // Extracts artist and title from filenames that look like:
          // My Artist - My Cool title.mp4
          "/^\\s*(?<artist>.+?) - (?<title>.+?)\\.\\w+$/i"
        ],
      // logs to DEBUG when MS tries to extract data from a filename
      "logFilenamePatterns": true,
    }
  }
]

Vlc Information Reporting

If you find that VLC is incorrectly reporting track information (in its interface) but multi-scrobbler is not parsing it correctly it may be due to the name of the fields VLC is reporting. mutli-scrobbler uses the most common field name but does not cover all use cases. Before reporting an issue please turn on metadata logging and include output from your logs while it is turned on:

    [
      {
        "name": "MyVlc",
        "enable": true,
        "data": {
          // ...
        },
        "options": {
          "dumpVlcMetadata": true
        }
      }
    ]

Client Configurations

Maloja

Configuration

| Environmental Variable | Required? | Default | Description | |------------------------|-----------|---------|-------------------------------| | `MALOJA_URL` | Yes | | Base URL of your installation | | `MALOJA_API_KEY` | Yes | | Api Key |

    <details>

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/maloja.json" language="json5">{MalojaConfig}</CodeBlock>

    </details>

    or <SchemaLink client lower objectName="MalojaClientConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample client data={MalojaConfig} name="maloja"/>

    </details>

    or <SchemaLink client lower objectName="MalojaClientConfig"/>
</TabItem>

Last.fm

Register for an API account here.

The Callback URL is actually specified by multi-scrobbler but to keep things consistent you should use

http://localhost:9078/lastfm/callback

or replace localhost:9078 with your own base URL

Configuration

| Environmental Variable | Required? | Default | Description | |------------------------|-----------|-----------------------------------------|-------------------------------------------------------------------------------| | `LASTFM_API_KEY` | Yes | | Api Key from your API Account | | `LASTFM_SECRET` | Yes | | Shared secret from your API Account | | `LASTFM_REDIRECT_URI` | No | `http://localhost:9078/lastfm/callback` | Url to use for authentication. Must include `lastfm/callback` somewhere in it | | `LASTFM_SESSION` | No | | Session id. Will be generated by authentication flow if not provided. |

    <details>

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/lastfm.json" language="json5">{LastfmConfig}</CodeBlock>

    </details>

    or <SchemaLink client lower objectName="LastfmClientConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample client data={LastfmConfig} name="lastfm"/>

    </details>

    or <SchemaLink client lower objectName="LastfmClientConfig"/>
</TabItem>

Listenbrainz

You will need to run your own Listenbrainz server or have an account on the official instance

On your profile page find your User Token to use in the configuration.

Configuration

| Environmental Variable | Required? | Default | Description | |------------------------|-----------|-------------------------------|---------------------------------| | LZ_TOKEN | Yes | | User token from your LZ profile | | LZ_USER | Yes | | Your LZ username | | LZ_URL | No | https://api.listenbrainz.org/ | The base URL for the LZ server |

    <details>

        <summary>Example</summary>

        <CodeBlock title="CONFIG_DIR/listenbrainz.json" language="json5">{ListenbrainzConfig}</CodeBlock>

    </details>

    or <SchemaLink client lower objectName="ListenBrainzClientConfig"/>
</TabItem>
<TabItem value="aio" label="AIO">
    <details>

        <summary>Example</summary>

        <AIOExample client data={ListenbrainzConfig} name="listenbrainz"/>

    </details>

    or <SchemaLink client lower objectName="ListenBrainzClientConfig"/>
</TabItem>

Monitoring

multi-scrobbler supports some common webhooks and a healthcheck endpoint in order to monitor Sources and Clients for errors.

Webhook Configurations

Webhooks will push a notification to your configured servers on these events:

Source polling started
Source polling retry
Source polling stopped on error
Scrobble client scrobble failure

Webhooks are configured in the AIO config.json file under the webhook top-level property. Multiple webhooks may be configured for each webhook type.

<summary>Example</summary>

```json5 title="config.json"
{
  "sources": [
    //...
  ],
  "clients": [
    //...
  ],
  "webhooks": [
    {
      "name": "FirstGotifyServer",
      "type": "gotify",
      "url": "http://192.168.0.100:8070",
      "token": "abcd"
    },
    {
      "name": "SecondGotifyServer",
      "type": "gotify",
      //...
    },
    {
      "name": "NtfyServerOne",
      "type": "ntfy",
      //...
    },
    //...
  ]
}
```

Gotify

Refer to the config schema for GotifyConfig

multi-scrobbler optionally supports setting message notification priority via info warn and error mappings.

<summary>Example</summary>

```json title="config.json"
{
  "type": "gotify",
  "name": "MyGotifyFriendlyNameForLogs",
  "url": "http://192.168.0.100:8070",
  "token": "AQZI58fA.rfSZbm",
  "priorities": {
    "info": 5,
    "warn": 7,
    "error": 10
  }
}


</details>

#### [Ntfy](https://ntfy.sh/)

Refer to the [config schema for NtfyConfig](https://json-schema.app/view/%23/%23%2Fdefinitions%2FNtfyConfig?url=https%3A%2F%2Fraw.luolix.top%2FFoxxMD%2Fmulti-scrobbler%2Fmaster%2Fsrc%2Fbackend%2Fcommon%2Fschema%2Faio.json)

multi-scrobbler optionally supports setting message notification priority via `info` `warn` and `error` mappings.

<details>

    <summary>Example</summary>

    ```json title="config.json"
    {
      "type": "ntfy",
      "name": "MyNtfyFriendlyNameForLogs",
      "url": "http://192.168.0.100:9991",
      "topic": "RvOwKJ1XtIVMXGLR",
      "username": "Optional",
      "password": "Optional",
      "priorities": {
        "info": 3,
        "warn": 4,
        "error": 5
      }
    }

Apprise

Refer to the config schema for AppriseConfig

multi-scrobbler supports stateless and persistent storage endpoints as well as tags/

<summary>Example</summary>

```json5 title="config.json"
{
  "type": "apprise",
  "name": "MyAppriseFriendlyNameForLogs",
  "host": "http://192.168.0.100:8080",
  "urls": ["gotify://192.168.0.101:8070/MyToken"], // stateless endpoints
  "keys": ["e90b20526808373353afad7fb98a201198c0c3e0555bea19f182df3388af7b17"], //persistent storage endpoints
  "tags": ["my","optional","tags"]
}
```

Health Endpoint

An endpoint for monitoring the health of sources/clients is available at GET http://YourMultiScrobblerDomain/health

Returns 200 OK when everything is working or 500 Internal Server Error if anything is not
The plain url (/health) aggregates status of all clients/sources -- so any failing client/source will make status return 500
- Use query params type or name to restrict client/sources aggregated IE /health?type=spotify or /health?name=MyMaloja
On 500 the response returns a JSON payload with messages array that describes any issues
- For any clients/sources that require authentication /health will return 500 if they are not authenticated
- For sources that poll (spotify, yt music, subsonic) /health will 500 if they are not polling

Files

configuration.mdx

Latest commit

History

configuration.mdx

File metadata and controls

Configuration

Configuration Types

Application Options

Base URL

Disable Web

Source Configurations

Configuration

Defaults

Only A Specific User

A Specific User + Defaults

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Configuration

Authentication

Configuration

Configuration

Configuration {#mopidy-config}

Configuration Options

URL

URI Blacklist/Whitelist

Album Blacklist

Configuration {#jriver-config}

URL

Configuration {#kodi-config}

URL

Configuration {#webscrobbler-config}

Multiple Users

Connectors Black/Whitelist

Configuration

Connecting Devices

mDNS Discovery

What Media Does MS Scrobble?

Allow Unknown Media Type

Forcing Media Tracking

Cast Troubleshooting

Configuration

Configuration

Enable HTTP Interface

Setting VLC Interface and Port

Configuration

Filename Parsing

Vlc Information Reporting

Client Configurations

Configuration

Configuration

Configuration

Monitoring

Webhook Configurations

Health Endpoint