HDHomerun apps not tuning in a channel

[wsuetholz]

Hello,

I have some older HDHR3-US devices and one HDHR5-4US.

The HDHomerun app on the Firestick, Windows and Mac have not ever worked for the older units, which is OK I suppose. But, the HDHR5-4US used to work fine.
Recently the apps just show a blank screen after I select a channel from the guide. In order to see if this was a firestick app issue I installed the Mac version of the application and it does the same thing!

I tested from Linux using VLC and I am able to use the url's to open a network stream and view the content from the tuner.

While exploring this, I noticed in the devices web page that the tuner never gets assigned when running from the HDHomerun app, but it does get assigned when running from VLC.
I also tested using VLC on the same iMac that I ran the app on and the vlc worked to stream the content and the tuner web page showed another tuner in use.

This is weird, it used to work for me, and it doesn't seem to be Firestick only since the same thing happened with the app on the iMac.

Something else that isn't working anymore, is in Linux I used to be able to run the hdhomerun_config_gui application and it would find all the devices, now it doesn't find any of them.
When I use the command line version hdhomerun_config it also doesn't work unless I specify the IP address, then it reports the correct information.
I checked and adjusted the firewall rules for the UDP port necessary and it still didn't work. (I did remember the reload).

Maybe somebody could have some ideas?

Thank you, Bill

[signcarver]

For the app to work with legacy equipment, the legacy device must be on recent firmware and a scan run from windows setup to inform SD's servers of the lineup (must be from windows) as the legacy devices don't maintain their own lineup.

However discovery must work to obtain the DeviceAuth. What you described of not being seen by hdhomerun_config typically occurs if you are segregating your lan in some manner (different subnets, vlans, ...) a random port will send a udp packet to the broadcast address port 65001 and the reply will be a unicast back to that port that sent the request. Depending on firewall, sometimes it will not associate such as being an established connection since the reply comes from the device's ip not the broadcast address that was "established" (though it should) as a result, you may need to permit traffic from the hdhomerun.

If you are seeing guide, the client found the device but most likely also found a record engine that didn't find the device as it will try to use a record engine to have a buffer. Note the record engine won't work with the legacy devices but in theory the app should eventually use them directly.

[wsuetholz]

Hello,

Thank you for your reply.

Let's ignore the "legacy" devices.. I'm actually thinking of putting them on an isolated switch connected to my MythTV server's second ethernet port to stop them from being discovered in this way.
My MythTV server has been off for the past few months, so it isn't affecting the outcome at the moment. I need to do some work on it in order to have it better handle sharing the HDHR5-4US which
MythTV doesn't really share well.

My network does not have any VLans configured. It is a relatively simple home network, which I haven't changed between when this was working and not working.
I have tested this both with Ethernet and WiFi connected devices and they all seem to be behaving the same.

I don't think that I have any HDHomerun record devices at all. Where is this record engine located?

Does this functionality require the device or the app to "phone home" to Silicon Dust?

I am seeing the guide in the app on the Firestick and the iMac. I haven't tested on Windows yet.

Thanks again!
Bill

[signcarver]

Sometimes during the windows or mac instalation it will install and turn on a record engine so unless you set such up on a linux machine or nas it would probably be on that if such exists. For troubleshooting i would probably remove the legacy devices as if they had ever been setup from a windows machine they could be providing enough to pull in the lineup.

In the app I would also check what devices it detects... the devices, the engine, and the clients all check in with SD's servers and you may find them by going to both ipv6-api.hdhomerun.com and it's ipv4 counterpart (typically modern devices and engines will show up at the ipv6 site and the legacy at ipv4 but that depends on how they were able to reach SD. Also the app will try to connect via ipv6 to the tuner/engine if such is available and sometimes that was overlooked in firewall settings. For me ipv6 caused issues for my vpn as it had no trouble with discovery but then sent future unicast requests out to the cloud through the vpn connection while if ipv6 was disabled it played nice with local traffic staying local.

[NedS]

As a test, unplug the two older DUAL units and leave just the 10770C53 unit connected, then see if the HDHomeRun app can play back the channel.