MikeD

There is only one example I have seen posted by wwat that may work: viewtopic.php?f=27&t=10348 His example is about 14 posts down on page1 with program examples and a screen shot of his 'Bathroom Scene changes' folder. I have used this method to set an integer variable from 1 to 10 to store a device's status then later using it to restore the light level of that device. It is a work around but does the job. ~Mike

I believe you do not want this setting, my IOLinc is set to Momentary A. The Sensor input of the IOLinc is used as a Controller in a Scene to turn a KeypadLinc Button On, or whatever is in the Scene. The Relay output of the IOLinc is used as a Responder in a Scene to control your Garage Door. So you need two separate Scenes to make everything work. Garage_Door_Relay_Scene <-Garage Door-Relay KeypadLinc_Button_A Garage_Door_Sensor_Scene ->Garage_Door-Sensor KeypadLinc_Button_A The KeypadLinc Button you use should be set to Non-Toggle mode. Non-Toggle [On] should work for you just fine. ~Mike

NHWA: I see your review at Smarthome, it is still there. ~Mike

Ah, yes... I know it will come in handy some day. Thanks ~Mike

I didn’t find anything useful when I searched the forum, my search returned too many finds and I probably did not go back far enough. Oddly when I searched using Google I think I found the answer to my question. http://www.forum.universal-devices.com/ ... 63&start=0 Just didn't look hard enough I guess! I did have the Event Viewer in Level 3 and never turned it off. I had mistakenly thought that if you closed the window it became inactive. ~Mike

Hi all, I am unsure why my error log is filling with this information. I believe this started yesterday when I upgraded to 3.3.8 from 3.2.6. This is only a small portion of what is there. Thu 2013/01/10 04:30:28 PM System -170001 [HTTP] 192.168.1.250:53556->1040 Thu 2013/01/10 04:30:28 PM System -170001 [HTTP] 192.168.1.177:53910->1040 Thu 2013/01/10 04:33:00 PM System -170001 [HTTP] 192.168.1.177:53913->1040 Thu 2013/01/10 04:39:25 PM System -170001 [HTTP] 192.168.1.250:53695->1040 Thu 2013/01/10 04:39:25 PM System -170001 [HTTP] 192.168.1.250:53698->1040 Thu 2013/01/10 04:39:25 PM System -170001 [HTTP] 192.168.1.250:53699->1040 Thu 2013/01/10 04:59:28 PM System -170001 [HTTP] 192.168.1.250:53945->1040 Thu 2013/01/10 04:59:28 PM System -170001 0: GET-->/desc Thu 2013/01/10 05:16:03 PM System -170001 [HTTP] 192.168.1.250:54265->1040 Thu 2013/01/10 05:16:03 PM System -170001 0: GET-->/desc Thu 2013/01/10 05:17:34 PM System -170001 [HTTP] 192.168.1.250:54318->1040 Thu 2013/01/10 05:19:05 PM System -170001 [HTTP] 192.168.1.250:54339->1040 Thu 2013/01/10 05:19:05 PM System -170001 0: GET-->/desc Thu 2013/01/10 05:51:24 PM System -170001 [HTTP] 192.168.1.250:55165->1040 Thu 2013/01/10 05:51:24 PM System -170001 [HTTP] 192.168.1.250:55168->1040 Thu 2013/01/10 05:51:32 PM System -170001 [HTTP] 192.168.1.250:55174->1040 Not familiar with what the -170001 [HTTP] means and why these entries are happening. Otherwise everything is working fine. The two IP addresses are my main PC and an iPad the MobiLinc is running on. I just happend to look at the error log. Thanks ~Mike

+1 Ordered my ISY last month, installed it and replaced all my X-10 devices in the past few weeks. Having a great time configuring all the scenes and creating programs. All done by researching user collaboration here on the forum. It is cool to be an ISY user. ~Mike

Hi all, Installed my ISY about a month ago and learning much by reading posts on this forum - thank you for helping us newbies. I too was fuzzy on how the ISY handles conditions and finding this conversation very enlightening. However one thing that has helped me understand how programmed conditions are handled is to watch the Programs-Summary tab as I use a SwitchLinc next to my PC to trigger an event. The explanations given by apostolakisl in this thread become very clear when I setup a program using 'Control' vs. 'Status' and watch the program run in real time. The program response when using the 'Control' command was not what I expected. But now I understand after watching when the program runs and when it does not. This by no means clears everything up but it does help! ~Mike

oberkc: Yes you are right! thanks for correcting me, I'm still learning... ~Mike

Did not purchase the kit, just the I/O Linc and a normally-closed magnetic switch. However I wanted the sensor status to show Off not On when the garage door was closed! So I ordered a normally-open magnetic switch which works the way I wanted. Sensor-On=Door open Sensor-Off=Door closed ~Mike

No, only the I/O Linc. You have to purchase a magnetic switch separately. ~Mike

From what I understand the program will only run if the status of 'Kitchen_oh' is changed to On. http://wiki.universal-devices.com/index ... m_Commands From the wiki: ~Mike

arw01: I answered my own question above, it worked! I didn't put a wait in there, just immediately turned the scene back on. The kpl buttons flashed twice then remained on until the sensor lined up when the door fully closed. Thank you, ~Mike

oberkc: I'm the opposite, I was afraid to have a false indication that the door was open! First and foremost I really only wanted the I/O Linc sensor input to turn the button lights on when the garage door started to open and then turn the button lights off when the garage door is fully closed. Having the buttons also act as the controller for the I/O Linc relay muddied the water a bit. Thanks for your input! ~Mike

Thank you for the suggestion. There already is a scene with the kpl buttons in it, along with the I/O Linc sensor. When I prevent the garage door from closing after hitting one of the kpl buttons, the status of the devices within the scene are I/O Linc sensor=on, and all 3 kpl's=off. Could I just turn that scene on? I'm new to the ISY world so appreciate pointing me in the right direction. ~Mike

I just installed my ISY system and Insteon devices over the past few weeks. Last weekend I added an I/O Linc in my garage and linked it to three KeypadLinks around the house. My configuration is very similar to the wiki and what oberkc described except for the following: 1. Door closed = LED sensor off (on I/O Linc) - Used a Normally Open magnetic contact switch (contact closes when magnet is removed) - Connected switch to GND & Sense terminals of I/O Linc 2. Configured KeypadLinc Button as non-toggle off 3. Trigger Reverse is not checked * v3.2.6 I did not get the dialog box containing the 'Trigger Lock' option 4. Connected Common & N/O terminals of I/O Linc to my garage door opener. I had two teminals on the main unit that said "relay" and they worked perfectly. Everything seems to be working fine. When someone opens the garage door the button lights on each KeypadLinc and the pressing the KeypadLinc button will close the garage door and all corresponding buttons turn off. Only thing is they turn off immediately, not when the garage door fully closes. I just have to figure out how to update the KeypadLinc buttons if the door fails to close. ~Mike