+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: HDHR Tuners remain locked (/t-hdhr-tuners-remain-locked)
HDHR Tuners remain locked - PaulMc - 2023-11-12
I've Jellyfin installed in docker on a QNAP and use an HDHomeRun for Live TV. Recordings work fine. If I view a channel from the Channels tab or via the Play button on the Guide details page then when I exit the program the tuner remains locked. Eventually (after four channel changes) there are no more tuners available. From this point channel changes no longer work and recordings fail. Viewing live tv via the HDHomeRun app works as expected and it releases the tuner when exiting the program. It is clear from the HDHR Status page that Kellyfin is the locking the tuners and not releasing them. My only course of action appears to be to restart the Jellyfin container on the NAS which releases the locks. Is there a setting that I'm missing to make this work as expected?
RE: HDHR Tuners remain locked - HokieRulz - 2024-01-17
I'm also having this issue.
Jellyfin Server: 10.8.13 docker on linux mint 21.3
Jellyfin Android Client: 2.6.0
Tuner: HDHomeRun Extend
I first check my HDHR web interface to ensure that no tuners are in use, and then start watching Live TV on the Jellyfin android client. I then click the back arrow (again in the android client) and it correctly returns to the guide. The web dashboard correctly notes under "Activity" that the client has finished playing. However, when I check the HDHR web interface, it still shows that the tuner is in use. The best way I have found to release the tuner is to restart the Jellyfin docker container - I can find no actions in Jellyfin that will release the tuner.
Additional testing suggests this is specific to the Jellyfin android client. The tuner is correctly released when using any of the following clients to watch Live TV: the Jellyfin Media Player on Windows, the web client in Chrome on Windows, and the web client in Chrome on Android. Currently my workaround is to use the web client in Chrome on android - but I would much prefer to use the android client instead.
Thank you everyone for all of your great work!