yaml list

applying modal=false to the menu (not to the dialog) to fix this in the same way as elsewhere in the codebase

.cspell/frigate-dictionary.txt

@@ -22,7 +22,6 @@ autotrack
 autotracked
 autotracker
 autotracking
-backchannel
 balena
 Beelink
 BGRA
@@ -317,4 +316,4 @@ yolo
 yolonas
 yolox
 zeep
-zerolatency
+zerolatency

.github/DISCUSSION_TEMPLATE/beta-support.yml

@@ -1,129 +0,0 @@
-title: "[Beta Support]: "
-labels: ["support", "triage", "beta"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thank you for testing Frigate beta versions! Use this form for support with beta releases.
-
-        **Note:** Beta versions may have incomplete features, known issues, or unexpected behavior. Please check the [release notes](https://github.com/blakeblackshear/frigate/releases) and [recent discussions][discussions] for known beta issues before submitting.
-
-        Before submitting, read the [beta documentation][docs].
-
-        [docs]: https://deploy-preview-19787--frigate-docs.netlify.app/
-  - type: textarea
-    id: description
-    attributes:
-      label: Describe the problem you are having
-      description: Please be as detailed as possible. Include what you expected to happen vs what actually happened.
-    validations:
-      required: true
-  - type: input
-    id: version
-    attributes:
-      label: Beta Version
-      description: Visible on the System page in the Web UI. Please include the full version including the build identifier (eg. 0.17.0-beta1)
-      placeholder: "0.17.0-beta1"
-    validations:
-      required: true
-  - type: dropdown
-    id: issue-category
-    attributes:
-      label: Issue Category
-      description: What area is your issue related to? This helps us understand the context.
-      options:
-        - Object Detection / Detectors
-        - Hardware Acceleration
-        - Configuration / Setup
-        - WebUI / Frontend
-        - Recordings / Storage
-        - Notifications / Events
-        - Integration (Home Assistant, etc)
-        - Performance / Stability
-        - Installation / Updates
-        - Other
-    validations:
-      required: true
-  - type: textarea
-    id: config
-    attributes:
-      label: Frigate config file
-      description: This will be automatically formatted into code, so no need for backticks. Remove any sensitive information like passwords or URLs.
-      render: yaml
-    validations:
-      required: true
-  - type: textarea
-    id: frigatelogs
-    attributes:
-      label: Relevant Frigate log output
-      description: Please copy and paste any relevant Frigate log output. Include logs before and after your exact error when possible. This will be automatically formatted into code, so no need for backticks.
-      render: shell
-    validations:
-      required: true
-  - type: textarea
-    id: go2rtclogs
-    attributes:
-      label: Relevant go2rtc log output (if applicable)
-      description: If your issue involves cameras, streams, or playback, please include go2rtc logs. Logs can be viewed via the Frigate UI, Docker, or the go2rtc dashboard. This will be automatically formatted into code, so no need for backticks.
-      render: shell
-  - type: dropdown
-    id: install-method
-    attributes:
-      label: Install method
-      options:
-        - Home Assistant Add-on
-        - Docker Compose
-        - Docker CLI
-        - Proxmox via Docker
-        - Proxmox via TTeck Script
-        - Windows WSL2
-    validations:
-      required: true
-  - type: textarea
-    id: docker
-    attributes:
-      label: docker-compose file or Docker CLI command
-      description: This will be automatically formatted into code, so no need for backticks. Include relevant environment variables and device mappings.
-      render: yaml
-    validations:
-      required: true
-  - type: dropdown
-    id: os
-    attributes:
-      label: Operating system
-      options:
-        - Home Assistant OS
-        - Debian
-        - Ubuntu
-        - Other Linux
-        - Proxmox
-        - UNRAID
-        - Windows
-        - Other
-    validations:
-      required: true
-  - type: input
-    id: hardware
-    attributes:
-      label: CPU / GPU / Hardware
-      description: Provide details about your hardware (e.g., Intel i5-9400, NVIDIA RTX 3060, Raspberry Pi 4, etc)
-      placeholder: "Intel i7-10700, NVIDIA GTX 1660"
-  - type: textarea
-    id: screenshots
-    attributes:
-      label: Screenshots
-      description: Screenshots of the issue, System metrics pages, or any relevant UI. Drag and drop or paste images directly.
-  - type: textarea
-    id: steps-to-reproduce
-    attributes:
-      label: Steps to reproduce
-      description: If applicable, provide detailed steps to reproduce the issue
-      placeholder: |
-        1. Go to '...'
-        2. Click on '...'
-        3. See error
-  - type: textarea
-    id: other
-    attributes:
-      label: Any other information that may be helpful
-      description: Additional context, related issues, when the problem started appearing, etc.

.github/DISCUSSION_TEMPLATE/report-a-bug.yml

@@ -6,8 +6,6 @@ body:
       value: |
         Use this form to submit a reproducible bug in Frigate or Frigate's UI.
 
-        **⚠️ If you are running a beta version (0.17.0-beta or similar), please use the [Beta Support template](https://github.com/blakeblackshear/frigate/discussions/new?category=beta-support) instead.**
-
         Before submitting your bug report, please ask the AI with the "Ask AI" button on the [official documentation site][ai] about your issue, [search the discussions][discussions], look at recent open and closed [pull requests][prs], read the [official Frigate documentation][docs], and read the [Frigate FAQ][faq] pinned at the Discussion page to see if your bug has already been fixed by the developers or reported by the community.
 
         **If you are unsure if your issue is actually a bug or not, please submit a support request first.**

docs/docs/configuration/live.md

@@ -178,8 +178,6 @@ To use the Reolink Doorbell with two way talk, you should use the [recommended R
 
 As a starting point to check compatibility for your camera, view the list of cameras supported for two-way talk on the [go2rtc repository](https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#two-way-audio). For cameras in the category `ONVIF Profile T`, you can use the [ONVIF Conformant Products Database](https://www.onvif.org/conformant-products/)'s FeatureList to check for the presence of `AudioOutput`. A camera that supports `ONVIF Profile T` _usually_ supports this, but due to inconsistent support, a camera that explicitly lists this feature may still not work. If no entry for your camera exists on the database, it is recommended not to buy it or to consult with the manufacturer's support on the feature availability.
 
-To prevent go2rtc from blocking other applications from accessing your camera's two-way audio, you must configure your stream with `#backchannel=0`. See [preventing go2rtc from blocking two-way audio](/configuration/restream#two-way-talk-restream) in the restream documentation.
-
 ### Streaming options on camera group dashboards
 
 Frigate provides a dialog in the Camera Group Edit pane with several options for streaming on a camera group's dashboard. These settings are _per device_ and are saved in your device's local storage.

docs/docs/configuration/reference.md

@@ -911,7 +911,7 @@ cameras:
       user: admin
       # Optional: password for login.
       password: admin
-      # Optional: Skip TLS verification and disable digest authentication for the ONVIF server (default: shown below)
+      # Optional: Skip TLS verification from the ONVIF server (default: shown below)
       tls_insecure: False
       # Optional: Ignores time synchronization mismatches between the camera and the server during authentication.
       # Using NTP on both ends is recommended and this should only be set to True in a "safe" environment due to the security risk it represents.

docs/docs/configuration/restream.md

@@ -24,12 +24,11 @@ birdseye:
   restream: True
 ```
 
-:::tip
+:::tip 
 
-To improve connection speed when using Birdseye via restream you can enable a small idle heartbeat by setting `birdseye.idle_heartbeat_fps` to a low value (e.g. `1–2`). This makes Frigate periodically push the last frame even when no motion is detected, reducing initial connection latency.
+To improve connection speed when using Birdseye via restream you can enable a small idle heartbeat by setting `birdseye.idle_heartbeat_fps` to a low value (e.g. `1–2`).  This makes Frigate periodically push the last frame even when no motion is detected, reducing initial connection latency.
 
 :::
-
 ### Securing Restream With Authentication
 
 The go2rtc restream can be secured with RTSP based username / password authentication. Ex:
@@ -160,31 +159,6 @@ go2rtc:
 
 See [this comment](https://github.com/AlexxIT/go2rtc/issues/1217#issuecomment-2242296489) for more information.
 
-## Preventing go2rtc from blocking two-way audio {#two-way-talk-restream}
-
-For cameras that support two-way talk, go2rtc will automatically establish an audio output backchannel when connecting to an RTSP stream. This backchannel blocks access to the camera's audio output for two-way talk functionality, preventing both Frigate and other applications from using it.
-
-To prevent this, you must configure two separate stream instances:
-
-1. One stream instance with `#backchannel=0` for Frigate's viewing, recording, and detection (prevents go2rtc from establishing the blocking backchannel)
-2. A second stream instance without `#backchannel=0` for two-way talk functionality (can be used by Frigate's WebRTC viewer or other applications)
-
-Configuration example:
-
-```yaml
-go2rtc:
-  streams:
-    front_door:
-      - rtsp://user:password@10.0.10.10:554/cam/realmonitor?channel=1&subtype=2#backchannel=0
-    front_door_twoway:
-      - rtsp://user:password@10.0.10.10:554/cam/realmonitor?channel=1&subtype=2
-```
-
-In this configuration:
-
-- `front_door` stream is used by Frigate for viewing, recording, and detection. The `#backchannel=0` parameter prevents go2rtc from establishing the audio output backchannel, so it won't block two-way talk access.
-- `front_door_twoway` stream is used for two-way talk functionality. This stream can be used by Frigate's WebRTC viewer when two-way talk is enabled, or by other applications (like Home Assistant Advanced Camera Card) that need access to the camera's audio output channel.
-
 ## Advanced Restream Configurations
 
 The [exec](https://github.com/AlexxIT/go2rtc/tree/v1.9.10#source-exec) source in go2rtc can be used for custom ffmpeg commands. An example is below:
@@ -195,4 +169,4 @@ NOTE: The output will need to be passed with two curly braces `{{output}}`
 go2rtc:
   streams:
     stream1: exec:ffmpeg -hide_banner -re -stream_loop -1 -i /media/BigBuckBunny.mp4 -c copy -rtsp_transport tcp -f rtsp {{output}}
-```
+```

docs/docs/guides/configuring_go2rtc.md

@@ -113,8 +113,7 @@ section.
 
 1. If the stream you added to go2rtc is also used by Frigate for the `record` or `detect` role, you can migrate your config to pull from the RTSP restream to reduce the number of connections to your camera as shown [here](/configuration/restream#reduce-connections-to-camera).
 2. You can [set up WebRTC](/configuration/live#webrtc-extra-configuration) if your camera supports two-way talk. Note that WebRTC only supports specific audio formats and may require opening ports on your router.
-3. If your camera supports two-way talk, you must configure your stream with `#backchannel=0` to prevent go2rtc from blocking other applications from accessing the camera's audio output. See [preventing go2rtc from blocking two-way audio](/configuration/restream#two-way-talk-restream) in the restream documentation.
 
 ## Homekit Configuration
 
-To add camera streams to Homekit Frigate must be configured in docker to use `host` networking mode. Once that is done, you can use the go2rtc WebUI (accessed via port 1984, which is disabled by default) to share export a camera to Homekit. Any changes made will automatically be saved to `/config/go2rtc_homekit.yml`.
+To add camera streams to Homekit Frigate must be configured in docker to use `host` networking mode. Once that is done, you can use the go2rtc WebUI (accessed via port 1984, which is disabled by default) to share export a camera to Homekit. Any changes made will automatically be saved to `/config/go2rtc_homekit.yml`.

docs/package.json

@@ -18,14 +18,14 @@
   },
   "dependencies": {
     "@docusaurus/core": "^3.7.0",
-    "@docusaurus/plugin-content-docs": "^3.7.0",
+    "@docusaurus/plugin-content-docs": "^3.6.3",
     "@docusaurus/preset-classic": "^3.7.0",
-    "@docusaurus/theme-mermaid": "^3.7.0",
+    "@docusaurus/theme-mermaid": "^3.6.3",
     "@inkeep/docusaurus": "^2.0.16",
     "@mdx-js/react": "^3.1.0",
     "clsx": "^2.1.1",
-    "docusaurus-plugin-openapi-docs": "^4.5.1",
-    "docusaurus-theme-openapi-docs": "^4.5.1",
+    "docusaurus-plugin-openapi-docs": "^4.3.1",
+    "docusaurus-theme-openapi-docs": "^4.3.1",
     "prism-react-renderer": "^2.4.1",
     "raw-loader": "^4.0.2",
     "react": "^18.3.1",
@@ -44,9 +44,9 @@
     ]
   },
   "devDependencies": {
-    "@docusaurus/module-type-aliases": "^3.7.0",
-    "@docusaurus/types": "^3.7.0",
-    "@types/react": "^18.3.27"
+    "@docusaurus/module-type-aliases": "^3.4.0",
+    "@docusaurus/types": "^3.4.0",
+    "@types/react": "^18.3.7"
   },
   "engines": {
     "node": ">=18.0"

frigate/api/preview.py

@@ -5,14 +5,10 @@ import os
 from datetime import datetime, timedelta, timezone
 
 import pytz
-from fastapi import APIRouter, Depends, HTTPException
+from fastapi import APIRouter, Depends
 from fastapi.responses import JSONResponse
 
-from frigate.api.auth import (
-    allow_any_authenticated,
-    get_allowed_cameras_for_filter,
-    require_camera_access,
-)
+from frigate.api.auth import require_camera_access
 from frigate.api.defs.response.preview_response import (
     PreviewFramesResponse,
     PreviewsResponse,
@@ -30,32 +26,19 @@ router = APIRouter(tags=[Tags.preview])
 @router.get(
     "/preview/{camera_name}/start/{start_ts}/end/{end_ts}",
     response_model=PreviewsResponse,
-    dependencies=[Depends(allow_any_authenticated())],
+    dependencies=[Depends(require_camera_access)],
     summary="Get preview clips for time range",
     description="""Gets all preview clips for a specified camera and time range.
     Returns a list of preview video clips that overlap with the requested time period,
     ordered by start time. Use camera_name='all' to get previews from all cameras.
     Returns an error if no previews are found.""",
 )
-def preview_ts(
-    camera_name: str,
-    start_ts: float,
-    end_ts: float,
-    allowed_cameras: list[str] = Depends(get_allowed_cameras_for_filter),
-):
+def preview_ts(camera_name: str, start_ts: float, end_ts: float):
     """Get all mp4 previews relevant for time period."""
     if camera_name != "all":
-        if camera_name not in allowed_cameras:
-            raise HTTPException(status_code=403, detail="Access denied for camera")
-        camera_list = [camera_name]
+        camera_clause = Previews.camera == camera_name
     else:
-        camera_list = allowed_cameras
-
-    if not camera_list:
-        return JSONResponse(
-            content={"success": False, "message": "No previews found."},
-            status_code=404,
-        )
+        camera_clause = True
 
     previews = (
         Previews.select(
@@ -70,7 +53,7 @@ def preview_ts(
             | Previews.end_time.between(start_ts, end_ts)
             | ((start_ts > Previews.start_time) & (end_ts < Previews.end_time))
         )
-        .where(Previews.camera << camera_list)
+        .where(camera_clause)
         .order_by(Previews.start_time.asc())
         .dicts()
         .iterator()
@@ -105,21 +88,14 @@ def preview_ts(
 @router.get(
     "/preview/{year_month}/{day}/{hour}/{camera_name}/{tz_name}",
     response_model=PreviewsResponse,
-    dependencies=[Depends(allow_any_authenticated())],
+    dependencies=[Depends(require_camera_access)],
     summary="Get preview clips for specific hour",
     description="""Gets all preview clips for a specific hour in a given timezone.
     Converts the provided date/time from the specified timezone to UTC and retrieves
     all preview clips for that hour. Use camera_name='all' to get previews from all cameras.
     The tz_name should be a timezone like 'America/New_York' (use commas instead of slashes).""",
 )
-def preview_hour(
-    year_month: str,
-    day: int,
-    hour: int,
-    camera_name: str,
-    tz_name: str,
-    allowed_cameras: list[str] = Depends(get_allowed_cameras_for_filter),
-):
+def preview_hour(year_month: str, day: int, hour: int, camera_name: str, tz_name: str):
     """Get all mp4 previews relevant for time period given the timezone"""
     parts = year_month.split("-")
     start_date = (
@@ -130,7 +106,7 @@ def preview_hour(
     start_ts = start_date.timestamp()
     end_ts = end_date.timestamp()
 
-    return preview_ts(camera_name, start_ts, end_ts, allowed_cameras)
+    return preview_ts(camera_name, start_ts, end_ts)
 
 
 @router.get(

frigate/data_processing/post/review_descriptions.py

@@ -251,22 +251,20 @@ class ReviewDescriptionProcessor(PostProcessorApi):
             if not primary_segments:
                 return "No concerns were found during this time period."
 
-            # Build hierarchical structure: each primary event with its contextual items
-            events_with_context = []
+            # For each primary segment, find overlapping contextual items from other cameras
+            all_items_for_summary = []
 
             for primary_seg in primary_segments:
-                # Start building the primary event structure
+                # Add the primary item with marker
                 primary_item = copy.deepcopy(primary_seg["metadata"])
-                primary_item["camera"] = primary_seg["camera"]
-                primary_item["start_time"] = primary_seg["start_time"]
-                primary_item["end_time"] = primary_seg["end_time"]
+                primary_item["_is_primary"] = True
+                primary_item["_camera"] = primary_seg["camera"]
+                all_items_for_summary.append(primary_item)
 
                 # Find overlapping contextual items from other cameras
                 primary_start = primary_seg["start_time"]
                 primary_end = primary_seg["end_time"]
                 primary_camera = primary_seg["camera"]
-                contextual_items = []
-                seen_contextual_cameras = set()
 
                 for seg in segments:
                     seg_camera = seg["camera"]
@@ -281,25 +279,21 @@ class ReviewDescriptionProcessor(PostProcessorApi):
                     seg_end = seg["end_time"]
 
                     if seg_start < primary_end and primary_start < seg_end:
-                        # Avoid duplicates if same camera has multiple overlapping segments
-                        if seg_camera not in seen_contextual_cameras:
-                            contextual_item = copy.deepcopy(seg["metadata"])
-                            contextual_item["camera"] = seg_camera
-                            contextual_item["start_time"] = seg_start
-                            contextual_item["end_time"] = seg_end
-                            contextual_items.append(contextual_item)
-                            seen_contextual_cameras.add(seg_camera)
+                        contextual_item = copy.deepcopy(seg["metadata"])
+                        contextual_item["_is_primary"] = False
+                        contextual_item["_camera"] = seg_camera
+                        contextual_item["_related_to_camera"] = primary_camera
 
-                # Add context array to primary item
-                primary_item["context"] = contextual_items
-                events_with_context.append(primary_item)
+                        if not any(
+                            item.get("_camera") == seg_camera
+                            and item.get("time") == contextual_item.get("time")
+                            for item in all_items_for_summary
+                        ):
+                            all_items_for_summary.append(contextual_item)
 
-            total_context_items = sum(
-                len(event.get("context", [])) for event in events_with_context
-            )
             logger.debug(
-                f"Summary includes {len(events_with_context)} primary events with "
-                f"{total_context_items} total contextual items"
+                f"Summary includes {len(primary_segments)} primary items and "
+                f"{len(all_items_for_summary) - len(primary_segments)} contextual items"
             )
 
             if self.config.review.genai.debug_save_thumbnails:
@@ -310,7 +304,7 @@ class ReviewDescriptionProcessor(PostProcessorApi):
             return self.genai_client.generate_review_summary(
                 start_ts,
                 end_ts,
-                events_with_context,
+                all_items_for_summary,
                 self.config.review.genai.debug_save_thumbnails,
             )
         else:

frigate/genai/__init__.py

@@ -177,60 +177,78 @@ Each line represents a detection state, not necessarily unique individuals. Pare
         self,
         start_ts: float,
         end_ts: float,
-        events: list[dict[str, Any]],
+        segments: list[dict[str, Any]],
         debug_save: bool,
     ) -> str | None:
         """Generate a summary of review item descriptions over a period of time."""
         time_range = f"{datetime.datetime.fromtimestamp(start_ts).strftime('%B %d, %Y at %I:%M %p')} to {datetime.datetime.fromtimestamp(end_ts).strftime('%B %d, %Y at %I:%M %p')}"
         timeline_summary_prompt = f"""
-You are a security officer writing a concise security report.
+You are a security officer.
+Time range: {time_range}.
+Input: JSON list with "title", "scene", "confidence", "potential_threat_level" (0-2), "other_concerns", "_is_primary", "_camera".
 
-Time range: {time_range}
+Task: Write a concise, human-presentable security report in markdown format.
 
-Input format: Each event is a JSON object with:
-- "title", "scene", "confidence", "potential_threat_level" (0-2), "other_concerns", "camera", "time", "start_time", "end_time"
-- "context": array of related events from other cameras that occurred during overlapping time periods
+CRITICAL - Understanding Primary vs Contextual Items:
+- Items with "_is_primary": true are events that REQUIRE REVIEW and MUST be included in the report
+- Items with "_is_primary": false are additional context from other camera perspectives that overlap in time
+- **DO NOT create separate bullet points or sections for contextual items**
+- **ONLY use contextual items to enrich and inform the description of primary items**
+- The "_camera" field indicates which camera captured each event
+- **When a contextual item provides relevant background, you MUST incorporate it directly into the primary event's bullet point**
+- Contextual information often explains or de-escalates seemingly suspicious primary events
 
-Report Structure - Use this EXACT format:
+Rules for the report:
 
-# Security Summary - {time_range}
+- Title & overview
+  - Start with:
+    # Security Summary - {time_range}
+  - Write a 1-2 sentence situational overview capturing the general pattern of the period.
+  - Keep the overview high-level; specific details will be in the event bullets below.
 
-## Overview
-[Write 1-2 sentences summarizing the overall activity pattern during this period.]
+- Event details
+  - **ONLY create bullet points for PRIMARY items (_is_primary: true)**
+  - **Do NOT create sections or bullets for events that don't exist**
+  - Do NOT create separate bullets for contextual items
+  - Present primary events in chronological order as a bullet list.
+  - **CRITICAL: When contextual items overlap with a primary event, you MUST weave that information directly into the same bullet point**
+  - Format: **[Timestamp]** - [Description incorporating any contextual information]. [Camera info]. (threat level: X)
+  - If contextual information provides an explanation (e.g., delivery truck → person is likely delivery driver), reflect this understanding in your description and potentially adjust the perceived threat level
+  - If multiple PRIMARY events occur within the same minute, combine them into a single bullet with sub-points.
+  - Use bold timestamps for clarity.
+  - Camera format: "Camera: [camera name]" or mention contextual cameras inline when relevant
+  - Group bullets under subheadings ONLY when you have actual PRIMARY events to list (e.g., Porch Activity, Unusual Behavior).
 
----
+- Threat levels
+  - Show the threat level for PRIMARY events using these labels:
+    - Threat level 0: "Normal"
+    - Threat level 1: "Needs review"
+    - Threat level 2: "Security concern"
+  - Format as (threat level: Normal), (threat level: Needs review), or (threat level: Security concern).
+  - **When contextual items clearly explain a primary event (e.g., delivery truck explains person at door), you should describe it as normal activity and note the explanation**
+  - **Your description and tone should reflect the fuller understanding provided by contextual information**
+  - Example: Primary event says "unidentified person with face covering" but context shows delivery truck → describe as "delivery person (truck visible on Front Driveway Cam)" rather than emphasizing suspicious elements
+  - The stored threat level remains as originally classified, but your narrative should reflect the contextual understanding
+  - If multiple PRIMARY events at the same time share the same threat level, only state it once.
 
-## Timeline
+- Final assessment
+  - End with a Final Assessment section.
+  - If all primary events are threat level 0 or explained by contextual items:
+    Final assessment: Only normal residential activity observed during this period.
+  - If threat level 1 events are present:
+    Final assessment: Some activity requires review but no security concerns identified.
+  - If threat level 2 events are present, clearly summarize them as Security concerns requiring immediate attention.
+  - Keep this section brief - do not repeat details from the event descriptions above.
 
-[Group events by time periods (e.g., "Morning (6:00 AM - 12:00 PM)", "Afternoon (12:00 PM - 5:00 PM)", "Evening (5:00 PM - 9:00 PM)", "Night (9:00 PM - 6:00 AM)"). Use appropriate time blocks based on when events occurred.]
-
-### [Time Block Name]
-
-**HH:MM AM/PM** | [Camera Name] | [Threat Level Indicator]
-- [Event title]: [Clear description incorporating contextual information from the "context" array]
-- Context: [If context array has items, mention them here, e.g., "Delivery truck present on Front Driveway Cam (HH:MM AM/PM)"]
-- Assessment: [Brief assessment incorporating context - if context explains the event, note it here]
-
-[Repeat for each event in chronological order within the time block]
-
----
-
-## Summary
-[One sentence summarizing the period. If all events are normal/explained: "Routine activity observed." If review needed: "Some activity requires review but no security concerns." If security concerns: "Security concerns requiring immediate attention."]
-
-Guidelines:
-- List ALL events in chronological order, grouped by time blocks
-- Threat level indicators: ✓ Normal, ⚠️ Needs review, 🔴 Security concern
-- Integrate contextual information naturally - use the "context" array to enrich each event's description
-- If context explains the event (e.g., delivery truck explains person at door), describe it accordingly (e.g., "delivery person" not "unidentified person")
-- Be concise but informative - focus on what happened and what it means
-- If contextual information makes an event clearly normal, reflect that in your assessment
-- Only create time blocks that have events - don't create empty sections
+- Conciseness
+  - Do not repeat benign clothing/appearance details unless they distinguish individuals.
+  - Summarize similar routine events instead of restating full scene descriptions.
+  - When incorporating contextual information, do so briefly and naturally within the primary event description.
+  - Avoid lengthy explanatory notes - integrate context seamlessly into the narrative.
 """
 
-        timeline_summary_prompt += "\n\nEvents:\n"
-        for event in events:
-            timeline_summary_prompt += f"\n{event}\n"
+        for item in segments:
+            timeline_summary_prompt += f"\n{item}"
 
         if debug_save:
             with open(

frigate/track/object_processing.py

@@ -78,8 +78,6 @@ class TrackedObjectProcessor(threading.Thread):
             [
                 CameraConfigUpdateEnum.add,
                 CameraConfigUpdateEnum.enabled,
-                CameraConfigUpdateEnum.motion,
-                CameraConfigUpdateEnum.objects,
                 CameraConfigUpdateEnum.remove,
                 CameraConfigUpdateEnum.zones,
             ],

web/public/locales/en/views/settings.json

@@ -330,8 +330,7 @@
         "audioCodecRequired": "An audio stream is required to support audio detection.",
         "restreamingWarning": "Reducing connections to the camera for the record stream may increase CPU usage slightly.",
         "brands": {
-          "reolink-rtsp": "Reolink RTSP is not recommended. Enable HTTP in the camera's firmware settings and restart the wizard.",
-          "reolink-http": "Reolink HTTP streams should use FFmpeg for better compatibility. Enable 'Use stream compatibility mode' for this stream."
+          "reolink-rtsp": "Reolink RTSP is not recommended. Enable HTTP in the camera's firmware settings and restart the wizard."
         },
         "dahua": {
           "substreamWarning": "Substream 1 is locked to a low resolution. Many Dahua / Amcrest / EmpireTech cameras support additional substreams that need to be enabled in the camera's settings. It is recommended to check and utilize those streams if available."
@@ -770,8 +769,7 @@
         "updatePassword": "Update Password for {{username}}",
         "setPassword": "Set Password",
         "desc": "Create a strong password to secure this account.",
-        "multiDeviceWarning": "Any other devices where you are logged in will be required to re-login within {{refresh_time}}.",
-        "multiDeviceAdmin": "You can also force all users to re-authenticate immediately by rotating your JWT secret."
+        "multiDeviceWarning": "Any other devices where you are logged in will be required to re-login within {{refresh_time}}. You can also force all users to re-authenticate immediately by rotating your JWT secret."
       },
       "changeRole": {
         "title": "Change User Role",

web/src/components/overlay/SetPasswordDialog.tsx

@@ -26,7 +26,6 @@ import ActivityIndicator from "../indicators/activity-indicator";
 import { zodResolver } from "@hookform/resolvers/zod";
 import { useForm } from "react-hook-form";
 import { z } from "zod";
-import { useIsAdmin } from "@/hooks/use-is-admin";
 
 type SetPasswordProps = {
   show: boolean;
@@ -47,7 +46,6 @@ export default function SetPasswordDialog({
 }: SetPasswordProps) {
   const { t } = useTranslation(["views/settings", "common"]);
   const { getLocaleDocUrl } = useDocDomain();
-  const isAdmin = useIsAdmin();
 
   const { data: config } = useSWR("config");
   const refreshSeconds: number | undefined =
@@ -235,28 +233,19 @@ export default function SetPasswordDialog({
               ns: "views/settings",
             })}
           </p>
-          {isAdmin && (
-            <>
-              <p className="text-sm text-muted-foreground">
-                {t("users.dialog.passwordSetting.multiDeviceAdmin", {
-                  ns: "views/settings",
-                })}
-              </p>
-              <p className="text-sm text-primary-variant">
-                <a
-                  href={getLocaleDocUrl(
-                    "configuration/authentication#jwt-token-secret",
-                  )}
-                  target="_blank"
-                  rel="noopener noreferrer"
-                  className="inline-flex items-center text-primary"
-                >
-                  {t("readTheDocumentation", { ns: "common" })}
-                  <LuExternalLink className="ml-2 size-3" />
-                </a>
-              </p>
-            </>
-          )}
+          <p className="text-sm text-primary-variant">
+            <a
+              href={getLocaleDocUrl(
+                "configuration/authentication#jwt-token-secret",
+              )}
+              target="_blank"
+              rel="noopener noreferrer"
+              className="inline-flex items-center text-primary"
+            >
+              {t("readTheDocumentation", { ns: "common" })}
+              <LuExternalLink className="ml-2 size-3" />
+            </a>
+          </p>
         </DialogHeader>
 
         <Form {...form}>

web/src/components/settings/wizard/Step4Validation.tsx

@@ -490,13 +490,6 @@ function StreamIssues({
           message: t("cameraWizard.step4.issues.brands.reolink-rtsp"),
         });
       }
-
-      if (streamUrl.startsWith("http://") && !stream.useFfmpeg) {
-        result.push({
-          type: "warning",
-          message: t("cameraWizard.step4.issues.brands.reolink-http"),
-        });
-      }
     }
 
     // Video codec check