Bug Fix Release: Jellyfin API Compatibility & Diagnostics
Fixed Issues
Badge Processing Not Working
- Resolved: Batch jobs and preview generation failing to apply badges due to Jellyfin API compatibility issues
- Root Cause: HTTP 400 errors when using general Jellyfin metadata API (
/Items/{id}) - Solution: Updated badge processors to use user-specific API (
/Users/{user_id}/Items/{id}) which has better compatibility - Impact: Badge processing (audio, resolution, etc.) now works reliably across different Jellyfin configurations
New Features
Jellyfin Diagnostics Page
A comprehensive new diagnostics page to help troubleshoot Jellyfin connectivity issues:
- Connection Test: Verify basic Jellyfin server connectivity
- Configuration Check: Validate API settings (URL, API key, User ID)
- Media Sample Tests: Test API compatibility with real media items from your libraries
- Custom ID Testing: Debug specific Jellyfin item IDs that are causing issues
Access via the new Diagnostics link in the sidebar navigation.
Technical Improvements
- Enhanced error handling with specific HTTP status code explanations (400, 401, 404)
- Improved logging to help identify Jellyfin API issues
- Media tests now use live Jellyfin data instead of requiring database scans
- Better fallback handling between different Jellyfin API endpoints
For Users Experiencing Badge Issues
If you were experiencing problems where:
- Batch jobs appeared to run but no badges were applied
- Preview generation showed "Applied: []" in logs
- HTTP 400 errors appeared in Jellyfin service logs
This release should resolve those issues. Use the new Diagnostics page to verify your setup is working correctly.
Resolves: Issue #70 - Badges not applying during batch processing