oberkc

Building upon LeeGs suggestion, how about: If Status 'TriggerLinc1-Opened' is On Then Wait 15 minutes Send Notification to 'ALL' content 'Custom with date' Run Program 'XXXX' (If) Else - No Actions - (To add one, press 'Action') Program XXX (must be disabled) Program YYY if Then Repeat 5 times Set 'ICON Dimmer 1' Fast Off Wait 1 second Set 'ICON Dimmer 1' Fast On Wait 1 second Else Repeat 5 times Set 'ICON Dimmer 1' Fast On Wait 1 second Set 'ICON Dimmer 1' Fast Off Wait 1 second

I am sorry, but I do not understand what you want to do.

Well...I can speak only of generalities at this point (away from home). This setup is for those who want to use a single KPL button to control a garage door, and simultaneously display its status. First is sensor position. It is arguably important to understand that the sensor has two states: on and off. If the sensor is physically located such that the magnet and sensor are adjacent to each other when the garage door is closed, then this state means "fully closed" and the other state means "not fully closed". In my mind, from a security standpoint, "not fully closed" is the same as "open". It is for this reason that I consider this the superior location for the sensor, rather than the alternative to mount is where the magnet and sensor are adjacent when the door is fully (or any other state of) opened. Second, I wanted my KPL button to be "off" when closed, and "on" when open (any degree). This means that the sensor must be wired so that its state is off when closed and on when open. I recall the instructions that came with the kit were less than clear on how to do this, but it had to do with using the correct two wires from the sensor, I think. I believe this also equates to the IOLinc LED being on when open and off when closed. Third, you must configure your KPL button to be non-toggle on. Since I was most concerned with being confident that the door was fully closed, indicated by KPL button being off, I did not want the ability to turn the KPL button off by manual presses. I wanted only one way to turn the KPL button off: by a command from the sensor. Fourth, you must configure the relay portion to respond to "on" commands only. Since the KPL is in non-toggle "on" mode, it would send only "on" commands. I wanted the relay (and connected opener) to respond to all KPL button presses, the same as the mechanical button in the garage. I don't recall the setting, but I think it was "momentary B", but you should look it up to be sure. The mode where relay response based on sensor position (momentary C?) won't work here. Lastly, create two scenes. One with sensor (controller) and KPL (responder). The second with KPL (controller) and relay (responder). I believe ALL these steps must be taken because how all this works together. I don't think you can pick and choose the options that you like without understanding how it all plays together. There are a lot of details. Hopefully, I was clear and did not forget any.

For this reason, it is important that the KPL button be configured in "non-toggle on" (of course, the relay has to be configured to respond to "on" commands). This way, the only way for the KPL light to be off is from a sensor command. Being configured in this way gives one a high confidence that KPL off means garage door closed. I am one of those that LeeG mentioned as a fan of the wiki approach.

