I'm running Channels DVR from a Synology package which provides the headless chrome.
Anyway, not sure how updating chrome will do what the discussion was about.
I understand. I do the same with a QNAP NAS. Often, TVE authentication fails when the chrome version gets out of date. Update chrome on your Synology. I had a similar problem a few months ago and it resolved when I updated chrome on my QNAP NAS.
There is no chrome package for my Synology NAS.
The headless chrome that Channels DVR uses is built-in.
[TVE] action=version product=Chrome/97.0.4692.56 jsVersion=9.7.106.18 protocol=1.3 revision=@04da6c66398ca50e603cc236a07dc7dfd3bbc750
The issue is with Xfinity. I was asking if they ever implemented this
teach the dvr to click "ask me later"
Glad you got it resolved.
Just an FYI. On synology if Channels DVR did have an update for Chrome which is a manual process. It will be on the troubleshooting page in red to click and update it.
1 Like
Like this?
Found a real screenshot of what it looks like 
Thanks for the fix!
1 Like
Probably an fyi. I started to get the following errors in the logs last night for discovery channels recordings we watch. action=science_stream error={[{access.denied.missingpackage 403}] {{[]}}}
I updated the password and rescanned did the trick to fix it will send over logs if helps.
Logs have been submitted as 08c047c9-87fb-48b7-b64e-680b4c049b22
Has anyone on here been able to successfully sign in to a Xfinity Campus account on Channels? This account works for the EPlus container but that allows for web sign in.
I highly doubt it. With the way xfinity has a separate link for campus logins I think the devs would have to write new code specifically for the additional steps required for drilling down to the correct university.
I figured. Thanks though!
Got that error today on 4 Discovery network channels while doing a rescan of all TVE channels.
I was able to manually rescan those individual channels successfully.
1 Like
Hey everyone, long time channels (non dvr) user. I recently dropped fubo in favor of the Xfinity internet+tv package as it was significantly cheaper (and includes the Turner networks). I haven't hooked up my HD Homerun Prime with cable card yet, but was very impressed to see how many channels worked flawlessly using TVE. The big outlier for me is FOX (In Oregon), everything else seems to be working as expected.
Does anyone have any tips for combining TVE with a CableCard source?
Most people use the prime as the main source and tve as the backup if they run out of tuners. I would suggest putting the prime at the top of source priority and favoriting prime channels in the dvr web ui so it will try to use them first for recordings . Tve is fairly reliable but the prime is more reliable.
2 Likes
Discovery family Channels not tuning or scanning ...
2023/03/20 12:49:47.678488 [TVE] Channel scan 75/217 DISCOVERY failed: POST: https://us1-prod-direct.sciencechannel.com/playback/v3/channelPlaybackInfo: 400 Bad Request: {
"errors" : [ {
"status" : "400",
"code" : "invalid.token",
"id" : "6xv4n7lTxL",
"detail" : "Token invalid"
} ]
}
2023/03/20 12:49:47.779362 [TVE] Channel scan 76/217 FOOD failed: POST: https://us1-prod-direct.sciencechannel.com/playback/v3/channelPlaybackInfo: 400 Bad Request: {
"errors" : [ {
"status" : "400",
"code" : "invalid.token",
"id" : "55fHCvTB0j",
"detail" : "Token invalid"
} ]
}
2023/03/20 12:49:47.876756 [TVE] Channel scan 77/217 ANIMAL-PLANET failed: POST: https://us1-prod-direct.sciencechannel.com/playback/v3/channelPlaybackInfo: 400 Bad Request: {
"errors" : [ {
"status" : "400",
"code" : "invalid.token",
"id" : "pNGLAot750",
"detail" : "Token invalid"
} ]
}
2023/03/20 12:49:47.990861 [TVE] Channel scan 78/217 HGTV failed: POST: https://us1-prod-direct.sciencechannel.com/playback/v3/channelPlaybackInfo: 400 Bad Request: {
"errors" : [ {
"status" : "400",
"code" : "invalid.token",
"id" : "3XmtFYVAWK",
"detail" : "Token invalid"
} ]
}
2023/03/20 12:49:48.094109 [TVE] Channel scan 79/217 TLC failed: POST: https://us1-prod-direct.sciencechannel.com/playback/v3/channelPlaybackInfo: 400 Bad Request: {
"errors" : [ {
"status" : "400",
"code" : "invalid.token",
"id" : "qHg1nAvs7i",
"detail" : "Token invalid"
} ]
}
2023/03/20 12:49:48.190840 [TVE] Channel scan 80/217 TRAVEL failed: POST: https://us1-prod-direct.sciencechannel.com/playback/v3/channelPlaybackInfo: 400 Bad Request: {
"errors" : [ {
"status" : "400",
"code" : "invalid.token",
"id" : "YG6psAvQYT",
"detail" : "Token invalid"
} ]
}
2023/03/20 12:49:48.288136 [TVE] Channel scan 81/217 INVESTIGATION-DISCOVERY failed: POST: https://us1-prod-direct.sciencechannel.com/playback/v3/channelPlaybackInfo: 400 Bad Request: {
"errors" : [ {
"status" : "400",
"code" : "invalid.token",
"id" : "jmRu4gbyiL",
"detail" : "Token invalid"
} ]
}
2023/03/20 12:49:48.391564 [TVE] Channel scan 82/217 DIY failed: POST: https://us1-prod-direct.sciencechannel.com/playback/v3/channelPlaybackInfo: 400 Bad Request: {
"errors" : [ {
"status" : "400",
"code" : "invalid.token",
"id" : "D9hLpQoFid",
"detail" : "Token invalid"
} ]
}
2023/03/20 12:49:48.486756 [TVE] Channel scan 83/217 COOKING-CHANNEL failed: POST: https://us1-prod-direct.sciencechannel.com/playback/v3/channelPlaybackInfo: 400 Bad Request: {
"errors" : [ {
"status" : "400",
"code" : "invalid.token",
"id" : "QPY4i0fTuL",
"detail" : "Token invalid"
} ]
}
2023/03/20 12:49:48.581468 [TVE] Channel scan 84/217 SCIENCE failed: POST: https://us1-prod-direct.sciencechannel.com/playback/v3/channelPlaybackInfo: 400 Bad Request: {
"errors" : [ {
"status" : "400",
"code" : "invalid.token",
"id" : "t3xqMjuuYI",
"detail" : "Token invalid"
} ]
}
2023/03/20 12:49:48.679988 [TVE] Channel scan 85/217 AHC failed: POST: https://us1-prod-direct.sciencechannel.com/playback/v3/channelPlaybackInfo: 400 Bad Request: {
"errors" : [ {
"status" : "400",
"code" : "invalid.token",
"id" : "uOZBvvsx8o",
"detail" : "Token invalid"
} ]
}
2023/03/20 12:49:48.789814 [TVE] Channel scan 86/217 DESTINATION-AMERICA failed: POST: https://us1-prod-direct.sciencechannel.com/playback/v3/channelPlaybackInfo: 400 Bad Request: {
"errors" : [ {
"status" : "400",
"code" : "invalid.token",
"id" : "ZT6FYaCDdy",
"detail" : "Token invalid"
} ]
}
Last time I saw that error was 2 months ago (knock on wood) on Magnolia channel
All my other channels worked logged on to Discovery website worked but it did have an odd screen after authorizing and showing the channels I have then it disappears after a few seconds..
This is still happening only on Discovery Family of channels ....
Logs have been submitted as 94c5d9b7-84d2-4b84-a855-30deadd7a596
2 Likes
For me, almost every time Channels failed to re-auth a Discovery Channel when its token had expired (expires every 7-8 days) was when it was trying to record the channel. I was then able to get the channel re-authed by playing the channel Live in the web UI player.
If you're still periodically forcing a rescan of all channels, that wouldn't help.
Appears there's a difference in the auth flows for rescanning, recording and trying to play Live.
1 Like