NextPVR Forums
  • ______
  • Home
  • New Posts
  • Wiki
  • Members
  • Help
  • Search
  • Register
  • Login
  • Home
  • Wiki
  • Members
  • Help
  • Search
NextPVR Forums Public NextPVR Support Docker amd64 v
« Previous 1 … 4 5 6 7 8 9 Next »
unRaid, Docker, legacy HD Homerun - no tuners found

 
  • 0 Vote(s) - 0 Average
unRaid, Docker, legacy HD Homerun - no tuners found
curiousfunk
Offline

Junior Member

USA
Posts: 4
Threads: 1
Joined: Dec 2020
#1
2020-12-12, 09:01 PM
Hello!

I have an original HDHR-US dual-tuner HD Homerun. It's been in use for a long time, with Win7 MCE and for a couple weeks demoing NextPVR in Windows 7. My quick tests in Windows worked great.

Today I began the process of Dockerizing NextPVR on my unRaid server. I believe I created the container correctly - I can access the NextPVR web GUI.

But NextPVR GUI does not list my HD Homerun.

The tuner responds at http://ipv4-api.hdhomerun.com/discover

Code:
[
    {
        "DeviceID": "10199268",
        "LocalIP": "192.168.1.217",
        "Legacy": 1,
        "BaseURL": "http://192.168.1.217",
        "DiscoverURL": "http://192.168.1.217/discover.json"
    }
]

My container's logs report:
Code:
[1] [
{
  "DeviceID": "10199268",
  "LocalIP": "192.168.1.217",
  "Legacy": 1,
  "BaseURL": "http://192.168.1.217",
  "DiscoverURL": "http://192.168.1.217/discover.json"
}
]
[1] Downloading from http://192.168.1.217/discover.json
[1] Unable to connect to HDHR device (http://192.168.1.217/discover.json): The remote server returned an error: (404) Not Found.

When I GET >> `http://192.168.1.217` it succeeds, returning model, device ID, firmware version, etc.

But when I GET >> `http://192.168.1.217/discover.json` it does 404. So it doesn't seem like my tuner is hosting/serving that file?

-- maybe related setup question --

My unRaid server lives at 192.168.1.11

My understanding is that legacy HDHR tuners need the extra parameters:

  1. --env HOST_IP=192.168.1.11   <-- this is supposed to be my server's IP?
  2. --publish 8020-8030:8020-8030/udp
I can attach full logs if needed.
mvallevand
Offline

Posting Freak

Ontario Canada
Posts: 52,995
Threads: 956
Joined: May 2006
#2
2020-12-12, 09:09 PM
Can you check http://192.168.1.217/discover.json from your browser? The 404 response is from the HDHR. Maybe you need a firmware update?

Martin
curiousfunk
Offline

Junior Member

USA
Posts: 4
Threads: 1
Joined: Dec 2020
#3
2020-12-12, 09:21 PM
That also 404's.

I've been thinking the same thing. My old tuner is on FW ver 20150406 Smile

In the FW changelog, I see:

Release 20161107/20161107b:
* Legacy models: Add support for DeviceAuth and discover.json APIs required for live TV in the latest HDHomeRun VIEW apps.

https://www.silicondust.com/support/down...changelog/
mvallevand
Offline

Posting Freak

Ontario Canada
Posts: 52,995
Threads: 956
Joined: May 2006
#4
2020-12-12, 09:22 PM (This post was last modified: 2020-12-12, 09:23 PM by mvallevand.)
You probably were using the BDA (ATSC) mode not HDHR mode on Windows.

Martin
curiousfunk
Offline

Junior Member

USA
Posts: 4
Threads: 1
Joined: Dec 2020
#5
2020-12-12, 09:28 PM
Sorry - not sure what that means (BDA vs HDHR mode).

I'll add: the Win10 HD Homerun app can't find my tuner either. So ... I'll dust off the old Win7 HTPC and try to update the firmware.
mvallevand
Offline

Posting Freak

Ontario Canada
Posts: 52,995
Threads: 956
Joined: May 2006
#6
2020-12-12, 09:31 PM
The HDHR is listing 3 times in Windows is North America.

ATSC
QAM
HDHR

The HDHR mode is the one that needs the new firmware.

Martin
curiousfunk
Offline

Junior Member

USA
Posts: 4
Threads: 1
Joined: Dec 2020
#7
2020-12-12, 09:50 PM (This post was last modified: 2020-12-12, 09:50 PM by curiousfunk.)
That (updating firmware) fixed it Big Grin

Thanks for your help @mvallevand!
« Next Oldest | Next Newest »

Users browsing this thread: 1 Guest(s)



Possibly Related Threads…
Thread Author Replies Views Last Post
  Migrating from Windows to Docker? boringgit 2 124 2025-06-09, 07:58 PM
Last Post: boringgit
  Comskip segfaults with comskip embedded in amd64 docker SickBoy 6 593 2025-02-24, 11:18 PM
Last Post: SickBoy
  Issues with Session Handling Behind Caddy Reverse Proxy in Docker: invalid session user001 5 589 2025-01-10, 08:23 PM
Last Post: sub
  Docker container becomes unresponsive overnight wapkaplet 6 777 2025-01-10, 04:47 PM
Last Post: wapkaplet
  Docker image upgrade ceejayemm 9 1,068 2025-01-07, 11:27 PM
Last Post: pkscout
  Current guide for NextPVR docker on Unraid? wapkaplet 1 875 2024-12-20, 02:40 AM
Last Post: wapkaplet
  NextPVR with Docker and Fritzbox icompas 9 776 2024-12-12, 02:50 PM
Last Post: icompas
  Docker postprocessing script aTF6i 12 1,162 2024-11-17, 01:17 AM
Last Post: aTF6i
  XMLTV folder for Docker stevil 1 456 2024-09-25, 06:56 PM
Last Post: mvallevand
  Add Intel iHD Driver to Docker Image for NextPVR thelanofvilles 8 1,410 2024-06-16, 08:10 PM
Last Post: thelanofvilles

  • View a Printable Version
  • Subscribe to this thread
Forum Jump:

© Designed by D&D, modified by NextPVR - Powered by MyBB

Linear Mode
Threaded Mode