RIght - just created some screencasts showing PleXBMC in action. There are 4 videos and they are all available in the first port : but i’ll link to them here as well:
You can also see two extra videos:
[list]
[] PleXBMC: Install and basic usage (using stock confluence skin)
[] PleXBMC: Quartz3 and advanced usage
[] PleXBMC: Remote playback via Plex/Web
[] PleXBMC: On the Raspberry Pi
[/list]
Only just gotten back to looking at this. I updated to the latest version of PMS (0.9.7.12), and now PleXBMC Helper has started working! I've added your new repo, and updated to the latest versions of everything, and its still working after that too :-)
The other thing I'm observing now is this. If the Helper is happily registered with the PMS on my desktop, and I restart the Raspberry Pi, the registration doesn't succeed after the reboot. At that point, I have to restart PMS before the registration will work again. In general, restarting the PMS is fine, as the registration succeeds afterwards.
Is that a PMS issue, or is that something that could be addressed in the helper?
Thanks for all your help so far!
From stuff I’ve seen, there appears to be some strange network related happenings with the current Plex release. I’m going to start a thread to see if there is a common fault v
Just to add to this, I've noticed now that the Helper actually loses registration with PMS even if the Pi isn't restarted. It seems that after a while (minutes rather than hours) the Helper is no longer able to detect PMS, and I have to restart PMS for the Helper to see it again :(
First time poster but just installed this last night on my Pi running XBIAN with the stable 12 release of Frodo.
Getting lots of errors when trying to run the app
13:02:04 T:2702480448 NOTICE: HTTP response error: 401 Unauthorized
13:02:06 T:2702480448 NOTICE: HTTP response error: 401 Unauthorized
13:02:07 T:2702480448 NOTICE: HTTP response error: 401 Unauthorized
13:02:08 T:2702480448 NOTICE: HTTP response error: 401 Unauthorized
Also seeing connection entries like this
13:02:25 T:3042099200 INFO: CheckIdle - Closing session to http://192.168.100.1 (easy=0xa3eab1b0, multi=(nil))
13:02:25 T:3042099200 INFO: CheckIdle - Closing session to http://192.168.100.1 (easy=0x2fd6780, multi=(nil))
13:02:25 T:3042099200 INFO: CheckIdle - Closing session to http://192.168.100.1 (easy=0xa519ccc8, multi=(nil))
13:02:25 T:3042099200 INFO: CheckIdle - Closing session to http://192.168.100.1 (easy=0x38446b0, multi=(nil))
For info, my PMS and XBMC are not even on this subnet so not sure where its getting this IP address from as this will be trying to open connections to my cable modem.
Anyone else getting anything similar?
Generally, if you are seeing 192.168.100.1 and it is a different net it is your cable modem (especially motorola).
I am sure this has been asked before, but I can’t seem to find the answer. How can I change the PleXBMC specific backgrounds for TV Shows and Movies? I tried changing the ones in /users/****/AppData/Roaming/XBMC/Addons/skin.aeon-nox.plexbmc/backgrounds and then deleting the Textures6.db and Thumbnail folders, that worked for a while but a few months later PleXBMC seems to have defaulted back to the previous backgrounds (the yellow stadium seating and the Dog on TV), perhaps from an update?
I have updated XBMC to Frodo and the PleXBMC repo to 2.0.2 so I have the newest version of PleXBMC.
All virgin cable modems respond on that IP address in the UK, it doesn't answer the question of why the plugin is opening connections to that IP as opposed to the configured IP of the system running PMS.
Not sure - the helper doesn't maintain a connection to the PMS, it sends a multicast packet every 5 seconds. This is picked up by the listening Media Servers.
In addition, the helper will send out a server discovery multicast packet, which asks for a response from all media servers. The media servers then send a packet with their details. It's these that the Helper checks against to verify registration.
If a registration packet isn't seen for a period of time, then the media server will assume it has disappeared and remove it.
What are you running the media server on? Not Windows 8 is it?
The only other thing I can think of, if you want to dig further, is to run some packet tracing on the Pi:
# sudo tcpdump -Av multicast
If you run this, you should see the multicast requests going out (both the client [HELLO] and the server discovery [M-SEARCH])
# sudo tcpdump -Av port 32414
If you run this, you should see the discovery going out and any returned server responses.
If these are blank, then the problem is that the responses are going out are not being replied too. After this, you would need to trace the media server machine, to see if these are being received.
You can configure custom fanart for sections in the media server. If you change these, then they should also change in PleXBMC. Note though, that it could take 24 hours to update, due to the image caching proces that XBMC uses.
PleXBMC will use the manual address to contact the media server. It then reads it's /server list and uses this to find all associated media servers. It is the IP address in this list that PleXBMC uses. Now, it should be the same, but a few people have reported some strange IP address related issues. I'm guessing the Plex has changed how it determine and records its IP connections.
Thanks hippojay, but I can’t seem to find where to do that in the Plex/web page. Also, is there anyway to only show new/unwatched flags instead of showing all the watched flags as well?
I've spent a bit more time, and I've managed to reproduce this. Looks like there are two way to do this, and I've only done one of them - I'm working on modifying the client update process. Hopefully this will have some positive results.
That sounds promising, thanks very much for spending more time on this :-)
To answer your previous question, I'm running the PMS on my Windows 7 desktop.
At this point would it be useful to post up the output from running tcpdump, or shall I just wait until you've had a chance to modify the update process and give that a try?
I seem to be getting a black screen when using PlexBMC (3,07) with the latest version of Xbian. It happens a few seconds after I open a video file, or randomly when I browse in plexbmc. Any tips on how to troubleshoot?
I have exactly the same situation. I am using ATV 1 with Openelec. I also can not go past the first level. Did you find a working solution? Any help will be appreciated.
EDIT: I read on the forum and tried restarting my MAC where the Plex Server was and this solved my problem. Thanks
hippojay:
Thank you also for this wonderful addon. Hope you have some solution for my problem as posted above.
Hi,
I’ve got this issue today (it was working fine yesterday :S) :
20:40:02 T:2833249344 NOTICE: PleXBMC -> getURL: url = 192.168.1.2:32400/servers<br />
20:40:02 T:2833249344 NOTICE: PleXBMC -> getURL: header = {}<br />
20:40:02 T:2833249344 NOTICE: PleXBMC -> getURL: ====== XML returned =======<br />
20:40:02 T:2833249344 NOTICE: <?xml version="1.0" encoding="UTF-8"?><br />
<MediaContainer size="1"><br />
<Server name="nas" host="nas.local" address="192.168.1.2" port="32400" machineIdentifier="ca4b66a98aad0110ece939bace252ef2c15c821f" version="0.9.7.11.386-d353989" /><br />
</MediaContainer><br />
20:40:02 T:2833249344 NOTICE: PleXBMC -> getURL: ====== XML finished ======<br />
20:40:02 T:2833249344 NOTICE: PleXBMC -> resolveAllServers: Resolved server List: [{'uuid': 'ca4b66a98aad0110ece939bace252ef2c15c821f', 'serverName': 'nas', 'owned': '1', 'token': None, 'master': 1, 'address': '192.168.1.2:32400', 'discovery': 'local'}]<br />
20:40:02 T:2833249344 NOTICE: PleXBMC -> resolveAllServers: Unique server List: [{'uuid': 'ca4b66a98aad0110ece939bace252ef2c15c821f', 'serverName': 'nas', 'owned': '1', 'token': None, 'master': 1, 'address': '192.168.1.2:32400', 'discovery': 'local'}]<br />
20:40:02 T:2833249344 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--<br />
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!<br />
Error Type: <type 'exceptions.UnboundLocalError'><br />
Error Contents: local variable 'aToken' referenced before assignment<br />
Traceback (most recent call last):<br />
File "/home/pi/.xbmc/addons/plugin.video.plexbmc/default.py", line 3829, in <module><br />
skin()<br />
File "/home/pi/.xbmc/addons/plugin.video.plexbmc/default.py", line 3178, in skin<br />
WINDOW.setProperty("plexbmc.%d.server.video" % (serverCount) , "http://"+server['address']+"/video&mode=7"+aToken)<br />
UnboundLocalError: local variable 'aToken' referenced before assignment<br />
-->End of Python script error report<--<br />
any ideas?
I already rebooted my rasp pi but didn't changed...
Ok - give this version a go [3.0.6](https://www.dropbox.com/s/i7xpj6cxxuh20ch/script.plexbmc.helper-3.0.6.zip). I've reworked the client registration code, so it responds to client discovery requests. This seems to work better. I've checked it against my OSX media server and I also install a media serve ron my windows 7 laptop, so I've checked it against that too (both running in parallel, which also worked).
I've also tested it against my Pi.
One thing to watch though, is that upgrading services on XBMC doesn't seem to wait until the service has actually stopped before starting it up again. It only gives me 5 seconds and this means that you may get the situation where the web server is unable to start as the port is in use.
Also changed is that I now pick up the XBMC network settings automatically, rather than having to be copied over into the helper settings. I've also set the helper to use the client name set in XBMC - so it shows up as the same device name as other services (such as airplay or over bonjour). These can all be overridden if needs be. It's be interested to see how you got on wit these as well if things go ok.
Yep, it's a bug. Sorry for that - not sure why it's only turned up now? If you were running an older version and just installed the repo, then I guess it would auto update your version to the latest. I'll put a fix together for it.
Yeah, I think that Plex is picking up some alternate network information, which when fed into PleXBMC causes it to go to the wrong address. I'm looking at how this happens and what is needed to fix.
This seems to happen more if you switch networks (VPN, dual connected, moving to a different network or putting a media server to sleep) - if this happens then a restart of the media server is needed.
I reinstalled Sunday the whole thing with USB stick on the pi, the repo and the helper (in order to remove the mac mini I was using As a client before and during the test of the pi). I've then changed version I guess...
Now I have to explain to my wife she'll have to wait for a serie ;-)
