Michel Kohanim

Hello AnthemAVM, These should be solved in 2.6.4 and they have to do with the timeout value for the HTTP/HTTPS request which will be configurable in 2.6.4. With kind regards, Michel

Hello, If you have version 2.6.1 and above, then the port is 443 and your external URL should be httpS://your.exteral.ip.address . Otherwise, please go to Help->About. In My URL field, the port is the number after the ':' in your URL. So, if you have http://192.168.1.101:62345 then the port is 62345. With kind regards, Michel

Linuxguy, You are 100% correct. It shall be done. Thanks and with kind regards, Michel

Hello AnthemAVM, If you have upgraded to the latest release, two things could be causing this: 1. Clear your Java Cache (Control Panel->Java->Settings Button->Delete Files) 2. Depending on your firewalls software, checkout: http://forum.universal-devices.com/viewforum.php?f=3 From experience, I can tell you that I think it's your firewall software. With kind regards, Michel

AnthemAVM, Please retry File->Enable Internet Access (or make sure your port is forwarded to the correct IP). With kind regards, Michel

k6jav, If you've setup your port manually, then there is no longer a need to issue File->Enable Internet Access. You would use File->Enable Internet Access if a) you have UPnP Router you would like ISY to create the port forwarding rules for you With kind regards, Michel

jswedberg, Yes, this has been resolved in 2.6.4 and it's related to connection timeout values. 2.6.4 should be out by the end of next week. With kind regards, Michel

aj, Please peruse this post: http://forum.universal-devices.com/viewtopic.php?t=635 and let us know if you still exprience any problems connecting remotely. with kind regards, Michel

Hello Jim, Please do be kind enough to let me know you still experience #1 below when you install 2.6.4 (due out by the end of next week). Thanks and with kind regards, Michel

clark21236, Thanks so very much for the update. For next time, may I humbly suggest rebooting ISY/PLM as the last resort? It could also be the location of the PLM and especially the UPS. With kind regards, Michel

Hi Matt, This is getting to be very strange. There are usually only two causes for this issue: 1. Corrupt/incompatible file 2. Firewall May I humbly ask what firewall software you have? With kind regards, Michel

clark21236, I am a little concerned that this problem is going to repeat itself. I've heard some UPS devices cause noise but I cannot be sure. With kind regards, Michel

Digger, Have you looked at your logs? If not, please do so and look for Scheduler entries during the same time that you experienced the flashing lights. Unplugging ISY simply means that ISY is not getting the signals from the PLM and those are the signals that I am very interested about. With kind regards, Michel It happened again last night. We had a power dip for a second or so and the entrance way light started flasing a minute or two later. I tried turning it off and it kept flashing, I tried turning it on and it kept flashing. I unplugged the ELK M1 ethernet connection and it kept flashing. I unplugged the ISY and it stopped. I plugged the ISY back in and it was fine.

Hi, Thanks so very much for the update. As far as the hour glass, I would not worry about it at all since it depends on the position of the mouse with respect to the progress bar. What worries me is that you have an intermittent communication problem and I suspect that it's not going to go away by itself. Do you have a filterlinc that you can use to isolate your computer. Also, what time of day did you try to perform the same operation on the previous attempt? Was there anything else on at the same time (plasma TV)? With kind regards, Michel

Hello 1001001, I am so very sorry. This is quite strange since I just downloaded it again and upgraded our lab's without a problem. Do you have any type of firewall software? Is your ISY on the internet? Can I access it remotely? If so, please send us your link/credentials to support@universal-devices.com. With kind regards, Michel

az1324, Consider it done! With kind regards, Michel

Hi Clark, Thanks and please do keep us posted. Also, you might want to try the DBG command (in the shell) and look at your Java console to see where it fails. With kind regards, Michel Yes, it still failed. I just tried the query from My Lighting and had no problems. And my laundry room program ran fine this morning. I tried it when I got home as well, and it worked then too. Yes, I have a long Ethernet cable. I will move the ISY and PLM to the outlet below my keypadlinc and see how it works. Presently they are only 20ft apart. Not saying that it is on the same phase, or it will be when I move it either. I have an access point in between them as well, by the way the crow flies.

Hello 1001001 (73?), I do apologize for the inconvenience. Would you be kind enough to retry the same link again (download)? With kind regards, Michel

Hello Clark, You are 100% correct: if a device is already at a level, the log does not show that the device was activated again. Do you still get Request Failed on your KPL Relay. We've had some problems with KPL Relays before but all isolated to Mutex/Toggle modes. Is it possible to move your KPL closer to your PLM and see whether or not you have the same issue? With kind regards, Michel

Chuck, That's true. Run simply runs the Then part. With kind regards, Michel

Hi, Unfortunately, not at the moment. With kind regards, Michel

az1324, If you are 100% sure that this has no effect on other browsers, we can immediately add it. With kind regards, Michel

Hello again, This is quite strange indeed. The log shows that the Scene was triggered by a program but the only program that activates that scene is based on a Fast On which is nowhere to be found in the log (in that time period). So, either the scene was triggered by the same program and the log is inaccurate or the program is run by itself. Either case is quite disturbing! As far as request failed, please do a query on your Network (top most node in the tree) and see if you get any device communication errors. In all likelihood, ISY cannot communicate with your device either because of noise or a defective PLM. With kind regards, Michel

Hello d_l, You can use the timers in EZRain but the only problem is that ISY does NOT hear EZRain's change of state and thus your ISY status will not be in synch with the actual EZRain. Of course, the Query at 3:00 AM will make them in synch again. In short, if you don't care whether or not ISY/EZRain states are in synch, and if you don't have any other conflicting programs, then you should be OK. With kind regards, Michel

CompKing, You do NOT need to open port 80 on your router to access ISY locally on the LAN. All you need is to figure out what's your ISY's local LAN IP address. So, please do not open the port 80 on your router. With kind regards, Michel