oberkc

Program looks fine. I expect it to work when you get your communication problems solved. In addition to those things said by larryllix - make sure you PLM is not on an outlet or circuit with lots of other electronic gadgets. - make sure you have confirmed communication between the legs of your electrical circuit. There is a test in the user manuals for most of your dual-band devices that include this test.

I cannot help but fear that this is a hardware failure.

"Best" is subjective. On this one, I would be afraid that motion would trigger during the 15min wait, causing the program to re-evaluate and run false, leaving the lights on indefinitely. Alternatively, if sunrise occurs during wait period, program will halt and leave lights on. Is your objective to have the motion lights turn off after 15minutes, even if subsequent motion is detected? "Control ...on" will only trigger a program upon receipt of ON signals from the motion sensor. OFF signals will NOT trigger the program. It will be TRUE only at that point in time when so triggered. At all other times that condition will be false. "Status...on" will trigger programs only upon a CHANGE of status. Repeated ON signals will NOT trigger the program. It will be TRUE so long as status remains ON. Any time a program is triggered (during a wait or repeat) the program will be interrupted. The only question is whether the program evaluates TRUE (runs THEN) or FALSE (runs ELSE). Having the variable does not halt the interruptions. Rather, having the variable changes the evaluated state (true/false) once interrupted. As for me, I would actually prefer that a new motion sense would reset the timer back to 15min. My recommendation is to state your requirements, in detail. Write them down. What do you want to happen when a motion sensor is triggered? What do you want to happen at sunrise (anything? Turn off the light?)? What do you want to happen if motion is sensed and the light is already on (reset the timer? nothing?) What do you want to happen when one sensor triggers and a second sensor triggers during the wait period? After the wait period?

Brian H, it sounded to me as if they have already tapped into the wall button with another gadget. This same approach would work with the IOLinc, don't you think?

The insteon garage door kit, including the IOLinc, can be configured to send a "momentary" ON signal, very much like a doorbell button.

It would help if you actually post the program. Are you on v4.X of the ISY software, or have you moved to v5.x? One possibility is that your conditions checking on lights being ON are "control on" (rather than "status on") conditions. Is this the case? If so, your program would not ever run the ELSE path.

Given what you describe, I think I would be happy to assume that I am leaving the cabin at approximately the same time each visit and turning off D button at the same time on the 10th day. Whether that is in the morning or evening or whatever, a simple approach would work. Given that you already have some programs working, I will also assume you have an understanding of programming with the ISY and are seeking an approach, rather than the exact steps and syntax for the specific programs. I would take the approach as I originally suggested. First, create a variable (probably would use a state variable here) that is to be used to count days since pressing the button. For these purposes, I will call it "daycount". Second, I would create a program which would increase the daycount variable by 1 each day. Third, I would create a program that would watch for status of D button. If D was ON, I would then enable the program created in the second step. If OFF, disable that program and reset the variable to zero. Finally, I would create a program which would, at a fixed time each day, check the variable value and, if = or greater than 10, turn off D button.

A simple method would simply be to initiate a pogram which increments a variable by one each day. When the variable reaches ten, do something. Whether or not this meets yo needs could depend on what you mean bt “10 days”. If you mean exactly 240 hours from the time you press the button, it might take a little more effort. If you simply mean to do something at a fixed time on the tenth day, this simple method might work.

To satisfy my own curiosity...you state that the ISY recognizes the device as a 5-button dimmer. How many buttons were added to the device tree, 5 (main, A, B, C, D) or 8 (A-H)? One factor that may come into play here is that these keypads can be converted from 5-button to 8-button (or reverse). The keypad sure sounds like it thinks it is in an 8-button configuration. I wonder what would happen if you converted it to a 5-button configuration following the instructions from the manual.

I know that I have converted 6-button versions to 8, and used the instructions that came with the keypad. I don't recall that this can be done via ISY. Also, if needed to perform a factory reset, this will bring the unit back to the original button configuration (6 or 8). According to the latest manuals, this conversion capability is still in place. But, yes, it seems that the 2334-222 is the current version of your old 2486D. Why would you be looking for other "options"?

Even if you don't have a spare device, create a scene (as a test) and put the relay in it. From there, send scene ON and OFF commands and observe how the different modes react. I think you will find that the device DOES work as expected from a scene perspective.

