enabled this EPG grabber module ?

 

15 hours ago, alturismo said:

enabled this EPG grabber module ?

 

where is this?

i have in the config file but not found it in the gui.

 

edit: found it, I dont have an internal option but I have an external: XMLTV grab which is enabled an pointing at the socket file

Edited August 10, 20196 yr by geekypenguin

Hello there,

 

have the following problem, when try install the dockerfile:

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-tvheadend' --net='bridge' --log-opt max-size='50m' --log-opt max-file='1' --privileged=true -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '9981:9981/tcp' -p '9982:9982/tcp' -v '/mnt/user/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-tvheadend':'/config':'rw' --device=/dev/tuner type 'binhex/arch-tvheadend'

Unable to find image 'type:latest' locally
/usr/bin/docker: Error response from daemon: pull access denied for type, repository does not exist or may require 'docker login'.
See '/usr/bin/docker run --help'.

The command failed.

 

I think you had to change type:latest to stable or something else, that the image can be downloaded...

 

Or maybe need docker login?

 

Thank you!

28 minutes ago, Holle88 said:

Hello there,

 

have the following problem, when try install the dockerfile:

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-tvheadend' --net='bridge' --log-opt max-size='50m' --log-opt max-file='1' --privileged=true -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '9981:9981/tcp' -p '9982:9982/tcp' -v '/mnt/user/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-tvheadend':'/config':'rw' --device=/dev/tuner type 'binhex/arch-tvheadend'

Unable to find image 'type:latest' locally
/usr/bin/docker: Error response from daemon: pull access denied for type, repository does not exist or may require 'docker login'.
See '/usr/bin/docker run --help'.

The command failed.

 

I think you had to change type:latest to stable or something else, that the image can be downloaded...

 

Or maybe need docker login?

 

Thank you!

Your docker run is broken because you haven't filled in your tuner type. That field shouldn't say "tuner type", that is something you are supposed to replace with the correct value for your specific hardware.

 

Did you read the docs linked in the first post of this thread?

Have I missed something here, what is the default username and password ? 

On 12/11/2019 at 2:32 PM, trurl said:

Your docker run is broken because you haven't filled in your tuner type. That field shouldn't say "tuner type", that is something you are supposed to replace with the correct value for your specific hardware.

 

Did you read the docs linked in the first post of this thread?

I have the same issue. Read all the docs in the first post and there is no mention of setting tuner type, nor is there any option of setting tuner type in the docker setup page. Tuner type set to 'binhex/arch-tvheadend' by default and cannot be changed. I'm sure this is NOT the issue.

9 minutes ago, shinoobieeve said:

I have the same issue. Read all the docs in the first post and there is no mention of setting tuner type, nor is there any option of setting tuner type in the docker setup page. Tuner type set to 'binhex/arch-tvheadend' by default and cannot be changed. I'm sure this is NOT the issue.

Ok, so found the advanced options button and removed "--device=/dev/tuner type" from extra parameters and now the docker starts

I have just set up TVH to serve streams from my internal Hauppauge DVB card to Xteve and merge with IPTV for use in PLEX on my unraid box.

 

I previously had the card working direct in plex. TVH can get the channels and EPG data (from the terrestrial stream) but when I try and play in the webgui it either stays on loading or gives me an unexpected error. I can access the playlist and epg export from TVH in Xteve but I cannot view the TV channels in plex or TVH webgui

On 9/8/2020 at 11:54 AM, kavo said:

I have just set up TVH to serve streams from my internal Hauppauge DVB card to Xteve and merge with IPTV for use in PLEX on my unraid box.

 

I previously had the card working direct in plex. TVH can get the channels and EPG data (from the terrestrial stream) but when I try and play in the webgui it either stays on loading or gives me an unexpected error. I can access the playlist and epg export from TVH in Xteve but I cannot view the TV channels in plex or TVH webgui

So I now have some updates - I am getting poll timeout - this seems to be intermittent as I have been able to get it working after increasing the descramble timeout on the streams settings but basically 99% of the time I can't get anything to work. Here is the log from TVH

 

