Lost Schedules Direct updates on both NEXTPVRs

[klemo]

I didn't notice this right away but I found that I only have 2 days of EPG data on both of the NEXTPRV windows PCs.

I can login to schedules direct ok but when I attempt to find a lineup I get an error " unable to log into schedules direct."

I also have an WMC and a MythTv and both of also use Schedules direct and they were not effected and update just fine.  Its only these two NEXTPVR PC that lost the ability's to update about the same time, maybe 12 days ago. .

[klemo]

Here my Logs

[mvallevand]

Makes sense since v4 doesn't fully support Schedules Direct authentication changes. It looks like you need to disable SD art and also reenter you user credentials since they are messed up and it might start working again.

Pretty much the only reason for v4 these days would be Ceton tuners and analog devices bit you seem to just basic Hauppauge. If you must have EPG123 generate XMLTV for you and use that but you must stop using SD art. If you are using Win 7 wait for the next build too.

Martin

[klemo]

FYUI, My other win 10 NEXTPVR is V5.2 and it lost the ability oy update its EPG.
NextPvr logs on both PCs have the same error:  "{"code":403,"response":"Username expected but not provided."} see below:
Both other MYTHTV and WMC (win 7) EPG remain updating just fine. 

Why has two different versions of NPVR (yes they are old but working fine) on separate PC and tuners have this same problem at the same time...
Could an Windows update have something to do with this or is this Schedule directs problem.  I sent several message to SD but haven't heard back from them...

2025-08-17 18:02:00.826 [ERROR][9] Unexpected error doing Schedules Direct login: System.Net.WebException: The remote server returned an error: (403) Forbidden.
  at System.Net.HttpWebRequest.GetResponse()
  at NShared.SchedulesDirectJSONEPGSource.DoPOSTRequest(String url, String token, String body)
2025-08-17 18:02:00.827 [ERROR][9] System.Net.WebException: The remote server returned an error: (403) Forbidden.
  at System.Net.HttpWebRequest.GetResponse()
  at NShared.SchedulesDirectJSONEPGSource.DoPOSTRequest(String url, String token, String body)
2025-08-17 18:02:00.827 [ERROR][9] {"code":403,"response":"Username expected but not provided."}
2025-08-17 18:02:00.827 [DEBUG][9] Using URL: https://json.schedulesdirect.org/20141201
2025-08-17 18:02:00.953 [DEBUG][9]
{"response":"TOKEN_MISSING","code":1004,"serverID":"20141201.web","message":"Token required but not provided in header or request URI.","datetime":"2025-08-17T23:02:04Z","serverTime":1755471724}
2025-08-17 18:02:00.953 [ERROR][9] Failed to get token:
2025-08-17 18:02:00.953 [DEBUG][9] Stopping recording (200486 on 42). Past end time of recording. 1

[sub]

We've messaged Schedules Direct about it. I think they've changed some stuff at their end which has unexpectedly caused problems.

From what I can tell, it works fine with the last couple of releases of NextPVR, but is has a problem with over versions (like your 5.2)

[mvallevand]

I heard back from SchedulesDirect and they are looking at a custom parser to let v4 users back in. I tested on their debug server and that part is working.

Martin

[scott967]

***Update : false alarm
I did lose my EPG and updated, but didn't see in NextPVR web app settings page I could scroll down to an "update EPG" button.  Did that and now EPG is refreshed.




I see there's a couple of threads on this but I also lost schedules direct.  Since I haven't had NextPVR issues in a long time not sure my version of NextPVR, but at least 5 something.  (Normally access via Kodi NextPVR client addon.)

So I installed the version off the site 7.0.2.250621 on Windows 8.1 and updated NextPVR also updated EPG123 configurator to 1.8.4.1 and rebooted.

NextPVR is running but no EPG update.  My schedules direct is current through 03-26.

scott s.
.