2017-11-13, 18:14
Update (11/13/17.1)
zap2epg....
OK. Back to normal, mostly. Must have been my "diddling" with 1 or 2 of the files with a non-Unix-compatible editor (like using Wordpad from Win 10 over to the RPI 3/OSMC sys
I went back to V0.3.2 and xfered over zpa2epg.py, settings.xml and default.py from the downloaded zip file and re-edited from scratch from inside the addon configure function. Then reran the grabber from inside OSMC. Back on line...yayyy!!
One thing I have left to figure out is that I downloaded 2 weeks successfully and can see 2 weeks of programming for all my enabled channels from inside of the TVHeadEnd web interface in Electronic Program Guide. However, from OSMC/TV/Guide, the listing looks good (again, for all channels) till ~4PM today and then everything goes to "No information found". I checked the xmltv.xml file and, as expected, the data was there. Good news is it seems zap2epg is working as it should and xmltv.xml located in the ..../userdata/addon_data/script.... directory works great, as well. So, this sounds like something not coming from zap2epg.....still....sighhhhhhh......
tvh2kodi.....
I mentioned this in a previous posting but it must have gotten lost in the zap2epg noise.
When I try to set the cron thru this addon, I can go thru the motions to make the change in the on-screen keyboard and then hit "Done". However, the new/edited value is not saved. The setting remains unchanged.
zap2epg or tvh2kodi...
Can't remember which one this was coming from....if I go into the information function of the specific addon, I get a whole bunch of numbers (which look like versions) in the top half of the screen over the normal info (description, version, etc.). Looks like a mess.
If I get the chance, I'll check out which addon it was and update here.
Cheers....
Original (11/13/17.0)
You're welcome, as usual.....except this getting to be like a "circle jerk"
Something is still a bit off or has changed somewhere (again...arghhhhhh). Back to the xmltv.xml file not being updated at all. If I run tv_grab_zap2epg directly on the RPI 3, I get a short (or no) download time and then what is currently in xmltv.xml (cat $XMLTV_OUTPUT from the last successful update) screams across the screen. Properties of the zap2epg.log file shows the file's been modified when I run tv_grab_zap2epg but with 0 bytes. xmltv.xml shows a date from the last successful update a couple of days ago.
I went back to V0.3.1 (zpa2epg.py and default.py) thinking V0.3.2 might have had some issue, but no change. So, back on V0.3.2 and time to see what else it might be.
So, now I've got TV/Guide and web-based TVHeadEnd connected to the xmltv.xml file just fine, but I can't seem to update (or download data for) xmltv.xml.
Keep you posted....any suggestions appreciated....cheers...
zap2epg....
OK. Back to normal, mostly. Must have been my "diddling" with 1 or 2 of the files with a non-Unix-compatible editor (like using Wordpad from Win 10 over to the RPI 3/OSMC sys
I went back to V0.3.2 and xfered over zpa2epg.py, settings.xml and default.py from the downloaded zip file and re-edited from scratch from inside the addon configure function. Then reran the grabber from inside OSMC. Back on line...yayyy!!One thing I have left to figure out is that I downloaded 2 weeks successfully and can see 2 weeks of programming for all my enabled channels from inside of the TVHeadEnd web interface in Electronic Program Guide. However, from OSMC/TV/Guide, the listing looks good (again, for all channels) till ~4PM today and then everything goes to "No information found". I checked the xmltv.xml file and, as expected, the data was there. Good news is it seems zap2epg is working as it should and xmltv.xml located in the ..../userdata/addon_data/script.... directory works great, as well. So, this sounds like something not coming from zap2epg.....still....sighhhhhhh......
tvh2kodi.....
I mentioned this in a previous posting but it must have gotten lost in the zap2epg noise.
When I try to set the cron thru this addon, I can go thru the motions to make the change in the on-screen keyboard and then hit "Done". However, the new/edited value is not saved. The setting remains unchanged.
zap2epg or tvh2kodi...
Can't remember which one this was coming from....if I go into the information function of the specific addon, I get a whole bunch of numbers (which look like versions) in the top half of the screen over the normal info (description, version, etc.). Looks like a mess.
If I get the chance, I'll check out which addon it was and update here.
Cheers....
Original (11/13/17.0)
You're welcome, as usual.....except this getting to be like a "circle jerk"
Something is still a bit off or has changed somewhere (again...arghhhhhh). Back to the xmltv.xml file not being updated at all. If I run tv_grab_zap2epg directly on the RPI 3, I get a short (or no) download time and then what is currently in xmltv.xml (cat $XMLTV_OUTPUT from the last successful update) screams across the screen. Properties of the zap2epg.log file shows the file's been modified when I run tv_grab_zap2epg but with 0 bytes. xmltv.xml shows a date from the last successful update a couple of days ago.
I went back to V0.3.1 (zpa2epg.py and default.py) thinking V0.3.2 might have had some issue, but no change. So, back on V0.3.2 and time to see what else it might be.
So, now I've got TV/Guide and web-based TVHeadEnd connected to the xmltv.xml file just fine, but I can't seem to update (or download data for) xmltv.xml.
Keep you posted....any suggestions appreciated....cheers...
(2017-11-13, 02:37)edit4ever Wrote: Thanks for testing - do note that since the current server that zap2epg pulls from is not providing the subchannel numbers - tvheadend will not automatically map the epg source to the channels. (unless the ATSC station transmitted service name matches the generic fcc name of KABCDT2, KNBCDT3, etc) So you may need to double check the mapping - which it sounds like you already did.
Hopefully they will add the subchannel numbers soon - seems weird to have a guide where the channel numbers don't match what exists in the real world.
