Jump to content

My ISY seems to have gotten forgetful


waffles

Recommended Posts

As of recent my ISY 994i has started acting a bit weird. I have noticed it with some programs where all of a sudden Notifications are no longer being sent. This despite no code or any other apparent changes to the set up. I had been using F/W 5.0.16 RC1 for several months and very recently updated to 5.0.16B RC1. It has happened with both versions.

Using the Test feature to test the SMTP settings (Default, as well as my own ones) are successful. Creating new test programs to trigger notifications work also.

Here is what I did to fix this issue - all methods worked, but only for some time.

1. Restore ISY and Devices (first time it worked, the second time it did not fix the issue)

2. Rebuilding my recipient Group and Customizations (Name/Customized Cotent), basically by copy/pasting the old ones.

 

This morning I noticed that the entry for the recipients under Groups is empty, i.e. there are no longer any Recipients listed. However, my ISY just sent me an email as it should have based on the program that has been running.?

 

The ISY seems to be working fine otherwise, e.g. Scenes are all working as far as I can tell.

 

I wonder what the root cause could be. Is the SD card is failing or corrupted? ISY and card are 1/2 dozen + years old.

 

Looking forward to your thoughts and suggestions....

Thanks!

Link to comment

I suppose it could be the SD card, but I would think that you would get error messages, not just missing functions.

The fact that scenes work does not mean anything.  Scenes are all Insteon device to Insteon device.  ISY is only involved if it is the root cause of the scene turning on/off.

I am thinking it is more likely you are not getting your notifications because the PLM is going bad.  I'm assuming your notifications are in response to something that happened to an Insteon device.  The PLM is the gateway between Insteon and ISY.  Bad PLM means ISY loses touch with Insteon devices.  The PLM is a VERY common failure point.  The ISY is a VERY rare failure point.  The SD card is only slightly more common failure point.  As the saying goes, when you hear hoofs, think horse, not zebra (unless you are in the Savanna). 

Link to comment

Thanks apostolakisl.

The responses are not in regards to a PLM. They are basically notifications about timers, so it's all 'w/in' the ISY. (Even though I had several PLMs failing on me in the past and the symptoms were as you said (loosing touch).)

I did not see any error messages, also the logs did not mention anything (that said, I have not found the build in ISY logs under Tools very useful).

 

I think I'll try a new SD card next. A new one is only a few $$.

 

Link to comment

No devices.

The trigger comes from Alexa, setting a Variable to trigger the notification. This works fine: in the ISY I can see the variable changing and the program icon flip to green. I can currently get messages, even though the Recipients field is empty and the Notifications are being sent to "3", which technically should no longer exist (I had this set up during earlier troubleshooting).

 

In the meantime I was able to find an old 2GB SD card which I formatted with my Win10 PC (I tried formatting it through the ISY (telnet and FS per wiki), but it never completed). Unfortunately, this was also unsuccessful: while the Recipients were visible again and everything else seemingly was there, I kept getting LIB_ERRORS-403 during log-on though the admin console. Also I was not able to connect to the ISY through the Portal (it showed the device as offline). I tried reformatting the 2 GB SD card several times, as well as restoring from different, in part rather old back up versions, but all to no avail.

Not sure if this is caused by a bad SD card, but I have now a brand new one (16GB) on order.

 

2019-12-25_15h41_41.png

2019-12-25_15h44_44.png

Link to comment

Hello Michel;

 

Here is are the recent error log entries

existing setup (the forgetful one):

2019/12/25 13:51:21  System    -5     Start

2019/12/25 13:51:28  System    -110022 /DEF/F6/I1/NLS/EN_US.TXT

2019/12/25 13:51:29  System    -110022 /CONF/UXT.BIN

2019/12/25 13:51:29  System    -110012 /CONF/UXT.BIN

2019/12/25 13:51:31  System    -170001 [Network] Established

2019/12/25 14:06:06  System    -5011  uuid:0

2019/12/26 01:51:37  System    -100   [DHCP] state=RENEW

2019/12/26 07:23:54  System    -5     Start

2019/12/26 07:24:01  System    -110022 /DEF/F6/I1/NLS/EN_US.TXT

2019/12/26 07:24:01  System    -110022 /CONF/UXT.BIN

2019/12/26 07:24:01  System    -110012 /CONF/UXT.BIN

2019/12/26 07:24:04  System    -170001 [Network] Established

2019/12/26 07:28:52  System    -5006  uuid:28

 

and my lookup of the messages:

-5: no error message found in wiki
-5006: no error message found in wiki

-5011: PROCESS DEVICE STATE CHANGE SID NOT FOUND
-110012: SD DRIVE CONFIG FILE OPEN READ FAILED
-110022: OPEN FILE FAILED
    
-170001: no error message found in wiki

 

with replacement SD card setup (the one I cannot connect to the portal):

This is the complete log after another fresh restore just now with my most recent backup file:

