Channels DVR does not discover change in HDHomeRun IP address

[hider]

Yesterday Channels DVR failed to record a scheduled program as it was trying to access HDHomeRun 10A2CCE9 using the wrong IP address of 192.168.0.68.

A few days ago we had a power outage late at night. After power was restored 2 of my 3 HDHomeRuns acquired new IP address. In this case 10A2CCE9 went from 192.168.0.68 to 192.168.0.146.

Bug 1: It would appear that Channels DVR did not send out a HDHomeRun discover request to verify that it was using the correct IP address for 10A2CCE9.

In trying to correct this I used the dashboard (port 8089) to try and get the right IP addresses assigned. I did a "scan network" this did not fix the IP addresses.

Bug 2: It would appear that "scan network" does not check the IP addresses returned by HDHomeRun discover with the ones it already has.

I had to go in and use "Add Source" > "HDHomeRun Device" for each tuner before it got corrected.

DVR server 2022.09.17.0215 on Synology DS1621+.

[tmm1]

Scan network sends out a HDHR discovery ping. That also happens automatically every few hours.

If that's not working, there must be something on your network or NAS that's interfering. I'm not sure what it could be, because I tried the same thing here and it picks up IP changes.

Either way, the best solution is to setup your router with static DHCP reservations so your HDHRs always get the same IPs

[hider]

I found the problem. The LAN subnet mask on the router was changed. Channels DVR continued to send out discover requests to 192.168.0.255 which was no longer the broadcast address for the LAN and consequently got no responses.

I think the dashboard (port 8089) should flag a configured HDHomeRun as unavailable if there is no response to discover.

I noticed that Silicon Dust utilities use 255.255.255.255 for the discover broadcast which was unaffected by the subnet change.

Anyway everything is working again now.