oberkc

Certainly it is easy enough to distinguish between ON and FASTON in a program and take different actions as a result. I am not so confident that one can create a condition based upon 100% status, but only if arrived to by ramping up. That would be a bit trickier.

When in momentary B mode, the IOLinc will respond to ON and OFF commands. Whether this is correct depends on other goals and faxtors, but it seems unlikely to me that this (or the 2 second dwell time) is the cause of your problems. Still, try 1 second and see what happens if you are unsure. Could this be a mechanical issue with the door? Sometimes, door can physically bounce and cause the opener to sense an overload condition and halt. Does this ever happen when you press the wall switch?

I agree with MWareman for those in a high threat area, but you COULD get by with ISY and geofencing control of garage door in areas where you don't have thieves waiting for every opportunity. If an open door is a virtual guarantee of an intruder, I would not connect insteon or ISY to the door control. For those of us in less threatening environments, I think a location-based opening and closing of the door can be a viable option. I use a combination of factors to decide when, or if, to automatically open the door. The general logic is based on: a) location, that is, connected to home wifi also connected to car Bluetooth c) checks current status of door and sends a signal only if open. I would probably not use location, alone, as a condition for opening or closing the door. My experience is that the combination of Bluetooth and wifi location is pretty robust logic and does not result in momentary crossing signals. I also send a notification to my EMail account when the door has been automatically activated, so that I can check things out if one of those notices comes unexpectedly. Video cameras are nice for this.

Neither the program I suggested, nor xathros' timer program, would turn the light back on. xathros override program would re-enable the timer program when the switch is manually turned OFF.

I would think this issue comes up all the time: there is an extra box location somewhere...now, what can I do with it?!. Yes! Put a keypad or another switch and use it however makes sense in your house. So long that this box location has hot and neutral, put an insteon switch of some time and provide control of something useful.

I also subscribe to xathros' theory that if the lights are already on, there is little harm in turning them on. The opposite is also true, in my mind. If all you want them to do is turn on at a certain time, then turn off 2 hours later, what is the problem with a program such as: if from a certain time (such as sunset -15 minutes in your case) to 2 hours later (or sunset plus 105 minutes in your case) then turn on lights else turn off lights A program such as the one above will turn the lights on at a certain time (if they were already on, does it matter?). Two hours later, the program will turn them off (if somebody already turned them off manually, does it really matter?). I would like the option to keep the lights ON somehow. Check to see if the lights were manually turned ON and, if so, keep the ON until manually turned off. Xathros' example override program appeared to address this issue

Care to share? Once involved, I cannot help but be curious?

Normally, I would assume such behavior is caused by a scene relationship. Are you saying that these devices and buttons are no longer in a scene, that the groupings are cleared, and it still does this? Is there a scene that includes the "one button" as controller. Does that scene include "all buttons"? Are responder levels for all buttons set to zero?

So, you have removed the button groups. What is the problem that remains? Is there some unexplained behavior somewhere?

try first the parentheses. It is my hope that this will work. If so, you are done. But...yes...I like simple better than complicated, all other things being equal.

I have used groupings in the past, as well, but prefer scenes so I do not use them now. Never saw a problem, but never made changes or replaced such a device. Be sure to take advantage of the tools. Select the device in question and it will show the scenes in which it is a part. From the programs list, there is a "find and replace" option that is very helpful for finding where certain devices are contained in a program.

I understand. I suggest, however, that if your intentions are simply to "turn of lights" (per original post), then the only harm is that the ISY will send an OFF command to lights that are already OFF. To me, that is harmless enough. If your new program fails to achieve your goals, you might try this approach as an intermediate step. This could help troubleshooting.

Doug95630 I suspect you problems have less to do about motion sensor reliability and more to do with programming logic. Do you know about parentheses in programs? Try putting parentheses around the last seven lines of your program condition. Alternatively, what harm do you see in completely eliminating the last seven lines of your program?

Like Brian H, I am unaware of any method one can use to eliminate a device or node from the ISY admin panel. The method I use is to name it something like "fanlinc light (unused)" and move it to a folder of unused devices.

