oberkc

Blueman2, Perhaps your original question was answered and I missed it. I expect you two programs to work fine together. Your understanding sounds about right to me.

johnjces, I am a little unclear on the details. Do you want this to "fire" only once per week, and no more than once per week? Seven day week? Five day? Something else? I believe this can be done on version 4.5.4. It would probably be a brute force approach, with several programs involved. Conceptually, one can create a program to generate a random variable value between 1-7 (alternatively, may be between 0-6, but I would have to investigate). At the beginning of each week I would run that program. Once the variable is set each week, I would create seven programs, one for each day of the week. Each program would check if the weekly variable matched the day of the week. If not, do nothing. If so, run a path which fires whatever event you desire at a random time. This is all experimental for me. These are program conditions and actions I don't use personally. Still, I think it has a good chance of working.

I doubt that they were used, but i dont think you would be the first to have recieved units with pre-existing links.

JayC, Regardless of what happened or how, you may give the advice from MWareman a shot. It might work and is less work than a full reset. Your symptoms do seem to suggest that there are some residual scenes out there somewhere, somehow.

If all scenes involving these switches are deleted yet they still behave strangely, delete from ISY, then factory reset each switch. Does the problem persist? If not, add back to ISY and create any new scenes needed.

Start with determining: - are the lights part of a scene - the specific time the lights come on unexpectedly - whether a program fires at the same time - other activty in the log at the same time

I use it on android and have heard the same allegations. Perhaps the android version is missing some features that the iOS version has. This is probably most significant for those who value being able to look at camera imagery using the same app being used to control the house. Yes, that seems to upset some. Still, when measured on it's own merits, and compared to the other android options, I think it holds up quite well.

I use mobilinc. I am not in a position to say what is best overall...I think it could depend on your needs. For me, mobilinc offers a couple of important features not found in other apps, including widgets and integration with tasker. I have no trouble recommending it. If all you want is simple access to devices and scenes, however, other may be just as good and less money. You may also find one interface more appealing than another.

Get an app. Several are listed in the section for third party products. Or go to google play store and search for insteon and ISY.

hello lithiumus, based on my experience, there are two non-toggle modes: non-toggle ON and non-toggle OFF. In non-toggle ON mode, it will flash then stay on, regardless of starting state. In non-toggle OFF mode, it will flash and stay off, regardless of starting state. I know of no "non-toggle" mode where it simply stays in whatever state it started. I find this experience consistent with the manual for the keypad, as well as the options available from the ISY admin panel. I have no opinion on what it "should" do...only what it does in my house. Either I misunderstand what you are saying, or our experiences and expectations are different. My oldest keypads are about 7 years old. My newest about a year. I have noticed no change in behavior regarding toggle mode.

Lithiumus, Based on my experiences, a botton set to non-toggle ON will, when pressed, flash a couple of times, then stay ON. Based upon that, i find the behavior you describe more like: unexpected and abnormal.

Litiumus, What I find interesting in your post is that, in the second paragraph, you state that the original keypad button is in non-toggle ON mode, yet you say it blinks twice then turns OFF!? I find that to be abnormal. My buttons, configured such, would flash and stay ON (much like your second button). The question, in my mind, is what is different about your first and second button xonfiguration that would cause the.different behavior? Regardless, I can think of no better solution than stusviews suggested approach.

I have no opinions beyond those I have already provided. Yes, it could always be a device failure.

I know of nothing native in the insteon switch that would cause this. Given the apparent broad confusion about some of the program actions associated with adjusting ON and OFF levels, I cannot help but wonder if you have a program that is being triggered by some of your fan buttons. Is this possible? If you are unsure, open your admin panel and view the program list. Have someone initiate of of the fan scenes and see if any program reacts.

Based upon my device, it clicks about as loud as a lamplinc dimmer (which, in my mind, is not for any practical purpose.) If one gets really close, perhaps there is something audible to some, but...no... I would describe it as not clicking at all. Yours must be different than mine.

Many complain of the lack of security for insteon. Can you imagine how bad it really would be if all devices heard and responded to all other devices, regardless of whether they were linked together? I think we should be glad that one must go through the linking process before things worked together. I certainly makes it harder for someone outside the house to take control of things.

Agree with Teken. Control statements are limited to when a device is switched on locally. (In the case of an outletlinc...by the little button or load sensing.) A device changing status as a result of scene response from a controller unkown to the ISY...I would not expect that to work.

well.... Outletlinc Dimmer can be used as a control condition in a program. No, outletlincs do not emit any audible noise that I can detect. Certainly not the click sound associated with the higher-powered relays.

Thanks, teken. I will not need to check now. I will, however, check the dimmer outlet (I have one).

I will try to remember to check later today to see if the newer outletlincs have the control option. Will let you know.

The manual for this device describes only the process for making the outletlic a responder. This makes me suspect it cannot be a scene controller, which would explain why there is no "control" option for ISY programs.

I would have to research to be certain, but I fear that lack of a "control" option is an indicator that your outletluc is a model without the ability to be a scene controller.

Trojanhorse most likely found the root cause of your problem. I should have asked upon what evidence you judged the program not working. Sometimes, a program can work perfectly, but just not doing what you expect.

Is it possible that your program is disabled? Is your program in any folder? Could the folder be disabled?

Yes, I understand there is a lot of z-wave capabilities in v5, including z-wave direct scenes, but I have found zwave devices to work in insteon scenes (assumed enforced by the ISY since, obviously, no direct comms between insteon an zwave devices). I don't believe z-wave devices can be controllers in insteon scenes. I also understand that this capability may vary by device. I use z-wave outlets and modules and they all have worked so far. I don't think I have tried my lock in a scene.