Wonderful and robust work James... One question it's posible that statistic window from shared users was exported or migrated at XML Web Page or I can be sent a URL with his resumed use... EMail notification or WhatsUp note from their mobiles devices?
Regards
I would like that Added Recently was sent by Pushover to my shared users or was sent at their devices mobiles... For example, if I have created a Plex shared User group in WatsApp I can send to them new notifications...
I’m now using PlexNotify v0.0.0.93, and I confirm that the tokens {player} and {platform} are now expanded correctly in notifications and log entries.
But the ETA values are still badly bugged. If a video is launched which has been played at an earlier date, its new ETA value is calculated based on the old launch timestamp, even if that is several months ago. As far as I can tell this bug has not changed at all since the last time I reported on it, in post #1357 of this thread.
eg: My brother started a video today, the calculated ETA in the notification and log entry of this launch is for a time three months ago… (the first time he played that video).
I'm now using PlexNotify v0.0.0.93, and I confirm that the tokens {player} and {platform} are now expanded correctly in notifications and log entries.
But the ETA values are still badly bugged. If a video is launched which has been played at an earlier date, its new ETA value is calculated based on the old launch timestamp, even if that is several months ago. As far as I can tell this bug has not changed at all since the last time I reported on it, in post #1357 of this thread.
eg: My brother started a video today, the calculated ETA in the notification and log entry of this launch is for a time three months ago... (the first time he played that video).
Best regards: dlanor
ahh I see I did make a mistake I will be fixed in the next patch
Humm what database are you using? MsSqlCE? Check the advanced settings tab.
Sent from my SM-N900P using Tapatalk
ok, never mind, I'm stupid, I had to reinstall PN (and clear PN data, reconfigure to MySQL. etc...) for issues I was having and it was set to OFF for the primary... all OK now...
The problem with ETA that I described only exists for videos which have been viewed more than once within the span of the total log. For such cases the ETA is based on the first launching, regardless of how old that event is.
At least this is how it works in v0.0.0.93 and a few preceding ones.
(It would be an error even if closer in time, as the ETA for each event should be based on the timestamp of that same event plus the playtime remaining at the time, ignoring all other events.)
Sorry if I seem to be nagging on this subject. I just want to ensure that the problem is clear to you.
It's easy to miss if you view a log without repeated viewing of videos by the same user. Because for such a log there will be NO instances of this ETA error.
But you should be able to replicate the issue yourself, simply by launching some movie or episode that you've already viewed recently, so that the old entry remains in your log. Then check the resulting ETA of the log entry for the new launch of that video.
The problem with ETA that I described only exists for videos which have been viewed more than once within the span of the total log. For such cases the ETA is based on the first launching, regardless of how old that event is.
At least this is how it works in v0.0.0.93 and a few preceding ones.
(It would be an error even if closer in time, as the ETA for each event should be based on the timestamp of that same event plus the playtime remaining at the time, ignoring all other events.)
Sorry if I seem to be nagging on this subject.
I just want to ensure that the problem is clear to you.
It's easy to miss if you view a log without repeated viewing of videos by the same user.
Because for such a log there will be NO instances of this ETA error.
But you should be able to replicate the issue yourself, simply by launching some movie or episode that you've already viewed recently, so that the old entry remains in your log. Then check the resulting ETA of the log entry for the new launch of that video.
Alpha v0.0.0.94 - Fixed some video posters on notifications being small. - Fixed Estimated end time.
I've just tested this version 0.0.0.94, and the ETA calculation is now perfect for the notifications and main screen. But something seems to go wrong for the corresponding entries in the "Log Of Events".
Here is a snapshot of the main screen showing correct ETA calculation of an episode of "The Big Bang Theory". 
But in the next snapshot from the "Log Of Events" you can see that the ETA of the corresponding entry is wrong. It shows a different ETA than that used for the same event in the main screen. 
For many cases the ETA shown in the log seems correct, though I can no longer compare them to the ETA values of the original notifications. But for some cases the ETA in the log has a large offset, in some cases representing a doubling of the estimated remaining play time. For example, the episode of "Star Trek Voyager" listed in that snapshot has a total play time of 43 minutes and 22 seconds, but the difference between the logged timestamp and the ETA is over 86 minutes. So that's almost exactly twice the correct amount...
Alpha v0.0.0.95
- Fixed Recently Added Table database errors, This will fix recently added notifications.
- Fix for IP address detection.
- Added version information to SQL error logs.
- Fixed bug with extremely long URLs causes infinite notifications
- Added Connected Clients to main window.
- Added Notifications for Clients connecting and disconnecting.
