I wouldn't call that a "bug" and I am not sure you are understanding what it does correctly. It's showing you exactly what the end user is doing. It will only notify once if a user was playing an item, and them they pause it. It will not continue to notify if the user keeps it paused. It will also notify on the resume if of course you have push_resumed enabled.
You are correct, sir! I only had Paused enabled, not Resume - And one of my users kept pausing/resuming a video playback. Just a wierd coincidence.
I've also got Twitter working, so I am one happy camper. Thanks a bunch for this! Now onto PlexWatchWeb testing..
Regarding twitter, can I just add a new line in alert_format with 'new' as the definition?
I don't have the option to "format" recently added content the same as the others, since it doesn't really fit into the same criteria as the others. The code is pretty close to allow for it, but I will have to work that in and verify it. Of course the allowed variables will potential be different or just less since it's not a "now playing" item.
Edit: I meant to mention that I will look into this for next release.
Can you give me an example of what you want it to look like? For TV and Movies. That way I hopefully don't miss options you were looking for. I usually try to include all of them, but you never know.
Well, I'm clearly missing something. I thought it all worked together. Now I'm thinking their is a web part which reads the db and one on the local system that creates the db. I'm def missing something. ARG!
Well, I'm clearly missing something. I thought it all worked together. Now I'm thinking their is a web part which reads the db and one on the local system that creates the db. I'm def missing something. ARG!
Correct. You will always need to run plexWatch no matter what. The plexWatch/Web is a front end to display what plexWatch has gathered.
Got the Watching/Watched stuff going (by email) but I'm struggling with the "Recently Added". I just get an empty email with subject "New Movie". That's it.. Isn't there supposed to be more info?
You've gotten further than I have buddy. I'm still not sure if we have to schedule the exe to run every so often, or keep it running 24/7, and how to get it all talking.
I'll give you a hand (but I only know about email configuration);
I've downloaded the zip from github and the plexWatch.exe and config.pl-dist-win32 from the startpost and put them all in c:\plexwatch (extracted the zip offcourse).
Then I edited the downloaded config.pl-dist-win32 and made these changes (and saved it as config.pl)
## EMAIL -- multiple destinations are supported
'EMAIL' => {
'1' => {
'enabled' => 1, ## set to 1 to enable local EMAIL
'push_recentlyadded' => 1,
'push_watched' => 1,
'push_watching' => 1,
'push_paused' => 0,
'push_resumed' => 0,
'server' => 'mailserver.mydomain.nl', # your mail server
'port' => '25', # your mail server port defalt 25 (587 is also a good choice)
'from' => 'plex@mydomain.nl', # your From email address: 'user@domain.com'
'to' => 'mb@mydomain.nl', # Email address to receive notification: 'user@domain.com'
'username' => '', # AUTH if needed [optional]
'password' => '', # AUTH if needed [optional]
'subject' => '{user} {push_title} {title}', ## push_title is special for EMAIL (for now)
'enable_tls' => 0, # ENABLE for TLS support ( your smtp server must allow STARTTLS )
'alert_format' => {
'start' => '{title} [{streamtype}] [{year}] [{rating}] on {platform} [{progress} in] {ip_address} {all_details}',
'paused' => '{title} [{streamtype}] [{year}] [{rating}] on {platform} [{progress} in] [{percent_complete}%] {ip_address} {all_details}',
'resumed' => '{title} [{streamtype}] [{year}] [{rating}] on {platform} [{progress} in] [{percent_complete}%] {ip_address} {all_details}',
'stop' => '{title} [{streamtype}] [{year}] [{rating}] on {platform} for {duration} [{percent_complete}%] {ip_address} {all_details}',
},
},
'2' => {
'enabled' => 1, ## set to 1 to enable EMAIL
## fill in the rest if you need more then 1 email notification
},
},
};
Don't really know what the 1 and 2 is? Looks like I have to enable email twice?
After this I scheduled plexWatchNotify.vbs to run every five minutes. Then I watched a show and got nice emails about it ;-)
/edit
What I actually think the exe is doing is creating some sort of snapshot of the log file. (first run). If you run it again (second run), it just looks up what has changes in the log file since the previous run. And then does some email sending or pushing. And then this process is just repeated over and over again (hence, that's why you have to schedule it over and over again) That's why (I think) you should not run it 24/7 but run it every so often (I choose 5 minutes, because 1 minute is silly).
But perhaps I'm completely wrong here, I'm still learning :)
/edit2
And my question still stands, why do I only get a blank email saying "New Movie" in the subject? :)
Got the Watching/Watched stuff going (by email) but I'm struggling with the "Recently Added". I just get an empty email with subject "New Movie". That's it.. Isn't there supposed to be more info?
I'll add it as an issue. I have noticed the body is sometimes blank for recently added. That is a different process than all the other notifications ( watched, watching, paused, etc) so it's very possible there is some sort of bug in just the RA stuff.
You've gotten further than I have buddy. I'm still not sure if we have to schedule the exe to run every so often, or keep it running 24/7, and how to get it all talking.
I am not sure I could have made it any easier, but people here are friendly, so run through those steps and just ask any questions about issues you have. It should "just" work if you run it on the same server PMS is running.
A quick question for ljunkie. I noticed in the config file some new advanced parameters.
$watched_show_completed = 1; ## advanced config -- always show completed show/movie as it's own line
$watched_grouping_maxhr = 2; ## advanced config -- do not group shows together if start/restart is > X hours
How exactly should these be used, and are they working in the Windows version? I had thought it would group views of a show that are started and stopped a few times into a single db record for that viewing. But either I am using it wrong, or it's not working, because I get multiple records for a show in those circumstances still. I guess I'm just curious what those parameters should be doing. hehe
A quick question for ljunkie. I noticed in the config file some new advanced parameters.
How exactly should these be used, and are they working in the Windows version? I had thought it would group views of a show that are started and stopped a few times into a single db record for that viewing. But either I am using it wrong, or it's not working, because I get multiple records for a show in those circumstances still. I guess I'm just curious what those parameters should be doing. hehe
Those are for the cli output only (--watched). If you are referring to the fact plexWatch/Web is not grouping them, don't worry it's coming soon :) The new version will work with existing data, so keep it running.
Those are for the cli output only (--watched). If you are referring to the fact plexWatch/Web is not grouping them, don't worry it's coming soon :) The new version will work with existing data, so keep it running.
Actually the question was prompted by what I found when I investigated the db structure, and viewed the records in the tables. I saw that there was a separate record for each instance of a show being started by a client, even if they were from the same client, and the same show, and started only minutes apart. I played around with that setting and couldn't see any difference, and came here to ask. Now it makes sense that it was just for your CLI. Thanks for the answer!
And I am also glad to hear that plexWatch/Web will handle this all better in a future release. That wasn't a big concern to me, but glad to hear all the same. Thanks again!
I may have missed this but why do some of my users not show up, I have multiple using Roku's but only 2 out of 5 I get notifications for all have their own accounts and all on the same version.
