oberkc

The fact that the lights do not turn on is not necessarily conclusive evidence that a program did not run. Perhaps the program ran, but the lamplincs did not respond. Perhaps they turned on, but something else turned them off. Personally, I have never knowingly had a program not trigger and run when it should. This is why I suspect something else is going on. Were this me, I would check status at admin panel right after program run to see if three devices match actual status. If not, there is a problem with communications most likely. Failing that, I would be looking at the program log to see if there are other programs being triggered immediately after this one. Is it possible that the change in status of one of these devices is triggering a program somewhere? But, maybe there is some bug somewhere. I can only say that a program so simple like this one is one I use multiple times a day and it fires every time.

I agree with apostolakisl. This should work. The program should run. There are no ways it cannot run. Why do you think it is not running (is it based on lights being not on)? After it runs, what does the ISY admin panel say about the status of the three devices? Does the ISY believe they are on? Is it possible that something is going on near sunset that is not going on when you manually run the program? Is the ISY sunset time accurate for your area?

Hey, Jack. If the switch is turning ON to a scene command, but not OFF, I would tend to discount (for now) a faulty switch. I did not see it asked, but what is the load on the switch? Can you temporarily remove the load to see if the switch starts responding to scene-off commands? (I am wondering if the load is causing the communication problem.) I do not believe that this is a programmatic problem. It sounds like a classic case of the ISY assuming a switch responds, but does not.

Yes. You can also check status (true/false) of the program. If true, that is a pretty good indicator tat it ladt run THEN path to completion.

Programs are triggered by events, based upon the conditions. Programs do not automatically re-evaluate based solely upon completion of an action clause.

I suppose it depends on what you would like it to do, and whether "closed" = "off". It may also be affected if you are using the sensor reverse mode on the IOLinc. In general, if the query causes a change in status of 'garage closed', the program will re-evaluate. A program in a wait state that is re-evaluated will be halted and run from the beginning, based upon the newly-evaluated status (true or false).

Good question. I do not know for sure. Do you actually use all eight scenes, or could you get by with four?

Gary, Perhaps I don't accurately perceive these hubs, but I understand that few have the automation power of the ISY. Yes, they may better support Z-wave links and scenes, but lack the logical power of the ISY. Is this inaccurate based on what you know?

The current status shown, I understand, is the last recieved command. Like I said, I don't believe you can change the status externally. Larryllix has the best idea I believe, which is to put the remotelinc into non-toggle mode and create a program (triggered by the proper button command) to turn the lights off (if on) or on (if off).

You are welcome, jedi yodallix

Like most, I see no reason to remove perfectly good insteon device and swap with z-wave. I am happy with insteon at this point, and if I could not continue with insteon, for some reason, then the ISY offers me an option to retrofit with z-wave as insteon devices fail. Otherwise, all is good.

My perceptions are that the sole purpose here is to avoid having to press a button twice, rather than a direct display of status. If a scene for which the remotelinc button is controller is turned on by other means, pressing the remotelinc could first send an ON command, rather than OFF command, apparently, forcing the operator to press twice to turn the scene off, or vice versa.

I control only one hib at a time. I thought stusviews mentioned four, but was not cerain whether he has all four linked to his alexa account simultaneously. Like you, I would not mind controlling more than one, but did not find a way to do so in the short time I have spent playing around with it.

My recollection was that they can be set to four- or eight-scene mode. In the four scene mode, there are discrete ON and OFF buttons for each scene. In the eight mode, buttons are toggled. I did not recall a non-toggle mode, but I quickly checkef the manual and it appears to have one. Good thought.

I don't believe so. Remotelincs typically transmit only...no recieve...no status.

Th Well, I already had a couple of Harmony Hubs in use around the house. Controlling them via the Echo was pretty simple. Like you, it seems I have less time now, after "retirement" than I did before. All that time I thought I would have seems nowhere to be found.

Good to know. Yeah, I suppose. Fortunately, I have enough automation with motion and doors and location that this is rarely the case. I am sure I would find it interesting and fun as well, but I have too many other hobbies and find myself wanting to play golf, play in the wood shop, and do some other projects around the house.

It has varied, but right now it is a small Roku TV. The echo controls it via the harmony remote control. With regards to the echo, I guess I just don't value enough voice control to put the effort into optimizing it. For the things I desire to control, I find conventional methods of control equally as convenient (if not more so).

Nicely done. I hope the logic is coming together in your mind regarding scenes, responders, controllers, etc... Thanks for the education on the echo. I actually have one, and am considering the spot when it becomes available. I remain uncertain whether I like voice commands and having to remember specific syntax, so I don't do a lot with it. Mostly, I use it to turn on my TV and one hue light.

I am mostly unfamiliar with what the echo can do with insteon. Clearly it can run a program. Can it turn on devices? Scenes? Multiple things in response to a voice command? You may have to break the single scene into three: on, single shot, and double shot. On has F as controller and G/H as responder, set to zero on level. Single shot has G as controller and F/H (100%/0)as responder. Double shot has H as controller and F/G (100%/0) as responder. Use the same response levels at the scene level, also. My temptation, after that, would be to create a couple of Alexa-specific programs. One would look something like: if nothing then turn on double-shot scene run Mazzer-Grinder-double shot (then path) The other would be similar and I leave it to you to figure out.

Accomplish this entirely with scenes. Afd.both dimmera to a scene, both as controllers. Pay attention to the responder rates are comsistent for both controllers. To activate via program, be sure to activate via the scene, rather than by one of the switches.

That looks consistent with your stated goals to me. If you are still getting results consistent with post #8, I would consider the possibility that you still have some of your existing programs are affecting button operation. Are your existing programs still active? If so, delete them. Then, create a couple of simple programs: if control button H is turned on then wait 26 seconds turn off scene else nothing If control button G is turned on then wait 17 seconds turn off scene else nothing

You must also establish correct responder levels for each of the controllers in the scene...not just the scene level. When you press buttons F, G, and H, reponders will comply with levels for each of the controller buttons which may or may not be same as scene level or as each other. With your mouse, click on button F within the scene. What are the responder levels for the other devices? Are they different than the scene levels? Make them what you want. Do the same for buttons G and H.

I think like stusviews in this case. Create a single scene with F, H, and G as controllers and appliancelinc as responder. Adjust responder levels independently for each of the three controllers. As an example, for controller F, rsponder levels G and H are set to zero. For controller G, responder F set to on, and respnder G set to zero. Do similar for controller H. Then use programs triggered by G and H to turn off scene after appropriate time. There may even be value in configuring buttons G and H as non-toggle ON.

My motion sensors are the original version (not current version). Based upon my admin panel, they have only three nodes: motion, dusk/dawn, and battery. None of the nodes show a number such as the one in your image.