HDHomeRun tuners not found

[zeppelin58]

I've installed the latest amd64 docker image and am not able to get it to find my hdhomerun devices.

I ran it with:

sudo docker run -d \
--volume /home/jim/nextpvr/config:/config \
--volume /home/jim/nextpvr/videos:/recordings \
--volume /home/jim/nextpvr/videos:/buffer \
--publish 8866:8866 \
--env HOST_IP=10.10.10.99 \
--publish 8020-8030:8020-8030/udp \
nextpvr/nextpvr_amd64:latest

When I log into the web gui (10.10.10.99:8866) under settings/devices it only shows IPTV. I can rescan but still nothing.

I exec'd a shell in the container and ran 'hdhomerun_config discover' and it returned 'no devices found'.

I stopped the container and ran it with:

sudo docker run -d \
--volume /home/jim/nextpvr/config:/config \
--volume /home/jim/nextpvr/videos:/recordings \
--volume /home/jim/nextpvr/videos:/buffer \
--network=host \
nextpvr/nextpvr_amd64:latest

Still nothing under devices but when I run 'hdhomerun_config' in the container it finds both my hdhomerun tuners.

I've attached the logs. Any idea what I am doing wrong?

My host running Ubuntu 18.04 if that matters.

[sub]

If you go to http://ipv4-api.hdhomerun.com/discover in a browser, is your HDHomeRun listed?

Is it an older legacy HDHR device?

[zeppelin58]

No, they are not listed. I have 2 devices; a Quatro Model HDHR5-4US I just bought and an Extend Model HDTC-2US I've had for years. These both show up in the Windows versions (v4 and v5).

[sub]

If you log into the web app on those HDHR, and do a scan, then try that url again, do they show up?

[zeppelin58]

They do not. Could this be because I am using an AT&T cellular for my internet? I'm in a double NAT situation. I'm in a very rural area and my choices are satellite or cellular.

[sub]

Yeah, it'll be something to do with that.

Basically the standard way of finding HDHR devices is by requesting the list from http://ipv4-api.hdhomerun.com/discover. There is some fallback logic, which uses a UDP broadcast to find them, but unfortunately that is currently limited to 192.168.1.x subnets (which is default for the majority of home networks). I can look into expanding that to detect the local broadcast address, rather than assuming 192.168.1.255.

[zeppelin58]

Got it. If I install it on my ubuntu server does it have the same limitation? If so, I guess I can either go back to windows version or change my subnet.

Thanks for your help on this.

[mvallevand]

The extend shouldn't be legacy and I didn't think the Quattro was either. Have you set them up with the latest silicon dust software and firmware? If you browse to their direct urls can you see lineups?

Martin

[zeppelin58]

Firmware is up to date and I see lineups. I think this is a combination of my double NAT internet and my home 10.10.10.xxx subnet.

[mvallevand]

If hdhomerun_config finds them then sub could use that info to load the lineups.

Martin