Kodi NPVR client refresh interval

[ceejayemm]

Using the latest NPVR plugin with LibreElec (9.2.3 / Kodi 18.7.1) on a RPi, how do I stop the plugin refreshing the list of recordings etc every minute ? An interval of an hour or so would be fine for my purposes.

Thnaks

Chris

[ceejayemm]

Oops, sorry meant to post this the Kodi /XBMC sub forum. Pleae move there if you wish.

Chris

[mvallevand]

It only updates the recording list when the recording status changes, when you watch a recording or when the server restarts. I can't seem to get the message across that logs are important. I can tell you much more about what is happening with this information and I don't have to ask.

I did look at your old logs and because of the lock error you are experiencing, kodi will be asking for channel listings often because of missing epg data. Are you sure it is recordings that is the issue?

Martin

[ceejayemm]

Martin

Thanks for the quick response as always.

I didn't post the logs as I thought, if there was a solution, it would be a case of 'change this setting to that value'.

You are right though I did come across this 'issue' as a result of investigating the 'database locked' issue where I am seeing Kodi requests for updates every minute or so making it difficult to 'see the wood from the trees'. If this is a symptom of the locked database issue then I an happy to look at this again once the main issue is resolved.

Thanks again.

Chris

[pkscout]

I'd noticed this before and just decided the logs were *really* robust.  I'm attaching my zip of logs to look through.  I know I'm watching more Live TV (which seems to generate more log entries), but I think there are big chunks (like early in the mornings that I'm not even up to interact with anything). It's not really a big deal, but if what I'm seeing isn't the expected behavior, then I'm happy to help figure out what the issue is.


  logs-20200610-1224.zip (Size: 980.76 KB / Downloads: 1)

[mvallevand]

@pkscout what are you asking me to check? Is this about the recordings? Sub likes the pretty-print url logging so IMO the logs are way too verbose (except for UI Client mode) and things look busier then they are but everything seems fine

- there are 2 sets of timer checks (recurring and scheduled) that Kodi backend does every five minutes.
- there are forced recording checks every minute because users complained that 5 minutes was too long to wait.
- there are channel.listings updates every two hours (PVR GUI setting)

Your right though you have a good setup because Kodi will do more backend checks when a channel is missing.

Martin

[pkscout]

@mvallevand, I see. I thought there might be an issue with the checks every minute, but if that's the expected behavior, then we're good. So basically I'm not asking you to look at anything then. '-) I honestly rarely look at the NPVR logs, and I've gotten used to creating search terms to try and find what I'm looking for through all the rest of the stuff.

[ceejayemm]

Now the 'Database is Locked' issue seems to be sorted and out of the way I can see what is happening here. The update frequencies posted by Martin above are way too frequent for my purposes, the machines involved will be spending more time working for each other that they would ever do for me.

I guess this isn't the place to ask for this process to be parameterized (and to also include a manual update option) - but where is ?

Chris

[mvallevand]

They are minutes not seconds and computer tasks are usually considered in microsecond. The call every minute is a trivial call 107 bytes which just looks bad because of excessive NextPVR logging, I would recommend turning off NextPVR debug logging since that probably will improve performance almost as much as reducing the calls.

For Matrix I am looking at improving the EPG update logic so that 24/7 clients only need to call for updates once a day. I am also going to cache the timer calls, if I can't find a way to patch the back end to make it async.

Finally you choose to build an RPi based platform, I did suggest it wasn't the best choice https://forums.nextpvr.com/showthread.ph...#pid531253

Martin

[ceejayemm]

Martin

You did indeed suggest that an RPi was not necessarily the best machine to run NPVR and I did it anyway using a RPi 4B with 4GB memory to see what happens. Apart from viewing Live TV / recordings via the web app it has performed flawlessly (other that the database is locked issue which now seems fixed) for nearly 6 months and I have absolutely no complaints about using this platform. I do my viewing via a separate RPi 3B running Libreelec v9.2.3 which again performs flawlessly for me. I appreciate my usage is not in the 'power user' range and as such the RPi's suit me just fine. It was on this basis that I queried the number of updates performed by the two PIs and which do indeed fill up an awful log of log space. I have been toying with setting the config.xml logging options to 'ERROR' rather than the default 'DEBUG' setting and may be this thread is the spur I need to make this happen.

Thanks as always for your invaluable help and suggestions, I appreciate them immensely which, together with the quick turn around from Sub, makes NPVR one of the better pieces of software I use - may it long continue.

Thanks

Chris