Plugin: SageAlert v2.x

[Slugger]

Welcome to the support thread for SageAlert v2.x. This is the latest version of SageAlert and is compatible only with SageTV v7.

NOTE: SageAlert v2.x is not available yet. I'm just creating this thread for future use and to provide the first screen shot.

SageAlert v2.x is getting close to an initial beta release into the plugin repository, but there's still some polish and a couple of features missing that I'd like to introduce first. Those wanting to know when the first beta is added to the repository should subscribe to this thread.

I've attached a screen shot that shows the new GUI. It should give those interested an idea of where SageAlert v2.x is heading.

[nethead]

Thank you for the hard work updating this GREAT addon

[Slugger]

The first beta for SageAlert v2.0 is now available in the plugin repository.

Please read carefully before installing...

First, this is in a beta state. Functionally, the alerts and notifications are working. If you configure an alert, it should trigger just fine or log why it didn't. The GUI is definitely rough around the edges. Comments welcome.

Docs are lacking - I'm playing catch up trying to get all my plugins ported to v7. A "docs day" is coming soon, however.

Important: Moving to SageAlert v2.0 will require a full reconfiguration. The db formats are not compatible between v1.x and v2.0. You will have to reconfigure all your settings, notifications systems, SMTP settings, etc. Sorry.

Key Changes:

The whole RPC/remote event firing system is deprecated and has been completely removed. This will be replaced by support for firing events to SageAlert using the Sage v7 event model. This is not implemented yet, more details to come.

Twitter: There are no docs yet, but to register a twitter account, click the link to go to twitter web site, give SageAlert access to your account then feed the pin back to SageAlert. Post questions if you have them. Docs are coming for this. (Basically, Twitter now requires OAuth authentication, and this is how it's implemented.)

Events: The low disk space event is missing; this is on purpose. Another plugin will reintroduce this event to SageAlert at a later date.

Right click items in the tree menu to do things (like add/delete accounts). Left click on events to add listeners to them. Hopefully this new interface is more user friendly/intuitive. Comments welcome.

Play around, give me some feedback.

[korben_dallas]

I would download this in a heartbeat if it could be configured & used 100% from within SageTV (i.e. without the browser requirement). I know that might be a different roadmap from where you plan to take this, but just thought I'd give some feedback.

[Slugger]

Originally Posted by korben_dallas

I would download this in a heartbeat if it could be configured & used 100% from within SageTV (i.e. without the browser requirement). I know that might be a different roadmap from where you plan to take this, but just thought I'd give some feedback.

Fair enough. A future version may introduce some of the basic settings into the STV, but the configuration of events and listeners and notifications, etc. will never be done in the STV (by me).

Why? I don't like writing STVi imports. Two reasons:

1) I'm not a big fan of Studio and how STVs are implemented. I'm not saying it's bad, it's just not my thing. If the STV was written in Java (like a Swing app or whatever) then I'd be more inclined to do it [maybe].

2) But the big reason I don't write STVi imports is because I will only ever be using 1 STV and if you support one, you inevitably get asked to support them all and I just don't have the time to do it. The nice thing about web apps is one interface to support, period. Obviously, right now there's only one STV, but Ortus and Phoenix will change that soon enough and I have no interest to write STVi imports for STV(s) that I'll never use.

I challenge other SageAlert users to write an STVi that brings the full configuration options into the Sage STV, but I'll never do it.

[Slugger]

Major packaging snafu with the first upload. Web GUI is useless with that build (841). A new build will appear in the repository shortly.

[Slugger]

v2.0.0.842 now in repository. It fixes the packaging errors from 841 that made the web GUI useless.

[darcilicious]

Never mind, this probably totally a jetty web server issue...

[GKusnick]

Originally Posted by Slugger

I challenge other SageAlert users to write an STVi that brings the full configuration options into the Sage STV, but I'll never do it.

Why does it have to be done as an STVI? The SageTVPlugin configuration methods should be adequate (although with this many settings it may be somewhat unwieldy). That would answer both of your objections: you could do it all in Java, without ever opening Studio, and it would be STV-independent.

[Slugger]

Originally Posted by GKusnick

Why does it have to be done as an STVI? The SageTVPlugin configuration methods should be adequate (although with this many settings it may be somewhat unwieldy). That would answer both of your objections: you could do it all in Java, without ever opening Studio, and it would be STV-independent.

All the menus with all the options (servers, listeners, events, etc.) are all generated dynamically. To call it unwieldy is being nice. Not impossible, but to make it visually appealing/usable requires some UCD skills that I simply do not possess nor desire to improve upon (at least not through these SageTV projects). The web UI was basically already done, it just required some minor changes to update the look. Again, if someone wants to write an STVi or write the config implementation additions to the plugin class (the plugin class in the source tree is located here) then I'm more than willing to accept a patch. I've got to cut myself off somewhere, and for me, this is my limit.

