• 1
  • 6
  • 7
  • 8(current)
  • 9
  • 10
  • 48
Zap2xml for ATSC in OpenELEC
Just as I thought - it is generally getting through an additional 4 sets of downloads per run. (except for on of them which looks like the zap2it server hadn't reset in time). This means 1 day can be added for each run before it needs to take a break. I'll have to see if I can create a specific pause for that.

In the meantime - as of the last log you posted it looked like it had reached number 28, which is just over 6 days. Try setting your request to 6 days and see if it completes. If it does, change it to 7 days and rerun. If that works, move to 8. etc. I assume you had this set to a 1 sec delay - so leave it how you had it set.

Thanks again for experimenting!
Current Kodi addon projects: zap2epg, sd4tvh and tvh2kodi (tvh config from inside Kodi)
Testing ATSC single and dual tuners on RPi3 and the occasional s905 box
If you like my work you can buy me a coffee!
Reply
So, at some point, it will get all the info it needs to update the xmltv file?
Reply
That's my theory. Then once all 14 days are in...since it updates on its own twice a day it should work from then on. If that turns out to be true I just need to figure out how to get it through those first 14 days. :-)
Current Kodi addon projects: zap2epg, sd4tvh and tvh2kodi (tvh config from inside Kodi)
Testing ATSC single and dual tuners on RPi3 and the occasional s905 box
If you like my work you can buy me a coffee!
Reply
Testing now.

I believe you are correct. Each scan takes longer, even up to 10 minutes, I believe.
Reply
This is a really great addition to Kodi! Thanks to edit4ever for putting this together and to clarkss12 for the youtube video that helped me get everything installed.

I use this on my openelec box that mainly functions as a tvheadend server.

I also have openelec for raspberry pi 2 that I use as a client where my tv is.

The one problem I'm having is that the guide on the pi 2 machine is 1h ahead of time. The system shows the correct time but the guide is off. The server machine shows the correct time if viewing the guide in kodi there. Does anyone know something I can check?
Reply
(2016-07-20, 14:27)igbee Wrote: The one problem I'm having is that the guide on the pi 2 machine is 1h ahead of time. The system shows the correct time but the guide is off.

Can you confirm that the timezone is set correctly for your area? My first thought would be a daylight saving issue depending on what timezone you live in.
Current Kodi addon projects: zap2epg, sd4tvh and tvh2kodi (tvh config from inside Kodi)
Testing ATSC single and dual tuners on RPi3 and the occasional s905 box
If you like my work you can buy me a coffee!
Reply
The timezone was correct but last night I decided to reset the guide data by having kodi reimport it from tvheadend and this has fixed the problem!
Reply
I have setup zap2xml grabber setup and I can see it in my grabber but it does not generate any data. I am using a Pi3 with an HDhomerun and Openelec. I am able to install zap2xml and I get "XMLTV: tv_grab_zap2xml is a simple wrapper for zap2xml.py" in the internal grabber but that is it. I get no channel or tvguide data.

TV headend delivers this;
2016-08-21 15:17:29.908 spawn: Executing "/storage/.kodi/addons/tools.module.zap2xml/bin/tv_grab_zap2xml"
2016-08-21 15:18:07.216 /storage/.kodi/addons/tools.module.zap2xml/bin/tv_grab_zap2xml: grab took 38 seconds
2016-08-21 15:18:07.248 /storage/.kodi/addons/tools.module.zap2xml/bin/tv_grab_zap2xml: parse took 0 seconds
2016-08-21 15:18:07.248 /storage/.kodi/addons/tools.module.zap2xml/bin/tv_grab_zap2xml: channels tot= 94 new= 0 mod= 0
2016-08-21 15:18:07.248 /storage/.kodi/addons/tools.module.zap2xml/bin/tv_grab_zap2xml: brands tot= 0 new= 0 mod= 0
2016-08-21 15:18:07.248 /storage/.kodi/addons/tools.module.zap2xml/bin/tv_grab_zap2xml: seasons tot= 0 new= 0 mod= 0
2016-08-21 15:18:07.248 /storage/.kodi/addons/tools.module.zap2xml/bin/tv_grab_zap2xml: episodes tot= 0 new= 0 mod= 0
2016-08-21 15:18:07.248 /storage/.kodi/addons/tools.module.zap2xml/bin/tv_grab_zap2xml: broadcasts tot= 0 new= 0 mod= 0
Any help would be greatly appreciated
Reply
In the tvheadend web interface...have you gone to the channel/epg - channels tab and set the epg source for each channel? This is how tvheadend knows which data stream to connect to which channels.

One other note - when setting up for the first time - if you have a lot of channels, don't turn on the options to download extra details or picons. This will overload the zap2it server and cause the download to fail. once you have basic data, you can start turning on the other options. You may have to add the delay if you have a lot of channels and want the extra details and picons to download.

If you have done that and still don't have any data - then I'll need you to post a copy of the xmltv.xml file.
Current Kodi addon projects: zap2epg, sd4tvh and tvh2kodi (tvh config from inside Kodi)
Testing ATSC single and dual tuners on RPi3 and the occasional s905 box
If you like my work you can buy me a coffee!
Reply
The strange part is when I click on EPG Source in channel tab it is empty. I checked the XMLTV file and there is information in it.

Do I need to set any XMLTV setting in openelec? right now it is set to XMLTV Configuration is set to None.
Reply
That did it, I didn't download any extra data and it all went through. Thanks so very much.
Reply
I've been using this for about five weeks and it has worked great. Sometime last night it dumped the current EPG info I had and started returning nothing. Has something changed with zap2it?
My channels are all set
My channels all have epg sources
my EPG grabber is set as XMLTV: tv_grab_zap2xml is a simple wrapper for zap2xml.py
***
I did a bit of digging and found /.kodi/userdata/addon_data/tools.module.zap2.xml and found that the last time xmltv.xml was updated was Aug 5th (about 16 days ago). That might explain why I'm not seeing current info in my EPG.
I guess this changes my question slightly to: Does anyone have any ideas why the scrapper stopped updating?
I checked the settings.xml and everything looks current.
Reply
rcrh - If you could post a copy of the zap2xml log file I can take a look to see what is happening. There is a version of the file located in the addon folder under userdata folder.
Current Kodi addon projects: zap2epg, sd4tvh and tvh2kodi (tvh config from inside Kodi)
Testing ATSC single and dual tuners on RPi3 and the occasional s905 box
If you like my work you can buy me a coffee!
Reply
(2016-08-21, 23:41)drhoeh Wrote: That did it, I didn't download any extra data and it all went through. Thanks so very much.

The key here is that zap2it will stop the transfer if there are too many http requests. So, if you want to download extra details and picons and 14 days of data for a lot of channels (like a cable setup instead of ATSC setup) then you need to do the following:
  • set the number of days to 3
  • force the grabber to run
  • turn on the extra details and picons and add a 1.5 second delay in options
  • force the grabber to run - if the grabber fails, increase the delay or lower to 2 days and run again
  • If the grabber worked, you can now add 2 more days and force the grabber to run again
  • If that works, continue adding a couple of days until you get to the number you want

Keep in mind that the grabs will take a lot longer with extra details, picons and a delay turned on. The key to getting a successful grab is to not overwhelm the zap2it server. If you add a couple of days each time and rerun, you will add to your database cache and it only needs to download the new data. Once you get to the 14 days, each day it will only need to download the new data for the day and will not overwhelm, so you can leave it set to 14 from that point on.

I would also suggest changing the time in the internal grabber cron setting. You will see it set to: 4 */12 * * * This means the grabber will run at 12:04am and 12:04pm. Since everyone shouldn't download at the same time, I would suggest changing the first number (4) which is the minutes to another number -- this way different users are grabbing data at different times.

This way to grab epg is really best for an ATSC setup. If you want to download a lot of channels for a full cable setup, I would suggest using schedules direct (free trial - then $25/yr) and try the following grabber:

https://www.dropbox.com/s/kvqx4wst32lot3...1.zip?dl=0

Good luck!
Current Kodi addon projects: zap2epg, sd4tvh and tvh2kodi (tvh config from inside Kodi)
Testing ATSC single and dual tuners on RPi3 and the occasional s905 box
If you like my work you can buy me a coffee!
Reply
(2016-08-22, 01:37)edit4ever Wrote: rcrh - If you could post a copy of the zap2xml log file I can take a look to see what is happening. There is a version of the file located in the addon folder under userdata folder.
Here it is. Thanks in advance for anything you see.
Reading config file: /storage/.kodi/addons/tools.module.zap2xml/.zap2xmlrc

[1/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1471816800000.html.gz
[2/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1471838400000.html.gz
[3/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1471860000000.html.gz
[4/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1471881600000.html.gz
[5/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1471903200000.html.gz
[6/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1471924800000.html.gz
[7/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1471946400000.html.gz
[8/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1471968000000.html.gz
[9/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1471989600000.html.gz
[10/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472011200000.html.gz
[11/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472032800000.html.gz
[12/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472054400000.html.gz
[13/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472076000000.html.gz
[14/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472097600000.html.gz
[15/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472119200000.html.gz
[16/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472140800000.html.gz
[17/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472162400000.html.gz
[18/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472184000000.html.gz
[19/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472205600000.html.gz
[20/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472227200000.html.gz
[21/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472248800000.html.gz
[22/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472270400000.html.gz
[23/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472292000000.html.gz
[24/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472313600000.html.gz
[25/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472335200000.html.gz
[26/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472356800000.html.gz
[27/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472378400000.html.gz
[28/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472400000000.html.gz
[29/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472421600000.html.gz
[30/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472443200000.html.gz
[31/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472464800000.html.gz
[32/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472486400000.html.gz
[33/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472508000000.html.gz
[34/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472529600000.html.gz
[35/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472551200000.html.gz
[36/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472572800000.html.gz
[37/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472594400000.html.gz
[38/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472616000000.html.gz
[39/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472637600000.html.gz
[40/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472659200000.html.gz
[41/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472680800000.html.gz
[42/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472702400000.html.gz
[43/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472724000000.html.gz
[44/56] Parsing: /storage/.kodi/addons/tools.module.zap2xml/cache/1472745600000.html.gz
Exception
error<type 'exceptions.TypeError'>
Traceback (most recent call last):
File "/storage/.kodi/addons/tools.module.zap2xml/zap2xml.py", line 1992, in <module>
main()
File "/storage/.kodi/addons/tools.module.zap2xml/zap2xml.py", line 1902, in main
parseGrid(fn) #data read in and unicode it
File "/storage/.kodi/addons/tools.module.zap2xml/zap2xml.py", line 1082, in parseGrid
p.feed(b)
File "/home/stephan/projects/openelec-6.0/build.OpenELEC-Nvidia_Legacy.x86_64-6.0.3/Python-2.7.3/.install_pkg/usr/lib/python2.7/HTMLParser.py", line 114, in feed
File "/home/stephan/projects/openelec-6.0/build.OpenELEC-Nvidia_Legacy.x86_64-6.0.3/Python-2.7.3/.install_pkg/usr/lib/python2.7/HTMLParser.py", line 158, in goahead
File "/home/stephan/projects/openelec-6.0/build.OpenELEC-Nvidia_Legacy.x86_64-6.0.3/Python-2.7.3/.install_pkg/usr/lib/python2.7/HTMLParser.py", line 324, in parse_starttag
File "/storage/.kodi/addons/tools.module.zap2xml/zap2xml.py", line 704, in handle_starttag
globals()['on_%s' % tag](self, tag, attrs)
File "/storage/.kodi/addons/tools.module.zap2xml/zap2xml.py", line 323, in on_td
if re.search("^MV",cp):
File "/home/stephan/projects/openelec-6.0/build.OpenELEC-Nvidia_Legacy.x86_64-6.0.3/Python-2.7.3/.install_pkg/usr/lib/python2.7/re.py", line 142, in search
TypeError: expected string or buffer
Reply
  • 1
  • 6
  • 7
  • 8(current)
  • 9
  • 10
  • 48

Logout Mark Read Team Forum Stats Members Help
Zap2xml for ATSC in OpenELEC4