Nothing below 6101 Channel will tune in - Spectrum

[Suds]

I can’t tell you how many times I’ve referred to your list of TVE tips. Just in case no one has thanked you on these forums, thanks.

[chDVRuser]

Thanks @Suds
Hopefully it has helped some users. It started as a text document I made after seeing common causes for TVE issues. Most of the info in it was spread around the forum, so I decided to post it, making it easier to point to one reference.

[scarng]

keep hoping there will be a fix soon. I able to watch streaming from Chrome form their site, but no love from ChannelDVR (TV Everywhere). Keep checking daily.

[chDVRuser]

What server device and OS is your Channels DVR installed on?

[scarng]

QNAP T2-253D Firmware QTS 5.0.1.2425 Memory 8GB

[chDVRuser]

Do you know what version of headless chrome is being used by Channels DVR on it?
My guess is v97. It shows in the DVR log whenever Channels DVR has to authenticate with a network.

Example from a Docker Container install below using v109

2023/08/07 20:25:43.366621 [TVE] action=version product=Chrome/109.0.5414.74 jsVersion=10.9.194.9 protocol=1.3 revision=@e7c5703604daa9cc128ccf5a5d3e993513758913

If it is running v97, my guess is that's the problem. I quit running in a Synology package and migrated to a docker container to get the newer version chrome.

Magnolia recording failed no login form found

Hopefully the last post I make in this topic. Since I can't update headless-chrome past v97 on my Synology Package installs, I've migrated them to TVE docker containers using the same record path and port after stopping the Synology Packages. Since the new :tve docker container uses chrome v109, I'm hoping this solves my problem. I should know next time Channels DVR needs to re-auth Magnolia, which should be Jan. 25 and Jan 29 for my two servers using TVE sources.

Magnolia recording failed no login form found

Just an update that since moving my TVE servers to docker containers using chrome v109, no issues.

[scarng]

No, I have no idea. QPKG (Channels DVR Server 1.1.0) is install on the QNAP TS-253D and we use Fire TV to watch Channel DVR.

OS
QNAP TS-253D
Linux
(kernel: 5.10.60-qnap)
CPU
4 cores / Intel(R) Celeron(R) J4125 CPU @ 2.00GHz
load averages: 2.78 1.95 1.61
RAM
3.68 GB
49.6% free

[scarng]

I found the header. product=Chrome/97.0.4692.56

2023/08/14 06:51:02.568381 [HTTP] | 200 | 888.065952ms | 172.16.0.41 | GET "/tmsimg/assets/s56905_ll_h15_ad.png"
2023/08/14 06:51:02.827406 [TVE] action=version product=Chrome/97.0.4692.56 jsVersion=9.7.106.18 protocol=1.3 revision=@04da6c66398ca50e603cc236a07dc7dfd3bbc750
2023/08/14 06:51:02.828350 [TVE] action=navigate url=https://auth.sciencechannel.com/login-affiliates?returnUrl=https://www.sciencechannel.com/live-now&hostUrl=us1-prod-direct.sciencechannel.com
2023/08/14 06:51:02.830152 [TVE] action=request type=Document method=GET url=https://auth.sciencechannel.com/login-affiliates
2023/08/14 06:51:02.830175 [TVE] action=auth_domain domain=auth.sciencechannel.com
2023/08/14 06:51:02.830182 [TVE] action=scienceauth reason=login
2023/08/14 06:51:02.862138 [HTTP] | 200 | 898.719µs | 172.16.0.30 | GET "/devices/TVE-Spectrum/status/0-38/debug"
2023/08/14 06:51:02.935032 [HTTP] | 200 | 57.854µs | 172.16.0.41 | GET "/updater"
2023/08/14 06:51:03.134572 [TVE] action=wait_for_page

[speedingcheetah]

current version of chrome is 115.0.5790.171

[chDVRuser]

Yes, but like the Synology package it's something the devs need to update

Cannot authenticate Xfinity anymore

The only way to get it updated is to have the devs update it. It's included in the package/container and we can't update it ourselves. Not like Windows and some other installs that use your existing Chrome.

Cannot authenticate Xfinity anymore

Yes, that can be done on both the syno pkg and docker, but it doesn't update any further than v97 (syno) and v109 (docker).

Or he can migrate the install to a Docker Container which works and is currently maxed out at headless-chrome v109

[speedingcheetah]

Why is that? Cant u update it manualy somehow? Or are those images read only? Arnt they linux based? Those have a cli you can use to install things.

[chDVRuser]

