Teleemix

Your music, your server, your phone. No friction.

→ Full documentation on the Wiki

A fast, lightweight Telegram bot written in Rust for requesting music downloads via your self-hosted deemix instance — from your phone, without ever touching the deemix web UI or dealing with ARL logins.

Supports Deezer URLs, Spotify links, YouTube, YouTube Music, Apple Music, voice search, song recognition, and free-text search.

• 🎵 Send a Deezer URL (track, album, playlist) → queued instantly
• 🔗 Send a Spotify link (track, album, or playlist) → looked up and queued automatically
• 🎬 Send a YouTube or YouTube Music link → resolved via Odesli and queued on Deezer
• 🍎 Send an Apple Music link → resolved via Odesli and queued on Deezer
• 🔍 Send a song or artist name → search results shown as buttons to pick from
• 🎤 Send a voice note → transcribe what you said and search (requires OpenAI key)
• 🎵 Send a voice recording of a song → identify it and queue it (requires AudD key)
• 📲 /menu — quick action keyboard buttons
• ⚙️ /settings — per-user settings with toggle buttons
• 💿 /album — search albums
• 🔔 Restart notifications — opt-in per user via /settings
• 🔄 /updatearl — update your Deezer ARL interactively via Telegram
• 📊 /status — shows pending, downloading, and completed queue items separately
• 🧹 /clearqueue — clear completed downloads from the deemix queue
• 🔒 Optional user allowlist to restrict access
• ⚡ Written in Rust — tiny memory footprint, static binary, no runtime dependencies

• A running deemix instance
• Docker + Docker Compose
• A Telegram bot token (from @BotFather)
• A Deezer account (free or paid; paid required for lossless)

1. Open Telegram and message @BotFather
2. Send /newbot and follow the prompts
3. Copy the token it gives you

For step-by-step instructions on how to find your Deezer ARL token in your browser, see this guide: How to Get Your Deezer ARL. Alternatively, a clean browser-based guide is available here.

The ARL lasts several months. When it expires, use /updatearl in Telegram to update it without touching the server.

cp .env.example .env
nano .env

Fill in all the values — see .env.example for descriptions of each variable.

⚠️ Teleemix requires deemix to run with DEEMIX_SINGLE_USER=true. Without this, deemix runs in multi-user mode and Teleemix will get NotLoggedIn errors. Add this to your deemix environment variables:

DEEMIX_SINGLE_USER=true

Edit docker-compose.yml and update the left side of these volume mounts to match your setup:

volumes:
  - /path/to/your/docker-compose.yml:/compose/docker-compose.yml
  - /path/to/your/.env:/app/.env
  - /path/to/your/data/registered_users.txt:/app/registered_users.txt
  - /var/run/docker.sock:/var/run/docker.sock

Create the registered users file before starting:

touch /path/to/your/data/registered_users.txt

docker compose pull
docker compose up -d

Send a voice note saying a song or artist name. Teleemix transcribes it and searches Deezer.

Three backend options — choose one:

Option 1 — OpenAI remote API (easiest, pay-per-use ~$0.006/min)

OPENAI_API_KEY=sk-your-key-here

Sign up at platform.openai.com.

Option 2 — Local compatible server (any OpenAI-compatible Whisper server)

WHISPER_URL=http://your-whisper-server:8000/v1/audio/transcriptions

Works with faster-whisper-server, whisper.cpp, or any compatible server.

Option 3 — Built-in local Whisper (no API key needed, runs in Docker)

Uncomment the whisper service block in docker-compose.yml, then set:

WHISPER_URL=http://whisper:8000/v1/audio/transcriptions

The default model is small which supports 99 languages including Dutch, English, and Arabic. To change the model, update WHISPER__MODEL in the compose file:

After changing the model, recreate the container:

docker compose up -d --force-recreate whisper

Send a voice recording of a song playing. Teleemix identifies the song using AudD and queues it.

AUDD_API_KEY=your-key-here

Free tier gives 100 recognitions/month. Sign up at audd.io.

Both features are optional — leave keys/URLs empty to disable. Users can toggle them individually in /settings.

The default download quality is set via DEEMIX_BITRATE in your .env:

Users can change the quality on the fly via /settings → 🎚️ Quality. Each tap cycles through the options.

⚠️ Quality changes in /settings affect all users on the server immediately, since the setting is shared in memory. The change resets to the DEEMIX_BITRATE default when the container restarts.

To lock the quality and prevent users from changing it, set:

DEEMIX_BITRATE_LOCK=true

When locked, the quality button in /settings shows a 🔒 and tapping it shows a message that it is administrator-locked.

Every user has their own settings managed via /settings:

Settings are stored in users.json and persist across container restarts.

docker compose pull
docker compose up -d

If you want Teleemix to update itself automatically whenever a new image is published, you can use Watchtower or an alternative like Diun.

Watchtower example — add to your compose file:

  watchtower:
    image: containrrr/watchtower
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    command: --interval 86400 teleemix
    restart: unless-stopped

This checks for a new teleemix image once a day and updates automatically.

⚠️ Only recommended if you trust the source. For production use, pin to a specific image digest instead.

Teleemix relies on Telegram's built-in access control rather than maintaining its own allowlist. Since only users who know your bot's username can message it, keeping your bot token private is the main security measure.

To restrict access further via @BotFather:

1. Message @BotFather → /mybots → select your bot
2. Bot Settings → Allow Groups — disable to make it private message only
3. Bot Settings → Group Privacy — controls what the bot can see in groups

For more detail see the Telegram Bot documentation and the project wiki.

Enable "🔔 Restart notifications" in /settings. From then on, every time the container restarts you will receive a message letting you know the bot is back online.

When your Deezer ARL expires, send /updatearl to the bot. It will prompt you to send the new ARL, then:

1. Re-logs into deemix immediately
2. Updates the ARL in your .env file so it persists across restarts

To run the experimental version, change the image tag in docker-compose.yml:

image: ghcr.io/asupersheep/teleemix:dev

• Rust
• teloxide — Telegram bot framework
• tokio — async runtime
• reqwest — HTTP client