Jump to content

Open/Close Routine workaround


stusviews

Recommended Posts

More than a few of us are concerned that the highly touted ISY v.3 skill doesn't support Off for both scenes and programs.

 

A workaround, probably discovered by other but not posted, is to use a program to turn the scene off (if it's a scene) and a second program with the Else statements in the Then section (if it's a program). You can leave the original program intact and delete all the workaround programs when and if a solution occurs.

Link to comment

I haven't noticed any difference between v2 and v3 so I dont understand the fuss r any of the benefits either. Multiple rooms still require multiple accounts and no accounts links can be changed that I can find.

 

I don't believe I use any scenes directly but only devices and programs. Many programs control scenes, some via variable value changes. 

Program Offs work just fine in the "Else" sections so that the vocal syntax works out properly

eg:

.....Alexa..turn off ALL LIGHTS.

 

works fine in the program Else section, turning on my Off scene.

Link to comment

More than a few of us are concerned that the highly touted ISY v.3 skill doesn't support Off for both scenes and programs.

 

A workaround, probably discovered by other but not posted, is to use a program to turn the scene off (if it's a scene) and a second program with the Else statements in the Then section (if it's a program). You can leave the original program intact and delete all the workaround programs when and if a solution occurs.

 

I haven't seen any projected ETA for Amazon to fix the problem so this is the workaround I'm using too.

Link to comment

More than a few of us are concerned that the highly touted ISY v.3 skill doesn't support Off for both scenes and programs.

 

A workaround, probably discovered by other but not posted, is to use a program to turn the scene off (if it's a scene) and a second program with the Else statements in the Then section (if it's a program). You can leave the original program intact and delete all the workaround programs when and if a solution occurs.

 

I'm reading you 5x5. I went back to v.2 for this reason and the ridiculous auto thermostat logic. As far as this routine issue goes, we are assuming it is a bug, but who knows with Amazon? I can't see any solution either, except to recreate separate programs using "then" statements only to control your most critical open/close items. This is what I did before reverting to v.2. I did not want to spend the time to recreate all the programs initially, just to hedge my bet that this is a bug and will be corrected eventually.

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...