Drivers and Effects defaults v0.5.7 -> v0.5.8

v0.5.7 -> v0.5.8

Server
=====
- esp32-s3: USB_MODE=1
- Drivers and Effects: set defaultNodeName
- Control: refactor loop
- NodeManager: add defaultNodeName
- Physical layer: add indexP for pass2 - WIP
- Virtual layer: use indexP in addLight

Author: ewowi

CHANGELOG.md

@@ -241,7 +241,7 @@ Add the following `build_flags` and adjust to your app, if needed:
 ```ini
     -D BUILD_TARGET=\"$PIOENV\"
     -D APP_NAME=\"ESP32-Sveltekit\" ; Must only contain characters from [a-zA-Z0-9-_] as this is converted into a filename
-    -D APP_VERSION=\"0.5.7.1\" ; semver compatible version string
+    -D APP_VERSION=\"0.5.8\" ; semver compatible version string
     -D EMBED_WWW
 ```
 

docs/moonbase/module/drivers.md

@@ -1,7 +1,5 @@
 # Drivers module
 
-🆕 (in release v0.5.7 Virtual and physical layers modules are still in one module called editor)
-
 <img width="396" alt="image" src="https://github.com/user-attachments/assets/965dd352-d7af-42a1-a72d-43da3b32a252" />
 
 The Drivers module allows you to define a **layout** (e.g. a panel 16x16), to drive LEDs (e.g. FastLED driver) and to run **supporting processes** (e.g. audiosync to run sound reactive effects and Art-Net to send light channels to an Art-Net controller).
@@ -18,7 +16,7 @@ Typically a node will define a modifier (💎) or a supporting process (☸️)
         * If a 1D strip is longer, you can address more LEDs by pretending it is a 2D fixture, e.g. 32x32 to address a strip of 1024 LEDs. 
         * In the future we might look at redefining Coord3D where width is 12 bytes, height is 7 bytes and depth is 5 bytes allowing for max 4096 x 128 x 32 ...
     * Currently **pins** are by default driven by FastLED.show. FastLED needs all LEDs specifications be defined at compile time, e.g. LED type, color order, etc. Normally also the pin(s) need to be defined beforehand but all pins are predefined in the code to avoid this (at a cost of larger firmware). As we want to be able to define all LED specs in the UI instead of during compile, we need to see how / if this can be done.
