Prusa Connect RTSP

Prusa Connect RTSP is a lightweight self-hosted utility that captures frames from a real-time streaming protocol (RTSP) camera and publishes them to Prusa…

  • Home Automation
  • Media Applications
  • Other
  • Productivity
  • Tools & Utilities
Prusa Connect RTSP is a lightweight self-hosted utility that captures frames from a real-time streaming protocol (RTSP) camera and publishes them to Prusa Connect as printer snapshots for remote viewing.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

8/100 Low

Maintained
0last commit 1056 days ago
Popular
00 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 19 days ago

GitHub stars
0
Open issues
1
Last commit
2023-12-30
Activity
stale

Checked 6 days ago - source: GitHub (beccazero/prusa-connect-rtsp)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Copy the Connect token from the config file Use the correct Prusa Connect server address and secret token from prusa_printer_settings.ini before first start, because without the right token it cannot log in and will not report status or accept commands. source
  • Start the printer connection loop The program needs to start the SDK communication loop and mark the printer READY after starting, because that loop is what keeps the printer connected and sending telemetry to Prusa Connect. source
  • Match the printer type and serial Set the printer type, serial number, and fingerprint (a checksum calculated from the serial) exactly as they belong to your printer, because mismatched values can prevent it from pairing with the right Prusa Connect account. source
  • Set the camera and identity environment variables Set PRUSA_CONNECT_RTSP_URL to the camera stream, PRUSA_CONNECT_FINGERPRINT to a unique value such as a UUID, and PRUSA_CONNECT_TOKEN to your Prusa Connect token before starting the container. source

Fetched 48 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which environment variables must be set to point the container at a camera and control log output?

Set PRUSA_CONNECT_RTSP_URL to the camera stream and LOGURU_LEVEL for log verbosity before starting the container.

Where do I get the Prusa Connect token value?

Use the secret token from the printer's prusa_printer_settings.ini, because without the right token it cannot log in and will not report status or accept commands.

What snapshot interval and camera count has a self-hosted setup reported?

A user reports sending snapshots to the Prusa Connect Camera API every 10 seconds and running 5 Wi-Fi cameras on a single Raspberry Pi Zero 2W.

Can a TP-Link Tapo C200C be connected over RTSP to Prusa Connect?

A user shares connecting a TP-Link Tapo C200C camera to a Mini+ via RTSP using Python code.

Answers sourced from forum.prusa3d.com, forum.prusa3d.com, github.com, github.com

Community

Collected 3 days ago - public community threads