2026-08-27, 01:25 PM
(This post was last modified: 2026-08-27, 05:30 PM by HokieRulz. Edited 1 time in total.)
I'm seeing the same issue with the Jellyfin android client when using either server v10.11.11 or v12rc6. There is already an issue opened on github, I added a comment there with my experience. Switching the JF android client to the web player instead of exoplayer makes it work for me. People are also saying that downgrading the android client to v2.7.0 works. If you switch your android client to use the web player instead of exoplayer, does it work for you to playback channel 4.1 in the JF android client from your HDHR? (Edit: This issue for the JF android client is now closed and marked as fixed by PR#2155. I would assume it will be part of android client v2.7.2 when it is released.)
A shot in the dark: Do you have good signal strength on channel 4.1? Does the problem happen on all channels or only this one channel? Open your HDHR web interface and go to the tuner0 (assuming no other hdhr playback happening) detail page , start playback in jellyfin, then quickly refresh the page in the HDHR web interface to get signal strength, signal quality, and symbol quality. If you use the HDHR client instead of Jellyfin, does playback work? Also look at your HDHR logs to make sure your the HDHR watchdog isn't rebooting your HDHR.
For zap2it.tmsimg.com, there is a bad url for every show in your guide data... so thousands. It will only help the playback issue if there is some new issue/requirment in JF server v12, but it would be a good idea to update your guide data source. The original https://github.com/jef/zap2xml was great, but it hasn't been updated for over a year and a lot has changed. There are a bunch of forks of it on github, and I'm sure someone has addressed the issue. I use https://github.com/shuaiscott/zap2xml - it seems to be fairly well maintained, and he has updated the asset url multiple times since the original zap2xml script. Since it's docker, all I have to do is run a "docker compose pull" to get updates.
For the logo.iptveditor.com, it looks like you have an IPTV tuner as well? If so logo.iptveditor.com is probably coming from that. I don't think it is causing the hdhr playback issue, but you might want to look into why there are references to a website that doesn't exist in your IPTV data.
Do you have multiple HD Homerun tuners? Your logs are showing two, one at 192.168.2.25, and another at 192.168.2.26. In the logs the playback attempt was from 192.168.2.25, and it looks like the hdhr at 192.168.2.25 at least initially responded normally. I'm just getting a handle on your environment looking for things that might cause issues.
In your JF server transcode config, if you uncheck "Allow encoding in AV1 format" and click save, then does you mpeg2 movie still play?
A shot in the dark: Do you have good signal strength on channel 4.1? Does the problem happen on all channels or only this one channel? Open your HDHR web interface and go to the tuner0 (assuming no other hdhr playback happening) detail page , start playback in jellyfin, then quickly refresh the page in the HDHR web interface to get signal strength, signal quality, and symbol quality. If you use the HDHR client instead of Jellyfin, does playback work? Also look at your HDHR logs to make sure your the HDHR watchdog isn't rebooting your HDHR.
For zap2it.tmsimg.com, there is a bad url for every show in your guide data... so thousands. It will only help the playback issue if there is some new issue/requirment in JF server v12, but it would be a good idea to update your guide data source. The original https://github.com/jef/zap2xml was great, but it hasn't been updated for over a year and a lot has changed. There are a bunch of forks of it on github, and I'm sure someone has addressed the issue. I use https://github.com/shuaiscott/zap2xml - it seems to be fairly well maintained, and he has updated the asset url multiple times since the original zap2xml script. Since it's docker, all I have to do is run a "docker compose pull" to get updates.
For the logo.iptveditor.com, it looks like you have an IPTV tuner as well? If so logo.iptveditor.com is probably coming from that. I don't think it is causing the hdhr playback issue, but you might want to look into why there are references to a website that doesn't exist in your IPTV data.
Do you have multiple HD Homerun tuners? Your logs are showing two, one at 192.168.2.25, and another at 192.168.2.26. In the logs the playback attempt was from 192.168.2.25, and it looks like the hdhr at 192.168.2.25 at least initially responded normally. I'm just getting a handle on your environment looking for things that might cause issues.
In your JF server transcode config, if you uncheck "Allow encoding in AV1 format" and click save, then does you mpeg2 movie still play?
