Hello is it possible to connect two TVHeadend servers.

I want to bring channels from TVHeadend Server A to TVHeadend Server B. 

but the client accesses only server B

Br ados

 

Hi!

 

I am just researching at the moment before I purchase equipment. Is it possible to use a combination of tuners with TVheadend in Unraid - e.g. a PCIe DVB-S2 tuner alongside a networked DVB-T2 HDHomeRun quad tuner?

 

Does anyone know if the TBS 6981 card (DVB-S2 Dual Tuner) is a known working card and would integrate with TVheadend with minimal issues?

 

If anyone has a recommendation for a DVB-S2/DVB-T2combo tuner for Freeview & Freesat that is compatible with this TVheadend docker image (Unicable compatible for the satellite would be a big bonus) I would greatly appreciate the steer in the right direction!

 

Thanks

 

Edited June 17, 20233 yr by eric90000

5 hours ago, eric90000 said:

e.g. a PCIe DVB-S2 tuner alongside a networked DVB-T2 HDHomeRun quad tuner?

yes, works fine with TVH, Combo of SAT & Network Tuners, preferable SATIP Standard, but TVH also has native HDHR support afaik

 

5 hours ago, eric90000 said:

If anyone has a recommendation for a DVB-S2/DVB-T2combo tuner for Freeview & Freesat that is compatible with this TVheadend docker image (Unicable compatible for the satellite would be a big bonus) I would greatly appreciate the steer in the right direction!

im using a DD Max S8 as unicable card

 

here as sample from my setup, unicable pcie card and a network SATIP Tuner

 

16 minutes ago, alturismo said:

yes, works fine with TVH, Combo of SAT & Network Tuners, preferable SATIP Standard, but TVH also has native HDHR support afaik

 

im using a DD Max S8 as unicable card

Thank you very much, that is great to know a combination of SATIP and tuner cards works well for you.

 

I will check out those devices you mentioned. From what I gather from reading online, the general consensus seems to be that the SATIP approach is the easiest, as it rules out driver issues with physical PCIe cards. I had been trying to find a Digibit R1 SATIP device, which could be paired with something like a HDHomeRun for DVB-T.

 

I really appreciate the screenshot of your setup - it will be handy when I come to setting mine up.

and here is the config for my hdhomerun. Nothing special needed in the docker xml to make this work, and appears rock solid.

 

 

 

Help, I'm stuck. Im trying to setup epg with url file location but i dont know how to edit tv_grab_file in bin folder to auto download epg

Edited December 23, 20232 yr by Doktor-X

1 hour ago, Doktor-X said:

Help, I'm stuck. Im trying to setup epg with url file location but i dont know how to edit tv_grab_file in bin folder to auto download epg

Check my post on November 7 22 maybe it can help you get started in the right direction.

13 hours ago, Mrtj18 said:

Check my post on November 7 22 maybe it can help you get started in the right direction.

Thanks, i did saw it, but i did not manage to get it to work like that, but then i just downloaded epg file with wget and place it to /mnt/cache/appdata/tvheadend/data folder and it works, now i just to need to automate download from web to specific folder

There's an option within TV headend ( I don't have access to my server at the moment) where it is set to run a cron job that will auto pull your epg data. Make sure you have that set. Should be under the epg grabber section.

26 minutes ago, Mrtj18 said:

There's an option within TV headend ( I don't have access to my server at the moment) where it is set to run a cron job that will auto pull your epg data. Make sure you have that set. Should be under the epg grabber section.

This is just for update tvh epg database from file, but i need to automate download of epg file itself from web location once in a while to be able to keep up with epg changes. I manage to automate this using user scripts plugin and i made simple wget script like that

"wget -O /mnt/cache/appdata/tvheadend/data/epg.xml http://user:password@ip:9981/xmltv"

 

I'm pulling epg from another tvh server

Edited December 24, 20232 yr by Doktor-X

