HDHR View Win10x64 - Invalid Quattro listed?

Help and support for HDHomeRun DVR and HDHomeRun software for Windows 10, Mac, Android, XBox, etc.
Post Reply
mike808
Posts: 101
Joined: Thu Aug 12, 2010 8:30 pm
Device ID: (K) Extend 10522C9A ; Quatro 10740D6C
Location: US

HDHR View Win10x64 - Invalid Quattro listed?

Post by mike808 »

my.hdhomerun.com and homerun.local and the HDHR Setup program all detect my Quattro device.

However, when I launch the HDHR View app (win10x64 2004 build 10.0.19041.508) and view my account / settings, it lists my Extend and the Record engine and my Quattro. However, my Quattro has a strikeout through it and a trash can (as if I can delete it). The Extend and the Record Engine just have checks next to them and no trash can (as if they cannot be deleted). I went to the registration URL and it lists both devices, the Extend and the Quattro. I've got the latest firmware installed in both (20200907) and the latest app (20200214/App, 20200924/UI) and record engine (HDHR Setup 20200907).

Is something wrong in my setup?

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

Re: HDHR View Win10x64 - Invalid Quattro listed?

Post by signcarver »

that says it did not detect your quatro via broadcast discovery when the app launched but is on the account. If your record engine is on a NAS or PC, I would check the logs and see if it discovers the quatro. Most common cause is either improper subnet or a delay in getting the response back (i.e. I know a few that have used some form of bridge to connect to their quatro, or multiple network ports that overlap networks). The trash can is to remove the device from your account.

Describe how things are connected in your network.

mike808
Posts: 101
Joined: Thu Aug 12, 2010 8:30 pm
Device ID: (K) Extend 10522C9A ; Quatro 10740D6C
Location: US

Re: HDHR View Win10x64 - Invalid Quattro listed?

Post by mike808 »

A couple of reboots (for other reasons) and it seems to have repaired itself. It is now reporting both devices and the engine with the checkmark.

I suspect that loading/unloading a VPN that doesn't quite have bypass/exclusion rules that work to allow the PC using the VPN to interact with local devices. I'd blame the VPN for not cleaning up after itself very well before HDHR. There were also some network driver updates (one of the reasons for a reboot) so that may be a culprit as well.

Case closed.

Post Reply