Jump to content

Email notifications fail for "Use Default" and Custom Setting (that one crashes ISY)


CMcCarron

Recommended Posts

Hello,

I am trying to configure email notifications on my ISY for the first time.  I first tried to use a hotmail account and entered the settings that are specified on the site (smtp.office365.com, email address, port 587, use TLS, 5000ms timeout and an app password freshly created for it).  If I do this and then try to use a Test with a group I created, I can reliably crash the ISY (v5.2.0).  The log just ends, nothing there except the subsequent restart.  The error log (this is between two crashes, so short) has this:

Tue 2021/03/16 05:32:32 PM    System    -5    Start    
Tue 2021/03/16 05:32:38 PM    System    -110022    /DEF/F6/I1/NLS/EN_US.TXT    
Tue 2021/03/16 05:32:38 PM    System    -110022    /CONF/UXT.BIN    
Tue 2021/03/16 05:32:38 PM    System    -110012    /CONF/UXT.BIN    
Tue 2021/03/16 05:32:40 PM    System    -170001    UDQ:Queue Full: IPOLLWAKEUP : Task[10] SOCK SOCK-PROC pty=27    
Tue 2021/03/16 05:32:39 PM    System    -110022    /CONF/ELKXPRT.XML    
Tue 2021/03/16 05:32:39 PM    System    -7153    ID 0002 :err=0, tag='/group', num=20, nest=5, o    
Tue 2021/03/16 05:32:40 PM    System    -110022    /CONF/UZWNDKEY.TXT    
Tue 2021/03/16 05:32:40 PM    System    -110012    /CONF/UZWNDKEY.TXT    
Tue 2021/03/16 05:32:40 PM    System    -170001    [Network] Established    
Tue 2021/03/16 05:59:10 PM    System    -50001    -20    
 

I've attached a screen capture of the settings. 

If I set it for "Use Default it also fails with the same authentication error (-20) but at least it gives me a dialog box to tell me rather than crashing the ISY.   Note the log below includes the one above but it has the extra error, with no crash and restart.

Tue 2021/03/16 05:32:38 PM    System    -110022    /DEF/F6/I1/NLS/EN_US.TXT    
Tue 2021/03/16 05:32:38 PM    System    -110022    /CONF/UXT.BIN    
Tue 2021/03/16 05:32:38 PM    System    -110012    /CONF/UXT.BIN    
Tue 2021/03/16 05:32:40 PM    System    -170001    UDQ:Queue Full: IPOLLWAKEUP : Task[10] SOCK SOCK-PROC pty=27    
Tue 2021/03/16 05:32:39 PM    System    -110022    /CONF/ELKXPRT.XML    
Tue 2021/03/16 05:32:39 PM    System    -7153    ID 0002 :err=0, tag='/group', num=20, nest=5, o    
Tue 2021/03/16 05:32:40 PM    System    -110022    /CONF/UZWNDKEY.TXT    
Tue 2021/03/16 05:32:40 PM    System    -110012    /CONF/UZWNDKEY.TXT    
Tue 2021/03/16 05:32:40 PM    System    -170001    [Network] Established    
Tue 2021/03/16 05:59:10 PM    System    -50001    -20    
Tue 2021/03/16 05:59:20 PM    System    -50001    -20  

Can anyone tell me if there's something I've obviously done wrong?  In any case, I think maybe crashing isn't a desirable behavior.

 

Thanks!

ISY Email.PNG

Link to comment
32 minutes ago, CMcCarron said:

Hello,

I am trying to configure email notifications on my ISY for the first time.  I first tried to use a hotmail account and entered the settings that are specified on the site (smtp.office365.com, email address, port 587, use TLS, 5000ms timeout and an app password freshly created for it).  If I do this and then try to use a Test with a group I created, I can reliably crash the ISY (v5.2.0).  The log just ends, nothing there except the subsequent restart.  The error log (this is between two crashes, so short) has this:

