For the ATSC version of the wintv-dualhd - using afl's current beta 6 release - I'm getting as far as the input extension initialized - but it never loads the dvb frontend.
Here's an excerpt from dmesg: [ 7.143377@3] usb 1-1.1: New device HCW 955D @ 480 Mbps (2040:026d, interface - Pastebin.com
Any thoughts on what could be holding back the frontend from loading??
ok - let's try something.
If you can edit the zap2xml.py file - look at the following section starting at line 341:
if cp != -1 and "-D" in options:
fn = os.path.join(cacheDir,cp + ".js.gz")
if not os.path.isfile(fn):
data = getURL(urlRoot + "gridDetailService?pgmId=" + cp)
wbf(fn, data)
log.pout("[D] Parsing: " + cp,'info')
parseJSOND(fn)
if "-I" in options:
fn = os.path.join(cacheDir,"I" + cp + ".js.gz")
if not os.path.isfile(fn):
data = getURL(urlRoot + "gridDetailService?rtype=pgmimg&pgmId=" + cp)
if data: #sometimes we fail to get the url try to keep going
wbf(fn, data)
log.pout("[I] Parsing: " + str(cp),'info')
parseJSONI(fn)Change it to the following:
if cp != -1 and "-D" in options:
fn = os.path.join(cacheDir,cp + ".js.gz")
if not os.path.isfile(fn):
data = getURL(urlRoot + "gridDetailService?pgmId=" + cp)
wbf(fn, data)
log.pout("[D] Parsing: " + cp,'info')
if os.path.isfile(fn):
parseJSOND(fn)
if "-I" in options:
fn = os.path.join(cacheDir,"I" + cp + ".js.gz")
if not os.path.isfile(fn):
data = getURL(urlRoot + "gridDetailService?rtype=pgmimg&pgmId=" + cp)
if data: #sometimes we fail to get the url try to keep going
wbf(fn, data)
log.pout("[I] Parsing: " + str(cp),'info')
if not os.path.isfile(fn):
parseJSONI(fn)I'm thinking if we only parse if the file exists - that may solve the error. The change is for both the program details and the program icon downloads.
Let me know if you are able to test.
I use expresszip - you should have the a file with the same name and just the .js extension.
That file can be opened by any text editor - although I use atom as it is built for looking at code.
BTW - Should the XXXXX.js.gz files be empty once my tvguide.xml file has been updated?
No - the files in the cache folder are just the downloads. They always have their data...They just need to be uncompressed first.
The xxxxxx.html.gz files contain the basic grid in 6 hour chunks. So if you have set the addon to download 1 day, you will have 4 of those files. When you have either the xtra description download or the program icon download enabled - the program parses (scans) those files and pulls the episode information and uses that to download the extra program details (generating the xxxxxxxxx.js.gz file) and the episode program icon (generating the Ixxxxxxxxx.js.gz file). Then all of that info is parsed to generate the final xmltv.xml file.
Apparently you're having an issue where it wants to download the xtra program detail or program icon and screener says the file doesn't exist. In theory the program should just move on - but apparently there is a piece of code missing. The weird thing is that should never happen. If there is an episode scheduled, it has a number and should have information to download. It's as though screener has the worng episode number in the program schedule for on of the programs in your listing.
Anyway - we'll keep trying to fix it! (or if you want - you can just get the schedules direct service for $25 for the year. That addon works great and has lots of good data!)
Wow - you have a big list of stations! If you're not actually using all 79 stations, you might want to edit the list down so only what you need is downloaded.
Let me know how your testing goes. In the meantime, I'll still try to look for any issues with the falied download section of the code. Thanks for the update!
That looks like it failed when it couldn't download the EP024717260011 episode information. That file doesn't exist - if you try to open the link screener gives you an error. I'll need to look through the code - it should have a way to deal with failed downloads, but something seems like it isn't working for you. Let's find out what program this is. If you open the .html.gz files you can search for EP024717260011 and see what show it is. Then we can go onto the screener site and see if the data there works or not.
I don't have OSMC, I run LE - although I believe they are mostly the same. I am running the latest LE 7.95 beta 2, which is kodi 17, on a raspberry pi 3 and it all is running fine. I don't seem to be able to duplicate the issue on my end. It likely just means there is a problem with the screener listing in your market - but the program should be able to handle that...so on to investigating!
Using afl's new build it seems the ATSC version of the Hauppauge wintv-dualhd gets loaded - but does not get the front end functioning. It is not seen in tvheadend. Here's a part of the dmesg on boot:
[ 7.811657@2] usb 1-1.1: em28174#0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x547901ca
[ 7.811670@2] usb 1-1.1: em28174#0: EEPROM info:
[ 7.811675@2] usb 1-1.1: em28174#0: microcode start address = 0x0004, boot configuration = 0x01
[ 7.818909@2] usb 1-1.1: em28174#0: AC97 audio (5 sample rates)
[ 7.818922@2] usb 1-1.1: em28174#0: 500mA max power
[ 7.818927@2] usb 1-1.1: em28174#0: Table at offset 0x27, strings=0x0a72, 0x187c, 0x086a
[ 7.820845@3] 8021q: 802.1Q VLAN Support v1.8
[ 7.821069@2] usb 1-1.1: em28174#0: Identified as Hauppauge WinTV-dualHD ATSC (card=100)
[ 7.826431@2] tveeprom: Hauppauge model 204101, rev B2I6, serial# 11511331
[ 7.826441@2] tveeprom: tuner model is SiLabs Si2157 (idx 186, type 4)
[ 7.826446@2] tveeprom: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
[ 7.826450@2] tveeprom: audio processor is None (idx 0)
[ 7.826453@2] tveeprom: has no radio, has IR receiver, has no IR transmitter
[ 7.826464@2] usb 1-1.1: em28174#0: dvb set to isoc mode.
[ 7.826664@2] usb 1-1.1: em28174#1: chip ID is em28174
[ 7.912229@1] wifi_platform_bus_enumerate device present 1
[ 7.912240@1] ======== Card detection to detect SDIO card! ========
[ 7.912245@1] sdio_reset_comm():
[ 8.910062@1] usb 1-1.1: em28174#1: EEPROM ID = 26 00 01 00, EEPROM hash = 0x547901ca
[ 8.910073@1] usb 1-1.1: em28174#1: EEPROM info:
[ 8.910078@1] usb 1-1.1: em28174#1: microcode start address = 0x0004, boot configuration = 0x01
[ 8.918557@1] usb 1-1.1: em28174#1: AC97 audio (5 sample rates)
[ 8.918566@1] usb 1-1.1: em28174#1: 500mA max power
[ 8.918572@1] usb 1-1.1: em28174#1: Table at offset 0x27, strings=0x0a72, 0x187c, 0x086a
[ 8.919284@1] usb 1-1.1: em28174#1: Identified as Hauppauge WinTV-dualHD ATSC (card=100)
[ 8.922158@1] tveeprom: Hauppauge model 204101, rev B2I6, serial# 11511331
[ 8.922203@1] tveeprom: tuner model is SiLabs Si2157 (idx 186, type 4)
[ 8.922209@1] tveeprom: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
[ 8.922213@1] tveeprom: audio processor is None (idx 0)
[ 8.922217@1] tveeprom: has no radio, has IR receiver, has no IR transmitter
[ 8.922228@1] usb 1-1.1: em28174#1: dvb ts2 set to isoc mode.
[ 9.123843@1] usbcore: registered new interface driver em28xx
[ 9.137837@1] WARNING: You are using an experimental version of the media stack.
[ 9.137837@1] As the driver is backported to an older kernel, it doesn't offer
[ 9.137837@1] enough quality for its usage in production.
[ 9.137837@1] Use it with care.
[ 9.137837@1] Latest git patches (needed if you report a bug to [email protected]):
[ 9.137837@1] a02ff2e02bee64e9955dbfd8811874c3f3880f58 cx231xx: Fix TBS MAC reading.
[ 9.139963@1] usb 1-1.1: em28174#1: Registering input extension
[ 9.172191@1] Registered IR keymap rc-hauppauge
[ 9.173707@1] input: 1-1.1: em28174#1 IR as /devices/dwc2_b/usb1/1-1/1-1.1: em28174#1/rc/rc0/input4
[ 9.174330@1] rc rc0: 1-1.1: em28174#1 IR as /devices/dwc2_b/usb1/1-1/1-1.1: em28174#1/rc/rc0
[ 9.174849@1] usb 1-1.1: em28174#1: Input extension successfully initalized
[ 9.174857@1] usb 1-1.1: em28174#1: Registering input extension
[ 9.175369@1] Registered IR keymap rc-hauppauge
[ 9.178019@1] input: 1-1.1: em28174#1 IR as /devices/dwc2_b/usb1/1-1/1-1.1: em28174#1/rc/rc1/input5
[ 9.178556@1] rc rc1: 1-1.1: em28174#1 IR as /devices/dwc2_b/usb1/1-1/1-1.1: em28174#1/rc/rc1
[ 9.178873@1] usb 1-1.1: em28174#1: Input extension successfully initalized
[ 9.178879@1] em28xx: Registered (Em28xx Input Extension) extension
[ 9.185431@1] sdio: queuing unknown CIS tuple 0x80 (2 bytes)
[ 9.189980@1] sdio: queuing unknown CIS tuple 0x80 (7 bytes)
[ 9.192518@1] sdio: queuing unknown CIS tuple 0x80 (3 bytes)
[ 9.287945@3] sdio: clk 200000000 SDR mode tuning start
[ 9.288144@3] sdio: rx_tuning_result[0] = 10
[ 9.288322@3] sdio: rx_tuning_result[1] = 10
[ 9.288520@3] sdio: rx_tuning_result[3] = 10
[ 9.288699@3] sdio: rx_tuning_result[4] = 10
[ 9.288705@3] sdio: best_win_start =3, best_win_size =4
[ 9.288711@3] sdio: sd_emmc_regs->gclock=0x1000245,sd_emmc_regs->gadjust=0x2000
[ 9.288719@3] sdio: gclock =0x1000245, gdelay=0x0, gadjust=0x2000
[ 9.288725@3] [sdio_reinit] finishIs there something I can check to see if all firmware/drivers are loaded?
stepher Can you check your xmltv.xml file and see if the channel numbers have been replaced with "0"??
My test download of your lineup gave me that instead of the channel numbers, so I'm wondering if something changed with the way they list the channels. Since I run my system with the channel name first option enabled, that may be why I haven't had an issue.
ZipCode: 94086
Lineup? Do you mean which channels? If so, what's the easiest way to get that list to you?
I mean - Over The Air or Cable or Satellite??? Usually in each zipcode - there are multiple providers (lineups) to choose from. You likely selected this when you customized your channels on the zap2it/screener site.
It seems as if the 'xtra prgram details' option continues to present problems. As soon as I disabled it and went thru a reboot, my tvguide.xml file was updated as expected.I'll keep it turned off until if, and when, you've got a viable coding solution that works with 'xtra prgram details' enabled.
This is strange as it is running on two of my systems without issue. There must be some other code in your lineup that I don't have in mine.
What zipcode and lineup are you using? I'll try to recreate the issue on my end.
Cleared the cache (Just want to confirm you meant "~\.kodi\addons\script.module.zap2xml\cache\") of 20K+ items and restarted tvh. Results below (looks about the same). No updates or system changes that I initiated.
OK - let's try to narrow down the issue. Turn off the download extra program details option and let's see if it will pull basic guide info.
That's an interesting error - looks like the problem was specifically with this download: 1487102400000.html.gz
You can try deleting that file or all the XXXXXXXX.html.gz files from the cache folder and see if it gets better data.
I am still up and running on my system - so I don't believe there was a change to the Screener site that would have broken it.
I should probably look at adding a "delete cache" function in the program so when there are errors it can run a clena download.
Let me know if clearing the cache file works.
awesome - thanks for the update. If all is well after you get through a full week+ - I'll update the addon with the fix.
I know it is more a general question but I'm stuck. Which file I have to edit to change my samba shares?
/storage/.config/samba.conf
You should see a sample file in there to work off of. The config fodler should be shared already - so you can see and edit it from your other system.
File "/home/osmc/.kodi/addons/script.module.zap2xml/zap2xml.py", line 352, in on_td
data = getURL(urlRoot + "gridDetailService?rtype=pgmimg&pgmId=" + cp)
TypeError: cannot concatenate 'str' and 'int' objects
There must be some program numbers that have a character that is messing with the putting together of the string.
My guess is if we force that whoel section to use str(cp) it will fix it... try this starting at 348:
if "-I" in options:
fn = os.path.join(cacheDir,"I" + str(cp) + ".js.gz")
if not os.path.isfile(fn):
data = getURL(urlRoot + "gridDetailService?rtype=pgmimg&pgmId=" + str(cp))
if data: #sometimes we fail to get the url try to keep going
wbf(fn, data)
log.pout(" Parsing: " + str(cp),'info')
parseJSONI(fn)
[hr]
Strangely, when I look inside the xmltv.xml file, all programmes starts 10 days later. The 1st programme is due on the 26th of January. If I check on zap2it website, all the informations are there for today (the 16th of January).
That's really strange. The data on the zap2it site looks correct. The downloads happen as a complete station group in 6 hour blocks...so it shouldn't happen.
You could try deleting the xmltv.xml file and in the .kodi/addons/script.module.zap2xml/cache folder try deleting all of the files that end with .html.gz - these are the bulk guide data downloads. There shouldn't be that many (depending on how many days you set to download - each file is a 6 hour block) All the other files are the pictures and extra details if you've set those to download.
If you're trying to navigate these folders from a windows computer (instead of from ssh) you will need to add the .kodi folder to your samba.conf file. Open that file (or if you haven't made one yet - rename the samba.conf.sample file to samba.conf and open it) and add the following ta the bottom:
[kodi]
path = /storage/.kodi
available = yes
browsable = yes
public = yes
writable = yes
root preexec = mkdir -p /storage/.kodi
This will allow you to browse the .kodi folder from windows and easily get to the addons folder.
If you delete the cache files / reboot and let zap2xml run again I'm hoping it clears up. Otherwise - I'm not sure why that one channel would have strange data.
Glad you got it!
You can setup all the detail information you want in the zap2xml addon configure settings under the Extra Details Order tab.
Just put what ever you want and whatever separators you want and the show description will be updated to conatin all that info.
Again - once you make that change - you will need to rerun the internal grabber and if you want kodi to update it's epg to match. Reboot again.
Double check the epg source closely in the tvh web interface. There may be two channels with similar names/numbers.
enjoy!
How can I see if TVH really trigger the zap2xml (from what I see, that doesn't happens) ?
There is a tvh log called service.log in the tvh addon userdata folder. ((you can also watch this log when you rerun the internal grabber in the bottom log window of the web interface - click the double up arrows in the bottom right corner of the screen) In that log you should see something like:
2017-01-10 15:54:41.000 [ INFO] xmltv: /storage/.kodi/addons/script.module.zap2xml/bin/tv_grab_zap2xml: grab /storage/.kodi/addons/script.module.zap2xml/bin/tv_grab_zap2xml
2017-01-10 15:54:41.007 [ INFO] spawn: Executing "/storage/.kodi/addons/script.module.zap2xml/bin/tv_grab_zap2xml"
2017-01-10 15:56:32.363 [ INFO] xmltv: /storage/.kodi/addons/script.module.zap2xml/bin/tv_grab_zap2xml: grab took 111 seconds
2017-01-10 15:56:34.445 [ INFO] xmltv: /storage/.kodi/addons/script.module.zap2xml/bin/tv_grab_zap2xml: parse took 2 seconds
2017-01-10 15:56:34.446 [ INFO] xmltv: /storage/.kodi/addons/script.module.zap2xml/bin/tv_grab_zap2xml: channels tot= 25 new= 0 mod= 0
2017-01-10 15:56:34.446 [ INFO] xmltv: /storage/.kodi/addons/script.module.zap2xml/bin/tv_grab_zap2xml: brands tot= 0 new= 0 mod= 0
2017-01-10 15:56:34.446 [ INFO] xmltv: /storage/.kodi/addons/script.module.zap2xml/bin/tv_grab_zap2xml: seasons tot= 5545 new= 5545 mod= 5545
2017-01-10 15:56:34.446 [ INFO] xmltv: /storage/.kodi/addons/script.module.zap2xml/bin/tv_grab_zap2xml: episodes tot= 5778 new= 4001 mod= 4006
And once the xmltv.xml file is generated (I can see it when I launch zap2xml manually) when does TVH pick it up ?
If all of the above is seen in the tvh log - the zap2xml grabber ran, made the xmltv.xml file and tvh read that file in. There should now be data in the epg of the tvh web interface. If it did not complete there should be a zap2xml.log file in the script.module.zap2xml userdata folder. Check it and post the last items - which should be an error of some kind.
Finally, when/if TVH parse the xmltv.xml file, when will I see it in Kodi's TV Guide ?
This depends on how you have configured the pvr settings in kodi. Normally they only update every few hours - so to test, if you see data in the eog of the tvh web interface = just reboot kodi and it should load in.
Let me know what you find when you check the logs.