Michel Kohanim

Hi David, Thanks for the update and yes it does make sense. Unfortunately, the only way to remove X10 address is via Factory reset. With kind regards, Michel

Hi AutomationNut, At a very high level: INST-ACK is the PLM acknowledging the receipt of an ISY command INST-SRX is whatever signals the PLM receives from the powerline So, what you have is: INST-SRX to Group 1 So, it seems that you pressed the button associated with the first IRLinc node. Since you do not have any scene being controlled by this node, no other status changes you see. The last piece is issued by your IRLinc trying to make sure all responders have done what they were supposed to (cleanup). With kind regards, Michel

Hi Allan, Thanks so very much! I have indeed received the calculations and it's currently planned to be supported after we are done with ECM1240. In short, it's in our plans ... Thanks again so very much, With kind regards, Michel

Hi David, Yes, you are very correct: ISY reevaluates conditions only when one or more conditions have changed. Now, we have to figure out why ISY misses the status changes! With kind regards, Michel

Hi David, Ah, yes! How could I have not seen that? So, sending All Unit's off via the REST interface (which calls the program) works fine but the program itself does not (once in a while). So, as you suggested, the problem could either be that ISY does not receive GDO Outlet Vehicle's status or that the X10 signal is not getting to its destination. Would you be kind enough to open the Tools | Diagnostics | Event Viewer on level 3 and make sure you get status feedback from GDO Outlet Vehicle. If so, then would you be kind enough to try and send the off command twice? The difference between Status and Control is this: Status changes with every change in status! This means that when a switch is ON and then you press the ON button again, the status does NOT change. Control is the actual physical activity imposed on the devices. So, if the device is ON, and you press the ON button, your program will receive another ON event. With kind regards, Michel

Hello someguy, I think it's about time to call our tech support so that you wouldn't have to waste more time trying to get the motion sensor to work. With kind regards, Michel

Hi davidn70, Very neat! The first thing I would do is to add 1 (or a little more) wait between the X10 offs. The second thing I would do is to ensure that the lights controlled by these X10 devices are not generating noise when they are on. Perhaps, you can unplug them one at a time and retest the program. With kind regards, Michel

Hi Rich, This is excellent and it should work fine. Please keep us posted. With kind regards, Michel

Hello ergodic, The first thing I would do is to run the Scene Test to see if the status of all the lights in the Garage Scene are tracked properly. If not, then that would certainly explain some of the issues you are seeing. With kind regards, Michel

Hi MSM, Thanks so very much for the update and I am so very delighted to hear that you are happy with the unit. With kind regards, Michel

Hi Mike, I actually like this idea. I would like to add it to our list of requirements (low priority). Thanks so very much. With kind regards, Michel

MSM, This is quite surprising: going to http://www.universal-devices.com/99i searches the network for your ISY. If this URL does not find your ISY, then perhaps the problem is that your ISY has a static IP address which is not in the same subnet as your new router. The only way to change the IP address is to connect your ISY to your computer, use Hyperterminal, and change ISY's IP address to something with in the current router's domain. Here are some instructions: http://www.universal-devices.com/mwiki/ ... IP_Address With kind regards, Michel

Hi cslee, There seems to be communications errors (-2). Would you be kind enough to try and query the devices and see if they respond? Also, you might want to check and see whether or not these issues are time related and, if so, we'll have to try and figure out what's causing the communications errors. With kind regards, Michel

Hi, This is a bug which we are working on. With kind regards, Michel

Hi Peter, Currently ISY does not support RFID unless the RFID device has an INSTEON interface. In lieu of RFID, you could assign a button on a KeypadLinc as your home/away indicator. Then, you create a folder which is enabled if and only if you are away (i.e. the status of the KPL button is off). You can add as many programs as you wish under the folder. This way, those programs will run if and only if you are either away or home. With kind regards, Michel

Hi someguy, This is quite odd. Do you have any other powerline devices in your installation? With kind regards, Michel

Hi Joe, Unfortunately, the main issue is the newer firmware for EZIO devices and our complete lack of understanding of what has changed between versions (that's why your old one works and the new one. As such, unfortunately so, there's probably no easy way of fixing this issue. With kind regards, Michel

Hi guys, I am so very sorry ... you are both correct and I was wrong. I do not know what I was thinking! With kind regards, Michel

Hi thomasolson, If you have an older KPL version, you might want to do a restore on it. This way, the load button is added last. With kind regards, Michel

Hi Rich, Unfortunately ISY cannot shutdown your system unless you have a resident program running on your computer which listens for instructions from a network port (just like WOL). i.e. a program that listens to port 555 and when given your authorization and your command, it shuts down your computer. With kind regards, Michel

Hi someguy, What firmware version are you running? Also, adding an AccessPoint right on top of the PLM helped before. All and all, this problem is due to RF cross interference from an Ethernet device to powerline. With kind regards, Michel

Rich, Notifications only send you the name of the program. Also, most ISPs consider emails of the same nature repeated every 2 minutes as spam and will throw it out. Now, as far as your programs: 1. On the first one, you do not need the "and not switched off" 2. This does not work with double press 3. Please ensure that you have a high timeout value on the SMTP settings. Usually 2500 would do fine And, finally, it's always good to look at the logs to see if you have any 5000x errors. If you do, then there are communications problems between ISY and your mail server. With kind regards, Michel

Hi Rich, Two conditions have to be met for ISY to be able to accomplish this feat: 1. The frame must be web enabled preferably with a static IP address 2. It must provide you with the APIs to communicate with it As long as those conditions are met (and as long as you have the Network Module), then you can ask the frame to do whatever their APIs allow you to do. The one exception to all this is that ISY cannot stream audio/video to your frame. With kind regards, Michel

Hi mikestreb, You have two options: 1. Removing all the floor plan objects 2. Telnet into your ISY, login, and then issue: RF /CONF/UDFLPL.XML With kind regards, Michel

Hi Rich, I think the following with clear everything up: 1. Repeat must be the last (or the only) block in the Action (Then) section 2. Everything that needs to be repeated must be listed below the Repeat line As such, you cannot do example 2. For example 1, simply make sure your actions are listed below the Repeat line. With kind regards, Michel