Same here, nothing in the notify window or in the statistics page for now playing, but logging into the PMS (127.0.0.1) shows the user currently playing a movie. Was working fine before this latest update.
P.S. Love Plex Notify!! Thanks for all the hard work
No need to say I love PlexNotify too! :)
Not sure if that helps, but I see a lot of the following in the log file:
"Object reference not set to an instance of an object"
Thank you!
Can you send it to me?No need to say I love PlexNotify too! :)
Not sure if that helps, but I see a lot of the following in the log file:
"Object reference not set to an instance of an object"
Thank you!
Don't know if this has been reported earlier, but I have three users connected to my server using iPad minis, and everytime one of them watches a video, I get a notification at the end with "[User] has stopped watching [video] at 89.xx%". The same users watching the same videos from Plex/Web reports the file being stoppet at around 99%, as expected. Is this a problem with the combination of the Plex iOS app and iPad Minis, or is this a problem with PlexNotify? At least two of the iPad Minis are running different iOS versions, so that doesn't seem to affect it. Using a normal iPad or an iPad Air also reports the file being stopped at closer to 99%, so this only happens with iPad mini.
As others have mentioned, plex notify has stopped working for me. User activity no longer is showing up in the app.
Im working on the notification problem now, All sessions are still being recorded in the database so no data is lost. There is a logic problem with the notification engine.
Ok, I downloaded PMS 0.9.9.10 and tested the release with that version. I posted an update Alpha 83 that will hopefully address the notification issue. I also noticed that when I tried to manually browse to http://*ip*:32400/status/sessions the page did not return with the new PMS, so if it does not notify try and navigate to that page in your web browser to see if anything comes up.
no nofifications after update.also running 0.9.9.10.link showed 2 lines.a xml version and a mediacontainer size=0 line.
no nofifications after update.also running 0.9.9.10.link showed 2 lines.a xml version and a mediacontainer size=0 line.
ok.tried it again.1st time I tried it from my lg tv.this time I played a movie direct from plex web on my pcand it showed midiacontainer size=1 and below that list the movie.ect that is playing.still go no notifications from plexnofity.
Same problem here, notification window nor Pushover notifications working after update. Running PlexNotify on WS2012 R2. http://IP:32400/web/sessions returns the correct XML as far as I can see, at least it gives me the xml information of the media currently being played. "MediaContainer=9"
Statistics work just fine, but Notifications give nothing but blank. Running newest Plexpass PMS, 0.9.9.10.458.
Same problem here, notification window nor Pushover notifications working after update. Running PlexNotify on WS2012 R2. http://IP:32400/web/sessions returns the correct XML as far as I can see, at least it gives me the xml information of the media currently being played. "MediaContainer=9"
Statistics work just fine, but Notifications give nothing but blank. Running newest Plexpass PMS, 0.9.9.10.458.
There ya go.
I looked in my log file n its pretty much the same as above.after 83 update just application started.i can stiil upload if u want but I don't see anything that aint in log above.
I looked in my log file n its pretty much the same as above.after 83 update just application started.i can stiil upload if u want but I don't see anything that aint in log above.
No, Thats ok I am working on some leads right now. Thank you though, Its some kind of logic problem.
I've seen several people say that statistics works fine, and maybe some aspects of it does, but there is one aspect that does NOT work properly for me, and hasn't done so for at least the last two updates (possibly much longer). I'm talking about the "Log Of Events" command in the statistics page. I hadn't used that command for some time, but back when I did use it this command would always show me a number of events (set by the user defined limit) leading up to the current time. But that no longer works.
Now when I use that command it displays a number of events, using the same limit as before, but leading up to a time one week ago.
So yesterday, on June 03, I was able to view logged events up to May 27. And today on June 04 I can view logged events up to May 28.
I did try raising the limit far beyond the existing number of entries (I set it to 3000), but while this did increase the number of scrollable events, some of the events listed were not even in correct chronological order. (possibly a clue to the cause of the problem, if events for the recent week have been mis-sorted out of reach) I did eventually find some recent log entries, but these were all at the end of a list of over 2000 events, which forces me to always set the limit far beyond the reasonable, to ensure that recent events are included in the listing. And as a consequence, the program will ALWAYS have to process every single entry in the log, every time I open the "Log Of Events", as that is the only way to ensure access to recent events.
I don't think this problem is connected to the most recent update 0.0.0.83, which stopped all notifications, because I noticed it also before the latest one, when notifications that were correctly displayed for playing videos could not be found in the log (since that showed nothing less than a week old).
What you need to do here is obviously two things:
1: Ensure that the entry display limit (I like mine at 500) is applied backwards from current time. Thus my setting would ensure that the 500 latest events are displayed, rather than 500 ancient events (like it currently does).
2: Correct the event order, which is currently inconsistent.
I'm attaching two pictures to illustrate some of the incorrect ordering (there were other instances too).
This first picture shows the correct event order for the May-June transition. There's not much wrong in this one.
But it is part of the same total listing which also contains errors, which is why I include this one too, for reference.
The next picture shows incorrect ordering for several entries, and it should be noted that this is part of the same list as the previous picture, after scrolling further down in that list.
As you can see this incorrect ordering is not exactly random, but consists of an unwarranted grouping of old access events for a video listed directly after a recent such event. This might make sense for other report modes, but it makes absolutely no sense at all for a generic "Log Of Events". This should simply list each event in proper chronological order, and preferably 'reverse order' so as to ensure entry at the most recent events.
I do realize that I can get rid of those incorrectly ordered old entries placed after the most recent one, by activating the flag option "Only show latest event for each Video". But that would remove all the older entries for that video completely from the listing, which is NOT what I want.
What I want is for each entry to appear individually in correct chronological order. That is the only form of log which is useful to me. If it's not in order it's impossible to relate to other simultaneous events. And if an event is removed I obviously can't relate it to anything. This is particularly important for those videos which I frequently use in tests, such as the episode listed in the second picture above. It is perfectly normal for this video to appear several dozen times in a log, and for me it is important that each one of those entries is placed in correct chronological order, together with other events of the same time interval.
That option "Only show latest event for each Video" needs to be renamed and/or redefined.
If continuing to work as it currently works it needs two descriptions:
ON: Remove all entries for a video except the latest one. OFF: Group all old entries for a video after the most recent one.
Note however that both these modes of operation are USELESS to someone who needs all entries and chronological order.
What I would rather suggest is that you redefine AND rename this option.
Its new name could be something like "Group old entries for a video after the most recent one"
Its new ON behaviour should be similar to the current OFF behaviour (as it does group entries that way)
Its new OFF behaviour should simply leave all entries in correct chronological order without grouping or removing any of them.
If you absolutely need an option that removes entries completely (the current ON behaviour), then that needs to be a separate option.
The default must always be that all entries are retained and in correct order.
Btw:
Though my report today is rather negative, rest assured that my overall response to PlexNotify is not at all negative. :)
I like it a lot, which is the main reason why I care about having any faults of it corrected.
Best regards: dlanor
I've seen several people say that statistics works fine, and maybe some aspects of it does, but there is one aspect that does NOT work properly for me, and hasn't done so for at least the last two updates (possibly much longer). I'm talking about the "Log Of Events" command in the statistics page. I hadn't used that command for some time, but back when I did use it this command would always show me a number of events (set by the user defined limit) leading up to the current time. But that no longer works.
Now when I use that command it displays a number of events, using the same limit as before, but leading up to a time one week ago.
So yesterday, on June 03, I was able to view logged events up to May 27. And today on June 04 I can view logged events up to May 28.
I did try raising the limit far beyond the existing number of entries (I set it to 3000), but while this did increase the number of scrollable events, some of the events listed were not even in correct chronological order. (possibly a clue to the cause of the problem, if events for the recent week have been mis-sorted out of reach) I did eventually find some recent log entries, but these were all at the end of a list of over 2000 events, which forces me to always set the limit far beyond the reasonable, to ensure that recent events are included in the listing. And as a consequence, the program will ALWAYS have to process every single entry in the log, every time I open the "Log Of Events", as that is the only way to ensure access to recent events.
I don't think this problem is connected to the most recent update 0.0.0.83, which stopped all notifications, because I noticed it also before the latest one, when notifications that were correctly displayed for playing videos could not be found in the log (since that showed nothing less than a week old).
What you need to do here is obviously two things:
1: Ensure that the entry display limit (I like mine at 500) is applied backwards from current time. Thus my setting would ensure that the 500 latest events are displayed, rather than 500 ancient events (like it currently does).
2: Correct the event order, which is currently inconsistent.
I'm attaching two pictures to illustrate some of the incorrect ordering (there were other instances too).
This first picture shows the correct event order for the May-June transition. There's not much wrong in this one.
But it is part of the same total listing which also contains errors, which is why I include this one too, for reference.
The next picture shows incorrect ordering for several entries, and it should be noted that this is part of the same list as the previous picture, after scrolling further down in that list.
As you can see this incorrect ordering is not exactly random, but consists of an unwarranted grouping of old access events for a video listed directly after a recent such event. This might make sense for other report modes, but it makes absolutely no sense at all for a generic "Log Of Events". This should simply list each event in proper chronological order, and preferably 'reverse order' so as to ensure entry at the most recent events.
I do realize that I can get rid of those incorrectly ordered old entries placed after the most recent one, by activating the flag option "Only show latest event for each Video". But that would remove all the older entries for that video completely from the listing, which is NOT what I want.
What I want is for each entry to appear individually in correct chronological order. That is the only form of log which is useful to me. If it's not in order it's impossible to relate to other simultaneous events. And if an event is removed I obviously can't relate it to anything. This is particularly important for those videos which I frequently use in tests, such as the episode listed in the second picture above. It is perfectly normal for this video to appear several dozen times in a log, and for me it is important that each one of those entries is placed in correct chronological order, together with other events of the same time interval.
That option "Only show latest event for each Video" needs to be renamed and/or redefined.
If continuing to work as it currently works it needs two descriptions:
ON: Remove all entries for a video except the latest one. OFF: Group all old entries for a video after the most recent one.
Note however that both these modes of operation are USELESS to someone who needs all entries and chronological order.
What I would rather suggest is that you redefine AND rename this option.
Its new name could be something like "Group old entries for a video after the most recent one"
Its new ON behaviour should be similar to the current OFF behaviour (as it does group entries that way)
Its new OFF behaviour should simply leave all entries in correct chronological order without grouping or removing any of them.
If you absolutely need an option that removes entries completely (the current ON behaviour), then that needs to be a separate option.
The default must always be that all entries are retained and in correct order.
Btw:
Though my report today is rather negative, rest assured that my overall response to PlexNotify is not at all negative. :)
I like it a lot, which is the main reason why I care about having any faults of it corrected.
Best regards: dlanor
Thanks for the detailed report dlanor. I will look into the algorithm I use for sorting the log of events. you are correct after investigating on my side I do see that the entries are out of order.
The expected behavior is Newest -> Oldest.
oddly I just noticed mine stopped working as well, and now it won't log anything at all, tried an uninstall and a reinstall but nothing is being propagated to logs or statistics, what's the best way to start from scratch again?
oddly I just noticed mine stopped working as well, and now it won't log anything at all, tried an uninstall and a reinstall but nothing is being propagated to logs or statistics, what's the best way to start from scratch again?
if you want to start over just rename/delete the Plex Notify directory in C:\Programdata when plex notify is off.
Ok I did that and my statistics still are not being updated, when I log into PMS I see activity on the activity page, but plex notify is not seeing any activity happening, do you have any idea where I could start for troubleshooting? I just installed the latest version.
