pycentauri 0.4.0__tar.gz → 0.4.1__tar.gz

{pycentauri-0.4.0 → pycentauri-0.4.1}/CHANGELOG.md

@@ -6,6 +6,24 @@ Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [0.4.1] - 2026-04-22
+
+### Changed
+- README audited end-to-end for accuracy: removed claims about a
+  `~/.config/pycentauri/config.toml` loader that was never implemented,
+  an `upload_file` / `list_files` MCP tool that doesn't exist, and a
+  `centauri files` command that was a stub. Added the RTSP endpoints
+  (`/api/rtsp/*`) and the FastAPI auto-docs URLs to the endpoint table,
+  plus a note that the RTSP bridge itself isn't gated by
+  `--enable-control`.
+- Updated the package tagline on PyPI and in the module docstring to
+  reflect all six surfaces rather than just three.
+
+### Removed
+- The stub `centauri files` CLI command. It always exited with
+  "not yet supported" and was only there to reserve the name; not
+  worth the README lie.
+
 ## [0.4.0] - 2026-04-22
 
 ### Added

{pycentauri-0.4.0 → pycentauri-0.4.1}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: pycentauri
-Version: 0.4.0
-Summary: Python client and MCP server for Elegoo Centauri Carbon 3D printers
+Version: 0.4.1
+Summary: Local-network toolkit for Elegoo Centauri Carbon 3D printers: async Python client, CLI, MCP server, REST/SSE HTTP server, web UI, and RTSP bridge
 Project-URL: Homepage, https://github.com/bjan/pycentauri
 Project-URL: Repository, https://github.com/bjan/pycentauri
 Project-URL: Issues, https://github.com/bjan/pycentauri/issues
@@ -48,8 +48,10 @@ Description-Content-Type: text/markdown
 
 # pycentauri
 
