Plugin: Schedules Direct EPG (not for v9)

[Slugger]

You're getting closer, believe it or not.

Go to the plugin settings, set the "capture sdjson data" setting to JSON, reload the web page. Zip up SageTV\plugins\sdepg\capture\ and send it to me (or just take a look at the files generated in there and see if the error pops out at you).

[Slugger]

Originally Posted by gdippel

I checked the log file and it does seem to be a permission issue. I log into my windows 7 sage server as a user as I run sage as a service under that user in order to connect to my media server via unc. Could that be the issue? I had no problem before the upgrade. I've attached the portion of the log from today.

So it looks like there is a program in your specific data feed that has an original air date value that is invalid. Send me an email (or your email addr via pm if you don't have mine) and I'll send you a patched jar file to try tomorrow at some point. So the invalid data appears to be halting my processing, which is why the tmp file is left around and is also probably why the file handle is left open and then that's why you get the access denied the next time it tries to run.

Anyway, get a hold of me by email and I'll get you a new jar sometime tomorrow to try.

[Slugger]

This morning's release forces an update of the sdjson-api library to the latest version, which addresses some bugs reported by other users.

However, after applying today's update and restarting Sage, you need to go to your SageTV\JARs folder in a command prompt and run:

dir sd*

There should only be two files in response:

sdepg.jar
sdjson-api-20131021.2-SNAPSHOT.jar

On my system, the Sage plugin manager did not delete the old sdjson-api-20131021.1.jar file, leaving both jars in there which will cause a classpath conflict. If the same happens to you, stop Sage, delete the sdjson-api-20131021.1.jar and restart Sage.

[Slugger]

Instead of repackaging sdepg just to force an upgrade of the sdjson-api jar, I'm just going to announce when a new api jar is released. Periodically, I'll update the sdepg plugin to force the issue, but I got a feeling there are going to be a few more of these over the next little while and this is way quicker to get things updated and done from my end.

So, all sdepg users should go to their installed library plugins in SageTV and update the sdjson-api library to 0.20131021.2.1; this fixes some bugs in the current api implementation in the client library.

[Slugger]

So Sage plugins can't have letters in their version numbers so when I release a snapshot version of the api jar, I have to wrap it around a Sage plugin version number that Sage will accept.

So the sdjson-api plugin version number is 0.20131021.2.1 and it provides the sdjson-api-0.20131021.2-SNAPSHOT jar. Furthermore, you must be sure that the Sage plugin manager is deleting the old jar and replacing it with the new one (I've seen quite a few instances in the last few weeks where Sage doesn't delete old jar and just drops the new one in, which will cause all kinds of problems, including slowly depleting EPG data.

In your JARs folder, this is what you should be seeing right now if you're up to date:

C:\Program Files (x86)\SageTV\SageTV\JARs>dir sd*.jar*
 Volume in drive C has no label.
 Volume Serial Number is B206-B9C8

 Directory of C:\Program Files (x86)\SageTV\SageTV\JARs

04/27/2014  15:02           195,074 sdepg.jar
05/01/2014  18:23            89,740 sdjson-api-0.20131021.2-SNAPSHOT.jar
               2 File(s)        284,814 bytes

Make note of the date (shown here as EDT) and size of these files. Any other sdjson-api* files in this dir must be removed. If this is ok on your system then something else is the problem and we need to go to the log files in SageTV\plugins\sdepg\logs\ for more details.

Note: The Sage STV won't alert you to new versions of the sdjson-api plugin because it's a library type plugin, which Sage doesn't alert you about. This is because library plugins are usually upgraded as the plugins that need them use them, which is correct. This is a special case, mostly because I'm a little lazy not wanting to repacking the actual plugin just to force the update of this one jar. This is why I'll announce new jar releases here as needed.

With that said, I made (non-critical) changes to the actual plugin code over the weekend, which means at some point this week I will have to repackage it all, which will force the issue. However, I'm still seeing the Sage plugin manager mess up the replacement of the jar files regularly, so people still need to verify that everything is right in their JARs folder after anything is upgraded.

[Slugger]

That last post was for gdippel, I got an email with a post of questions from him, but the post has since disappeared, which really loses the context of that reply.

[gdippel]

Sorry about that. I thought I had figured it out and didn't want to put my stupidity on public display. I realized that I had to update (Yes there was an update notification that I missed) and epg data is now populated. My question was basically about the naming of the jar, SNAPSHOT and and the fact that I had misread the earlier post.

[Slugger]

Here's the full update that will get all dependencies updated as needed. This update includes new versions of the sdjson-api and the sdjson-grabber app. This update should provide the stability required with the sdjson apis and allow me to proceed with some sdepg/SageTV specific updates over the next few weeks before shutting down my IDE and compiler for the summer.

Today my production box and test box both upgraded fine and the Sage plugin manager did everything right so I'm even more confused on what causes the problem, but just to be safe, here's what your JARs folder should look like after this upgrade:

C:\Program Files (x86)\SageTV\SageTV\JARs>dir sd*.*
 Volume in drive C has no label.
 Volume Serial Number is B206-B9C8

 Directory of C:\Program Files (x86)\SageTV\SageTV\JARs

05/08/2014  09:51           195,103 sdepg.jar
05/08/2014  09:40            91,965 sdjson-api-0.20131021.2-SNAPSHOT.jar
               2 File(s)        287,068 bytes

(File times are EDT.)

[HelenWeathers]

Slugger (or anyone who has an idea):

I just set up a new server with SageTV, the Sage provided Google weather update and the Schedules Direct epg plugin.

I have my OTA tuners and my HD-PVRs on two seperate lineups.

I can only get one lineup to work at a time. Remove HD-PVR source and OTA lineup updates. Remove OTA source and HD-PVR lineup updates.

With both sources set up only HD-PVR lineup updates (it's listed first in my SD lineups at Schedules Direct).

I suspect it might be a licensing issue (salicense folder was empty after install). I did try dropping my old lifetime license into the folder but it made no difference.

The sa license plugin is loaded (it loaded with sd plugin install).

Logs from sd and sage are attached.

Thanks,
Helen

[Slugger]

Hmm... something weird is going on.

So from the SageTV log:

Thu 5/8 22:09:02.179 [EPG@1bf0931] EPG needs an update in 0 minutes
Thu 5/8 22:09:02.179 [EPG@1bf0931] EPG attempting to expand Local 33161 (Antenna)
Thu 5/8 22:09:02.179 [Seeker@bc7f71] MARK 1 currRecord=null enc=AVerMedia 716x BDA Digital Capture #2 clients=[] ir=false
Thu 5/8 22:09:02.179 [Seeker@bc7f71] Seeker in AUTOMATIC mode nextRecord=null nextTTA=9223372036854775807
Thu 5/8 22:09:02.180 [Seeker@bc7f71] newRecord=null
Thu 5/8 22:09:02.180 [EPG@1bf0931] expand called on Local 33161 (Antenna) at Thu 5/8 22:09:02.179 expandedUntil=Thu 5/8 23:45:33.943 scannedUntil=Sun 8/17 2:12:55.807
Thu 5/8 22:09:02.181 [Seeker@bc7f71] NOTHING TO RECORD FOR NOW...
Thu 5/8 22:09:02.181 [EPG@1bf0931] EPG attempting to expand Comcast Dade Co./ North Miami - Digital Aventura (Cable)
Thu 5/8 22:09:02.181 [Seeker@bc7f71] MARK 1 currRecord=null enc=AVerMedia 716x BDA Digital Capture #3 clients=[] ir=false
Thu 5/8 22:09:02.181 [EPG@1bf0931] expand called on Comcast Dade Co./ North Miami - Digital Aventura (Cable) at Thu 5/8 22:09:02.181 expandedUntil=Wed 12/31 19:00:00.000 scannedUntil=Sun 8/17 2:12:55.807
Thu 5/8 22:09:02.181 [Seeker@bc7f71] Seeker in AUTOMATIC mode nextRecord=null nextTTA=9223372036854775807
Thu 5/8 22:09:02.181 [EPG@1bf0931] EPG Expanding Comcast Dade Co./ North Miami - Digital Aventura (Cable) at Thu 5/

So I see Sage saying it's requesting an update for each lineup, but in the sdepg logs:

2014-05-08 22:09:05,828 INFO  [EpgDownloader]: Downloading EPG data for lineup: 'Comcast Dade Co./ North Miami - Digital Aventura (Cable)'
2014-05-08 22:09:05,876 INFO  [EpgDownloader]: Requesting 9 channels

The updateGuide(), which is the method Sage calls, is only being called once. Is that correct for your cable lineup, just nine channels enabled?

I think I see a problem in my code where you get caught in this scenario where only one lineup will ever update iff you have multiple lineups being used on different tuners. Send me an email or pm me if you don't have my email and I'll get you a test jar over the weekend and see if I can't clean this up.

It's definitely not an salicense issue, don't worry about that.

[HelenWeathers]

Just to let everyone know......

Slugger sent me the jar, I installed it and have let him know that I have both my lineups now.

[Slugger]

The fix will be in the next release. ETA will probably be at least a week or two unless something critical arises before then. If you're in the same situation (multiple Sage inputs using different SD lineups) then PM me with your email address (or just send me an email directly) for the fixed jar, but I suspect I'd have heard if others were affected (it's a pretty big deal if you are affected), which is why I'm not going to rush out a release for this one fix.

[JerryB]

I don't know whether it's due to a change in the listings at SD or one of the recent changes in you software because of the SD changes but I've lost Star Ratings for shows in my SDEPG download.

[Slugger]

It's missing in the SD data feed. I've opened a ticket with them. When it's fixed on their end, the data should just reappear in Sage unless the format of the data also changes on SD's end then I'll need to update my code as well. We'll know more after SD fixes their end.

[BobbyDing]

Just restarted my PC using SD plugin, and since a few updates have occurred since last I ran it I figured I'd remove and re install the plugin. I ran into issues right off when first checking the SD lineups using Jetty. I get the Sage Web Interface and the SD drop menu, but when I select either of the two selections I get an error (attached). I do have the current jar files dated 5/8/14 in the SageTV\JARs folder...

sdepg.jar
sdjson-api-0.20131021.2-SNAPSHOT.jar

The java is Version 7, update 55.

It's probably something I'm doing wrong.... Any suggestions?

Thanks,

Bobby

[Slugger]

My guess is you do not have your SD id/pwd set in the plugin settings. If that's not it, you need to enable debug logging and set the sdjson capture data setting to all and try again (both in the plugin config settings). When it fails, zip up the contents of SageTV\plugins\sdepg\logs and SageTV\plugins\sdepg\capture and send it to me.

[BobbyDing]

Re-Entered username and password. Same error. Logs attached.

Thank you!

[Slugger]

Ah, you did not follow the upgrade instructions.

Specifically, you need to change the Base URL setting to https://json.schedulesdirect.org

Please read thru the entire doc to make sure you didn't miss anything else.

[BobbyDing]

Thanks Slugger,
Your correct, I did not do those steps (embarrassing). So I've gone through the steps completely (editing .properties and the base url) it still errors out when I go to set up the lineups. It may be that this machine has seen too many changes/mods/etc.. I think I'll just re install sage from scratch this weekend. In this case, I assume I should use the directions in the users guide (as a new setup)?

Thanks as always!

Bobby

[Slugger]

There really is no reason to reinstall Sage just to get this plugin working. If you completed all of the upgrade steps and it's still failing then let's see the new set of logs.