Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] Linuxserver.io - TVHeadend

Featured Replies

14 minutes ago, Maggi0r said:

If I don't install the driver.
If the DVB stick is not found in the TVH plugin.
I also have to have installed the DVB plugin otherwise the DVB driver is not recognized by the TVH plugin.


root@2e48b5c5004d:/# ls -al /dev/dvb
total 0
drwxr-xr-x 3 root root  60 Jun  3 11:36 .
drwxr-xr-x 6 root root 360 Jun  3 11:36 ..
drwxr-xr-x 2 root root 100 Jun  3 11:36 adapter0
root@2e48b5c5004d:/# 

These are the authorizations when I reinstall the TVH Docker.

 

Regards Maggi

Then you have not changed the permissions on the adapter correctly in unraid. It should say abc:abc as user.

  • Replies 1.3k
  • Views 315.1k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • You need to install the driver to use your adapter. Then use /dev/dvb as the path for the device pass through. If you are using 6.9.x I don't know if the permissions are set correctly, so make sure no

  • Thanks man, I'm just playing around with TV stuff so I'll try it here. 

  • I tried WG+ but in the end I gave up, purely because it's too complicated and too cumbersome. I got it working, but it wasn't reliable and you have to rebuild the first search index relatively frequen

Posted Images

Ok so that means I have to chown -R abc: abc / dev / dvb or chown -R nobody: users / dev / dvb.

If I run chown -R abc: abc / dev / dvb on unraid, I get chown: invalid user: 'abc: abc'.

 

Regards Maggi

6 minutes ago, Maggi0r said:

Ok so that means I have to chown -R abc: abc / dev / dvb or chown -R nobody: users / dev / dvb.

If I run chown -R abc: abc / dev / dvb on unraid, I get chown: invalid user: 'abc: abc'.

 

Regards Maggi

You use the command I already supplied in a previous post.

The abc user is only in the container.

Also do chmod -R 777 /dev/dvb

 

You should not have any space in the command either. Use exactly what I have posted.

Edited by saarg

So I think I'm kind of too stupid for that.

Here again what I did now.

 

on the unraid servver
chown -R nobody: users /dev/dvb
chmod -R 777 /dev/dvb

This is how it looks now. On the unraid.
root @ Tower: / dev / dvb # ls -al /dev/dvb
totally 0
drwxrwxrwx 3 nobody users 60 Jun 3 11:10 ./
drwxr-xr-x 17 root root 3320 Jun 3 12:07 ../
drwxrwxrwx 2 nobody users 100 Jun 3 11:10 adapter0 /
root @ tower: / dev / dvb #

 

on the TVHDocker
chown -R abc: abc /dev/dvb
chmod -R 777 /dev/dvb

 

After restarting the container, the rights are set to root again.

But unfortunately it doesn't help the adapter is found.

Regards Maggi

6 minutes ago, Maggi0r said:

So I think I'm kind of too stupid for that.

Here again what I did now.

 

on the unraid servver
chown -R nobody: users /dev/dvb
chmod -R 777 /dev/dvb

This is how it looks now. On the unraid.
root @ Tower: / dev / dvb # ls -al /dev/dvb
totally 0
drwxrwxrwx 3 nobody users 60 Jun 3 11:10 ./
drwxr-xr-x 17 root root 3320 Jun 3 12:07 ../
drwxrwxrwx 2 nobody users 100 Jun 3 11:10 adapter0 /
root @ tower: / dev / dvb #

 

on the TVHDocker
chown -R abc: abc /dev/dvb
chmod -R 777 /dev/dvb

 

After restarting the container, the rights are set to root again.

But unfortunately it doesn't help the adapter is found.

Regards Maggi

You don't do anything in the tvheadend container.

Also, have the container stopped when you do permission change on unraid. Then start the container and show me the permissions of /dev/dvb inside the container.

I have now done it as you said.
Before that I stopped the container.

on unraid
chown -R nobody: users /dev/dvb
chmod -R 777 /dev/dvb