Certain packages and the docker container images use the built-in headless chrome which the devs have to update (I think the RPi was the same). I have never seen a comprehensive list of what installs use Channels built-in vs. what installs rely on the native OS having chrome available for use by Channels, I just know it's a fact. It's not even mentioned if you look at the install instructions except for Linux / FreeBSD

[racameron]

@chDVRuser

I have never seen a comprehensive list of what installs use Channels built-in vs. what installs rely on the native OS having chrome available for use by Channels

It's simple: if you are using the containers (Docker/Podman/etc.), then the Chrome is as provided by Fancy Bits/Channels. (That's the whole point of a container: it is wholly contained and separate from your host OS; the only thing it knows about your host system are the limited directories you give it access to.) If you are installing the DVR directly onto your system—bare metal—then you are expected to provide Chrome/Chromium.

(The installation on NAS is more closely aligned with a container installation; mostly because users don't really have access to install additional arbitrary software in the NAS, as well as the NAS treating "applications" essentially as containers, but with slightly more privileges.)

[chDVRuser]

You should do this again since you're now running the latest pre-release version (make sure you update to the latest before submitting them)

Nothing below 6101 Channel will tune in

Please go to Support -> Troubleshooting -> Submit Diagnostic Logs from the web interface of the DVR and let us know when it's been submitted so we can have a better idea of what was going on.

[chDVRuser]

Makes sense. I realize their documentation needs updated all over the place, not just install instructions.

[racameron]

@chDVRuser

I realize their documentation needs updated all over the place, not just install instructions.

It's not really about the instructions being vague, it's that people are trying to do things without understanding what they are doing. (It seems lately that 1/3 of the forum posts are about containers and playlists, and the back-and-forth that shouldn't happen if people understood the technologies before trying to use them for themselves and instead are relying upon out-dated copypasta.)

[chDVRuser]

@racameron

people are trying to do things without understanding what they are doing

I understand what you're saying, and I agree 100% about those that don't want to research/learn and just want to copy/paste things.

But you can't expect a new (or not new) Channels DVR user to know they need to have Chrome installed on their Windows PC to use a TVE source when they try adding one to Channels DVR. Why is it only mentioned in the Linux / FreeBSD install instructions (you'd think those users are more advanced and should just know that because they understand how Channels DVR TVE works after reading the docs ;-). And that a NAS user installing per instructions doesn't realize the built-in chrome (they didn't even know was there) is outdated causing an auth issue.

[racameron]

@chDVRuser

But you can't expect a new (or not new) Channels DVR user to know they need to have Chrome installed on their Windows PC to use a TVE source when they try adding one to Channels DVR.

You're right; the official documentation should include wording that Chrome/Chromium is needed for TVE support.

@chDVRuser

And that a NAS user installing per instructions doesn't realize the built-in chrome (they didn't even know was there) is outdated causing an auth issue.

Updates should not only include newer versions of FFmpeg, but also all bundled applications (Chromium and Comskip included), regardless of platform.

Unfortunately, the exhaustion of knowledgeable users dealing with needless questions from those "punching above their weight class" is making the usefulness of the forum less than it could be.

[speedingcheetah]

Its not a useless or annoying post to say, you need to update your Chrome in order to use TVE. The Troubleshooting pages even say to update Chrome, or that it is out of date.
The TVE Troubleshooting steps say to update Chrome.

What is not clear in the documentations, is that users of Synology, and Docker, are locked down to that ecosystem and its limitations. Most end users that buy a Synology NAS, do not know the complex inner workings and design of how OS and ecosystem works, compared to others, or a standard Linux distro. They just use it at face GUI level. AND, Channels DVR website says it will work with their device and expect it to.

Docker, can get more complex, but Docker for desktop software is pretty easy, and has been, at least for me, few clicks, or couple lines of code to install and run a container. But what i use, i can edit and change things in it, but that single container and use case, is the expanse of my use of the ecosystem.

If the devs have to update these containers/images/packages, then ok. Fine. But, until then, seems Synology users are SOL. I guess that is a big negative to using those platforms.
I would think it would be quite trivial a thing for them to make the update, and push it out....but maybe they have not had the time, or have some other issues.

[chDVRuser]

@speedingcheetah

maybe they have not had the time, or have some other issues.

or not enough users are reporting the issues.

I'm an exception, as I try to find workarounds if the devs are silent. In this case by switching from the Synology Package to the docker container. I've switched between them before due to what I believe is the included chrome being too old. I know other users have just migrated to another platform or another Provider.