-    * 🆕 **Multiple layout nodes** can be defined which will execute one after the other
+    * **Multiple layout nodes** can be defined which will execute one after the other
     * In the future, instead of pins, also **IP addresses and universes** can be specified to support sending lights data to Art-Net devices - e.g. [Pknight Art-Net DMX 512](https://s.click.aliexpress.com/e/_ExQK8Dc) to control DMX lights or [Art-Net LED controller](https://s.click.aliexpress.com/e/_Ex9uaOk) to control LED strips or panels over local network. Currently this is handled by the [Art-Net Node](https://moonmodules.org/MoonLight/moonlight/nodes/#art-net/).
     * Alternatively Moonlight supports 2 other drivers: [Physical Driver](https://github.com/hpwit/I2SClocklessLedDriver) and [Virtual Driver](https://github.com/ewowi/I2SClocklessVirtualLedDriver). Firmware ending with PD or VD will have this enabled. Code has been included but not tested yet (tested in StarLight), this is planned for June/July. 
         * The physical driver is an alternative to the FastLED driver and does not need LED specifications defined at compile time, all can be controlled via UI. 
@@ -35,7 +33,7 @@ Typically a node will define a modifier (💎) or a supporting process (☸️)
 ## Layout 🚥 Nodes
 🚧
 
-### PanelLayout 🚥 🆕
+### PanelLayout 🚥
 
 * Defines a 2D panel with width and height
 * Controls:
@@ -45,7 +43,7 @@ Typically a node will define a modifier (💎) or a supporting process (☸️)
     * snake: is the first axis in snake / serpentine layout?
     * pin: to do add more pins
 
-### CubeLayout 🚥 🆕
+### CubeLayout 🚥
 
 * Panel layout + depth
 * Controls:

docs/moonbase/module/effects.md

@@ -1,7 +1,5 @@
 # Effects module
 
-🆕 (in release v0.5.7 Effects and drivers modules are still combined in one module called editor)
-
 <img width="396" alt="image" src="https://github.com/user-attachments/assets/965dd352-d7af-42a1-a72d-43da3b32a252" />
 
 The Effects module allows you to define the tasks to run an **effect** (e.g. bouncing balls), to **modify** the effect (e.g mirror).
@@ -39,7 +37,7 @@ Precompiled effects can be found in [effects](https://github.com/MoonModules/Moo
 * Controls: Red, Green, Blue, Brightness
 * Usage: Can be used as background to other effects, order it before other effects
 
-### Scrolling text 🔥 🆕
+### Scrolling text 🔥
 
 * WIP: Currently shows system info on leds. You need at least 16*6 pixels for that (Panel 16x16 recommended). Later custom texts will be possible
 * Controls:

docs/moonbase/module/pins.md

@@ -2,7 +2,7 @@
 
 Shows info in gpio pins.
 
-🆕 🚧
+🚧
 
 * Per pin:
     * GPIO = gpio_num;

docs/moonlight/overview.md

@@ -22,11 +22,11 @@ Note: These docs are updated also after a release has been published preparing f
     * Execute a live script
 
     This list is dynamic and will change over time if crash reasons change.
-    Clicking on the icon allows you to restart (🆕)
+    Clicking on the icon allows you to restart
 
-* **Restart needed**: 🆕 e.g. when drivers are changed, a restart might be needed, see 🔄 in the statusbar. Clicking on the icon allows you to restart (🆕)- 🚧
+* **Restart needed**: e.g. when drivers are changed, a restart might be needed, see 🔄 in the statusbar. Clicking on the icon allows you to restart ()- 🚧
 
-* **Save** and **Cancel** 🆕 Changes are only saved after pressing the save button 💾. To undo changes, press the cancel button 🚫.
+* **Save** and **Cancel** Changes are only saved after pressing the save button 💾. To undo changes, press the cancel button 🚫.
 
 * **Wifi**: See ESP32-Sveltekit
 

docs/statefulservice.md

@@ -601,7 +601,7 @@ By enabling `FT_DOWNLOAD_FIRMWARE=1` in [features.ini](https://github.com/theeli
 ```ini
     -D BUILD_TARGET="$PIOENV"
     -D APP_NAME=\"ESP32-Sveltekit\" ; Must only contain characters from [a-zA-Z0-9-_] as this is converted into a filename
-    -D APP_VERSION=\"0.5.7.1\" ; semver compatible version string
+    -D APP_VERSION=\"0.5.8\" ; semver compatible version string
 ```
 
 A build script copies the firmware binary files for all build environment to `build/firmware`. It renames them into `{APP_NAME}_{$PIOENV}_{APP_VERSION}.bin`. It also creates a MD5 checksum file for verification during the OTA process. These files can be used as attachment on the GitHub release pages.

docs/structure.md

@@ -98,7 +98,7 @@ Also you must make use of couple build flags in [platformio.ini](https://github.
 ```ini
     -D BUILD_TARGET=\"$PIOENV\"
     -D APP_NAME=\"ESP32-Sveltekit\" ; Must only contain characters from [a-zA-Z0-9-_] as this is converted into a filename
-    -D APP_VERSION=\"0.5.7.1\" ; semver compatible version string
+    -D APP_VERSION=\"0.5.8\" ; semver compatible version string
 ```
 
 Out of these flags the [rename_fw.py](https://github.com/theelims/ESP32-sveltekit/blob/main/scripts/rename_fw.py) script will copy and rename the firmware binary to `/build/firmware/{APP_NAME}_{$PIOENV}_{APP_VERSION}.bin`. In addition it will also create a corresponding MD5 checksum file. These files are ready to be uploaded to the Github release page without any further changes. The frontend searches for the firmware binary which matches the build environment and uses this as the update link. This allows you to serve different build targets (e.g. different boards) from the same release page.

docs/system/status.md

@@ -3,7 +3,7 @@
 <img width="350" src="https://github.com/user-attachments/assets/9e27494a-284a-4d9e-ba55-c52786cb0374" />
 
 * 🌙 **Performance**: loops per second: nr of times main loop is executed
-* 🌙 **Safe Mode** 🆕: After a crash, the device will start in Safe Mode disabling possible causes of crashes. See also [MoonLight](https://moonmodules.org/MoonLight/moonlight/overview/). In case of safe mode, the statusbar will show a shield: 🛡️. Try to find the reason of the crash and correct and restart the device. If no crash, it will go out of safe mode.
+* 🌙 **Safe Mode**: After a crash, the device will start in Safe Mode disabling possible causes of crashes. See also [MoonLight](https://moonmodules.org/MoonLight/moonlight/overview/). In case of safe mode, the statusbar will show a shield: 🛡️. Try to find the reason of the crash and correct and restart the device. If no crash, it will go out of safe mode.
 * 🌙 **Firmware Target**: Which firmware has been installed, see [MoonLight Web Installer](https://raw.githack.com/MoonModules/MoonLight/refs/heads/main/firmware/installer/index.html)
 * 🌙 **Firmware Date**: What is the date the firmware is created (format YYYYMMDDHH)
 

docs/wifi/sta.md

@@ -2,7 +2,7 @@
 
 <img width="350" src="https://github.com/user-attachments/assets/0be091ab-1bd6-46c9-a766-e8b6b4cbb616" />
 
-* **WiFi TX Power** 🆕🌙: WiFi transmit power can be set to optimize WiFi behavior. Some boards are known to work better by setting transmit power to 8.5 dBM (So called LOLIN_WIFI_FIX).
+* **WiFi TX Power** 🌙: WiFi transmit power can be set to optimize WiFi behavior. Some boards are known to work better by setting transmit power to 8.5 dBM (So called LOLIN_WIFI_FIX).
     * Default is typically 20 dBm (100mW) - the maximum allowed
     * Common recommended settings:
 	    * For most indoor applications: 15-17 dBm

firmware/esp32-s3.ini

@@ -5,8 +5,8 @@ build_flags =
   ${livescripts.build_flags}
   ${HP_ALL_DRIVERS.build_flags}
   -D CONFIG_IDF_TARGET_ESP32S3=1
-  ; -D ARDUINO_USB_MODE=1 ; which USB device classes are enabled on your ESP32 at boot. default 1 in board definition (serial only)
-  ; -D ARDUINO_USB_CDC_ON_BOOT=1 ;Communications Device Class: controls whether the ESP32's USB serial port is enabled automatically at boot, default 1 in board definition
+  -D ARDUINO_USB_MODE=1 ; which USB device classes are enabled on your ESP32 at boot. default 1 in board definition (serial only)
+  -D ARDUINO_USB_CDC_ON_BOOT=1 ;Communications Device Class: controls whether the ESP32's USB serial port is enabled automatically at boot, default 1 in board definition
   -D ARDUINO_USB_MSC_ON_BOOT=0 ;Mass Storage Class, disable
   -D ARDUINO_USB_DFU_ON_BOOT=0 ;download firmware update, disable
   ; -D ML_LIVE_MAPPING