HDHome Run getting lost

[MarkTheNewf 4]

I did get another router in the mix and set Starlink in bypass mode and now it seems to work.  I didn't argue or complain much about it as I was planning to get a new router and mesh set up in the near future.

As of now, reserving addresses for the HTPC and the network tuner seems to have fixed the issue, but I can't confirm 100% since it's only been a bit over a week.

Yes, fanboys can be quite toxic.  I'm for the software but not for making excuses for it.  That stated, Emby seems to be pretty stable and there appears to be efforts to advance it as indicated by the other fixes and new Apps.  However, me having to buy new hardware to get it to play nice in the network that is already working just fine is a bit off-putting.
 

[revengineer 142]

16 hours ago, MarkTheNewf said:

Yes, fanboys can be quite toxic.  I'm for the software but not for making excuses for it.  

This has nothing to do with fanboys. It was simply pointed out that you were asking for software patch to address a niche issue while a standard, commonly-used hardware solution exists. It sounds like you have now implemented this solution and it works well.

I wonder whether you have contacted Silicondust about supporting static IPs for their devices. This seems to be the ideal solution that would not have required additional hardware in your setup. This is also likely easier to robustly implement than software that chases devices around the network.

[Carlo 4560]

It's a shame the HDHRs don't allow a static IP to be set.
It's unfortunate that Starlink doesn't allow picking/setting the IP range to use (in case of conflict) as well as allowing for DHCP reservations for the LAN side.
It's a shame that Starlink doesn't support local name to IP mapping, so devices and equipment can be accessed by name vs IP. This is trivial to do when you can integrate dhcp & dns together. Many home routers do this as a default.

Many of the home 5G plans are the same or worse when it comes to DHCP but even worse as your behind a CG-NAT for IP4 but have fully routable IP6 addresses handed out by DHCP but have no firewall, port mapping or port forwarding control. T-Mobile for example allows setting the SSID and password for 2.4 and 5 WIFI bands and that's the adjustable settings under your control. The newer Sage router/switch/AP/modem adds the ability to scan/set the channel each WIFI band uses as well. T-Mobile does IP4 over IP6 encapsulation which lowers the MTU to 1400ish and has 0 CG-NAT on IP6 but double NAT on IP4

With Starlink, you can get a public IP4 address in your dashboard, (but it's not static) which removes the CG-NT. You can also switch out the Starlink router replacing it with your own adding a lot of additional functionality such as QOS, VPN, Tailscale, traffic shaping, traffic filtering, firewall, port forwarding, DNS & DHCP, optionally WIFI & Mesh as well. You can do this for $35-$100 depending on WIFI & Mesh with higher quality equipment than home routers using Mikrotik routers or router/switches or router/switch/APs. You can't do this with T-Mobile or some other 5G home plans. The closest you can get on T-Mobile is plugging in a router that supports IP6 passthrough but will add a 3rd NAT to IP4. It could also get you other functionality as mentioned above.

Without replacing or adding additional routers you can still fix or work-around IP issues on HDHR which don't allow setting an IP directly. For device similar to an HDHR you could plug the device directly into your Emby server if you have an open Ethernet port or could add a cheap NIC. You could then enable a DHCP server directly on the Emby server running Windows, Linux, Docker, etc bound to only the NIC supporting the device. The NIC would use a static IP on it's own LAN segment and assign a reserved IP to the device. If you have a smart switch supporting VLAN use a 2nd NIC wouldn't be needed as the DHCP server would be assigned to the VLAN created for the device.

If the only device giving you an issue switching IPs once in a while, then it's even easier.  Don't use an IP when setting up the HDHR in Emby.  Instead use the device ID.
You can install hdhomerun_config on Windows, Linux, Mac, BSD & Solaris OSes. Once installed you can use 

hdhomerun_config discover

To find all HDHRs are the network getting their IIP as well as ID. From that point on you can use IP or device ID to talk to the device.

hdhomerun_config <device id> get help
hdhomerun_config <ip address> get help

This works for any of the web/http endpoints as well as from the command line using hdhomerun_config to access the web/http end points.

Read more about using the device ID instead of IP here: https://info.hdhomerun.com/info/hdhomerun_config

Edited December 30, 2024 by Carlo

[justinrh 259]

4 hours ago, Carlo said:

  Do use an IP when setting up the HDHR in Emby

Did you mean to say 'do not use'?

[Carlo 4560]

16 hours ago, justinrh said:

Did you mean to say 'do not use'?

Yes, Don't use an IP address, but instead use the device id.

I've had 3 Prime & 2 Quatro devices setup this way that have been moved to these different address spaces 192.168.0.1, 192,168,1.1, 192.168.12.1, 10.0.0.1 10,69.0.1 without me having to do anything for Emby to use the devices as usual.

[justinrh 259]

7 hours ago, Carlo said:

Yes, Don't use an IP address, but instead use the device id.

You mean you can put the device ID in here?