**** BELOW FIXED **** Turns out the HDHomeRun tuner was going faulty. Replaced tuner and now working

 

Hi, i've been using this TVHEADEND docker for many years without issue.

 

Tuner: HDHomeRun Connect Quatro HDHR5-4DT, Firmware latest - 20231214. I'm in the UK using DVB-T/T2.

 

This is used through Kodi and OSMC and I have just recently noticed I can't view any channel. 

 

Checking the docker I can still see the HDHomeRun and get green lights on all 4 tuners.

 

 

However when I look at the Muxes the scan results are all set at failed. You can see I previously had services and these were mapped.

 

No matter what I try I cannot scan the Muxes which is why it is not working through Kodi. I also have an HDMI to iptv converter which allows for Sky to be distributed via TVHeadend and that still works OK.

 

I have tested:

- I do have a strong reception on my TV Ariel

- Using HDHomeRun software on the PC I tune into stations and can watch TV (So I know the HDHomeRun unit is working)

- Using HDHomeRun software on a Fire Stick I can watch TV so again the HDHomeRun unit is working.

 

There has been some Firmware updates on the HDHomeRun which were automatically applied. As I normally watch TV through Sky I did not take much notice as I don't the HDHomeRun as my daily driver.

 

Has anyone else using HDHomeRun Quattro or Duo running through TVHeadend noticed their system not working in the last few months?

 

Any suggestions on what I can do?

 

Many thanks

 

 

Edited February 1, 20242 yr by chakobsa

On 1/28/2024 at 11:30 AM, chakobsa said:

**** BELOW FIXED **** Turns out the HDHomeRun tuner was going faulty. Replaced tuner and now working

 

Hi, i've been using this TVHEADEND docker for many years without issue.

 

Tuner: HDHomeRun Connect Quatro HDHR5-4DT, Firmware latest - 20231214. I'm in the UK using DVB-T/T2.

 

This is used through Kodi and OSMC and I have just recently noticed I can't view any channel. 

 

Checking the docker I can still see the HDHomeRun and get green lights on all 4 tuners.

 

 

However when I look at the Muxes the scan results are all set at failed. You can see I previously had services and these were mapped.

 

No matter what I try I cannot scan the Muxes which is why it is not working through Kodi. I also have an HDMI to iptv converter which allows for Sky to be distributed via TVHeadend and that still works OK.

 

I have tested:

- I do have a strong reception on my TV Ariel

- Using HDHomeRun software on the PC I tune into stations and can watch TV (So I know the HDHomeRun unit is working)

- Using HDHomeRun software on a Fire Stick I can watch TV so again the HDHomeRun unit is working.

 

There has been some Firmware updates on the HDHomeRun which were automatically applied. As I normally watch TV through Sky I did not take much notice as I don't the HDHomeRun as my daily driver.

 

Has anyone else using HDHomeRun Quattro or Duo running through TVHeadend noticed their system not working in the last few months?

 

Any suggestions on what I can do?

 

Many thanks

 

 

I've got an similar issus...

But my Tuner works well (with a TVHeadend on a Pi)
😞

Edited March 14, 20242 yr by fcscholz
Error

Hello. I am using this docker with the TVHeadend (libreelec) and this docker gets updated fairly often so that TVH version in this is always newer than the one on my dedicated libreelec boxes running TVH. On those older versions of TVH (4.3-2180) , looking at the start time/ end time columns in the epg guide and recordings tabs they have the day of the week included with the time and date. but on this newer version in the docker (currently 4.3-2336~g366e56290) the day is missing, just showing time and date. I am not sure if this is something you can rectify or whether it is down to the developers of TVH, because I prefer to see the day information.

1 hour ago, boragthung70 said:

whether it is down to the developers of TVH

Exactly 😉

Thanks for confirming. I just wasn't sure if the docker version was customised or something.

1 hour ago, boragthung70 said:

Thanks for confirming. I just wasn't sure if the docker version was customised or something.