Tue 2021/03/16 05:32:32 PM    System    -5    Start    
Tue 2021/03/16 05:32:38 PM    System    -110022    /DEF/F6/I1/NLS/EN_US.TXT    
Tue 2021/03/16 05:32:38 PM    System    -110022    /CONF/UXT.BIN    
Tue 2021/03/16 05:32:38 PM    System    -110012    /CONF/UXT.BIN    
Tue 2021/03/16 05:32:40 PM    System    -170001    UDQ:Queue Full: IPOLLWAKEUP : Task[10] SOCK SOCK-PROC pty=27    
Tue 2021/03/16 05:32:39 PM    System    -110022    /CONF/ELKXPRT.XML    
Tue 2021/03/16 05:32:39 PM    System    -7153    ID 0002 :err=0, tag='/group', num=20, nest=5, o    
Tue 2021/03/16 05:32:40 PM    System    -110022    /CONF/UZWNDKEY.TXT    
Tue 2021/03/16 05:32:40 PM    System    -110012    /CONF/UZWNDKEY.TXT    
Tue 2021/03/16 05:32:40 PM    System    -170001    [Network] Established    
Tue 2021/03/16 05:59:10 PM    System    -50001    -20    
 

I've attached a screen capture of the settings. 

If I set it for "Use Default it also fails with the same authentication error (-20) but at least it gives me a dialog box to tell me rather than crashing the ISY.   Note the log below includes the one above but it has the extra error, with no crash and restart.

Tue 2021/03/16 05:32:38 PM    System    -110022    /DEF/F6/I1/NLS/EN_US.TXT    
Tue 2021/03/16 05:32:38 PM    System    -110022    /CONF/UXT.BIN    
Tue 2021/03/16 05:32:38 PM    System    -110012    /CONF/UXT.BIN    
Tue 2021/03/16 05:32:40 PM    System    -170001    UDQ:Queue Full: IPOLLWAKEUP : Task[10] SOCK SOCK-PROC pty=27    
Tue 2021/03/16 05:32:39 PM    System    -110022    /CONF/ELKXPRT.XML    
Tue 2021/03/16 05:32:39 PM    System    -7153    ID 0002 :err=0, tag='/group', num=20, nest=5, o    
Tue 2021/03/16 05:32:40 PM    System    -110022    /CONF/UZWNDKEY.TXT    
Tue 2021/03/16 05:32:40 PM    System    -110012    /CONF/UZWNDKEY.TXT    
Tue 2021/03/16 05:32:40 PM    System    -170001    [Network] Established    
Tue 2021/03/16 05:59:10 PM    System    -50001    -20    
Tue 2021/03/16 05:59:20 PM    System    -50001    -20  

Can anyone tell me if there's something I've obviously done wrong?  In any case, I think maybe crashing isn't a desirable behavior.

 

Thanks!

ISY Email.PNG

Try the following to see if there is any change in behavior:

SMTP Server: smtp-mail.outlook.com

Time Out: 1000

From: ISY Series Controller: whateverisyouremail@hotmail.com

Link to comment
13 hours ago, Teken said:

Try the following to see if there is any change in behavior:

SMTP Server: smtp-mail.outlook.com

Time Out: 1000

From: ISY Series Controller: whateverisyouremail@hotmail.com

Thanks for the suggestion.  I tried that and the behavior is slightly modified, but not much.  The Test operation still causes the ISY controller to abruptly crash and and restart.  I no longer see the authentication error (-20) in the log, however.  Now the tail of the error log shows the last event last night followed by the startup after the crash this morning:

