Missing 1 day of EPG data in TV Guide

[PapaJay]

Hi

I searched the forum but could not find anything close to the problem I have encountered.

I am missing 23 hours of EPG data in my TV Guide.  The source of the data is Schedules Direct, and NextPVR has never had a problem processing this data until now.  The schedule is updated daily at 7 PM. I am downloading next 14 days of schedule data each time.  This data has been missing for many days now and I was hoping it was a Schedules Direct data problem that would be corrected by now if it was a problem on their end.

The missing data starts at 8PM Eastern Daylight Savings Time on Saturday October 31 and data in the guide resumes at 7PM Eastern Standard Time on Sunday November 1 - note that during this period Toronto, Canada where I live switches from daylights savings to standard time at 2 AM Sunday November 1.  Last year when we switched from daylight savings to standard time we did not see missing data in the TV Guide.

I am running the NextPVR server on Windows 10 and it is at level 4.2.3 (181112) - yes, I know I am back level.  I would have checked to see if there was a problem that was fixed in 4.2.5 or V5 but I have been unable to find a list of fixes between releases.

NextPVR logs are attached.

Note, I have posted a question to the Schedules Direct Forum asking if there is data missing in the stream being processed by NextPVR. ( I have no idea if NextPVR downloads the Schedules Direct data to a temporary file for processing, and if it does where this file might be so that is could be attached also)

Thank You.   PapaJay

[sub]

I am running the NextPVR server on Windows 10 and it is at level 4.2.3 (181112) - yes, I know I am back level.  I would have checked to see if there was a problem that was fixed in 4.2.5 or V5 but I have been unable to find a list of fixes between releases.

I'm not aware of NextPVR v4 having an issue like that in the past daylight savings shifts. Realistically though, if it was anything that needed a NextPVR fix, it'd only happen on NextPVR v5, so you'd need to check if you have the issue there.