devices unavailable

[kfd82]

Running NextPVR on Libreelec 10 on an Intel NUC.  Nextpvr suddenly quit seeing the tuners (HDhomerun connect Quatro)  I have tried rebooting the NUC, installing the newest version of Nextpvr, rebuilding the docker image, no joy.  I even created a schedulesdirect account to if that helped.  logs attached.  Thank you.

[mvallevand]

Outside Docker can you try these,

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

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

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

Martin

[kfd82]

I ssh'ed into the machine and typed these into the command line, they just returned a new command prompt. I guess I don't understand what I'm supposed to do with these commands.

[mvallevand]

The may have returned [] and you didn't notice.

Could you try on another machine, it is possible your device is not connected.

Martin

[kfd82]

Thank you...yes it returned [] and I didn't notice it in front of the prompt.

I can access the tuner's webpage, and view a livestream from the tuner via VLC....how do I re-connect it to LE and NextPVR?

Thank you.

[mvallevand]

Do all 3 return []

Martin

[kfd82]

the first and third return []

the second returns curl: (6) Could not resolve host: ipv6-api.hdhomerun.com

[mvallevand]

I guess you don't have ipv6 running.

If your devices are on line and working you need to open a support ticket with Silicon Dust. In the meantime maybe go to Settings->General and disable the device scan at startup and restart your Docker. I am not sure if that will help now that they are marked unavailable but it might.

Martin

[kfd82]

Alright....I disabled the device scan at startup, and restarted the Docker with no success. I ran the HDHomeRun's setup app and did a channel scan there, just for grins. Waited a while, came back to the NextPVR web app, and rescanned for devices, and they connected! Now my only issue is that in the Scheduler: recurring list, the reported time for recordings is vastly off what I enter. I wonder is that is connected to "--volume /etc/localtime:/etc/localtime:ro \" in my docker setup; I had that in an earlier incarnation of the system, and do this infrequently enough that I don't remember if I need it or not.

EDIT: in the upcoming recordings, the reported times are correct.

[mvallevand]

You might be only able to disable it before it goes unavailable.

As for the other problem, it is unrelated but you do need to make sure your Docker has the correct timezone.

Martin