Eternet Portal Documentation
Camera Stream Detail
Information and controls
The detail route resolves camera information from the Frigate camera-detail API and presents the stream’s available formats and metadata. Related controls may include stream configuration, recording, zones, review events, or AI settings according to the camera and backend response.
Live versus sample media
Configured RTSP/HLS sources are routed through portal proxy endpoints for browser playback. A small set of known fixture stream IDs uses local demo MP4 media instead; verify the source before presenting a clip as live.
Availability
Playback requires the stream service, camera configuration, and a browser-compatible media response. API metadata success does not by itself establish that frames are currently arriving.
Investigating one camera
The detail route is useful when an operator already knows which stream needs attention and wants to focus on that camera rather than scan the inventory. It resolves the camera identifier through the Frigate detail endpoint, then presents the returned name, stream format, dimensions, status, location, or description when those fields are supplied. The same identifier is used to build browser playback paths and to load related review or configuration functions. A stable camera identifier therefore matters for both inventory navigation and downstream operations.
When investigating playback, check the camera detail response first, then the selected media format and its browser URL. RTSP sources cannot be played natively in most browsers, so the portal routes them through the HLS/proxy service. Validate that the proxy can reach the camera, that transcoding produces a compatible stream, and that the browser receives media segments. A successful metadata response alone proves only that the camera record was found. It does not prove the image is current. Watch for a changing frame and verify the timestamp or stream state when the customer asks whether the feed is live.
Configuration and event context
Depending on the service response and installed features, a stream detail experience can expose related zones, recording state, AI configuration, detections, face or plate events, and review status. Each control belongs to a backend operation and may have its own authorization. A change to a detection zone can alter which objects are considered relevant; a recording switch can affect future footage; an AI configuration change can affect all subsequent analysis. Explain the scope of a change before applying it and verify the resulting service response rather than relying solely on local UI state.
Event context helps the operator understand why a stream is being inspected. Review events should be associated with the camera and time interval returned by the backend. Thumbnails and exports may be delivered via protected portal proxy routes, so they depend on session authorization and the upstream retention window. If the event is absent, distinguish “no event returned” from “camera did not detect an event”; service availability, filters, and retention can all affect the result.
Presentation guidance
For a customer demonstration, choose a stream with an approved source and known working media path. Identify whether it is a production camera, a configured but offline camera, or a local fixture. Demonstrate one read-only operation before showing controls that mutate recording, zones, or AI configuration. The stream detail page is an operator surface and not a replacement for the camera recorder or the video-management system. Video transport, retention, and analysis are provided by the integrated stream and Frigate services; the portal provides navigation, authenticated access, and operational presentation.