stusviews

I found some way to offend it, some pleasurable responses from it, as well

As with the transition from the original skill to v2, everything you've accomplished will transfer to V3, so yes, continue to build.

What's the result if you eliminate the "wait" command? How do you set the variable to 1?

If "Resource '(MED) TiVo - Commercial Skip'" changes the variable to 1, then after the wait statement the program will re-run. That's just the way state variable work.

If you have an understanding of the difference between ON and FAST ON (and OFF and FAST OFF), then an understanding of the code and log isn't needed--unless something doesn't work as expected. At that point the code shown in the log will help.

You are using a variable in the IF section of you program. Unless you invoke Izzy (voice), the portal does not even know that the IF section exists. How are you running the program? In other words, what changes the variable/runs the program?

I'm not having that experience with my Echo devices except that responses to commands usually precedes the acknowledgement, so it's actually faster now--mostly. I wonder why your system is so slow and why the Alexa app goes away at all.

The portal does not run a program at all unless you evoke Izzy. The portal runs If when you state On and Else when you state Off. A state variable will run the program automatically when it evaluates as true, independently of the portal. An integer variable will not.

When you change the variable to 1 (the ISY portal modifies a state variable in this case “hb.Commercial_Skip.Switch.On” is set to 1), the IF evaluates to true and runs the program during the Wait statement. If you don't want the program to run automatically whenever the variable is set to 1, the use an Integer variable instead. Another choice is to use two programs.

How are you running the program using your voice? Normally On and Off run THEN and ELSE, respectively. It IF section is not tested unless you invoke Izzy. What changes the variable to 1. Are you using a state or integer variable?

Benoit, I'm relieved. All my groups have only one load device so I can set the brightness by voice. Any scene with multiple loads uses scenes or programs as you recommend. Thanks for the info. Respectfully, Stu

Post the problem program (right click on the program name, select Copy to Clipboard).

Correct again. I have two Dine Out buttons, one at the side door and one at the front. Both buttons are in the same scene.

As a trigger, Control sends a signal each time the I/O Linc sends a signal, even if the signal is the same. Status will send a signal only if the state of the device changes. For most devices (not the I/O Linc), Control requires that the device itself (e.g., SwitchLinc, KeypadlLnc) sends the signal. Status changes can be initiated remotely (e.g., scene, program) or manually.

That's correct. Toggle alternates between on and off on each subsequent push.

Setting a button to non-Toggle off sends an off only and cannot be used to turn anything on at all (without a program). Setting the button to non-toggle On can be used to turn device on or off, but the button will remain lit unless you use a program to turn the button's LED off. Turning the button off using a programwill do jut that, nothing else. kingwr: The 6 (or 5) button mode has the top (large) button as On and the bottom (large) button as off. The other 4 buttons are labelled A, B, C and D. In 8-button mode, the top left button controls the load (if any) and is labelled A. The remaining secondary buttons are B, C, D, E, F, G and H.

First a bit of clarity: The 6-button Keypad is a 5-scene controller. The top and bottom buttons serve as On and Off, respectively, for the same scene. Various revisions of the same keypad are shown sometimes as a 5-button and sometimes as a 6-button. They both refer to the same keypad. The top (On) button will always be illuminated when pressed. the bottom (Off) button will illuminate when pressed, but can be set to not illuminate when pressed. The top button illumination can't be changed (except for brightness level which affects all buttons). If you want a secondary button to turn some devices off and others on, then the button should be set to non-toggle On. The button will always remain lit--unless you create a separate scene with the button as the only member and control that scene using a program. Gouldc: an image of the scene would help. Also cut and paste your program (right click on the program name, select copy to Clipboard).

The images you posted are a carry-over from earlier versions. They have no purpose other than notations. The "spoken" field has no other purpose. It's not used for anything.

I got the Mimo2+ to work with 4.6.1 and 4.6.2, but it provided only one input and output, so I opted for the less costly MimoLite.

So, you added a device to the portal, gave it a spoken and then tried discover in the Alexa app and nothing appeared?

"Alexa, going to work," doesn't seem like a valid command. Alexa understands On, Off and sometimes Open and Close, but not "going."

Amazon Echo skills are independent of the ISY portal which uses yet a different Amazon skill. You need to add ISY devices, scenes and/or programs to the ISY portal before discovering them.

I may not have been clear. Each ISY scene controller accounts for two links, each scene responder as one. Reusing scenes as part of a program does not increase the number of links. But, controlling a device (or button) via a program as opposed to a scene does not use a link for each device or button at all.

Hmm, using a program to control scenes with everything in the scene as a responder, does not reduce the count of links being used by the ISY. That's because just creating a scene uses two links for each controller and one for each responder. In fact, each device, button, scene and/or folder uses a node (I'm nor really clear on the difference between a link and a node in this context other than a link involve devices themselves, but not scenes nor folders). Using a program to control individual devices instead of scenes does reduce the link (nor node?) count. The ISY has a limit for the number of nodes (links?) that's apart from the limit for the number of programs.

Removing skills won't help. Linking and re-linking won't help. The Alexa app remembers everything. Try a "Forget All," again. Wait until the process completes. Ensure that all devices are, in fact, gone. You should also uncheck any grouped devices. Too, forget all scenes (Alexa scenes are not the same as Insteon scenes). Wait a minute or two, then use you voice to tell the app to discover devices.