TVHeadEnd PVR Docker for use with Kodi

[ChaOConnor]

I'm trying to find a docker that will act as the backend for a Kodi PVR.  I see someone tried a Tvheadend Docker but haven't had much success with it.  Has anyone else found or considered a docker for a compatible backend for Kodi?  Thanks!

[sparklyballs]

I'm trying to find a docker that will act as the backend for a Kodi PVR.  I see someone tried a Tvheadend Docker but haven't had much success with it.  Has anyone else found or considered a docker for a compatible backend for Kodi?  Thanks!

 

http://lime-technology.com/forum/index.php?topic=37375.msg345434#msg345434

 

mentions something about a --device mapping in docker. this would be something required for pvr etc...

[saarg]

I have made a TVHeadend docker which are available on the docker hub. I have it working here, but I use IPTV and have not tried to pass through a DVB card. Transcoding is disabled beacause the ppa of tvheadend doesn't build the deb packages with transcoding enabled.

You might be able to use your HDHomerun with my container as I saw there was mention of someone adding the device without installing drivers on the TVHeadend forum here: https://tvheadend.org/boards/5/topics/14377?r=14703#message-14703

I do not have a HDHomerun, so I have no possibilities to test it.

 

My docker is not 100% ready, but if you want to try it you can find it here: https://registry.hub.docker.com/u/tobbenb/tvheadend-unstable/

You will then have to add it to the docker page in advanced mode.

[ChaOConnor]

I have made a TVHeadend docker which are available on the docker hub. I have it working here, but I use IPTV and have not tried to pass through a DVB card. Transcoding is disabled beacause the ppa of tvheadend doesn't build the deb packages with transcoding enabled.

You might be able to use your HDHomerun with my container as I saw there was mention of someone adding the device without installing drivers on the TVHeadend forum here: https://tvheadend.org/boards/5/topics/14377?r=14703#message-14703

I do not have a HDHomerun, so I have no possibilities to test it.

 

My docker is not 100% ready, but if you want to try it you can find it here: https://registry.hub.docker.com/u/tobbenb/tvheadend-unstable/

You will then have to add it to the docker page in advanced mode.

 

Thanks, I'll give it a shot tonight!

 

Thanks, i'll give it a shot tonight!

[callummc]

Just gave this a crack and it doesn't seem to like the username / password (admin/password)?

[saarg]

Sorry about that. Don't know what went wrong when the image was built, but here is what you can do:

In the config folder for tvheadend you have to make a file called superuser and add this

{
"username": "admin",
"password": "password"
}

After you Stop/start the container, you should be able to log in.

After you log in you should also go to access control and make a new admin user. After you have verified you can log in with the new user, you can delete the superuser file.

[callummc]

Ok - it seems that I can now get to the TVHeadEnd UI, which is a great step forward

 

But how do I configure my HDHomeRun's here?  I'm not seeing anything under Configuration --> TV Inputs --> TV Adaptors.  I have two HDHomeRun devices on my network, but they don't seem to be appearing and I don't have an option to "add" them?

 

P.S.  You should consider creating a Docker template repo for this, adding an icon and configuring the "WebUI" link to open to the appropriate page

 

 

[saarg]

Have you updated the tvheadend-unstable container? Push the Reload info button on the docker page and see if it needs an update.

Tvheadend is now compiled with HDHomerun support directly and as I understand it you should not need to do anything outside of Tvheadend to get it to work. But... I don't have a HDHomerun, so I might be wrong.

The HDHomerun should show up in the TV Adapters list.

 

I will shortly make the template repo available, but nothing is released until everything works.

You might find the templates if you follow the links from the docker hub But do not use the stable build of TVHeadend as it's not working.

[callummc]

Yeah - I've just updated the container and still no dice

 

From what I understand, TVHeadEnd should show the adaptors... *but* it requires the libhdhomerun software to be installed first.

 

These are the posts that I've read up on :

 

https://tvheadend.org/projects/tvheadend/wiki/HDHomerun/5

https://tvheadend.org/boards/4/topics/14822

 

Any chance that you could try adding the drivers to the docker image?

 

[Yoshiofthewire]

I tried to create TVHdeadend with the following code

docker run -d -–name=tvheadend -v /mnt/cache/docker:/config -v /mnt/user/RecordedTV:/recordings -v /etc/localtime:/etc/localtime:ro -p 9981:9981 -p 9982:9982 -p 5004:5004 tobbenb/tvheadend-unstable

