oberkc

I am certainly no expert at Reading the event viewer. Still, I find it easy, at least, to see if commands are being seen by the isy. For example, if you press one of your keypad buttons a, it's not too hard to see whether you are getting an on or off command. I definitely would like to confirm that your buttons are all configured in non toggle (on) mode.

Good. Perhaps, then, I misunderstand. When you press Button A on keypad2 or keypad3, even the button A does not come on? This suggests to me that they are in non-toggle (off) mode or that there is some type of failure. In my experience, if a keypad button is in non-toggle (off) mode, they will flash when pressed, transmit an OFF command, then stay off. If a keypad button is in non-toggle (on) mode and pressed, it will flash, transmit an ON command, and stay on. If you confirm that they are, in fact, in non-toggle (on) mode, yet don't stay on when pressed, this is a problem with the keypad, itself. Either the ISY is not configuring it properly, or there is some type of failure in the keypad. I would check, again, that these buttons are in non-toggle (on) mode. A secondary check would be to open the ISY event viewer and observe what commands are coming when you press the keypad buttons A. Is the ISY seeing an ON command or OFF command? What does the ISY show as status for keypad buttons A when each is pressed?

And, given that some of the A buttons do not come ON when you press them, it makes me suspect that they are in "non-toggle-off" mode. Do they flash a couple of times when you press them? Given what you state that you want, I would ensure that ALL buttons A are in non-toggle-ON mode. Based upon the four .pdf files you attached, it appears that the scene settings are correct. My best guess is that some of your controller buttons are not all configured properly for non-toggle-ON mode. Based, also, upon my impression from your matrix for keypad1, I cannot help but wonder if you are having some communication problems somewhere. I also cannot help but notice that some of your link types are "command" rather than "Insteon". I would have guessed that all should be "Insteon".

yes, the same on mine. While small, individual scenes work fine (mostly), larger scenes seem to be taking longer as z-wave becomes a larger part. I can, and have, live with it but it makes me pause at the idea of a total transition to z-wave.

I have tried some experiments with Zwave devices and nodes, but have never successfully been able to create a z-wave scene (aka association). While I have Zwave devices within the ISY scenes, the link "type" as shown in the scene definition is alway "default" and I have never seen a link type "z-wave basic" between any zwave devices or nodes that I have tried.

Well, one thing that was not obvious from the post was whether this was a 6- or 8-button keypad. On the 6-button, "A" is not the load controller.

I thought the same thing, and have twice recommended checking the responder levels for all the controller devices within the scene. I am not sure that the message is getting through amongst all the other tangential thoughts.

Except that non-toggle sounds like the best approach to meet the stated needs (button A always "turns ON the scene"...the only stated requirement for pressing button A). Yes, there may be unstated requirements and yes there may be future requirements and expansion, but my intention was to address why the solution did not meet stated requirements, rather than question the requirements.

Unfortunately, your attachment showed only the responder levels for each device when the "scene" is controlled (ie, ISY/PLM is controller device). As I suggested earlier (perhaps with insufficient clarity) you also need to check responder levels for the other controller devices. Remember, this is still an Insteon system, and controller/responder relationships are established between individual Insteon devices. Each device you have established as a controller will have controller/responder levels that may or may not be the same as for the scene and for the other controller devices. You must ensure all responder levels for each of the controller device is correct. Do this by selecting each of the controller devices within the scene and observing/confirming responder devices for the other devices in the scene. Yes, one can do this, but it does not necessarily explain why the approach by SESamuels is not working. And, if one does not need the extra flexibility, then one has multiple scenes where one is otherwise sufficient.

Assuming it is not something such as communication errors (does not sound like it to me), I would confirm a few things.... Sounds about right. I suggest checking the responder levels for both buttons A. Mouse-Click on the scene name...what are the responder levels for the various devices in the scene? Mouse-Click on each of the two scene controller buttons...are the responder levels the same? Are they what you expected? Remember that scene controllers are also responders to other scene controllers. Also sounds correct. Make sure that this is true not only for scene#1 (when selected in the device listing) but also for when any other controller in that scene (two buttons A) is selected. Remember, responder levels within a given scene can be different for each and any controller within that scene. Which leads me to a question...does button A keypad 1 cause anything to happen to any of the keypad 2 buttons? Which leads me to: how do you determine that scene#1 "does not turn on". Does button A of keypad 2 not turn on? What must be ON for you to declare scene#1 to be ON? Are there light fixtures involved? To what Insteon device(s) are those fixtures attached?

