NextPVR EPG not showing in Emby livetv

[DParsons]

Hello Sub if you don't mind having a look at this forum thread from Emby to see if you can spot any issues that might be causing me to not be able to load the guide from NextPVR in Emby. I posted the issue I'm having there and Luke said to contact NextPVR about an error he is seeing on the Emby logs from NextPVR. NextPVR Logs attached.

I have uninstalled and reinstalled both Emby and NextPVR to see if that might fix the problem, but the problem persists. That is the livetv module in Emby is not importing anything from NextPVR, no recordings, no schedule, no series info. Only the guide without any EPG info will show. I can still steam livetv by playing the channel but no program info shows up. After reinstalling both programs it is now importing the schedule, recordings and everything except the EPG still will not import and remains blank. Everything worked until about two days ago and no changes have been made in that time.

Original Emby forum thread:
https://emby.media/community/index.php?/...ntry427591

[mvallevand]

Your logs don't go back far enough to show the Emby error. I would check the event viewer logs for the error, if not restart the NextPVR server and try again. Also remember Emby doesn't use sub's interface it use UJB's JSON.

Martin

[DParsons]

Thanks Martin, I'll see if I can reproduce it and post the logs again. I'm not sure if you can see the logs I posted on the Emby forum but those should have the error they are talking about.

[DParsons]

Immediately after posting here I checked Emby again and it is back to normal. I'm posting logs I just created just to see if possibly you all can spot anything obvious. :confused:

[mvallevand]

I responded on the Emby forum but I will duplicate it here for completeness

"Note that 500 is a valid response to some NEWA JSON calls requiring special handling. In this case the call that was failing here was not the guide listing info. What I saw on the EPG side of NextPVR was no guide data was being returned

2017-03-04 07:36:13.290 [INFO][59] #*** Created listing for 0 events in 0.519 seconds.

In the future if this happens again you would need to confirm there was guide data in NextPVR and on a Kodi refresh and report that on the NextPVR forum."

Martin

[DParsons]

That is what was happening, that is no guide data. If it happens again I'll post the logs here. I have had at least a couple of issues with Emby livetv (with the nextpvr backend) that eventually went away. It seems like the Emby web app itself must be able to create some issues that they then fix and the forum people don't seem to be aware of those possible issues and subsequent fixes, not sure about that but this is not the first time I've had a problem resolved after I've reported it on the forum without any input from the Emby forum people. Just a guess but it's my best assumption of what may have happened here. The main thing is that it has never been a problem with NextPVR which is what the forum people initially suggest but then it just gets resolved. The Emby NextPVR addon does not perform at the same level as other PVR backends (I've been told the hdhomerun is what works best but my stb makes the use of the colossus II the only way PVR will work for me and NextPVR is the only media center I'm aware of that works with it) and will not perform all functions that are available to the PVR backend. But it works well enough as is it's just little things like being able to set a recording to new only that will not work correctly.

[mvallevand]

The Emby NextPVR addon does not perform at the same level as other PVR backends (I've been told the hdhomerun is what works best but my stb makes the use of the colossus

I don't agree with that statement, the Emby API code is pretty straight so any clients should have similar difficulties. A transcoding solution is bound to have some problems. As for the EPG problem you complicate things for us because you uise Kodi and sub unfortunately spams the web logs but if you send the logs earlier the next time we might see something.

Martin

[DParsons]

I used the Emby app remotely yesterday after it had started working again and after not very long it happened again, the guide went blank and recordings and the schedule and everything went blank. Before this I played several channels in a row and everything seemed fine. I then check to see if I could schedule a recording and could not. This has been an ongoing issue that I'm aware of how to fix so I manually refreshed the guide, which would normally fix this, and something about doing that at this time then caused Nrecord.exe to max out my CPU, another recurring issue I've posted about here before. So what ended up happening is most all issues I've been having with Emby and NextPVR as the backend all occurred yesterday as I was testing to see if everything was back to normal. I've found in the past that by using Emby remotely and changing channels frequently can trigger this series of events and it did that again.

After arriving back to my home network I had to stop the NextPVR recording service and end Nrecored.exe in task manager and that will stop the CPU over utilization. I then copied the logs that are attached. After that point I manually refreshed the guide in Emby and everything went back to normal. I've included the NextPVR and Emby logs.

[DParsons]

the Emby API code is pretty straight so any clients should have similar difficulties.

Martin

I was told this by someone on the Emby forum it's not my opinion. After bringing up a related issue there someone mentioned that me not being able to save recording options in Emby was a result of me using the NextPVR addon as opposed to the hdhomerun addon as my livetv backend.

[mvallevand]

Do you shutdown your Emby server? Emby looks like it doesn't do an EPG update on startup

2017-03-05 19:10:16.0593 Info TaskManager: Daily trigger for Refresh Guide set to fire at 3/6/2017 3:30:00 AM, which is 499.73234457 minutes from now.

Again, Kodi spam doesn't let us know much about when EPG updates where requested but that Emby log makes it look like Emby might not have been running after the EPG udpate. If Emby does not cache between runs, that could be a problem so I posted on the Emby forum.

Martin