CamAdmiral v2026.09.14-02

More reliable camera monitoring and media recovery

• Allow up to 30 seconds for snapshots from cameras with slower stream startup.
• Check selected streams independently, so a failed detect stream does not incorrectly mark a working record stream offline.
• Run snapshot checks in a bounded background worker pool without blocking active-stream monitoring.
• Clean up stalled snapshot processes and connections to prevent retained consumers and memory growth.
• Bound snapshot conversion threads and allow 512 MiB for concurrent camera media work.

Also included since the previous public release

• Preserve Frigate recording continuity when removing or unadopting a managed camera by safely retiring its configuration.
• Let Frigate camera detection inherit the configured frame rate.

Existing camera identities, stable RTSP URLs, credentials, and Frigate bindings are preserved.

Update

git pull
./start-camadmiral.sh --update

Reefy users can select the new CamAdmiral app version in the dashboard.

Validation

475 unit/component tests and the full camera/Frigate E2E release gate passed. Coverage includes delayed real video, per-stream failure isolation and recovery, snapshot cleanup, production memory/PID limits, recording continuity, and camera address recovery with stable URLs.

Full release gate

CamAdmiral v2026.09.06-00

What's changed

• Add Find Frigate in Settings > Integrations to discover compatible local Frigate APIs without looking up their ports.
• Check ports 5000, 8971, and 20000-20999 with bounded concurrency and a 12-second overall deadline.
• Show discovered API URLs and versions, mark already-added endpoints, and prefill the existing connection form.
• Keep discovery read-only: adding an integration and selecting cameras remain explicit actions.
• Preserve manual URL entry for remote machines, custom ports, HTTPS, and authentication-required endpoints.

Local discovery runs inside CamAdmiral's network namespace. Bridge-networked installations may need a manually entered host address.

Update

git pull
./start-camadmiral.sh --update

On Reefy, select this version for your CamAdmiral app.

Validated with 457 local tests and the complete Docker/browser E2E release gate. See PR #32 for implementation and coverage details.

Full changelog: v2026.09.03-02...v2026.09.06-00

CamAdmiral v2026.09.03-02

What's changed

• Add cameras manually from complete RTSP URLs when network discovery is unavailable.
• Support one or two streams, optional credentials, DNS hostnames resolving to private addresses, and multiple independent cameras on one RTSP server.
• Give manually added cameras stable downstream URLs, health monitoring, incidents, thumbnails, and Frigate synchronization.
• Keep direct RTSP cameras independent from network scans and discovery identity.
• Add complete API, storage, browser, video-decoding, restart, isolation, and Frigate E2E coverage.

See PR #31 for implementation and validation details.

Full changelog: v2026.09.02-01...v2026.09.03-02

CamAdmiral v2026.09.02-01

What's Changed

• Harden multi-subnet discovery resource and inventory handling by @aospan in #28

Full Changelog: v2026.08.29-00...v2026.09.02-01

CamAdmiral v2026.08.29-00

This release hardens network scanning across multiple subnets.

Highlights

• Bound RTSP and reachability workers across the entire scan, preventing PID exhaustion under the production container limit.
• Preserve camera status on networks that were not selected for a partial scan.
• Continue following a stable camera identity when it moves into a selected subnet.
• Add Docker E2E coverage for production PID limits and partial-subnet inventory reconciliation.

Validation

The exact tagged commit passed the full unit, component, browser, and isolated Docker E2E release gate. The immutable amd64 container image was then published from that verified commit.

Update

git pull
./start-camadmiral.sh --update