Updated Presets (markdown)

This commit is contained in:
Aircoookie 2020-11-16 00:20:42 +01:00
parent 72a5fc46fe
commit 43fe30ae46
1 changed files with 7 additions and 6 deletions

View File

@ -34,26 +34,27 @@ This is enabled by default when adding a new preset and disabled when editing an
When enabled, it will write the current segment config, including all colors and effect, to the preset.
When disabled, it will instead give you a textfield to enter a custom API command or show you the command currently saved.
*Include brightness*
*Include brightness*
If disabled, the brightness value is not included in the preset. This can be useful e.g. when you want to control the brightness manually and want the preset to only set the effect.
*Save segment bounds*
*Save segment bounds*
This is an important one. Make sure it is enabled for your boot preset, so that your segment config is properly restored on boot!
When disabled, the segment start and stop LEDs are not included in the preset. This can be useful if you plan to make changes to your segment setup and don't want your presets to always reset it to the point it was when the preset was saved.
*API command*
*API command*
This accepts any HTTP or JSON API command! (only visible if the current state checkbox is unchecked)
It replaces the previous macro functionality.
If you know your JSON, you can even create playlists of other presets!
*Save to ID*
*Save to ID*
This is the ID the preset will be saved to.
When creating a new preset, you likely won't have to change it as the lowest unused ID will be chosen automatically.
If you change the ID on an existing preset and save, you can copy it to the new ID - change the name though.
*Save and Delete buttons*
*Save and Delete buttons*
Now these are self-explanatory, but I said I'd cover each point :)
*ID*
*ID*
This is the number you'll want to use to apply this preset from a timed macro or automation!
#### A note on performance