NextPVR 6 Failure adding HDHomeRun Prime

mvallevand · 2022-10-08, 12:46 PM

It appears https://ipv4-api.hdhomerun.com/discover and http://ipv4-api.hdhomerun.com/discover are not return devices I contacted SD to see what is going on.

Martin

sinttesi · (This post was last modified: 2022-10-08, 01:22 PM by sinttesi.)

(2022-10-08, 12:46 PM)mvallevand Wrote: It appears https://ipv4-api.hdhomerun.com/discover and http://ipv4-api.hdhomerun.com/discover are not return devices I contacted SD to see what is going on.

Martin

Thanks for the help. If SD need some device information let me know. I've posted pn the SD forum asking if the firmware can be downgraded.

mvallevand · (This post was last modified: 2022-10-08, 01:20 PM by mvallevand.)

It is not device specific, this should be returning a device list

curl https://ipv4-api.hdhomerun.com/discover

So new devices can't be added.

Martin

sinttesi · 2022-10-08, 01:25 PM

(2022-10-08, 01:20 PM)mvallevand Wrote: It is not device specific, this should be returning a device list

curl https://ipv4-api.hdhomerun.com/discover

So new devices can't be added.

Martin

Not sure I understand your post (I'm not a coding expert my any means!), if I clink your link it does bring up the HDHR device information.

I have deleted the previous tuners from NextPVR and when I rescan for new devices nothing comes up. Is NextPVR blocking new devices from been added?

mvallevand · (This post was last modified: 2022-10-08, 03:16 PM by mvallevand.)

It is failing for more me returning just [] If you are getting it now restart the server or click rescan.

Martin

leastsquares · 2022-10-08, 05:29 PM

(2022-10-08, 01:30 PM)mvallevand Wrote: It is failing for more me returning just [] If you are getting it now restart the server or click rescan.

Martin

I am seeing what looks like correct output when I hit https://ipv4-api.hdhomerun.com/discover:

Code:
curl https://ipv4-api.hdhomerun.com/discover | jq -r

[

  {

    "DeviceID": "1015****",

    "Legacy": 1,

    "BaseURL": "http://192.168.1.184",

    "DiscoverURL": "http://192.168.1.184/discover.json"

  }

]

Yet when I try to scan for devices, this is the output I get (same as above):

Code:
nextpvr     | [3] Got request [192.168.1.60]: /services/service (setting.devices)

nextpvr     | [3] method=setting.devices

nextpvr     | [3] parameters: 

nextpvr     | [3]    method: setting.devices

nextpvr     | [3]    refresh: true

nextpvr     | [3]    format: json

nextpvr     | [3]    sid: 3bb4ba70-cc67-4091-92f3-a84632c87e41

nextpvr     | [3]    client_ip: 192.168.1.60

nextpvr     | [3]    user_agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:105.0) Gecko/20100101 Firefox/105.0

nextpvr     | [3]    host_callback: ...

nextpvr     | [3] setting.devices

nextpvr     | [3] Starting SAT>IP discovery

nextpvr     | [3] CaptureSource.LoadAll()

