The pattern field of backlight plugin commands is exported as wrong file type.

[taylorlm88]

When a backlight command is called to set the power of a colored LED, the pattern input is optional. If it is provided, however, it should be exported as a string. Right now it is exported to the yaml file as an integer. The yaml file is getting pattern: 1010 when it should be getting pattern: "1010"

[mbreiser]

Fixed in commit c4f2279 (v0.8.1).

Root cause: Both param input handlers (Commands tab line ~2270, Table tab line ~2720) used Number(val) to try numeric coercion on all param values. Since Number("1010") returns 1010 (not NaN), the string "1010" was silently converted to the integer 1010, which was then exported as a bare number in YAML.

Fix: The input handlers now consult the plugin registry schema via getCommandParams(). If the schema declares type: 'string' for a param (as it does for the backlight pattern field), the value is kept as a string. Numeric coercion only applies to params with numeric types.