oberkc

What Alexa category did you use for this scene? Light? Switch? Scene? Other? Does this scene work when run from the admin console? Depending on the fixture and bulb, sometimes low levels of dimming can be more than the fixture can handle. I have not been successful trying to dim Insteon scenes from Alexa. Furthermore, if the scene is not added as Alexa category "light", I don't thing that Alexa will recognize the scene via voice commands within the context of the room in which Alexa resides. A simple solution (hopefully) would be to create an Alexa routine. Choose a voice input command that is easy to remember (such as Alexa: dim room). When commanded, Alexa would be programmed to turn on the Insteon scene.

Thanks for the refresher. I thought it might be something like this, but did not recall. I also did not recall whether there was another command such as "end repeat" to break a repeat sequence.

I thought messing with things is what we do here. There is always one more thing to automate. Have fun at the beach.

If you want the whole ISY-994 unit, you can have that as well. I think it unlikely that I will use it again and I would rather it find a good home than sit it my house for the next 20 years collecting dust. Send me a PM with your address.

To create a scene, you can choose the little symbol that is three small circles within one larger circle. I think it is also available under "link management". Scenes are a pretty basic and powerful feature of Insteon and ISY. If you are not familiar with them, I would check out the user manual or wiki.

Perhaps I assumed too much or responded too quickly. Upon further review, I see that you are using a couple of programs where I (and I suspect most) would use a scene. Unless I continue to miss something, I would create a scene with your office "2-way" as a controller and the other switches as responders. Once created, get rid of the two programs. Scenes can be created from the admin console where the devices are all listed. One benefit of the scene is that it would work even if the ISY fails or is removed. If, for some reason, you would prefer to keep the programs, change the condition in the two programs from a "control" to a "status" type. I understand that you have already played around with these types of conditions and that status may not work for you in this case. Try a scene instead. (unfortunately, I have had less than full success using z-wave devices as scene controllers but I am hoping it will work for you for the z-wave switch you are using.)

I find this curious, and would consider the possibility that this is more than a coincidence. What else is plugged in here? If you disconnect the loads from the appliancelincs, does communication improve? If you remove one of the appliancelincs, does communication with the other improve? If you temporarily move the appliancelincs to another location, does this improve communication? Do both happen to be plugged into, or near, a surge suppressor?

When you add the device to amazon Alexa, add the scene rather than adding the individual switch. Add it as Alexa category "light" just as you did when you added the zw switch. Also, remove the zw switch from Alexa so that she is not confused.

I think my old -994 has a 500 series board still in it. If I can figure out how to get it out, you can have it.

I have a vague recollection that some (if not all) versions of the ISY-994 had separate (from Insteon) z-wave backups or none. It has been a while since I did it, though. When I did my move from ISY-994, I recall having some of my z-wave devices moved but it was inconsistent and some were not added. I was not sure that it was any easier than just factory resetting them and adding them new to the new IoX device. If you use your old 994 for z-wave only (assuming it works and disabling the PLM connection) you would also loose any scene relationships you have established between Insteon and z-wave.

Your program looks to me as if it will meet your stated requirements. The only thing I notice that may cause an issue is in the last repeat (repeat 1 time) of the last program. (I assume that your garage door is configured to alway trigger from an ON command, which may not be true.) First, I am not sure but assume that those last few lines will be executed twice (literally repeated 1 time). Second, if so, you might be closing your door, then opening the door 30 seconds later.

One thing that I have noticed about z-wave switches on IoX is that most that I have tried do not trigger "control" (is switched on) conditions. I have found them also not to work well for me as scene controllers. (Because of this, I have tended not to use z-wave switches in locations where they would be conditions in my programs.) They seem to trigger "status" conditions, however. So, your program you might try something like: if 'switch' status is on then do something

My routine triggered by a variable is not working, based upon a manual change of value from 0 to 1 to 0. Alexa says that this "sensor" has been inactive for 15 days. I did not see any change in Alexa status from manually changing the values to the variable. On the other hand, routines triggered by door sensors seem to be working. I am on ISY 5.8.3 and the "Optimized" skill. Update: and now, a couple hours later, the variable changes, Alexa sees the change, and triggers the routine.

