Firmware 20250506

[Billi23]

Did you run a new channel scan? Such is required for it to get the values (or at least it was when first came out)

Twice.
Once before and once after turning on Early access to features

[nickk]

Signal strength/quality information is generated during a physical channel scan (antenna)... it isn't generated from a CableCARD channel scan.

In theory it could be, it is just signal usually isn't an issue with cable and you don't need to disable channels based on signal quality.

[mooninite]

On my HDHR5-4K I do not see any signal strength on the channel line-up page. I have rescanned channels a few times. Nothing different. The device still works as expected otherwise. Am I missing something?

[Cabal]

On my HDHR5-4K I do not see any signal strength on the channel line-up page. I have rescanned channels a few times. Nothing different. The device still works as expected otherwise. Am I missing something?

Are you looking in the HDHomeRun app or on the device's web page? It's only in the app.

[signcarver]

Not only in the app... as it is where the app gets the channel lineup info from... the lineup.json

[mooninite]

I was looking on the device web page. I do not use the app.

I do see the signal data in the .json output. Thanks!

[randommike]

Changelog posted

Thank you for the update.

Upgraded my device just a little while ago and so far, so good. Cheers!

[Frostyfruit]

Hi all,

I'm having trouble since upgrading to this firmware with K**i finding the hdhomerun connect Quatro with the Hdhomerun add-on over VPN. It previously did work fine, so would there be anything in this firmware that would pose an issue for my device to be found?

Works fine over wifi locally with the same K**i setup.

Thanks

Frosty.

[signcarver]

Unless you were on extremely old firmware (>2years) or something else changed in you internet setup regarding ipv6 (even from your isp) there shouldn't be any such issue. Though I could be wrong, I don't think the k addon ever supported the discovery from https://ipv6-api.hdhomerun.com/discover when they separated such over 2 years ago and that would change with firmware from the past few years or if they now are connecting to SD through ipv6 (primes and legacy equipment still connect through ipv4 as they don't support ipv6, others will only show up at the ipv4 site (which the older links such as my.hdhomerun.com/discover not specifying ip version redirect to)

Also such discovery requires client device and hdhr connecting to SD from same public ip address (if outside your home your client must do internet requests through the vpn connection to your home network so the request for http discovery comes from the same place. Other changes such as NAT by your isp, or vpn connection to internet may also affect such. What client and vpn are you using to connect (i.e. Android typically won't use correct mode to allow local broadcast discovery, and many others simply won't pass such without configuration, but the addon can be set to use http discovery provided the request to SD is from the same public ip).

Another possible change specific to latest firmware if upnp discovery is used (which I dont believe the addon uses) is that only the primary ipv4 and ipv6 addresses get advertised so the link local ones don't and perhaps you had something that those link local addresses were needed.

[Frostyfruit]

Hi,

Thanks for the reply. I am using a VPN Tap configuration using the Android version of 'VPN Client Pro' that applies the VPN to the same LAN as to what the HDhomerun is on. While the VPN is connected I can via web browser still populate the Device configuration page by entering its IP address in the browser. So seems something has changed with device discovery via the various apps while using the VPN. Not sure if there's some routing I should try set up within the VPN.
Regards,
Frosty