You probably didn't see the first post starting this thread where I said it was a P+ problem,
"Paramount+ only works on one wireless Joey but not on any of the other devices. Been through all the network router resets and now Paramount support admits it is their problem and I have an unresolved open ticket."
I do have other devices I can watch it. Football is better on a bigger screen than a phone or tablet and screen mirroring invariably has screen break ups. I can buy another firestick or move it around from room to room.
I know that we are now expected to tolerate "glitches". When I ran a software company we called them bugs and got on fixing them or rolling back updates ASAP.
The more we put up with poor service the more we will get IMHO. You'd think Dish would have a big enough base they'd want to fix it.
Ok, latest update. Paramount+ support sent me an email about this known ongoing bug and some potential fixes. None of them worked.
But, while I was fiddling with my routers and such, I thought I'd try running the hopper+ Internet off my primary LAN network.
I have two ISPs and two separate LANs. My primary LAN has a commercial grade non WiFi router with 2 wired wifi access points with hot WAN failover to my backup ISP (starlink) and has around 55 wifi devices on it.
I had the hopper+ connected to my Backup starlink router and LAN because the Starlink wifi router was closer and had a better signal to the hopper, has less 5G channel interference with only the Starlink router in the 5G channel group, only has 7 devices on the router, far less LAN traffic and being a generic off the shelf router configuration has been more acceptable to peculiar apps and devices than my primary LAN which has layers of intrusion protection and network monitoring software & hardware, etc.
I started to wonder if Paramount + might be having issues with Starlink. My primary ISP is a microwave connection to a local tower connected to fiber. It's latency consistently is 15-20 ms, versus Starlink 35-70ms, jitter is 4-7 versus Starlink 22-35, rarely has packet losses versus Starlink <0.4%. Speed on primary WAN is consistently (in mbps) 70-90 DL, 15-25 UL versus Starlink 30-250 DL and 8-35 UL.
So, I connected the hopper+ to my primary WAN, and Shazam!!! Paramount + worked on all four of my Dish devices.
So, I thought, ok, Paramount + must have some low level signal quality checks that didn't like the jitter, packet losses or latency causing the "oops, connection problem " on my Starlink router.
That would be easy enough to test by switching my router WAN failover settings to swap primary and back up WAN connections. Now, hopper+ is on my congested primary LAN but is accessing the Internet through Starlink with all the jitter, latency and packet losses that go with it.
To my surprise, PARAMOUNT + STILL WORKED! and has done so over the last week. So, all I can say is that the Paramount + known problem seems to be an issue with the Starlink router as the primary router. (Keep in mind with the Starlink router behind my primary router, all the internet traffic is double NATing.)
I'd be curious if anyone else with Starlink as their primary router and Dish hopper plus is having this problem with Paramount +?
The Starlink router is such a simple, generic basic setup, I can't imagine why it would cause this bug to be exposed and I imagine there a many other basic routers that would have this problem too.