nextpvr     | [3] [

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     | [3] Downloading from http://192.168.1.184/discover.json

nextpvr     | [3] Unable to connect to HDHR device (http://192.168.1.184/discover.json): Value cannot be null. (Parameter 'ipString')

nextpvr     | [3] With environment: LD_LIBRARY_PATH=/app/DeviceHost/x64:

nextpvr     | [3] Local Devices: <devices>

nextpvr     | </devices>

mvallevand · (This post was last modified: 2022-10-08, 07:38 PM by mvallevand.)

My error might be localized, since I get a different message in NextPVR too

2022-10-08 11:38:32.966 [WARN][1] Error discovering HDHR devices: Name or service not known (ipv4-api.hdhomerun.com:80)
2022-10-08 11:38:33.968 [WARN][1] Error discovering HDHR devices: Name or service not known (ipv4-api.hdhomerun.com:80)

However looking at theaw discovery JSON response sI see Kodi reads a LocalIP field and that is is missing

https://github.com/kodi-pvr/pvr.hdhomeru...s.cpp#L142

I suspect that is the same issue in NextPVR

Martin

sinttesi · 2022-10-08, 09:57 PM

(2022-10-08, 05:29 PM)leastsquares Wrote:
(2022-10-08, 01:30 PM)mvallevand Wrote: It is failing for more me returning just [] If you are getting it now restart the server or click rescan.

Martin

I am seeing what looks like correct output when I hit https://ipv4-api.hdhomerun.com/discover:

Code:
curl https://ipv4-api.hdhomerun.com/discover | jq -r [ { "DeviceID": "1015****", "Legacy": 1, "BaseURL": "http://192.168.1.184", "DiscoverURL": "http://192.168.1.184/discover.json" } ]

Yet when I try to scan for devices, this is the output I get (same as above):

Code:
nextpvr | [3] Got request [192.168.1.60]: /services/service (setting.devices) nextpvr | [3] method=setting.devices nextpvr | [3] parameters: nextpvr | [3] method: setting.devices nextpvr | [3] refresh: true nextpvr | [3] format: json nextpvr | [3] sid: 3bb4ba70-cc67-4091-92f3-a84632c87e41 nextpvr | [3] client_ip: 192.168.1.60 nextpvr | [3] user_agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:105.0) Gecko/20100101 Firefox/105.0 nextpvr | [3] host_callback: ... nextpvr | [3] setting.devices nextpvr | [3] Starting SAT>IP discovery nextpvr | [3] CaptureSource.LoadAll() nextpvr | [3] [ 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 | [3] Downloading from http://192.168.1.184/discover.json nextpvr | [3] Unable to connect to HDHR device (http://192.168.1.184/discover.json): Value cannot be null. (Parameter 'ipString') nextpvr | [3] With environment: LD_LIBRARY_PATH=/app/DeviceHost/x64: nextpvr | [3] Local Devices: <devices> nextpvr | </devices>

This is the same reply I get when trying to scan or rescan after changing the HDHR settings. Disabling and re-enabling the tuners just returns the same message.

(2022-10-08, 01:30 PM)mvallevand Wrote: It is failing for more me returning just [] If you are getting it now restart the server or click rescan.

Martin

Mine has always returned the device configuration.

mvallevand · 2022-10-08, 10:04 PM

I found the issue with mine, you must not be using ipv6 ipv4 works. SD did do an ipv6 change on the 5th.

To paraphrase an old expression

He who goes fourth on the fifth with the sixth shell name cam forth on the eighth

I confirmed the JSON API also has changed.

Martin

sinttesi · 2022-10-09, 05:45 PM

ipv6 and ipv4 settings are not my forte, but after some button bashing in the router settings I can now see the tuners – hurrah! Thanks for your help Martin.
Does anyone now have issues getting guide data? NextPVR moves on to the next frequency after a few seconds and does not download any EPG data. This wasn’t an issue previously, so wondering if it’s all connected.

Possibly Related Threads…
Thread		Author	Replies	Views	Last Post
	Building a Linux box for NextPVR advice please	bgowland	21	826	2025-03-27, 10:03 PM Last Post: bgowland
	nextPVR support Hauppauge 01595?	RedDawg	8	2,291	2023-06-16, 06:18 PM Last Post: sub
	Does the TBS6909 satellite card work on NextPVR?	LeoL	5	1,368	2023-02-19, 03:34 PM Last Post: mvallevand
	Replace Hauppauge tuner card with Hauppauge 1682 or HDHomeRun Flex Duo?	mountainsoft	0	1,007	2022-10-29, 01:34 AM Last Post: mountainsoft
	HDHomeRun Prime Installation to NextPVR using reclaimed cablecard	wwhenderson	7	2,470	2022-03-30, 12:09 AM Last Post: sub
	NextPVR on Linux Set Top Box?	something_fishy	1	1,554	2022-03-10, 04:06 PM Last Post: mvallevand
	NextPVR, xteve, Plex and Colossus 2 connected to a set-top-box	tboneus	4	2,394	2021-11-18, 01:12 AM Last Post: sub
	NextPVR on Raspberry Pi - Login Failed	PaulM	3	1,945	2021-10-04, 08:45 PM Last Post: mvallevand
	How to find what version number of NextPVR is running	SiyonKart	1	1,223	2021-09-17, 03:17 AM Last Post: sub
	HDHomeRun CONNECT DUO?	zodiac	1	1,421	2021-05-16, 02:29 PM Last Post: BrettB