No, I do not think you are confused about momentary-A. (Either that, or we are both confused.) My understanding of momentary-A mode is that either (both) ON and OFF commands will trigger the relay to close momentarily. The only thought that I have is that this may work differently when the relay is part of a scene with another insteon device (keypad button, for example) as controller. Is there a chance you have a spare device laying around to test this theory?

Your action first sets the main door open, then waits. Unfortunately, this will retrigger your program and halt further execution of the action, which will now be false and run ELSE. The trick here is to use two programs. One option would be something like: If $Retirement_Garage_Door >= 50 And 'MyQ / Main Door' Door State is Closed Then run next program (then path)Else - No Actions - (To add one, press 'Action') next program: If nothing Then Set 'MyQ / Main Door' Open Wait 1 minute $Retirement_Garage_Door = 0 Else - No Actions - (To add one, press 'Action')

I do not recall a "resume" type of command. While I imagine creative programming techniques could achieve your goal, I am not sure that there is a canned command for this. Without thinking too much about this, I wonder if you could insert a condition in your programs which would trigger them at the conclusion of your 15-minute wait period. What I imagine might be even harder would be to resume prior status, regardless of whether the result of a program, or manual control.

OK. Try mouse-click on the lts low (IRLinc Reciever) within the scene definition. Check to be sure the ramp rates and ON levels match those shown in your snip. (Most likely they do not.) Remember, responder levels can be different for each controller.

I had the same experience as Asbril (though I do not know from where he was talking on the phone). He went well above the call of duty.

I am not in a position to confirm, but current month is one of the system variables, I thought. In fact, I think I use it in one of my programs.

I believe it was available in 4.x, but who wants to update this condition every year if there is a convenient way to avoid doing so.

I have played around now with both echo and google devices. I am underwhelmed by both. My particular hub has a bad habit of reverting back to “set up with google home” messages on the screen, but I think it is related to a particular location in the house (in proximity to ipads and other bluetooth devices). One thing I prefer with the hub is direct control over a roku device. I also find it a little better at recognizing vocal commands than an echo. I like the display of the home hub, also, but find it expensive for the value it offers. I dont like voice control in a bedroom, so I find the hub to be not useful for the obvious location. I dont like thatthere is very limited touch control for some very basic functions (like setting or disabling an alarm). On the echo, I like the “drop in” function as an intercomm. I really dont like that neither can be configured for specific hubs/echos to control specific, but different, harmony remotes. I find both to be roughly equal at controlling my lighting and other devices.

Sure. One first has to create a program which assigns the value of the month system variable to a variable created by you. You would then use that variable as a condition in the program to turn on the pool light.

So...you have three PLMs total.. a plm hooked to the ISY and then one on each end of your rj45 cable?

I don't know how important it is to use the node server, but hue lights can be controlled via network resource also, assuming you have the network module added to your ISY. This approach would, I expect, allow one to cycle through different hue light settings (Color, brightness, etc...) in the way you desire. But, I see you figured this out so...never mind.

Absolutely! If your devices are keypad buttons, this is exactly the way I would do it. The only question is whether you want the button in a perpetual state of ON or OFF. That sure sounds like his suggestion...to avoid consolidation. While I have not tried this program, I must admit that it would surprise me a bit if his concern turned out to be realized. Theoretically, I guess the consolidated program could cause an infinite loop, constantly changing the variable value and retriggering itself, changing the value again, retriggering again...etc.... I was just not sure that theory holds out here, whether by design or just the nature of computer latency. My nature is also to use a single program but, perhaps, it is safest to keep them separate in retrospect.

You may want some parentheses. Furthermore, it might be possible (or even beneficial) to combine your two variable programs (programs 1 and 2): If $KitRopeFav is 4 And ( 'Kitchen Lights / KPL Kitchen - Breakfast / KPL Kitchen - Unused F' is switched On Or 'Kitchen Lights / KPL Kitchen - Breakfast / KPL Kitchen - Unused F' is switched Off ) Then $KitRopeFav = 1 Else $KitRopeFav += 1 As your programs were, both would have triggered and run TRUE if you tapped the OFF side of your switch. Have you checked the value of your variable lately? Might it be higher than 4? Do programs 3 and 4 run properly if you select, right-click, run then?

Or "restore" links. Of course, the motion sensor must be awake in order for this to work. Is this the only motion sensor you have? (Do the others work?) ISY sees comms between all other devices just fine? Can we assume that the PLM is a dual-band version? Can we assume that the PLM is not plugged into a UPS or into a circuit that contains lots of electronic gadgets including UPS, computers, routers, power supplies, etc....?