Tuner remains unavailable if not connected when NextPVR starts

[loucurapt]

My tuner is an Avermedia H830, though it's probably irrelevant here.
I use NextPVR (and KODI) in my laptop (Windows), and only connect my tuner when I want to watch or record TV.

When the NextPVR Service starts (including when starting Windows), if the tuner is not connected, it will show up as "unavailable" in Settings > Devices, even after connecting it.
If I then try to watch or record TV in KODI or NextPVR, or update EPG, it fails.
Even after going to Settings > Devices and pressing "ReScan For Devices" it still fails, even though the tuner no longer shows as "unavailable" in the list.

If I restart the NextPVR Service with the tuner connected, it starts working.

This didn't happen in NextPVR version 4.
In version 5 it seems like, when starting, NextPVR marks the device as "unavailable" if it's not connected and then never tries to see if it's connected again.
It would be great if NextPVR would check if the tuner is connected yet before doing it's thing.
Is there any settings that could solve this?

[mvallevand]

Yes this is a very annoying "feature" but I think for my HDHR that it happened in v4 too.

Martin

[sub]

It's typically slow to check for the existence of tuners, so it only does it at select times. (when the service starts, or when the user explicitely hits the 'rescan devices' button in Settings->Devices)

[loucurapt]

At least for me, when this happens, clicking that "ReScan Devices" button is not enough to make the tuner work.
The tuner is no longer listed as "(unavailable)", but live TV, recording, etc. don't work (but updating EPG seems to work, somehow).
I actually have to restart the NextPVR Service for it to work.

Maybe when trying to watch TV, record, etc. and the device is "unavaible", NextPVR should do whatever it does at startup to find the devices, but only for that device if possible, as a fallback?
Or it could do that when an "unavailable" tuner is connected to the computer. But since NextPVR is cross-platform now, that could be difficult, I suppose.
Or maybe it should simply consider all devices as available from the start, even if they are not connected. But I suppose there's a good reason for this behavior.
Or some other better idea.

[mvallevand]

Rescan doesn't help you need to restart the server. While sub's logic may sound good for new users who don't like long delays, I find it is flawed since the state of previously configured working tuners at start up doesn't at all represent the state days or weeks later.

Fortunately I've been able to add an Extra tuner for my HDHR's to solve my problem.

Martin