These are the rights on the container.
root @ 2e48b5c5004d: / dev / dvb # ls -al /dev/dvb
totally 0
drwxr-xr-x 3 root root 60 Jun 3 12:49.
drwxr-xr-x 6 root root 360 Jun 3 12:49 ..
drwxr-xr-x 2 root root 100 Jun 3 12:49 adapter0
ls -al /dev/dvb/adapter0
totally 0
drwxr-xr-x 2 root root 100 Jun 3 12:49.
drwxr-xr-x 3 root root 60 Jun 3 12:49 ..
crwxrwxrwx 1 abc abc 212, 1 Jun 3 12:49 demux0
crwxrwxrwx 1 abc abc 212, 2 Jun 3 12:49 dvr0
crwxrwxrwx 1 abc abc 212, 0 Jun 3 12:49 frontend0

 

However, I still get the error in the LOG.

Regards Maggi

1 hour ago, Maggi0r said:

I have now done it as you said.
Before that I stopped the container.

on unraid
chown -R nobody: users /dev/dvb
chmod -R 777 /dev/dvb

These are the rights on the container.
root @ 2e48b5c5004d: / dev / dvb # ls -al /dev/dvb
totally 0
drwxr-xr-x 3 root root 60 Jun 3 12:49.
drwxr-xr-x 6 root root 360 Jun 3 12:49 ..
drwxr-xr-x 2 root root 100 Jun 3 12:49 adapter0
ls -al /dev/dvb/adapter0
totally 0
drwxr-xr-x 2 root root 100 Jun 3 12:49.
drwxr-xr-x 3 root root 60 Jun 3 12:49 ..
crwxrwxrwx 1 abc abc 212, 1 Jun 3 12:49 demux0
crwxrwxrwx 1 abc abc 212, 2 Jun 3 12:49 dvr0
crwxrwxrwx 1 abc abc 212, 0 Jun 3 12:49 frontend0

 

However, I still get the error in the LOG.

Regards Maggi

Then I do not know what is happening. Permissions should be correct now.

Yes, I think so too. I don't know why he still complains that he can't open it. Although all rights now fit.

As I said what surprised me is that the TVH plugin works.
I suspect it's somehow related to the transfer of rights or something.

Because the plugin seems to access the / dev / dvb folder directly.

 

As I said, the DVBUnraid plugin finds everything except the adapter itself.

 

Regards Maggi

Edited by Maggi0r

2 hours ago, Maggi0r said:

Yes, I think so too. I don't know why he still complains that he can't open it. Although all rights now fit.

As I said what surprised me is that the TVH plugin works.
I suspect it's somehow related to the transfer of rights or something.

Because the plugin seems to access the / dev / dvb folder directly.

 

As I said, the DVBUnraid plugin finds everything except the adapter itself.

 

Regards Maggi

The plugin is running as root so it has access to the dvb device.

Yes, I think so. But somehow doesn't help.
I think it is somehow related to the stick even though the driver is loaded. As you can see in DVBUnraid but somehow it is not handed over correctly.

Regards Maggi

25 minutes ago, Maggi0r said:

Yes, I think so. But somehow doesn't help.
I think it is somehow related to the stick even though the driver is loaded. As you can see in DVBUnraid but somehow it is not handed over correctly.

Regards Maggi

The dvb plugin only checks at boot, so as long as you install the driver yourself, the dvb plugin will not show it.

The dvb plugin doesn't hand anything over.

Yes, thanks, I thought so.
I suspect that I will probably not get it with the Sundtek piece.

I will probably get one from the main eye soon so that it works.

Anyone else has an idea with it.

Regards Maggi

On 02/06/2020 at 03:11, saarg said:

Não tenho certeza se o docker no Unraid tem suporte para V6.

-6 é a opção correta? Você não forneceu nada dos logs ou de quaisquer mensagens de erro, portanto, qual é o problema.

the launch function according to the forum documentation and

Server connectivity

  -6, --ipv6 Listen on IPv6

https://discourse.linuxserver.io/t/tvheadend-container-cannot-connect-no-matter-what-i-try/941

However, I don't know where to put it.

9 hours ago, saarg said:

You have to use the variable RUN_OPTS and set -6 or --ipv6 as the value in the docker template.

Worked perfectly !!

 

image.png.94654f0e964075d25a90b3279cb623f7.png

 

image.png.1e174032046adf6190947323d7892ca1.png

 

Thank you

  • 4 weeks later...

How is anyone else getting this to work? I'm lost....