I can see the container running, but I am unable to connect to the web interface.

The page never loads.  What did I do wrong?

[callummc]

I found that it didn't work for me initially either.

 

I was clicking on the Docker Icon and selecting "WebUI" - I suspect that you might be doing the same thing.

 

Try going to http://[YourServerIP]:9981

 

If this works and you can see the TVHeadEnd GUI, then you can make a simple adjustment to your docker container config to set it up correctly.

 

To adjust the container config :

 

• Select the "Docker" tab in the unRAID GUI, then click on the TVHeadEnd icon, then select the "Edit" option from the drop down menu.
  
• A modal window will then open showing the docker "container config".
  
• Move your mouse to the top right hand corner of the modal window, a button labelled "advanced" will appear, allowing you to click on it.
  
• Once the "advanced" button has been clicked, you will see additional fields in the "container config" window which were previously hidden.
  
• In the field labelled "WebUI", add : http://[YourServerIP]:9981
  
• In the field labelled "Icon", add : https://avatars0.githubusercontent.com/u/1908588?v=3&s=400 (This will add a spiffy icon)
  
• Click "Apply"
  

 

Let me know if that works for you

 

 

[callummc]

ChaOConnor, as the owner of this thread, are you able to change it's title?

 

If so, would you consider changing it to "TVHeadEnd PVR Docker for use with Kodi"?

 

It might make it easier for others to find the thread

[saarg]

I tried to create TVHdeadend with the following code

docker run -d -–name=tvheadend -v /mnt/cache/docker:/config -v /mnt/user/RecordedTV:/recordings -v /etc/localtime:/etc/localtime:ro -p 9981:9981 -p 9982:9982 -p 5004:5004 tobbenb/tvheadend-unstable

I can see the container running, but I am unable to connect to the web interface.

The page never loads.  What did I do wrong?

 

You are using unraid_IP:9981?

I would just delete the container and re-add it from the docker tab in Unraid GUI.

[saarg]

Yeah - I've just updated the container and still no dice

 

From what I understand, TVHeadEnd should show the adaptors... *but* it requires the libhdhomerun software to be installed first.

 

These are the posts that I've read up on :

 

https://tvheadend.org/projects/tvheadend/wiki/HDHomerun/5

https://tvheadend.org/boards/4/topics/14822

 

Any chance that you could try adding the drivers to the docker image?

 

It should work according to this report in my repository thread

 

 

  Drivers for hdhomerun are in the docker. Tvheadend- stable did not load for me but Tvheadend-Unstable did. My hdhomerun prime shows up. I can not answer much more because I have never used the program and have to learn how to set it up.  The modified unraid files are only needed to use hardware that requires kernel drivers like a tuner card in your unraid pc.

 

Reed.

 

Do you run the container as bridge or host networking?

If I have understood how HDHomerun works, you connect to it through the network?

[callummc]

Yes - I discovered that you have the drivers installed after checking your docker file in github.

 

Your question was on the right path.  As the HDHomeRun tuner is a network device, it connects on a specific port (although I'm not sure exactly which one).  I switched the docker app to "host" mode, which then enabled it to recognise the HDHomeRun tuners 

 

I should probably work out which port it connects on and switch it back to bridge mode at some point. Right now I'm busy trying to work out the WebGrab++ config to see if I can get TVHeadEnd up and running 

 

For the moment, I can confirm it recognises the HDHomeRun tuners and enables a channel / mux scan to be completed. 

 

I'll post more details once I have it all up and running

[saarg]

I have the same problem myself with IPTV. If I map the correct port for multicast and set the container to use bridged network, it does not want to play nice 

But I think that has to do with limitations with docker itself and multicast.

 

From Silicon Dust's homepage it says that you have to open port 65001/udp for the HDHomerun to be discovered.

So try adding that port and choose udp in the configuration for the container.

 

[jtenniswood]

Its probably not going to work in bridged mode, because the hdhomeruns don't show up when you have a different subnet, which is what's happening in docker's network stack. Annoying as I'm looking to do the same thing.

[CHBMB]

Its probably not going to work in bridged mode, because the hdhomeruns don't show up when you have a different subnet, which is what's happening in docker's network stack. Annoying as I'm looking to do the same thing.

You know this thread is over a year old right?

 

May be better posting in the TVHeadEnd support thread.