My experience is that the ISY status remains pretty faithful to truth. To verify, the only way that I know is to run a query, as you have done. Unfortunately, the problems that cause it to be out of sync can also affect query results. There are, however, a few times that I have experienced problems. One is when experiencing communication problems. The other, if I recall, was associated with firewall and java issues (I don't recall specifically which). I have been swapping out browsers between chrome and explorer (currently using the latter) but each swap appeared to cause temporary issues with the admin panel status not keeping sync. Unfortunately, my methods with firewall and jave issues is trial-and-error rather than skill.

If, however, ons has easy access to the device, I find it quite viable (even preferable) to use the "start linking" button on the ISY admin panel and simply putting the insteon device into linking mode as responder. The ISY will populate address and device type quite well, thank you very much. You may still wish to change name to something meaningful. Of course, I enjoy moving around a bit, would rather walk than type, and am in no hurry.

I don't believe so, just as long as you pay attention to the priority between "and" and "or", putting parentheses in the appropriate places. Yup. You have some interesting conditions. I do, without observed problems. Apparently, my experience is different than bmercier, however. Possibly, but the use of scene tests, event viewers, and program status can often help figure things out. It is not always easy and sometimes frustrating. It sounds as if you have a lot more requirements in you head than I have attempted to address in the suggested programs. I apologize, but I also continue to be unclear about what your progam is, or is not, doing that is should not, or should, do to be able to offer more concrete suggestions.

I stand corrected. Brain dead. So you have a variable to indicate one, or both, doors are opened. That should work. You may need to create a second variable (I will call it IGarageLight) to track how your garage lights are last turned off and create a program to track. The logic would be something like: if ( control garage light is set off or control garage light is set fast off ) and status garage light is not on then Set IGarageLight = 1 <<< indicating light was last turned off manually else set IGarageLight = 0 <<< indicating light is either on or turned off other than manually Your main program would then look something like: if Status Program = "true" <<<IGarageLight = 0 <<< not last turned off manually then Set garage light on This is all theoretical an untested, but I hope it gives you enough ideas to move forward.

I believe your level of complexity just went one step higher. I don't have exact syntax memorized, so I will offer a conceptual suggestion, hoping that it will give you enough clues or ideas that you can fill in the blanks. Create an integer variable, call it IGarage. Modify the first program as follows: If Status Garage Door Sensor is On then wait 5 minutes set IGarage = 1 <<< a condition indicating that the door was open for at least five minutes Then notify me (garage is open) else run new program (if path) Create a new program, if IGarage = 1 then send notify me (garage is closed) set IGarage = 0 <<else set IGarage = 0 One could actually accomplish this logic without variables if that has value to you, but I see no reason not to take advantage of them given that they exist.

This is not a trivial set of criteria. So the plain-english condition would be something like: if either of my two garage doors are opened and garage light is off and garage light was not turned off manually then turn the garage light off I cannot help but suspect I am misunderstanding something.

It is good that you replaced your defective, and potentially defective, devices. quick confirmation of what I hope is understood: a. do you have access points or other dual-band devices to provide insteon communication between legs of your electrical system? b. have you plugged your PLM in, or on the same circuit as a UPS or surge suppressor? Do you have any of these devices? c. have you plugged your PLM into an outlet with lots of other computer stuff? d. do you have any X-10 devices?

This may actually be quite simple, given the way programs are triggered and how wait (and repeat) statements work with the ISY. How about: If Status Garage Door Sensor is On <<then wait 5 minutes Then notify me else The beauty of this is that if the status changes during the 5 minute wait period, the program execution will be halted and re-run, based on the newest evaluation and status.

I suspect the reason that LeeG did not address this concern is that it appeared you had already figured that part out when you said: That is certainly how I interpreted this post. Regardless, and ironically, there is a current thread on the same topic: http://forum.universal-devices.com/viewtopic.php?f=27&t=7552

Based on your description, I expect your program to work and can either conclude that I don't understand your program correctly, or that there is something else going on unrelated to program logic. I have a program much like LeeGs and yours. I have a secondary keypad button, set to non-toggle off. Because one cannot directly control secondary keypad buttons from a program, I created a scene, with only the secondary keypad in it. I then created a program such as: if status "light 1" is not off <<or status "light 2" is not off or status "light 3" is on <<then set "scene with secondary KPL button" on else set "scene with secondary KPL button " off It works great for me.

In other words, you want the program to evaluate as false ("don't want to run true") if you switch the garage light off? Status 'Main Floor / Garage Light' is not On This particular condition will be TRUE if you switch the garage light off. (This is not a dimmer, is it? Only two conditions: on and off?) This sounds to me exaclty the opposite of what you want. If you want a condition that will be false when you switch the garage light off, try: Status 'Main Floor / Garage Light' is not off I apologize, but besides "I don't want to run true if I switch the garage light off , I don't see where you describe what it is that you want your program to do.

Nice! I am glad you found the better solution. Have you not checked out the mobilinc threads, under third-pary apps?

Yes, and of scenes and room folders . the ISY-99 and the "my lighting" tree are not, in my estimation, intended as user interfaces for the purpose of turning on lights and activating scenes. As such, the idea of accidently hitting "all the lights" is near non-existent. Use the ISY to create scenes and programs. Scene controllers should be insteon switches or keypads or android apps or iphone apps or.... Unfortunately, I don't use mobilinc so I cannot help with how to set this up to make user friendly. I cannot help but strongly suspect there are better options than renaming the lighting tree.

Sorry, but I missed any mention of prior experience with smartlinc. I have not memorized part numbers and your mention of "2412" just went right over my head. My earlier suggestions were based upon having failed to catch that little tidbit. Generally, I agree with the logic that if a PLM location worked for smartlinc, it should work for ISY. I vaguely recall posted suspicions that the new, dual-band, PLM may not communicate as well as the older versions. I suspect that smarthome would not admit to this being the case, if true (and it may not be). Glad it is all working now. Sometimes computers simply need rebooted.

I don't believe it matters. You have two legs, whether main panel or sub. Perform the test in the instructions that confirm the devices are on opposite legs, and you will be fine.

For most systems, you need at least two dual-band devices, one on each leg of your electrical system. If you are sure that all of your insteon devices are on the same leg, then you may be able to forgo this, but if not, then best be safe. Your impressions are correct. Yes. Do you not have two dual-band devices? Yes, your dual-band PLM is one. You need two, on opposite legs, to provide a communication path between legs of your electrical system. If you don't have two properly installed dual-band devices, my suggestion is to purchase a single access point and install it in an outlet on the opposite leg of your PLM. Given this news about your possible lack of enough dual-band devices, the extension cord test may be inconclusive. If you had two dual band devices, the extension cord test would have confirmed the suspected communication problems on your computer circuit. A filter for your computer equipment would be the remedy. Filters are not terribly expensive. Perhaps it would be good insurance simply to purchase one regardless.

Try out LeeGs extension cord test first, to confirm this is the problem. Be sure to plug it into an outlet on a different circuit than your computer. It probably does not hurt to ask whether you have the two legs of your electrical system coupled with any dual-band insteon devices or access points or signalincs? It could simply be that your PLM is on a different leg of your electrical system than is your PLM.

With regards to your 'cloudy days B' program, it will trigger an evaluation at: sunrise + 1 hour, sunset - 1 hour 15 minute, and ANY change in status of the motion sensor. If this program triggers an evaluation which results of "true", then it will run the "then" path. But you know all this. Additionally, if the program is re-triggered during the 25 minute wait (by a change in motion sensor status, for example), the execution will halt and restart the "then" or "else" path, based upon the results of the new evaluation. In other words, if the 25 minute period was counting down, and the motion sensor status changed to "on" during the wait period, current execution would halt and the "else' path would execute. Nothing further would happen (empty else path). Therefore, I don't believe you need a separate check of the motion sensor status. I do notice a couple of things hower. First, I find it unusual that you would limit the response of lights to daylight hours (from sunrise to sunset). Normally, lights are more needed during nightime hours (sunset to sunrise (next day)). Second, your "B" program will fail you if the lights are on and it is triggered less than 25 minutes before 'sunset-1h15m'. If this were to ever happen your lights would remain on all night. There are several ways to avoid this. The simplest, in your case, may be to add a third program to turn the lights off at Sunset - 1 hour and 15 minutes, as a backup.

The difference between the two situations is communication with the PLM. Where is it plugged in? In a surge suppressor or UPS? Next to one or both? Along with lots of other computer stuff? For the ISY to be at its most effective, you need to create links using the ISY. If you are having problems with this, my suggestion is to identify and solve that problem.

LeeG, Are there any (older) versions of dimmers that require a power cylce to accept new scene setting such as this?

Scene settings can be different based on the controller that initiates an action. In the "my lighting" tree, when you select a "scene" and view the settings for each of the responder devices, you will see the response based on the ISY/PLM being the controller. In this case, I expect to find the family romm ceiling set at 58%. Under the scene, if you now select button G, I suspect you will see a different set of responses, to be achieve when the scene is controlled by button G (as opposed to controlled by the ISY/PLM). I expect to find a 30% setting for your ceiling lights. Change this to 58% if this is the response you want when pressing button G. This is because moblinc is activating the scene based on the ISY/PLM being the controller.