2017-11-15, 19:05
Problem Solved:
I compared my 2 RPi systems and found that the problem child had an LE setting the good system didn't have: a timeserver setting. I've removed the timeserver setting and have rebooted the problem child 6 times and each time, the EPG time was correct.
Background:
RPi systems do not have a clock so when the internet is down, an RPi shows the time it was the LE software was compiled. My solution to this problem was to turn my back end NextPVR server, a Windows 10 desktop PC, into a time server for the RPi since it has a clock. The solution appeared to work well until Daylight Savings Time ended. I don't know if the problem would exist if I had specified an external time server. What I do know is that specifying the windows PC as a time server is problematic.
Sent from my Galaxy Tab 2
I compared my 2 RPi systems and found that the problem child had an LE setting the good system didn't have: a timeserver setting. I've removed the timeserver setting and have rebooted the problem child 6 times and each time, the EPG time was correct.
Background:
RPi systems do not have a clock so when the internet is down, an RPi shows the time it was the LE software was compiled. My solution to this problem was to turn my back end NextPVR server, a Windows 10 desktop PC, into a time server for the RPi since it has a clock. The solution appeared to work well until Daylight Savings Time ended. I don't know if the problem would exist if I had specified an external time server. What I do know is that specifying the windows PC as a time server is problematic.
Sent from my Galaxy Tab 2
