I have two HDHomeRuns networked to my server and thus have two channels at most channel numbers. This mostly works, but it seems like adding channels to Channel Collections ends up adding the wrong channel using channel number as a key rather than [source + channel number]. Any tips on how to handle this?
You would need to import the remote HDHR as an M3U with modified channel numbers
Thanks, that seems like a workable solution (for future readers' reference, [HDHR IP]/lineup.m3u gets a playlist directly from the HDHR).
The main issue there is just that when using custom channel numbers + downloaded OTA XMLTV, looks like I have to manually link every channel in the lineup to its corresponding guide data due to the custom channel numbers obviously not matching guide data. Not the worst thing in the world since it's a one-time thing, but would be great if the guide data could link by M3U channel id/number rather than by the custom ones.
Check out the playlist manager docker container, you can import the hdhr m3u and then build your own m3u with transposed channel numbers. Then use the olivetin docker contamer to lookup the gracenote id's for each channel and then add that to playlist manager. The end result will be an m3u that will automatically have each channel matched even though the channel number is different.
I used to effectively do this by feeding the playlist + EPG from a second Channels server over to Threadfin/Xteve to remap channel numbers and then feed that to my primary Channels server, but wanted to get rid of the extra dependencies to minimize hiccups & latency with the multiple proxies involved with that setup and just connect my primary Channels server directly to the second HDHR. I've ended up settling for using that HDHR playlist and manually mapping the channels I care about, which is working smoothly.
Looks like I spoke too soon without actually trying the Collections side again. Even with the modified channel numbers, seems like the this feature relies on the channel IDs rather than the channel numbers, and so this issue persists despite ignoring channel numbers from the HDHR's playlist. I tried the PUT request manually using the channel number and it does not reflect the channel correctly in the collection afterwards (claiming channel 2002 doesn't exist), so this seems like expected behavior and that collections are listing channel IDs on the backend rather than channel numbers.
@tmm1 Is there any way to handle this within Channels or does this use case require using workarounds like above to remap channel IDs from the original playlist?
Ah yes you're right it requires unique IDs to tell the channels apart
