Plugin: SageAlert v2.x

[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).

Originally Posted by davidk21770

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

Thanks.

Yeah, subtle dependency issues. Problem is I have so many jars already preinstalled on my system that when I go to figure out what should be listed as a dependency, I keep forgetting one or two.

Make sure you're running 2.0.0.845 as it includes a fix to work around a bug in the twitter4j library as well.

[darcilicious]

Can't thank Slugger enough for taking the time to debug this! And to follow up as another problem showed up after he thought he was done

[toricred]

I just upgraded to this today. I see there is no test for the mail server. I'm not getting alerts that I think I should be getting. Any suggestions on testing?

[Slugger]

Originally Posted by toricred

I just upgraded to this today. I see there is no test for the mail server. I'm not getting alerts that I think I should be getting. Any suggestions on testing?

SageTV\plugins\sagealert\sagealert.log

It logs every notification attempt and if it fails then the exception/error that caused it.

(The ability to test the email settings, twitter account, Growl account, etc. will return eventually.)

[toricred]

Here are the results from that log with an error that I can't figure out how to fix:

2010-05-31 15:57:56,800 INFO  [AppEventsListener]: Event received: EPGUpdateCompleted
2010-05-31 15:57:57,331 ERROR [EmailServer]: Error sending email
com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.0 Must issue a STARTTLS command first. 21sm4325911pzk.0

	at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1829)
	at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:1368)
	at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:886)
	at com.google.code.sagetvaddons.sagealert.server.EmailServer.sendMessage(EmailServer.java:130)
	at com.google.code.sagetvaddons.sagealert.server.EmailServer.access$300(EmailServer.java:39)
	at com.google.code.sagetvaddons.sagealert.server.EmailServer$1.run(EmailServer.java:76)
2010-05-31 15:57:57,331 ERROR [EmailServer]: Email for 'An EPG update has completed' event FAILED to 'brian@xxxx.org'

[Slugger]

Looks like your SMTP server is requiring an SSL connection. In your SMTP settings for SageAlert, ensure "Use SSL" is checked.

[toricred]

That didn't fix it and my mail client is set to not use an ssl connection. Here's the new error:

2010-05-31 17:10:19,784 ERROR [EmailServer]: Error sending email
javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 587;
  nested exception is:
	javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
	at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1706)
	at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:525)
	at javax.mail.Service.connect(Service.java:291)
	at javax.mail.Service.connect(Service.java:172)
	at javax.mail.Service.connect(Service.java:192)
	at com.google.code.sagetvaddons.sagealert.server.EmailServer.sendMessage(EmailServer.java:127)
	at com.google.code.sagetvaddons.sagealert.server.EmailServer.access$300(EmailServer.java:39)
	at com.google.code.sagetvaddons.sagealert.server.EmailServer$1.run(EmailServer.java:76)
Caused by: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
	at com.sun.net.ssl.internal.ssl.InputRecord.handleUnknownRecord(Unknown Source)
	at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
	at com.sun.mail.util.SocketFetcher.configureSSLSocket(SocketFetcher.java:503)
	at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:234)
	at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1672)
	... 7 more
2010-05-31 17:10:19,800 ERROR [EmailServer]: Email for 'SageAlert has successfully started...' event FAILED to 'brian@sedlaceks.org'

[Slugger]

If you're using Gmail's SMTP server then I'd recommend settings like this (which is exactly what I use, and my emails are sent no problem):

host: smtp.gmail.com
port: 465
user: yourid@gmail.com
pwd: yourpwd
Use SSL: yes (i.e. box is checked)
Sender address: yourid@gmail.com

Sender address must equal user name or Google will reject your emails.

[toricred]

I'm using google apps with my own domain name. It was working with sagealert v.1. I changed to port 465 and using ssl. It took a little while, but it looks like it's working now. Thanks for the help.

[GKusnick]

Originally Posted by Slugger

The GUI is definitely rough around the edges. Comments welcome.

OK, here are some quick first impressions, in no particular order:

* The SMTP password displays in cleartext.

* I can create email accounts, but I can't figure out how to get back to them for later editing or verification. Left-clicking on Email doesn't seem to do anything, and right-clicking just gives me the Create option again. (There's a Delete option too, but it's disabled.)

* Revise that: After manually refreshing the page I can now click open the Email node of the tree and see the accounts I created. However I still can't do anything with them. Left-clicking does nothing, and right-clicking shows me a menu with both Create and Delete disabled.

* There was a whole Settings page in the old UI that seems to have no equivalent in the new UI.

* The Clients page seems to show only Placeshifter/extender clients. The old version showed SageTVClients and the server's own pseudoclient as well.

