You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe what you are trying to accomplish and why in non technical terms
I want to be able to mark a camera as "intermittent" in the config so that I can have a camera that I manually turn on and off without the logs getting polluted by a stack of error messages every 10 seconds:
ERROR: camera06: Unable to read frames from ffmpeg process.
ERROR: camera06: ffmpeg process is not running. exiting capture thread...
ERROR: Ffmpeg process crashed unexpectedly for camera06.
ERROR: The following ffmpeg logs include the last 100 lines prior to exit.
ERROR: [tcp] Connection to tcp://detect... failed: No route to host
ERROR: http://detect...: No route to host
ERROR: [tcp] Connection to tcp://record... failed: No route to host
ERROR: http://record...: No route to host
Describe the solution you'd like
I'd like to be able to set intermittent: true # default: false on a camera, and that it would no longer log these specific events as an error or even an info. It can optionally still be a debug log or a "camera came online" one-shot info and "camera went offline" one-shot info.
Describe alternatives you've considered
I tried playing around with the component specific logger overrides, but I can't find many examples of using this, and a total of 8 errors are thrown every 10 or so seconds by 3 different components:
frigate.video
watchdog.camera06
ffmpeg.camera06.detect
ffmpeg.camera06.record
I can hide some errors, but not all, because ffmpeg errors, even when hidden, trigger frigate.video errors, and I still want all other errors and infos to show up. I am uncertain if the logs configuration can be used for what I'm trying to accomplish.
Additional context
Perhaps there are more possibilities with the logging components, and if so, perhaps this case can be specifically documented. But configuring log behavior for a camera as "intermittent" seems involved enough that if it is possible, I couldn't figure it out on my own. I would still think a single configuration boolean to take care of all this for you is a good idea.
Reasons for intermittent camera's:
On cold windy days close the cat/dog flap, have intermittent camera to function as 'doorbell' for pet.;
Intermittent baby monitor;
Hall monitor;
Just a cam to play around with;
All of the above can be the same movable camera on different parts of the day.
The text was updated successfully, but these errors were encountered:
Describe what you are trying to accomplish and why in non technical terms
I want to be able to mark a camera as "intermittent" in the config so that I can have a camera that I manually turn on and off without the logs getting polluted by a stack of error messages every 10 seconds:
Describe the solution you'd like
I'd like to be able to set
intermittent: true # default: false
on a camera, and that it would no longer log these specific events as anerror
or even aninfo
. It can optionally still be adebug
log or a "camera came online" one-shotinfo
and "camera went offline" one-shotinfo
.Describe alternatives you've considered
I tried playing around with the component specific logger overrides, but I can't find many examples of using this, and a total of 8 errors are thrown every 10 or so seconds by 3 different components:
frigate.video
watchdog.camera06
ffmpeg.camera06.detect
ffmpeg.camera06.record
I can hide some errors, but not all, because
ffmpeg
errors, even when hidden, triggerfrigate.video
errors, and I still want all other errors and infos to show up. I am uncertain if thelogs
configuration can be used for what I'm trying to accomplish.Additional context
Perhaps there are more possibilities with the logging components, and if so, perhaps this case can be specifically documented. But configuring log behavior for a camera as "intermittent" seems involved enough that if it is possible, I couldn't figure it out on my own. I would still think a single configuration boolean to take care of all this for you is a good idea.
Reasons for intermittent camera's:
The text was updated successfully, but these errors were encountered: