Proper CableCARD/HDHomeRun Prime support

Robert Cameron · 2018-05-14T19:11:36+00:00

CableCARD Network support This branch/patchset adds a CableCARD network type to Tvheadend. When adding muxes, the "Channel" field is used for the channel nu...

Robert Cameron

Yusef Neblett wrote:
> Thanks Robert for your time,
>
> Just to be clear in what commands to use to run the srcipt. Should I create the script file xxxx.sh or xxx.py? and I guess the file path used to run the script doesnt matter correct?
>
> I have basic linux knowledge on scripts.
>
> Appreciatte your time
>

> YN

Name it whatever you like, it doesn't matter. Just make sure it's marked as executable. If you're going to give it an extension,

.sh

is most appropriate. The shebang in the first line of the script (@#!/bin/sh@) tells your command processor to use a POSIX shell to execute the script.

Also note, you need both

curl

and

jq

for my script to work.

curl

is part of most every distribution, but

jq

usually needs to be installed separately.

Yusef Neblett

Hi Robert,

jq and curl are installed. I have created a script file with .sh containing your script as your adviced:

#!/bin/sh
TVHEADEND="TVHEADENDMIGRATIONSTART774403362b034bd9a940fa4c0c3a51a1TVHEADENDMIGRATIONEND #URL used to access Tvheadend WebUI NETWORK=hdhomerun-CC #Name of CableCARD network to add muxes to
DEVICE=1323B3C0 #DeviceID of HDHomeRun device UUID=$(
curl -sS "${_TVHEADEND}/api/idnode/load" \
-d "class=dvb_network_cablecard" -d "enum=1" |
jq ".entries[] | select(.val == \"${_NETWORK}\") | .key" |

tr -d \")

LINEUP=$( curl -sS "TVHEADENDMIGRATIONSTARTeb5c5069b11346ddafd1a1db219620c4TVHEADENDMIGRATIONEND | jq ".[] | select(.DeviceID == \"${DEVICE}\") | .LineupURL" |

tr -d \")

forCHANNEL in $( curl -sS "${LINEUP}" |
jq '.[].GuideNumber | tonumber')
do
curl -sS "${_TVHEADEND}/api/mpegts/network/mux_create" \
-d "uuid=${_UUID}" \
--data-urlencode "conf={\"epg\":0, \"vchan\":${_CHANNEL}}" > /dev/null

done

I am using @localhost:9981 because I am running the script in the tvhd server, I tried changing to the server Ip as well.

I am running the script with:

./myscript.sh

But I keep getting this error: parse error: Invalid numeric literal at line 1, column 10

I checked the script and look ok to me but I cant figure out the root cause of the issue.

Thanks for your time again.

Robert Cameron

Sounds like a problem logging in to your Tvheadend server. However, wihout details I can't be specific.

Try running the commands manually from the command line; slowly adding the piped commands to each command and substituting the literal text for the variables.

Unfortunately, beyond that I'm not sure what additional help I can offer.

Yusef Neblett

Hi Robert,

Thanks for your help, I been trying to figur out the reason for the script not working to me. and I have a question:

I run the cablecard.sh script:

root@raspberrypi:/media/tvhd# bash -x cablecard.sh
+TVHEADEND=TVHEADENDMIGRATIONSTART92e05a9ebd03449da7ae12680a520a14TVHEADENDMIGRATIONEND + NETWORK=CCPrime
+DEVICE=1323B3C0 ++ curl -sS TVHEADENDMIGRATIONSTART213ee2dcc6d14278beb81bf917d371ebTVHEADENDMIGRATIONEND -d class=dvbnetwork_cablecard -d 'enum = 1'
++ tr -d '"'
++ jq '.entries[] | select(.val == "CCPrime") | .key'
parse error: Invalid numeric literal at line 1, column 10
+UUID= ++ curl -sS TVHEADENDMIGRATIONSTART7892acc3ecbe487b953bd16d81999a03TVHEADENDMIGRATIONEND ++ jq '.[] | select(.DeviceID == "1323B3C0") | .LineupURL' ++ tr -d '"' + LINEUP=http://192.168.1.100:80/lineup.json ++ curl -sS http://192.168.1.100:80/lineup.json ++ jq '.[].GuideNumber | tonumber'
+ forCHANNEL in $( curl -sS "${LINEUP}" |
jq '.[].GuideNumber | tonumber')
+ curl -sS http://admin:mypass@127.0.0.1:9981/api/mpegts/network/mux_create -d uuid= --data-urlencode 'conf={"epg":0, "vchan":11}'
+ forCHANNEL in $( curl -sS "${LINEUP}" |

jq '.[].GuideNumber | tonumber')

What bring my attention is that the output line: curl -sS http://admin:Monsrak24@127.0.0.1:9981/api/mpegts/network/mux_create -d uuid= --data-urlencode 'conf={"epg":0, "vchan":11}'

shows empty after the uuid= . I am not sure what is an uuid (perhaps like a file checksum) but I guess I need that value when running the script.

when I run the http://api.hdhomerun.com/discover I get this: (no uuid value)
[
{
"DeviceID": "1323B3C0",
"LocalIP": "192.168.1.100",
"ConditionalAccess": 1,
"BaseURL": "http://192.168.1.100:80", "DiscoverURL": "http://192.168.1.100:80/discover.json", "LineupURL": "http://192.168.1.100:80/lineup.json" }

]

My setup:
Tvheadend 4.3-1273~g610c6fa74

running on a Rpi 3 with raspbian

please let me know if you see what I am doing wrong or what I am missing.

Thanks

Robert Cameron

Yusef, I'm going to try to walk you through this, but I can't guarantee everything will come through as intended.

Yusef Neblett wrote:
> I run the cablecard.sh script:
>
> root@raspberrypi:/media/tvhd# bash -x cablecard.sh
> +TVHEADEND=TVHEADENDMIGRATIONSTART148b50d6b4674200b4af17af7c15d711TVHEADENDMIGRATIONEND > + NETWORK=CCPrime
> +DEVICE=1323B3C0 > ++ curl -sS TVHEADENDMIGRATIONSTART6c10bf857ed34b9b8ea54ab8e729e7c9TVHEADENDMIGRATIONEND -d class=dvbnetwork_cablecard -d 'enum = 1'
> ++ tr -d '"'
> ++ jq '.entries[] | select(.val == "CCPrime") | .key'
> parse error: Invalid numeric literal at line 1, column 10
> +UUID= > ++ curl -sS TVHEADENDMIGRATIONSTART57a572eb8eb9497ba266ae296f7863a7TVHEADENDMIGRATIONEND > ++ jq '.[] | select(.DeviceID == "1323B3C0") | .LineupURL' > ++ tr -d '"' > + LINEUP=http://192.168.1.100:80/lineup.json > ++ curl -sS http://192.168.1.100:80/lineup.json > ++ jq '.[].GuideNumber | tonumber'
> + forCHANNEL in $( > curl -sS "${LINEUP}" |
> jq '.[].GuideNumber | tonumber')
> + curl -sS http://admin:mypass@127.0.0.1:9981/api/mpegts/network/mux_create -d uuid= --data-urlencode 'conf={"epg":0, "vchan":11}'
> + forCHANNEL in $( > curl -sS "${LINEUP}" |

> jq '.[].GuideNumber | tonumber')

A couple things to begin with:
# I'm not sure if it is merely a formatting issue with you cutting-and-pasting your terminal's output, or some other error you made when you saved the script, but I'm not sure I fully understand what you've posted. The series of

and

++

make no sense, and there are missing elements that render what you have posted unworkable.
# When you run the script, if you have saved it as a file called

cablecard.sh@, all that you need to do to execute it is call the script; if you are executing the script from the same directory in which it is saved, you would merely type @./cablecard.sh

. Telling

bash

to execute the script may cause issues, as this is not a

bash

script, but rather POSIX shell.

With that said,

curl

can sometimes have problems escaping input, which is why in my example script the

_TVHEADEND

variable is double-quoted when it is defined. Also, it is not clear if the output you are sharing is the result of running the script as a script, or whether from your attempts at troubleshooting by manually entering the commands. If you are troubleshooting (and manually entering the commands), either set the variables in your shell or just substitute the actual text.

I'm going to walk through the script step-by-step.

#!/bin/sh _TVHEADEND="http://localhost:9981" # URL used to access Tvheadend WebUI _NETWORK=Cable # Name of CableCARD network to add muxes to _DEVICE=FFFFFFFF # DeviceID of HDHomeRun device

If you were running this as a script, you would modify these variables to suit your needs. In my case, I do not need a username or password for admin access to my Tvheadend server based upon the access controls that I have established. To differentiate my CableCARD network from any others, I've named it after my cable provider. Also, I have several HDHR Primes, but I only need one with a channel lineup. So, here are the variables I use for my script:


_TVHEADEND="http://10.0.0.21:9981"
_NETWORK=Charter
_DEVICE=1321F1A1

Now, if instead of running this as a script, but you were going to manually run the commands to make sure everything works, you could do so by setting the variables in your terminal with commands such as:

export _TVHEADEND="http://10.0.0.21:9981"@, @export _NETWORK=Charter@, and @export _DEVICE=1321F1A1@.

The next part of the script sets a variable called @_UUID

to the UUID that Tvheadend assigned to your CableCARD network when you created it.


_UUID=$(
  curl -sS "${_TVHEADEND}/api/idnode/load"                 \
    -d "class=dvb_network_cablecard" -d "enum=1"           |
  jq ".entries[] | select(.val == \"${_NETWORK}\") | .key" |
  tr -d \")

This is actually doing several things:
# Run the command

curl -sS "${_TVHEADEND}/api/idnode/load" -d "class=dvb_network_cablecard" -d "enum=1"

(This command asks the Tvheadend server for the names and UUIDs of all of the CableCARD networks)
# Take the ouput from the previous

curl

command, and use it as the input into the command

jq ".entries[] | select(.val == \"${_NETWORK}\") | .key"

(This command sorts through the name/UUID combinations, and returns the UUID that matches the network name you provided in the

_NETWORK

variable)
# Take the output from the previous

jq

command, and use it as the input into the command

tr -d \"

(This command strips all of the

(double-quotes) from string it is given)
# Finally, take the output from the previous

tr

command, and save it in the

_UUID

variable.

To guide you along, I'm going to show you the result of these commands on my system. Since this is the output of manually entering the commands, I'm going to be manually setting the variables. This is most evident when

_UUID

gets set, but normally the script would completely handle setting that variable.


[robert@loki ~]$ echo ${_TVHEADEND}

[robert@loki ~]$ echo ${_NETWORK}

[robert@loki ~]$ echo ${_DEVICE}

[robert@loki ~]$ export _TVHEADEND="http://10.0.0.21:9981"
[robert@loki ~]$ export _NETWORK=Charter
[robert@loki ~]$ export _DEVICE=1321F1A1
[robert@loki ~]$ echo ${_TVHEADEND}
http://10.0.0.21:9981
[robert@loki ~]$ echo ${_NETWORK}
Charter
[robert@loki ~]$ echo ${_DEVICE}
1321F1A1
[robert@loki ~]$ curl -sS "${_TVHEADEND}/api/idnode/load" -d "class=dvb_network_cablecard" -d "enum=1"
{"entries":[{"key":"bdaa87b15019374a2f0360a61c5c1438","val":"Charter"}]}
[robert@loki ~]$ curl -sS "${_TVHEADEND}/api/idnode/load" -d "class=dvb_network_cablecard" -d "enum=1" | jq ".entries[] | select(.val == \"${_NETWORK}\") | .key"
"bdaa87b15019374a2f0360a61c5c1438"
[robert@loki ~]$ curl -sS "${_TVHEADEND}/api/idnode/load" -d "class=dvb_network_cablecard" -d "enum=1" | jq ".entries[] | select(.val == \"${_NETWORK}\") | .key" | tr -d \"
bdaa87b15019374a2f0360a61c5c1438
[robert@loki ~]$ echo ${_UUID}

[robert@loki ~]$ export _UUID=$(curl -sS "${_TVHEADEND}/api/idnode/load" -d "class=dvb_network_cablecard" -d "enum=1" | jq ".entries[] | select(.val == \"${_NETWORK}\") | .key" | tr -d \")
[robert@loki ~]$ echo ${_UUID}
bdaa87b15019374a2f0360a61c5c1438

The next part of the script is where it gets the address/URL for the scanned channel lineup of your HDHR tuner.


_LINEUP=$(
  curl -sS "http://api.hdhomerun.com/discover"                |
  jq ".[] | select(.DeviceID == \"${_DEVICE}\") | .LineupURL" |
  tr -d \")

Again, like the previous snippet of the script that set the

_UUID

variable, this bit does several things to set the

_LINEUP

variable:
# Run the command

curl -sS "http://api.hdhomerun.com/discover"

(This command contacts Silicon Dust's servers and gets a listing of all of the HDHomeRun tuners and servers that are running on your local network)
# Take the output from the previous

curl

command and use it as the input to the command

jq ".[] | select(.DeviceID == \"${_DEVICE}\") | .LineupURL"

(This command returns the

LineupURL

that matches the DeviceID of the HDHR tuner that you set in the

_DEVICE

variable)
# Take the output from the previous

jq

command, and use it as input to the command

tr -d \"

(Again, this strips the

from the string)
# Finally, take the final output from the

tr

command, and store it in the

_LINEUP variable


[robert@loki ~]$ curl -sS "http://api.hdhomerun.com/discover"
[
    {
        "DeviceID": "131F3E8D",
        "LocalIP": "10.0.0.49",
        "ConditionalAccess": 1,
        "TuningResolver": 1,
        "BaseURL": "http://10.0.0.49:80",
        "DiscoverURL": "http://10.0.0.49:80/discover.json",
        "LineupURL": "http://10.0.0.49:80/lineup.json"
    },
    {
        "DeviceID": "1321DC95",
        "LocalIP": "10.0.0.50",
        "ConditionalAccess": 1,
        "TuningResolver": 1,
        "BaseURL": "http://10.0.0.50:80",
        "DiscoverURL": "http://10.0.0.50:80/discover.json",
        "LineupURL": "http://10.0.0.50:80/lineup.json"
    },
    {
        "DeviceID": "1321F1A1",
        "LocalIP": "10.0.0.51",
        "ConditionalAccess": 1,
        "TuningResolver": 1,
        "BaseURL": "http://10.0.0.51:80",
        "DiscoverURL": "http://10.0.0.51:80/discover.json",
        "LineupURL": "http://10.0.0.51:80/lineup.json"
    }
]
[robert@loki ~]$ curl -sS "http://api.hdhomerun.com/discover" | jq ".[] | select(.DeviceID == \"${_DEVICE}\") | .LineupURL"
"http://10.0.0.51:80/lineup.json"
[robert@loki ~]$ curl -sS "http://api.hdhomerun.com/discover" | jq ".[] | select(.DeviceID == \"${_DEVICE}\") | .LineupURL" | tr -d \"
http://10.0.0.51:80/lineup.json
[robert@loki ~]$ echo ${_LINEUP}

[robert@loki ~]$ export _LINEUP=$(curl -sS "http://api.hdhomerun.com/discover" | jq ".[] | select(.DeviceID == \"${_DEVICE}\") | .LineupURL" | tr -d \")
[robert@loki ~]$ echo ${_LINEUP}
http://10.0.0.51:80/lineup.json


I think I'll stop there for the walk through, because those two chunks of the script set up the variables that are needed for the final @for

loop that actually creates the muxes. However, it seems as if you aren't getting to that point because the initial variables (most likely,

_UUID@) are being set.

> What bring my attention is that the output line: curl -sS http://admin:Monsrak24@127.0.0.1:9981/api/mpegts/network/mux_create -d uuid= --data-urlencode 'conf={"epg":0, "vchan":11}'
> shows empty after the uuid= . I am not sure what is an uuid (perhaps like a file checksum) but I guess I need that value when running the script.

Because you're not seeing anything after the @uuid=

in the

curl

command, it makes me believe that you haven't set the

_UUID

variable with the Tvheadend uuid of the CableCARD network.

> when I run the http://api.hdhomerun.com/discover I get this: (no uuid value)
> [
> {
> "DeviceID": "1323B3C0",
> "LocalIP": "192.168.1.100",
> "ConditionalAccess": 1,
> "BaseURL": "http://192.168.1.100:80", > "DiscoverURL": "http://192.168.1.100:80/discover.json", > "LineupURL": "http://192.168.1.100:80/lineup.json" > }

> ]

No, you wouldn't have a UUID value here. The UUID comes from Tvheadned, and this information is coming from Silicon Dust; they have no knowledge about your Tvheadend servers, only the HDHR tuners and servers on your network.

> My setup:
> Tvheadend 4.3-1273~g610c6fa74
> running on a Rpi 3 with raspbian
>
> please let me know if you see what I am doing wrong or what I am missing.
>

> Thanks

Your version shouldn't matter, nor should the hardware. The problem is most likely that you've got an error of some sort when you created your script.

(Also, in the future, if you are going to post scripts or terminal output, please post it in

pre

tags so it's easier to read/understand.)

Yusef Neblett

Hi Robert,

Thanks so so much for your help and explanation. I realize the issue was a loggin issue to the tvheadend server now with your help. Thanks so mush!!

When I was running the script line by line, I got an error when trying to call the tvheadend server:


root@raspberrypi:/media/tvhd# curl -sS "${_TVHEADEND}/api/idnode/load" -d "class=dvb_network_cablecard" -d "enum=1"
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>401 Unauthorized</TITLE>
</HEAD><BODY>
<H1>401 Unauthorized</H1>
<P STYLE="text-align: center; margin: 2em"><A HREF="/" STYLE="border: 1px solid; border-radius: 4px; padding: .6em">Default

So I created a new user that will not require password to loging and ran the script as you adviced: ./script.sh

Thanks for your time and work. I really appreciate it.

Yusef

Robert Cameron

Yusef Neblett wrote:
> Hi Robert,
>
> Thanks so so much for your help and explanation. I realize the issue was a loggin issue to the tvheadend server now with your help. Thanks so mush!!
>
> When I was running the script line by line, I got an error when trying to call the tvheadend server:
>
> [...]
>
> So I created a new user that will not require password to loging and ran the script as you adviced: ./script.sh
>
> Thanks for your time and work. I really appreciate it.
>

> Yusef

Glad you figured it out ... but I believe I mentioned that logging in to your Tvheadend server was most likely the cause of your error a couple of days ago ... Would have saved much time and frustration.

Benjamin Neblett

Robert

I have to congratulate you for this amazing work.

i compiled it to run in openwrt chaos calmer and it took me 3 weeks but at the end i was able to compile and run it in the firewall an ar71xx chip.

I run version 4.2.6 with the patch very well however i have one question.

when i Run the script to create the muxes it creates all muxes very well and scans all services but the name of the services are all "single Word" if I have 10 FOX Channels , FOX SPORTS, FOX FAMILY, FOX MOOVIES they all show with the name FOX and i cant identify which one is which.

i know the chanel numbers of my cable probider but is there any way to let tvheadend import the complete channel name instead of just the first word?

Robert Cameron

Benjamin Neblett wrote:
> Robert
> I have to congratulate you for this amazing work.
>
> i compiled it to run in openwrt chaos calmer and it took me 3 weeks but at the end i was able to compile and run it in the firewall an ar71xx chip.
> I run version 4.2.6 with the patch very well however i have one question.
>
> when i Run the script to create the muxes it creates all muxes very well and scans all services but the name of the services are all "single Word" if I have 10 FOX Channels , FOX SPORTS, FOX FAMILY, FOX MOOVIES they all show with the name FOX and i cant identify which one is which.

> i know the chanel numbers of my cable probider but is there any way to let tvheadend import the complete channel name instead of just the first word?

Unfortunately, those names are the ones from your CableCARD/provider mapping. They're read from the Prime itself as the callsign on the feed. Also, those service names come when the mux is scanned/service created, and not a part of the mux creation script. The mux creation script only creates a mux for a channel that has been successfully scanned by the HDHomeRun webui.

Perhaps another patchset will be an EPG source for HDHR tuners, or maybe dig into bouquets and how they might be created based upon the lineup.json or guide.json sources.

stefan fiala

Great work!, thanks.
I pulled the git-tip for 4.3 before seeing you mentioned patchsets.
Built it ran into the issue running the script to setup muxes
(line1 column10)

(created user *, as http://user:password@ ddint want to work).

I now have lots of muxes but no services, should they have been
created and if so is it because tvheadend's git is behind your patches?.

[What should I look for?].

I did see a lot of "tsid 0" messages in the log, but my last
experience with tvheadend+hdhomerun using an iptv setup did similar.
This setup looks to be a lot less hassle than configuring everything

using iptv.

I may be open to testing any upcoming changes, an EPG source would
be great as the schedulesdirect setup is a a bit of a hassle.

Saen Acro

stefan fiala wrote:
> (created user, as TVHEADENDMIGRATIONSTARTc4a65869517b4531a6499db75fa47269TVHEADENDMIGRATIONEND ddint want to work). set authentication to Both plain and digest* to work ;)

stefan fiala

I wandered around in the gui and briefly unnder .hts/ and didnt come across
any obvious authentication settings. Where exactly should I look?.

stefan fiala

Found it:-
Gui->configuration->view-level-advanced, scroll down thru settings.

Robert Cameron

The script to create muxes by no means was meant to be an official/bundled way to create muxes for CableCARD channels; rather it is merely a quick hacked-together script that worked for me and I thought others might benefit from it, too.

However, due to several different issues and changes, I have begun migrating my DVR from Tvheadend to Channels. That, combined with my move away from cable to OTA broadcasts, I doubt I will be putting much effort into maintaining this feature. All of the code is up, and support is present in master. I'll offer support where I can, but I can make no guarantees.

stefan fiala

Many thanks for the background.

So on tvheadend git master [version/sha/date] it all appeared to work for you, services and all?.

Would I have to hack further on the script to add services or is that

expected to work?. If hackery is needed any tips about tidbits of api that maybe useful?.

I only have a vague notion about how all this htsp stuff fits together, muxes,channels and services.
I could probably figure it out if pointed in the right general direction.

Robert Cameron

stefan fiala wrote:
> Many thanks for the background.
> So on tvheadend git master [version/sha/date] it all appeared to work for you, services and all?.
>
> Would I have to hack further on the script to add services or is that
> expected to work?. If hackery is needed any tips about tidbits of api that maybe useful?.
>
> I only have a vague notion about how all this htsp stuff fits together, muxes,channels and services.

> I could probably figure it out if pointed in the right general direction.

The CableCARD network type and using HDHomeRun Prime tuners has been in 4.3 for several months now.

Regarding creating muxes/services: The script is for creating muxes based upon the scanned/enabled channels on your Prime device. Services are only created after a mux is scanned, and the script has nothing to do with that. If you do not wish to use the script, you can still manually create your muxes; there is nothing that requires external scripts.

As far as additional hacks or API documentation: I feel that the script is pretty self-explanatory. For Tvheadend's HTTP/JSON API, I used the source to figure out which endpoints to use. (Take a look in the src/api directory: at the end of each api_*.c file is an

api_hook_t

array that includes all of the API endpoints. Look for the functions in the source, and use a little trial and error to get it going.)

Reggie Burnett

Robert

I'm seeing odd behavior that may or may not be related to the cablecard stuff. Very regularly when I try to tune a channel it just hangs. The TVH log says (for example) '2018-10-04 09:34:51.097 subscription: 0095: "192.168.1.102 [ reggie | Kodi Media Center ]" subscribing on channel "CNN HD", weight: 100, adapter: "HDHomeRun CableCARD Tuner #0 (192.168.1.148)", network: "CableCARD Network", mux: "1111", service: "CNNHD", profile="htsp", hostname="192.168.1.102", username="reggie", client="Kodi Media Center".

And it just sits there. If I tune a different channel it works and then go back to try and tune the one that just hung it will also work. This is very regular and is not a kodi problem as I recreated it with the thv client on IOS.

Just wondering if you are seeing anything similar?

Robert Cameron

Reggie Burnett wrote:
> Robert
>
> I'm seeing odd behavior that may or may not be related to the cablecard stuff. Very regularly when I try to tune a channel it just hangs. The TVH log says (for example) '2018-10-04 09:34:51.097 subscription: 0095: "192.168.1.102 [ reggie | Kodi Media Center ]" subscribing on channel "CNN HD", weight: 100, adapter: "HDHomeRun CableCARD Tuner #0 (192.168.1.148)", network: "CableCARD Network", mux: "1111", service: "CNNHD", profile="htsp", hostname="192.168.1.102", username="reggie", client="Kodi Media Center".
>
> And it just sits there. If I tune a different channel it works and then go back to try and tune the one that just hung it will also work. This is very regular and is not a kodi problem as I recreated it with the thv client on IOS.
>

> Just wondering if you are seeing anything similar?

If I had to guess (which is essentially the case), I'd say that your problem is most likely a tuning issue and hardware related. Are you running the most current firmware?

When having tuning issues in the past, sometimes the only way I found to fix it was to power off the tuner and the tuning adapter, plugging both back in, waiting for the TA to be in a ready state, and then re-running a channel scan. (While I am not currently using TVH for my DVR, I had to follow this procedure with my 3 Primes in order to get some channels to tune.)

Reggie Burnett

Robert Cameron wrote:
> Reggie Burnett wrote:
> > Robert
> >
> > I'm seeing odd behavior that may or may not be related to the cablecard stuff. Very regularly when I try to tune a channel it just hangs. The TVH log says (for example) '2018-10-04 09:34:51.097 subscription: 0095: "192.168.1.102 [ reggie | Kodi Media Center ]" subscribing on channel "CNN HD", weight: 100, adapter: "HDHomeRun CableCARD Tuner #0 (192.168.1.148)", network: "CableCARD Network", mux: "1111", service: "CNNHD", profile="htsp", hostname="192.168.1.102", username="reggie", client="Kodi Media Center".
> >
> > And it just sits there. If I tune a different channel it works and then go back to try and tune the one that just hung it will also work. This is very regular and is not a kodi problem as I recreated it with the thv client on IOS.
> >
> > Just wondering if you are seeing anything similar?
>
> If I had to guess (which is essentially the case), I'd say that your problem is most likely a tuning issue and hardware related. Are you running the most current firmware?
>

> When having tuning issues in the past, sometimes the only way I found to fix it was to power off the tuner and the tuning adapter, plugging both back in, waiting for the TA to be in a ready state, and then re-running a channel scan. (While I am not currently using TVH for my DVR, I had to follow this procedure with my 3 Primes in order to get some channels to tune.)

Appreciate the response. I take it you are not seeing anything like this? It's not a hardware issue because I tested the tuners with the SiliconDust HD app (I have the HD DVR installed as well but idle) and all the channels tune flawlessly. Havenever had one not tune correctly. I'm stumped. I'll keep updating the 4.3 docker image and testing to see if some other change happened in TVH that caused this. This is a relatively new development.

Reggie Burnett

BTW, what DVR did you go with?

« Previous Page Next Page »