2020-09-09 21:47:55.159 http: 192.168.0.58: using ticket e6699b0a240f1d4b5e86bef72a9e13d7a895590a for /stream/channel/ed244666e0765118183c5710fab6fd1f
2020-09-09 21:47:55.159 mpegts: 655.625MHz in DVB-T Network - tuning on Silicon Labs Si2168 #1 : DVB-T #0
2020-09-09 21:47:55.159 subscription: 03C0: "HTTP" subscribing on channel "7mateHD Toowoomba", weight: 100, adapter: "Silicon Labs Si2168 #1 : DVB-T #0", network: "DVB-T Network", mux: "655.625MHz", provider: "Seven Network", service: "7mateHD Toowoomba", profile="pass", hostname="192.168.0.58", username="mitch", client="VLC/3.0.6 LibVLC/3.0.6"
2020-09-09 21:47:56.217 linuxdvb: Silicon Labs Si2168 #1 : DVB-T #0 - poll TIMEOUT
2020-09-09 21:48:01.159 subscription: 03C0: service instance is bad, reason: No input detected
2020-09-09 21:48:01.179 mpegts: 655.5MHz in DVB-T Network - tuning on Silicon Labs Si2168 #1 : DVB-T #0
2020-09-09 21:48:01.179 subscription: 03C0: "HTTP" subscribing on channel "7mateHD Toowoomba", weight: 100, adapter: "Silicon Labs Si2168 #1 : DVB-T #0", network: "DVB-T Network", mux: "655.5MHz", provider: "Seven Network", service: "7mateHD Toowoomba", profile="pass", hostname="192.168.0.58", username="mitch", client="VLC/3.0.6 LibVLC/3.0.6"
2020-09-09 21:48:02.267 linuxdvb: Silicon Labs Si2168 #1 : DVB-T #0 - poll TIMEOUT
2020-09-09 21:48:07.160 subscription: 03C0: service instance is bad, reason: No input detected
2020-09-09 21:48:09.160 subscription: 03C0: restarting channel 7mateHD Toowoomba
2020-09-09 21:48:11.160 mpegts: 655.625MHz in DVB-T Network - tuning on Silicon Labs Si2168 #1 : DVB-T #0
2020-09-09 21:48:11.160 subscription: 03C0: "HTTP" subscribing on channel "7mateHD Toowoomba", weight: 100, adapter: "Silicon Labs Si2168 #1 : DVB-T #0", network: "DVB-T Network", mux: "655.625MHz", provider: "Seven Network", service: "7mateHD Toowoomba", profile="pass", hostname="192.168.0.58", username="mitch", client="VLC/3.0.6 LibVLC/3.0.6"
2020-09-09 21:48:12.218 linuxdvb: Silicon Labs Si2168 #1 : DVB-T #0 - poll TIMEOUT
2020-09-09 21:48:16.094 webui: Stop streaming /stream/channel/ed244666e0765118183c5710fab6fd1f?ticket=e6699b0a240f1d4b5e86bef72a9e13d7a895590a, timeout waiting for packets
2020-09-09 21:48:16.094 subscription: 03C0: "HTTP" unsubscribing from "7mateHD Toowoomba", hostname="192.168.0.58", username="mitch", client="VLC/3.0.6 LibVLC/3.0.6"

 

TVHeadEnd Docker with Technisat SKYSTAR 2 DVB-S2 PCI card?
Hi there - interested to see if this will work with an old DVB-S2 card that I have lying around:
https://www.technisat.com/en_XX/Downloads-and-Information/352-515/?tsc=1&productID=1676
It is supposed to have linux support, but from what I can see there used to be issues with this card in the past:
https://tvheadend.org/boards/5/topics/2905
Just wondering if anyone has had any success with this card before I go down this rabbit hole  

I had this docker installed for a long time and it worked great.  I had to rebuild my docker image file and re-install my apps and found that this will not install now.

 

When I click on the Install icon, this is what I see;

 

 

After hitting Apply, I get the follow errors;

 

IMAGE ID [1896728381]: Pulling from binhex/arch-tvheadend.
IMAGE ID [3b4c5248da92]: Pulling fs layer. Downloading 100% of 263 B. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [684482506bb1]: Pulling fs layer. Downloading 100% of 2 KB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [039d9be946ba]: Pulling fs layer. Downloading 100% of 656 KB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [f0784c3ceec3]: Pulling fs layer. Downloading 100% of 5 KB. Verifying Checksum. Extracting. Pull complete.
IMAGE ID [be2ac6bab66e]: Pulling fs layer. Downloading 100% of 170 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [e554bfb17b98]: Pulling fs layer. Downloading 100% of 292 B. Verifying Checksum. Download complete. Extracting. Pull complete.
IMAGE ID [bf5a1987e1d2]: Pulling fs layer. Downloading 100% of 2 KB. Download complete. Extracting. Pull complete.
IMAGE ID [7c4efb200f59]: Pulling fs layer. Downloading 100% of 187 MB. Verifying Checksum. Download complete. Extracting. Pull complete.
Status: Downloaded newer image for binhex/arch-tvheadend:latest

