oberkc

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....?

I recall a thread about the use of 2 ISY devices, communicating with each other via network module. Unfortunately, I cannot find it. Perhaps another can remember it. That seems to me to be the most promising option.

If this fails to work, I would be looking at issues other than programmatic. And, as I said, it depends on your goals. If you want only to trigger when the switch is manually activated, use control conditions. If you want to trigger when the switch is turned on in any way (manually, program, scene) then use the scene condition as suggested by paulbates.

I recall a recent post with similar intentions. Rather than hang the outdoor module from the pole, why not get a short extension cord and plug the module into that. The extension cord would only have to be long enough so that the outdoor module could be sitting on the ground. I have several insteon devices in unconditioned space (no direct exposure to rain or snow). They seem to hold up for me.

Using status may be the easiest approach, but would depend on your goals. If you desire only to track and react to the switch being manually turned on (as opposed to being turned on as a scene responder, for example), another approach could be: if control 'bonus' is switched on and control 'bonus" is not switched off then ….unchanged....

I use, also, a couple of z-wave sensors. I have not noticed one being better than the other as far as battery life. I, too, get much more than a couple of months with both insteon and z-wave sensors. Maybe a year...maybe more.

In the case of ISY-994, a controller is, by default, also a responder.

I don't believe anything has changed due to the major overhaul. I think the advice can still be good, but would depend on conditions. If your conditions can often get triggered, but often false, or if your action can re-trigger the program, it might be good to separate the condition from the action. Such a separate can prevent the triggers from interrupting wait statement and repeats. An example: if time is sunset and status light is off then turn light on wait 2 hours turn light off else nothing When this program triggers true, it will run, but immediately re-trigger (false) and halt the wait statement, re-running the else path. In this case, best separate the conditions and actions.

first, make sure that the garage lights are not in a scene with the motion sensor. Alternatively, you can put it in a scene, but make sure the motion sensor is configured only to send ON commands. Then... if control motion sensor is switched on then turn on garage lights wait 10 minutes turn off garage lights

I am not sure that ANY outlet is waterproof. The question, I think, is the ability of the insteon electronics to survive the temperatures and humidity. I still have a couple of X-10 devices that work well outdoors for such things. It is like a short extension cord with the brains built-in. I also have a similar (though larger) z-wave module. Perhaps something like this would work for you.

In addition to the suggestion by Larryllix, one can also check which programs last run. When you experience that light going off at unexpected times, check your program list to see which programs recently ran and could have turn it off. If not a program, do make sure that the light is not part of any scene that includes motion sensors or other controllers that might be turning off for some reason.

But this is not what is happening, correct? The lights are turning off even if the door is still open, correct? If so, my question stands...are the lights turning off at sunrise? Or are they turning off at other times even when the door is open?

If the program works, then clearly the ISY is seeing both OPEN (on?) and CLOSED (off?) status. I have no idea why it would not show up in the admin panel.

I am not sure that "control" is the solution here. To be clear, you are saying that the light is turning off at times other than sunrise, correct? Your program WILL turn the lights off at sunrise, regardless of sensor status.

Have you figured out why you don't see "closed" status on the ISY? (This program will not work without having both open and closed status for the ISY.)

Did you create a scene with both switches as controller and module as responder? If so, within that scene select each of the controller devices and make sure all responder levels match up. All three devices should have identical ON level responses.

And the insteon switches have all the fancy LEDs which satisfies the geek side.

Sorry. When I said “module black”, this would be the “line” connection. You may need to add a short wire extension from the bundle of blacks. “Module white” is neutral connection. “Module red” is load connection. Yes, the sense wires will be unused in this case. Ironically, you could use your existing two switches with the micromodule sense wires and have complete automation control.