Thanks for the directv info. Strangest thing, I was on directv website, tried to sign up, they said my email was invalid, and after that, I couldn't load any directv website. I kept getting access denied. Then spectrum started working. I'm wondering if my spectrum Internet is behind that? I've never had any problems like this. I'll be switching to directv at the next problem...
Tonight I had a recording fail on the Discover Channel because it would not authenticate on DirecTv or Spectrum. I am tired of trying different methods to unlock the "secret code or sequence" needed to get them to work. I suppose the developers, @tmm1, @maddox, and @eric, have determined that keeping TVE functional is either not worth their time or is not doable. If this is the case, then please tell the community.
Certainly the cable providers are making changes to impact the TVE usability. It seems that daily at least one member of this forum complains about one of the TVE providers service is broken. In my opinion Channels DVR service is becoming unusable for the purpose I have enjoyed using for a number of years.
2 Likes
I tried waiting a few days and attempted to add Spectrum back in as a TVE provider and yet still get the failed login due to bot detection.
I use Spectrum (west coast) and I've continued to periodically check and rescan the TLC channel... and every once in a while it seems to register, but gets the wrong guide data (east coast). Checking the channels.m3u file, it has the wrong grace note id. Can someone explain why all my other Spectrum TVE channels have west coast channel call letters and guide data, but TLC has the generic call letters (east coast) and shifted guide data (also east coast).
Most of the time when scanning TLC (and several others in my Spectrum line-up) I've received the dreaded "adobe auth reg code: no login form found". Some channels still work fine...it's a handful of them that don't or are finicky. Is this a known problem and being addressed...the problem with TVE and Spectrum has persisted for weeks if not months? Any help is truly appreciated.
1 Like
This morning, after updating to the new pre-release, v2026.08.27.0359, I was able to load Spectrum with no bot errors. Prior to loading I restarted my NAS server to clear the cache. All the channels authenticated much faster than they had the past few weeks. Thanks for the help.
Does this package include USA network? I have been having a hard time getting that from spectrum.
USA is DRM so no TVE from any source.
Ok bummer, thanks!
You'll want to look into Prismcast for USA stuff.
Looks like this has fixed my issue. Thanks for the fix!!
Using the latest pre-release build 2026.08.29.2212 was able to scan the spectrum channels... happy to see this was fixed.
Even with the scan now working, I'm still getting east coast TLC. In the past (prior to all the TVE issues) this wasn't a problem... it would load the correct guide data (for me is west coast). Viewing the Spectrum guide directly it's listed as TLCPHD... but the Channels TVE scan brings it in as TLCHD. Since it's a TVE source, we don't have the option of adjusting the channel identification/selection (other sources let you individually select/fix anything that doesn't match correctly). Is anyone else seeing this TLC guide misalignment? Will this be addressed in another pre-release? Any guidance/help is appreciated.
I only get 6105 TLC in my lineup, and I'm west coast.
But then I don't watch the channel, so wouldn't know if the guide is off.
With the latest pre-release update, I do get the channel 6105 TLC, but when I check it against the Spectrum app and TLC online guide, it's the wrong guide data (it's east coast).
I used to get the correct guide data until all the TVE issues over the last few months.
Did you actually watch the channel to see if it matches the guide data you get?
Maybe you're getting the East coast feed and the East coast guide data, like me.
1 Like
@chDVRuser, I can't thank you enough for pointing out the obvious. I checked TLC online, the Spectrum guide, etc... and the TVE channel streaming for Spectrum is truly east coast. I was matching the guides and couldn't get them to line-up, but apparently when you add the channel via TVE it's different than watching it directly through Spectrum... I never would have guessed that. This appears to be working fine and I just didn't realize it ... thank you so much!
I lost some of my Spectrum channels tonight and they wouldn't reauthorize when I scanned them, so I updated to the latest pre-release which is now 2026.08.30.2236. It still couldn't detect them, so I deleted and added the source again. Now I can't get any Spectrum channels. Just like a couple of weeks ago, I am getting the Blocked by Spectrum: their bot detection rejected the sign-in (IDID-4000). Please try again later message.
After too many authorization attempts, Spectrum will block the scans. Normally you can try again the next day. Once you do a scan and get most (some might still throw errors), rather than doing another full scan, just re-scan those individual channels.
To the attention of all Cox users who are being transitioned to Spectrum:
All of this is happening to me now, too, so yay!
With my Cox id-based lineup, most everything lost its connection overnight and I had to force a manual reconnection by faking a password change. I was able to get everything back except FS1/2, which are giving me false not entitled: mvpd: Resource is not supported by MVPD errors. I don't expect the devs to fix since Cox standalone is being retired. Interestingly enough, those stations are working elsewhere, like with EPlusTV. Also worth noting that some providers like NFL have already removed their option to select Cox, even though the Cox login still works most everywhere else, including its own watch website.
It's a safe to assume that all of those all those other websites are going to slowly remove their Cox connection, thus I decided to try to create a new TVE lineup with my migrated Spectrum login. With this new one, I appear to be locked out for the day with 26 expected stations giving me the Blocked by Spectrum: their bot detection rejected the sign-in (IDID-4004). Please try again later., so I guess I'll have to try again tomorrow!
For the record, I'm on prerelease v2026.09.14.0210.
Thanks for the heads up on this. Boy this was sudden. I noticed a couple of my fast channels stations that were authorized with cox no longer work. Did you figure out a workaround to fake a password change with the fast channels cox authorization? or was that with adb tuners using hdmi encoders?
@KineticMan