lilyoyo1

The pool deck floods switch is a response not a controller so that is part of it. Make sure the devices are configured in all controllers too, not just the scene. Simply remove the responder and add it back to the scene as a controller

I acknowledged that you updated to 5.3 in your original post which is why I asked if your UI matched. If it doesn't you will have issues such as what you're experiencing. Downloading something doesn't mean your UI matches. The instructions says to clear your Java cache which you did not say whether you did or not. A quick look at the help>about tab would show the information I'm asking for. Your pictures so not show the scene itself from the device column on the left hand side of the admin console.

The isy is not aware of an unplugged device so it will still attempt to do its job by wiring to that device. This week slow down both protocols since the isy is still controlling the whole system. The best way around this would be to either leave the device plugged in or disable removed devices do it will skip it. Upgrading to the pro version allowed you to disable writing to wireless devices

You never said if your UI matched your firmware. If they do not, this could be why your isy is behaving this way Check your scene itself. Controllers should be in red while responders are blue. If you want these lights to behave as if they were a multi-way switch then all should be controllers

In addition to what was already posted, I would verify your 6 button is not in non toggle on mode. If it is, the button will always stay on. If all devices are associated together and controlling each other the same exact way, I would add each one to a single scene (if it's not already) as a controller and making sure all are triggering each other the same. Since you've recently updated, make sure that your firmware and UI matches.

Its neither but if you wanted to be technical about it, then it would be a status condition. Status about the state of the device. This can be changed via multiple avenues such as voice, app, another device. Control is the physical control of a device. ie: you manually press the button on a switch. Zwave does add a wrinkle to this because...its zwave. Who knows why zwave does the way zwave does. Some devices will use status even though you are manually controlling the device. IF time is from sunset to sunrise THEN Set Light on OR ELSE Set Light off

I wasnt trying to be specific in writing a program which is why i wrote it that way (doesnt even have anything to do with what op wanted). I was simply showing how AND & OR functioned. However you are correct. If this were a proper example, one would need to use status

And & Or does work differently depending on what you are trying to accomplish. For example, If you wanted to turn on a kpl button whenever a light in your kitchen is on (let's say you have 3 sets of lights), you would use "Or" for your program. Ie: if light 1, or light 2, or light 3 is turned on THEN do whatever If you wanted that kpl light to turn off when all lights in the kitchen are off then you would use "And" Ie: if light 1, and light 2, and light 3 are off THEN do whatever. Just remember when it comes to Or Else statements, it works great for basic stuff such as simple on/off timers (turn your outside lights on at sunset off at sunrise). Anything beyond that, you're better off splitting your programs....especially if you'll have multiple programs controlling the same devices.

Must be the invisible text Udi uses. Makes it hard to read. You can find it in the first page of this post. Very first post

I don't know. I don't use it. You could check the isy wiki or Google isy smart meter

As long as it's a 994 then it's compatible

That was at the beginning of your post. After you found a work around, i was responding to post in regards to how variables could have helped for what you wanted. Since you found a better work around, the whole variable is moot

Im assuming you must not have read any of my precious responses on this post because I've already acknowledged and explained that explained that in previous posts right above this. I will repeat, at the time, the variable was only to set the light to where you wanted it to be. Since you found a workaround all of this is a moot point

Wasn't quite sure of your point so I was clarifying my statement to lessen the chance of misunderstanding

It's not a bug in the firmware. It's insteon's behavior. Insteon was designed to work first and foremost without a controller so there are things devices can do that the isy cannot prevent. The isy is seeing the press otherwise variables wouldn't update. The command that it sends (turning lights to 100%) is interpreted by the device outside of the isy. To the Isy, the device is only turning on to where it is supposed to go while the device itself is interpreting the command the way it's supposed to. It's similar to using the mutually exclusive option that the isy has (why Udi recommends scenes instead). Those are within the device and the Isy doesn't see it.

The variable has nothing to do with stopping the light from ramping up. It was to track the press which would then run a program to adjust the light to the desired level accordingly. 1 press- light (scene) turns on at 70% variable updates #1 2 press- light (scene) goes to 100%. Variable updates to #2. Program runs and Isy turns light (scene) to 70% Off press- light (scene) turns off and variable goes to 0

Its his issue in regards to the status but not in regards to his variable not updating. The variable was only to track the button press so that if it was hit a second time, it would update and run the corresponding program. The program itself would then run based on that variable to set his scene to the proper level.

I don't know. It could be based on timing when the isy sees the second press. Are you doing it quickly where it's seeing a double tap vs a single tap? I have my variable set up to count presses. In testing my variable updates with the second press. Even in the video, it shows you the counter moving while testing the variable so I'm not understanding why yours doesn't update My program is set to capture double taps and the variable. That way whether I want music immediately in both areas or change my mind later, it will operate without issue.

I'm glad xlurkr's suggestion works for you. Not sure why a variable didn't work as I use it for switching my music in the bathroom from single room to bath and bed without issue

As in life, there's no elegant fixes for behavioral fixes. Nothing is really going to fix his issue perfectly as there are other variables that will inevitably come into play. Going that the rabbit hole will cause more problems long term than it solves. Personally, I'd leave well enough alone and show guests how to use things properly rather than deal with trying to program my way out of it. variables can help with the swl (the way he describes the situation this sounds like it's the problem). Whether it's a double tap or a second press in general, the isy can capture that via the variable (including programming) and trigger the proper scene based on the second tap regardless of what the light level the switch is showing. 1 tap would move the counter to 1 and the scene would run as normal. Should a person tap it a second time, the counter would move to 2, his program for the second tap would then see it and run causing the lights to go back to their normal level. Once he turns off the switch, the counter would reset, restarting the whole process over again. There are other factors at play which could impact things, which would require additional programs to account for. This is why I said earlier that there are no elegant solutions.

It's true for all keypads in regards to turning on and off. A 6 button kpl would be the same as a dimmer since it's on and off are separate (didn't add that tidbit). An 8 button in default mode toggles on/off. Depending on the level, you can dim up from a low level or dim down from higher levels. Regardless, for what he wants to accomplish and why, any other method other than variables will most likely lead to more programming to make up for something else that goes wrong with those methods

Did you watch the video? It explains how it would help you?

If the isy doesn't show 100% based off the button press, then status will not work since it'll be wrong. Using variables is the only way to accomplish what you want

A variable is the best method. The link I sent earlier showed how to set that up. You could use status. If status of light is 100% Wait 2 seconds Then set to 60%. The wait is there to ensure the isy has time to process everything

Unless double tapped, a keypad should turn off on a second press (if it's in toggle mode). Only switches will turn 100% on when it is pressed a second time since on is always the default command built into the device. You cannot override default behavior with the isy. You can only have the isy adjust it once done. You could use the status of the light to adjust the light downward. The problem with that is it will always dim even for the times you may want the light 100%. If you're that concerned about a second tap, using variables is the best way to go. It can see the second press and adjust the light after the fact. Keep in mind, the same thing from above applies. Should there be a need for 100%, the lights will not go to it. If this is a guest only location, why bother automating it in that way? You'll cause more confusion and headache trying to program for vs keeping things as normal as possible for people who are not accustomed to that. Here's a video on variables https://youtu.be/d8sHbgWc0vQ