Michel Kohanim

Hello bbb2008, Please go to Help->About and check My URL. If you do not see :port at the end of the URL, then the port is 80. Otherwise, the port will be indicated. With kind regards, Michel

Hello bbb2008, Please go to Help->About and check My URL. If you do not see :port at the end of the URL, then the port is 80. Otherwise, the port will be indicated. With kind regards, Michel

Hi Joe, Boy, you do get the strangest problems. Was this Error and Mem blinking or just MEM? If so, do you have screen capture of the error? I checked our error codes and we do not have I/O error messages. Are you talking about "-2" errors? With kind regards, Michel

Hello RLIKWARTZ, Are you still having intermittent issues with your older devices after going through all this? With kind regards, Michel

upstatemike, Apologies for the inconvenience. I will have to check into the PLM links table issue as it seems to be a bug. Indeed, there can only be 4 issues contributing to this problem: 1. Noise ... not ruled out yet 2. i2 .... which is ruled out (because you are using old switches) 3. PLM ... not ruled out yet 4. ISY ... not ruled out yet So, may I humbly suggest actually replacing the PLM? We do have a spare one that I can send you for your testing purposes. With kind regards, Michel

Hi RichTJ99, Yes and yes. If you really want to do it, make sure you use scenes. With kind regards, Michel

CompKing! I just had to post because you just made my day .... after a LOOOONG day, I needed this laugh! LOL. With kind regards, Michel

Hello Bill, Thanks so very much for the update. This is not good at all. Has anything else changed in your environment? A new computer, an older monitor, anything at all. I really do not think the difference between version would cause such drastic problems unless the PLM is not handling the i2 commands (and is becoming deaf/dumb). This is very possible if you have PLMs version 58 and below. Please do be kind enough to keep me posted. With kind regards, Michel

Hi Zellarman, All programs refer to addresses of devices and NOT names. So, even if you have renamed and moved them to different scenes, they should automatically be reflected. This said, however, if you have replaced a device with a new device, you will see an Unknown in the programs referring to a device that no longer exists. With kind regards, Michel

Hello RLIKWARTZ, Are these devices new? Specifically, are they the SWLs and LampLincs? With kind regards, Michel

Hi Rich, Yes, absolutely! With kind regards, Michel

Hello Zellarman, Were you aware that SignaLincs do not support i2? Have you recently added new i2 devices? With kind regards, Michel

Hi Rich, Yes, All on/Off will always do ONLY/ALL the devices that have been linked to your RL. Depending on your case, this might be a subset of all your devices. With kind regards, Michel

huddadudda, I do not recommend 2.6.7. If you wish, please downgrade to 2.6.8. The .und files are definitions (name/address) for the nodes and have no impact on communications. I think this file was in use while you tried to back it up. If this persists, please reboot your ISY and retry. With kind regards, Michel

Hello, We do have instructions for almost all routers here: http://forum.universal-devices.com/viewtopic.php?t=635 This post will give you the link to portforward.com which has details of port forwarding for ALL routers. With kind regards, Michel

Hello AD8BC, These are known issues with the latest SWL, KPL, and LL/AL firmware. SmartHome is trying to resolve/debug/pinpoint these issues as we speak. How long more do you have on your 30 day? With kind regards, Michel

Hi Rich, If you put your devices in scenes, then you can program them without having to airgap. But, the main issue is that programming on level/ramp rates may take a long time (depending on the number of devices in the scene) and it's usually not worth the trouble and extra traffic. With kind regards, Michel

Hi Rich, I cannot answer the last question by for the first two questions: RL's All on/All off controls ANYTHING that has been linked to RL. The caveat is that the onlevels and ramprates are taken from the first ever linkage to the RL. Yes, you can assign a button for All On/All Off but you will have to create a scene with all your devices (unless you want to use the All on/off button -- see above) With kind regards, Michel

Hi CompKing, Yes, I have scene this and, as Zellarman suggests, it has to do with the IR sensor being close to Plasma TV. Please do keep me posted. With kind regards, Michel

CJVann, I think there's a bit of confusion here: It is NOT the case that INSTEON devices uses the ramp rate of the last scene: 1. They use their stored/default ramp rate/on level. 2. Now, this is ONLY true if you are turning on/off the device directly. If you turn on/off the device through a scene, then the ramp rate/on level for that scene takes over. 3. If you control the device through another controller, then the ramp rate/on level for that controller-device combination takes over. 4. And, FINALLY, if you turn on/off My Lighting, then the ramp rate/on level for the FIRST ever scene of which the device is a part take over. All this said, which scenario are you referring to? With kind regards, Michel

JasonWPB, This is NOT normal at all. When you go to the configuration tab, do you get Request Failed when you try synchronizing with the NTP server? With kind regards, Michel

Hello again, This is a great progress. What this means is that your M1XEP either requires a reboot or has a bug. I strongly suggest rebooting your M1XEP and retrying the port 2101 as I think there are some strange things happening here. If that does not work, then I suspect you have another device on your network with the same IP address as your M1XEP. If you are connected to your M1 RP (which it seems you are), then NOTHING will work neither lighting rules from within ELK nor commands from ISY. The only thing that may work (intermittently at best) is arm/disarm. With kind regards, Michel

Hi again, This is quite strange to say the least. Do you see any errors in ISY's log? With kind regards, Michel

Hello again, The bug should not impact your programs right now. If you see 0 for the status of your thermostats, then please go to Help->About and let me know the version number. With kind regards, Michel

Hi Rob, Yes, the unsecured port will not work. Which port are you using now and are you sure this is the right port configured in M1? With kind regards, Michel