My cookie expired this morning and I had to reauthenticate, so it seems like T-Mobile hasn’t fixed things on their end for everyone. Regardless, No issues on Channels’ end.
Hi, all -
Sad to say - MSNBC is no longer authenticating on my T-Mobile Source. Started happening this morning sometime prior to 3am. It was working fine yesterday and had authenticated properly for the first time in a long time. Now, it says cable provider authentication failed and I am getting a T-Mobile (?) text message w/ a 6 digit verification code to my phone around the same time but with no place to enter the code in Channels.
Anyone else experiencing this?
FYI... I have tried to authenticate the MSNBC channel using Chrome and Safari browsers on a Mac OS Big Sur today using the latest pre-release as of a few minutes ago. I have not tried to re-authenticate all the T-Mobile channels at once for fear that all the other channels will disappear from Channels authentication.
Interesting... TLC shows up as an authenticated channel on my T-Mobile source. I subscribe to the TVision Live subscription level (not TVision Live+). Did you try re-authenticating those "No Log In Form found" channels individually. When I did that yesterday, the few that I had to do that to authenticated fine.
That is what I was doing, which is what caused a 2FA code to be sent to my phone, similar to what you described for the reauthentication of MSNBC, but also with no visual indication from within the DVR menu (just the "spinning wheel" for lack of a better term) until I closed out of the edit window. This was a few hours after I initially authenticated the original channels, so it is possible if I delete the source and add it again, I can keep whatever authentication cookie is initially sent and try to immediately fix any initially scanned channels that get skipped. If we’re going to need to do this on a daily basis (no fault of the developers), I am likely not going to keep T-Mobile as a provider.
I did have to reauthenticate today. After Channels was done scanning, I did see a few channels where the no login error occurred for channels I know are part of my package. Rescanning those immediately enabled them without needing additional authentication. As or right now, it does look like TMobile authentication will only last for 24 hours?
Anyone else using the Docker container with T-Mobile successfully? My docker gets stuck at authenticating when trying to add T-Mobile as a provider, I get nothing except the spinning arrow. Then my Unraid server running the docker pegs the CPU and Channels becomes unresponsive. I have to restart Channels. I really want to dump my cable provider but T-Mobile seems to be purposely making this difficult and it doesn't seem to work on the Docker container. Could be me, not sure how.
Happy Camper again!
After applying the latest beta release of Channels and authenticating my T-Mobile source (at the source level, not individual channel level), all of my subscribed TVision channels come in and allow me to record (including CNN, MSNBC, etc.)! I have not tested access to every single channel, but all appears fine. At least for now. Only time will tell if I will have to authenticate on a daily or periodic basis (sure do hope not). Byron (T-Mobile tech) said I would NOT have to re-authenticate again unless T-Mobile changed their security protocol down the road or I changed my subscription. So, here's hoping he's correct. If not, I will hold T-Mobile accountable for this and see where that goes.
For now, I will stay with T-Mobile because of their price point for the channels I'm most interested in having. This gives me access to Live and Recorded TV watching w/ auto commercial skip! Plus, free MLB app access again this year - can't get that anywhere else at the moment....(will need add'l VPN subscription to avoid those darn blackouts but can't get around that).
Thanks for everyone that has been working on this, nice to be getting somewhere with this, I had some channels that would just spin forever and it would not go past them, just had to stop process, but better than it was.
I had to authenticate again tonight... tried to use a channel and got a text from TMobile asking to enter my 2FA code. No idea what the fastest way is to complete the authentication step; I’ve been rescanning all channels which is less than ideal. Obviously if I’m trying to record anything it is going to be hit or miss as to if I’m within my 24 hour window or not. I’m giving it a few more days, but I’m beginning to think I’m going to end up cancelling my subscription, which is too bad because it is a good price point.
Yes, thank you to everyone for contributing. I am having the same authentication problems, but updated to newest version and was able to authenticate at the server last night. This morning, trying to watch any TVE channel on AppleTV, iPad or iPhone sends a t-mobile code to my phone - with no where to input. So, only place to watch is on a monitor hooked up to server? Fingers crossed for a resolution.
I had to re-authenticate this morning to get non-local channels to come through via the T-Mobile source. I was assured by T-Mobile that this would NOT be necessary. So I have reported the issue (yet again) to TVisionTech Suport and hope to hear back NLT Wednesday of this week.
Meanwhile I have paused all scheduled recordings for non-local T-Mobile sourced channels so that I don’t get those pesky text messages that can’t be authenticated.
If you re-authenticate Channels DVR at the source level, you should get a text message on your phone with a 6-digit code that can be entered during the source level authentication process. Just make sure you are on the latest beta release of ChannelsDVR.
If it doesn’t authenticate, you might need to call T-Mobile and/or send diagnostics to Channels support.
Hope this helps and gets resolved soon. Hanging in with T-Mobile for now primarily due to price point.
I did not have to re-authenticate Channels DVR for channels such as MSNBC and CNN, etc. this morning. I don't really know what changed but will keep monitoring this to see if I have to re-authenticate in the future. If I do, I'll post again.
Next step is to slowly unpause series recordings for one or two of my authenticated T-Mobile channels to see how authentication behaves.
Meanwhile, perhaps authentication is now fixed for the T-Mobile source. Fingers crossed.
1 Like
Well I tried to load TBS this morning and would not work until I re-authenticated, and I had done this last night.
Another Tvision customer here. Today I added T-mobile Tv into channels dvr. Everything went smooth until it started verifying the Discovery suite of channels. The 2fa popped on Own, Discovery, Food, Travel and ID and the window to enter the 2fa code popped up. The channels that requested the 2fa got successfully authorized.. After testing some, went to edit the lineup and manually add the discovery network channels that failed authentication. Tried Animal Planet. Got a 2fa text on my phone but no window popped up to enter that code. Same issue with the remaining 10 channels from discovery that did not authorized the first time around. So in my case seems to be the Discovery networks that are messing up.
The only way I’ve been able to get the authentication code window to appear is to rescan all the channels. If you have issues with the channels authorizing the first time through, rescanning individual channels immediately after the initial scan will not require a new authentication. I’ve had to reauthenticate every day, and will likely be looking for another provider as the solution thus far is unreliable (no fault of the developers, the authentication method via t-mobile is lacking). One thing to note.... I’ve logged into Disney live streams through the website on my laptop via T-Mobile via chrome, and the authentication seems to carry over at least one day after an initial 2FA. Not sure what is different between how channels is authenticating through T-Mobile and my browser does, but I thought I would bring this up (it won’t be 24 hrs on my laptop until later this evening, but I was able to view multiple streams across multiple websites without needed to authenticate both yesterday and today).
For the 3rd day in a row, I have not had to re-authenticate any of my TVision Live channels. I have not tried to unpause any of my recordings yet but will try that soon. I don't really fully understand why I am not having to re-authenticate while others seem to experience this still. Perhaps it has something to do with making T-Mobile your sole TV Provider on all your devices. One other thing I did which may or may not be related, is I individually authenticated my NBC, CNN apps with T-Mobile provider for all my devices (iPhone, iPad, AppleTV) the other day and have not had to re-authenticate these apps or my T-Mobile source on channels since. Coincidental? I don't know, But perhaps worth a try if you feel like trying it.
If you need to enter the code, try clicking Add Source > TV Everywhere and I think it will have a place to enter the 2FA.
This is not the case for everyone. I am not sure why but I do not receive the pop-up to enter the code. It either spins indefinitely until it times out and goes idle or I receive the T-mobile 2fa screen stating that authentication has failed. Can you please look into why I am not receiving pop up to enter my code.
I've been following this discussion for a couple of weeks now. I enabled TOTP ("Google Authenticator" codes) on my account. Now, on the latest beta (2021.03.16.1916), I received a prompt to enter the 2FA code… but the page was on the selection screen to choose which phone number to send the code to. I have three phone numbers registered for code receipts, so I need to choose one when logging in.
When I log in, the first prompt asks if I want to get a text, enter a TOTP code, or receive an email (SMS is the default). Then, if I select text, I have to choose to which number (three choices) I want to send the SMS. Only after both of these choices do I receive a text message.
Is there any way to force my T-Mobile account to use TOTP as the default method? Alternatively, is there a plan to make the Chromium browser window interactive for events like this?
Please submit diagnostics and email support.