CMcCarron

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.

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.

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!

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!

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!

Disregard that please - apparently still had ElkRP connected so the refresh silently fails.

I wonder if there are any other troubleshooting steps for this condition that anyone can suggest? I just added the Elk module to my ISY and no matter what I do I can only get outputs 065 - 208. I've tried to refresh it and it doesn't really help. The module is communicating - I can see that when I trip a zone the status changes immediately at the ISY. But no matter what I seem to do, including reboots and refreshes, I can't get the outputs below 065 to show up. Any ideas appreciated!