[Slugger]

Originally Posted by darcilicious

Never mind, this probably totally a jetty web server issue...

As in nevermind, it's working?

[darcilicious]

No, never mind in that it's not working but I'm not sure it's a SageAlert problem. I'll post again if otherwise

See http://forums.sagetv.com/forums/show...7&postcount=17 and the rest of the thread for context.

[Peter_h]

I can't click on anything in the "Servers" tree. So, I can't configure an email address. However, it is sending emails to the address I had configured in SageAlert v1.X.

Would this happen to be a similar issue to what we saw in the SRE thread? Maybe not compatible with previously installed versions?

-Peter

[davidk21770]

When I surf to http://localhost:8080/sagealert, I get:

HTTP ERROR: 503

Problem accessing /sagealert. Reason:

SERVICE_UNAVAILABLE

Powered by Jetty://

Jetty's working fine because I have Sage TV Web Interface up and running with no problems.

Actually, this happened with the web interface initially, but it cleared-up when I copied a backed-up config file to the new install (webserver subdir). Could I be missing any files that would be there if I was updating?

[Slugger]

Originally Posted by darcilicious

No, never mind in that it's not working but I'm not sure it's a SageAlert problem. I'll post again if otherwise

See http://forums.sagetv.com/forums/show...7&postcount=17 and the rest of the thread for context.

Originally Posted by davidk21770

When I surf to http://localhost:8080/sagealert, I get:

Jetty's working fine because I have Sage TV Web Interface up and running with no problems.

Actually, this happened with the web interface initially, but it cleared-up when I copied a backed-up config file to the new install (webserver subdir). Could I be missing any files that would be there if I was updating?

I need someone to work with me on MSN messenger to get the proper debug info. It could be a SageAlert problem, but until someone can get me the proper logs then I can't make that determination. PM for details on contacting me through MSN (my id is just my email address in case you already know my addr - I just won't post it in here).

[Slugger]

Originally Posted by Peter_h

I can't click on anything in the "Servers" tree. So, I can't configure an email address. However, it is sending emails to the address I had configured in SageAlert v1.X.

Would this happen to be a similar issue to what we saw in the SRE thread? Maybe not compatible with previously installed versions?

-Peter

You see Email, Twitter and Growl under "Servers", right? Right click on one of those to add a new account.

Something isn't right. SageAlert 2.x cannot use a v1.x db file... so either 1.x is still running somehow or... well, that's the only possibility. Easiest thing to do is grab me on MSN messenger so we can work through some debugging. PM for my MSN details (my id is just my email address, if you already know what that is).

[farfromuman]

I got the same result but Sagealert started working after I manually restarted the service. I can confirm that after the service was restated the sagealert files appeared in the jetty folder and the URL started working. It looks like Sage did not do a full restart when installing via the plugin manager.

I setup email alerts and they are working.

Originally Posted by davidk21770

When I surf to http://localhost:8080/sagealert, I get:

Jetty's working fine because I have Sage TV Web Interface up and running with no problems.

Actually, this happened with the web interface initially, but it cleared-up when I copied a backed-up config file to the new install (webserver subdir). Could I be missing any files that would be there if I was updating?

[Peter_h]

Originally Posted by Slugger

You see Email, Twitter and Growl under "Servers", right? Right click on one of those to add a new account.

Something isn't right. SageAlert 2.x cannot use a v1.x db file... so either 1.x is still running somehow or... well, that's the only possibility. Easiest thing to do is grab me on MSN messenger so we can work through some debugging. PM for my MSN details (my id is just my email address, if you already know what that is).

Sounds good. I have to work today, (IT emergency ) so it will be when I get home later.

[davidk21770]

I tried restarting the server, restarting sage, and rebooting my computer -- but your update finally fixed it!

Thanks.

[Slugger]

Originally Posted by Slugger

I need someone to work with me on MSN messenger to get the proper debug info. It could be a SageAlert problem, but until someone can get me the proper logs then I can't make that determination. PM for details on contacting me through MSN (my id is just my email address in case you already know my addr - I just won't post it in here).

Thanks to darcilicious, one major bug was tracked down this morning. I failed to include the SQLite JDBC driver dependency in the plugin. So users who didn't already have that plugin/driver installed would not be able to use SageAlert.

A new build is now available in the repository. I'm also noticing a race condition between Jetty and SageAlert where the start up may not work properly. I'll follow up with jreichen on that. This, I think, is what farfromuman experienced. In this case, opening and resaving SageAlert.context.xml in SageTV\jetty\contexts should fix things (by forcing a restart of the app).