oberkc

Yes, there are three options you listed, but you may need to do all three depending on your goals. You could choose your option number 1, but that would only change when the scene is controlled via ISY action (it would have no effect when devices are manually controlled, nor when responding to another controller device. Assuming you want the stated on-levels regardless of how a device is initially turned on, 1. Click on the scene and set the on-levels of the two devices to suit your 50/28 preference. 2. Click on each controller device within the scene and set the on-levels of each of the two devices to suit your 50/28 preference. See if this works for you.

Thanks for that bit of knowledge. In an attempt at full disclosure, there was a short time where I had changed the default login credentials on the IoP and had yet to make the change to the PG3 settings. I don't doubt that this created some log errors until I updated PG3. I had two "ISY"s connected to PG3. During all this difficulty I was having, my belief that both the ISY/IoP were connected was because there was at least one node server (not the Hue Emulator) on each that was appearing to work, and reflected in the admin console (the nodes were in the device listing, as well as under the drop down node server dialog box.) Thanks for your help

My whole experience with the IoP and PG3 has been odd (putting it kindly). I had a working ISY-994>PG2. I was preparing to migrate to IoP by updating the software of the IoP. The results included breaking my ISY-994>PG2 relationship. I thought I had, but I can see it was not obvious, or perhaps answering the wrong question. I have checked multiple times and my settings are correct as best I can tell. Both show "connected". I was on 3.1.8, but am now on 3.1.10. It took me a few minutes to recognize that the update reset the username and password to default. This did seem to have an affect. Hue node servers are now showing connected on ISY-994 and IoP. I tried installing the Hue Emulator node server on IoP and ISY-994. No more errors and both are showing "connected". I am going to call this a small victory. The hue nodes now show up in "my lighting" , as does the hue emulator. I will call it a big victory when I can confirm or configure all the programs and scenes with the hue lights. Usernames are correct as best I can tell. Both have been showing, and continue to show connected. Both had some node servers working but others not. But...the point may now be moot given that moving from PG3 v3.1.8 to 3.1.10 may have fixed the problem. I will know more soon, but it all seems to be coming together now The non-standard port was driven many years ago. I had another device that also used port 80, so when I tried to access the ISY on port 80 from a remote location, it found the other device. I gave the ISY it's own port at that time and things have been working well, so I never changed it back. I will continue to check out everything to see if it is working or, if not, update all the programs and scenes to their original configuration.

Thanks for looking and finding the errors in the log. I wish I knew what do to about such a revelation. I can get the hue node server to run on PG3>IOP, so the connection seems to be working. Unlike the Hue node server, the hue emulator, I notice, has fields for the ISY, which I have populated multiple times, and match the global PG3 settings for the ISY. In the hue emulator, I notice that the port for ISY (8080) is the same as the port for the emulated hue (also 8080). I assume that this is not a problem. I also observer that I can install the hue emulator, I get the big red error message during installation, but the hue emulator still shows up on the dashboard (disconnected). I can then populate the ISY fields under the configuration page, but after a few minutes, the dashboard no longer has the hue emulator. FWIW, I also have a second ISY (the legacy ISY-994) running and recognized by PG3. The results with the hue emulator are nearly identical. Furthermore, the hue node server (as opposed to the emulator) will not connect (it DOES connect to the IoP).

I will try to send it, but the message system is not accepting the file for some reason.

Would love to do so. To where does the log package download go (not to downloads, apparently, on a Mac)? Do you want the "debug" package or one of the others? While I suspect there is a problem with the "log PACKAGE", it appears that I can download a "log" file. I will PM to you. FYI, the error I get when trying to install the Node Server install of undefined failed with message: status is not defined

While updating software for IoP (in preparation for moving from ISY-994), the node servers from PG2 (on policy) all became disconnected. Based on advise from submitting a ticket with UDI, I am now trying to move to PG3. Unfortunately, I cannot get the Hue Emulator to run on PG3, neither while connected to the legacy ISY-994 nor to IoP. When I load the Hue Emulator while connected to the legacy ISY-994 I get a big red error: Node Server install of undefined failed with message: status is not defined When I load it while connected to the IoP, it appears to actually load, but shows current status as disconnected. More details upon request. Thoughts?

I would be a little surprised if this was noise, since this appears universal across a type of device. I wonder if restoring the keypad would solve this (perhaps some link records became corrupted or don't match the IoP).

My first instinct is to confirm that the new "ISY" is seeing the button press. If you open the event viewer and have someone press the button H, does the event register?

I don’t know whether you are late to the party, but this is how I have done echo voice announcements.

Unfortunately, some zwave switches do not trigger program “switched on” coditions, including ge/jasco. “Status” conditions might work. I recall, also, that one might be able to create a node for this switch that DOES respond to switced conditions. I fear, however, that this may be a downside risk with zwave devices.

Yes. I have a couple of empty programs I use as a binary state indicator

??? Run a program step that calls the binary status program "then" or "else" action. Did I miss the intent of this quoted statement?

In different words, since your main basement lights are physically powered by the six-button keypad, and time that you turn on the keypad main (on/off) button, the connected load will also turn on. I was wrong to suggest that it could the on button could be lit without the main basement lights being on.

You may be right. I forgot that this is the button to which the load is connected.

I don't think it would be that hard.... if laundry room light is not off or hallway light is not off then turn on keypad main button this is not even close to being a hole yet, compared to some of the stuff you guys do

Good that is is working. Now...the question becomes whether you want the keypad button to be an indicator that at least one of you basement/laundry room lights are on? Are you satisfied that a laundry room or hallway light can be on, but the keypad button stays off?

Please make sure that this is the case. My program was more logic oriented and syntax was approximate, at best. Make sure that your condition is a “control” rather than “status”. If you want us to check your program, feel free to post it here.

I am not convinced that this is true. On my six-button keypads, if the main button is OFF, and I press the OFF button, it will send another OFF signal. (This is also true on toggle and rocker switches.). Given this, you would not have to turn ON the main button before turning it off.

Technically, both ON and OFF buttons are linked (part of a scene) to your two basement lights. If you want only the OFF button to turn other off, a program would work. I would put all the other (besides the two that are linked) lights you want to turn off into a new scene. Then, create a program: if six button switch is switched off then turn off new scene

Good catch snd should be heeded.

One can set up an ISY program as a device for Alexa to turn on or off. When doing so, commanding Alexa to turn off the device (the program, in this case) the program will execute the "ELSE" path of the program. When commanding Alexa to turn on the device, the program will execute the "THEN" path. Given this, my initial reaction would be to create three programs. Logically, they could look something like: Program 1 (the program Alexa would turn on and off): if nothing then run program 2 (if path) else run program 3 (if path) Program 2: if from sunset to sunrise then turn on inside lights turn on outside lights else turn on inside lights Program 3 if from sunset to sunrise turn off inside lights else turn off inside lights turn off outside lights

A scene relationship will not work for this case. I believe a program is the solution you will need for this. Assuming that you also want the opposite (button off when sensor on), such a program could look something like: if sensor is on then turn off button scene* else turn on button scene* *Most keypad buttons cannot be directly turned on or off. Most likely you will need to put the button into a scene and have the program control the scene.

I have not used a z-wave companion switch before. Insteon did not have companion switches. If I were wiring this, I would use two full-feature z-wave switches and link the two switches via zwave communication. At the top of the stairs, connect line to both the switch (line) and to the black wire of the 3-conductor (red, white, black) cable. Connect the neutral wire to the neutral connection on the switch and to the white wire of the 3-conductor cable. Cap off the red wire of the 3-conductor cable (you won't need it). At the bottom of the stairs, black is now line, and white is now neutral. Cap off the red wire. Connect black to switch line. Connect white wire to switch neutral and to load white wire. Connect load black wire to load connection on switch. In all cases and locations connect grounds (bare copper) to switches and to each other. To get your three-way to work you will now have to link the two switches. If using an ISY, create a scene and add both switches, both as controllers. Hopefully, this will work for you.

I would probably be interested in a couple of the IOLincs