How in the world do you get EPG working
Added by Antonio Battista over 8 years ago
Hi all,
First time TVHeadend user, and im excited to get it going 100%. Plan to cut the cord in a couple of months so i am starting the configuration now. I have it all setup except EPG. I have followed so many how-to's and EPG refuses to work. I have TV_Grab_file setup correctly, or at least i think i do, and I am using mc2xml to get my xmltv file setup. I have the file located at /home/hts/.xmltv/ and i also set that location in the tv_grab file, but it refuses to work. I keep getting the following in the log file. Any help would be greatly appreciated. I am Using a HDHomerun Connect, on Ubuntu 14.04, TVHeadend 4.0.8-3. BTW- I did use the options recommended on the 3rd to the last line.
Thanks all!!
2016-02-19 14:54:53.493 /usr/bin/tv_grab_na_dd: grab /usr/bin/tv_grab_na_dd
2016-02-19 14:54:53.496 spawn: Executing "/usr/bin/tv_grab_na_dd"
2016-02-19 14:54:53.697 spawn: using config filename /home/hts/.xmltv/tv_grab_na_dd.conf
2016-02-19 14:54:53.711 spawn: Password for tbattista: Use of uninitialized value $r in chomp at /usr/share/perl5/XMLTV/Ask/Term.pm line 66.
2016-02-19 14:54:53.989 spawn: Fetching from Schedules Direct Use of uninitialized value $local_pass in string at /usr/bin/tv_grab_na_dd line 719.
2016-02-19 14:54:54.000 mpegts: 743.028MHz in HDHomeRun - scan no data, failed
2016-02-19 14:54:54.000 subscription: 023F: "scan" unsubscribing
2016-02-19 14:54:54.111 spawn: Fetched 0 k/bytes in 1 seconds
2016-02-19 14:54:54.116 spawn: loading data:
2016-02-19 14:54:54.116 spawn: WARNING: error parsing DD xml:
2016-02-19 14:54:54.116 spawn: syntax error at line 1, column 49, byte 49 at /usr/lib/perl5/XML/Parser.pm line 187.
2016-02-19 14:54:54.116 spawn: at /usr/bin/tv_grab_na_dd line 928.
2016-02-19 14:54:54.116 spawn: ERROR: Bad XML from DD, cannot continue. Consider using --dropbadchar or Capture xml with --dd-data
2016-02-19 14:54:54.122 /usr/bin/tv_grab_na_dd: no output detected
2016-02-19 14:54:54.122 /usr/bin/tv_grab_na_dd: grab returned no data
Replies (3)
RE: How in the world do you get EPG working - Added by K Shea over 8 years ago
Antonio Battista wrote:
...and I am using mc2xml to get my xmltv file setup...
mc2xml stopped working a few months ago. Use zap2xml. See https://freetoairamerica.wordpress.com/2014/12/03/some-hints-for-getting-free-to-air-satellite-channels-into-the-electronic-program-guide-in-kodi-or-xbmc-or-another-frontend/ and post again if you have any questions.
RE: How in the world do you get EPG working - Added by Antonio Battista over 8 years ago
That was it! Thank you so much!!!
RE: How in the world do you get EPG working - Added by Mike Freeman over 8 years ago
Well, I'm having some major EPG problems. I had zap2xml working ok for a few years now (although I would prefer something else, since the result is barely usable at best), but this week it seemed to have gone offline. I made sure I had the latest zap2xml script. However, I get a bad hostname error. I also tried zap2xml's tvguide source. Same problem. I also tried a free trial of Schedules Direct (which I had problems with in the past). Again, bad hostname error. Here are the outputs of each of the scripts (omitting the login sections for security reasons, and that they don't offer any pertinent info):
zap2it (zap2xml):
Can't connect to tvschedule.zap2it.com:80 (Bad hostname) LWP::Protocol::http::Socket: Bad hostname 'tvschedule.zap2it.com' at /usr/share/perl5/LWP/Protocol/http.pm line 51.
tvguide:
Getting: http://mobilelistings.tvguide.com/Listingsweb/ws/rest/schedules//start/1461351600/duration/180 [Attempt 1] 500 Can't connect to mobilelistings.tvguide.com:80 (Bad hostname)
Schedules Direct: (sudo /usr/bin/tv_grab_na_dd --configure)
WARNING: error parsing DD xml: not well-formed (invalid token) at line 1, column 3, byte 3 at /usr/lib/perl5/XML/Parser.pm line 187 at /usr/bin/tv_grab_na_dd line 928 ERROR: Bad XML from DD, cannot continue. Consider using --dropbadchar or Capture xml with --dd-data
Running the same script with --dropbadchar makes no difference. Running the same script with --dd-data gives this info:
Can't connect to dd.schedulesdirect.org:80 (Bad hostname) LWP::Protocol::http::Socket: Bad hostname 'dd.schedulesdirect.org' at /usr/shar$
Any help would be appreciated! Thanks!