TOTAL DATA PULLED: 358 MB

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-tvheadend' --net='bridge' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '9981:9981/tcp' -p '9982:9982/tcp' -v '/mnt/user/HDHomeRun/':'/data':'rw' -v '/mnt/user/Automation/Apps/binhex-tvheadend':'/config':'rw' --device=/dev/tuner type 'binhex/arch-tvheadend:latest'
Unable to find image 'type:latest' locally
/usr/bin/docker: Error response from daemon: pull access denied for type, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See '/usr/bin/docker run --help'.

The command failed.

 

Help please

Hello

 

Can you tell me if this is correct, I can't work out which is the AV In?

Thank you

I am assuming DVB-C uses the same input as DVB-S?

 

 

Having the same problem as @optiman resulting in an orphaned docker image. Has anyone a solution to get the docker running? @binhex

 

16 minutes ago, faxesystem said:

Having the same problem as @optiman resulting in an orphaned docker image. Has anyone a solution to get the docker running? @binhex

 

your issue is with the '--device=/dev/tuner type' note the space between tuner and type, this is causing docker to think 'type' is a part of the repository name and thus failing, you might need to change it to be in single quotes in order to get around this issue.

@binhex thank you for the quick solution. How can I do this? When using the GUI I don't see that this device is mentioned anywhere in the docker config.

21 hours ago, faxesystem said:

How can I do this? When using the GUI I don't see that this device is mentioned anywhere in the docker config.

 

left click tvheadend icon, select edit, click 'advanced view' toggle button top right then look for 'extra parameters' change the value of this to be the dvb device type you want, e.g.:-

 

--device=/dev/dvb

 

What do I need to put into the device type if I want to use iptv?

I have tried --device=/dev/iptv or --device=/dev/IPTV 

I get a failure with

"Error response from daemon: error gathering device information while adding custom device "/dev/IPTV": no such file or directory."

What do I need to change?

5 minutes ago, ridley said:

What do I need to change?

 

iptv is no physical device ... so nothing as /dev/...

 

may take a look at tvheadend forums about add iptv network and so on ... most common u need to pipe the streams also as they are not .ts standard, just as note ahead, there are plenty threads at the tvheadend forum.

 

thx

 

Hello Guys,

is it possible to route the tvheadend trough another docker container with vpn? I made the changes from spaceinvaderone video "how to route any docker container trough a VPN container" but I can't connect to the container. As soon as I changed the settings back to stock, I can connect to the webui
Made the following changes:
Network Type: None
Extra parameters: --net=container:sabnzbdvpn (it's my container with vpn - wireguard)
Added the two ports to the sabnzbdvpn container (9981 + 9982)

Thanks :)

47 minutes ago, Hyvacation said:

is it possible to route the tvheadend trough another docker container with vpn?

like any container, yes

 

47 minutes ago, Hyvacation said:

Extra parameters: --net=container:sabnzbdvpn (it's my container with vpn - wireguard)
Added the two ports to the sabnzbdvpn container (9981 + 9982)

should be correct and working, may ask in the VPN Forum's from him how to handle this, when i remember correctly he made some changes and added these variables also ... just when i remember correctly

 

I have just got an Sat>IP tuner/Server(?), this one https://www.amazon.co.uk/gp/product/B016XL584C/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

 

And I have tried it out using a standalone player, which found the server, scanned the channels and allowed me to watch all the Freesat channels across the network, great!

However, I cannot seem to get TVHEADEND to work with it, should TVHE detect it like the standalone player did?

Any advice or links to help would be greatly appreciated.

1 hour ago, ridley said:

However, I cannot seem to get TVHEADEND to work with it, should TVHE detect it like the standalone player did?

yes, but tvheadend needs to run in host mode or custom:br0 (which is also a host mode with individual ip)

2 hours ago, alturismo said:

yes, but tvheadend needs to run in host mode or custom:br0 (which is also a host mode with individual ip)

 

I have set it to "Host"* and it has seen the sat>IP server straight away and is now busily scanning for channels, thanks so much.

 

* which is preferable "Host" or "Custom:br0"?

Edited February 19, 20224 yr by ridley

7 hours ago, ridley said:

* which is preferable "Host" or "Custom:br0"?

a matter of personal taste ...

 

to make it short as its offtopic here, stay in host mode now, keep in mind that its blocking now the used ports in unraid, like 9981-9983, ... so in terms another docker, app, ... needs it you have to rethink your setup. custom:br0 is not everybodys darling ....