Michel Kohanim

Thom, Thank you for posting your issues in our forum and I do hope they will benefit everyone. My assumptions (which may be wrong) that you have a program turning these devices on/off is based on the following: ISY updates the status of devices on the Admin Console if and only if: 1. You physically turned on/off a device, PLM sensed it --> ISY sensed it, updated the status, checked to see whether or not this is a controller for a scene, and predicted the status of all the devices in that scene 2. You turned on/off a device through ISY (either web or program), in which case, ISY waits for response back from the device and if one received, updates the status of that device ONLY. If not, you get device comm errors. 3. You turned on/off a scene (including All on/All off) through ISY (either web or program), in which case ISY waits for a confirmation from the PLM (that it has send out the command) and then predicts the status of the devices in that scene Unless there's a bug that we cannot reproduce here (but will continue trying), it seems that somehow ISY believes that the status of those devices have changed and, as I mentioned before, there are only 3 cases which this takes place. With kind regards, Michel

Mike, Thank you so very much for helping us test the unit and all the bugs you found have truly made a major difference. Furthermore, thanks so very much for composing the Quick IR tutorial: http://www.universal-devices.com/mwiki/ ... R_Tutorial . With kind regards, Michel

jgraziano, Yes, creating a scene in ISY would indeed give you the correct status. Furthermore, creating a scene in ISY is not less efficient simply because 1. The devices are linked as if you were linking them manually 2. You would know the approximate (to within +/- 5% accuracy) status of all your devices regardless of how they were turned on/off 3. You have immediate access to what controls what and what is controlled by what devices/scenes in both the Topology as well as the tree to your right With kind regards, Michel Definitely make sure you create your links on the ISY. If you link 2 devices together, but not to the PLM, they will only inform themselves of any status changes. The PLM will not know you've turned them on or off unless the devices are also linked to the PLM. Creating links within the ISY ensures that the proper links are created between both the switches AND the PLM. I've only been using scenes in the ISY for actual scenes the ISY is to control. If I want to control one lamp with one button on the CL, I've been doing it manually. In that kind of scenario, should I create a scene with one lamp and one button? Seems kind of inefficient to me, but if it does indeed give me status correctly, I guess it's worth it.

Hello jgraziano, You might want to add a delay between your X10 and INSTEON setting scenes. Now, my main question is: 1. If you turn scenes "SC-Pre Sunset Lightup" and 'SC-Master Bedroom Lamps On' from ISY, does ISY get updated with the right status? 2. If you have any controllers in these scenes, and if you physically turn on/off your controllers, does ISY get updated with the right status? With kind regards, Michel

Hi Glenn, Yes and I already replied. With kind regards, Michel

jgraziano, Would you be kind enough to do the following and let me know the results: 1. Turn on/off your Sunset scene through ISY (click on the scene) 2. Check and see whether or not the status of the devices are updated correctly Please do let me know. With kind regards, Michel

wjoel, Apologies for a tardy reply. You might need to break this into two programs since it seems that Foyer_S changes the status of Foyer. With kind regards, Michel

Glenn, All changes are updated at runtime and immediately. Have you upgraded to 2.6? With kind regards,

Hello gmurch, May I humbly suggest the peruse of the User Guide? You have a link to both the PDF version as well as the on line version under the Help menu. Here's the on line version: http://www.universal-devices.com/mwiki/ ... User_Guide . Please find my comments below. With kind regards, Michel Please make sure you understand the difference between the "scene" on level/ramp rate vs. the local on level and ramp rate: http://www.universal-devices.com/mwiki/ ... teon:Scene Please checkout our How To section http://forum.universal-devices.com/viewforum.php?f=9 . The first topic is exactly what you are looking for. In release 2.7 ... very soon! http://www.universal-devices.com/mwiki/ ... figuration

Hi kcrossley, Put the device and the KPL button into the same scene and make device responder (or controller) and make sure the KPL button is a controller. With kind regards, Michel

DEGoodrich, What are you experiencing? The same exact issues as before? No changes whatsoever? With kind regards, Michel

