Jellyfin Live TV Not Working

In this tutorial, you'll learn about Jellyfin Live TV Not Working. We cover key concepts, practical examples, and best practices.

Hook

You configure an HDHomeRun or M3U playlist in Jellyfin Live TV. The channel list populates. You click a channel — black screen. No audio, no video, and the tuner status shows "Idle" even though you just requested a stream.

The Wrong Way

Adding dozens of M3U URLs at once or enabling every codec option in the tuner profile creates conflicts that make all channels unplayable.

<!-- BAD: Enabling every possible stream type -->
<StreamProfile>
  <VideoCodec>h264,h265,mpeg2,vp9</VideoCodec>
  <AudioCodec>aac,ac3,eac3,mp3</AudioCodec>
</StreamProfile>

Channel: BBC One — No signal or black screen
Tuner: HDHomeRun — Status: Idle

Too many codec options confuse the stream negotiation. The tuner sends a format the client cannot render.

The Right Way

Start with a minimal tuner profile and expand only as needed.

# Check HDHomeRun device detection
hdhomerun_config discover

hdhomerun device 12345678 found at 192.168.1.100

In Jellyfin Dashboard → Live TV:

1. Tuner Device: Select HDHomeRun or M3U Tuner.
2. Stream Profile: Set to Default (H.264 + AAC).
3. Channel Scan: Run a fresh scan.
4. Test: Open a channel directly in Jellyfin Web.

# Test the raw stream with ffplay
ffplay "http://192.168.1.500:5004/auto/v1"

If the raw stream plays but Jellyfin shows black, the issue is the transcode profile. Change the tuner's stream profile to Native (pass-through) and disable transcoding for Live TV.

Prevention

• Use a wired HDHomeRun — Wi-Fi tuners drop packets.
• Keep your M3U playlist file local (not a URL to a remote server).
• Test each new channel source with ffplay before adding to Jellyfin.
• Set Live TV transcoding to Remux only if your clients support the stream format.
• Check Jellyfin logs for LiveTV errors during channel tuning.

Advanced Troubleshooting

Check the Logs

Most TOOL errors are logged to stdout or a dedicated log file. Check your logs first:

# Check system logs
journalctl -u tool --since "1 hour ago"

# Or check the application log
tail -50 ~/.tool/logs/error.log

Test with a Minimal Example

Create the simplest possible tool configuration to verify the base setup works:

tool --version
tool --help

If the minimal test passes, add configuration options one at a time until you find the breaking change.

Common Configuration Mistakes

• Using the wrong file path or URL in configuration
• Forgetting to restart TOOL after changing config files
• Mixing tabs and spaces in YAML configuration files
• Setting incorrect permissions on configuration directories

When to Reinstall

If none of the above resolves the issue, consider a clean reinstall:

# Backup your configuration
cp -r ~/.tool ~/.tool.bak

# Remove and reinstall
# Follow the official TOOL installation guide

This ensures you start from a known good state and can isolate the issue.

Common Mistakes with live tv

1. Forgetting deriving (Show, Eq) on custom data types needed for debugging
2. Placing the wildcard pattern first in case expressions, making all subsequent patterns unreachable
3. Using head and tail instead of pattern matching, causing runtime errors on empty lists

These mistakes appear frequently in real-world JELLYFIN code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

DodaTech — TV, your way, on your server.