wswartz Posted August 11, 2015 Posted August 11, 2015 ISY 994i Pro v4.2.30 Have had an issue for about a year with my ISY locking up on occasion. Only happens about once a week or so but seems to be happening more frequently, thus my concern. Only pattern I can notice is it seems to happen just as I'm entering a control interface. For example, I observe the ISY is working (based on lighting changes in the house or something), then I access either the web interface (as user or admin), the Java interface, or use my MobileLinc. When it happens, I'll get no response from the respective interface I'm using at the time. From there I'll ping the ISY and get no response. Recovery is to unplug the ISY to reboot. This happened prior to my recent upgrade to v4.2.30 (don't recall what version that was). Any thoughts on what to check? Bill
Michel Kohanim Posted August 11, 2015 Posted August 11, 2015 Hi Bill, Please send your error log to support@universal-devices.com. With kind regards, Michel
Teken Posted August 11, 2015 Posted August 11, 2015 ISY 994i Pro v4.2.30 Have had an issue for about a year with my ISY locking up on occasion. Only happens about once a week or so but seems to be happening more frequently, thus my concern. Only pattern I can notice is it seems to happen just as I'm entering a control interface. For example, I observe the ISY is working (based on lighting changes in the house or something), then I access either the web interface (as user or admin), the Java interface, or use my MobileLinc. When it happens, I'll get no response from the respective interface I'm using at the time. From there I'll ping the ISY and get no response. Recovery is to unplug the ISY to reboot. This happened prior to my recent upgrade to v4.2.30 (don't recall what version that was). Any thoughts on what to check? Bill Hello Bill, Just some quick feed back as to some items you can check to insure they are not the root cause. 1. Very tight timed or looping programs. 2. Network Traffic: If you have 3rd party devices which send data to the ISY via state variables. Ensure the send interval is not set too low such as every 5 seconds etc. 3. SMTP Traffic: Confirm you don't have lots of e-mails being sent out by the system. I know its fanciful for people to receive all kinds of alerts based on MS movement, window, doors, being open. But if you have a active family, pets, etc having the ISY send 10-20 emails under a minute uses up lots of resources. 4. KPL Blink: Lots of people use this method to make a KPL blink. I know lots of people are a fan of this because it gives a good feed back etc. But, this can cause lots of Insteon traffic and ties up the ISY when more than one KPL is doing the LED flash dance. 5. Anti Virus / Firewall: You should always check the anti virus / firewall to insure rules or policies have not changed. Often times a update of the two will cause the conflict where the system takes longer to connect etc. 6. Run at start up: It should be noted that if you have lots of programs that run at startup. You should consider scaling a few down to only have mission critical programs run at start up. 7. Query: I know lots of people who use query as a method to verify the state of a device. Mostly as a band aid to poor communications etc. Please verify if you have lots of query programs or query all of the system. I have seen a few people who actually query the entire network on multiple timed intervals. Doing so ties up the ISY Series Controller from doing anything else and this comes across as the unit is locked up. But in fact its super busy processing etc. Most of the tasks and processes are based on FIFO (First In, First Out)
Recommended Posts