OpenDCT: An open source digital cable tuner.

[CptKirk]

Yes, thanks.

I have verified that both services are enabled and started.

[CptKirk]

Added my opendct log and properties file.

From my http://192.168.99.51:9091/

OpenDCT 0.5.32
Loaded Capture Devices:

DCT-HDHomeRun HDFX-4K Tuner 10A26C08-0: Idle
DCT-HDHomeRun HDFX-4K Tuner 10A26C08-1: Idle
DCT-HDHomeRun HDFX-4K Tuner 10A26C08-2: Idle
DCT-HDHomeRun HDFX-4K Tuner 10A26C08-3: Idle
DCT-HDHomeRun Prime Tuner 1324B362-0: Idle
DCT-HDHomeRun Prime Tuner 1324B362-1: Idle
DCT-HDHomeRun Prime Tuner 1324B362-2: Idle

In the logs 192.168.99.51 is the sagetv server and opendct location.

13182976 is the old Prime tuner that died and has been disconnected from the network. The IP address that it used was 192.168.99.102.

1324B362 is the NEW Prime tuner and is connected to the network, found by opendct, but not found in Sagetv when trying to add a new source. IP address that it used is 192.168.99.55.

[Zogg]

Originally Posted by CptKirk

Added my opendct log and properties file.

From my http://192.168.99.51:9091/



In the logs 192.168.99.51 is the sagetv server and opendct location.

13182976 is the old Prime tuner that died and has been disconnected from the network. The IP address that it used was 192.168.99.102.

1324B362 is the NEW Prime tuner and is connected to the network, found by opendct, but not found in Sagetv when trying to add a new source. IP address that it used is 192.168.99.55.

You're on Windows, right? What is the BDA compatibility mode set to in HDHomeRun Setup? It should be SageTV or I think J River.

[hb4]

I'm no expert, but did you load a fresh copy of OpenDCT? Is the Prime the only thing using OpenDCT? it looks like there's lots of other tuners in the properties file.

[CptKirk]

Yes, Windows. BDA compatibility=SageTV.

Been using HDHomeRun Prime for years and years with no problems. Got a lightning strike and it died. Bought a new Prime which I'm trying to get working.


HDHomeRun HDFX-4K Tuner
HDHomeRun Prime Tuner

Those are the two HDHomeRun units installed.

I'm going to try and uninstall opendct, delete directories, etc to make it as clean as I can before reinstalling it.

[nyplayer]

Originally Posted by CptKirk

Yes, Windows. BDA compatibility=SageTV.

Been using HDHomeRun Prime for years and years with no problems. Got a lightning strike and it died. Bought a new Prime which I'm trying to get working.


HDHomeRun HDFX-4K Tuner
HDHomeRun Prime Tuner

Those are the two HDHomeRun units installed.

I'm going to try and uninstall opendct, delete directories, etc to make it as clean as I can before reinstalling it.

BDA drivers do not matter when using OPENDCT... You have to make sure when running the console that OPENDCT service is stopped also SageTV is stopped.... once you close the console then you can Start OpenDCT service.... fire up SageTV and setup your tuners. When setting up OPENDCT for first time you have to make sure OPENDCT service is started before staring SageTV.

[Tiki]

Have you gone through the built-in web page for your hdhr tuners and made sure everything looks good there? Card is properly paired to the hdhr and diagnostics look good? Channel scan complete?

[CptKirk]

Sorry for the long post. What I have done to try and get to as 'clean' a spot in trying to get Prime tuners into SageTV with OpenDCT.

Ran SageTVSetupx86_9.2.6.exe and did a Repair
Rebooted server

Uninstalled Java 8 32bit
Uninstalled HDHomerun software
Uninstalled Opendct
Rebooted server
Checked C:\Program Files, C:\Program Files (x86), C:\ProgramData for any folder of the uninstalled software and manually deleted them.
Rebooted server

Install jre-8u311-windows-i586.exe
Rebooted server

Install hdhomerun_windows_20211212.exe
Rebooted server

