Merge pull request 'Add French language support: translations, language mapping, and UI localization.' (#45) from Nathacks/KX-Bridge-Release:master into master

CHANGELOG.de.md

@@ -1,5 +1,25 @@
 # Changelog
 
+## [0.9.19.1] – 2026-06-04
+
+### Behoben
+- Standalone-Binaries (Linux/Windows) zeigten `vunknown` als Version.
+  Die `VERSION`-Datei ist jetzt ins PyInstaller-Onefile eingebettet.
+- Bei fehlenden TLS-Zertifikaten (`anycubic_slicer.crt`/`.key`) gab
+  es nur den rohen Fehler `[Errno 2] No such file or directory`. Die
+  Bridge meldet jetzt klar, wo die Dateien hingelegt werden müssen
+  und dass `anycubic-certs.zip` aus dem Gitea-Release stammt.
+
+### Geändert
+- Filament-Profil-Liste neu kuratiert: 209 statt 399 Einträge.
+  Profile die nur für drucker-spezifische Vendor-Bundles existieren
+  (z.B. Eryone Thinker X400, Artillery M1 Pro, WonderMaker ZR,
+  Tiertime, Cubicon, CoLiDo, Afinia, Snapmaker) sind rausgeflogen
+  — OrcaSlicer hätte sie im Standard-Kobra-X-Setup beim Sync
+  ohnehin nicht gefunden, weil die jeweiligen Vendor-Bundles nur
+  bei aktivem Drucker-Vendor geladen werden. Für solche Filamente
+  bleibt der Custom-Profile-Import (Issue #41) der Weg.
+
 ## [0.9.19] – 2026-06-02
 
 ### Neu
@@ -19,9 +39,9 @@
   wird beim Sync an Orca als User-Match weitergegeben. Funktioniert
   über HTTP, also auch wenn die Bridge im Docker auf Raspi/NAS läuft
   und OrcaSlicer auf dem Desktop. Auch reine Override-Profile mit nur
-  `inherits: "Generic PLA @System"` + ein paar Tweaks (z.B.
+  `inherits: "Generic PLA @System"` + ein paar Tweaks werden korrekt
-  „Bert - PLA") werden korrekt erkannt — die Bridge resolved die
+  erkannt — die Bridge resolved die vererbten Felder aus dem
-  vererbten Felder aus dem System-Parent.
+  System-Parent.
 
 ### Fixes
 - **AMS-Sync landete hartnäckig auf „Generic PLA":** das Orca-

CHANGELOG.md

@@ -1,5 +1,25 @@
 # Changelog
 
+## [0.9.19.1] – 2026-06-04
+
+### Fixed
+- Standalone-Binaries (Linux/Windows) zeigten `vunknown` als Version.
+  Die `VERSION`-Datei ist jetzt ins PyInstaller-Onefile eingebettet.
+- Bei fehlenden TLS-Zertifikaten (`anycubic_slicer.crt`/`.key`) gab
+  es nur den rohen Fehler `[Errno 2] No such file or directory`. Die
+  Bridge meldet jetzt klar, wo die Dateien hingelegt werden müssen
+  und dass `anycubic-certs.zip` aus dem Gitea-Release stammt.
+
+### Changed
+- Filament-Profil-Liste neu kuratiert: 209 statt 399 Einträge.
+  Profile die nur für drucker-spezifische Vendor-Bundles existieren
+  (z.B. Eryone Thinker X400, Artillery M1 Pro, WonderMaker ZR,
+  Tiertime, Cubicon, CoLiDo, Afinia, Snapmaker) sind rausgeflogen
+  — OrcaSlicer hätte sie im Standard-Kobra-X-Setup beim Sync
+  ohnehin nicht gefunden, weil die jeweiligen Vendor-Bundles nur
+  bei aktivem Drucker-Vendor geladen werden. Für solche Filamente
+  bleibt der Custom-Profile-Import (Issue #41) der Weg.
+
 ## [0.9.19] – 2026-06-02
 
 ### New
@@ -19,9 +39,9 @@
   are passed through to Orca on sync as user matches. Works over HTTP
   so the bridge can run in Docker on a Raspi/NAS while OrcaSlicer
   lives on a desktop. Override-only profiles with just
-  `inherits: "Generic PLA @System"` + a few tweaks (e.g. "Bert - PLA")
+  `inherits: "Generic PLA @System"` + a few tweaks are detected
-  are detected correctly — the bridge resolves the inherited fields
+  correctly — the bridge resolves the inherited fields from the
-  from the system parent.
+  system parent.
 
 ### Fixes
 - **AMS sync stuck on "Generic PLA":** the Orca data model has 68

README.de.md

@@ -67,17 +67,44 @@ docker compose up -d
 
 **Linux-Binary (kein Docker):**
 ```bash
-chmod +x kx-bridge && ./kx-bridge
+chmod +x kx-bridge-linux-amd64 && ./kx-bridge-linux-amd64
 ```
 
 **Windows-EXE (kein Docker):**
 ```
 kx-bridge.exe
 ```
-> `config\` und `data\` werden neben der EXE angelegt — portabel.
 
-> Bei Linux- und Windows-Binary liegen `config/` und `data/` (Einstellungen, SQLite,
+> ⚠️ **TLS-Zertifikate für Standalone-Binary nötig**
-> GCode-Store) jeweils neben dem Programm. Einfach den ganzen Ordner kopieren = umziehen.
+>
+> Die Bridge spricht per mTLS mit dem Drucker-MQTT und braucht zwei
+> Zertifikat-Dateien **direkt neben dem Binary**:
+>
+> - `anycubic_slicer.crt`
+> - `anycubic_slicer.key`
+>
+> Beide liegen im **`anycubic-certs.zip`** auf derselben Release-Seite.
+> Lade die ZIP herunter und entpacke die beiden Dateien in dasselbe
+> Verzeichnis wie `kx-bridge-linux-amd64` bzw. `kx-bridge.exe`. Ohne
+> die Zertifikate siehst du `Verbindung fehlgeschlagen: TLS-Zertifikate
+> fehlen …` (0.9.19.1+) oder `[Errno 2] No such file or directory`
+> (ältere Builds).
+>
+> So muss es aussehen:
+> ```
+> ~/kx-bridge/
+> ├── kx-bridge-linux-amd64   (oder kx-bridge.exe)
+> ├── anycubic_slicer.crt     ← aus anycubic-certs.zip
+> ├── anycubic_slicer.key     ← aus anycubic-certs.zip
+> └── config/                 (wird beim ersten Start angelegt)
+> ```
+>
+> Docker-User müssen das nicht machen — die Zertifikate sind im Image
+> enthalten.
+
+> Bei Linux- und Windows-Binary liegen `config/` und `data/` (Einstellungen,
+> SQLite, GCode-Store) jeweils neben dem Programm. Einfach den ganzen Ordner
+> kopieren = umziehen.
 
 **Python direkt:**
 ```bash
@@ -130,7 +157,7 @@ Für sauberen AMS-Filament-Sync gibt es einen **gepatchten OrcaSlicer-Build**:
 - Vendor-Match wenn `tray_info_idx` gesetzt ist, das Preset aber inkompatibel
 - Zwei-Pass-Suche: erst kompatible Presets, dann alle sichtbaren
 
-**Warum das zusammen wichtig ist:** ohne #13719 landen die AMS-Slots in OrcaSlicer alle auf `Generic PLA` / `Generic PETG`, obwohl die Bridge die konkrete Marke schon mitsendet (`name + vendor_name + gate_filament_name`). Mit dem KX-Build matched OrcaSlicer deine echten User-Presets — auch die, die du via [Eigene OrcaSlicer-Profile importieren](#-features) in die Bridge gezogen hast.
+**Warum das zusammen wichtig ist:** ohne #13719 landen die AMS-Slots in OrcaSlicer alle auf `Generic PLA` / `Generic PETG`, obwohl die Bridge die konkrete Marke schon mitsendet (`name + vendor_name + gate_filament_name`). Mit dem KX-Build matched OrcaSlicer deine echten User-Presets — auch die, die du via [Eigene OrcaSlicer-Profile importieren](https://gitea.it-drui.de/viewit/KX-Bridge-Release/src/branch/master/docs/filament-preset-bridge-guide.md) in die Bridge gezogen hast.
 
 Stock-Upstream-OrcaSlicer funktioniert für Slicing und Drucken weiterhin — nur das Per-Slot-Vendor-Matching beim AMS-Sync fällt dann weg. Material und Farbe pro Slot kannst du auch ohne den KX-Build über die Bridge ans Drucker-Display schreiben (das läuft über MQTT, nicht über den Slicer).
 

README.es.md

@@ -66,17 +66,43 @@ docker compose up -d
 
 **Binario Linux (sin Docker):**
 ```bash
-chmod +x kx-bridge && ./kx-bridge
+chmod +x kx-bridge-linux-amd64 && ./kx-bridge-linux-amd64
 ```
 
 **EXE Windows (sin Docker):**
 ```
 kx-bridge.exe
 ```
-> `config\` y `data\` se crean junto al EXE — instalación portátil.
 
-> Con los binarios de Linux y Windows, `config/` y `data/` (configuración, SQLite, almacén de GCode)
+> ⚠️ **Certificados TLS necesarios para el binario standalone**
-> viven junto al programa. Copia toda la carpeta para mover la instalación.
+>
+> El bridge habla con el MQTT de la impresora vía mTLS y necesita dos
+> ficheros de certificado **junto al binario**:
+>
+> - `anycubic_slicer.crt`
+> - `anycubic_slicer.key`
+>
+> Ambos vienen en **`anycubic-certs.zip`** en la misma página de release.
+> Descárgalo y extrae los dos ficheros en el mismo directorio que
+> `kx-bridge-linux-amd64` o `kx-bridge.exe`. Sin ellos verás
+> `Verbindung fehlgeschlagen: TLS-Zertifikate fehlen …` (0.9.19.1+) o
+> `[Errno 2] No such file or directory` (versiones anteriores).
+>
+> Estructura correcta:
+> ```
+> ~/kx-bridge/
+> ├── kx-bridge-linux-amd64   (o kx-bridge.exe)
+> ├── anycubic_slicer.crt     ← de anycubic-certs.zip
+> ├── anycubic_slicer.key     ← de anycubic-certs.zip
+> └── config/                 (se crea en el primer arranque)
+> ```
+>
+> Los usuarios de Docker no necesitan hacer esto — los certificados
+> están incluidos en la imagen.
+
+> Con los binarios de Linux y Windows, `config/` y `data/` (configuración,
+> SQLite, almacén de GCode) viven junto al programa. Copia toda la carpeta
+> para mover la instalación.
 
 **Python directamente:**
 ```bash

README.md

@@ -30,7 +30,7 @@ officially tested or supported. Feedback welcome.</sub>
 
 ---
 
-## ✨ Features
+## Features
 
 | | |
 |---|---|
@@ -50,7 +50,7 @@ officially tested or supported. Feedback welcome.</sub>
 
 ---
 
-## 🚀 Quick Start
+## Quick Start
 
 ### 1. Prepare the printer
 
@@ -66,17 +66,43 @@ docker compose up -d
 
 **Linux binary (no Docker):**
 ```bash
-chmod +x kx-bridge && ./kx-bridge
+chmod +x kx-bridge-linux-amd64 && ./kx-bridge-linux-amd64
 ```
 
 **Windows EXE (no Docker):**
 ```
 kx-bridge.exe
 ```
-> `config\` and `data\` are created next to the EXE — portable.
 
-> With the Linux and Windows binaries, `config/` and `data/` (settings, SQLite, GCode store)
+> ⚠️ **TLS certificates required for the standalone binary**
-> live next to the program. Copy the whole folder = move the installation.
+>
+> The bridge talks to the printer's MQTT over mTLS and needs two
+> certificate files **right next to the binary**:
+>
+> - `anycubic_slicer.crt`
+> - `anycubic_slicer.key`
+>
+> Both ship inside **`anycubic-certs.zip`** on the same release page.
+> Download it and extract the two files into the same directory as
+> `kx-bridge-linux-amd64` / `kx-bridge.exe`. Without them you'll see
+> `Verbindung fehlgeschlagen: TLS-Zertifikate fehlen …` (0.9.19.1+)
+> or `[Errno 2] No such file or directory` (older builds).
+>
+> Working layout:
+> ```
+> ~/kx-bridge/
+> ├── kx-bridge-linux-amd64   (or kx-bridge.exe)
+> ├── anycubic_slicer.crt     ← from anycubic-certs.zip
+> ├── anycubic_slicer.key     ← from anycubic-certs.zip
+> └── config/                 (auto-created on first run)
+> ```
+>
+> Docker users don't need to do this — the certs are baked into the
+> image.
+
+> With the Linux and Windows binaries, `config/` and `data/` (settings,
+> SQLite, GCode store) live next to the program. Copy the whole folder
+> = move the installation.
 
 **Python directly:**
 ```bash
@@ -104,13 +130,13 @@ Printer → Connection type **Moonraker** → Host: `http://BRIDGE-IP:7125`
 
 ---
 
-## 📺 Video Tutorial
+## Video Tutorial
 
 [![KX-Bridge Setup & Usage](https://img.youtube.com/vi/1Ql4wfH27fM/hqdefault.jpg)](https://www.youtube.com/watch?v=1Ql4wfH27fM)
 
 ---
 
-## 🎨 Recommended Slicer
+## Recommended Slicer
 
 For proper AMS filament-sync we ship a **patched OrcaSlicer build**:
 
@@ -129,7 +155,7 @@ For proper AMS filament-sync we ship a **patched OrcaSlicer build**:
 - Vendor match when `tray_info_idx` is set but its preset is incompatible
 - Two-pass lookup: first compatible presets, then all visible ones
 
-**Why this matters:** without #13719 the AMS slots in OrcaSlicer all fall back to `Generic PLA` / `Generic PETG` even though the bridge already sends the concrete brand (`name + vendor_name + gate_filament_name`). With the KX build OrcaSlicer matches your actual user presets — including profiles you imported into the bridge via the [Import your own OrcaSlicer profiles](#-features) flow.
+**Why this matters:** without #13719 the AMS slots in OrcaSlicer all fall back to `Generic PLA` / `Generic PETG` even though the bridge already sends the concrete brand (`name + vendor_name + gate_filament_name`). With the KX build OrcaSlicer matches your actual user presets — including profiles you imported into the bridge via the [Import your own OrcaSlicer profiles](https://gitea.it-drui.de/viewit/KX-Bridge-Release/src/branch/master/docs/filament-preset-bridge-guide.md) flow.
 
 Stock upstream OrcaSlicer still works for slicing and printing — you just lose the per-slot brand matching on AMS sync. Slot material + colour can still be pushed bridge → printer either way (that goes over MQTT, not via the slicer).
 
@@ -137,7 +163,7 @@ OrcaSlicer-KX is a build of [OrcaSlicer](https://github.com/SoftFever/OrcaSlicer
 
 ---
 
-## 🏠 Community & Integrations
+## Community & Integrations
 
 - **[Home Assistant integration](https://github.com/gangoke/kobrax-lan-hass-component)**
   by [@gangoke](https://github.com/gangoke) — exposes sensors, print controls,
@@ -154,7 +180,7 @@ OrcaSlicer-KX is a build of [OrcaSlicer](https://github.com/SoftFever/OrcaSlicer
 
 ---
 
-## 🔧 Getting credentials manually
+## Getting credentials manually
 
 Normally not needed — *"+ Add printer"* does this automatically. If you do need it:
 
@@ -171,7 +197,7 @@ Alternatively (if the IP is unknown): open AnycubicSlicerNext, connect the print
 
 ---
 
-## ⚙️ Useful commands
+## Useful commands
 
 ```bash
 docker compose logs -f                 # show logs
@@ -182,7 +208,7 @@ docker compose up -d --build           # rebuild locally (instead of pulling)
 
 ---
 
-## 🩹 Troubleshooting
+## Troubleshooting
 
 <details>
 <summary><b>"Wrong MQTT credentials" on start</b></summary>
@@ -216,7 +242,7 @@ Migration runs automatically on first start after the upgrade — no action requ
 
 ---
 
-## 🔒 Security
+## Security
 
 - The bridge is reachable on the local network at `http://<host-IP>:7125` — **do not** expose it to the internet
 - `config/config.ini` contains printer credentials — do not share publicly
@@ -224,7 +250,7 @@ Migration runs automatically on first start after the upgrade — no action requ
 
 ---
 
-## 📄 License
+## License
 
 [![License: GPL v3](https://img.shields.io/badge/License-GPL_v3-blue.svg)](LICENSE)
 

VERSION

@@ -1 +1 @@
-0.9.19
+0.9.19.1

docs/filament-preset-bridge-guide.md

@@ -0,0 +1,344 @@
+# Eigene Filament-Presets anlegen, prüfen und mit KX-Bridge verknüpfen
+
+> **Gilt für:** OrcaSlicer-KX v2.4.0-alpha-kx2 oder neuer
+
+---
+
+## Was ist die `filament_id` und warum ist sie wichtig?
+
+Jedes Filament-Preset in OrcaSlicer hat eine interne `filament_id`. Diese ID wird von der KX-Bridge genutzt, um beim AMS-Sync das richtige Preset zuzuordnen.
+
+- System-Presets (z.B. "Polymaker PolyTerra PLA") haben eine feste ID wie `GFL99` oder `OGFL04`.
+- **Eigene (User-)Presets** bekommen in OrcaSlicer-KX automatisch eine eindeutige ID, die mit `P` beginnt (z.B. `P3a7f2c1`).
+
+Ohne eindeutige ID zeigt OrcaSlicer beim Sync immer "Generic PLA" — auch wenn das Preset existiert.
+
+---
+
+## 1. Eigenes Filament-Preset anlegen
+
+1. OrcaSlicer-KX starten
+2. Rechts oben im **Filament-Dropdown** ein passendes Basis-Preset wählen (z.B. "Generic PLA" oder ein Hersteller-Preset)
+3. Einstellungen nach Wunsch anpassen (Temperaturen, Kühlung, etc.)
+4. Auf das **Speichern-Symbol** (Diskette) klicken → **"Save as new preset"**
+5. Namen eingeben — z.B. `SUNLU PLA+ 2.0`
+   > Der Name muss später exakt so in der Bridge eingetragen werden.
+6. Drucker auswählen: **Anycubic Kobra X 0.4 nozzle** — wichtig für die Kompatibilität!
+7. **Speichern** klicken
+8. OrcaSlicer **einmal neu starten** — erst dann wird die `filament_id` dauerhaft gespeichert.
+
+---
+
+## 2. Eindeutige ID prüfen
+
+Nach dem Neustart prüfen, ob die ID korrekt gesetzt wurde:
+
+**Windows:**
+```
+%APPDATA%\OrcaSlicer\user\default\filament\SUNLU PLA+ 2.0.json
+```
+
+**Linux:**
+```
+~/.config/OrcaSlicer/user/default/filament/SUNLU PLA+ 2.0.json
+```
+
+Die Datei öffnen und nach `filament_id` suchen:
+
+```json
+{
+  "filament_id": "P3a7f2c1",
+  ...
+}
+```
+
+✅ Korrekt: ID beginnt mit `P` gefolgt von 7 Hex-Zeichen  
+❌ Fehlt oder leer: OrcaSlicer-KX zu alt — Update auf v2.4.0-alpha-kx2 oder neuer
+
+---
+
+## 3. Preset auf einen anderen PC übertragen (Import)
+
+### Exportieren (Quell-PC)
+
+Die Preset-Datei einfach kopieren:
+
+**Windows:**
+```
+%APPDATA%\OrcaSlicer\user\default\filament\SUNLU PLA+ 2.0.json
+```
+
+**Linux:**
+```
+~/.config/OrcaSlicer/user/default/filament/SUNLU PLA+ 2.0.json
+```
+
+### Importieren (Ziel-PC)
+
+**Methode A — Datei direkt kopieren:**
+1. Die `.json`-Datei in das gleiche Verzeichnis auf dem Ziel-PC kopieren
+2. OrcaSlicer neu starten → Preset erscheint im Dropdown
+
+**Methode B — OrcaSlicer Import-Funktion:**
+1. In OrcaSlicer: **File → Import → Import Configs...**
+2. Die `.json`-Datei auswählen
+3. OrcaSlicer neu starten
+
+> **Wichtig:** Die `filament_id` in der Datei bleibt erhalten — das Preset wird auf dem Ziel-PC genauso erkannt wie auf dem Quell-PC.
+
+---
+
+## 4. Preset in KX-Bridge verknüpfen
+
+1. KX-Bridge UI öffnen
+2. **Filament-Verwaltung** → AMS-Slot auswählen
+3. Im Feld **Filament-Name** exakt den OrcaSlicer-Preset-Namen eintragen:
+   ```
+   SUNLU PLA+ 2.0
+   ```
+4. Speichern
+
+Die Bridge sendet beim Sync `filament_name: "SUNLU PLA+ 2.0"` → OrcaSlicer findet das Preset anhand von Name und `filament_id` → zeigt es korrekt an.
+
+---
+
+## Wichtige Hinweise
+
+| Was | Warum |
+|-----|-------|
+| Name in OrcaSlicer und Bridge müssen **exakt** übereinstimmen | Groß-/Kleinschreibung und Sonderzeichen werden verglichen |
+| Preset muss für **Anycubic Kobra X 0.4 nozzle** kompatibel sein | Beim Speichern den richtigen Drucker auswählen |
+| Nach dem ersten Speichern OrcaSlicer **neu starten** | Erst dann wird die `filament_id` persistent geschrieben |
+| **OrcaSlicer-KX v2.4.0-alpha-kx2** oder neuer verwenden | Ältere Versionen generieren keine eindeutige `filament_id` für User-Presets |
+
+---
+---
+
+# How to Create, Verify and Import Custom Filament Presets for KX-Bridge
+
+> **Requires:** OrcaSlicer-KX v2.4.0-alpha-kx2 or newer
+
+---
+
+## What is the `filament_id` and why does it matter?
+
+Every filament preset in OrcaSlicer has an internal `filament_id`. The KX-Bridge uses this ID to match the correct preset during AMS sync.
+
+- System presets (e.g. "Polymaker PolyTerra PLA") have a fixed ID like `GFL99` or `OGFL04`.
+- **Custom (user) presets** automatically receive a unique ID starting with `P` (e.g. `P3a7f2c1`) in OrcaSlicer-KX.
+
+Without a unique ID, OrcaSlicer will always show "Generic PLA" during sync — even if the preset exists.
+
+---
+
+## 1. Create a Custom Filament Preset
+
+1. Launch OrcaSlicer-KX
+2. Select a suitable base preset from the **filament dropdown** (e.g. "Generic PLA" or a vendor preset)
+3. Adjust settings as needed (temperatures, cooling, etc.)
+4. Click the **save icon** (floppy disk) → **"Save as new preset"**
+5. Enter a name — e.g. `SUNLU PLA+ 2.0`
+   > This name must be entered in the bridge exactly as typed here.
+6. Select printer: **Anycubic Kobra X 0.4 nozzle** — required for compatibility!
+7. Click **Save**
+8. **Restart OrcaSlicer once** — the `filament_id` is only written permanently after a restart.
+
+---
+
+## 2. Verify the Unique ID
+
+After restarting, check that the ID was set correctly:
+
+**Windows:**
+```
+%APPDATA%\OrcaSlicer\user\default\filament\SUNLU PLA+ 2.0.json
+```
+
+**Linux:**
+```
+~/.config/OrcaSlicer/user/default/filament/SUNLU PLA+ 2.0.json
+```
+
+Open the file and look for `filament_id`:
+
+```json
+{
+  "filament_id": "P3a7f2c1",
+  ...
+}
+```
+
+✅ Correct: ID starts with `P` followed by 7 hex characters  
+❌ Missing or empty: Your OrcaSlicer-KX version is too old — update to v2.4.0-alpha-kx2 or newer
+
+---
+
+## 3. Transfer a Preset to Another PC (Import)
+
+### Export (source PC)
+
+Simply copy the preset file:
+
+**Windows:**
+```
+%APPDATA%\OrcaSlicer\user\default\filament\SUNLU PLA+ 2.0.json
+```
+
+**Linux:**
+```
+~/.config/OrcaSlicer/user/default/filament/SUNLU PLA+ 2.0.json
+```
+
+### Import (target PC)
+
+**Method A — Copy file directly:**
+1. Copy the `.json` file to the same directory on the target PC
+2. Restart OrcaSlicer → preset appears in the dropdown
+
+**Method B — OrcaSlicer import function:**
+1. In OrcaSlicer: **File → Import → Import Configs...**
+2. Select the `.json` file
+3. Restart OrcaSlicer
+
+> **Note:** The `filament_id` inside the file is preserved — the preset will be recognized on the target PC exactly as on the source PC.
+
+---
+
+## 4. Link the Preset in KX-Bridge
+
+1. Open the KX-Bridge UI
+2. Go to **Filament Management** → select the AMS slot
+3. In the **Filament Name** field, enter the OrcaSlicer preset name exactly:
+   ```
+   SUNLU PLA+ 2.0
+   ```
+4. Save
+
+The bridge sends `filament_name: "SUNLU PLA+ 2.0"` during sync → OrcaSlicer matches by name and `filament_id` → displays the preset correctly.
+
+---
+
+## Quick Reference
+
+| What | Why |
+|------|-----|
+| Name in OrcaSlicer and Bridge must match **exactly** | Case and special characters are compared |
+| Preset must be compatible with **Anycubic Kobra X 0.4 nozzle** | Select the correct printer when saving |
+| **Restart OrcaSlicer** after saving for the first time | The `filament_id` is only written persistently after a restart |
+| Use **OrcaSlicer-KX v2.4.0-alpha-kx2** or newer | Older versions do not generate a unique `filament_id` for user presets |
+
+---
+---
+
+# Cómo crear, verificar e importar perfiles de filamento personalizados para KX-Bridge
+
+> **Requiere:** OrcaSlicer-KX v2.4.0-alpha-kx2 o superior
+
+---
+
+## ¿Qué es el `filament_id` y por qué es importante?
+
+Cada perfil de filamento en OrcaSlicer tiene un `filament_id` interno. KX-Bridge usa este ID para asignar el perfil correcto durante la sincronización AMS.
+
+- Los perfiles del sistema (p. ej. "Polymaker PolyTerra PLA") tienen un ID fijo como `GFL99` o `OGFL04`.
+- Los **perfiles personalizados (usuario)** reciben automáticamente un ID único que empieza por `P` (p. ej. `P3a7f2c1`) en OrcaSlicer-KX.
+
+Sin un ID único, OrcaSlicer mostrará siempre "Generic PLA" durante la sincronización, aunque el perfil exista.
+
+---
+
+## 1. Crear un perfil de filamento personalizado
+
+1. Iniciar OrcaSlicer-KX
+2. Seleccionar un perfil base adecuado en el **menú desplegable de filamento** (p. ej. "Generic PLA" o un perfil de fabricante)
+3. Ajustar la configuración según sea necesario (temperaturas, refrigeración, etc.)
+4. Hacer clic en el **icono de guardar** (disquete) → **"Save as new preset"**
+5. Introducir un nombre — p. ej. `SUNLU PLA+ 2.0`
+   > Este nombre debe introducirse en la bridge exactamente igual.
+6. Seleccionar impresora: **Anycubic Kobra X 0.4 nozzle** — ¡necesario para la compatibilidad!
+7. Hacer clic en **Guardar**
+8. **Reiniciar OrcaSlicer una vez** — el `filament_id` solo se escribe de forma permanente tras un reinicio.
+
+---
+
+## 2. Verificar el ID único
+
+Tras reiniciar, comprobar que el ID se ha establecido correctamente:
+
+**Windows:**
+```
+%APPDATA%\OrcaSlicer\user\default\filament\SUNLU PLA+ 2.0.json
+```
+
+**Linux:**
+```
+~/.config/OrcaSlicer/user/default/filament/SUNLU PLA+ 2.0.json
+```
+
+Abrir el archivo y buscar `filament_id`:
+
+```json
+{
+  "filament_id": "P3a7f2c1",
+  ...
+}
+```
+
+✅ Correcto: el ID empieza por `P` seguido de 7 caracteres hexadecimales  
+❌ Falta o está vacío: la versión de OrcaSlicer-KX es demasiado antigua — actualizar a v2.4.0-alpha-kx2 o superior
+
+---
+
+## 3. Transferir un perfil a otro PC (importar)
+
+### Exportar (PC de origen)
+
+Simplemente copiar el archivo del perfil:
+
+**Windows:**
+```
+%APPDATA%\OrcaSlicer\user\default\filament\SUNLU PLA+ 2.0.json
+```
+
+**Linux:**
+```
+~/.config/OrcaSlicer/user/default/filament/SUNLU PLA+ 2.0.json
+```
+
+### Importar (PC de destino)
+
+**Método A — Copiar el archivo directamente:**
+1. Copiar el archivo `.json` al mismo directorio en el PC de destino
+2. Reiniciar OrcaSlicer → el perfil aparece en el menú desplegable
+
+**Método B — Función de importación de OrcaSlicer:**
+1. En OrcaSlicer: **File → Import → Import Configs...**
+2. Seleccionar el archivo `.json`
+3. Reiniciar OrcaSlicer
+
+> **Nota:** El `filament_id` dentro del archivo se conserva — el perfil se reconocerá en el PC de destino exactamente igual que en el de origen.
+
+---
+
+## 4. Vincular el perfil en KX-Bridge
+
+1. Abrir la interfaz de KX-Bridge
+2. Ir a **Gestión de filamentos** → seleccionar la ranura AMS
+3. En el campo **Nombre de filamento**, introducir el nombre exacto del perfil de OrcaSlicer:
+   ```
+   SUNLU PLA+ 2.0
+   ```
+4. Guardar
+
+La bridge envía `filament_name: "SUNLU PLA+ 2.0"` durante la sincronización → OrcaSlicer busca por nombre y `filament_id` → muestra el perfil correctamente.
+
+---
+
+## Referencia rápida
+
+| Qué | Por qué |
+|-----|---------|
+| El nombre en OrcaSlicer y en Bridge debe coincidir **exactamente** | Se comparan mayúsculas, minúsculas y caracteres especiales |
+| El perfil debe ser compatible con **Anycubic Kobra X 0.4 nozzle** | Seleccionar la impresora correcta al guardar |
+| **Reiniciar OrcaSlicer** tras guardar por primera vez | El `filament_id` solo se escribe de forma permanente tras un reinicio |
+| Usar **OrcaSlicer-KX v2.4.0-alpha-kx2** o superior | Las versiones anteriores no generan un `filament_id` único para perfiles de usuario |

kobrax_client.py

@@ -154,6 +154,13 @@ class KobraXClient:
     # -- Connection ----------------------------------------------------------
 
     def _do_connect(self):
+        if not os.path.exists(CERT_FILE) or not os.path.exists(KEY_FILE):
+            raise FileNotFoundError(
+                f"TLS-Zertifikate fehlen: anycubic_slicer.crt + anycubic_slicer.key "
+                f"müssen neben der kx-bridge Binary liegen ({_SCRIPT_DIR}/). "
+                f"Lade anycubic-certs.zip vom Gitea-Release herunter und entpacke "
+                f"die Dateien dorthin."
+            )
         ctx = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT)
         ctx.check_hostname = False
         ctx.verify_mode    = ssl.CERT_NONE

kobrax_moonraker_bridge.py

@@ -3973,7 +3973,9 @@ class KobraXBridge:
     GITEA_RAW_BASE     = "https://gitea.it-drui.de/viewit/KX-Bridge-Release/raw/tag"
 
     def _read_version(self) -> str:
-        for base in (pathlib.Path(_BASE), pathlib.Path(_BASE).parent):
+        # PyInstaller-Onefile entpackt VERSION (per kx-bridge.spec datas) nach
+        # sys._MEIPASS — daher _WEB_BASE statt _BASE benutzen.
+        for base in (pathlib.Path(_WEB_BASE), pathlib.Path(_BASE), pathlib.Path(_BASE).parent):
             p = base / "VERSION"
             if p.is_file():
                 return p.read_text(encoding="utf-8").strip()

kx-bridge.spec

@@ -6,7 +6,7 @@
 # ein → zur Laufzeit über sys._MEIPASS lesbar (_WEB_BASE in der Bridge).
 from PyInstaller.utils.hooks import collect_all
 
-datas = [("web", "web"), ("data", "static")]  # bridge/data/ → static/ im _MEIPASS
+datas = [("web", "web"), ("data", "static"), ("VERSION", ".")]  # bridge/data/ → static/ im _MEIPASS
 binaries = []
 hiddenimports = []
 

web/themes/default/app.js

@@ -108,10 +108,10 @@ function _langToggleLabel(lang){
 function _mapSupportedLang(lang){
   if(!lang)return '';
   var l=String(lang).toLowerCase().replace(/_/g,'-').trim();
-  if(l==='de'||l==='en'||l==='es'||l==='zh-cn')return l;
+  if(l==='de'||l==='en'||l==='es'||l==='fr'||l==='zh-cn')return l;
 
   var base=l.split('-')[0];
-  if(base==='de'||base==='en'||base==='es')return base;
+  if(base==='de'||base==='en'||base==='es'||base==='fr')return base;
 
   if(base==='zh'){
     if(l.indexOf('cn')>=0||l.indexOf('hans')>=0||l==='zh')return 'zh-cn';

web/themes/default/index.html

@@ -38,6 +38,7 @@
       <option value="de">Deutsch</option>
       <option value="en">English</option>
       <option value="es">Espanol</option>
+      <option value="fr">Français</option>
       <option value="zh-cn">中文(简体)</option>
     </select>
   </div>

web/translations/fr.json

@@ -0,0 +1,247 @@
+{
+  "header_status_standby": "Prêt",
+  "header_status_printing": "Impression",
+  "header_status_complete": "Terminé",
+  "header_status_error": "Erreur",
+  "kobra_free": "Disponible",
+  "kobra_busy": "Occupé",
+  "kobra_printing": "Impression",
+  "kobra_preheating": "Préchauffage",
+  "kobra_auto_leveling": "Mise à niveau auto",
+  "kobra_checking": "Vérification",
+  "kobra_updated": "Mise à jour",
+  "kobra_init": "Initialisation",
+  "kobra_pausing": "Pause en cours…",
+  "kobra_paused": "En pause",
+  "kobra_resuming": "Reprise en cours…",
+  "kobra_resumed": "Repris",
+  "kobra_stopping": "Arrêt en cours…",
+  "kobra_stoped": "Arrêté",
+  "kobra_finished": "Terminé",
+  "kobra_failed": "Erreur",
+  "kobra_canceled": "Annulé",
+  "kobra_offline": "Hors ligne",
+  "nav_dashboard": "Tableau de bord",
+  "nav_print": "Impression",
+  "nav_temps": "Températures",
+  "nav_motion": "Mouvement",
+  "nav_ams": "AMS",
+  "nav_extras": "Lumière / Ventilateur",
+  "nav_console": "Console",
+  "card_progress": "Progression",
+  "card_temps": "Températures",
+  "card_light_fan": "Ventilateur",
+  "card_speed": "Vitesse d'impression",
+  "card_cam": "Caméra",
+  "lbl_elapsed": "Écoulé :",
+  "lbl_remaining": "Restant :",
+  "lbl_slicer_time": "Estimation slicer :",
+  "lbl_layers": "Couche",
+  "speed_silent": "🐢 Silencieux",
+  "speed_normal": "⚡ Normal",
+  "speed_sport": "🚀 Sport",
+  "lbl_light": "💡 Lumière",
+  "lbl_feed": "Charger",
+  "lbl_unload": "Décharger",
+  "card_ace_dry": "Séchage ACE",
+  "ace_dry_dryer": "Séchoir",
+  "ace_dry_status_off": "Statut : Arrêté",
+  "ace_dry_status_on": "Statut : Actif",
+  "ace_dry_status_remaining": "Restant",
+  "ace_dry_humidity": "Humidité",
+  "ace_dry_current_temp": "Température",
+  "ace_dry_chart": "Historique (Temp/Humidité)",
+  "ace_dry_temp": "Température (°C)",
+  "ace_dry_duration": "Durée (min)",
+  "ace_dry_start": "▶ Démarrer",
+  "ace_dry_stop": "■ Arrêter",
+  "ace_dry_auto_refill": "Remplissage auto",
+  "ace_dry_enable": "Activer le séchage",
+  "ace_dry_temp_line": "Température de séchage",
+  "ace_dry_time_line": "Durée de séchage",
+  "ace_dry_ui_pending": "(Interface seule, backend suivant)",
+  "ace_dry_dialog_title": "Réglages Temp/Durée du séchoir",
+  "ace_dry_dialog_temp": "Température (30-80°C)",
+  "ace_dry_dialog_time": "Temps restant (h:m:s)",
+  "ace_dry_dialog_confirm": "Confirmer",
+  "ace_dry_dialog_cancel": "Annuler",
+  "ace_dry_dialog_save_restart": "Enregistrer et redémarrer",
+  "ace_dry_dialog_custom_name": "Nom personnalisé",
+  "ace_dry_dialog_reset_default": "Réinitialiser",
+  "cam_placeholder": "📷 Caméra non démarrée",
+  "cam_stream_unavailable": "Flux indisponible",
+  "btn_cam_start": "▶ Caméra",
+  "btn_cam_stop": "◼ Caméra",
+  "btn_pause": "⏸ Pause",
+  "btn_resume": "▶ Reprendre",
+  "btn_cancel": "✕ Arrêter",
+  "label_nozzle": "Buse",
+  "label_bed": "Plateau",
+  "label_fan": "🌀 Ventilateur",
+  "label_light": "💡 Lumière",
+  "label_on_off": "On / Off",
+  "label_speed": "Vitesse",
+  "panel_print_title": "Contrôle impression",
+  "panel_print_btn_pause": "⏸ Pause",
+  "panel_print_btn_resume": "▶ Reprendre",
+  "panel_print_btn_cancel": "✕ Annuler",
+  "panel_print_temps_live": "Températures (en direct)",
+  "label_set": "Définir",
+  "label_off": "Éteint",
+  "panel_temps_nozzle": "Buse",
+  "panel_temps_bed": "Plateau chauffant",
+  "panel_temps_chart": "Historique (60 dernières valeurs)",
+  "label_target_c": "Cible :",
+  "panel_motion_xy": "Axes XY",
+  "panel_motion_z": "Axe Z",
+  "label_step": "Pas :",
+  "btn_home_z": "Origine Z",
+  "btn_home_xy": "Origine XY",
+  "btn_home_all": "Origine Tout",
+  "btn_disable_motors": "Moteurs Off",
+  "panel_ams_title": "Filament",
+  "card_ams": "Filament",
+  "ams_no_data": "Aucune donnée AMS reçue",
+  "label_slot": "Slot",
+  "ams_empty": "Vide",
+  "panel_extras_light": "Lumière",
+  "panel_extras_fan": "Ventilateur",
+  "panel_extras_camera": "Caméra",
+  "btn_cam_start2": "▶ Démarrer",
+  "btn_cam_stop2": "◼ Arrêter",
+  "panel_console_title": "Journal d'événements",
+  "log_light_on": "Lumière allumée",
+  "log_light_off": "Lumière éteinte",
+  "log_fan": "Ventilateur →",
+  "log_nozzle": "Buse →",
+  "log_bed": "Plateau →",
+  "log_axis": "Axe",
+  "log_home": "Origine",
+  "log_home_all": "Origine Tout",
+  "log_cam_start": "Caméra démarrée :",
+  "log_cam_stop": "Caméra arrêtée",
+  "log_poll_error": "Erreur de sondage :",
+  "log_error": "Erreur :",
+  "confirm_cancel": "Vraiment annuler l'impression ?",
+  "settings_title": "Paramètres",
+  "settings_connection": "Connexion",
+  "settings_print": "Paramètres d'impression",
+  "settings_poll": "Intervalle de sondage",
+  "settings_version": "Version",
+  "settings_save": "Enregistrer et redémarrer",
+  "settings_printer_name": "Nom de l'imprimante",
+  "settings_printer_ip": "IP de l'imprimante",
+  "settings_mqtt_port": "Port MQTT",
+  "settings_username": "Nom d'utilisateur MQTT",
+  "settings_password": "Mot de passe MQTT",
+  "settings_device_id": "ID de l'appareil",
+  "settings_mode_id": "ID du mode",
+  "hint_ip_no_port": "Adresse IP uniquement, sans port (ex. 192.168.1.102)",
+  "settings_default_slot": "Slot par défaut (couleur unique)",
+  "settings_slot_auto": "Auto (tous les slots chargés)",
+  "settings_auto_leveling": "Mise à niveau auto avant impression",
+  "settings_camera_on_print": "Activer la caméra au démarrage de l'impression",
+  "settings_web_upload_warning": "Afficher un avertissement lors de l'impression de fichiers web",
+  "update_check": "Vérifier les mises à jour",
+  "update_checking": "Vérification…",
+  "update_available": "disponible",
+  "update_none": "Déjà à jour",
+  "update_apply": "Installer maintenant",
+  "update_applying": "Téléchargement…",
+  "update_restarting": "Redémarrage…",
+  "update_error": "Erreur",
+  "btn_connect": "⚡ Connecter",
+  "btn_disconnect": "✕ Déconnecter",
+  "lbl_conn_error": "Erreur de connexion :",
+  "slot_edit_title": "Modifier le slot",
+  "slot_edit_color": "Couleur",
+  "slot_edit_material": "Matériau",
+  "slot_edit_load": "⬇ Charger",
+  "slot_edit_unload": "⬆ Décharger",
+  "slot_edit_save": "💾 Enregistrer",
+  "slot_edit_custom": "ex. PLA, PETG, ABS…",
+  "slot_edit_ok": "Slot AMS",
+  "slot_edit_profile": "Profil OrcaSlicer",
+  "slot_edit_profile_hint": "Envoyé lors de la synchronisation OrcaSlicer comme marque spécifique au lieu de \"Générique\"",
+  "slot_edit_profile_default": "— Générique (défaut) —",
+  "orca_profile_section": "Profils OrcaSlicer",
+  "orca_profile_hint": "Importez vos propres profils de filament OrcaSlicer (ouvrez le dossier utilisateur via Aide → Afficher le dossier de configuration)",
+  "orca_profile_import_btn": "Importer des profils",
+  "orca_profile_import_link": "★ Importer mes profils…",
+  "orca_profile_import_title": "Importer vos profils OrcaSlicer",
+  "orca_profile_help_html": "Déposez un <b>ZIP</b> de votre dossier filament OrcaSlicer ou des fichiers <b>.json</b> individuels.<br>Dans OrcaSlicer : <i>Aide → Afficher le dossier de configuration → user/&lt;id&gt;/filament/</i>",
+  "orca_profile_dropmsg": "Déposez ici ou cliquez",
+  "orca_profile_list_label": "Profils importés",
+  "orca_profile_user_label": "Mes profils",
+  "orca_profile_user_empty": "– aucun –",
+  "orca_profile_uploading": "Envoi en cours…",
+  "orca_profile_done": "Importé",
+  "orca_profile_skipped": "ignoré",
+  "log_dir_all": "Tout",
+  "log_lvl_label": "Niveau :",
+  "file_ready_btn": "▶ Lancer l'impression",
+  "file_slots_btn": "🎨 Choisir les slots",
+  "file_cancel_btn": "✕ Annuler",
+  "nav_printers": "Imprimantes",
+  "skip_title": "✂ Ignorer des objets",
+  "skip_hint": "Décochez les objets que vous ne souhaitez plus imprimer :",
+  "skip_btn_label": "Objets",
+  "skip_no_objects": "Aucun objet dans cette impression.",
+  "skip_already": "ignoré",
+  "skip_select_at_least_one": "Veuillez sélectionner au moins un objet.",
+  "skip_sending": "Envoi …",
+  "skip_success": "Les objets seront ignorés.",
+  "fd_objects_hint": "Ignorer des objets (optionnel) :",
+  "fd_slots_hint": "Associer le canal GCode au slot AMS :",
+  "fd_cancel": "Annuler",
+  "fd_print": "▶ Imprimer",
+  "fd_no_slots_msg": "Aucun slot AMS chargé.{br}Lancer l'impression quand même ?",
+  "fd_slot": "Slot",
+  "fd_no_matching_material": "Aucun matériau correspondant",
+  "fd_used": "UTILISÉ",
+  "add_printer": "Ajouter une imprimante",
+  "apd_lbl_ip": "IP de l'imprimante",
+  "apd_lbl_name": "Nom (optionnel)",
+  "apd_placeholder_name": "ex. Kobra X Salon",
+  "apd_cancel": "Annuler",
+  "apd_confirm": "Ajouter",
+  "apd_fetching": "Récupération des données de l'imprimante…",
+  "apd_success": "Imprimante ajoutée, redémarrage du bridge…",
+  "apd_err_ip": "Veuillez saisir une adresse IP",
+  "printers_remove": "Supprimer l'imprimante",
+  "printers_remove_confirm": "Supprimer l'imprimante \"{name}\" ? Le bridge va redémarrer.",
+  "printers_active": "● actif",
+  "printers_switch": "Changer →",
+  "printers_current": "Imprimante actuelle",
+  "printers_loading": "Chargement…",
+  "printers_none": "Aucune imprimante configurée.",
+  "printers_empty_hint": "Aucune imprimante configurée.",
+  "nav_browser": "Navigateur",
+  "panel_browser_title": "Explorateur de fichiers",
+  "store_search_placeholder": "🔍 Rechercher…",
+  "store_empty": "Aucun fichier uploadé.",
+  "store_refresh": "↻ Actualiser",
+  "store_print": "▶ Imprimer",
+  "store_download": "⬇ Télécharger",
+  "store_delete_confirm": "Supprimer le fichier ?",
+  "store_print_confirm": "Imprimer le fichier ?",
+  "store_web_verify_title": "Vérifier le fichier",
+  "store_web_verify_msg": "Veuillez vérifier que ce fichier a été créé pour l'Anycubic Kobra X.",
+  "store_web_verify_confirm": "Confirmer",
+  "store_web_verify_abort": "Annuler",
+  "store_no_results": "Aucun fichier trouvé.",
+  "store_never": "jamais imprimé",
+  "store_estimate": "Estimation",
+  "store_upload_label_prefix": "Déposez un GCode ici ou ",
+  "store_upload_label_browse": "parcourir",
+  "store_upload_busy": "⏳ Envoi en cours…",
+  "store_upload_success": "✓ {file}",
+  "store_upload_error": "✗ {error}",
+  "sf_all": "Tout",
+  "sf_ok": "✓ Terminés",
+  "sf_err": "✗ Échoués",
+  "sf_new": "Nouveau",
+  "ss_date": "↓ Date",
+  "ss_name": "A–Z Nom",
+  "ss_dur": "⏱ Durée d'impression"
+}