I still have boxcar and email notifications on my list
Please forgive me if I didn't decipher this message correctly.
Boxcar is already part of plexWatch. Email is still on the "todo" list which should be very simple, I just haven't had anyone ask for it yet ( or remember anyone asking ). I will be promoting RC1 to final this week and should have a release candidate soon after including email.
I run plexWatch on a Raspberry Pi with my PMS on a Mac Mini define by IP ($server). Will this work or do I need to do anything else to have client IP logging? Thanks.
I run plexWatch on a Raspberry Pi with my PMS on a Mac Mini define by IP ($server). Will this work or do I need to do anything else to have client IP logging? Thanks.
Client IP logging requires access to the PMS logs, so you'd have to run it on the mac mini. The other option would be to mount the log directory from the mini on the PI through nfs/cifs/afp to gain access to the server logs. Is there any reason you are not running this though on the mini?
I run plexWatch on a Raspberry Pi with my PMS on a Mac Mini define by IP ($server). Will this work or do I need to do anything else to have client IP logging? Thanks.
Not exactly, IP logging is done by parsing the PMS log file, therefore you need to have readacess to this file on the network. On the mac the log file is located @ '/Users/YOURUSERNAME/Library/Logs/Plex Media Server.log';
Finally you need to point your $server_log to the location of the Plex Media Server. Might be tricky over the network.
$server_log = location over network to plex Media server.log
I would recommend running the script locally on the mac, there is no technical reason you can't, I do :)
Sadly it's because I'm having a hell of a time getting the perl modules installed on the mini. I tried cpan but everytime I do cpan seems to think it's the initial install. I tried via MacPorts but it can't seem to find all the perl modules. By now I think I've gotten perl intermingles between cpan and macports. I'm new to both. I use apt-get with no fuss success. Like I said, sad. I think I'll mount the mini drive on the RPi.
Please forgive me if I didn't decipher this message correctly.
Boxcar is already part of plexWatch. Email is still on the "todo" list which should be very simple, I just haven't had anyone ask for it yet ( or remember anyone asking ). I will be promoting RC1 to final this week and should have a release candidate soon after including email.
I'd love to get an email option added to the notifications but would like the ability to group up all "media added" notifications for a specified time period (like daily). That way the email could go out to the users i share my server with and serve as a daily notification of all new media added. It would also be a bonus to have the ability to edit the email before being sent. Not sure how that could work from a script but would be a cool option.
I'd love to get an email option added to the notifications but would like the ability to group up all "media added" notifications for a specified time period (like daily). That way the email could go out to the users i share my server with and serve as a daily notification of all new media added. It would also be a bonus to have the ability to edit the email before being sent. Not sure how that could work from a script but would be a cool option.
Email notification will definitely happen in the next dev, but I will be looking into grouping recently added into a daily report ( or even weekly etc ). I believe Plex only keeps a certain amount of recently added content so I might be keying off the plexWatch.db to email daily, weekly, monthly, etc reports. I.E. someone can add hundreds of shows in one day and if we query it let's say at 12am for the previous days content, you would only get the last 100. I am thinking as a type :) Along with adding time frame for recently added content.. I will probably be able to extend this to --watched reports and others if they fit.
What do you mean by editing the email before it's sent? Are you talking about some sort of template ( which I would definitely plan on doing).
So I have sections that I don’t share with everyone. I am going to use the email to notify my shares users if new media I’ve added but don’t want them to see media I’ve added to sections I’m not sharing. Since recent media notifications aren’t specified to only certain sections I was thinking I’d want to edit the email to delete things I don’t want them seeing. The easiest workaround would be to email myself and then I could edit and forward along to my users. Or is it possible to specify which sections to include in the email notification?
So I have sections that I don't share with everyone. I am going to use the email to notify my shares users if new media I've added but don't want them to see media I've added to sections I'm not sharing. Since recent media notifications aren't specified to only certain sections I was thinking I'd want to edit the email to delete things I don't want them seeing. The easiest workaround would be to email myself and then I could edit and forward along to my users. Or is it possible to specify which sections to include in the email notification?
Makes sense. I will add add that to the list of things -- limited sections of recently added ( for the normal notification --recently_added ) and for this new idea of recently added reports
I just wanted to let everyone know I haven't forgotten about pushing the dev version to master and adding the email provider. Real life (job) has been taking some of my "non work" hours I use for this script as I've been on call... also a modified ROKU channel has taken up a little too :) http://forums.plexapp.com/index.php/topic/79897-rarflix-modified-roku-channel/. Hopefully I will have some free time this weekend.
Sorry to be a bit off topic here, but the information may be relevant in positioning future features for PlexWatch. I have created a thread/poll to get some feedback on how many users people typically share their library with. Please take a second to submit your answer on the poll:
This could provide some good insights in how to structure the db given the typical user. I am sure PlexWatch users are a bit more active on the sharing front, so it would be great to get your info:)
* added options for logging IP Address of client (default is disabled)
* enable this in config.pl with the $server_log, $log_client_ip (enable $debug_logging to see what matched )
-- format_options: {ip_address}
-- Requires parsing of PMS log file. $server_log in config.pl
-- log file searched in reverse order for most recent line (File::ReadBackwards)
-- match on itemID+machineIdentifier -or- machineIdentifier
-- fallback to only itemID (ratingKey). Could match wrong IP if multiple clients watch the same itemID (fallback: mainly for clients in 'List of networks that are allowed without auth')
-- REQUIRES perl module File::ReadBackwards - to conserve memory)
* Added SSL support (port 32443)
* friendly name now allows for user+platform(title) ( example in config.pl-dist )
* $debug_logging added to config.pl ( still need to add more debug logging though )
* Variables allowed in 'application' for prowl,pushover & 'from' for boxcar
* Fix: AM/PM for OSX (non GNU)
* Fix: --watching now calls --notify before it shows now playing content. Fixes issue when content hasn't been logged as started/stopped
* Fix: allows season/episode fields to be empty for 'show'
* Fix: Do not update XML in DB if the XML is not valid
* Fix: --watched: {percent_complete} -- use the last viewOffset instead of the first.
* Fix: --watched: always display a 100% watched show/movie. I.E. show two lines: if user completes show1 (100%), then restarts said show and tops at < 90% on the same day (advanced config)
* Fix: --watched: do NOT group shows together IF hours between start of the same show is > 3 hours. (advanced config)
* 'application' => $appname removed from boxcar ( not used ) 'from' is the equivalent
* advanced config options available. View README. (Mainly to not convolute the config more than it already is)
* README: updated instructions to NOT call sudo before running the script. This way the DB is not owned by root and can be run by the 'normal' user.
* any time you upgrade, please copy your plexWatch.db to a safe location for a backup.
* If you enable ip logging - File::ReadBackwards is required
All i really want is to send notifications to me. In email or whatever ways it can. I don’t need it to push to Facebook or twitter. So to begin setup what is a must to get it working in the config file
Alli really want is to send notifications to me. In email or whatever ways it can. I don't need it to push to Facebook to twitter.
Look at https://github.com/ljunkie/plexWatch under the Supported Push Notifications area. Those are the current supported notification options you can set in the config.pl. Email will probably be in the next release.