[darcilicious]

Originally Posted by GKusnick

* The Clients page seems to show only Placeshifter/extender clients. The old version showed SageTVClients and the server's own pseudoclient as well.

My PC client and 127.0.0.1 (server) both show up on my clients page but I don't have any placeshifters or extenders in my set up / network either.

[GKusnick]

Originally Posted by GKusnick

* The Clients page seems to show only Placeshifter/extender clients. The old version showed SageTVClients and the server's own pseudoclient as well.

Originally Posted by darcilicious

My PC client and 127.0.0.1 (server) both show up on my clients page but I don't have any placeshifters or extenders in my set up / network either.

Yes, I figured out that I have to restart my clients in order to fire the ClientConnected event that SageAlert now uses to track this.

[Slugger]

Originally Posted by GKusnick

OK, here are some quick first impressions, in no particular order:

* The SMTP password displays in cleartext.

Fixed for next build.

* I can create email accounts, but I can't figure out how to get back to them for later editing or verification. Left-clicking on Email doesn't seem to do anything, and right-clicking just gives me the Create option again. (There's a Delete option too, but it's disabled.)

* Revise that: After manually refreshing the page I can now click open the Email node of the tree and see the accounts I created. However I still can't do anything with them. Left-clicking does nothing, and right-clicking shows me a menu with both Create and Delete disabled.

Accounts are suppose to be added to the tree when created. It was working, now it's not. That'll be fixed for the next build.

The ability to delete is there, but the option is inadvertently disabled. That, too, will be fixed for the next build.

* There was a whole Settings page in the old UI that seems to have no equivalent in the new UI.

All of those settings had to do with how frequently the polling threads polled the Sage API looking to fire the pseudo events I was generating in Sage v6 for everything. Now, SageAlert simply listens for the actual API events and reacts to them so all of those settings are obsolete. The exception were the settings for the date/time format used in messages. So far I haven't had a need to bring those back, so I haven't.

* The Clients page seems to show only Placeshifter/extender clients. The old version showed SageTVClients and the server's own pseudoclient as well.

Clients/extenders/placeshifters are added to the list on the ClientConnected event. You may need to restart a client to get it to register in that list. Does the pseudo client fire the ClientConnected event? If so, does it fire before SageAlert registers for the event? (This is possible because of the asynchronous manner in which jetty apps are deployed - I'm looking to handle this scenario in a future build.) Disconnecting and reconnecting PC clients or the pseudo client should register it in the Clients list in SageAlert (full app refresh currently needed to refresh the clients list - that, too, will be addressed ). I have had my clients and extenders and placeshifters all register successfully (just tested it again).

[GKusnick]

Originally Posted by Slugger

Accounts are suppose to be added to the tree when created. It was working, now it's not. That'll be fixed for the next build.

The ability to delete is there, but the option is inadvertently disabled. That, too, will be fixed for the next build.

But is there a way to change the account settings (e.g. message type) without deleting and re-creating it?

Originally Posted by Slugger

Clients/extenders/placeshifters are added to the list on the ClientConnected event. You may need to restart a client to get it to register in that list.

Yeah, figured that out. Next question: is there a way to delete a client from that list? (I started one of my clients using the wrong NIC/MAC addr.)

[Slugger]

Originally Posted by GKusnick

But is there a way to change the account settings (e.g. message type) without deleting and re-creating it?

Currently, no. The key value cannot be changed (email address, twitter id, growl hostname), but the other data could be changed without affecting the event registrations. I'll probably add that ability.

Yeah, figured that out. Next question: is there a way to delete a client from that list? (I started one of my clients using the wrong NIC/MAC addr.)

No. Reconnecting from the new NIC would add the new registration. Deleting clients isn't an option. Clients that don't connect simply aren't used.

[Slugger]

2.0.0.846 now available with a bunch of UI bug fixes.

[Peter_h]

upgrading to the latest version fixed the issue I was having with the old sagealert still running... I think.

[nethead]

Great! Time to upgrade to v7 now.

Will have to after 4pm on Saturday, as the wife records her chinese shows from 9am to 4pm every day, and you don't mess with wife recordings

[davidk21770]

I'm not getting any emails.
The log shows the following error:

2010-06-03 02:03:56,502 ERROR [EmailServer]: Error sending email
javax.mail.MessagingException: Could not connect to SMTP host: mail.comcast.net, port: 110, response: -1
...

The SMPT section is set up the same way that my email is set up in Thunderbird.
Do you have any suggestions?

[Slugger]

Port 110 is typically the POP3 server on most networks. I'd try changing it to port 25. If that doesn't work, search your ISP's web site for details on its SMTP server settings.