Time                          User         Code    Message
Thu 2019/12/26 07:45:16 AM    System    -5    Start    
Thu 2019/12/26 07:45:17 AM    System    -110022    /CONF/INSTENG.OPT    
Thu 2019/12/26 07:45:17 AM    System    -110012    /CONF/INSTENG.OPT    
Thu 2019/12/26 07:45:17 AM    System    -110022    /DEF/F1/I1/NLS/EN_US.TXT    
Thu 2019/12/26 07:45:17 AM    System    -110022    /CONF/UXT.BIN    
Thu 2019/12/26 07:45:17 AM    System    -110012    /CONF/UXT.BIN    
Thu 2019/12/26 07:45:17 AM    System    -110022    /WEB/ELKNLS.XML    
Thu 2019/12/26 07:45:17 AM    System    -170001    [Network] Established    
Thu 2019/12/26 07:45:17 AM    System    -110022    /CONF/PORTALS.PSF    
Thu 2019/12/26 07:45:17 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:45:46 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:45:58 AM    System    -110022    /WEB/DRIVER.XML    
Thu 2019/12/26 04:45:58 AM    System    -110022    /WEB/DRIVER.XML    
Thu 2019/12/26 04:46:16 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:46:46 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:47:17 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:47:47 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:48:17 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:48:47 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:49:17 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:49:47 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:50:17 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:50:39 AM    System    -5    Start    
Thu 2019/12/26 04:50:41 AM    System    -110022    /DEF/F1/I1/NLS/EN_US.TXT    
Thu 2019/12/26 04:50:41 AM    System    -110022    /DEF/F4/I1/NLS/EN_US.TXT    
Thu 2019/12/26 04:50:41 AM    System    -110022    /DEF/F6/I1/NLS/EN_US.TXT    
Thu 2019/12/26 04:50:41 AM    System    -110022    /CONF/UXT.BIN    
Thu 2019/12/26 04:50:41 AM    System    -110012    /CONF/UXT.BIN    
Thu 2019/12/26 04:50:41 AM    System    -110022    /WEB/ELKNLS.XML    
Thu 2019/12/26 04:50:43 AM    System    -170001    [Network] Established    
Thu 2019/12/26 04:50:44 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:51:14 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:51:44 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:51:55 AM    System    -110022    /WEB/DRIVER.XML    
Thu 2019/12/26 04:51:55 AM    System    -110022    /WEB/DRIVER.XML    
Thu 2019/12/26 04:52:00 AM    System    -10011    n/a    
Thu 2019/12/26 04:52:14 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:52:44 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:53:03 AM    System    -110022    /WEB/DRIVER.XML    
Thu 2019/12/26 04:53:03 AM    System    -110022    /WEB/DRIVER.XML    
Thu 2019/12/26 04:53:14 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:55:13 AM    System    -5    Start    
Thu 2019/12/26 04:55:15 AM    System    -110022    /DEF/F1/I1/NLS/EN_US.TXT    
Thu 2019/12/26 04:55:15 AM    System    -110022    /DEF/F4/I1/NLS/EN_US.TXT    
Thu 2019/12/26 04:55:15 AM    System    -110022    /DEF/F6/I1/NLS/EN_US.TXT    
Thu 2019/12/26 04:55:16 AM    System    -110022    /CONF/UXT.BIN    
Thu 2019/12/26 04:55:16 AM    System    -110012    /CONF/UXT.BIN    
Thu 2019/12/26 04:55:16 AM    System    -110022    /WEB/ELKNLS.XML    
Thu 2019/12/26 04:55:17 AM    System    -170001    [Network] Established    
Thu 2019/12/26 04:55:17 AM    System    -170001    [TCP-Conn] -256/-140002, Portal-Dispatch    
Thu 2019/12/26 04:55:28 AM    System    -5006    uuid:27    
Thu 2019/12/26 04:55:37 AM    System    -110022    /WEB/DRIVER.XML    
Thu 2019/12/26 04:55:37 AM    System    -110022    /WEB/DRIVER.XML    
Thu 2019/12/26 04:55:45 AM    System    -10011    n/a

 

No SMTP errrors, but a bunch of System messages/errors.

Where should I go from here?

Link to comment

@Michel Kohanim

Funny! That's actually that's what I just did :-)   

Before that I had installed the brand new 16GB SD card, as well as doing a factory reset of the ISY.  This did not do the trick, e.g. no access to Portal.  Then I noticed that there was a difference between F/W and UI version: v5.0.16B vs. v5.0.16, so I decided to reinstall the F/W.  While the versions have not changed (=> is this correct?), the ISY is now connected to the Portal.

 

I also noticed:

  • Logon credentials had reverted to default (admin, admin) and had not been retained

  • System location settings had not been retained.

=> Is this normal after a config restore?

 

This is a fresh error log, after an ISY reboot:

2019/12/27 12:17:28  System    -5	Start
2019/12/27 12:17:34  System    -110022	/DEF/F6/I1/NLS/EN_US.TXT
2019/12/27 12:17:35  System    -110022	/CONF/UXT.BIN
2019/12/27 12:17:35  System    -110012	/CONF/UXT.BIN
2019/12/27 12:17:37  System    -170001	[Network] Established

 

-110012: SD DRIVE CONFIG FILE OPEN READ FAILED
-110022: OPEN FILE FAILED

 

So it seems there are still file errors, correct?

=> How do I address this?

 

2019-12-27_11h50_44.png

Link to comment

Archived

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


×
×
  • Create New...