oberkc

True, but I was just responding to your statement that you did not have the secret decoder ring. I tend to ascribe this problem to the load attached to the Insteon device. When off: interference. When on: interference. If possible, temporarily disconnect the load (unscrew the light bulb?) and see if the Insteon devices can now be turned on AND off. I wonder if the program changes were not initially saved.

Red bar on program indicates that the program last ran false. Green bar means last ran true. Solid red means it is currently running (usually indicating a wait statement within) false and solid green means currently running true.

Unless one has ADD

One of the things I understand about the IoX and Insteon is that direct commands to devices (as opposed to scene commands) involve the command followed by some type of acknowledgement from the responding device. The command is repeated a few times if no acknowledgement is received. These types of commands tend to be more reliable, in my experience. Scene commands, on the other hand, do not have the acknowledgement and IoX simply assumes the responder device reacted accordingly. I find large scenes can be less reliable in response. I have devices that respond to queries and direct commands near 100% but respond to scene commands less reliably. I have a couple of devices at my house that are particularly prone to this problem. Communication problem? Yes. I have also found that replacing the suspect device (some of mine are probably starting to push 15 years old) usually solves the problem which makes me think that Insteon communication performance can fade over time without completely failing. Of course, the devices of the electrical system in my house have evolved over that same time and I am sure that the electrical environment (noise, attenuation) has evolved along with it. The only reason I bring this up is that I it is not uncommon at my house to find status mismatches between IoX and various devices but without showing "unable to communicate".

I think you will find that a single scene, with both as controllers, will work fine. Controllers are, by definition, also responders. Remotelincs, if I recall, have certain limitations due to being battery devices. I do not believe that they are constantly listening for signals (to save battery life) and may not respond to scene commands.

Are you trying to solve a particular problem or add a new capability?

I tend to agree with Geddy. I recall a time where z-wave was a big factor, and it may be that v5 is where z-wave is backed up and, thus, restorable on EISY when you make the transition. If you don't have z-wave, or if you have minimal z-wave, it could be more work than it is worth for you if you are otherwise happy with where you are and staying there until you upgrade.

I am considering trying this. I have had a tablet in the past, prior to UD Mobile. In fact, I already have a couple of tablets lined up for this. I think it would work very well for the switches, but I was hoping for a clock and camera feeds (have never gotten my cameras to work on UD Mobile.). Sometimes, I just don't know what I like until I try things.

That is a good summary. I would say that it is an echo device configured for wall mount and touch interface, specialized for home automation. The visual user interface seems to be the big difference. I have always wanted a touch screen interface for my home automation and thought this might be it. I would like something like an eight button keypad but touch screen based, that I can configure the labels and colors and icons. The main screen on the hub can also include some cameras and other stuff, but the jury is still out whether this is something I will like. It is programmed mostly through the Alexa mobile app, but widgets can be added and configured directly through the hub screen, itself. I am thinking that a tablet with UD mobile, pinned, might also work. I have a few around and may try it as well.

I already have the ability to open and close garage doors by Alexa voice commands, keypad buttons, UD mobile. I am attempting, however, to use an echo HUB and create a favorite that I can TOUCH to activate the doors and to simultaneously show status (basically trying to create a keypad button on the Alexa favorite screen). It is a little different than voice commands. Unfortunately, I am running into limitations with Alexa that is making this an interesting problem to solve. Also, unfortunately, I am fearing that I am not getting consistent response from the virtual switch to Alexa and Alexa seems to be missing some changes-of-state with the virtual switch.

I must admit that I have never had much use for setting a variable (a numerical representation of the switch status) to trigger a program when I already have the switch status (on/off) directly available that could be used without need to translate to a number. It seems like a lot of unneeded complication. Besides, I have not even stated my application. But since you ask, my interest is in having an Alexa favorite show the status of my garage doors (open/close or on/off) and, when I press the same Alexa favorite, it would trigger the door. I have a pretty good idea how to accomplish this, but was hoping to avoid unnecessary programs.

Thank you. I was looking for a simple answer to a simple question. I was hoping that there was a trick I was missing that would allow a virtual switch to be controller in a scene.

May I take this as your position that the virtual button cannot be a scene controller?

The way to do this with Insteon does not require a program. I cannot say about whether RatGDO would work the same. (Does RatGDO plug in have relay and sensor nodes?). With Insteon, create two scenes. One with the keypad button as controller and relay as responder. The second scene would have the sensor as controller and same keypad button as responder (set up so that the sensor is ON when the door is open). Configure the keypad button as non-toggle (on) mode. Configure the IOLinc to accept ON commands to trigger a momentary closure of the contact. Hopefully, RatGDO will work the same.

I am currently (may change) not using any programs. I am simply trying to use the virtual switch in a scene, as controller. I have tried controlling the virtual switch directly from the admin panel, and in response to an Alexa echo device. The virtual switch changes status, but the scene in which it is added as a controller device remains untriggered. I hope that there is some step that I am missing, but suspect this is not possible.