blakeblackshear
commented
2 years ago You have record disabled in your config. It's not going to record any video when recording is disabled.
Closed HSB-collab closed 2 years ago
blakeblackshear
commented
2 years ago You have record disabled in your config. It's not going to record any video when recording is disabled.
HSB-collab
commented
2 years ago Thanks for the prompt reply @blakeblackshear. I am afraid I copied the whole debug stats and did not make it clear above that I had 2 cameras and had only enabled one of them to record (Camera2). The first camera (Camera1) is not enabled which is what you have correctly picked up but I was doing my testing on the 2nd camera (Camera2) which you can see from the above debug stats is enabled. The excerpt from the debug stats is below.
Do you have any other suggestions? Thanks in anticipation (I really do appreciate the help you give on this amazing project).
"objects": {
"filters": {
"person": {
"mask": null,
"max_area": 24000000,
"min_area": 0,
"min_score": 0.5,
"threshold": 0.7
}
},
"mask": "",
"track": [
"person"
]
},
"record": {
"enabled": true,
"events": {
"max_seconds": 60,
"objects": null,
"post_capture": 5,
"pre_capture": 5,
"required_zones": [],
"retain": {
"default": 10,
"mode": "active_objects",
"objects": {}
}
},
"expire_interval": 60,
"retain": {
"days": 0,
"mode": "all"
},
"retain_days": null
},
NickM-27
commented
2 years ago @HSB-collab It is still disabled in your config that you originally posted:
Camera2:
ffmpeg:
inputs:
- path: rtsp://*****:******@10.0.0.125/live
roles:
- detect
- rtmp
- record
detect:
enabled: False
width: 1920
height: 1080
fps: 5
# motion:
# mask:
# - 449,925,880,604,774,55,360,199,0,354,0,500
objects:
track:
- person
record:
enabled: False
# retain_days: 0 #deprecated after release 0.10.0 -use mode under retain
events:
max_seconds: 60
retain:
default: 10
mode: active_objects
snapshots:
enabled: True
crop: True
height: 500it must be enabled in the config. If you have it disabled in the config the UI and MQTT will not fix this.
NickM-27
commented
2 years ago @blakeblackshear I wonder if it would be a good idea to have the UI button disabled and MQTT throw an error if the recording is attempted to be enabled for a camera with it disabled in the original config?
HSB-collab
commented
2 years ago THANK YOU! @NickM-27 you were correct. I had assumed that recording was disabled in the config file and then enabled via MQTT which is what I did. Now that I have enabled recording in the config file, it is working. Thanks so much - it was driving me crazy. Your suggestion of an error message would certainly have saved me a lot of time.
blakeblackshear
commented
2 years ago The way this is handled in config parsing makes it difficult to know at runtime whether or not record was disabled at startup. At the very least, there could be some info about this in the example config docs.
HSB-collab
commented
2 years ago Maybe if you put something in the documentation (which I went through carefully) to explain how to record active objects that would be good. Or in the documentation where you explain the configuration file and have the comment "# active_objects - save all recording segments with active/moving objects" mention that you still need to enable record in the config.yml file.
NickM-27
commented
2 years ago I'll take a stab at it and see if I can get it to work well figuring out if record is disabled in the file and I'll update the docs either way.
stale[bot]
commented
2 years ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
metaphorLion
commented
2 years ago This project just send snapshots to a discord using a bot --> https://github.com/vibin18/go-mqtt-discord
Describe the problem you are having
This issue is similar to #3033 but different so I have started a new issue. I really hope someone can help me because it is driving me crazy!
I have a Home-Assistant and Frigate setup which works perfectly so I decided to replicate the setup on a new machine for a relative who wants to run HA. The new setup is almost identical in every way. I am testing it on the same cameras. The original setup works perfectly - it detects events, produces snapshots and records clips when an event is detected.
My new setup detects events, produces snapshots but I cannot get it to record clips when an event is detected.
The setup is as follows: PC running a Core-i3 (2nd generation - that is one of 2 differences with the original setup which has a 3rd generation core-i3); 8Gbyte RAM, 500Mbyte hard disk (this is the other difference with the original setup which has a 120Gbyte SSD).
Both machines are running Lubuntu 20.04.
Both machines are running Home-Assistant Supervised in a Virtualbox VM.
Both machines are running Frigate 0.10.1-amd64 inside a Docker container. Both machines launch Frigate with the same docker-composer frigate.yaml file. Both machines have identical config.yml files for the Frigate Docker container. Both machines give identical outputs from ffprobe on the cameras.
Version
0.10.1-83481AF
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Debian
Install method
Docker Compose
Coral version
PCIe
Network connection
Wired
Camera make and model
Wyze Camera v2, Wyze Camera Pan, Sercomm iCamera2
Any other information that may be helpful
I have 3 different types of camera - all exhibit the same issue, namely I get recordings in the original setup but not in the new one.
In the setup that is failing to record I have a ton of hard disk space (500Gbyte) so I am not running out of free disk space.
Could the fact that the original setup runs on an SSD and the new one on a mechanical drive make a difference?