Run hdhomerun_setup
hdhomerun_setup finds my 7 tuners, 3 prime cc and 4 4k-flex ota
hdhomerun_setup DBA set to sagetv
hdhomerun_setup cc start channel scan
hdhomerun_setup channel scan completed, 500+ comcast channels found, clicked Apply
hdhomerun_setup clicked on a few of the channels, vlc opens and starts playing the channel
hdhomerun_setup for completeness went to the digital antenna tab and did a channel scan there as well, clicked Apply
Open the Prime web interface at http://192.168.99.55/, Card Authentication success, Card OOB Lock success, Card Validation success. All CC status looks ok. Clicked on Channel Lineup, click on Detect Channels and do a channel scan here as well.
Rebooted server

Install OpenDCT_0.5.32_x86.msi

Both SageTV service and SageTV OpenDCT service are set to manual startup type by me so that I can control when they are actually running. Both are set to Log On As to a local account with administrator privileges

Run OpenDCT as console
After finished checked the opendct.log file. There are 4 Java errors that happened in HDHomeRunControl and HDHomeRunDiscovery.
Log files attached
Rebooted server

From start menu did: OpenDCT start as service
Verified in Computer Management-Services that the OpenDCT service has started
Wait for 3 minutes
Use the SageTVServiceControl app to start the SageTV service
Verified in Computer Management-Services that the SageTV service has started

Started SageTV in my home theater system using the HD300
Went to Setup-Setup Video Sources-Add New Source
There are NO OpenDCT found tuners listed

