Thank you Jason, that is what I suspected. Leave it to Spectrum to only provision one of my CableCARDs properly when a new channel is added to the lineup. I can't wait to waste another half day with a service tech in my basement...

Good, sounds like I don't need to worry about that when the time comes to upgrade my firmware. As far as channel 291 goes; I'm hoping Jason can figure something out, it seems like whenever I have to involve Spectrum they need to roll a truck and spend a half day in my basement to correct an issue ...

So, for clarification: both of my Primes are still on 20250623, and they both currently show "Card Validation success". When I decide to upgrade to 20260313, will my card validation switch to none, or should it continue to show success?

Performed the following steps:

Enabled diagnostic data for both devices
Powered-off then powered-on both devices
Ran channel scans for both devices

13231929 - channel number 291 (DSN) was found by the channel scan and I am able to view the channel without issue
13256C0B - channel number 291 ...

OK, so the good news is that Spectrum has added the new channel to their lineup so that I can watch the Detroit Tiger games. I've performed a number of channel scans for my two Primes, and here are the results:
One Prime consistently detects the new channel during the scan, and I am able to view ...

The webpage for the Prime might give some clues.

So if the channel has become available and is not DRMd, the Prime would be able to stream it over ethernet whether or not a channel scan has been performed since the channel was added, correct?

Also, when the AVC icon is displayed for a channel, does that imply MPEG-4 format? Is it possible that ...

My favorite MLB team is no longer being broadcast on FSN, they are standing up a brand new cable channel instead. I do not really use the SD software, I run SageTV/OpenDCT to watch and record content from my Primes. OpenDCT is a network encoder that directly interfaces with the Prime; I don't know ...

@petelombardo, I have run into situations in the past where the developer of a piece of software/freeware discontinues support and enhancements, for whatever reason. Unless there is another developer with the coding skills required to pick up where the original developer left off, it becomes "use at ...

rikd wrote: Mon Feb 16, 2026 6:55 am Might take some time for the template update to make it's way through.

The template update finally arrived, I'm running successfully in Bridge mode.

just remember also to specify the devices with the variable if you do switch to bridge mode as autodiscovery will stop working.

According to comments on a recent commit (in github),
This adds an HTTP fallback using the HDHomeRun cloud API (ipv4-api.hdhomerun.com/discover) when UDP finds no ...

It still does not seem to want to install with Bridge as the default. Here are the steps that I performed:

Stopped the docker
Removed the docker (with the 'also remove image' checkbox checked
From the community Apps screen, clicked on 'Previous Apps', then 'Docker'
Checked the checkbox next to ...

petelombardo wrote: Sun Feb 15, 2026 7:14 am I just pushed an updated template. The new one should use bridge mode by default with the correct port mappings.

Hmmm, I just removed the docker and then installed it again. It's still installing as a "Host" Network Type. Maybe I need to try again later?

I noticed a change that was recently made to the Signal Strength app:

Add HTTP fallback discovery for HDHomeRun devices; switch Docker to bridge networking

After I updated the docker (within Unraid), I tried modifying the docker Network Type to Bridge (from Host). After the docker was restarted ...