#Camera recording is tasking...
1 messages · Page 1 of 1 (latest)
also the recordings miss a coupe seconds each time they save and start anew. Any suggestions for fixes?
Use Frigate and a Coral TPU, it offloads a lot of the CPU work to the TPU and you should be able to run a typical household (like 5-10 cameras) on a 6700K no problem with reasonable CPU load
I played around with frigate, but the reolink integration is far more robust when it comes to the camera features. I don't need the coral because all the object detection happens on board (camera.) is frigate better at recording than the record function built in?
alias: Front Record
description: ""
triggers:
- trigger: state
entity_id:- switch.front_record
to: "on"
- switch.front_record
- trigger: homeassistant
event: start
conditions: []
actions: - repeat:
sequence:
- action: camera.record
metadata: {}
data:
filename: >-
/media/Reolink/Recordings/Front/{{now().strftime("%d•%m•%Y -
%H:%M:%S")}}.mp4
lookback: 6
duration: 1800
target:
entity_id: camera.front_clear
while:
- condition: state
entity_id: switch.front_record
state: "on"
mode: single
I have 4 of these... Is this just bad?
Every time the automation runs it has to make a new connection to the camera, which is why you see a gap. If you want to record you should use something designed to do that long term, HA is not an NVR. Also there isn't a good way to view these recordings you're saving directly in a combined / succinct view.
That's where an NVR like Frigate comes in. Frigate has no requirement for object detection, you can just run recording if you want to
Right on, I will give frigate another try, it didn't seem very well put together when I checked it out last.
if somebody could help me turn off detections... That would be appreciated