The only way that I was able to get this working was to have the app request a pcap from a DEV tuner on the LAN once the app discovered the channel lineup, parse the saved pcap, extract the ALP UDP payloads, parse the LCT packets, reassemble each object, decompress if using gzip, save the images ...

If you go with the Shaw Butte location be sure your lease agreement covers whatever you intend to do now and in the future. The reason we killed the FSN up there was that the tower owner decided that even though we only had one transmitter operating on one channel, they decided that we owed them ...

nickk wrote: Sat Mar 14, 2026 10:24 pm Would you be open to committing the project to github?

Then we can link to it from our Linux page.

Nick

I've only ever used GitHub for downloading, but I have no objection.

- Trip

Something that I would find very useful would be a web API that could return the PLP Info and (if Dev) L1 string. My immediate thought would be something like:

http://hdhomerun.local:5004/auto/ch33p0p1p16?duration=15&format=plpinfo

And if not already tuned to those PLPs, it could tune them and ...

Trip, have you tuned PLP0 via the CLI and set the target to forward and watched either the network rate in Config GUI or monitored via Wireshark to see if there's anything actually on there?

hdhomerun_config xxxxxxxx set /tuner0/channel atsc3:25:0
hdhomerun_config xxxxxxxx set /tuner0/target ...

Thanks for the feedback!

I added some PLP info for the ATSC 3.0 channels and maybe fixed the issue with no info being displayed. I was not able to consistently reproduce that one as described. Maybe it was due to longer signal lock times or something, so it should be more robust from that ...

I have Android devices that work in the Android ecosystem, so I have been missing the HDHomeRun Signal app. I vibe coded the following to fill the gap. Run it in docker somewhere on your network and then you can tune from anywhere.

https://github.com/Petelombardo/hdhomerunsignal/blob/main/README ...

The "Signal Quality" meter on hdhomerun_config_gui does bounce between 0 and 100% (mostly at 0%), but the stream is still working.


So in my closet I have an HDHR Connect 4K, and just yesterday I got an HDHR Flex 4K. Both are running the newest Dev firmware, both are unable to lock plp16 for ...

So I got an answer back from someone involved in WNUV:

"CTI can be used in multi-PLP TDM operations as long as any given CDP only utilizes a single core PLP. In this case, we have a CDP, BPS, that utilizes just PLP 16, another set of CDPs for the mobile/BEST services which utilize just PLP0 (core ...

This is just a guess, but I think some of these PLP 16 configurations are out of spec. Specifically, when there are two PLPs in a subframe using the CTI interleaver.

If you look at section 7.1.1 of A/322, it talks about what interleavers can be used. Unless you're using LDM, if there are multiple ...

Version 0.8.6: https://www.rabbitears.info/dl/hdhomeru ... _0.8.6.zip

The PCAP capture function for Dev models now captures ALP-PCAP instead of IPv4-PCAP.

- Trip

Nick,

I'm having a minor issue with a local 3.0 signal. I have two signals near me running 3.0 with an extremely robust BPS PLP (PLP16) and they behave very differently.

16: sfi=0 mod=qpsk cod=2/15 layer=core ti=cti lls=0 lock=1
-> Required SNR: AWGN -6.23 to -5.55 dB, Rayleigh -5.72 to -5.06 dB ...

The latest 0.8.5 zip file includes the libhdhomerun source code. Just wondering if that was intentional. Might overwrite something unintentionally when unzipping.

Otherwise it compiles, looks, and runs fine on Debian 11 with a flex4k. It "just works" so nothing else really to comment on ...

Had to fix another regression that prevented the l1detail from being parsed.

https://www.rabbitears.info/dl/hdhomeru ... _0.8.5.zip

- Trip

Rapid new update.

https://www.rabbitears.info/dl/hdhomeru ... _0.8.4.zip

Added the HDHR firmware version number to the ATSC 3.0 details screen. No other changes.

- Trip