the apps inside dockers are more or less never customized, if ... then most common just added extras ...

 

may just ask here if its possible to start tvheadend with a special option to get the wanted feature

 

https://tvheadend.org/t/general-support

 

i assume we talk about this and you prefer to have the day (sample friday) written there

 

Exactly right. It is a lot easier ensuring no interfering recordings are set when you can see the day as well. To me anyway 😀.

Got this all set up and working to Plex. Is there a buffer setting I can change in TVHeadend? Plex likes to stop playing 1-2 during a 2-hour hockey game for example.

 

Thank You

9 hours ago, kumper33 said:

Plex likes to stop playing 1-2 during a 2-hour hockey game for example.

may rather describe your complete setup and also how you come to the conclusion tvheadend buffering could help.

 

1/ tvheadend input == dvb, iptv, ... ?

2/ plex is connected to tvh how ?

3/ Plex is playing direct or transcoded ?

 

then may someone could may help ...

On 8/4/2021 at 1:04 AM, Guillaurent said:

I've found the issue I was having. The incoming UDP traffic could not get through to the tvheadend container in Network type bridge (or custon bridge).

Switching Network type to Host did the trick but I don't know if there's another way around it.

Sorry for the post digging but this was useful for me. It may be useful for other.

A fix has been added in TVH to force a range of ports for RTSP UDP

https://github.com/tvheadend/tvheadend/issues/1738

You will find these settings in latest version of TVH in Configuration > General > Base (in expert mode)
Settings are named: RTSP UDP minimum port & RTSP UDP maximum port.
You should choose a range of at least 2 ports but I would recommend 12 at least

you should then pass this ports to the container. In a docker composer yaml file it should look like this.

 ports:
 - 9981:9981
 - 9982:9982
 - "26000-26012:26000-26012/udp"

26000 to 26012 is the range I chose.

I've bought a Digibit Twin, which is on my local network at 192.168.1.188. I can see it when I set up tvheadend on a local machine, but the Linuxserver container doesn't see it — it just offers me IPTV networks in the wizard.

Presumably the Docker network type is to blame — I have it set to the same custom network as the Jellyfin container, but whatever tvheadend is doing to discover the SATIP stuff isn't working.

Is this the correct network type? I do need the Jellyfin container to be able to access tvheadend. Or do I need to add some explicit flags to point tvheadend at the tuner?

2 hours ago, ElectricBadger said:

Or do I need to add some explicit flags to point tvheadend at the tuner?

as satip broadcasts tvheadend wont see it in a regular bridge (or custom network in a bridge)

you can try the following

• host mode

• custom br0 (eth0) on its own IP

and you also may add the xml url as RUN_OPTS env in Tvheadend, like described in the tvheadend docs, sample

i run dvb-c (fritz) and dvb-s (digital devices)

when i google about your device, may should be something like this

http://<your_digibit_ip>:38400/description.xml

cant tell as i run different devices.

if you want to keep in bridge mode, then you also need to bind ports on tuners and forward them to the docker,
each tuner would need 2 ports, sample here 9998-9999

also may some settings specific for your tuner need to be done, read into it if there are issues.

so, may just read some tvheadend docs and enjoy then ;)

16 hours ago, alturismo said:

as satip broadcasts tvheadend wont see it in a regular bridge (or custom network in a bridge)

you can try the following

• host mode

• custom br0 (eth0) on its own IP

and you also may add the xml url as RUN_OPTS env in Tvheadend, like described in the tvheadend docs, sample

i run dvb-c (fritz) and dvb-s (digital devices)

when i google about your device, may should be something like this

cant tell as i run different devices.

if you want to keep in bridge mode, then you also need to bind ports on tuners and forward them to the docker,
each tuner would need 2 ports, sample here 9998-9999

also may some settings specific for your tuner need to be done, read into it if there are issues.

so, may just read some tvheadend docs and enjoy then ;)

Thanks — giving it its own IP solved the problem.