Feature Request - Toggle State (vs on, or off)

Community Playground General Discussions
1

Would it be possible to have a command which is “toggle state”?

For example, right now, a command can turn a light ON or OFF.

However, what I want is essentially a “notification”.
ie. If the back door is opened, toggle for 5s, the light in the living room, then resume previous state.

So if the light was ON, and the back door was opened, the light will turn OFF for 5s, then back ON
If the light was OFF, and the back door was opened, the light will turn ON for 5s, then back OFF.

2

I wholeheartedly second this motion for adding a “TOGGLE” command to Vera. (In fact, I’d love it if we could “TOGGLE” a device more than 1 time per command. e.g. “TOGGLE” 5 “Times”)

This way, we could make Vera flash a lamp, for instance, when someone rings the doorbell (a valuable aid for the heaing impaired!!). Or flash the porch lights when someone enters the wrong deadbolt user code several times in a row. And so on…

3

[quote=“ubiquityman, post:1, topic:164517”]Would it be possible to have a command which is “toggle state”?

For example, right now, a command can turn a light ON or OFF.

However, what I want is essentially a “notification”.
ie. If the back door is opened, toggle for 5s, the light in the living room, then resume previous state.

So if the light was ON, and the back door was opened, the light will turn OFF for 5s, then back ON
If the light was OFF, and the back door was opened, the light will turn ON for 5s, then back OFF.[/quote]

Sorry if I’m missing something, but why can’t you use events and scenes?
There were options to do something for X sec, then get into previous state…

4

The only aspect you’re missing, 325xi, is that users may want Vera to alternate ON-OFF several times in succession, or switch a device to the opposite state without forknowledge of its current state.

A scene/macro cannot currently be instructed to “turn the lamp OFF if it’s ON, but turn it ON if it’s OFF”. Does that make more sense?

5

It’s in the Scene definition that you want it. Currently the “action” part, for something like a Light, can only be “ON” or “OFF” - likely as these map to the Native ZWave command for that type of device.

The request here is to provide a convenience to add “TOGGLE” to this list, so you dont need to jump into Luup-scripting to do that (even if the option simply executes the equivalent Luup behind the scenes).

In effect, you could [declaratively] use this to get the same effect that Leviton’s “Scene Controllers” do by default. “Press once to turn on, Press again to Turn off”… something you lose once you Method 2 the install.

6

I think this is definately needed but I’m thinking it would be better to add conditional programming and that would provide this plus other options. If we had a simple way to setup if x then y programming we could have a scene toggle on when the button is pressed and it was off and so on. It would also be handy to have conditional programming so for example I could have an event trigger if some conditions were true or false.