I just added the four-pack of Govee spot lights. Everything seems to work well, though color temperature is not an option from the Admin Console, One thing I noticed in the Govee app settings: an option for "LAN Control". Based upon the description, this should be toggled on for local control through the API to work.

I think the hardest thing to wrap one’s head around in this situation is that you will have eight controllers (two keypads time four buttons) and all eight need to separately have responder levels defined, and that some responder levels will need to be zero (responder turn off when contoller turns on). For example, define a scene with nine devices, (eight keypad buttons as controllers and the fanlinc as responder). You will need to select each of the controllers within the scene and separately set the response levels for the other eight devices. You need to do that eight times, plus set the responder levels for the whole scene. This approach should work well if your goal is limited to controlling fans only via keypad buttons. if you desire to control the fans externally, such as via a program or alexa, using four separate scenes (for off, low, med, and high) can give you a bit more flexibility.

Unfortunately, I don't have an example but I am with apostolakisl. I cannot envision why this cannot be done. The only thing I want to mention is that I have done fan control with a single scene and with four scenes. Both work for me. Setting these scenes up definitely takes some attention to detail.

Portal is required for alexa and google, home, I believe. It may also simplify connection to ud mobile app and remote access. I donkt recall that it had a funtion regarding node servers. Given what you have described, I don’t think you need a portal subscription.

This is my experience as well. UPS will mess with insteon signals.

I have one indoor and one outdoor YoLink motion sensor. They work great as program triggers so far. While I have had less success with using z-wave motion sensors (or most other z-wave devices) as scene controllers, the YoLink motion sensor seems to be just fine as scene controller. While not quite immediate as with all Insteon scenes, it is still pretty quick when using as a scene controller. The motion sensor appears to have a temperature node but I have not tried using it in any program.

That device slipped past my attention. I am sure it is good as well. I am trying one inside and one outside motion sensor. I intent to mount the indoor sensor on the ceiling. My interest (besides the "all on" problem) is coverage area and sensitivity compared to the Insteon and zwave motion sensors I have tried. I will also be interested in determining how the YoLink sensors behave in programs based on "control" and "status" conditions.

After I saw this thread, I looked harder at the range of devices available from YoLink and also decided to take the plunge. The only trouble I had was trying to "copy" the various credentials from a phone app to a computer screen. It is, apparently, easy to get a character wrong. Initial device was the power strip and was happy to be able control each of the four outlets separately, along with the USB ports. Anyhow, all seems to work well and I am going to try some motion sensors and see how well they trigger some of my motion programs. I continue to get the dreaded "all on" problem and tend to blame the Insteon motion sensors for this. I will replace a few of them with YoLinks and hope to reduce the house lighting up at the wrong time.

I am not sure that I fully understand the problem here (I dont use HA). regardless….. Mutually exclusive relationships are only enforced when manually controlling a keypad. These will not be enforced when commoanding a button via a scene or via the admin panel, or via a program. given this, I would not use the mutually exclusive relationship to achieve th desired results. Wihtin the scene for each button, add the other buttons that you want to turn off, as responders. For thos responder buttons, set the ON level to “off”. Once set, when you turn on a scene, regardless of method, the responder buttons will turn off.

I know that one can create an Alexa routine to run an IoX program (or turn off/on switches, etc). I have added TVs (unfortunately I do not have any compatible Samsung TVs) to Alexa and find that that Alexa can control them. To do this, IIRC, add an ISY program to Alexa. When Alexa tries to turn the device (program) on the program THEN path will run. Turning the device off will cause the ELSE path to run. Alexa routines can have multiple actions, including turning on/off TVs.

FWIW, my andoid has been solid geofencing through ud mobile. Wife’s iphone has had some misses.

I have many scenes havin insteon controllers with zwave responders so, yes, I expect it should work for you.. (Having zwave controlers with insteon responders is a different story.) it sounds to me as if you have correctly identified the failure of IoX to respond to keypad button presses as the problem. Of course, the fun part is figuring out why that is the case. Since you have restored the keypad, I would tend to minimize the possibility that corrupted link records are the problem. Is it possible that you are having communication problems between the keypad and the PLM?