3/5/17 Quick Update:
My tvguide.xml file still being updated as set in the schedule. So things are still good.
What I noticed this morning in the xap2xml.log file was the following:
....snip....
[D] Parsing: EP024717260046
Getting: gridDetailService?pgmId=EP024717260035
:Function: getURL :Line: 225
error<class 'mechanize._response.httperror_seek_wrapper'>
Getting: gridDetailService?pgmId=EP024717260035
:Function: getURL :Line: 225
error<class 'mechanize._response.httperror_seek_wrapper'>
Getting: gridDetailService?pgmId=EP024717260035
:Function: getURL :Line: 225
error<class 'mechanize._response.httperror_seek_wrapper'>
Failed to download within 3 retries.
:Function: getURL :Line: 228
error<class 'mechanize._response.httperror_seek_wrapper'>
[D] Failed to download: EP024717260035
[D] Parsing: SH000046300000
....snip....
I assume this is what I should see when a specific update cannot be downloaded. Saw this same logging of repeated attempts 1 or 2 times more in the file. The final lines of the file:
....snip....
Downloaded 1972995 bytes in 521 http requests.
Writing XML file: /home/osmc/.xmltv/tvguide.xml
Completed in 411s (Parse: 198s) 79 stations, 9693 programs, 34851 scheduled.
which seems to indicate that even tho there were a few errors, the tvguide.xml file was still updated...which I believe is what we were looking for.
Cheers....
------------------------------------------------------------------------------------------
2 days in...so far so good I'll post status again at the end of a week. Now I can go focus on a few other aspects of the PVR. I haven't yet cut the cord, but I'm getting very close...maybe another month, possibly 2, at most.
Funny that you come from a non-technical space. I, too, am a former marketing exec, but in the high tech domain (Silicon Valley). I also have an engineering degree, and while it was focused on the h/w side, I've done quite a bit of dabbling in s/w...a little bit of hi level here and there (still threatening to learn Python), but mostly at the CPU level ("diddling bits and bytes", as they say
I'm glad and very appreciative you took this on. I feel zap2xml is turning into a really nice addon. Maybe, just maybe, I'll actually get Python learned and I can look at contributing new features, as well.
Thx and cheers....
Thanks again for the update. This is all totally a hobby. I didn't know the first thing about python and other code until I started playing with this and modifying Kodi skins.
As for the different logs - I'm not sure how or why that happens. This project was orginally done by fasteddycurrent - which you can see here: GitHub - FastEddyCurrent/zap2xml: zap2xml in Python 2.7 for use on the RaspberryPI - it was he who converted the the original zap2xml perl script into python.
I basically took what he did and created a kodi addon and then started adding features I wanted to see. And now here we are. I'm just a former tv marketing exec who likes to play. I'm driven by the goal of wanting cheaper/better dvr service and this year I finally cut the cord. If i get around to it, I'll have to look at how the log system is structured.
BTW - the "Skipped:" entry means the code fix worked. That indicates that there was an empty or missing details file that would have previously crashed the grabber. Glad to see it completed!