Kodi cant connect to NPVR if left dormant for a few hours...

[gdogg371]

As per the below Kodi logs, if I dont watch Kodi for a while, then try to resume watching, the backend seems to go into some kind of sleep, where it is no longer responding to requests from Kodi. I then have to reboot NPVR. Can anyone see from the attached log why that might be the case? Running Kodi 19 and NPVR most recent version as of yesterday. The NPVR logs have not been update for several hours...

https://pastebin.com/45Gf70QA

[mvallevand]

For Kodi support I'd need to see both the zipped NextPVR logs to confirm the server is still responding and awake I'd need the required Kodi debug log to see when it stopped connecting. The default Kodi log is usually not very helpful

This looks like a tuning issue to me since it is not working right after the connect.

Martin

[gdogg371]

https://workupload.com/archive/SmwsWA3c ...NPVR logs and the Kodi debug log

[mvallevand]

It is much easier for us if you attach the zip file you get from the browser to the post on the forum

These messages in the capture logs

2021-03-14 01:16:40.951 [DEBUG][4] Device reports resolution(2): 0x0 (fps:0) (aspect:0) (progressive:1) (videoIdCode:0)
2021-03-14 02:04:13.041 [DEBUG][8] Device reports resolution(2): 0x0 (fps:0) (aspect:0) (progressive:1) (videoIdCode:0)
2021-03-14 02:04:44.487 [DEBUG][10] Device reports resolution(3): 0x0 (fps:0) (aspect:0) (progressive:1) (videoIdCode:0)

will mean the Colossus is not seeing any signal from the capture source so there is no data to send to Kodi. Perhaps the source is going to sleep and you need to wake it. Sometimes if you don't give the blaster command enough time to tune between channels you will also see that.

When it works you will see a line like

2021-03-13 16:00:00.247 [DEBUG][19] Device reports resolution(3): 1280x720 (fps:50) (aspect:2) (progressive:1) (videoIdCode:19)

Martin

[gdogg371]

It is much easier for us if you attach the zip file you get from the browser to the post on the forum

These messages in the capture logs

2021-03-14 01:16:40.951 [DEBUG][4] Device reports resolution(2): 0x0 (fps:0) (aspect:0) (progressive:1) (videoIdCode:0)
2021-03-14 02:04:13.041 [DEBUG][8] Device reports resolution(2): 0x0 (fps:0) (aspect:0) (progressive:1) (videoIdCode:0)
2021-03-14 02:04:44.487 [DEBUG][10] Device reports resolution(3): 0x0 (fps:0) (aspect:0) (progressive:1) (videoIdCode:0)

will mean the Colossus is not seeing any signal from the capture source so there is no data to send to Kodi.  Perhaps the source is going to sleep and you need to wake it.  Sometimes if you don't give the blaster command enough time to tune between channels you will also see that.

When it works you will see a line like

2021-03-13 16:00:00.247 [DEBUG][19] Device reports resolution(3): 1280x720 (fps:50) (aspect:2) (progressive:1) (videoIdCode:19)

Martin

...ah yes, i hadnt thought of that...there is a basic API on this box that allows you to check and then change the status of the box I believe, so will work on ensuring it is awake. will upload the zip next time. thanks...