HDHRs no longer seen by server

My server updated to 2024.09.10.2115 last night (I'm on stable), and my 2 HDHRs are no longer showing in available sources, even after a manual scan. They're still accessible on the network, and the Channels app can use them directly, but the DVR doesn't see them. I'm running in docker (and have been for over a year without issue) and haven't changed anything in the config. I also tried power cycling the tuners and my network hardware, and down-and-up'd the container as well. The only thing I haven't tried is adding the tuners manually, because I've never had to do that and would like to figure out what's up.

I also noticed there's no version history up for 2024.09.10.2115 yet. Any chance this wasn't an intentional push?

Edit: Sent server diagnostics: 90a59a8c-593f-44ce-ba60-e921325fcb68

Release notes will be up shortly.

Can you ping the IP of the HDHRs?

Yep, nothing seems to be blocked as far as I can tell.

Can you add that IP into the dvr under add source

Yep that works, guess I'm leaving that in place now. If nobody else is seeing this I have to assume something has gone wonky on my LAN :man_shrugging:

Feature request: Support DNS name for HDHR tuner address (assuming it's unsupported because if I enter anything besides an IP address the dialog just immediately disappears and nothing seems to happen)

2 Likes

Using host, or bridge mode network?
If using host mode, it should see the HDHR, using bridge mode it will not.

Yes, definitely host which is why this is so weird (as it's been working fine for over a year)

Had no problems with my HDMR after updating to this version using the package on Synology NAS

1 Like

Some questions to ask yourself.
Are the DVR Server and HDHR on the same switch?
Same LAN segment?
Same subnet?
Are you using VLAN's?
Are your netmasks set correctly?
Does the HDHR have a reserved DHCP IP address?
Is your LAN setup for IPv6 or IPv4 only?
Anything on your network that would block UDP discovery packets on the same subnet/segment?

Same switch, segment, and subnet. Using VLANs but only for IOT devices. Netmasks correct, HDHRs using reserved DHCP, LAN using both IPv6 & 4. Discovery doesn't appear to be a problem for other devices (chromecasts & apple TVs) but I'm not sure if they use the same method of discovery as the HDHRs. Regardless I ended up specifying the IPs on the Channels server and it's been fine since. Just weird that it happened exactly when the server was updated.