Beta

.github/workflows/main.yml

@@ -5,6 +5,10 @@ on:
     branches:
       - main
       - develop
+  pull_request:
+    branches:
+      - main
+      - develop
 
 jobs:
   build:
@@ -16,25 +20,54 @@ jobs:
           - esp32-s3-mini
 
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v6
 
-      - uses: actions/cache@v3
+      - uses: actions/cache@v5
         with:
           path: |
             ~/.cache/pip
             ~/.platformio/.cache
-          key: ${{ runner.os }}-pio
-      - uses: actions/setup-node@v4.1.0
+          key: ${{ runner.os }}-python-3.12-pio-${{ hashFiles('platformio.ini', 'miniweb/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-python-3.12-pio-
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
 
-      - uses: actions/setup-python@v4
+      - uses: actions/setup-python@v6
         with:
-          python-version: "3.11"
+          python-version: "3.12"
 
       - name: Build webUI
-        run: cd miniweb && npm i && npm run build;
+        run: cd miniweb && npm ci && npm run build
 
       - name: Install PlatformIO Core
-        run: pip install --upgrade platformio
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install "platformio==6.1.19"
+
+      - name: Prime pioarduino Python environment
+        run: |
+          python -m venv ~/.platformio/penv
+          ~/.platformio/penv/bin/python -m pip install --upgrade pip
+          ~/.platformio/penv/bin/python -m pip install \
+            "uv>=0.1.0" \
+            "https://github.com/pioarduino/platformio-core/archive/refs/tags/v6.1.19.zip" \
+            "littlefs-python>=0.16.0" \
+            "fatfs-ng>=0.1.14" \
+            "pyyaml>=6.0.2" \
+            "rich-click>=1.8.6" \
+            "zopfli>=0.2.2" \
+            "intelhex>=2.3.0" \
+            "rich>=14.0.0" \
+            "urllib3<2" \
+            "cryptography>=45.0.3" \
+            "certifi>=2025.8.3" \
+            "ecdsa>=0.19.1" \
+            "bitstring>=4.3.1" \
+            "reedsolo>=1.5.3,<1.8" \
+            "esp-idf-size>=2.0.0" \
+            "esp-coredump>=1.14.0"
 
       - name: Build PlatformIO Project
         run: |
@@ -47,15 +80,16 @@ jobs:
           name: firmware-${{ matrix.board }}
           path: |
             .pio/build/${{ matrix.board }}/firmware.bin
-            .pio/build/${{ matrix.board }}/spiffs.bin
+            .pio/build/${{ matrix.board }}/littlefs.bin
 
   publish:
+    if: ${{ github.event_name == 'push' && github.repository == 'tadelv/yaeger' }}
     needs: build
     runs-on: ubuntu-latest
     permissions:
       contents: write
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v6
         with:
           fetch-depth: 0
 

.github/workflows/publish-firmware.yml

@@ -9,7 +9,7 @@ on:
 
 jobs:
   publish:
-    if: ${{ github.event.workflow_run.conclusion == 'success' }}
+    if: ${{ github.event.workflow_run.conclusion == 'success' && github.event.workflow_run.event == 'push' && github.event.workflow_run.repository.full_name == 'tadelv/yaeger' }}
     runs-on: ubuntu-latest
     permissions:
       contents: write
@@ -68,7 +68,7 @@ jobs:
           done
 
       - name: Check out repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v6
         with:
           fetch-depth: 0
 

.github/workflows/release-build.yml

@@ -11,7 +11,7 @@ jobs:
     outputs:
       matrix: ${{ steps.collect.outputs.matrix }}
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v6
 
       - name: Collect PlatformIO environments
         id: collect
@@ -43,26 +43,55 @@ jobs:
       matrix: ${{ fromJson(needs.determine-boards.outputs.matrix) }}
 
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v6
 
-      - uses: actions/cache@v3
+      - uses: actions/cache@v5
         with:
           path: |
             ~/.cache/pip
             ~/.platformio/.cache
-          key: ${{ runner.os }}-pio
+          key: ${{ runner.os }}-python-3.12-pio-${{ hashFiles('platformio.ini', 'miniweb/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-python-3.12-pio-
 
-      - uses: actions/setup-node@v4.1.0
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
 
-      - uses: actions/setup-python@v4
+      - uses: actions/setup-python@v6
         with:
-          python-version: "3.11"
+          python-version: "3.12"
 
       - name: Build webUI
-        run: cd miniweb && npm i && npm run build
+        run: cd miniweb && npm ci && npm run build
 
       - name: Install PlatformIO Core
-        run: pip install --upgrade platformio
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install "platformio==6.1.19"
+
+      - name: Prime pioarduino Python environment
+        run: |
+          python -m venv ~/.platformio/penv
+          ~/.platformio/penv/bin/python -m pip install --upgrade pip
+          ~/.platformio/penv/bin/python -m pip install \
+            "uv>=0.1.0" \
+            "https://github.com/pioarduino/platformio-core/archive/refs/tags/v6.1.19.zip" \
+            "littlefs-python>=0.16.0" \
+            "fatfs-ng>=0.1.14" \
+            "pyyaml>=6.0.2" \
+            "rich-click>=1.8.6" \
+            "zopfli>=0.2.2" \
+            "intelhex>=2.3.0" \
+            "rich>=14.0.0" \
+            "urllib3<2" \
+            "cryptography>=45.0.3" \
+            "certifi>=2025.8.3" \
+            "ecdsa>=0.19.1" \
+            "bitstring>=4.3.1" \
+            "reedsolo>=1.5.3,<1.8" \
+            "esp-idf-size>=2.0.0" \
+            "esp-coredump>=1.14.0"
 
       - name: Build PlatformIO Project
         run: |
@@ -73,7 +102,7 @@ jobs:
         run: |
           mkdir -p release/${{ matrix.board }}
           cp .pio/build/${{ matrix.board }}/firmware.bin release/${{ matrix.board }}/firmware.bin
-          cp .pio/build/${{ matrix.board }}/spiffs.bin release/${{ matrix.board }}/spiffs.bin
+          cp .pio/build/${{ matrix.board }}/littlefs.bin release/${{ matrix.board }}/littlefs.bin
 
       - name: Upload firmware artifacts
         uses: actions/upload-artifact@v4

README.md

@@ -58,12 +58,77 @@ You can also control Yaeger from its own web interface without an app. Just poin
 your home wifi, or `192.168.4.1` if Yaeger creates its own access point.
 ![yaeger webui](./assets/yaeger-webui.png)
 
+The web UI now includes a **Version & Network Info** section that shows the Web UI version/build timestamp and device firmware/network details (mode, SSID, IP, hostname) so you can quickly check when the currently loaded build was last updated.
+
+### Frontend status
+
+- `miniweb` (TypeScript + Vite) is the **only supported** web UI in this repository.
+- The old `webserver` Svelte/Rollup frontend and related legacy files have been removed.
+- Project scripts and firmware asset packaging target `miniweb`.
+
 #### Using Yaeger on the go
 
 If Yaeger can't connect to your preferred Wifi, it will create its own access point. Perfect for when out and about :grin:
 
 ## Build guide (WIP)
 
+## What changed in this fork
+
+If you are reviewing this fork before opening a PR against `tadelv/yaeger`, here is the practical summary:
+
+* `miniweb` is now the canonical frontend (TypeScript + Vite). Legacy `webserver` content is gone.
+* OTA uploads are now aligned with ElegantOTA (`/update`) and no longer depend on PlatformIO `espota`.
+* A one-command OTA flow (`ota_update_all.sh`) now updates both LittleFS web assets and firmware in one run.
+* OTA tooling is isolated in a local Python virtual environment (`.ota-venv`) to avoid polluting global Python installs.
+* GitHub Actions build flow now supports PR validation and avoids publish failures on forks/non-upstream repos.
+
+## Installation / update flows
+
+There are now two recommended paths depending on how you connect to your board:
+
+### 1) USB flash (first-time install or recovery)
+
+Use this when the device is connected over USB serial:
+
+```bash
+./build_and_flash.sh s3
+# or
+./build_and_flash.sh s3-mini
+```
+
+What it does:
+1. installs frontend dependencies with `npm ci`,
+2. builds `miniweb`,
+3. optionally erases flash,
+4. uploads LittleFS (`buildfs` + `uploadfs`),
+5. uploads firmware (`upload`).
+
+### 2) OTA update (already deployed device on network)
+
+Use this once the device is reachable over Wi-Fi and ElegantOTA is available:
+
+```bash
+./ota_update_all.sh s3
+# or
+./ota_update_all.sh s3-mini
+```
+
+What it does:
+1. creates/reuses `.ota-venv`,
+2. installs OTA dependencies in that venv (`platformio`, `littlefs-python`, `fatfs-ng`, `pyyaml`),
+3. builds `miniweb`,
+4. uploads LittleFS image over ElegantOTA,
+5. uploads firmware over ElegantOTA.
+
+If your device requires OTA credentials, set:
+
+```bash
+export YAEGER_OTA_USERNAME=admin
+export YAEGER_OTA_PASSWORD='your-password'
+```
+
+(`YAEGER_OTA_USERNAME` defaults to `admin` if omitted.)
+
 ### Schema
 
 ![schema](./schema/Schematic_Yaeger_2024-12-24.svg)
@@ -76,13 +141,43 @@ Courtesy of [@dlisec](https://github.com/dlisec)
 
 A build script has been provided by [@matthew73210](https://github.com/matthew73210), so to get up and running on the
 ESP, just run `./build_and_flash.sh`. Make sure to read the comments in the script. But also in the platformio.ini and choose the right board
+Yaeger OTA in this project is provided by the web-based ElegantOTA handler (`/update`) and not the PlatformIO `espota`
+upload protocol.
+
+For VS Code + PlatformIO uploads via ElegantOTA, use one of these environments:
+
+* `esp32-s3-elegantota`
+* `esp32-s3-mini-elegantota`
+
+These use a custom PlatformIO upload script that sends the built firmware to `http://yaeger.local/update` through the
+same ElegantOTA mechanism used by the device web UI.
+
+For a **single-command OTA update of the whole project** (frontend files + firmware), run:
+
+```bash
+./ota_update_all.sh s3
+# or
+./ota_update_all.sh s3-mini
+```
+
+This builds `miniweb`, then runs OTA in two explicit steps: (1) upload LittleFS (`buildfs` + `uploadfs`) and (2) upload firmware (`upload`). The script creates and uses a local Python virtual environment (`.ota-venv`), installs required OTA dependencies (`platformio`, `littlefs-python`, `fatfs-ng`, `pyyaml`), and auto-retries if PlatformIO reports missing Python modules.
+
+For local frontend builds, use npm from `miniweb`:
+
+```bash
+cd miniweb
+npm ci
+npm run build
+```
 
 ## Latest features
 
 ### PID
 
 PID temp follower, set the temperature setpoint and the PID controller will try and follow. You'll need to find your own PID values
 
+A controller review with alternatives (including MPC/LQR and fan min/max envelope design) is available at `docs/control_strategy_review_2026-04-14.md` (current recommendation: ADRC as primary advanced controller, with an ADRC autotune workflow proposal).
+
 ### Profile
 
 Still in the works, but there is now a profile follower, it follows a simple .json format. You can have a go at [Gaggiuino web profiler](https://matthew73210.github.io/Gaggiuino-web-profiler/) under the _pun_ "Yägermeister Mode"

build_and_flash.sh

@@ -31,36 +31,21 @@ fi
 
 echo "Using PlatformIO environment: $PIO_ENV"
 
-
-read -p "Choose frontend (r for reyaeger, empty for classic): " frontend
-
-if [ $frontend = 'r' ]; then
-
-echo "reyaeger download";
-curl -L https://github.com/RobTS/reyaeger/releases/latest/download/reyaeger.zip > reyaeger.zip
-rm -rf data
-mkdir data
-unzip -d ./data ./reyaeger.zip
-
-else
-
-# Step 1: Navigate to the miniweb directory
+# Step 1: Navigate to the primary frontend (miniweb)
 echo "Navigating to miniweb..."
 cd miniweb || { echo "miniweb folder not found!"; exit 1; }
 
-# Step 2: Install dependencies
-echo "Installing dependencies with npm..."
-npm install || { echo "npm install failed!"; exit 1; }
+# Step 2: Install dependencies with npm (standardized package manager)
+echo "Installing dependencies with npm ci..."
+npm ci || { echo "npm ci failed!"; exit 1; }
 
 # Step 3: Build the web assets
 echo "Building the web project..."
 npm run build || { echo "npm build failed!"; exit 1; }
 
 # Step 4: Return to the project root
 echo "Returning to the project root..."
-
 cd .. || exit 1
-fi
 
 # Step 5: Erase the device memory (optional but recommended)
 echo "Erasing the device memory..."