Hello jgraziano, Except for Jave (JRE) we do NOT have any other programs running on your computer. As such, I did a search on the internet and, sure enough, this is a virus! Please eradicate it as soon as possible (http://www.virus-malware.com/antivirus/remadm+pskill/). With kind regards,

Hi Wayne, Here's what you do: 1. Create a scene and name it whatever you like 2. Put all KPL button Cs and your SL1 in that scene and make them all Controllers This way, all your buttons Cs not only will control each other but also control SL1. Furthermore, your SL1 will control all your button Cs on all your KPLs. Please note that you can select more than one device at a time by pressing/holding the Ctrl button on your keyboard while selecting (mouse click) on the devices you want to add to a scene; then Right Mouse Click and choose "Add to Scene ..." menu option. When you get a the Add Confirmation dialog - and for your scenario above - make sure you choose controller for all the devices you've selected. For more information, here's a great start: http://forum.universal-devices.com/viewtopic.php?t=14 With kind regards, Michel

Wayne, Thanks so very much for the update. I updated my previous post to reflect the pinout as you found. With kind regards, Michel No apologies are neccessary! I was able to make the cable but I did have to reverse the TX and RCV to make it work. I am able to log in and I have updated to the latest release. I have also manually added a couple of KPL's and the devices they are linked to. I must say ISY is pretty cool. Now I'll begin learning how to do all the great functions it's capable of. I would like to once again point out to everyone that the tech support from UD is unsurpassed. You guys have earned a lifetime customer. Thanks for all the help so far, Wayne

Hello All, If you have a UPnP router, on Admin Console please try File->Enable Internet Access the outcome of which should be the URL at which you can access ISY remotely. If you do not have a UPnP router, or if File->Enable Internet Access returns "null" or fails, then: 1. On Admin Console go to Help->About 2. Write down IP Address and Port number for your ISY listed in front of My URL. So, for instance, if you have: My URL: http://192.168.1.105:54321/0/p then Your IP is 192.168.1.105 and Your your Port is 54321 If you do not see any ports, then you would want to forward to port 443 (for HTTPS) unless it has been changed using CWP 3. Follow the information in http://portforward.com/ to configure your specific router for port forwarding 4. Your remote access URL will be in the form: http://your.isps.address:your.isys.port/0/x Please note: 1. Each ISY has its own unique Port number 2. If your ISY is on a DHCP (default behavior for most routers) then ISY's IP address may change. As such, if you plan to use remote access: a. Use static IP for ISY, or b. On your router, make ISY's IP lease permanent, or c. Use dynamic DNS services such as dyndns.com or tzo.com With kind regards,

Hi Just Another Joe, I am so very sorry ... you are 100% correct: you were not in any of our lists! Please do accept my sincere apologies. With kind regards, Michel Hi Rand. While I agree with the remainder of your post, I didn't get the Thank You note you mentioned. I'm feeling so left out! Am I the only one?

Rand, Thank you so very much for your kind words. Again, none of this would've been possible without the help, support, and feedback. Merry Christmas, Happy New Year, and Happy Holiday! Thank you so very much, With kind regards, Michel

Hi Wayne, Apologies for a tardy reply! 1. Yes, please do not connect the 12v to anything on the serial side 2. If you do not get anything except the "Keep This Window Open", then please do be kind enough to make sure you have Java 1.6_03 installed. 3. You should be able to login to ISY even without the PLM plugged in Please do let me know of the status. With kind regards, Michel

Wayne, This is so ... Here you go: On the RJ45 side: Pin 1 = RX (Receive from PLM) Pin 2 = 12V DC Pin 7 = GND Pin 8 = TX (Transmit to PLM) On the RS232 Side Pin 2 - RX (from PLM) Pin 3 - TX (to PLM) Pin 5 - Ground So, what you should have is RJ45RS232 1 3 8 2 7 5 Here's the link to serial cable pinouts: http://www.zytrax.com/tech/layer_1/cabl ... _rs232.htm MAKE SURE YOU LOOK AT THE FEMALE DB9 PINOUT. If this doesn't work, simply swap pins 2 and 3 are retry. With kind regards, Michel

Rand, You are 100% correct (no surprise there). MikeB, Here's the problem: Secondary buttons do not have on levels/ramp rates associated with them and therefore the only things you can do with them are on/off. Therefore, if you have any other controller that controls the lights associated with that button, all you could expect is to have it follow your controller. UNLESS - and as you have done previously - make your controller non-toggle or have two scenes as Rand suggested. With kind regards, Michel

Hi Glenn, Not yet but very very soon! With kind regards, Michel

Hello jgraziano, Yes, you are 100% correct in your assumption. Here's the code If Time is 3:00:00AM Then Set Scene 'My Lighting' Query Else - No Actions - (To add one, press 'Action') With kind regards, Michel

jgraziano, In your list of programs do you see any programs which query My Lighting at 3:00 A.M.? With kind regards, Michel

jgraziano, For migrated units, it's not called 'QueryAll'; it's simply called Program 'n' under My Old Schedules. It simply does a Query on My Lighting at 3:00 AM. With kind regards, Michel

All, Thanks so very much for all your help and support. As both Rand and Mike suggested, this was a bug which was fixed a long time ago and, as such, I am wondering: jdva, what version of ISY are you running? With kind regards, Michel