Lidarr joins your queue.
Lidarr does for music what Sonarr does for TV, and Tillarr treats it the same way. The first beta watches it by its address; during the beta it gets its own pages and joins the shared download queue.
What you see
- Whether it answers, how quickly, and which address answered
- A tap to open its own web page
What's next
During the beta: artists and albums with what's monitored and missing, a release calendar, missing albums, and its downloads in the shared queue. Add an artist, search for an album, and remove or blocklist a download.
Connect Lidarr
What to have ready when you add it in Tillarr.
- Its address. Usually http://your-server:8686. Add a remote address too, and Tillarr uses it when home doesn't answer.
- Nothing else. Watching needs no key and no login, so it's free and can't change anything in Lidarr. When full support arrives, Tillarr asks for its key.
Good to know
- Lidarr has no "needs manual import" event, so import and download failures are the signals Tillarr watches for.
- Lidarr 3 removed the web UI's basic login. Its API key isn't affected, and Allowed Hosts applies as in Sonarr.
Behind a sign-in page
If a sign-in page guards Lidarr, let /login through so the check can reach it. The remote access guide shows how.
How Tillarr checks Lidarr
Without a key, Tillarr asks for /login to see that Lidarr is up. Every request goes from your device straight to your server, never through us. Works with Lidarr 2 and 3 (API v1).
Questions
When does Lidarr get full support?
During the public beta, with SABnzbd, NZBGet, Transmission, Plex and Tautulli. Until then Tillarr watches it, which is free.
Will Lidarr share the download queue?
Yes. Its downloads join Sonarr's and Radarr's in one queue, matched to the torrent or Usenet item behind them.