-Python client, CLI, and MCP server for the [Elegoo Centauri
-Carbon](https://www.elegoo.com/) 3D printer.
+Local-network toolkit for the [Elegoo Centauri
+Carbon](https://www.elegoo.com/) 3D printer. Python library, CLI, MCP
+server, REST/SSE server, built-in web UI, and an RTSP bridge — all
+powered by the same async client.
 
 `pycentauri` speaks the printer's native SDCP v3 protocol over its local
 WebSocket (port 3030) — no cloud account required. It exposes six surfaces:
@@ -68,18 +70,21 @@ WebSocket (port 3030) — no cloud account required. It exposes six surfaces:
 > **Status:** alpha. The protocol has been reverse-engineered from the official
 > [`elegoo-link`](https://github.com/ELEGOO-3D/elegoo-link) C++ SDK and the
 > [`CentauriLink`](https://github.com/CentauriLink/Centauri-Link) project. It
-> works against the original Centauri Carbon on current firmware. The newer
-> Centauri Carbon 2 (which uses MQTT) is not supported.
+> works against the original Centauri Carbon on current firmware (tested on
+> V1.1.46). The newer Centauri Carbon 2 (which uses MQTT) is not supported.
 
 ## Install
 
 ```sh
 pip install pycentauri                    # library + CLI
 pip install "pycentauri[mcp]"             # + MCP server
-pip install "pycentauri[server]"          # + HTTP REST/SSE server
-pip install "pycentauri[mcp,server]"      # everything
+pip install "pycentauri[server]"          # + HTTP REST/SSE server + web UI
+pip install "pycentauri[mcp,server]"      # all Python surfaces
 ```
 
+The RTSP bridge additionally requires [MediaMTX](https://github.com/bluenviron/mediamtx/releases)
+and `ffmpeg` on `$PATH` — see the RTSP section below for install hints.
+
 ## Quick start — CLI
 
 ```sh
@@ -96,17 +101,19 @@ centauri watch --host 192.168.1.209
 # Grab a webcam snapshot
 centauri snapshot --host 192.168.1.209 shot.jpg
 
-# Files on the printer
-centauri files --host 192.168.1.209
+# Printer attributes (model, firmware, mainboard ID, capabilities)
+centauri attributes --host 192.168.1.209
 
-# Control actions require --enable-control
+# Control actions — require --enable-control
 centauri print start cube.gcode --host 192.168.1.209 --enable-control
-centauri print pause              --host 192.168.1.209 --enable-control
-centauri print resume             --host 192.168.1.209 --enable-control
-centauri print stop               --host 192.168.1.209 --enable-control
+centauri print pause            --host 192.168.1.209 --enable-control
+centauri print resume           --host 192.168.1.209 --enable-control
+centauri print stop             --host 192.168.1.209 --enable-control
 ```
 
-The host can also come from `PYCENTAURI_HOST` or `~/.config/pycentauri/config.toml`.
+The host can also come from the `PYCENTAURI_HOST` environment variable.
+If neither is set, every command auto-discovers via a 2.5 s UDP broadcast
+and bails out if it finds zero or more than one printer.
 
 ## Quick start — Python
 
@@ -117,26 +124,30 @@ from pycentauri import Printer
 async def main():
     async with await Printer.connect("192.168.1.209") as printer:
         status = await printer.status()
-        print(status.state, status.progress, status.temp_nozzle)
+        print(status.print_status, status.progress, status.temp_nozzle)
 
         jpeg = await printer.snapshot()
         with open("shot.jpg", "wb") as f:
             f.write(jpeg)
 
         async for update in printer.watch():
-            print(update.state, update.progress)
+            print(update.print_status, update.progress)
 
 asyncio.run(main())
 ```
 
+Control actions (`start_print`, `pause`, `resume`, `stop`) require
+`Printer.connect(..., enable_control=True)`.
+
 ## Quick start — HTTP server
 
 ```sh
 # Read-only, bound to loopback so only this box can hit it:
 centauri server --host 192.168.1.209 --port 8787
 
-# Read + write, bound to all interfaces (put a reverse proxy in front):
-centauri server --host 192.168.1.209 --bind 0.0.0.0 --port 8787 --enable-control
+# Read + write + RTSP, bound to all interfaces (put a reverse proxy in front):
+centauri server --host 192.168.1.209 --bind 0.0.0.0 --port 8787 \
+                --enable-control --rtsp
 ```
 
 | Method | Path | Notes |
@@ -144,12 +155,15 @@ centauri server --host 192.168.1.209 --bind 0.0.0.0 --port 8787 --enable-control
 | `GET` | `/` | Redirects to `/ui/` |
 | `GET` | `/ui/` | Built-in web dashboard |
 | `GET` | `/api/info` | Health + version (JSON) |
-| `GET` | `/status` | Latest status push (cached; updates every ~5s) |
+| `GET` | `/status` | Latest status push (cached; updates every ~5 s) |
 | `GET` | `/attributes` | Printer attributes |
 | `GET` | `/snapshot` | `image/jpeg` response |
 | `GET` | `/stream` | MJPEG stream proxied from the printer (embeds in `<img>`) |
 | `GET` | `/discover` | LAN scan |
 | `GET` | `/events/status` | Server-Sent Events stream of pushes |
+| `GET` | `/api/rtsp` | RTSP bridge state (when `--rtsp` is set) |
+| `POST` | `/api/rtsp/{start,stop}` | Start/stop the RTSP bridge (when `--rtsp` is set) |
+| `GET` | `/docs` / `/redoc` | Auto-generated OpenAPI docs |
 | `POST` | `/print/start` | Body: `{"filename": "cube.gcode"}`. Requires `--enable-control`. |
 | `POST` | `/print/{pause,resume,stop}` | Requires `--enable-control`. |
 
@@ -160,7 +174,7 @@ the firmware's 5-slot limit.
 ## Quick start — RTSP bridge
 
 ```sh
-# Install dependencies first:
+# Install system dependencies first:
 #   mediamtx  https://github.com/bluenviron/mediamtx/releases  (or `brew install mediamtx`)
 #   ffmpeg    `brew install ffmpeg` or `apt install ffmpeg`
 
@@ -170,64 +184,79 @@ centauri rtsp --host 192.168.1.209
 
 # Or, integrated with the HTTP server + web UI
 centauri server --host 192.168.1.209 --rtsp --bind 0.0.0.0
-# Web UI gains a STREAM panel with a toggle, a copy-URL button, and live status
-# at http://<this-host>:8787/ui/
+# The web UI gains a STREAM panel with a start/stop toggle, a copy-URL button,
+# and live status: http://<this-host>:8787/ui/
 ```
 
 Open that URL in **VLC** (Media → Open Network Stream), point **Home Assistant**
 at it via the Generic Camera integration, or feed it to **Frigate** / **Jellyfin**
 / **Synology Surveillance** for NVR recording and motion detection.
 
-MediaMTX runs the ffmpeg transcode only while at least one client is actually
-connected, so idle cost is zero. Tunable: `--fps`, `--bitrate`, `--preset`,
-`--path`, `--port`, `--bind`. Run `centauri rtsp --help` (or
-`centauri server --help`) for the full list.
+MediaMTX runs the ffmpeg transcode only while at least one client is
+actually connected, so idle cost is zero. Tunable flags: `--fps`,
+`--bitrate`, `--preset`, `--path`, `--port`, `--bind` (standalone),
+or `--rtsp-fps`, `--rtsp-bitrate`, `--rtsp-path`, `--rtsp-port`,
+`--rtsp-bind` (on `centauri server`). Run `centauri rtsp --help` or
+`centauri server --help` for the full list.
 
 ## Quick start — MCP
 
 Register the server with your agent. With Claude Code:
 
 ```sh
-claude mcp add pycentauri -- python -m pycentauri.mcp
-# or, with control actions enabled (gives the agent start/pause/stop/upload):
-claude mcp add pycentauri -- python -m pycentauri.mcp --enable-control
+claude mcp add pycentauri --env PYCENTAURI_HOST=192.168.1.209 \
+    -- python -m pycentauri.mcp
+
+# Or, with control actions enabled (gives the agent start/pause/resume/stop):
+claude mcp add pycentauri --env PYCENTAURI_HOST=192.168.1.209 \
+    -- python -m pycentauri.mcp --enable-control
 ```
 
-Set `PYCENTAURI_HOST` in your MCP server env so the agent can't target an
-arbitrary IP. The server exposes these tools:
+Setting `PYCENTAURI_HOST` in the MCP server's launch env means the agent
+can't be tricked into targeting an arbitrary IP through prompt injection —
+the host is pinned at spawn time. Tools exposed:
 
 | Tool | Always available | Description |
 |---|---|---|
 | `get_status` | yes | State, temperatures, progress, elapsed/remaining |
-| `get_attributes` | yes | Model, firmware, mainboard ID |
-| `list_files` | yes | Files stored on the printer |
-| `get_snapshot` | yes | Webcam frame as MCP `Image` content |
+| `get_attributes` | yes | Model, firmware, mainboard ID, capabilities |
+| `get_snapshot` | yes | Webcam frame as MCP `Image` content (LLMs see the picture) |
 | `discover_printers` | yes | LAN scan |
-| `start_print` | only with `--enable-control` | Starts a print |
+| `start_print` | only with `--enable-control` | Starts a print from a file already on the printer |
 | `pause_print` | only with `--enable-control` | Pauses the current print |
 | `resume_print` | only with `--enable-control` | Resumes a paused print |
 | `stop_print` | only with `--enable-control` | Stops the current print |
-| `upload_file` | only with `--enable-control` | Uploads a file to the printer |
+
+Control tools aren't just gated — they're not *registered* without the
+flag, so an LLM that wasn't given the `--enable-control` launch can't see
+them in the tool list at all.
 
 ## Safety
 
-Control actions are gated behind an explicit `enable_control=True` (library) or
-`--enable-control` flag (CLI / MCP). Destructive MCP tools are not even
-registered when the flag is off, so an LLM never sees them. Still: leaving a
-printer running unattended with write-capable agents is your responsibility.
+Printer control actions are gated behind an explicit `enable_control=True`
+(library) or `--enable-control` flag (CLI / MCP). Destructive MCP tools
+aren't registered when the flag is off, so an LLM never sees them. Still:
+leaving a printer running unattended with write-capable agents is your
+responsibility, as is securing the HTTP surface (it's unauthenticated — put
+a reverse proxy with auth in front if you expose it beyond loopback).
+
+The RTSP bridge itself isn't gated by `--enable-control` because it only
+reads the webcam feed and doesn't change printer state; it's enabled
+per-server via the `--rtsp` flag.
 
 ## Known firmware quirks
 
 - **5 concurrent WebSocket connections max.** The printer's SDCP server
   accepts up to 5 open WebSockets on port 3030; the 6th returns HTTP 500
   with body `"too many client"`. Slots release immediately when a
-  connection closes — the CLI and MCP server each open/close one per
-  invocation, so this is almost never a problem in practice.
+  connection closes — the CLI each opens and closes one per invocation,
+  the HTTP and MCP servers hold a single long-lived one, so this is
+  almost never a problem in practice.
 - **Paused / errored states don't auto-push Attributes.** The printer only
   sends its `Attributes` frame spontaneously while idle or printing. In
   paused and errored states it stays silent until asked. Since every SDCP
-  command needs the printer's `MainboardID`, the client takes care of this
-  by pre-seeding the mainboard ID from a UDP discovery on every connect
+  command needs the printer's `MainboardID`, the client handles this by
+  pre-seeding the mainboard ID from a UDP discovery on every connect
   (as of v0.1.1). If you call `Printer.connect()` directly without
   discovery, pass `mainboard_id=` yourself.
 

{pycentauri-0.4.0 → pycentauri-0.4.1}/README.md

@@ -1,7 +1,9 @@
 # pycentauri
 
-Python client, CLI, and MCP server for the [Elegoo Centauri
-Carbon](https://www.elegoo.com/) 3D printer.
+Local-network toolkit for the [Elegoo Centauri
+Carbon](https://www.elegoo.com/) 3D printer. Python library, CLI, MCP
+server, REST/SSE server, built-in web UI, and an RTSP bridge — all
+powered by the same async client.
 
 `pycentauri` speaks the printer's native SDCP v3 protocol over its local
 WebSocket (port 3030) — no cloud account required. It exposes six surfaces:
@@ -20,18 +22,21 @@ WebSocket (port 3030) — no cloud account required. It exposes six surfaces:
 > **Status:** alpha. The protocol has been reverse-engineered from the official
 > [`elegoo-link`](https://github.com/ELEGOO-3D/elegoo-link) C++ SDK and the
 > [`CentauriLink`](https://github.com/CentauriLink/Centauri-Link) project. It
-> works against the original Centauri Carbon on current firmware. The newer
-> Centauri Carbon 2 (which uses MQTT) is not supported.
+> works against the original Centauri Carbon on current firmware (tested on
+> V1.1.46). The newer Centauri Carbon 2 (which uses MQTT) is not supported.
 
 ## Install
 
 ```sh
 pip install pycentauri                    # library + CLI
 pip install "pycentauri[mcp]"             # + MCP server
-pip install "pycentauri[server]"          # + HTTP REST/SSE server
-pip install "pycentauri[mcp,server]"      # everything
+pip install "pycentauri[server]"          # + HTTP REST/SSE server + web UI
+pip install "pycentauri[mcp,server]"      # all Python surfaces
 ```
 
+The RTSP bridge additionally requires [MediaMTX](https://github.com/bluenviron/mediamtx/releases)
+and `ffmpeg` on `$PATH` — see the RTSP section below for install hints.
+
 ## Quick start — CLI
 
 ```sh
@@ -48,17 +53,19 @@ centauri watch --host 192.168.1.209
 # Grab a webcam snapshot
 centauri snapshot --host 192.168.1.209 shot.jpg
 
-# Files on the printer
-centauri files --host 192.168.1.209
+# Printer attributes (model, firmware, mainboard ID, capabilities)
+centauri attributes --host 192.168.1.209
 
-# Control actions require --enable-control
+# Control actions — require --enable-control
 centauri print start cube.gcode --host 192.168.1.209 --enable-control
-centauri print pause              --host 192.168.1.209 --enable-control
-centauri print resume             --host 192.168.1.209 --enable-control
-centauri print stop               --host 192.168.1.209 --enable-control
+centauri print pause            --host 192.168.1.209 --enable-control
+centauri print resume           --host 192.168.1.209 --enable-control
+centauri print stop             --host 192.168.1.209 --enable-control
 ```
 
-The host can also come from `PYCENTAURI_HOST` or `~/.config/pycentauri/config.toml`.
+The host can also come from the `PYCENTAURI_HOST` environment variable.
+If neither is set, every command auto-discovers via a 2.5 s UDP broadcast
+and bails out if it finds zero or more than one printer.
 
 ## Quick start — Python
 
@@ -69,26 +76,30 @@ from pycentauri import Printer
 async def main():
     async with await Printer.connect("192.168.1.209") as printer:
         status = await printer.status()
-        print(status.state, status.progress, status.temp_nozzle)
+        print(status.print_status, status.progress, status.temp_nozzle)
 
         jpeg = await printer.snapshot()
         with open("shot.jpg", "wb") as f:
             f.write(jpeg)
 
         async for update in printer.watch():
-            print(update.state, update.progress)
+            print(update.print_status, update.progress)
 
 asyncio.run(main())
 ```
 
+Control actions (`start_print`, `pause`, `resume`, `stop`) require
+`Printer.connect(..., enable_control=True)`.
+
 ## Quick start — HTTP server
 
 ```sh
 # Read-only, bound to loopback so only this box can hit it:
 centauri server --host 192.168.1.209 --port 8787
 
-# Read + write, bound to all interfaces (put a reverse proxy in front):
-centauri server --host 192.168.1.209 --bind 0.0.0.0 --port 8787 --enable-control
+# Read + write + RTSP, bound to all interfaces (put a reverse proxy in front):
+centauri server --host 192.168.1.209 --bind 0.0.0.0 --port 8787 \
+                --enable-control --rtsp
 ```
 
 | Method | Path | Notes |
@@ -96,12 +107,15 @@ centauri server --host 192.168.1.209 --bind 0.0.0.0 --port 8787 --enable-control
 | `GET` | `/` | Redirects to `/ui/` |
 | `GET` | `/ui/` | Built-in web dashboard |
 | `GET` | `/api/info` | Health + version (JSON) |
-| `GET` | `/status` | Latest status push (cached; updates every ~5s) |
+| `GET` | `/status` | Latest status push (cached; updates every ~5 s) |
 | `GET` | `/attributes` | Printer attributes |
 | `GET` | `/snapshot` | `image/jpeg` response |
 | `GET` | `/stream` | MJPEG stream proxied from the printer (embeds in `<img>`) |
 | `GET` | `/discover` | LAN scan |
 | `GET` | `/events/status` | Server-Sent Events stream of pushes |
+| `GET` | `/api/rtsp` | RTSP bridge state (when `--rtsp` is set) |
+| `POST` | `/api/rtsp/{start,stop}` | Start/stop the RTSP bridge (when `--rtsp` is set) |
+| `GET` | `/docs` / `/redoc` | Auto-generated OpenAPI docs |
 | `POST` | `/print/start` | Body: `{"filename": "cube.gcode"}`. Requires `--enable-control`. |
 | `POST` | `/print/{pause,resume,stop}` | Requires `--enable-control`. |
 
@@ -112,7 +126,7 @@ the firmware's 5-slot limit.
 ## Quick start — RTSP bridge
 
 ```sh
-# Install dependencies first:
+# Install system dependencies first:
 #   mediamtx  https://github.com/bluenviron/mediamtx/releases  (or `brew install mediamtx`)
 #   ffmpeg    `brew install ffmpeg` or `apt install ffmpeg`
 
@@ -122,64 +136,79 @@ centauri rtsp --host 192.168.1.209
 
 # Or, integrated with the HTTP server + web UI
 centauri server --host 192.168.1.209 --rtsp --bind 0.0.0.0
-# Web UI gains a STREAM panel with a toggle, a copy-URL button, and live status
-# at http://<this-host>:8787/ui/
+# The web UI gains a STREAM panel with a start/stop toggle, a copy-URL button,
+# and live status: http://<this-host>:8787/ui/
 ```
 
 Open that URL in **VLC** (Media → Open Network Stream), point **Home Assistant**
 at it via the Generic Camera integration, or feed it to **Frigate** / **Jellyfin**
 / **Synology Surveillance** for NVR recording and motion detection.
 
-MediaMTX runs the ffmpeg transcode only while at least one client is actually
-connected, so idle cost is zero. Tunable: `--fps`, `--bitrate`, `--preset`,
-`--path`, `--port`, `--bind`. Run `centauri rtsp --help` (or
-`centauri server --help`) for the full list.
+MediaMTX runs the ffmpeg transcode only while at least one client is
+actually connected, so idle cost is zero. Tunable flags: `--fps`,
+`--bitrate`, `--preset`, `--path`, `--port`, `--bind` (standalone),
+or `--rtsp-fps`, `--rtsp-bitrate`, `--rtsp-path`, `--rtsp-port`,
+`--rtsp-bind` (on `centauri server`). Run `centauri rtsp --help` or
+`centauri server --help` for the full list.
 
 ## Quick start — MCP
 
 Register the server with your agent. With Claude Code:
 
 ```sh
-claude mcp add pycentauri -- python -m pycentauri.mcp
-# or, with control actions enabled (gives the agent start/pause/stop/upload):
-claude mcp add pycentauri -- python -m pycentauri.mcp --enable-control
+claude mcp add pycentauri --env PYCENTAURI_HOST=192.168.1.209 \
+    -- python -m pycentauri.mcp
+
+# Or, with control actions enabled (gives the agent start/pause/resume/stop):
+claude mcp add pycentauri --env PYCENTAURI_HOST=192.168.1.209 \
+    -- python -m pycentauri.mcp --enable-control
 ```
 
-Set `PYCENTAURI_HOST` in your MCP server env so the agent can't target an
-arbitrary IP. The server exposes these tools:
+Setting `PYCENTAURI_HOST` in the MCP server's launch env means the agent
+can't be tricked into targeting an arbitrary IP through prompt injection —
+the host is pinned at spawn time. Tools exposed:
 
 | Tool | Always available | Description |
 |---|---|---|
 | `get_status` | yes | State, temperatures, progress, elapsed/remaining |
-| `get_attributes` | yes | Model, firmware, mainboard ID |
-| `list_files` | yes | Files stored on the printer |
-| `get_snapshot` | yes | Webcam frame as MCP `Image` content |
+| `get_attributes` | yes | Model, firmware, mainboard ID, capabilities |
+| `get_snapshot` | yes | Webcam frame as MCP `Image` content (LLMs see the picture) |
 | `discover_printers` | yes | LAN scan |
-| `start_print` | only with `--enable-control` | Starts a print |
+| `start_print` | only with `--enable-control` | Starts a print from a file already on the printer |
 | `pause_print` | only with `--enable-control` | Pauses the current print |
 | `resume_print` | only with `--enable-control` | Resumes a paused print |
 | `stop_print` | only with `--enable-control` | Stops the current print |
-| `upload_file` | only with `--enable-control` | Uploads a file to the printer |
+
+Control tools aren't just gated — they're not *registered* without the
+flag, so an LLM that wasn't given the `--enable-control` launch can't see
+them in the tool list at all.
 
 ## Safety
 
-Control actions are gated behind an explicit `enable_control=True` (library) or
-`--enable-control` flag (CLI / MCP). Destructive MCP tools are not even
-registered when the flag is off, so an LLM never sees them. Still: leaving a
-printer running unattended with write-capable agents is your responsibility.
+Printer control actions are gated behind an explicit `enable_control=True`
+(library) or `--enable-control` flag (CLI / MCP). Destructive MCP tools
+aren't registered when the flag is off, so an LLM never sees them. Still:
+leaving a printer running unattended with write-capable agents is your
+responsibility, as is securing the HTTP surface (it's unauthenticated — put
+a reverse proxy with auth in front if you expose it beyond loopback).
+
+The RTSP bridge itself isn't gated by `--enable-control` because it only
+reads the webcam feed and doesn't change printer state; it's enabled
+per-server via the `--rtsp` flag.
 
 ## Known firmware quirks
 
 - **5 concurrent WebSocket connections max.** The printer's SDCP server
   accepts up to 5 open WebSockets on port 3030; the 6th returns HTTP 500
   with body `"too many client"`. Slots release immediately when a
-  connection closes — the CLI and MCP server each open/close one per
-  invocation, so this is almost never a problem in practice.
+  connection closes — the CLI each opens and closes one per invocation,
+  the HTTP and MCP servers hold a single long-lived one, so this is
+  almost never a problem in practice.
 - **Paused / errored states don't auto-push Attributes.** The printer only
   sends its `Attributes` frame spontaneously while idle or printing. In
   paused and errored states it stays silent until asked. Since every SDCP
-  command needs the printer's `MainboardID`, the client takes care of this
-  by pre-seeding the mainboard ID from a UDP discovery on every connect
+  command needs the printer's `MainboardID`, the client handles this by
+  pre-seeding the mainboard ID from a UDP discovery on every connect
   (as of v0.1.1). If you call `Printer.connect()` directly without
   discovery, pass `mainboard_id=` yourself.
 

{pycentauri-0.4.0 → pycentauri-0.4.1}/pyproject.toml

@@ -4,8 +4,8 @@ build-backend = "hatchling.build"
 
 [project]
 name = "pycentauri"
-version = "0.4.0"
-description = "Python client and MCP server for Elegoo Centauri Carbon 3D printers"
+version = "0.4.1"
+description = "Local-network toolkit for Elegoo Centauri Carbon 3D printers: async Python client, CLI, MCP server, REST/SSE HTTP server, web UI, and RTSP bridge"
 readme = "README.md"
 license = "Apache-2.0"
 license-files = ["LICENSE"]

pycentauri-0.4.1/src/pycentauri/__init__.py

@@ -0,0 +1,28 @@
+"""Local-network toolkit for Elegoo Centauri Carbon 3D printers.
+
+Six surfaces, all backed by the same async client:
+
+* :class:`pycentauri.Printer` — asyncio SDCP client
+* the ``centauri`` CLI (``python -m pycentauri.cli``)
+* an MCP stdio server at ``python -m pycentauri.mcp``
+* a FastAPI + SSE HTTP server at :mod:`pycentauri.server`
+* a static web UI bundled in :mod:`pycentauri.web`
+* an RTSP/H.264 bridge via MediaMTX in :mod:`pycentauri.rtsp`
+"""
+
+from pycentauri.client import ControlDisabledError, Printer, PrinterError
+from pycentauri.discovery import DiscoveredPrinter, discover
+from pycentauri.models import Attributes, PrintInfo, Status
+
+__all__ = [
+    "Attributes",
+    "ControlDisabledError",
+    "DiscoveredPrinter",
+    "PrintInfo",
+    "Printer",
+    "PrinterError",
+    "Status",
+    "discover",
+]
+
+__version__ = "0.4.1"

{pycentauri-0.4.0 → pycentauri-0.4.1}/src/pycentauri/cli.py

@@ -250,19 +250,6 @@ def cmd_snapshot(
     _run(run())
 
 
-@app.command("files")
-def cmd_files(host: HostOpt = None, as_json: JsonOpt = False) -> None:
-    """List files stored on the printer.
-
-    Note: the file-list command isn't wired in v0.1 (the upstream SDK also
-    marks it as not-implemented on CC); this is a stub so the command name
-    is reserved.
-    """
-
-    _echo_err("file listing is not yet supported on the original Centauri Carbon firmware")
-    raise typer.Exit(code=1)
-
-
 @print_cmd.command("start")
 def cmd_print_start(
     filename: Annotated[str, typer.Argument(help="File name as it appears on the printer.")],

pycentauri-0.4.0/src/pycentauri/__init__.py

@@ -1,18 +0,0 @@
-"""Python client for Elegoo Centauri Carbon 3D printers."""
-
-from pycentauri.client import ControlDisabledError, Printer, PrinterError
-from pycentauri.discovery import DiscoveredPrinter, discover
-from pycentauri.models import Attributes, PrintInfo, Status
-
-__all__ = [
-    "Attributes",
-    "ControlDisabledError",
-    "DiscoveredPrinter",
-    "PrintInfo",
-    "Printer",
-    "PrinterError",
-    "Status",
-    "discover",
-]
-
-__version__ = "0.4.0"