Tue 2021/03/16 06:11:32 PM    System    -170001    [Network] Established    
Wed 2021/03/17 08:38:25 AM    System    -5    Start    
Wed 2021/03/17 08:38:31 AM    System    -110022    /DEF/F6/I1/NLS/EN_US.TXT    
Wed 2021/03/17 08:38:31 AM    System    -110022    /CONF/UXT.BIN    
Wed 2021/03/17 08:38:31 AM    System    -110012    /CONF/UXT.BIN    
Wed 2021/03/17 08:38:33 AM    System    -170001    UDQ:Queue Full: IPOLLWAKEUP : Task[10] SOCK SOCK-PROC pty=27    
Wed 2021/03/17 08:38:32 AM    System    -110022    /CONF/ELKXPRT.XML    
Wed 2021/03/17 08:38:32 AM    System    -7153    ID 0002 :err=0, tag='/group', num=20, nest=5, o    
Wed 2021/03/17 08:38:33 AM    System    -110022    /CONF/UZWNDKEY.TXT    
Wed 2021/03/17 08:38:33 AM    System    -110012    /CONF/UZWNDKEY.TXT    

So, better I think, but it still seems quite problematic that the controller crashes.  And email does not go through.

 

Thanks!

Link to comment
35 minutes ago, CMcCarron said:

Thanks for the suggestion.  I tried that and the behavior is slightly modified, but not much.  The Test operation still causes the ISY controller to abruptly crash and and restart.  I no longer see the authentication error (-20) in the log, however.  Now the tail of the error log shows the last event last night followed by the startup after the crash this morning:

Tue 2021/03/16 06:11:32 PM    System    -170001    [Network] Established    
Wed 2021/03/17 08:38:25 AM    System    -5    Start    
Wed 2021/03/17 08:38:31 AM    System    -110022    /DEF/F6/I1/NLS/EN_US.TXT    
Wed 2021/03/17 08:38:31 AM    System    -110022    /CONF/UXT.BIN    
Wed 2021/03/17 08:38:31 AM    System    -110012    /CONF/UXT.BIN    
Wed 2021/03/17 08:38:33 AM    System    -170001    UDQ:Queue Full: IPOLLWAKEUP : Task[10] SOCK SOCK-PROC pty=27    
Wed 2021/03/17 08:38:32 AM    System    -110022    /CONF/ELKXPRT.XML    
Wed 2021/03/17 08:38:32 AM    System    -7153    ID 0002 :err=0, tag='/group', num=20, nest=5, o    
Wed 2021/03/17 08:38:33 AM    System    -110022    /CONF/UZWNDKEY.TXT    
Wed 2021/03/17 08:38:33 AM    System    -110012    /CONF/UZWNDKEY.TXT    

So, better I think, but it still seems quite problematic that the controller crashes.  And email does not go through.

 

Thanks!

The 110022 error message means: -SET SESSION KEY UNSUPPORTED BULK ALGORITHM

What is the contents of the notification you are trying to send? Maybe something is corrupt with the notification. Try deleting it and creating a new test notification with a different name.

Link to comment
15 hours ago, Teken said:

From: ISY Series Controller: whateverisyouremail@hotmail.com

It's been awhile since I experienced a similar issue, but I think the : can't have a space on either side of it--however I don't think it caused the ISY to crash, i think the mail send simply errored out. 

personally I also need a greater than 1 second timeout.

@CMcCarron are you using the "test" button to crash the ISY or is an actual program in use? 

 

Link to comment
1 hour ago, DennisC said:

The 110022 error message means: -SET SESSION KEY UNSUPPORTED BULK ALGORITHM

What is the contents of the notification you are trying to send? Maybe something is corrupt with the notification. Try deleting it and creating a new test notification with a different name.

Interesting, I'll try that but an unsupported bulk key sounds like the TLS session couldn't negotiate a bulk encryption algorithm.  I know Outlook365 has been deprecating everything before TLS1.2, is there any information (or way to control) what the ISY uses?  

 

Thanks!

Link to comment

I’d start with the basic which should have been done.

- Can you send & receive email now from this account. Use another email and validate new mail arrives without issue.

- Are there default filter rules in place to reduce spam / junk. If so disable them and check.

- Firewall: If there are any firewall rules in place disable them all to see cause & effect.

- Antivirus: Disable all to see cause & effect.

- Gmail: Create a Gmail account and see if mail arrives successfully.

- WiKi: The UDI WiKi will call out all of the network errors to narrow down possible root cause.

