plexus-python 0.11.4__tar.gz → 0.11.5__tar.gz

{plexus_python-0.11.4 → plexus_python-0.11.5}/API.md

@@ -165,7 +165,7 @@ For real-time UI-controlled streaming, devices connect via WebSocket.
 1. Device connects to the gateway
 2. Device authenticates with API key (and advertises any registered commands)
 3. Device streams `telemetry` frames
-4. Dashboard/API invokes registered commands via `typed_command`
+4. Plexus invokes registered commands via `typed_command` (see the note under Commands)
 
 ### Device Authentication
 
@@ -227,7 +227,9 @@ Devices authenticate using an API key. The gateway echoes the declared `source_i
 
 ### Commands
 
-Dashboard/API actions reach the device as a single `typed_command` envelope; the device replies with `command_result` frames. Register handlers with `px.on_command(...)` before the first `send()`.
+Commands reach the device as a single `typed_command` envelope; the device replies with `command_result` frames. Register handlers with `px.on_command(...)` before the first `send()`.
+
+> **Note:** the public API route for sending commands (`POST /v1/sources/{id}/commands`) was turned off on 2026-09-21 and returns `410 Gone`. Nothing in Plexus can currently trigger a custom handler.
 
 ```json
 // Server → Device

{plexus_python-0.11.4 → plexus_python-0.11.5}/CHANGELOG.md

@@ -2,6 +2,23 @@
 
 ## [Unreleased]
 
+## [0.11.5] - 2026-09-21 - The commands API is off
+
+No code changes. The docs described a way to send commands to a device that
+no longer exists.
+
+### Changed
+
+- **`POST /v1/sources/{id}/commands` is turned off, and the docs now say so.**
+  Plexus turned the endpoint off on 2026-09-21. It returns `410 Gone`.
+  Any API key of any scope could send any command name to any device in
+  the org, which is not safe for commands that reach hardware.
+  - The agent skill no longer offers to send commands, and it tells agents
+    not to call the endpoint.
+  - README and `API.md` say plainly that nothing in Plexus can currently
+    trigger an `on_command` handler.
+  - `on_command` itself is unchanged.
+
 ## [0.11.4] - 2026-09-08 - Docs that actually work
 
 No code changes. Every edit here is documentation or dead weight, but the

