paauto Posted January 26, 2016 Posted January 26, 2016 My ISY 994i has frozen up (won't run programs and failes to communicate with my computer via IP Address). If I unplug it and the PLM and then re-plug in, seems to work fine. First time was week or so ago and tehn again today. Is the ISY dying?
Teken Posted January 26, 2016 Posted January 26, 2016 (edited) My ISY 994i has frozen up (won't run programs and failes to communicate with my computer via IP Address). If I unplug it and the PLM and then re-plug in, seems to work fine. First time was week or so ago and tehn again today. Is the ISY dying? The real question you should be asking is how old is the 2413S PLM and is it fast approaching the two year death mark? Also do a PLM link count and see how many links the system shows. Run it a few times to ensure its accurate . . . If you have like 25-50 devices and you see something really stupid like 12 links. Well, you have your answer and need to either repair the PLM or purchase another unit. NOTE: For the benefit of others please state if the ISY has any LED's lit up when you notice this problem arise. Using the Wiki you can determine what the LED's indicate and best course of action to take if its the controller itself. Lastly, its rare but ensure the power supply to the controller is fine. Edited January 26, 2016 by Teken
paauto Posted January 26, 2016 Author Posted January 26, 2016 PLM is about a year old. I have spare sitting on the counter next to it for all the reasons we know... The reason I think it is my ISY is I tried to access it via its IP address via my computer and no luck )i.e. accessing it directly, not thru PLM). Just got home and rebooted and its working fine now. Also rebooted the PLM so too late to rule that out.
Teken Posted January 26, 2016 Posted January 26, 2016 PLM is about a year old. I have spare sitting on the counter next to it for all the reasons we know... The reason I think it is my ISY is I tried to access it via its IP address via my computer and no luck )i.e. accessing it directly, not thru PLM). Just got home and rebooted and its working fine now. Also rebooted the PLM so too late to rule that out. Once the controller settles down login and let us know the PLM link count. Also can you let us know what firmware you're running right now? Make sure the Help -> About indicates the UI & Firmware is the same . . . Aside from those basic things you should confirm if your system has any programs that have conflicts or if you have lots of network resources in use now. Specifically you need to verify there aren't too many tight loop programs running with short intervals. You also need to limit any of the many silly things I see people doing like making the controller flash and beep Insteon devices. Just doing this act will tie up the controller forever . . . You should also confirm best practices are in play which is - is your network and the computer that is accessing the controller is properly accessible from firewall, anti-virus, port forwarding, and random ISP IP changes. Best thing is to save both error logs and send it to UDI for direct support and reference this thread. This will get the ball going and limit all the guessing from this point forward. You may create a service request using this resource link: http://www.universal-devices.com/contact-support/
stusviews Posted January 27, 2016 Posted January 27, 2016 If you power cycle anything, then order is important. Power up the PLM first, wait a few seconds and then power up the ISY.
paauto Posted January 27, 2016 Author Posted January 27, 2016 Once the controller settles down login and let us know the PLM link count. Also can you let us know what firmware you're running right now? Make sure the Help -> About indicates the UI & Firmware is the same . . . Aside from those basic things you should confirm if your system has any programs that have conflicts or if you have lots of network resources in use now. Specifically you need to verify there aren't too many tight loop programs running with short intervals. You also need to limit any of the many silly things I see people doing like making the controller flash and beep Insteon devices. Just doing this act will tie up the controller forever . . . You should also confirm best practices are in play which is - is your network and the computer that is accessing the controller is properly accessible from firewall, anti-virus, port forwarding, and random ISP IP changes. Best thing is to save both error logs and send it to UDI for direct support and reference this thread. This will get the ball going and limit all the guessing from this point forward. You may create a service request using this resource link: http://www.universal-devices.com/contact-support/ Confirmed that my firmware and UI are both 4.3.26. PLM Link count 445. Checked log and nothing out of the ordinary seemed to be going on when things crashed. Confirmed computer, router, port forwarding all good and working. Will submit error log. Thx.
paauto Posted January 27, 2016 Author Posted January 27, 2016 Submitted the ticket and heard back immediately. Here's what they said. BTW, what great support! I am so very sorry to hear. If you are using MobiLinc and specifically Apple Watch, the issue is that MobiLinc does not close sockets consistently. This has been identified and we put a solution that forcefully closes these sockets in 4.4.2. Please do be kind enough to:1. Clear your Error Log2. Install 4.4.2 (which is very stable): http://forum.universal-devices.com/topic/17732-release-442-beta-is-now-available/Let us know if you still have the same issues.With kind regards,****************************** With kind regards,*****************************************UDI Tech Support Michel KohanimUniversal Devices, Inc.support@universal-devices.com
Teken Posted January 27, 2016 Posted January 27, 2016 Let us know if updating to 4.4.2 resolves the access issue. In the end, we will remember not the words of our enemies, but the silence of our friends.
paauto Posted January 27, 2016 Author Posted January 27, 2016 Let us know if updating to 4.4.2 resolves the access issue. In the end, we will remember not the words of our enemies, but the silence of our friends. will do. Suspect time will tell as it sounds like it has to do with repetitive use of Mobilinc and things not clearing out on the ISY and then freezing it. so far so good. That's my interpretation, but recognize i'm not super technical.
Recommended Posts