tvheadend: Please add hdhomerun support

[sphr2k]

@sairon
Could you enable "hdhomerun_client" build option, so that we can use HDHomeRun network tuners on Turris Omnia? I'm not sure why the feature is still disabled by default, since it's been working reliably for a while now.

[ajsomething]

I agree to this and am bumping. routers have tons of bandwidth available to use the HDHomeRun tuners and this would increase the popularity of dd-wrt as it eliminates an entire piece of equipment.

If someone can compile this special for me I will compensate them for their time.

its been 2 years, can we get some love?

[sjjgo]

This is fixed in this PR: #6386

It's turned off by default, but can be added from the build configuration menu.

[neheb]

ping @BKPepe I think you guys have this package updated?

[BKPepe]

Yes, we do, but I don't have HDHomeRun network tuner, so I can not test it on that device. But before doing that, I will need to add two packages for that. However, I don't want to promise anything, but I will try to look at it and send it here as I am using it almost on daily basis.

[walterav1984]

Can this still be enabled by default for 21.02 release?

[M95D]

ping @BKPepe I think you guys have this package updated?

Updated to v4.2.8 with significant changes in OpenWRT package features. See #16475.
(v4.3.0 appears to be significantly older than v4.2.8.)

HDHomeRun is enabled by default, but I didn't test it. I don't have the hardware.
Please test and close the issue if there are no problems.

[walterav1984]

Nice I saw that P.R. this weekend and noticed the HDHomerun was set on default.

Just testing snapshot OpenWrt SNAPSHOT, r17454-f08b76b32f on a Raspberry Pi and the HDhomerun HDHR3-EU is detected as tuner in "Configuration>DVB Inputs>Tv adapters" section!

opkg install tvheadend
Installing tvheadend (4.2.8-2) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/arm_arm1176jzf-s_vfp/packages/tvheadend_4.2.8-2_arm_arm1176jzf-s_vfp.ipk
Installing libopenssl1.1 (1.1.1l-1) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/arm_arm1176jzf-s_vfp/base/libopenssl1.1_1.1.1l-1_arm_arm1176jzf-s_vfp.ipk
Installing zlib (1.2.11-3) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/arm_arm1176jzf-s_vfp/base/zlib_1.2.11-3_arm_arm1176jzf-s_vfp.ipk
Installing libffi (3.4.2-1) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/arm_arm1176jzf-s_vfp/packages/libffi_3.4.2-1_arm_arm1176jzf-s_vfp.ipk
Configuring libffi.
Configuring libopenssl1.1.
Configuring zlib.
Configuring tvheadend.

However it was detected as DVB-T, but after setting it to DVB-C both tuners are now scanning and operational tested both on multiple muxes.

Questions:
Is it correct that the tvheadend webinterface has no username/password setup, pressing default login just signs me in?

Is satip-client in this setup functional since it won't detect the Fritzbox 6490 Satip server, this tuner is however detected on other machines/architectures running tvheadend? Or does it need extra upnp/avahi packages to operate? On other tvheadend instances it helps to discover by going in the tvheadend webinterface to the button "Configuration>General>SATIP-Server>Discover SATIP-Servers" but this also doesn't help.

Side note about the raspberry pi 1 512MB model, its ethernet port won't come up after it has been disconnected... probably unrelated to this.

UPDATE:
Just noticed that the OpenWrt "libavahi-client" package is not installed while installing TvHeadend and I see the avahi support to be set as default 'n' in Config.in.

Im not sure if the function of this package is announcing Tvheadend features on the network or for listening which services are broadcasted by other devices like satip servers.

In my memory I got satip and hdhomerun running 2 years ago by manually compiling tvheadend 4.0.x for openwrt in early 18.07.x or even 17.x lede branch on a device I don't own anymore.

UPDATE2:
If I know howto add runtime arguments to TvHeadend in OpenWrt via /etc/init.d/tvheadend or /etc/config/tvheadend I might test satip client without avahi/SSDP?
TVH_ARGS="--satip_xml http://satipserverip:8080/description.xml"
https://tvheadend.org/boards/5/topics/14189?r=14337

UPDATE3:
Adding "--satip_xml http://satipserverip:49000/satipdesc.xml" to /etc/init.d/tvheadend at end of line 83 made the Fritzbox satip work!

UPDATE4:
It is not needed to have package "libavahi-client" installed nor tvheadend compiled with avahi support to have satip client working! Just run following command and both satip servers Fritzbox dvb-c and Octopus-Net dvb-s2 show up in tvheadend webinterface after pressing "Configuration>General>SATIP-Server>Discover SATIP-Servers".

ip route add 239.255.255.250/32 dev eth0

Credit goes to Roland.A from the TvHeadend forum
Excuse for going a little bit offtopic, I will open a seperate issue #16500 for tvheadend package how the SSDP broadcast/multicast should be handled to get satip-client working out of the box.

[walterav1984]

Feel free @sphr2k to close this issue since HDHomerun support has been verified using a HDHR3-EU using DVB-C with this commit #16475 multiple tuners and multiple muxes.

[M95D]

Questions:
Is it correct that the tvheadend webinterface has no username/password setup, pressing default login just signs me in?

Yes. That is the default after (re)install. It creates a default user only after install. After that, the user can set up accounts from web interface.

Let's discuss SAT>IP in the other issue you opened. Please close this one.

[sphr2k]

Thanks for adding.

[walterav1984]

@M95D will #16475 also be backported to the 21-02 branch or is more testing required?

[M95D]

Is this my decision? I never did a backport before.
Since this was my first significant pull request, I would feel more comfortable if more people test it.