Mark Reolink PTZ as Frigate-autotracking incompatible (v1.37.0)#128
Merged
Conversation
#124 part 2, Reolink slice. On 20 mechanical-PTZ Reolink with a Frigate config: configs.frigate.autotracking=false + note (Reolink = absolute ONVIF PTZ; Frigate autotracking needs relative move), and ptz.onvif_ptz=absolute on the 18 exposing ONVIF. Camera-side ptz.autotracking unchanged. Community-sourced integration fact, labeled. Fixed dual-lens (Duo/Elite) excluded.
Sets ptz.autotracking:true on 10 Reolink PTZ confirmed via official Reolink product pages / support table: Argus Track, E1, E1 Zoom, RLC-823S2, Omvi 3I PoE/WiFi, Omvi X16, Go PT Plus/Ultra, Go Ranger PT (24->34). 4 are hw-revision gated (model tracks current production). Folded into the Reolink autotracking PR.
…autotracking # Conflicts: # CHANGELOG.md # package.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#124 part 2 — Reolink slice. Encodes the camera-side vs Frigate-autotracking distinction for Reolink: onboard tracking works, but Frigate autotracking does not because Reolink exposes only absolute ONVIF PTZ (Frigate needs relative movement).
Changed (20 mechanical-PTZ Reolink with a Frigate config)
configs.frigate.autotracking: false+ note ("Reolink uses absolute ONVIF PTZ; Frigate autotracking requires relative movement") on all 20.ptz.onvif_ptz: absoluteon the 18 that expose ONVIF (the 2 without ONVIF in our data — rlc-823a, rlc-830a — get the frigate flag only, no ONVIF claim).ptz.autotracking(which genuinely works) left untouched and distinct.Models: E1 Outdoor ×5, E1 Pro, E1 Zoom, RLC-823A/-16x/S1/S1W/S2, RLC-830A, RLC-523WA, RLC-81PA, RLC-423, P830, TrackMix PoE/WiFi, TrackFlex.
Scope / sourcing (per your call)
ptz.autotrackinggaps on ~10 other Reolink PT models (argus-track, duo-3, omvi, etc.) are a separate follow-up, not in this PR.AJV passes on all 2,230; build + gen-docs clean.
package.json/CHANGELOG rebase.