Calling preset 0 on 0.13.3 turns LED's off?

I noticed that if I call preset 0 using a button on 0.13.3 the LED’s turn off? Is this a bug?

Zero means default behavior. There is no preset 0. :wink:

yes, that is default behaviour

For instance, If I want to trigger a preset on the rising edge of a switch button but not the falling edge of a switch button what should I put in the on → off text box?

I have been putting a preset that doesn’t exist but I’m not sure if this is good practice.

Switch and (push) button are different. :wink: Switch is maintained so you would use on->off or off->on.

0 would be default action on button 0, but nothing on others. -1 would be safe for all for no action.

1 Like

It does not allow a -1 for switch button action.

Good catch.

1 Like

You can disable a button if you do not want any action.
If you want only long-press, assign a preset that does nothing to a short press.

1 Like

Is that better than calling a preset that doesn’t exist?

Calling preset that does not exist produces an error (visible in UI) and/or may have undefined behaviour.

1 Like

So if I create a preset but the API command box is just empty, no error will happen, but no change will happen to the LED’s, correct?

Yes. You may add "v":true in it for clarity.

What does that do?

Verbose output.