root@Tower:/mnt/user/appdata/tvheadend# docker exec -it -u abc tvheadend /usr/bin/tv_grab_file --configure
/usr/bin/tv_grab_file: illegal option -- -
unknown option: -

 

10 minutes ago, Fith said:

How is anyone else getting this to work? I'm lost....


root@Tower:/mnt/user/appdata/tvheadend# docker exec -it -u abc tvheadend /usr/bin/tv_grab_file --configure
/usr/bin/tv_grab_file: illegal option -- -
unknown option: -

 

There is nothing to configure. It grabs the XML file in /config/data/

2 minutes ago, saarg said:

There is nothing to configure. It grabs the XML file in /config/data/

Yea, I had TVH on WSL but my Guide area is blank. Something not working....

image.thumb.png.37bc2b14c5092e98423c86b78bd8c8a9.png

 

 

Edited by Fith

Oh wait...I have no `config/data` ...Let me create that.....

Edited by Fith

Just now, Fith said:

Yea, I had TVH on WSL but my Guide area is blank. Something not working....

 

Huh? Wsl? If you are not running unraid, this is not the correct place for support.

Containers running on windows isn't something we really support either. We only test on Linux.

So go to our forum or join our discord.

 

1 minute ago, Fith said:

Oh wait...I have no `config/data` ...Let me create that.....

Read my previous post.

2 minutes ago, saarg said:

Huh? Wsl? If you are not running unraid, this is not the correct place for support.

Containers running on windows isn't something we really support either. We only test on Linux.

So go to our forum or join our discord.

 

I'm on unRaid....I had it setup BEFORE in WSL....I'll try creating that directory...

root@Tower:/mnt/user/appdata/tvheadend# mkdir config
mkdir: cannot create directory ‘config’: File exists
root@Tower:/mnt/user/appdata/tvheadend# 

 

Edited by Fith

I do have a directory called data

root@Tower:/mnt/user/appdata/tvheadend/data# ls -la
total 31044
drwxr-xr-x 1 nobody users       43 Jul  3 10:16 ./
drwxrwxrwx 1 nobody users     4096 Jul  3 11:57 ../
-rw-r--r-- 1 nobody users 31777651 Jul  3 10:16 guide.xml
-rwxr-xr-x 1 nobody users     1099 Jul  3 10:15 tv_grab_file*
root@Tower:/mnt/user/appdata/tvheadend/data#

 

2 minutes ago, Fith said:

I do have a directory called data


root@Tower:/mnt/user/appdata/tvheadend/data# ls -la
total 31044
drwxr-xr-x 1 nobody users       43 Jul  3 10:16 ./
drwxrwxrwx 1 nobody users     4096 Jul  3 11:57 ../
-rw-r--r-- 1 nobody users 31777651 Jul  3 10:16 guide.xml
-rwxr-xr-x 1 nobody users     1099 Jul  3 10:15 tv_grab_file*
root@Tower:/mnt/user/appdata/tvheadend/data#

 

/config/data is inside the container. So the /config folder is the same as /many/user/appdata/tvheadend.

You have to add the guide.xml to that folder and then tvheadend adds the guide to it's internal EPG when the tv_grab_file grabber is set to run. You also have to enable it in tvheadend.

Did you copy the tv_grab_file in the data folder? That is not needed there.

4 minutes ago, saarg said:

/config/data is inside the container. So the /config folder is the same as /many/user/appdata/tvheadend.

You have to add the guide.xml to that folder and then tvheadend adds the guide to it's internal EPG when the tv_grab_file grabber is set to run. You also have to enable it in tvheadend.

Did you copy the tv_grab_file in the data folder? That is not needed there.

Yea, That's one i have edited with a curl address for EPG that I use......One sec, I'll check the container

root@6cdb21ab5d3b:/config/data# ls -la
total 31044
drwxr-xr-x 1 abc abc       43 Jul  3 10:16 .
drwxrwxrwx 1 abc abc     4096 Jul  3 11:57 ..
-rw-r--r-- 1 abc abc 31777651 Jul  3 10:16 guide.xml
-rwxr-xr-x 1 abc abc     1099 Jul  3 10:15 tv_grab_file

yea, it's in there too...just not showing in TVH...I've restarted 30-40 times already :(

Edited by Fith

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.