Some have said they use zwave exclusively with the ISY controller. I do not. My perceptions are that it could work well but youwould be near fully dependent on programs. I do not believe the ISY has the ability to create direct scene relationships between zwave devices. While i still use more insteon than zwave, I have liked both. Until the point the ISY supports zwave scenes, though, I would probably continue to favor insteon and use zwave selectively.

While I own two of the WF2IR devices, I use them with other software and have only performed limited experiments using them with the ISY994. I am a little fuzzy on what the flex device does and how that compares. My impressions are that one could use the WF2IR and learn specific codes from an ir remote, but that it takes some effort (and the network module) to get things working. If you are willing to experiment a bit, however, I expect that this would work. The one concern I have is that some ir-controlled devices can use codes that appear to be non static and that may create some complications. On the other hand, if you were able to learn the command on your harmony, I doubt this is a concern. Is there some reason you have not chosen the irlinc transmitter? While I do not own one, this seems to me to be the obvious option. (Perhaps there is some limitation with ISY of which I am not aware?)

When you have noticed comm issues with this device, is the prblem normally the pump failing to come ON? If so, then I would be focusing on factors external to the pump, itself. This is definitely a relay outlet, not dimmer. Correct? Also, be sure to do your best to ensure PLM is on a clean circuit. No other gadgets and computers/ups/routers/modems. Right? Do you ever use filters?

Some folks have downloaded the data describing the meaning of all this. I have not done so yet. Stiil, I believe the fouth line may be the axknowlegement from the responder and the hop count suggests pretty good communication at this point in time. Did your outlet turn on? Given appearances that comm is good at least some of the time, I would be considering what intermittent devices (HVAC, washer/dryer refrigerator, etc..) that might explain why comms would be good some time and not others. Also, see if comms are as good when turning OFF the fountain. If not, this could suggest that the fountain pump, itself, could be contributing to comm errors

My initial assumption in cases like this is to treat as a communication problem. My understanding is that ISY will assume commands issued are followed, and device status tracked according to those assumptions. Even if expected confirmation from device is not recieved, device status will be updated based on assumed response to commands. Obviously, ISY status and truth can conflict when the device failed to respond as expected. Given this, I would start troubleshooting effort to identify comm problems.

I ran a minor experiment. In fact, if a device is a scene controller, you can use it in both places (controller and responder). Assuming that 'lum. salle de bain' is a scene controller, I suggest the action: in scene 'lum. salle de bain' set 'lum. salle de bain' 40% If it is not currently a scene controller, create a scene, with it as scene controller, and no other device. Then use the action statement, above.

A more accurate statement of this action context would be: In Scene 'name_of_scene_controller' Set 'name_of_scene_responder' 40% (On Level) Of couse, "name of scene controller" can be the name of the scene, itself, if looking to adjust the response to ISY programs or commands.

Ok. So...instead of changing scene responder level of 'lum. salle de bain' , we need to find a programmatic way to change responder levels when applied locally. I have never needed to do this, so I am uncertain how. The ISY user manual claims that the "adjust scene" action can be used to adjust the ON levels for devices or scenes, so I assume it can be done. Unfortunately, I see no instructions how this is done. is "lum. salle de bain" already a scene controller? If so, use the adjust scene like: In scene 'lum. salle de bain set lum. salle de bain" XX%. If not already a scene controller, perhaps creation a new scene with the single device as controller and use the same action, above.

I dont know whether your problem is related to the speed of the ISY (doubt it) or the nature of insteon devices to complete one task before starting the next. Yes, this can be fixed, and I think stusviews is on the right track here. I believe that you should change responder levels at 8:00pm to 40% and back to 100% at sunrise. Modifying stusviews ideas: If From 8pm To Sunrise (next day) Then In scene 'scene nommer' set 'luminieres/liminiers ineriures/lum salle de bain' 40% Else In scene 'scene nommer' set 'luminieres/liminiers ineriures/lum salle de bain' 100% Sorry for my language skills. I dont speak anything but english, and probably not well.

Regarding speed, the thing that I notice that seems to slow program response is communication problems. While it seems a response of a second or less is tough to improve, longer response times may be an indication of communication difficulties.

I do not believe that scenes, alone, can accomplish your goals.