{plexus_python-0.11.4 → plexus_python-0.11.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: plexus-python
-Version: 0.11.4
+Version: 0.11.5
 Summary: Thin Python SDK for Plexus — send telemetry in one line
 Project-URL: Homepage, https://plexus.company
 Project-URL: Documentation, https://docs.plexus.company
@@ -255,7 +255,7 @@ px.send("temperature", 72.5, timestamp=t)   # your timestamp, used as-is, no cor
 By default the SDK connects over a **WebSocket** to `/ws/device` on the gateway — the gateway's device wire protocol. This gives you:
 
 - lower-latency streaming of telemetry,
-- live command delivery from the UI / API to the device.
+- the channel that will carry actions triggered from a Plexus dashboard.
 
 If the socket is unavailable, sends transparently fall back to `POST /ingest` so no data is lost.
 
@@ -283,6 +283,8 @@ px.send("temperature", 72.5)   # opens the socket, waits for auth
 
 The SDK sends an `ack` frame before invoking the handler, then a `result` frame with whatever the handler returns (or an `error` frame if it raises).
 
+> **Note:** nothing in Plexus can currently trigger a custom handler. The API route for sending commands was turned off on 2026-09-21. Triggering handlers from a dashboard, with permissions and a record of every run, is being rebuilt.
+
 ## Environment Variables
 
 | Variable                | Description                  | Default                          |

{plexus_python-0.11.4 → plexus_python-0.11.5}/README.md

@@ -218,7 +218,7 @@ px.send("temperature", 72.5, timestamp=t)   # your timestamp, used as-is, no cor
 By default the SDK connects over a **WebSocket** to `/ws/device` on the gateway — the gateway's device wire protocol. This gives you:
 
 - lower-latency streaming of telemetry,
-- live command delivery from the UI / API to the device.
+- the channel that will carry actions triggered from a Plexus dashboard.
 
 If the socket is unavailable, sends transparently fall back to `POST /ingest` so no data is lost.
 
@@ -246,6 +246,8 @@ px.send("temperature", 72.5)   # opens the socket, waits for auth
 
 The SDK sends an `ack` frame before invoking the handler, then a `result` frame with whatever the handler returns (or an `error` frame if it raises).
 
+> **Note:** nothing in Plexus can currently trigger a custom handler. The API route for sending commands was turned off on 2026-09-21. Triggering handlers from a dashboard, with permissions and a record of every run, is being rebuilt.
+
 ## Environment Variables
 
 | Variable                | Description                  | Default                          |

{plexus_python-0.11.4 → plexus_python-0.11.5}/plexus/__init__.py

@@ -23,7 +23,7 @@ from plexus.client import (
 )
 from plexus.config import RetryConfig
 
-__version__ = "0.11.4"
+__version__ = "0.11.5"
 __all__ = [
     "AuthenticationError",
     "BatchSender",

{plexus_python-0.11.4 → plexus_python-0.11.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "plexus-python"
-version = "0.11.4"
+version = "0.11.5"
 description = "Thin Python SDK for Plexus — send telemetry in one line"
 readme = "README.md"
 license = "Apache-2.0"

{plexus_python-0.11.4 → plexus_python-0.11.5}/skills/plexus/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: plexus
-description: Integrate with the Plexus telemetry API — send data, query metrics, subscribe to live streams, send commands to devices. Use when the user mentions Plexus, plexus.company, gateway.plexus.company, plexus-data-api.fly.dev, or plx_ API keys. ALSO USE when the request involves IoT/hardware telemetry, fleet observability, sending sensor data to a backend, querying device time-series, building a fleet dashboard, monitoring drones/satellites/robots/edge devices, or any phrase like "send my sensor readings somewhere", "store telemetry", "track a fleet", "ingest metrics", or "device observability" — even if "Plexus" is never said.
+description: Integrate with the Plexus telemetry API — send data, query metrics, subscribe to live streams. Use when the user mentions Plexus, plexus.company, gateway.plexus.company, plexus-data-api.fly.dev, or plx_ API keys. ALSO USE when the request involves IoT/hardware telemetry, fleet observability, sending sensor data to a backend, querying device time-series, building a fleet dashboard, monitoring drones/satellites/robots/edge devices, or any phrase like "send my sensor readings somewhere", "store telemetry", "track a fleet", "ingest metrics", or "device observability" — even if "Plexus" is never said.
 tools: Read, Write, Edit, Bash, WebFetch
 ---
 
@@ -13,7 +13,7 @@ Plexus is a telemetry/observability platform for hardware fleets (drones, satell
 Trigger on any of:
 
 - The user mentions "Plexus", "plexus.company", `plx_` keys, `gateway.plexus.company`, or `plexus-data-api.fly.dev`
-- The user wants to ingest telemetry, query device metrics, stream live points, or send commands to a device
+- The user wants to ingest telemetry, query device metrics, or stream live points
 - The user is building a dashboard, alert pipeline, or analysis on top of fleet telemetry
 - The user pastes a Plexus curl example and asks for help
 
@@ -27,7 +27,7 @@ Two base URLs. Authenticate with an `x-api-key` header on HTTP.
 | Purpose                                            | Host                             |
 | -------------------------------------------------- | -------------------------------- |
 | Ingest                                              | `https://gateway.plexus.company` |
-| Read API (sources, metrics, logs, fleet, commands, live stream) | `https://plexus-data-api.fly.dev` |
+| Read API (sources, metrics, logs, fleet, live stream) | `https://plexus-data-api.fly.dev` |
 
 ```
 x-api-key: plx_...
@@ -141,9 +141,9 @@ You do **not** need to answer application-level pings on this endpoint; keepaliv
 
 The gateway's own sockets (`/ws/device`, `/ws/browser`) are for the Python SDK and the Plexus app respectively. Don't write third-party clients against them. There is no `/v1/stream` on the gateway.
 
-### Control (data API)
+### Control
 
-`POST /v1/sources/{id}/commands` — body `{ command, params? }`, response `{ queued: bool }`. Confirm with the user before sending — these hit physical hardware.
+There is no API for sending commands to devices. `POST /v1/sources/{id}/commands` was turned off and returns `410 Gone`. Don't write code that calls it, and don't offer to trigger device behavior through the API.
 
 ## Standard scaffolding
 
@@ -216,7 +216,6 @@ let the pipeline settle first.
 - **Telemetry frames are batched** — `points` is an array. Handling one frame as one point silently drops data.
 - `start`/`end` are **ISO date-times on every endpoint** that takes them — `query`, `logs` and `fleet/metrics` alike. `last=1h` is easier and works on all three.
 - `auto_downsampled: true` in a query response means the bucket size was picked for you — surface it in the UI so users understand what they're looking at.
-- Commands queue on the device; they don't execute synchronously. Don't promise the user "it rebooted" — promise "reboot queued".
 
 ## When unsure
 

{plexus_python-0.11.4 → plexus_python-0.11.5}/uv.lock

@@ -425,7 +425,7 @@ wheels = [
 
 [[package]]
 name = "plexus-python"
-version = "0.11.4"
+version = "0.11.5"
 source = { editable = "." }
 dependencies = [
     { name = "websocket-client" },