New EPG Option -open discussion
- Thread starter viper8690
- Start date
Yeah just read the many posts before yours. Funny that some people have the guide with kodi 17. I wish they would shed some light instead of just saying it works. I'm sure they tweaked it somehow to get the guide to work. I've already spent hours with no luck.
Hello Friends:
I hope you're all well.
I stumbled into the following issue today and was wondering if anyone else has experienced it.
Kodi was updated today from v16 (final) to v17.x (v17.0 Git:20170201-a10c504) on my Android box (Marshmallow), via the PlayStore. It was updated just like all other updatable apps were.
After the update completed, I launched Kodi and let it complete it's little first-run "Upgrading plugins ..." task. All was well. I simply needed to re-enable the Stalker Client (perhaps it was updated, too, as part of the "first-run" task). The Stalker Client version is now v2.8.3 (I don't recall what it was before the Kodi update). That works, too, thankfully but for this:
The EPG no longer loads. My stalker XML configuration file hasn't changed, so the http://yahyabell.com URL is still in effect.
The message is: Stalker Client: Unable To Load Guide
Has anyone else noticed this after upgrading to Kodi 17? I'm scratching my head.
Thank you!
Did you try using the Github address to which the Yahyabell url is redirected? I've seen that work with a couple of the K17 iterations...
Code:
https://raw.githubusercontent.com/viper8690/epg/master/guide.xmlDo you mean just point to that remote URL ? OK I will try it when I get home.
Is everything still done remotely ? Do I cache the guide locally ?
Many Thanks
Yes, use it as the remote url. In actual operation, the yahyabell address redirects to that Github address.
Hi @ilan:
Yes, I did last night as part of my troubleshooting. See the following post (it's just a few posts before this one).
When, in the below post, I said "used the underlying URL (at the deepest level -- with no indirections)", I meant that I used the canonical URL directly (no aliases -- i.e. the very one you refer to above) in my settings.xml. But as you can see from the debug log in the below post, doing so did not resolve the issue, sadly.
Code:
http://iptvtalk.net/showthread.php?24382-New-EPG-Option-open-discussion&p=175527&viewfull=1#post175527Thanks!
The issue is right below, but which KODI component is problematic (KODI or the Stalker Client), I don't know:
Code:
23:44:42.817 T:18446744072957880624 DEBUG: CCurlFile::Open - effective URL: <https://raw.githubusercontent.com/viper8
690/epg/master/guide.xml>
23:44:42.818 T:18446744073025038640 DEBUG: Thread FileCache start, auto delete: false
23:44:44.029 T:18446744073025038640 INFO: CFileCache::Process - Source read didn't return any data! Hit eof(?)Yes since both were updated it could be either one. Stalker client was disabled after the kodi upgrade.
I'm still waiting for those that posted it is working for them on 17 to chime in on what they did.
I'm still waiting for those that posted it is working for them on 17 to chime in on what they did.
Do the KODI and/or Stalker PVR Client people watch this? I imagine not since there are so many things to watch.
Any place to file a bug?Turned on cache guide data in stalker client using the github URL and it worked this morning.
Haven't tried the yahybell URL yet.
Haven't tried the yahybell URL yet.
There is no reason to change the URL if things are working. Ultimately, the yahya URL simply redirects to the Github address anyway.
Thank you for trying this and letting us know.
I tried it and can confirm that that does work:
- Cache enabled within a portal (I used portal-1)
- Cache duration is 24 hours
- My URL is the yahyabell one
I guess we don't know if this is a work-around that you found, or it's intended to work that way.
Btw, this could make sense: Previously we noticed (in my debug logs) that a data-format-error seemingly was being issued. If Kodi and/or the Stalker Client was reading from a cache area for the EPG, and we didn't have that enabled, then there was nothing there to read. Just speculation on my part.
P.S. A little off-topic, but I was happy to finally see Kodi-17 download-able (again from the Android PlayStore). Kodi-16 final was crashing on me every time I used it (multiple times per use session). It was really bad. But that is now gone with Kodi-17. \o/ So Kodi-17 configured with (the downloaded-able) Confluence skin is all goodness now.
The default kodi 17 skin is very smooth. I think it's time to move on from confluence. The channel and guide startup when going into kodi Seams a lot faster loading.
I gave Estuary a chance, but I think that's a matter of personal preference, not a technical advantage of one over the other (kodi and channel load times are the same). But, for example under Confluence, the way that the Stalker Client positions the channel list on the left-hand-side and the Now-playing-preview-video/inset-box on the upper-right-hand-side, isn't replicable in Estuary. There are other differences, too.
It's just preference.
I'm not in front of my set-up now. Take a look at the guide settings
System > Settings > TV > Guide
There should be a setting for the default click. Have it set to switch channels.
If you're clicking future shows, you obviously won't get it to launch.