Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Channels not listed, but numbered in Tvheadend starting from 1 (radio) and 100(tv) #47

Open
bugsyb opened this issue Jan 7, 2022 · 2 comments

Comments

@bugsyb
Copy link

bugsyb commented Jan 7, 2022

Tvheadend works properly, shows channels and all is visible and works from Kodi perspective.
Channels got numbered automatically by Tvheadend when created from services even if there's no setting at Network level anymore. When checking channels it looks all good from numbers perspective.

Jellyfin even if connects properly doesn't see any channels. All references under other issues (#13) were down to channel numbering, but it doesn't seem to be the case here.

Where could I start looking to get some better understanding of what's wrong?

Docker based (all):
Tvheadend: 4.3-1986~g09a2c71ab, arm64v8

Jellyfin: Version: 10.7.7, Linux Arm
Jellyfin-tvheadend plugin: 9.0.0.0, tried v7.0.0.0

Checked of course steps from:
https://jellyfin.org/docs/general/server/plugins/tvheadend.html
There's nothing like this in current Tvheadend even if channels got numbered automatically starting from 1:

Automatic mode
Go to Configuration > DVB Inputs > Networks
Select the network you want and press Edit
In the option Channel numbers from we enter the number so we want the numbering of the channels to start (for example: 1), this number must be nonzero

Uploading Screenshot from 2022-01-07 11-44-18.png…

@bugsyb
Copy link
Author

bugsyb commented Jan 9, 2022

Coming back, just to state that with no action from my end it works now. Literally nothing has been done, potentially a reboot, but that doesn't make sense as both tvheadend and jellyfin were restarted when trying to troubleshoot above.

I'd be still keen to understand where to look should similar problem arise in the future and for others.

Thank you.

@sirjeannot
Copy link

in case it helps, I encountered the same issue in an all dockerized environnent (tvheadend+jellyfin) on the same host.
the issue was the jellyfin account in tvheadend which I filtered to come from the NIC IP (192.168.x.x) but tvheadend logs showed me jellyfin coming from the internal docker address 172.16.x.x.

tvheadend 4.3-2095~g470f02fb3
jellyfin 10.8.9
jellyfin tvheadend plugin 11.0.0.0

before
2023-02-15 14:19:24.589 htsp: 172.17.0.1: Identified as user 'jellyfin' (unverified) 2023-02-15 14:19:24.589 htsp: 172.17.0.1 [ jellyfin ]: Welcomed client software: TVHclient4Emby-10.8.9.0 (HTSPv20) 2023-02-15 14:19:24.600 htsp: 172.17.0.1 [ jellyfin | TVHclient4Emby-10.8.9.0 ]: Unauthorized access 2023-02-15 14:20:51.366 htsp: 172.17.0.1 [ jellyfin | TVHclient4Emby-10.8.9.0 ]: Disconnected

after adjusting the allowed networks in tvheadend
image

2023-02-15 14:21:12.576 htsp: 172.17.0.1: Identified as user 'jellyfin' (unverified) 2023-02-15 14:21:12.576 htsp: 172.17.0.1 [ jellyfin ]: Welcomed client software: TVHclient4Emby-10.8.9.0 (HTSPv20) 2023-02-15 14:21:12.587 htsp: 172.17.0.1 [ jellyfin | TVHclient4Emby-10.8.9.0 ]: Identified as user 'jellyfin' 2023-02-15 14:21:12.587 htsp: 172.17.0.1 [ jellyfin | TVHclient4Emby-10.8.9.0 ]: Privileges updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants