UI Optimization - Creating new LED-Instances

[Lord-Grey]

Feature request

As a user, I would like to be guided through the set-up of a new LED-instance that way that I am presented valid configuration options rather that I define them myself.

What problem does this feature solve?

Presenting valid configuration elements to a user will mitigate the risk of misconfiguration and not working setups. In addition, the user is presented with platform specific elements rather than default values deemed for another platform. e.g. serial ports are named differently between Linux and Windows based platforms.

What does the proposed API look like?

N/A

How should this be implemented in your opinion?

Envisioned sequence of activities:

1. User selects to create new LED-instance (Clicks "Big +")
2. Select LED-device type (e.g. WLED, Philips Hue, APA102,...)
3. Select LED-device Sub-type/model (e.g. Philips Hue vs. Entertain, Cololight Pro vs. Stripe)
4. Configure Security Details (e.g. Tokens, Client-IDs, etc.)
5. Get Device Properties (e.g #Hardware-LEDs, available device ports [COM1,COM6])
6. Allow to test/identify the device, (if provided by device)
7. Capture/Refine #Hardware-LEDs, if not automatically resolved
8. Configure Color Order (BGR, RGB,...)
9. Allow to configure device specifics, e.g. a. Baud Rate b. ... c. Latch Time d. Rewrite Time
10. Define the layout considering that #LEDs must not exceed ‘HardwareLEDs”, options a. Simple Layout, map device to predefined areas (like for Hue, Yeelight) b. Layout Wizard, as per today c. Layout Wizard, free drawing
11. Propose an instance name for the setup (e.g. Type.Subtype.#), allow to overwrite naming
12. Save instance incl. layout under given name
13. Start instance

To find devices, get device properties or identify them, existing JS-functions interacting with the hyperion backend can be leveraged.

Are you willing to work on this yourself?