Not sure what the best method is (as I am not a dev) but I can confirm than using http://IP:PORT/status/sessions reports all remote/local users as well as the PMS owner, providing the clients they are using support the latest 0.9.8 release of PMS.
Well at least it appears to be working correctly for me and the script that I have.
Not sure what the best method is (as I am not a dev) but I can confirm than using http://IP:PORT/status/sessions reports all remote/local users as well as the PMS owner, providing the clients they are using support the latest 0.9.8 release of PMS.
Well at least it appears to be working correctly for me and the script that I have.
Strange, it didn't work for me when the client and server was on the same machine. And I wan't all clients no matter what version they are using since there are loads of different clients out there.
Strange, it didn't work for me when the client and server was on the same machine.
And I wan't all clients no matter what version they are using since there are loads of different clients out there.
It depends on what client you are using, the client needs to support it. PMC/PHT does not yet support it and will not show up there. Yet.
Yes, there are other clients that needs to get an update as well.
I have tested it with PHT and it works great.
It would be great if you could add the itemID to the websocket to instead of just the session id. It is already available for metadata related notifications and would be great for these playback notifications to.
"404 Not Found" -.- I have the latest version of Plex Media Server and I was clicking on the link on the same computer that the server is on.
Do you have 'Require authentication on local networks' enabled under WebPlex's Settings->myPlex->Advanced Settings. If you do you will need to add your myPlex user token to the API call:
Do you have 'Require authentication on local networks' enabled under WebPlex's Settings->myPlex->Advanced Settings. If you do you will need to add your myPlex user token to the API call: