Plugin: SageAlert v2.x

[Slugger]

I just uploaded the final release of SageAlert v2.0.0 to the plugin repository. The final version number is 2.0.0.1521.

The beta tag has been removed and this is the last expected update to SageAlert until the fall. This update includes 3 major bug fixes:

• Cleanup the clutter on the client event configuration screen; remove abundance of buttons and replace them with clean dropdown boxes
• Fix bug where sometimes the SMTP server test button would not send the test email for properly configured SMTP servers
• Read and write client/extender aliases from the new sagex properties in Sage.properties instead of using custom alias settings; users will have to redefine their aliases if not already set via sagex (i.e. the latest nielm web interface uses these aliases)

Thanks to all who have been testing during the beta period of SageAlert v2.0!

Again, for those who may have missed it, I'm about to embark on my annual SageTV dev vacation, which typically lasts until the fall. With this final release, I have no plans to touch this code base until the fall. With that said, major bugs will be addressed during the summer, if necessary, and I'll be hanging around the user forums and so will be answering questions, etc. I just have no plans to do any major coding on my SageTV plugins.

Enjoy the summer, I know I will!

[Slugger]

Nearly a year to remove the beta tag on 2.0.0, but just six days to release 2.0.1!

v2.0.1 is now in the plugin repository and contains a single fix:

Ticket 295: Fix bug where the UnresolvedRecordingConflicts event would incorrectly notify listeners of the ConflictStatusChanged event, causing a double notification of the CSC event and no notifications of the URC event

[Slugger]

sagetv-addons licensing is changing soon. Details are outlined here. For those that may be considering a license purchase, you may want to read that doc closely, especially this FAQ question and answer.

[wayner]

Can I be the first to request that SageAlert be able to send notifications to an iOS 5 client as part of the improved notifications system in iOS 5?

[Slugger]

Originally Posted by wayner

Can I be the first to request that SageAlert be able to send notifications to an iOS 5 client as part of the improved notifications system in iOS 5?

You certainly can.

Correct me if I'm wrong, but iOS SDK is only available on Mac OS X? I don't have a Mac and so no dev env to add such support. Project donations are no where near the levels required to go out and buy one for such development. If I'm wrong, and you can develop for iOS on Windows or Linux, then I'd be more than willing to investigate it, especially since I recently moved from BlackBerry to iPhone myself.

EDIT: Just to be clear, the PayPal donations account is not even close to being close to being able to think about getting a Mac for plugin development so a few more donations aren't going to make this happen. After reading my post, I just want to make sure that's clear. In other words, if iOS dev has to be done on a Mac, I won't be doing it.

[BKeadle]

Quick question (I hope this is the right place to post this)
I'm using v1.0.2.781 for SageTV v6.
Is there any way to get more detailed information from SJQ alerts? Currently I'll get an alert like this:

SJQ: Task 'SJQMOVETVShows' failed for media object '1534951'

Which isn't very helpful/descriptive.

[Slugger]

Originally Posted by BKeadle

Quick question (I hope this is the right place to post this)
I'm using v1.0.2.781 for SageTV v6.
Is there any way to get more detailed information from SJQ alerts? Currently I'll get an alert like this:

SJQ: Task 'SJQMOVETVShows' failed for media object '1534951'

Which isn't very helpful/descriptive.

The idea behind the alert is to just bring the event to your attention. From here, I'd expect the user to head to their SJQ logs for more details and to investigate. The verbosity of the message is an SJQ issue and if you're using SJQv3 (on Sage v6) then I won't be making any code changes to that version - though the source code is in Google Code and you're more than welcome to modify it. All of my plugins for v6 are no longer supported by me (as I no longer have any Sage v6 env to run them in).

[BKeadle]

Fair enough - I wasn't sure whether it was a configurable items somewhere that was missing. Not being a programmer, I rely on the talents of people like you to make my life easy. Thanks for your contribution(s)

[mevans]

Hi there.

Just installed this fab plug-in.

Searching through this forum, i get the impression that the ability to post to twitter is not working at the moment. Can somebody please confirm?

I can send emails via SageAlert (the test button worked!)

Cheers

mevans

[Slugger]

Twitter works fine... my Sage server is happily tweeting as we speak. You must get the PIN number from twitter.com for your account after registering the account within SageAlert web UI.

[nethead]

Tweeting for me also, just deleted a show and BAM tweet showed up

[mevans]

OK - Great news

In which case, i think i'm making this harder than it is!

I'm not the sagealert web page, i right click 'twitter' in the servers section. click create, and i get:

Obtain PIN: [Click here]
PIN:
[Add Twitter Account]

I'm unsure what to do now....

Slugger, you refer to

the PIN number from twitter.com

what is this?

cheers

[wayner]

You can always search for #SageAlert at Twitter to see the Tweets. http://twitter.com/#!/search?q=%23SageAlert

Someone named profgadgetsHTPC just imported a Dexter xViD rip to his system called Dexter.S06E09.HDTV.XviD-LOL . He might want to turn off the Tweeting of video imports as this could be a sign to the world that he is downloading video content via BitTorrent.

[Slugger]

Originally Posted by mevans

OK - Great news

In which case, i think i'm making this harder than it is!

I'm not the sagealert web page, i right click 'twitter' in the servers section. click create, and i get:

Obtain PIN: [Click here]
PIN:
[Add Twitter Account]

I'm unsure what to do now....

Slugger, you refer to
what is this?

cheers

Click the button, it'll take you to twitter.com, authorize your twitter account for use by SageAlert. Twitter.com will then give you a PIN number, feed that number back into the form then click Add.

Note: You may need to disable popup blockers if the twitter web site doesn't appear when you click the first button.

[mevans]

Originally Posted by Slugger

Click the button, it'll take you to twitter.com, authorize your twitter account for use by SageAlert. Twitter.com will then give you a PIN number, feed that number back into the form then click Add.

Note: You may need to disable popup blockers if the twitter web site doesn't appear when you click the first button.

OK, i've click on the "Click Here" button, and get this message:

TwitterException{statusCode=-1, retryAfter=0, rateLimitStatus=null}

I've tried in Firefox, and IE, with popups turned off.

Any ideas?

[Slugger]

Originally Posted by mevans

OK, i've click on the "Click Here" button, and get this message:

TwitterException{statusCode=-1, retryAfter=0, rateLimitStatus=null}

I've tried in Firefox, and IE, with popups turned off.

Any ideas?

Nope. That error is coming from SageAlert side. Is there a firewall blocking access to the internet or twitter.com from the machine you're trying this on?

[mevans]

Originally Posted by Slugger

Nope. That error is coming from SageAlert side. Is there a firewall blocking access to the internet or twitter.com from the machine you're trying this on?

No. i can use the internet and twitter.com fine. i tried on another comuter (via the same router) and got the same result. i tried with zone alarm and antivirus off too, but same result.

[nethead]

oh yes, the public twitter posting.

you may wish to make a new account on twitter, just for your sagetv tweets and make the account private, adding only your twitter account to be allowed to view the tweets.

[Slugger]

Originally Posted by mevans

No. i can use the internet and twitter.com fine. i tried on another comuter (via the same router) and got the same result. i tried with zone alarm and antivirus off too, but same result.

Are there any other errors in the sagealert.log file?

[mevans]

Originally Posted by Slugger

Are there any other errors in the sagealert.log file?

Apologies for the lack of response - duty calls...
hopefully get a chance tonight