build: sources for v0.9.11

CHANGELOG.de.md

@@ -1,5 +1,55 @@
 # Changelog
 
+## [0.9.11] – 2026-05-20
+
+### Neu
+- **ACE Pro 2 Support (experimentell, Community-Beitrag von @gangoke, PR #26):** Die Bridge erkennt jetzt die Filament-Hardware automatisch und passt sich an:
+  - **Modi:** `toolhead` (kein ACE, Standard-4-Slot-Box), `ace_direct` (ein ACE Pro 2 direkt am Toolhead), `ace_hub` (bis zu 4 ACE-Units am Slot-4-Hub) — insgesamt bis zu **19 Slots**.
+  - **AMS Auto-Refill** Umschalter.
+  - **Trockner:** Temperatur-/Luftfeuchte-Monitor, Start/Stop/Temp/Dauer-Steuerung, mit Material-Presets in einer neuen Config-Sektion `[ace_dry_presets]` (PLA, PLA+, PETG, TPU, ABS/ASA, PA/PC + 3 Custom).
+  - **UI:** Filament-Sektion skaliert auf 19 Slots, Modus-Label, geladener Slot grün umrandet mit Lade-/Entlade-Puls-Animation, Unload/Load direkt aus dem Slot-Edit-Dialog.
+  - **GCode-Farb-Mapping:** ACE2-fähig, Farbe-aus-GCode-Fix, Hinweis bei Inkonsistenz zwischen Mapping und Objekten, besseres Default-Mapping.
+
+> **⚠️ Experimentell:** Die ACE-Pro-2-Hardware-Pfade wurden vom Contributor mit einer einzelnen ACE2-Unit entwickelt und getestet; die 2–4-Unit-Hub-Konfigurationen sind theoretisch und auf echter Hardware ungetestet. Wir haben hier ebenfalls keine ACE2-Hardware zur Verifikation. Der Standard-`toolhead`-Pfad (ohne ACE) wurde live gegen einen echten Kobra X getestet. Wer ein Multi-ACE-Setup betreibt: bitte per Issue Rückmeldung geben.
+
+### Fixes
+- **Happy-Hare-MMU-Emulation:** Es werden nur belegte Slots gesynct — kein Placeholder für leere Slots (kompatibel mit OrcaSlicer PR #13372).
+- **GCode-Farb-Dialog** zeigt nach einem neuen Upload nicht mehr die Daten der vorherigen Datei.
+
+---
+
+## [0.9.10] – 2026-05-17
+
+> **Hinweis:** Mit diesem Release wird der Fokus von neuen Features auf
+> **Stabilisierung und Bugfixing** verlagert. Die Kern-Workflows
+> (Multi-Printer, Drucker hinzufügen/entfernen, Filament-Dialog,
+> Skip-Objekte, Standalone-Binaries) sind funktional ausreichend — ab jetzt
+> steht Robustheit vor neuen Features. Größere Feature-Wünsche (ACE Pro 2,
+> Home-Assistant-Integration vervollständigen, …) bleiben vorerst im Backlog.
+
+### Neu
+- **Objekte überspringen (vor und während des Drucks):** Aus dem AnycubicSlicerNext-Workbench-Bundle rekonstruiert — der Kobra X kann das nativ über sein Protokoll, der Anycubic-Slicer bietet es bloß nicht im UI an. Die Bridge schon, in zwei Varianten:
+  - **Vor dem Druck:** beim Starten eines Multi-Object-Drucks aus dem Browser-Tab hat der Filament-Dialog jetzt einen zusätzlichen Abschnitt „Objekte". Einzelne Objekte abwählen (oder Polygon direkt im Build-Plate-SVG anklicken) — sie werden vor dem Druck herausgenommen.
+  - **Während des Drucks:** neuer ✂-Button im Dashboard (nur während eines laufenden Drucks sichtbar). Öffnet einen Dialog mit derselben interaktiven SVG-Vorschau — Teil anklicken, bestätigen, der Drucker druckt es nicht weiter. Bereits übersprungene Teile bleiben ausgegraut, der Dialog aktualisiert sich live damit man sieht welche schon weg sind.
+- **Filament-Dialog – farbige Kanal- und Slot-Marker (Issue #23):** Die GCode-Kanal-Nummer sitzt jetzt in einer farbigen Box links (Hintergrund = Kanal-Farbe, Auto-Kontrast-Text statt des alten kleinen Punktes), der zugewiesene AMS-Slot bekommt rechts neben dem Dropdown denselben Look — aktualisiert sich live wenn man die Auswahl ändert. Funktioniert mit 4 Kanälen; das Layout iteriert sauber für mehr, aber >4 echte Filament-Slots brauchen eine ACE-Pro-2-Box und sind ohne entsprechende Hardware nicht durchgängig testbar (geparkt als Feature-Request, Issues #22 und #23).
+
+### Intern
+- Neue Helfer `kobrax_client.skip_objects(names)` / `query_skip_objects()`.
+- Neue Endpunkte: `GET /kx/files/{id}/objects`, `POST /kx/skip`, `POST /kx/skip/query`, `GET /kx/skip/state`.
+- SQLite-Schema: `gcode_files` bekommt die Spalten `objects_skip_parts` und `svg_image` (Auto-Migration auf bestehenden DBs).
+- `_on_file` extrahiert die vom Drucker gelieferte Objektliste + SVG-Vorschau und speichert sie pro Datei.
+- `_on_skip`-Callback verfolgt, welche Objekte der Drucker aktuell als übersprungen meldet.
+
+---
+
+## [0.9.9] – 2026-05-14
+
+### Fixes
+- **„Failed to fetch"-Schleife in der UI (Issue #21):** Wenn die Web-UI über die LAN-IP geöffnet wurde, lieferte `/kx/printers` `bridge_url: http://localhost:7125` zurück. Der Browser machte daraufhin Cross-Origin-Requests von der LAN-IP nach `localhost` — die wurden vom Browser blockiert und produzierten eine Flut aus `TypeError: Failed to fetch`-Poll-Fehlern. Die Bridge liefert jetzt im Einzel-Drucker-Modus eine leere `bridge_url`, sodass das Frontend relative Pfade gegen dieselbe Origin wie die UI nutzt. Im Multi-Printer-Modus werden `localhost`/`127.0.0.1` als Bridge-Hosts herausgefiltert.
+- **Windows-EXE crasht beim Start (Issue #21):** Die v0.9.8-`kx-bridge.exe` wurde mit einer veralteten `config_loader.py` aus einem früheren Release gebaut und stürzte mit `AttributeError: module 'config_loader' has no attribute 'list_printers'` ab. `release.sh` synct jetzt `config_loader.py` zusammen mit den anderen Quellen ins Windows-Build-Repository.
+
+---
+
 ## [0.9.8] – 2026-05-12
 
 ### Neu

CHANGELOG.md

@@ -1,5 +1,55 @@
 # Changelog
 
+## [0.9.11] – 2026-05-20
+
+### New
+- **ACE Pro 2 support (experimental, community contribution by @gangoke, PR #26):** the bridge now auto-detects the filament hardware and adapts:
+  - **Modes:** `toolhead` (no ACE, stock 4-slot box), `ace_direct` (one ACE Pro 2 directly on the toolhead), `ace_hub` (up to 4 ACE units on the slot-4 hub) — up to **19 slots** total.
+  - **AMS auto-refill** toggle.
+  - **Dryer:** temperature/humidity monitor, start/stop/temp/duration control, with material presets configurable in a new `[ace_dry_presets]` config section (PLA, PLA+, PETG, TPU, ABS/ASA, PA/PC + 3 custom).
+  - **UI:** filament section scales to 19 slots, mode label, loaded slot is green-outlined with a load/unload pulse animation, unload/load straight from the slot-edit dialog.
+  - **GCode color mapping:** ACE2-aware, color-from-GCode fix, inconsistency notifier when the mapping doesn't match the objects, better default mapping.
+
+> **⚠️ Experimental:** the ACE Pro 2 hardware paths were developed and tested by the contributor with a single ACE2 unit; the 2–4 unit hub configurations are theoretical and untested on real hardware. We don't have ACE2 hardware to verify against either. The standard `toolhead` (no-ACE) path was verified live against a real Kobra X here. If you run a multi-ACE setup, please report back via Issues.
+
+### Fixes
+- **Happy Hare MMU emulation:** only populated slots are now synced — no placeholder for empty slots (aligns with OrcaSlicer PR #13372).
+- **GCode color dialog** no longer shows the previously-uploaded file's data after a new upload.
+
+---
+
+## [0.9.10] – 2026-05-17
+
+> **Heads-up:** with this release the focus shifts from new features to
+> **stabilization and bug-fixing**. The core flows (multi-printer, add/remove,
+> filament dialog, skip objects, standalone binaries) are feature-complete
+> enough — from now on the priority is making them rock-solid before adding
+> more on top. Bigger feature requests (ACE Pro 2, Home Assistant integration
+> completeness, …) stay on the backlog for now.
+
+### New
+- **Skip objects (pre-print and mid-print):** Reverse-engineered from the AnycubicSlicerNext Workbench bundle — the Kobra X actually supports object skipping over its native protocol, but the Anycubic slicer doesn't expose it. The bridge does now, in both flavors:
+  - **Pre-print:** when starting a multi-object print from the Browser tab, the filament dialog now has an additional "Objects" section. Uncheck individual objects (or click the polygon directly on the build-plate SVG preview) and they're stripped from the print before it starts.
+  - **Mid-print:** new ✂ button on the dashboard (only visible during an active print). Opens a dialog with the same interactive SVG preview — click a part to mark it for skipping, hit confirm, and the printer drops it from the rest of the run. Already-skipped parts stay greyed out and the dialog refreshes live so you can see which ones are gone.
+- **Filament dialog – colored channel and slot markers (Issue #23):** the GCode channel number now sits in a colored box on the left (background = channel color, auto-contrast text instead of the old tiny dot), and the assigned AMS slot gets the same treatment on the right of the dropdown — updates live as you change the selection. Plays well with 4 channels; the layout iterates so more channels render correctly, but >4 actual filament slots still need an ACE Pro 2 hub to be testable end-to-end (parked as a feature request, Issues #22 and #23).
+
+### Internal
+- New `kobrax_client.skip_objects(names)` / `query_skip_objects()` helpers.
+- New endpoints: `GET /kx/files/{id}/objects`, `POST /kx/skip`, `POST /kx/skip/query`, `GET /kx/skip/state`.
+- SQLite schema: `gcode_files` gained `objects_skip_parts` and `svg_image` columns (auto-migrates on existing DBs).
+- `_on_file` now extracts the printer-provided object list + SVG preview and persists them per file.
+- `_on_skip` callback tracks which objects the printer reports as currently skipped.
+
+---
+
+## [0.9.9] – 2026-05-14
+
+### Fixes
+- **"Failed to fetch" loop in the UI (Issue #21):** When the web UI was opened via the LAN IP, `/kx/printers` was returning `bridge_url: http://localhost:7125`, which caused the browser to fire cross-origin requests from the LAN IP to `localhost` — these were silently blocked, producing a flood of `TypeError: Failed to fetch` poll errors. The bridge now sends an empty `bridge_url` in single-printer mode so the frontend uses relative paths against the same origin as the UI. In multi-printer mode, `localhost`/`127.0.0.1` are filtered out as bridge hosts.
+- **Windows EXE startup crash (Issue #21):** The v0.9.8 `kx-bridge.exe` was built with a stale `config_loader.py` from an earlier release and crashed on startup with `AttributeError: module 'config_loader' has no attribute 'list_printers'`. `release.sh` now syncs `config_loader.py` into the Windows build repository together with the other source files.
+
+---
+
 ## [0.9.8] – 2026-05-12
 
 ### New

LICENSE

@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<https://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.

NOTICE.md

@@ -0,0 +1,68 @@
+# NOTICE
+
+This repository contains code licensed under the **GNU General Public License
+v3.0** (see [LICENSE](LICENSE)) and material that is **not** covered by that
+license. Read this file before forking, distributing, or building from source.
+
+## What is GPLv3-licensed
+
+The original work in this repository:
+
+- `bridge/` — Bridge daemon, MQTT client, web UI, configuration loader,
+  protocol implementation
+- `tools/` — `extract_credentials`, `fetch_credentials` utilities
+- `_archive/tools/kx_printer_emulator.py` — printer emulator
+- `Dockerfile`, `docker-compose.yml`, `release.sh`, build scripts
+- Documentation files (`README*`, `CHANGELOG*`, `_archive/RE/06_docs/*`)
+- `kobra_x_orcaslicer_preset.zip` — slicer profile derived from public OrcaSlicer
+  presets, adapted for the Kobra X
+
+You are free to use, modify and redistribute this code under the terms of
+GPLv3 — including for commercial purposes — provided downstream forks remain
+under GPLv3 and source is made available to recipients.
+
+## What is **not** GPLv3-licensed
+
+The following items are **third-party material**, included here only for
+**interoperability purposes** as permitted under §69e UrhG (German Copyright
+Act; equivalent: EU Software Directive Art. 6, US fair-use for reverse
+engineering for interoperability):
+
+- **`bridge/anycubic_slicer.crt`** and **`bridge/anycubic_slicer.key`** —
+  TLS client certificate and private key extracted from Anycubic Slicer Next
+  binaries. Copyright remains with Anycubic / their respective authors.
+  Included solely to enable the bridge to authenticate against the LAN MQTT
+  broker that runs on a Kobra X printer the end-user already owns. No
+  ownership claim is made.
+
+- **MQTT protocol structures, payload formats and signature algorithms** —
+  reverse-engineered from `Workbench.dll` / `cloud_mqtt.dll` of the Anycubic
+  Slicer Next application. The protocol itself is documented in
+  `_archive/RE/06_docs/` for transparency. Any reproduction of code or
+  protocol details serves interoperability only.
+
+- **AMS material naming, slot numbering, GCode markers (`EXCLUDE_OBJECT_*`)**
+  — follow conventions established by Anycubic and the wider Klipper
+  ecosystem; usage here is purely interoperability-driven.
+
+## What this means for forks
+
+If you fork KX-Bridge:
+
+1. **You must keep this `NOTICE.md` and `LICENSE` file** in your fork.
+2. Your modifications and additions to the bridge code, UI, tools and docs
+   inherit GPLv3 — they must be made available under the same license if you
+   distribute them.
+3. The third-party material listed above is **not** something you can
+   relicense; it stays under the original (implicit) rights of its owners.
+4. Removing the certificates and rebuilding them from your own Anycubic
+   Slicer installation is the safest path for redistribution if you are
+   unsure about the §69e situation in your jurisdiction.
+
+## Disclaimer
+
+This project is independent, non-commercial reverse-engineering work. It is
+**not** affiliated with, endorsed by, or supported by Anycubic Technology
+Co., Ltd. or any of their subsidiaries.
+
+All trademarks are property of their respective owners.

README.de.md

@@ -1,160 +1,194 @@
-<p align="center"><img src="knlogo.png" alt="KX-Bridge Logo" width="180"/></p>
+<div align="center">
 
-# KX-Bridge – Anycubic Kobra X
+<img src="knlogo.png" alt="KX-Bridge" width="160"/>
 
-**Version:** 0.9.8
+# KX-Bridge
 
-Steuere deinen **Anycubic Kobra X** mit OrcaSlicer — ohne Klipper, ohne Raspberry Pi.  
-KX-Bridge ist eine Moonraker-kompatible Bridge die direkt mit dem Drucker kommuniziert.
+**Steuere deinen Anycubic Kobra X mit OrcaSlicer — ohne Klipper, ohne Raspberry Pi.**
+
+Eine Moonraker-kompatible Bridge, die direkt mit dem Drucker spricht.
+
+<sub>🇬🇧 <a href="README.md">English version</a></sub>
+
+<br>
+
+[![Ko-fi](https://img.shields.io/badge/Ko--fi-Support%20this%20project-FF5E5B?style=for-the-badge&logo=ko-fi&logoColor=white)](https://ko-fi.com/viewitde)
+&nbsp;
+[![Releases](https://img.shields.io/badge/Download-Releases-2EA043?style=for-the-badge&logo=gitea&logoColor=white)](https://gitea.it-drui.de/viewit/KX-Bridge-Release/releases)
+&nbsp;
+[![Video](https://img.shields.io/badge/YouTube-Tutorial-FF0000?style=for-the-badge&logo=youtube&logoColor=white)](https://www.youtube.com/watch?v=1Ql4wfH27fM)
+
+<sub>Gefällt dir KX-Bridge? Ein Kaffee auf <a href="https://ko-fi.com/viewitde">Ko-fi</a> hält das Projekt am Leben. ☕</sub>
+
+</div>
 
 ---
 
-## Schnellstart in 3 Schritten
+## ✨ Was kann KX-Bridge?
 
-### Schritt 1 – Drucker vorbereiten
+| | Feature |
+|---|---|
+| 🖨️ | **Druckersteuerung** — Start, Pause, Resume, Abbruch, Temperaturen, Druckgeschwindigkeit |
+| 📊 | **Live-Status** — Temperatur, Fortschritt, Layer, Restzeit, Kamera-Stream |
+| 🎨 | **AMS / Multicolor** — Filament-Slots, Per-Kanal-Remapping, MMU-Emulation für OrcaSlicer Filament-Sync |
+| 🗂️ | **GCode-Browser** — hochgeladene Dateien mit Thumbnail, Druckhistorie, Suche & Filter |
+| 🧩 | **Multi-Printer** — mehrere Drucker in **einer** Bridge-Instanz, Umschalten per Dropdown |
+| ➕ | **Drucker hinzufügen per Klick** — nur die IP eingeben, Zugangsdaten werden automatisch importiert |
+| 🔄 | **Self-Update** — neue Versionen direkt im Browser installieren |
+| 🌐 | **OrcaSlicer** — volles Moonraker-Protokoll (HTTP + WebSocket), DE/EN UI |
 
-Den Kobra X in den LAN-Modus versetzen:  
-**Drucker-Display → Einstellungen → LAN-Modus einschalten**
+---
 
-### Schritt 2 – Credentials holen
+## 🚀 Schnellstart
 
-Die MQTT-Zugangsdaten sind druckerspezifisch und an die Hardware gebunden.
+### 1. Drucker vorbereiten
 
-**Option A – fetch_credentials (empfohlen):**
+LAN-Modus am Kobra X aktivieren:
+**Drucker-Display → Einstellungen → LAN-Modus aktivieren**
+
+### 2. Bridge starten
+
+**Docker (empfohlen):**
+```bash
+docker compose up -d
+```
+
+**Linux-Binary (kein Docker):**
+```bash
+chmod +x kx-bridge && ./kx-bridge
+```
+
+**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,
+> GCode-Store) jeweils neben dem Programm. Einfach den ganzen Ordner kopieren = umziehen.
+
+**Python direkt:**
+```bash
+pip install -r bridge/requirements.txt
+python bridge/kobrax_moonraker_bridge.py
+```
+
+### 3. Drucker einrichten
+
+Web-UI öffnen: **`http://BRIDGE-IP:7125`**
+
+Beim Erststart erscheint der **Drucker-Tab** mit *„+ Drucker hinzufügen"* — einfach die
+IP-Adresse des Druckers eingeben, der Rest (Username, Passwort, Device-ID) wird automatisch
+vom Drucker geholt und entschlüsselt. Fertig.
+
+> Mehrere Drucker? Einfach mehrfach *„+ Drucker hinzufügen"* — jeder bekommt seinen eigenen
+> Port (7125, 7126, …) und ist im Header-Dropdown auswählbar.
+
+### 4. OrcaSlicer verbinden
+
+Drucker → Verbindungstyp **Moonraker** → Host: `http://BRIDGE-IP:7125`
+
+> ⚠️ Verbindungstyp muss **Moonraker** sein (nicht „Bambu" oder „Klipper").
+> Vollständige URL inkl. `http://` und Port `:7125` im Host-Feld eintragen.
+
+---
+
+## 📺 Video-Tutorial
+
+[![KX-Bridge Setup & Usage](https://img.youtube.com/vi/1Ql4wfH27fM/hqdefault.jpg)](https://www.youtube.com/watch?v=1Ql4wfH27fM)
+
+---
+
+## 🔧 Zugangsdaten manuell ermitteln
+
+Normalerweise nicht nötig — *„+ Drucker hinzufügen"* macht das automatisch. Falls doch:
 
 ```bash
 fetch_credentials --ip 192.168.x.x --write-config
 ```
+Holt die Zugangsdaten per HTTP direkt vom Drucker und schreibt sie in `config/config.ini`.
+Nur die Drucker-IP nötig, kein Slicer.
 
-Holt die Credentials direkt per HTTP vom Drucker und schreibt sie automatisch in `config/config.ini`. Benötigt nur die Drucker-IP — kein Slicer nötig.
+Alternativ (wenn die IP unbekannt ist): AnycubicSlicerNext öffnen, Drucker verbinden,
+dann `extract_credentials` ausführen → gibt Username, Passwort, Device-ID und IP aus.
 
-**Option B – extract_credentials (wenn Drucker-IP unbekannt):**
+> **Downloads:** [Releases](https://gitea.it-drui.de/viewit/KX-Bridge-Release/releases) → `fetch_credentials` / `extract_credentials` (Linux & Windows)
 
-1. **AnycubicSlicerNext** öffnen und Drucker verbinden (bis Status angezeigt wird)
-2. **`extract_credentials`** ausführen — gibt Username, Password, Device-ID und Drucker-IP aus
-3. Werte im Web-UI eintragen (⚙-Menü)
+---
 
-> **Download:** [gitea.it-drui.de/viewit/KX-Bridge-Release/releases](https://gitea.it-drui.de/viewit/KX-Bridge-Release/releases) → `fetch_credentials` / `extract_credentials` (Linux & Windows) im jeweiligen Release-Asset
-
-### Schritt 3 – Bridge starten
+## ⚙️ Nützliche Befehle
 
 ```bash
-./start.sh
-```
-
-Das Skript baut das Docker-Image automatisch beim ersten Aufruf.
-
-**Web-UI öffnen:** `http://BRIDGE-IP:7125`  
-→ Das ⚙-Menü öffnet sich beim ersten Start automatisch  
-→ Bei Option B: Credentials aus Schritt 2 eintragen → **Speichern & Neustart**
-
-**OrcaSlicer verbinden:**  
-Drucker → Verbindungstyp **Moonraker** → Host: `http://BRIDGE-IP:7125`
-
-> **Wichtig:** Verbindungstyp muss **Moonraker** sein (nicht „Bambu" oder „Klipper").  
-> Im Host-Feld vollständige URL mit `http://` und Port `:7125` angeben.
-
----
-
-## 📺 Video Tutorial
-
-[![KX-Bridge Setup & Bedienung](https://img.youtube.com/vi/1Ql4wfH27fM/hqdefault.jpg)](https://www.youtube.com/watch?v=1Ql4wfH27fM)
-
----
-
-## ⚠️ Update von 0.9.1 oder älter
-
-Ab **0.9.2** speichert KX-Bridge Einstellungen in `config/config.ini` statt in `.env`.
-
-**Migration erfolgt automatisch** — keine manuelle Aktion nötig:
-- Beim ersten Start nach dem Update liest die Bridge die vorhandene `.env` und erstellt `config/config.ini` automatisch
-- Einstellungen bleiben ab sofort nach `docker-compose restart` und zukünftigen Updates erhalten
-- Die `.env`-Datei bleibt read-only gemountet als Migrationsquelle — kann liegen bleiben
-- Zum manuellen Anlegen einer `config.ini`: Vorlage unter `config/config.ini.example` kopieren
-
----
-
-## Was wird unterstützt?
-
-| Funktion | Details |
-|----------|---------|
-| Druckerstatus | Temperatur, Fortschritt, Zustand, Restzeit |
-| Drucksteuerung | Start, Pause, Fortsetzen, Abbrechen |
-| Temperaturregelung | Nozzle und Bett während des Drucks |
-| Druckgeschwindigkeit | Leise / Normal / Sport |
-| AMS-Farbwechsel | Filament einziehen / ausziehen |
-| Licht & Lüfter | Drucklicht und Lüfterdrehzahl |
-| Web-UI | Dashboard, Achsensteuerung, Kameraansicht |
-| Self-Update | Neue Versionen direkt im Browser installieren |
-| OrcaSlicer | Moonraker-Protokoll (HTTP + WebSocket) |
-
----
-
-## Alternativen zu Docker
-
-**Linux Binary** (kein Docker nötig):
-```bash
-chmod +x kx-bridge
-./kx-bridge
-```
-
-**Python direkt:**
-```bash
-pip install aiohttp
-python bridge/kobrax_moonraker_bridge.py
-```
-
-Web-UI jeweils unter `http://localhost:7125` — ⚙-Menü führt durch die Erstkonfiguration.
-
----
-
-## Nützliche Befehle
-
-```bash
-# Logs anzeigen
-docker-compose logs -f
-
-# Bridge stoppen
-docker-compose down
-
-# Bridge neu starten (nach Update)
-./start.sh
+docker compose logs -f      # Logs anzeigen
+docker compose down         # Bridge stoppen
+docker compose up -d --build # Bridge neu bauen & starten (nach Update)
 ```
 
 ---
 
-## Fehlerbehebung
+## 🩹 Troubleshooting
 
-**„Falsche MQTT-Zugangsdaten"** beim Start:
-- `fetch_credentials --ip <Drucker-IP> --write-config` erneut ausführen und Bridge neu starten
-- Wenn IP unbekannt: AnycubicSlicerNext neu starten, Drucker verbinden, `extract_credentials` erneut ausführen
-- Nur die IP-Adresse ins Feld eintragen, keinen Port (✗ `192.168.1.102:9883` → ✓ `192.168.1.102`)
+<details>
+<summary><b>"Falsche MQTT-Zugangsdaten" beim Start</b></summary>
 
-**Drucker nicht gefunden / kein LAN-Modus:**
-- Am Drucker-Display: Einstellungen → LAN-Modus einschalten
+- Drucker über *„+ Drucker hinzufügen"* erneut hinzufügen, oder
+  `fetch_credentials --ip <ip> --write-config` ausführen und Bridge neu starten
+- Nur die IP-Adresse eingeben, ohne Port (✗ `192.168.1.102:9883` → ✓ `192.168.1.102`)
+</details>
+
+<details>
+<summary><b>Drucker nicht gefunden / kein LAN-Modus</b></summary>
+
+- Am Drucker-Display: Einstellungen → LAN-Modus aktivieren
 - Drucker und Bridge müssen im selben Netzwerk sein
+</details>
+
+<details>
+<summary><b>Docker: Permission denied</b></summary>
 
-**Docker: Permission denied:**
 ```bash
-sudo usermod -aG docker $USER  # dann neu einloggen
+sudo usermod -aG docker $USER   # danach aus- und wieder einloggen
 ```
+</details>
+
+<details>
+<summary><b>Upgrade von 0.9.1 oder älter</b></summary>
+
+Ab 0.9.2 speichert KX-Bridge die Einstellungen in `config/config.ini` statt `.env`.
+Die Migration läuft automatisch beim ersten Start nach dem Upgrade — keine Aktion nötig.
+</details>
 
 ---
 
-## Sicherheitshinweise
+## 🔒 Sicherheit
 
-- Die Bridge ist im lokalen Netzwerk erreichbar unter `http://<Host-IP>:7125` — nicht ins Internet freigeben
-- `config/config.ini` enthält Drucker-Credentials — nicht öffentlich teilen
-- Credentials haben keinen Zugang zu Anycubic-Cloud-Diensten
+- Die Bridge ist im lokalen Netzwerk unter `http://<host-IP>:7125` erreichbar — **nicht** ins Internet exposen
+- `config/config.ini` enthält Drucker-Zugangsdaten — nicht öffentlich teilen
+- Die Zugangsdaten geben **keinen** Zugriff auf Anycubic-Cloud-Dienste
 
 ---
 
-## Lizenz & Rechtliches
+## 📄 Lizenz
 
-Interoperabilitätsforschung gem. §69e UrhG — ausschließlich private, nicht-kommerzielle Nutzung.
+[![License: GPL v3](https://img.shields.io/badge/License-GPL_v3-blue.svg)](LICENSE)
 
-<p align="center">
-  <a href="https://ko-fi.com/viewitde">
-    <img src="https://ko-fi.com/img/githubbutton_sm.svg" alt="Ko-fi Support"/>
-  </a>
-</p>
+KX-Bridge steht unter der **GNU General Public License v3.0** ([LICENSE](LICENSE)).
+Forks und Erweiterungen müssen bei Weitergabe ebenfalls unter GPLv3 stehen.
+
+Die MQTT-Protokoll-Implementierung ist das Ergebnis unabhängiger
+Reverse-Engineering-Arbeit zur Herstellung der Interoperabilität (§69e UrhG /
+EU-Softwarerichtlinie Art. 6). Drittmaterial im Repository (Anycubic-
+TLS-Zertifikate) fällt **nicht** unter die GPLv3 und ist ausschließlich
+enthalten, um die Authentifizierung am eigenen Drucker zu ermöglichen.
+Details + Disclaimer in [NOTICE.md](NOTICE.md).
+
+Dieses Projekt ist unabhängig und steht in keinem Zusammenhang mit Anycubic.
+
+<div align="center">
+<br>
+
+**Wenn dir KX-Bridge hilft, freut sich das Projekt über Unterstützung:**
+
+[![Ko-fi](https://ko-fi.com/img/githubbutton_sm.svg)](https://ko-fi.com/viewitde)
+
+</div>

README.md

@@ -1,47 +1,94 @@
-<p align="center"><img src="knlogo.png" alt="KX-Bridge Logo" width="180"/></p>
+<div align="center">
 
-# KX-Bridge – Anycubic Kobra X
+<img src="knlogo.png" alt="KX-Bridge" width="160"/>
 
-**Version:** 0.9.8
+# KX-Bridge
 
-Control your **Anycubic Kobra X** with OrcaSlicer — no Klipper, no Raspberry Pi.  
-KX-Bridge is a Moonraker-compatible bridge that communicates directly with the printer.
+**Control your Anycubic Kobra X with OrcaSlicer — no Klipper, no Raspberry Pi.**
+
+A Moonraker-compatible bridge that talks directly to the printer.
+
+<sub>🇩🇪 <a href="README.de.md">Deutsche Version</a></sub>
+
+<br>
+
+[![Ko-fi](https://img.shields.io/badge/Ko--fi-Support%20this%20project-FF5E5B?style=for-the-badge&logo=ko-fi&logoColor=white)](https://ko-fi.com/viewitde)
+&nbsp;
+[![Releases](https://img.shields.io/badge/Download-Releases-2EA043?style=for-the-badge&logo=gitea&logoColor=white)](https://gitea.it-drui.de/viewit/KX-Bridge-Release/releases)
+&nbsp;
+[![Video](https://img.shields.io/badge/YouTube-Tutorial-FF0000?style=for-the-badge&logo=youtube&logoColor=white)](https://www.youtube.com/watch?v=1Ql4wfH27fM)
+
+<sub>Like KX-Bridge? A coffee on <a href="https://ko-fi.com/viewitde">Ko-fi</a> keeps the project alive. ☕</sub>
+
+</div>
 
 ---
 
-## Quick Start in 3 Steps
+## ✨ Features
 
-### Step 1 – Prepare the printer
+| | |
+|---|---|
+| 🖨️ | **Printer control** — start, pause, resume, cancel, temperatures, print speed |
+| 📊 | **Live status** — temperature, progress, layers, remaining time, camera stream |
+| 🎨 | **AMS / multicolor** — filament slots, per-channel remapping, MMU emulation for OrcaSlicer filament sync |
+| 🗂️ | **GCode browser** — uploaded files with thumbnails, print history, search & filter |
+| 🧩 | **Multi-printer** — multiple printers in **one** bridge instance, switch via dropdown |
+| ➕ | **Add a printer with one click** — just enter the IP, credentials are imported automatically |
+| 🔄 | **Self-update** — install new versions directly in the browser |
+| 🌐 | **OrcaSlicer** — full Moonraker protocol (HTTP + WebSocket), EN/DE UI |
+
+---
+
+## 🚀 Quick Start
+
+### 1. Prepare the printer
 
 Enable LAN mode on the Kobra X:
 **Printer display → Settings → Enable LAN mode**
 
-### Step 2 – Get credentials
-
-The MQTT credentials are printer-specific. Here's how to get them:
-
-1. Open **AnycubicSlicerNext** and connect the printer (wait until status is shown)
-2. Run **`extract_credentials.exe`** (Windows) or **`extract_credentials`** (Linux) — outputs Username, Password, Device ID and printer IP
-3. Note / copy the values
-
-> **Download:** [gitea.it-drui.de/viewit/KX-Bridge-Release/releases](https://gitea.it-drui.de/viewit/KX-Bridge-Release/releases) → `extract_credentials.exe` (Windows) / `extract_credentials` (Linux) in the release assets
-
-### Step 3 – Start the bridge
+### 2. Start the bridge
 
+**Docker (recommended):**
 ```bash
-./start.sh
+docker compose up -d
 ```
 
-The script builds the Docker image automatically on first run.
+**Linux binary (no Docker):**
+```bash
+chmod +x kx-bridge && ./kx-bridge
+```
 
-**Open Web-UI:** `http://BRIDGE-IP:7125`  
-→ The ⚙ menu opens automatically on first start  
-→ Enter credentials from Step 2 → **Save & Restart**
+**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)
+> live next to the program. Copy the whole folder = move the installation.
+
+**Python directly:**
+```bash
+pip install -r bridge/requirements.txt
+python bridge/kobrax_moonraker_bridge.py
+```
+
+### 3. Set up the printer
+
+Open the Web UI: **`http://BRIDGE-IP:7125`**
+
+On first start the **Printers tab** shows *"+ Add printer"* — just enter the printer's IP
+address, the rest (username, password, device ID) is fetched from the printer and decrypted
+automatically. Done.
+
+> More than one printer? Just click *"+ Add printer"* again — each gets its own port
+> (7125, 7126, …) and is selectable from the header dropdown.
+
+### 4. Connect OrcaSlicer
 
-**Connect OrcaSlicer:**  
 Printer → Connection type **Moonraker** → Host: `http://BRIDGE-IP:7125`
 
-> **Important:** Connection type must be **Moonraker** (not "Bambu" or "Klipper").  
+> ⚠️ Connection type must be **Moonraker** (not "Bambu" or "Klipper").
 > Enter the full URL including `http://` and port `:7125` in the host field.
 
 ---
@@ -52,98 +99,97 @@ Printer → Connection type **Moonraker** → Host: `http://BRIDGE-IP:7125`
 
 ---
 
-## ⚠️ Upgrading from 0.9.1 or earlier
+## 🔧 Getting credentials manually
 
-Starting with **0.9.2**, KX-Bridge stores settings in `config/config.ini` instead of `.env`.
+Normally not needed — *"+ Add printer"* does this automatically. If you do need it:
 
-**Migration is automatic** — no manual action required:
-- On first start after upgrade, the bridge reads your existing `.env` and creates `config/config.ini` automatically
-- Settings now survive `docker-compose restart` and future updates
-- The `.env` file stays mounted read-only as a migration source — you can keep it in place
-- If you want to create a `config.ini` manually: copy `config/config.ini.example`
-
----
-
-## What's supported?
-
-| Feature | Details |
-|---------|---------|
-| Printer status | Temperature, progress, state, remaining time |
-| Print control | Start, pause, resume, cancel |
-| Temperature control | Nozzle and bed during print |
-| Print speed | Silent / Normal / Sport |
-| AMS filament change | Load / unload filament |
-| Light & fan | Print light and fan speed |
-| Web-UI | Dashboard, motion control, camera view |
-| Self-update | Install new versions directly in the browser |
-| OrcaSlicer | Moonraker protocol (HTTP + WebSocket) |
-
----
-
-## Alternatives to Docker
-
-**Linux binary** (no Docker needed):
 ```bash
-chmod +x kx-bridge
-./kx-bridge
+fetch_credentials --ip 192.168.x.x --write-config
 ```
+Fetches the credentials directly from the printer via HTTP and writes them to `config/config.ini`.
+Only the printer IP is required, no slicer.
 
-**Python directly:**
-```bash
-pip install aiohttp
-python bridge/kobrax_moonraker_bridge.py
-```
+Alternatively (if the IP is unknown): open AnycubicSlicerNext, connect the printer, then run
+`extract_credentials` → outputs username, password, device ID and the printer IP.
 
-Web-UI available at `http://localhost:7125` — the ⚙ menu guides through initial setup.
+> **Downloads:** [Releases](https://gitea.it-drui.de/viewit/KX-Bridge-Release/releases) → `fetch_credentials` / `extract_credentials` (Linux & Windows)
 
 ---
 
-## Useful commands
+## ⚙️ Useful commands
 
 ```bash
-# Show logs
-docker-compose logs -f
-
-# Stop bridge
-docker-compose down
-
-# Restart bridge (after update)
-./start.sh
+docker compose logs -f       # show logs
+docker compose down          # stop the bridge
+docker compose up -d --build # rebuild & start (after an update)
 ```
 
 ---
 
-## Troubleshooting
+## 🩹 Troubleshooting
 
-**"Wrong MQTT credentials"** on start:
-- Restart AnycubicSlicerNext, reconnect the printer, run `extract_credentials` again
+<details>
+<summary><b>"Wrong MQTT credentials" on start</b></summary>
+
+- Re-add the printer via *"+ Add printer"*, or run
+  `fetch_credentials --ip <ip> --write-config` and restart the bridge
 - Enter only the IP address, no port (✗ `192.168.1.102:9883` → ✓ `192.168.1.102`)
+</details>
+
+<details>
+<summary><b>Printer not found / no LAN mode</b></summary>
 
-**Printer not found / no LAN mode:**
 - On the printer display: Settings → Enable LAN mode
 - Printer and bridge must be on the same network
+</details>
+
+<details>
+<summary><b>Docker: Permission denied</b></summary>
 
-**Docker: Permission denied:**
 ```bash
-sudo usermod -aG docker $USER  # then log out and back in
+sudo usermod -aG docker $USER   # then log out and back in
 ```
+</details>
+
+<details>
+<summary><b>Upgrading from 0.9.1 or earlier</b></summary>
+
+Starting with 0.9.2, KX-Bridge stores settings in `config/config.ini` instead of `.env`.
+Migration runs automatically on first start after the upgrade — no action required.
+</details>
 
 ---
 
-## Security
+## 🔒 Security
 
-- The bridge is accessible on the local network at `http://<host-IP>:7125` — do not expose to the internet
+- 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
-- Credentials do not grant access to Anycubic cloud services
+- The credentials do **not** grant access to Anycubic cloud services
 
 ---
 
-## License
+## 📄 License
 
-Interoperability research under §69e UrhG — private, non-commercial use only.
+[![License: GPL v3](https://img.shields.io/badge/License-GPL_v3-blue.svg)](LICENSE)
 
-<p align="center">
-  <a href="https://ko-fi.com/viewitde">
-    <img src="https://ko-fi.com/img/githubbutton_sm.svg" alt="Ko-fi Support"/>
-  </a>
-</p>
+KX-Bridge is released under the **GNU General Public License v3.0**. See
+[LICENSE](LICENSE) for the full text. Forks and modifications must remain
+under GPLv3 if redistributed.
+
+The MQTT protocol implementation is the result of independent
+reverse-engineering for interoperability purposes (§69e UrhG / EU Software
+Directive Art. 6). Third-party material in the repository (Anycubic TLS
+certificates) is **not** covered by GPLv3 and is included solely to enable
+authentication against printers the end-user already owns. See
+[NOTICE.md](NOTICE.md) for details and disclaimer.
+
+This project is independent and not affiliated with Anycubic.
+
+<div align="center">
+<br>
+
+**If KX-Bridge helps you, the project appreciates your support:**
+
+[![Ko-fi](https://ko-fi.com/img/githubbutton_sm.svg)](https://ko-fi.com/viewitde)
+
+</div>

VERSION

@@ -1 +1 @@
-0.9.8
+0.9.11

kobrax_client.py

@@ -14,6 +14,13 @@ Verwendung:
   info = client.query_info()
   print(info["data"]["temp"])
   client.disconnect()
+
+────────────────────────────────────────────────────────────────────────────
+Copyright (C) 2026 viewit (KX-Bridge contributors)
+
+Licensed under GPLv3 — see LICENSE in the project root.
+Protocol reverse-engineered for interoperability (§69e UrhG / EU Software
+Directive Art. 6). Not affiliated with Anycubic. See NOTICE.md.
 """
 
 import hashlib
@@ -458,6 +465,20 @@ class KobraXClient:
     def stop_print(self, taskid: str = "-1") -> dict | None:
         return self.publish("print", "stop", {"taskid": taskid})
 
+    # -- Part-Skip ("Exclude Object") ---------------------------------------
+
+    def query_skip_objects(self) -> dict | None:
+        """Fragt den Drucker nach der aktuellen Objekt-/Skip-Liste."""
+        return self.publish("skip", "query_obj")
+
+    def skip_objects(self, names: list[str]) -> dict | None:
+        """Überspringt die genannten Objekte – auch mid-print möglich.
+
+        Namen entsprechen den EXCLUDE_OBJECT_DEFINE NAME=… Einträgen
+        im GCode-Header bzw. file_details.objects_skip_parts.
+        """
+        return self.publish("skip", "start", {"objects_skip_parts": list(names)})
+
     # -- G-Code Upload -------------------------------------------------------
 
     def upload_gcode(self, filepath: str, remote_filename: str | None = None,