Replies: 1 comment
-
|
This is a duplicate of #11314 feel free to leave a 👍 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Problem / Use Case
Currently, when disabling/enabling cameras through the UI or Home Assistant, the state is temporary and resets to the config.yml value after Frigate restarts. This creates friction for common scenarios:
Proposed Solution
Add an option to persist camera enable/disable state to the database, with priority over config.yml:
Option 1 - Global setting:
Option 2 - Per-camera setting:
Behavior
Alternatives Considered
Implementation Notes
configtable or newcamera_statetableGET/POST /api/cameras/{name}/stateSimilar Features
Other NVR software with this behavior:
Would this feature be aligned with Frigate's philosophy? Happy to contribute if there's interest!
Beta Was this translation helpful? Give feedback.
All reactions