I have a couple of Leviton zwave switches. I can add them as scene controllers. Unfortunately, I am unable to create scenes directly linked (link type: zwave) but only via the ISY (link type: default) to other zwave devices. The scenes function fine, but I assume would cease to do so absent the ISY-994 controller (unlike Insteon).

I wonder if one of those Itach WF2IR-type devices, along with a network resource, could be made to work. I am (unfortunately) uncertain whether they can receive IR, or just transmit.

Don't know whether they are going out of business but I, too, used the GE/Jasco outlets and they work very well. At one point they were available at Lowes, but I don't see them anymore at my location.

There may be a few tricks to the z-wave "inclusion" process, but they are relatively easy to learn and, once included, z-wave works quite well based upon my experience. I understand z-wave is a mesh-type system and may require multiple devices, depending upon how far away the z-wave device is from the ISY. Sometimes, a device has to be included close by before installation in the final location. Factory reset of the z-wave device is a good idea, like with Insteon. I will add, too, that z-wave works best as a responder device than as a controller. Outlets, and plug-in modules work quite well in scenes and programs. Controller devices (such as wall switches) have some potential issues with programs and scenes, but there are possible work-arounds depending upon which z-wave controller device you have. I would definitely give one a shot.

I don't fully understand why this is the case, but I had to bring my lock quite close to the ISY (after factory resetting) to enroll it. Once enrolled, it works fine at the installed location, 30 feet away separated by walls, but with a couple of z-wave devices in-between. Enrolling the lock while installed did not work well for me. This process was also required by a couple of z-wave switches I use.

This is how I have done a lot of my devices. In a couple of cases, this is the only way I could get it to work. I sometimes update them, and when I check the neighbors for each device, the logical ones seem recognized.

I had a single switch that exhibited this behavior for a few years. I have several of these same brand and model switches yet only one exhibited this behavior but I never did figure out how to make that annoying (switch otherwise worked) green icon go away. Recently, I replaced the switch for unrelated reasons. No more green icon. Was this a bug in the ISY? A bug in the switch? A faulty or marginal device? Not sure there is enough data to reach any conclusions.

While I do not suspect this to be the problem, it is easy enough to check…. what happens if you try to include one of the buttons into a scene with anothe insteon device, as a controller? Does the scene work?

Yes, "status" works on mine also. If, however, your logic works better with a "control" condition, try the "add/refresh button press node" trick. It might work for you (it does for me.)

The GE smart switch is z-wave!? I have had zero luck using "switched on" with GE switches. "Status" seems to work for me, but not "switched on". There is one trick that I am aware of: right-click on the switch node and choose "zwave>>add/refresh button press node". Once the node is added, see if this new node triggers your program. I understand that other z-wave devices might work better in this regard.

I have found the same thing in my house

Don't think that you will accomplish your goals with a scene. I understand the quicker nature of scenes, and your desire to take advantage of this, but scenes are between devices and cannot be disabled as far as I know. No. I think you are fighting an uphill battle here.

I don't expect that this will do what you want. In general, Insteon scenes cannot be stopped. Unfortunately, I cannot say with certainty that a mixed (z-wave/insteon) scene cannot be halted, but suspect the same is true as for a fully-insteon scene. Controlling when a device reacts to another device is best, in my estimation, done via programs, without scene relationships. Delete the scene and create a program such as: if time is from sunset to sunrise (next day) and motion sensor is switched on then turn on light wait a little bit turn off light else turn off light There are additional possibilities and sophistication that one can add, depending on needs and interests, but this should get you started.

IIRC, adding a program to Alexa will result in the program executing THEN path when Alexa is told to turn it on, and executing the ELSE path if told to turn it off. No condition is needed.

I am only superficially aware of how all this works together. I am not familiar with many of the details. I would try restarting the node server. After that... Open alexa app, see if errors message with individual devices or indication of problems with the ISY skill