Not seen by my.hdhomerun.com or Mac app

ATSC 3.0 Forum
Post Reply
bap
Posts: 18
Joined: Tue Jan 13, 2004 8:35 pm
Device ID: 1080B35E
x 1

Not seen by my.hdhomerun.com or Mac app

Post by bap »

I just received my HDHR5-4K and was able to update the firmware manually. However when I go to http://my.hdhomerun.com/ it says no devices were found. I've tried installing the Mac app on a few different Macs on our network and they also just pop up a message stating "No devices detected". The HDHR5 is on the same network as all the Macs (and all wired connections) so I'm not sure why this doesn't work. If I go to http://<ip_of_HDHR5> I am able to see the GUI for it. I was also able to get it fully configured within Plex by specifying the IP address there as well. So it certainly appears to be working, just not discoverable by anything on my network. How are they detected? Is it a broadcast of some sort, or something else?

Edit: I found something that indicated UDP broadcast on port 65001 is what's used. I'm seeing nothing on that port. I do, however, have another device on my network that broadcasts via UDP port 50222 and listening to that I see the traffic, so it's apparently not an issue with my network, Mac setup, etc.
Last edited by bap on Fri Oct 16, 2020 4:42 pm, edited 1 time in total.

signcarver
Expert
Posts: 9247
Joined: Wed Jan 24, 2007 1:04 am
Device ID: 10802091 131B34B7 13231F92 1070A18E 1073ED6F 15300C36
x 15

Re: Not seen by my.hdhomerun.com or Mac app

Post by signcarver »

Surprised the mac app's aren't seeing it.

The apps use broadcast discovery by sending a UDP packet to the network broadcast address and port 65001. Some routers/firewalls, vpn's, vlans, etc. can cause issue with such discovery.

my.hdhomerun.com uses what is often referred to as http discovery which relies on the device connecting to SD (does so every 8 hours) from the same public ip address that the browser you use connects to my.hdhomerun.com from. A VPN, proxy, ISP changing your public ip, etc can prevent such from working. Additionally the computer/browser may prevent a remote site from accessing content, particularly unsecure content, from a resource on your network. So there is a lot more that can go wrong with such discovery compared to broadcast discovery (assuming everything really is on the same network and not in different broadcast domains).

Have you run a channel scan on the device itself?

bap
Posts: 18
Joined: Tue Jan 13, 2004 8:35 pm
Device ID: 1080B35E
x 1

Re: Not seen by my.hdhomerun.com or Mac app

Post by bap »

A channel scan ran fine and found something like 53 channels. I'm able to watch them through the Plex that I set up.

I just added a note to my original post since I found some other documentation that mentioned UDP port 65001 is what's used. If I use netcat to listen for that traffic I never see anything. I have another device on the same network that broadcasts via UDP port 50222 and netcat sees that traffic fine, so I don't think it's an issue with my network, Mac, etc.

bap
Posts: 18
Joined: Tue Jan 13, 2004 8:35 pm
Device ID: 1080B35E
x 1

Re: Not seen by my.hdhomerun.com or Mac app

Post by bap »

A thought regarding my.hdhomerun.com. When I view the system log of my HDHR I see a lot of instances of this message:
19700101-04:11:12 System: myhdhomerun_sync: webclient error (dns failed)
If the HDHR needs to "phone home" for my.hdhomerun.com to work properly then this may very well be the reason that is failing. If it's unable to resolve DNS for some reason then I can see why that wouldn't work.

bap
Posts: 18
Joined: Tue Jan 13, 2004 8:35 pm
Device ID: 1080B35E
x 1

Re: Not seen by my.hdhomerun.com or Mac app

Post by bap »

Yup, it was a DNS issue for the my.hdhomerun.com issue. I have pi-holes for DNS ad-blocking on my network, and the blocklists I was using have both tuner-api.hdhomerun.com and location-api.hdhomerun.com listed for some reason. I just whitelisted all of *.hdhomerun.com and now my.hdhomerun.com is working. Still not seeing the UDP broadcast though.

NedS
Silicondust
Posts: 1511
Joined: Mon Dec 10, 2018 12:38 pm
x 41

Re: Not seen by my.hdhomerun.com or Mac app

Post by NedS »

bap wrote: Fri Oct 16, 2020 5:14 pm Yup, it was a DNS issue for the my.hdhomerun.com issue. I have pi-holes for DNS ad-blocking on my network, and the blocklists I was using have both tuner-api.hdhomerun.com and location-api.hdhomerun.com listed for some reason. I just whitelisted all of *.hdhomerun.com and now my.hdhomerun.com is working. Still not seeing the UDP broadcast though.
Is that with the default lists? That had happened once before and I was able to contact the maintainer of the list we had gotten on, and they fixed it, but I wonder if it happened again.

bap
Posts: 18
Joined: Tue Jan 13, 2004 8:35 pm
Device ID: 1080B35E
x 1

Re: Not seen by my.hdhomerun.com or Mac app

Post by bap »

These are the pi-hole lists I'm using that they were found in:

Code: Select all

Match found in https://dbl.oisd.nl:
   location-api.hdhomerun.com 
 Match found in https://raw.githubusercontent.com/Perflyst/PiHoleBlocklist/master/SmartTV.txt:
   tuner-api.hdhomerun.com 
   location-api.hdhomerun.com 

bap
Posts: 18
Joined: Tue Jan 13, 2004 8:35 pm
Device ID: 1080B35E
x 1

Re: Not seen by my.hdhomerun.com or Mac app

Post by bap »

Also FYI, after power-cycling the HDHR it's now being seen by the Mac app. Firmware update & warm reboot didn't seem to work, but a full cold reboot solved the problem...

NedS
Silicondust
Posts: 1511
Joined: Mon Dec 10, 2018 12:38 pm
x 41

Re: Not seen by my.hdhomerun.com or Mac app

Post by NedS »

bap wrote: Sat Oct 17, 2020 5:59 am These are the pi-hole lists I'm using that they were found in:

Code: Select all

Match found in https://dbl.oisd.nl:
   location-api.hdhomerun.com 
 Match found in https://raw.githubusercontent.com/Perflyst/PiHoleBlocklist/master/SmartTV.txt:
   tuner-api.hdhomerun.com 
   location-api.hdhomerun.com 
Thanks, hopefully they will update the blocklists now that they've been given a heads up.

jonw747
Posts: 2
Joined: Wed Oct 21, 2020 2:28 pm

Re: Not seen by my.hdhomerun.com or Mac app

Post by jonw747 »

bap wrote: Fri Oct 16, 2020 4:55 pm A thought regarding my.hdhomerun.com. When I view the system log of my HDHR I see a lot of instances of this message:
19700101-04:11:12 System: myhdhomerun_sync: webclient error (dns failed)
If the HDHR needs to "phone home" for my.hdhomerun.com to work properly then this may very well be the reason that is failing. If it's unable to resolve DNS for some reason then I can see why that wouldn't work.
I'm getting a lot of connect errors rather than dns failed. No clue why. The only thing unique about my network (other than using multiple switches) is that my subnet mask is 255.255.255.240 rather than the more typical 255.255.255.0.

I'm also having device detection problems, albeit my tuners work fine in Plex.

Post Reply