30 replies to this topic

[5stringdeath]

I've yet to clearly figure out why it needs Library updates since my Plex auto-updates .. however its nice to see some love from the SB dev

Thought someone might be interested

Attached Files

•  Screen shot 2011-03-27 at 8.13.41 PM.png   52.82K   132 downloads

[Isaac Ordonez]

That's pretty cool!

[Jonny Wray]

Could be mistaken, but I think Sander wrote that extension to sick beard

[Silent Assassin]

This feature is fantastic! I personally don't use Plex auto-updates b/c I don't want Plex searching through the file system unnecessarily (especially while I'm watching a movie) or making my external hard drives stay awake. So I love the fact that Sickbeard will call a Plex update only when there is new content downloaded.

[5stringdeath]

This feature is fantastic! I personally don't use Plex auto-updates b/c I don't want Plex searching through the file system unnecessarily (especially while I'm watching a movie) or making my external hard drives stay awake. So I love the fact that Sickbeard will call a Plex update only when there is new content downloaded.

I guess I can understand your USB/power issue, but what difference does it make if Plex updates while you're watching a movie? The old issues of stuttering etc because of this haven't affected me for some time now. Also I'm a bit confused ... I mean if you download a show with SB and sab moves it to the folder and Plex auto-updates, how is that any different than if you DL a show and then SB triggers the update? Its going to update either way :-)

It is a cool feature, but for me its only 1/2 the equation ... Couchpotato would need to do the same. But as I've said Plex auto-updates for me fine. With Sabnzbd the last part of the process is to move files to their relative folders in my Plex archives so everything is automated.

Now I haven't really played with the "notification" part of this only because I hate growl notifications when I'm watching media so I expect I would hate this as well. Right now I have SB send notifications to Prowl which go to my iPhone. Also Mynzb on the phone keeps a fine log of what's been dl'ing.

So many options! Its a good thing.

[Silent Assassin]

This is how I have my setup personally (and I recognize that everyone has different needs)...

I download nearly all of my content during the evening hours and view it during the day. So I don't want Plex trying to run updates over my enormous library (which does still cause a stutter because it is so large) during the day. Before the most recent version of Plex, updates would talk about 45 seconds on my mini. It's down to a few seconds since the most recent update. So, for me, I only want Plex updating when it needs to.

Also, during the day, if I do want to force a download, I want it to show up in Plex right away. And with this SickBeard update mechanism, I get exactly this. I use to have nearly the same code that the Sickbeard team integrating into their project pasted at the end of my sabToSickBeard.py script. I took it out this morning, and this is cleaner for SickBeard-acquired content.

You are 100% right that it's not the whole picture, though. I still have a script force a Plex update (via SABnzbd) when I download a movie (either manually or via CouchPotato) or if I get non-Sickbeard-TV-content (like a sports event). In both of those cases, I have SABnzbd groups that invoke a python script that hit the Plex update URL.

FYI - the code is here:

http://forums.plexap...visiting-a-url/

[Silent Assassin]

Does anyone else know why you'd ever want to update Plex on a SickBeard "snatch"? If the content hasn't been acquired yet, then it has nothing to update on? I was curious when I saw that option.

Also, why would you need to update a Plex "client" (not the Media Server)? I was confused by this option as well.

[Atrus]

Actually, the reason why it is working better now is because PMS actually checks if you are playing a video file, and if it does then the most CPU intensive tasks are not done. I don't think it does almost anything IF a movie is being played.

[vengeancegoon]

I figured I'd give it a shot but trying the test it keeps failing on me, I've tried localhost and the actual IP but still no go. To be honest I'm fine with Plex set up how it is but I'm always interested to try new stuff, especially as I'm hooking other people up to Plex, might be useful for others.

[n3n]

Gives me the following error:

"2011-03-28 21:48:19.807332 CP Server Thread-7 :: Update of show directory failed on 192.168.1.4:3000, trying full update as requested
"

Also it seems to connect to the client, not the PMS. Is this right ? Why is it asking for the PMS ip ?

[sander1]

Hey all!
Yep, I wrote the addon a while back, Midgetspy has pulled the code in and has changed a couple of things too. He asked me to test, but apparently the code already made it into the master branch
As somebody already said, everybody has different needs. I store my media on a network drive, Plex can't detect changes in the filesystem there. I also don't want to let Plex scan every x time (as I've explained here).

Also I'm a bit confused ... I mean if you download a show with SB and sab moves it to the folder and Plex auto-updates, how is that any different than if you DL a show and then SB triggers the update? Its going to update either way :-)

It really depends on how you set up things. I let SABnzbd do the downloading, but let Sick Beard do the moving and renaming, so I need (want) to let Sick Beard send the update signal to Plex, not SABnzbd.

It is a cool feature, but for me its only 1/2 the equation ... Couchpotato would need to do the same.

True, although this also depends on your setup. In my case, SABnzbd does send the update signal to Plex in case of movies. Since Sick Beard only downloads TV shows, it'll let Plex only update the TV part of your libraries.

Does anyone else know why you'd ever want to update Plex on a SickBeard "snatch"? If the content hasn't been acquired yet, then it has nothing to update on? I was curious when I saw that option.

This isn't update related. It send a message to Plex (I havent checked yet if this works at all)

Also, why would you need to update a Plex "client" (not the Media Server)? I was confused by this option as well.

The Plex Client can recieve messages (something like Growl) to notify you about anything. The "library update" signal will be sent to the Plex Media Server.

[Mikedm139]

It is a cool feature, but for me its only 1/2 the equation ... Couchpotato would need to do the same.

I've got CouchPotato updating Plex using the XBMC option. Works great! I can post details if anyone is interested and needs help.

[Driekes]

I would really like that!

[Silent Assassin]

If I'm not mistaken, the XBMC update method is only available in Plex v8 and earlier. With Plex v9, the update URL is different.

In Plex v8, I think the URL pattern was something like:

http://PLEX-IP:3000/xbmcCmds/xbmcHttp?command=ExecBuiltIn&parameter=XBMC.updatelibrary(video)

And in Plex v9, I think the URL pattern is:

http://PMS-IP:32400/library/sections/[x]/refresh[?force=1]

[Silent Assassin]

sander1,

I posted a note on the Sickbeard issue tracker re: Plex notification at http://code.google.c...detail?id=1195:

I enabled Plex notification, and it works properly. However, if I try the "Test Plex Media Server" button it says it failed. I checked in the log, and it looks like a Plex v8 (i.e. XBMC url pattern) command is issued. I guess you don't know whether the person is running Plex v8, v9, etc. So you issue both types of commands and let the wrong one fail? On update, it looks like you issue both v8 and v9 type commands. But on "test server", you only try v8?

So the person above to said that this didn't work for them is probably referring to the "test" button which actually isn't working with my setup either, but actual updates are working after successful Sickbeard downloads.

Here is my Sickbeard debug log when the "Test Plex Media Server" button is pressed. I'm running Plex v9 - so this URL won't work for me:

Mar-29 06:57:26 INFO     CP Server Thread-3 :: Warning: Couldn't contact XBMC HTTP server at : 
Mar-29 06:57:26 DEBUG    CP Server Thread-3 :: Contacting XBMC via url: http:///xbmcCmds/xbmcHttp/?parameter=Notification%28Test+Notification%2CTesting+Plex+notifications+from+Sick+Beard%29&command=ExecBuiltIn
Mar-29 06:57:26 DEBUG    CP Server Thread-3 :: Encoded command is parameter=Notification%28Test+Notification%2CTesting+Plex+notifications+from+Sick+Beard%29&command=ExecBuiltIn
Mar-29 06:57:26 DEBUG    CP Server Thread-3 :: Sending notification to XBMC via host: username:  password: 
Mar-29 06:57:26 DEBUG    CP Server Thread-3 :: Sending notification for Testing Plex notifications from Sick Beard

[Mikedm139]

If I'm not mistaken, the XBMC update method is only available in Plex v8 and earlier. With Plex v9, the update URL is different.

In Plex v8, I think the URL pattern was something like:

http://PLEX-IP:3000/xbmcCmds/xbmcHttp?command=ExecBuiltIn&parameter=XBMC.updatelibrary(video)

And in Plex v9, I think the URL pattern is:

http://PMS-IP:32400/library/sections/[x]/refresh[?force=1]

I'm not at my computer right now, so I don't have screen shots or exact details. In the CP settings, all you need to do is enter the PMS update url

http://PMS-IP:32400/library/sections/[x]/refresh[?force=1]

in where CP asks for the XBMC host. To avoid unneccesary scanning and metadata re-downloading, I recommend leaving the 'force' option off.

[Driekes]

Does anyone else know why you'd ever want to update Plex on a SickBeard "snatch"? If the content hasn't been acquired yet, then it has nothing to update on? I was curious when I saw that option.

Also, why would you need to update a Plex "client" (not the Media Server)? I was confused by this option as well.

I have the same problem. Any idea what the correct settings are? It works perfectly from Couchpotato!

[Mikedm139]

The client option sends an onscreen notification. You only 'need' it if you want the notifications. There are other options too, like Growl if that suits you better.

[dirRtyjoe]

CouchPotato has added native Plex support at a request I posted!! Check it out, seems to work great.

[5stringdeath]

The client option sends an onscreen notification. You only 'need' it if you want the notifications. There are other options too, like Growl if that suits you better.

I don't think the Growl notifications work still on the OSX version, due to something with Growl which hasn't been updated in awhile. I use the Prowl option in SB to send notifications to my iPhone though, and it works great. Its just a personal thing but I don't want/need any kind of on-screen notification popping up while I'm watching TV or a Movie

Here's the thread I'm referencing for the Growl problems on OSX:

http://code.google.com/p/sickbeard/issues/detail?id=112#c15