- Support: If trying all of the above create a support ticket with UDI. Reference this thread and relay all error logs with your submission.

Link to comment
23 minutes ago, Teken said:

I’d start with the basic which should have been done.

- Can you send & receive email now from this account. Use another email and validate new mail arrives without issue.

- Are there default filter rules in place to reduce spam / junk. If so disable them and check.

- Firewall: If there are any firewall rules in place disable them all to see cause & effect.

- Antivirus: Disable all to see cause & effect.

- Gmail: Create a Gmail account and see if mail arrives successfully.

- WiKi: The UDI WiKi will call out all of the network errors to narrow down possible root cause.

- Support: If trying all of the above create a support ticket with UDI. Reference this thread and relay all error logs with your submission.

The account is working fine, I'm using a couple of other clients to test it and send and receive is definitely OK.  I'm not sure I can do much with antivirus, I mean, this is crashing the ISY itself, it hasn't anything to do with a machine where I control the operating system or software running.  I did find this document ISY994 Series Network Security Guide.pdf (universal-devices.com) and I verified that the HTTPS client settings are TLS1.2.  I cant tell for sure that this applies to SMTP but, if it does, then I wonder if the handshake here can negotiate a bulk encryption algorithm (the error sounds that way).

I unfortunately don't have a switch where I can mirror the port and capture the TLS hello and check this out.  I wonder if anyone else is having any luck using outlook365/hotmail since around Dec of last year (that's when the protocol support may have changed according to the docs)?

Thanks.

Link to comment
The account is working fine, I'm using a couple of other clients to test it and send and receive is definitely OK.  I'm not sure I can do much with antivirus, I mean, this is crashing the ISY itself, it hasn't anything to do with a machine where I control the operating system or software running.  I did find this document ISY994 Series Network Security Guide.pdf (universal-devices.com) and I verified that the HTTPS client settings are TLS1.2.  I cant tell for sure that this applies to SMTP but, if it does, then I wonder if the handshake here can negotiate a bulk encryption algorithm (the error sounds that way).
I unfortunately don't have a switch where I can mirror the port and capture the TLS hello and check this out.  I wonder if anyone else is having any luck using outlook365/hotmail since around Dec of last year (that's when the protocol support may have changed according to the docs)?
Thanks.

I’d create a dedicated gmail account for the ISY Series Controller. This would be a interim break fix so emails could be sent out. Until you figure out the technical issues with O365.
Link to comment

Actually, looking at this more closely, the reply from DennisC is a little off.  The error is a -100022, not -10022.  According to ISY-99i/ISY-26 INSTEON:Errors And Error Messages - Universal Devices, Inc. Wiki (universal-devices.com), this is actually OPEN FILE FAILED.  The other error at the same point was SD DRIVE CONFIG FILE OPEN READ FAILED.  So it would seem as if there might be a problem opening or reading a config file and this might really have nothing whatsoever to do with encryption, security or communication.

I'll run down this path for a bit and see if I can find anything and open a support case if not.

 

Thanks.

Link to comment
6 hours ago, CMcCarron said:

Actually, looking at this more closely, the reply from DennisC is a little off.  The error is a -100022, not -10022.  According to ISY-99i/ISY-26 INSTEON:Errors And Error Messages - Universal Devices, Inc. Wiki (universal-devices.com), this is actually OPEN FILE FAILED.  The other error at the same point was SD DRIVE CONFIG FILE OPEN READ FAILED.  So it would seem as if there might be a problem opening or reading a config file and this might really have nothing whatsoever to do with encryption, security or communication.

I'll run down this path for a bit and see if I can find anything and open a support case if not.

 

Thanks.

Apologies, didn't mean to send you down the wrong path......

Link to comment

Archived

This topic is now archived and is closed to further replies.


  • Recently Browsing

    • No registered users viewing this page.
  • Who's Online (See full list)

  • Forum Statistics

    • Total Topics
      36.9k
    • Total Posts
      370.2k
×
×
  • Create New...