The OpenDCT service (http://192.168.99.51:9091) is showing that these are available:

OpenDCT 0.5.32
Loaded Capture Devices:

DCT-HDHomeRun HDFX-4K Tuner 10A26C08-0: Idle
DCT-HDHomeRun HDFX-4K Tuner 10A26C08-1: Idle
DCT-HDHomeRun HDFX-4K Tuner 10A26C08-2: Idle
DCT-HDHomeRun HDFX-4K Tuner 10A26C08-3: Idle
DCT-HDHomeRun Prime Tuner 1324B362-0: Idle
DCT-HDHomeRun Prime Tuner 1324B362-1: Idle
DCT-HDHomeRun Prime Tuner 1324B362-2: Idle

So the OpenDCT service is saying those are available, but for some reason, SageTV is reading that they are not out there.

Kinda at a loss now. This has worked for a bunch of folks with no problems. Worked for me in the past with no problems.

I can't figure out what is causing the break in communication between OpenDCT and SageTV.

Attachements:
OpenDCT as console log.txt
opendct.log
wrapper.log
opendct.properties
Sage.properties

[nyplayer]

Originally Posted by CptKirk

Sorry for the long post. What I have done to try and get to as 'clean' a spot in trying to get Prime tuners into SageTV with OpenDCT.

Ran SageTVSetupx86_9.2.6.exe and did a Repair
Rebooted server

Uninstalled Java 8 32bit
Uninstalled HDHomerun software
Uninstalled Opendct
Rebooted server
Checked C:\Program Files, C:\Program Files (x86), C:\ProgramData for any folder of the uninstalled software and manually deleted them.
Rebooted server

Install jre-8u311-windows-i586.exe
Rebooted server

Install hdhomerun_windows_20211212.exe
Rebooted server

Run hdhomerun_setup
hdhomerun_setup finds my 7 tuners, 3 prime cc and 4 4k-flex ota
hdhomerun_setup DBA set to sagetv
hdhomerun_setup cc start channel scan
hdhomerun_setup channel scan completed, 500+ comcast channels found, clicked Apply
hdhomerun_setup clicked on a few of the channels, vlc opens and starts playing the channel
hdhomerun_setup for completeness went to the digital antenna tab and did a channel scan there as well, clicked Apply
Open the Prime web interface at http://192.168.99.55/, Card Authentication success, Card OOB Lock success, Card Validation success. All CC status looks ok. Clicked on Channel Lineup, click on Detect Channels and do a channel scan here as well.
Rebooted server

Install OpenDCT_0.5.32_x86.msi

Both SageTV service and SageTV OpenDCT service are set to manual startup type by me so that I can control when they are actually running. Both are set to Log On As to a local account with administrator privileges

Run OpenDCT as console
After finished checked the opendct.log file. There are 4 Java errors that happened in HDHomeRunControl and HDHomeRunDiscovery.
Log files attached
Rebooted server

From start menu did: OpenDCT start as service
Verified in Computer Management-Services that the OpenDCT service has started
Wait for 3 minutes
Use the SageTVServiceControl app to start the SageTV service
Verified in Computer Management-Services that the SageTV service has started

Started SageTV in my home theater system using the HD300
Went to Setup-Setup Video Sources-Add New Source
There are NO OpenDCT found tuners listed

The OpenDCT service (http://192.168.99.51:9091) is showing that these are available:

OpenDCT 0.5.32
Loaded Capture Devices:

DCT-HDHomeRun HDFX-4K Tuner 10A26C08-0: Idle
DCT-HDHomeRun HDFX-4K Tuner 10A26C08-1: Idle
DCT-HDHomeRun HDFX-4K Tuner 10A26C08-2: Idle
DCT-HDHomeRun HDFX-4K Tuner 10A26C08-3: Idle
DCT-HDHomeRun Prime Tuner 1324B362-0: Idle
DCT-HDHomeRun Prime Tuner 1324B362-1: Idle
DCT-HDHomeRun Prime Tuner 1324B362-2: Idle

So the OpenDCT service is saying those are available, but for some reason, SageTV is reading that they are not out there.

Kinda at a loss now. This has worked for a bunch of folks with no problems. Worked for me in the past with no problems.

I can't figure out what is causing the break in communication between OpenDCT and SageTV.

Attachements:
OpenDCT as console log.txt
opendct.log
wrapper.log
opendct.properties
Sage.properties

OPENDCT looks good the Prime is there so it is not a problem with OPENDCT ... I am looking through your sage.properties maybe I can spot something.

[nyplayer]

Is the subnet on your server 255.255.255.252 ? that is what it should be for your ip range.

IP Address:	192.168.99.55
Network Address:	192.168.99.52
Usable Host IP Range:	192.168.99.53 - 192.168.99.54
Broadcast Address:	192.168.99.55
Total Number of Hosts:	4
Number of Usable Hosts:	2
Subnet Mask:	255.255.255.252
Wildcard Mask:	0.0.0.3
Binary Subnet Mask:	11111111.11111111.11111111.11111100
IP Class:	C
CIDR Notation:	/30
IP Type:	Private
 
Short:	192.168.99.55 /30
Binary ID:	11000000101010000110001100110111
Integer ID:	3232260919
Hex ID:	0xc0a86337
in-addr.arpa:	55.99.168.192.in-addr.arpa
IPv4 Mapped Address:	::ffff:c0a8.6337
6to4 Prefix:	2002:c0a8.6337::/48

[hb4]

Maybe a sage.properties setting? Perhaps a full Sage uninstall/install cycle would work better. Doesn't the stop/start OpenDCT service cycle cause the changes in sage.properties to add tuners? If so, you could stop OpenDCT, uninstall/install Sage, copy Wiz.bin only, and <Edit> start OpenDCT and then Sage <Edit>

I'm always worried that past sage.properties changes don't get re-set with this method, but it worked for my latest install so all's well that ends well I guess.

[CptKirk]

No, using 255.255.255.0, which was setup automatically when I created my network on my Unifi hardware.

Gateway IP/Subnet 192.168.99.1/24

Gateway IP 192.168.99.1
Network Broadcast IP 192.168.99.255
Network IP Count 254
Network IP Range 192.168.99.1 - 192.168.99.254
Network Subnet Mask 255.255.255.0

I have a good 30 network clients spread out over that range.

That is a perfectly fine private IP range with the 255.255.255.0 mask.

192.168.99.51 is the server that SageTV and OpenDCT are running on.

192.168.99.55 is the HDHomerun Prime unit.

[CptKirk]

With the SageTV service off, when you run opendct console, then start the opendct service is it supposed to write entries into the sage.properties file?

Is that how Sagetv knows the tuners from opendct are there?

[nyplayer]

Originally Posted by CptKirk

No, using 255.255.255.0, which was setup automatically when I created my network on my Unifi hardware.



I have a good 30 network clients spread out over that range.

That is a perfectly fine private IP range with the 255.255.255.0 mask.

192.168.99.51 is the server that SageTV and OpenDCT are running on.

192.168.99.55 is the HDHomerun Prime unit.

Good just covering all possibilities. UPNP is enable ? ran out of ideas.

[CptKirk]

Win7 box with 'Turn on network discovery' checked, which is what I believe has UPNP on.

I am running out of ideas as well. Really don't want to do a SageTV uninstall/install. Too much stuff to try and remember how I setup everything.

Added the sagetv_0.txt file which I'm going through now as well. But nothing is jumping out at me. I was doing the opendct work around the 13:30 time mark.

Edit...

I do see this though in sagetv_0.txt

Thu 1/13 13:34:35.070 [main@9f23b4] Error discovering servers:java.net.SocketTimeoutException: Receive timed out
Thu 1/13 13:34:35.071 [main@9f23b4] ERROR in network encoder server discovery of: java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine

Which is at the beginning where it was starting to work on tuners.

[jhkoenig]

Have you checked your Windows Firewall to be sure that Sage and OpenDCT can connect with each other? Many years ago when I first set up OpenDCT I faced similar issues that ended up being the (software) firewall. I have no idea beyond that, sadly.

[JustFred]

The devices named DCT-HDHomeRun* (in opendct.properites) didn't get populated into sage.properties.

One likely cause: the SageTv program or service was already running when the DCT console was run. As an experiment, use TaskManager (not the SageTVServiceControl app) to stop the SageTv program and service. Then re-run the DCT console. Next, before starting SageTv, inspect the contents of sage.properties. You should see multiple entries starting with "mmc/encoders" for each of the "device_name=DCT-HDHomeRun" lines in opendct.properties.

After the DCT-HDHomeRun entries are present in sage.properties, start SageTv.

[CptKirk]

I actually disabled the firewall completely to test that out. No luck with that.

The devices named DCT-HDHomeRun* (in opendct.properites) didn't get populated into sage.properties.

^^ this

I agree this is what is happening (or not happening).

I have been using Computer Management-Services to make sure the services were running or not as well.

I will switch and use task manager and give it another try.

Edit...

Ok, used task manager and verified that I have no processes or services of SageTV running. Also checked Computer Management-Services there again as well.

OpenDCT service is also not running.

Ran the opendct as console, before starting sagetv or opendct services I open sage.properties and check for mmc/encoders.

The four hdhomerun 4K flex ota tuners show up:

mmc/encoders/1961691293/video_capture_device_name=Silicondust HDHomeRun Tuner 10A26C08-0
mmc/encoders/1961691294/video_capture_device_name=Silicondust HDHomeRun Tuner 10A26C08-1
mmc/encoders/1961691295/video_capture_device_name=Silicondust HDHomeRun Tuner 10A26C08-2
mmc/encoders/1961691296/video_capture_device_name=Silicondust HDHomeRun Tuner 10A26C08-3

As BDA devices. Not as the OpenDCT devices. The Prime does not show up at all.

None of these show up in the sage.properties file:

DCT-HDHomeRun HDFX-4K Tuner 10A26C08-0: Idle
DCT-HDHomeRun HDFX-4K Tuner 10A26C08-1: Idle
DCT-HDHomeRun HDFX-4K Tuner 10A26C08-2: Idle
DCT-HDHomeRun HDFX-4K Tuner 10A26C08-3: Idle
DCT-HDHomeRun Prime Tuner 1324B362-0: Idle
DCT-HDHomeRun Prime Tuner 1324B362-1: Idle
DCT-HDHomeRun Prime Tuner 1324B362-2: Idle

So I've got something that is stopping opendct console from writing to sage.properties.

FYI, I doulbe checked again an neither of the services are running yet.

[CptKirk]

Attached

opendct console log.txt
wrapper.log
opendct.log

from what I just attempted.

[nyplayer]

Originally Posted by CptKirk

Attached

opendct console log.txt
wrapper.log
opendct.log

from what I just attempted.

Why don't you message enternoescape he can probably tell you exactly what is wrong. Looks like you are getting bombarded with Ideas.... and I am one of them doing the bombarding.