Tvheadend

Thomas Pfister wrote:

I am aware of the "satip_xml" command line argument, but it's no solution for me (KATHREIN EXIP 414E doesn't have such an XML file).

It would be really great if this could be done! :-)

Hi,

As described in http://www.satip.info/products/sat%3Eip%20servers
this device is a SAT>IP CERTIFIED SERVER! Therefore, it must publish the XML file.

I feel you don't know the correct URL of the XML file. Please, use one SSDP discovery tool for get the message from this server.

Futhermore, it's very strange that TVH doesn't see your device. Please, check if another SAT>IP client (like the free DVBSatIP for Windows) can discover your server.

Thanks! ;-)

Mono Polimorph wrote:

I feel you don't know the correct URL of the XML file. Please, use one SSDP discovery tool for get the message from this server.

This is obviously true. I googled but I didn't find the XML-Path for my Device. I wasn't aware it's that easy to get it! ;-)

I installed gupnp-tools and found the path. Just FTR (especially for the guys googling the XML-File of KATHREIN EXIP 414E), my /etc/default/tvheadend looks now like this:

TVH_ARGS="--satip_xml http://192.168.0.2/rootDescr"

One other question (I had this issue before and it didn't go away with the static IP):
After a reboot, the server is obviously not found automatically, I have to click "Discover SAT>IP-Servers" once. Then they appear at "DVB-Inputs". Is there any chance this could happen automatically? ;-)

Thomas Pfister wrote:

I installed gupnp-tools and found the path.

This is the correct way for discovering the XML URL!

One other question (I had this issue before and it didn't go away with the static IP):
After a reboot, the server is obviously not found automatically, I have to click "Discover SAT>IP-Servers" once. Then they appear at "DVB-Inputs". Is there any chance this could happen automatically? ;-)

I don't know if I understand the problem:

- If you reboot the SAT>IP server and you lose it in the TVH configuration, then the problem is with the IP address. You need to fix the IP address in your DHCP server (in your LAN router), or set it manually in the Karhrein.

- If you reboot the server where the TVH is running, or you restart the TVH instance, and you lose the SAT>IP device, then the problem is with the TVH_ARGS argument. You need to start the TVH binary all the times with this parameter. So, check your init.d configuration files.

I hope this helps!

It appears that the network is not ready when tvheadend starts, so the first discovery fails (TVH does the SAT>IP client discovery after start). You should fix your network settings or try to delay the tvheadend start until the network is functional.

I think there is no way to speed the network up. It's directly connected to the SAT>IP-Server and both use static IPs, I don't see any way to speed that up. However delaying the tvh-start looks like a solution (some seconds should suffice...) - is there a "correct" way to do this? ;-)

Jaroslav Kysela wrote:

It appears that the network is not ready when tvheadend starts, so the first discovery fails (TVH does the SAT>IP client discovery after start). You should fix your network settings or try to delay the tvheadend start until the network is functional.

the possibility to easy delay the start was removed here https://github.com/tvheadend/tvheadend/commit/c6f8e600535bdc78f2dd7833375a19a7ef9ed336
is there an proper alternative to delay it ?

C vH wrote:

Jaroslav Kysela wrote:

It appears that the network is not ready when tvheadend starts, so the first discovery fails (TVH does the SAT>IP client discovery after start). You should fix your network settings or try to delay the tvheadend start until the network is functional.

the possibility to easy delay the start was removed here https://github.com/tvheadend/tvheadend/commit/c6f8e600535bdc78f2dd7833375a19a7ef9ed336
is there an proper alternative to delay it ?

+1

I'm not author of this commit and I barely maintain the debian stuff.

Thomas Pfister wrote:

I think there is no way to speed the network up. It's directly connected to the SAT>IP-Server and both use static IPs, I don't see any way to speed that up. However delaying the tvh-start looks like a solution (some seconds should suffice...) - is there a "correct" way to do this? ;-)

Even if you have static IPs, the discovery of the SAT>IP server is done via UPnP broadcast to 239.255.255.250 (if you're not using --satip_xml).

I have the same device (Kathrein EXIP414/E) and noticed that on one TVheadend Pi it found it during installation (single network interface), on the other one it did not (several virtual interfaces). Turned out, that if you more than one network interface and the Kathrein server happens to be on the interface with not the default route, and if you do not have a route to 239.255.255.250/32 to the correct interface then, the UPnp discovery is sent to the wrong device.

Maybe that is also the problem for you. In my case, the Pi with the "internet interface" was not able to detect any UPnP device at all, because the LAN subnet obviously is different from the UPnP target address and the default route points to the internet. Just my 2cents.

Roland A. wrote:

Maybe that is also the problem for you. In my case, the Pi with the "internet interface" was not able to detect any UPnP device at all, because the LAN subnet obviously is different from the UPnP target address and the default route points to the internet. Just my 2cents.

I forgot to mention that at least Raspian Jessie is not adding a route to that specific address by default to the physical NIC. Ubuntu does and is not affected.

FYI: Added a sleep 5 to /etc/init.d/tvheadend. Restarted the server yesterday after a long time and it worked.
No best practice, but works.