From 3b93a1b4e1f5318c960dc58d8f137305585d8a70 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Iwo=20Strzebo=C5=84ski?= Date: Thu, 15 Oct 2026 23:10:57 +0000 Subject: [PATCH] Confirm at the network layer that a P1P has no RTSP endpoint `camera.rs` said a P1/A1 camera is reachable only over Bambu's port-6000 JPEG stream, inferred from the absence of `rtsp_url` in what the printer reports. Checked directly today: the H2C accepts TCP on 322 and the P1P *refuses* 322 while listening on 6000. So the inference was right and is now a fact. Worth writing down, because it closes off the tempting shortcut - there is no URL to guess for a P1P, the endpoint does not exist. --- src/camera.rs | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/camera.rs b/src/camera.rs index 95252c6..a10ae20 100644 --- a/src/camera.rs +++ b/src/camera.rs @@ -22,6 +22,11 @@ //! crate does not speak, so those printers get no stream here and say so //! rather than advertising one that will not play. //! +//! That is not just an inference from the missing field - it is confirmed at +//! the network layer (2026-10-15). The H2C accepts TCP on 322; the P1P +//! *refuses* 322 and listens on 6000. So a P1P has no RTSP endpoint to +//! restream, and no amount of guessing a URL would produce one. +//! //! That is also why this module reads the *reported* URL and never builds one //! from the printer's IP: the fact that a printer has a camera and the fact //! that the camera has an RTSP endpoint are different facts, and only the