Kodi NPVR client refresh interval

[mvallevand]

I did some checking with the debugger and if you increase the advancedsetting.xml https://kodi.wiki/view/Advancedsettings.xml#epg from the default <updatecheckinterval>300</updatecheckinterval> that will reduce the number of checks for timer changes.

Timers are still going to be reset by NextPVR when they really change via the lastupdated call which is done every minute

Martin

[ceejayemm]

Changing the LogLevel setting in /var/opt/nextpvr/config.xml from DEBUG to ERROR seems to have no effect. Should the change be made elsewhere if so where ?

Thanks

Chris

[mvallevand]

I suspect sub may not enabled this because you will effectively lose support for problems. Are you sure you aren't just perceiving this to be a problem? If the CPU load is high maybe consider symlinking the logs folder to you NAS. Also see if the advancedsetting change helps and we can recheck the logs after a few hour run.

Martin

[ceejayemm]

Martin

Thanks for the tips I will have a look at the updatecheckinterval setting in advancedsettings.xml for Kodi.

I don't have a problem with performance, I just don't like seeing lots and lots of 'debug' messages when they are not necessary (to me) but I do however see the point of having this level of logging turned on for the express support I have noted previously. I will forget about trying to get rid of these messages as there doesn't seem to be an immediate solution and I may actually be trying to 'flog a dead horse' on this matter.

I don't (yet) use the native USB booting capability of the new RPi 4B which is currently in beta testing, but I did use the details from this thread:

https://www.raspberrypi.org/forums/viewt...9&t=196778

to enable the PI to run Rasbian from a USB hard drive and not from its SD Card which should help logging somewhat - following your suggestion to this effect in January :-)

Thanks

Chris

[sub]

<LogLevel> wasn't used in v5, but I've added support for it in the next build.