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

Kodi HTS PVR addon not updating TV channel number change from backend? #694

Open
slrslr opened this issue Jan 12, 2025 · 7 comments
Open

Comments

@slrslr
Copy link

slrslr commented Jan 12, 2025

Hello,

I have found that the newly added channels into TVHeadend backend were automatically loadeded to the Kodi TV (I have enabled automatic syncing from backend).

But it was added to the end of the list with large/automatic numbers, despite that in TVheadend backend, I have set custom low numbers. My Kodi TV sorts channels according to a number set in backend.

I suspect that it happened because client downloaded the channels from backend at the time when I have not yet set the numbers to the new channels. And then did not sync (overnight) the changed number from backed once I have updated it.

I think that the client should be regularly (and pretty often like minutely or even earlier) syncing even these minor changes like channel number change.

After disabling PVR client addon and enabling or after system restart, it helped to add the channels with proper numbers. But this should not be needed to bother manually disabling client PVR addon or rebooting the system.

TVHeadend version/package: xbian-package-tvheadend/stable,now 4.3-2190-1704695301 armhf

@ksooo
Copy link
Member

ksooo commented Jan 12, 2025

Which Kodi version exactly? Debug log with PVR component debugging enabled, please, to reproduce.

@ksooo
Copy link
Member

ksooo commented Jan 12, 2025

I think that the client should be regularly (and pretty often like minutely or even earlier) syncing even these minor changes like channel number change.

No, it works the way that tvheadend must notify changes whenever they happen. It's a push approach, not pull. Don't know yet, but could be a tvheadend issue. We need to find out.

@jansohn
Copy link

jansohn commented Jan 12, 2025

I think that the client should be regularly (and pretty often like minutely or even earlier) syncing even these minor changes like channel number change.

No, it works the way that tvheadend must notify changes whenever they happen. It's a push approach, not pull. Don't know yet, but could be a tvheadend issue. We need to find out.

I don't think this makes sense. Clients are not permanently connected to the server. And the server does not even have a list of all clients as far as I know.

@slrslr
Copy link
Author

slrslr commented Jan 12, 2025

Kodi (20.3 (20.3.0) Git:20240111-cfbcba599c-dirty). Platform: Linux ARM 32-bit
I do not know why, but this time the TV channel number shown in Kodi, changed quickly (under couple of minutes maybe) after updating in backend. I have not tried to add new TV channel, just update numbers of previously added channels.
I know this log file /home/xbian/.kodi/temp/kodi.log and inside it I know how to "Enabled debug logging due to GUI setting. Level 2." selecting PVR.

@ksooo
Copy link
Member

ksooo commented Jan 12, 2025

I don't think this makes sense. Clients are not permanently connected to the server. And the server does not even have a list of all clients as far as I know.

It makes perfect sense, as when a new client connects, the data are synced. This is proven to work just fine for years.

@jansohn
Copy link

jansohn commented Jan 12, 2025

I don't think this makes sense. Clients are not permanently connected to the server. And the server does not even have a list of all clients as far as I know.

It makes perfect sense, as when a new client connects, the data are synced. This is proven to work just fine for years.

I know that it works just fine but I don't think it qualifies as a push mechanism as you've described it.

@ksooo
Copy link
Member

ksooo commented Jan 12, 2025

Now what?

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

3 participants