NextPVR 6 Failure adding HDHomeRun Prime

[bail9stamina2GONE]

Howdy,

New user here. I setup a docker container running version 6.0.0.220904. I have a HDHomeRun Prime at 172.0.0.50 and when I try to scan for devices, I get this in the console output

Code:

[43] Starting SAT>IP discovery
[43] CaptureSource.LoadAll()
[43] [
    {
        "DeviceID": "REDACTED",
        "ConditionalAccess": 1,
        "BaseURL": "http://172.16.0.50",
        "DiscoverURL": "http://172.16.0.50/discover.json",
        "LineupURL": "http://172.16.0.50/lineup.json"
    }
]
[43] Downloading from http://172.16.0.50/discover.json
[43] Unable to connect to HDHR device (http://172.16.0.50/discover.json): Value cannot be null. (Parameter 'ipString')

When I check the results from discover.json, It is indeed missing a ipString field

Code:

curl http://172.16.0.50/discover.json | jq -r .
{
  "FriendlyName": "HDHomeRun PRIME",
  "ModelNumber": "HDHR3-CC",
  "FirmwareName": "hdhomerun3_cablecard",
  "FirmwareVersion": "20220822",
  "DeviceID": "REDACTED",
  "DeviceAuth": "REDACTED",
  "BaseURL": "http://172.16.0.50:80",
  "LineupURL": "http://172.16.0.50:80/lineup.json",
  "TunerCount": 3,
  "ConditionalAccess": 1
}

Is this an issue with the firmware I'm running? I believe it's the latest firmware available for my device. Is there a workaround I could use to give it a try?

Thank you!

[mvallevand]

Is your devices supposed to use a public IP address?

Martin

[bail9stamina2GONE]

Is your devices supposed to use a public IP address?

Martin

I redacted the IP address one octet too many. It's a 172.16 private ip range, not a public one.

[mvallevand]

Do you have your channels stored on the HDHR web site so lineup.json returns a channel list?

Martin

[bail9stamina2GONE]

Do you have your channels stored on the HDHR web site so lineup.json returns a channel list?

Martin

Yes, 523 channels.

Example output

Code:

curl http://172.16.0.50/lineup.json | jq -r .
[
  {
    "GuideNumber": "3",
    "GuideName": "KBTC",
    "VideoCodec": "MPEG2",
    "AudioCodec": "AC3",
    "URL": "http://172.16.0.50:5004/auto/v3"
  },
  <SNIP>
]

[mvallevand]

Is the curl command in a docker bash? I feel it cannot get out.

Martin

[bail9stamina2GONE]

Is the curl command in a docker bash?  I feel it cannot get out.

Martin

Yes I have been running them in the docker container.

I believe that the logs showing the correct DeviceID and ip seems to indicate that NextPVR is successfully connecting at least once.

Thank you for the idea though.

[sub]

Post the logs and we'll take a look.

[leastsquares]

I think I may be running up against the same/similar issue here.

HDHR IP: 192.168.1.184
Docker Host IP: 192.168.1.111

Note I am using an original HDHR Dual. So my hardware counts as "Legacy". In particular, http://192.168.1.184/lineup.json does not work. However, http://192.168.1.184/discover.json works and returns JSON that includes LineupURL: http://ipv4-api.hdhomerun.com/api/lineup...THCODEHERE which works.

Anyway, the problem: NextPVR can't add the device. When I start the container I get this console output:

Code:

nextpvr     | [1] Version 6.0.0.220904
nextpvr     | [1] Starting SAT>IP discovery
nextpvr     | [1] local address: 192.168.48.3
nextpvr     | [1] CaptureSource.LoadAll()
nextpvr     | [1] [
nextpvr     |     {
nextpvr     |         "DeviceID": "1015****",
nextpvr     |         "Legacy": 1,
nextpvr     |         "BaseURL": "http://192.168.1.184",
nextpvr     |         "DiscoverURL": "http://192.168.1.184/discover.json"
nextpvr     |     }
nextpvr     | ]
nextpvr     | [1] Downloading from http://192.168.1.184/discover.json
nextpvr     | [1] Unable to connect to HDHR device (http://192.168.1.184/discover.json): Value cannot be null. (Parameter 'ipString')
nextpvr     | [1] With environment: LD_LIBRARY_PATH=/app/DeviceHost/x64:
nextpvr     | [1] Local Devices: <devices>
nextpvr     | </devices>
nextpvr     |

Indeed, I don't see any ipString parameter in the JSON when I hit http://192.168.1.184/discover.json:

Code:

curl http://192.168.1.184/discover.json | jq -r
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   333    0   333    0     0  13983      0 --:--:-- --:--:-- --:--:-- 16650
{
  "FriendlyName": "HDHomeRun DUAL",
  "ModelNumber": "HDHR-US",
  "Legacy": 1,
  "FirmwareName": "hdhomerun_atsc",
  "FirmwareVersion": "20200225",
  "DeviceID": "1015****",
  "DeviceAuth": "REDACTED",
  "TunerCount": 2,
  "BaseURL": "http://192.168.1.184:80",
  "LineupURL": "http://ipv4-api.hdhomerun.com/api/lineup?DeviceAuth=REDACTED"
}

If I prompt for a rescan:

Code:

nextpvr     | [10] Got request [192.168.1.60]: /services/service (setting.devices)
nextpvr     | [10] method=setting.devices
nextpvr     | [10] parameters:
nextpvr     | [10]    method: setting.devices
nextpvr     | [10]    refresh: true
nextpvr     | [10]    format: json
nextpvr     | [10]    sid: 42737574-ec6d-4baf-8b20-d57544593e07
nextpvr     | [10]    client_ip: 192.168.1.60
nextpvr     | [10]    user_agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:105.0) Gecko/20100101 Firefox/105.0
nextpvr     | [10]    host_callback: ...
nextpvr     | [10] setting.devices
nextpvr     | [10] Starting SAT>IP discovery
nextpvr     | [10] CaptureSource.LoadAll()
nextpvr     | [10] [
nextpvr     |     {
nextpvr     |         "DeviceID": "10154DA7",
nextpvr     |         "Legacy": 1,
nextpvr     |         "BaseURL": "http://192.168.1.184",
nextpvr     |         "DiscoverURL": "http://192.168.1.184/discover.json"
nextpvr     |     }
nextpvr     | ]
nextpvr     | [10] Downloading from http://192.168.1.184/discover.json
nextpvr     | [10] Unable to connect to HDHR device (http://192.168.1.184/discover.json): Value cannot be null. (Parameter 'ipString')
nextpvr     | [10] With environment: LD_LIBRARY_PATH=/app/DeviceHost/x64:
nextpvr     | [10] Local Devices: <devices>
nextpvr     | </devices>
nextpvr     |
nextpvr     | [10] SAT>IP discovery complete
nextpvr     | [10] CaptureSource.LoadAll()
nextpvr     | [10] ReloadSettings()
nextpvr     | [10] Checking for new capture devices
nextpvr     | [10] CaptureSource.LoadAll()
nextpvr     | [10] ReloadSettings()@2
nextpvr     | [10] ReloadSettings()@3
nextpvr     | [10] ReloadSettings()@4
nextpvr     | [10] CaptureSource.LoadAll()
nextpvr     | [10] ReloadSettings()@5
nextpvr     | [10] ReloadSettings()@6
nextpvr     | [10] ReloadSettings()@exit
nextpvr     | [10] CaptureSource.LoadAll()
nextpvr     | [10] [{
nextpvr     | "id": "20",
nextpvr     | "name": "IPTV Device",
nextpvr     | "channelCount": 0,
nextpvr     | "sourceType": "IPTV",
nextpvr     | "present": true,
nextpvr     | "enabled": true
nextpvr     | }
nextpvr     | ]...snip...

My docker-compose file:

Code:

  nextpvr:
    container_name: nextpvr
    image: nextpvr/nextpvr_amd64:stable
    volumes:
      - /home/icserver/nextpvr/config:/config
      - /home/icserver/nextpvr/videos:/recordings
      - /home/icserver/nextpvr/videos:/buffer
    restart: "unless-stopped"
    ports:
      - 8866:8866
      - 16981:16981/udp
      - 8026:8026/udp
    # environment:
    #   HOST_IP: 192.168.1.184
   

Note that HOST_IP, which is recommended for Legacy devices on the Docker page is commented out here. However, if I uncomment I get the same results. This suggests to me that NextPVR is able to at least see the tuner on the network.

Here's the output of the log file:

Code:

2022-10-08 03:57:48.342    [INFO][1]    See LICENSE.txt for license information
2022-10-08 03:57:48.344    [DEBUG][1]    No /config/scripts/PreStartup.sh
2022-10-08 03:57:48.353    [DEBUG][1]    Checking if upgrade required
2022-10-08 03:57:48.354    [DEBUG][1]    master file is /app/data/Config-master-dont-edit.xml
2022-10-08 03:57:48.356    [DEBUG][1]    Doing database updates
2022-10-08 03:57:48.357    [DEBUG][1]    Database: /config/npvr.db3
2022-10-08 03:57:48.469    [INFO][1]    Version 6.0.0.220904
2022-10-08 03:57:48.524    [DEBUG][1]    Starting SAT>IP discovery
2022-10-08 03:57:48.531    [DEBUG][1]    local address: 192.168.48.4
2022-10-08 03:57:48.617    [DEBUG][1]    CaptureSource.LoadAll()
2022-10-08 03:57:48.850    [DEBUG][1]    [
    {
        "DeviceID": "10154DA7",
        "Legacy": 1,
        "BaseURL": "http://192.168.1.184",
        "DiscoverURL": "http://192.168.1.184/discover.json"
    }
]
2022-10-08 03:57:48.911    [DEBUG][1]    Downloading from http://192.168.1.184/discover.json
2022-10-08 03:57:48.919    [ERROR][1]    Unable to connect to HDHR device (http://192.168.1.184/discover.json): Value cannot be null. (Parameter 'ipString')
2022-10-08 03:57:49.132    [DEBUG][1]    With environment: LD_LIBRARY_PATH=/app/DeviceHost/x64:
2022-10-08 03:57:49.142    [DEBUG][1]    Local Devices: <devices>
</devices>

Let me know if other info may be helpful.

[sinttesi]

Similar issue with HDHR Connect Quatro after updating to the latest firmware this morning, NextPVR can no longer connect to it. I was not playing with any NextPVR settings at the time and confirm it was working moments before the firmware update, strongly suggesting that is the culprit.
At first I thought it was because I was using an older version of NextPVR and latest HDHR firmware, however I (finally!) updated to the latest AMD64 docker image this morning and get the same issue. I’ve attached log files and this I the HDHR section:

Code:

2022-10-08 11:06:02.685    [DEBUG][1]    Downloading from http://192.168.178.50/discover.json
2022-10-08 11:06:02.694    [ERROR][1]    Unable to connect to HDHR device (http://192.168.178.50/discover.json): Value cannot be null. (Parameter 'ipString')
2022-10-08 11:06:02.908    [DEBUG][1]    With environment: LD_LIBRARY_PATH=/app/DeviceHost/x64:
2022-10-08 11:06:02.917    [DEBUG][1]    Local Devices: <devices>
</devices>

The HDHR is alive and kicking, I can watch channels using their own app and access it’s web/config page. If I go to http://192.168.178.50/lineup.json it returns a list of channels, and http://192.168.178.50/discover.json returns some device information and also points to lineup.json. I assume this means the HDHR is broadly doing what it is supposed to? I’m not sure what the firmware update has changed?
Any suggestions greatly appreciated!