I have a collection that is missing a channel in the admin web Grid Guide filtered view. I've tried removing the missing channel and adding it back in but it still is missing. CH 6000
256b011d-5aaa-4b9d-915e-795cdd526935
I have a collection that is missing a channel in the admin web Grid Guide filtered view. I've tried removing the missing channel and adding it back in but it still is missing. CH 6000
256b011d-5aaa-4b9d-915e-795cdd526935
Please submit diagnostics.
The diagnostics token is on the last line.
@maddox, I’ve noticed a possibly related bug with channel collections on the web EPG: if you have multiple sources and any channel in your collection has a channel number that conflicts with a channel number from an HDHR source, those channels will be missing in the web EPG.
I have an HDHR on my network that shows up in Channels as a source but is not configured (I instead access it through an M3U so I can set more logical channel numbers). Even though the HDHR isn’t set up, its channel numbers still seem to have influence in Channels. For example, in my M3U channel 32 is ITV2; on my HDHR channel 32 is 5STAR. I’ve added channel 32 to my ‘General’ channel collection, but it’s missing in the web EPG. It appears as expected (as ITV2) on clients.
The same issue happens with Pluto channels if you added the M3U and selected ‘prefer channel numbers in M3U’. If any of the Pluto channel numbers conflict with the unconfigured HDHR, they will disappear in channel collections on the web EPG.
Is this in general, or specifically when filtering with a Channels Collection.
In other words, was this happening before the introduction of Channel Collections in the web guide?
I would highly suggest not using this setting and doing the best you can to avoid conflicting channel numbers.
Yes, I believe it was, though it's difficult to explain. It always had odd behaviour when things were marked as favourites and selecting the favourites view in the web EPG. I believe the channels would show up but sometimes the wrong one if there was a number conflict with the HDHR or with mismatched guide info. But, you could sort of get around the issue if you changed the source to anything except 'all sources'. It then seemed to follow the channel numbering from that source...and interestingly it would still show favourites from other sources (I don't know if that was a bug or feature
).
Is there a way to block the HDHR auto-discovery? I'm running Channels in a Docker container with macvlan networking so all my clients see Channels as a standalone device on my LAN and can access it directly. As a consequence Channels does pick up the HDHR broadcasting its presence and dutifully adds it.
The only reason I like 'prefer channel numbers' for Pluto is that it groups the channels nicely into their genres. Without it, the channels seem to get assigned numbers in a random order, which makes for a lot of manual sorting and makes it more difficult to see when new channels have been added or removed.
Any suggestions for keeping them nicely grouped in genres?
HDHR tuners send out broadcast packets on 65001/U. You could have your firewall block incoming packets on that port to your macvlan address.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.