[Bug]: When two cameras have recording off, the third camera does not trigger events #15368

italicize9610 · 2024-12-06T04:12:09Z

italicize9610
Dec 6, 2024

Checklist

I have updated to the latest available Frigate version.
I have cleared the cache of my browser.
I have tried a different browser to see if it is related to my browser.
I have tried reproducing the issue in incognito mode to rule out problems with any third party extensions or plugins I have installed.

Describe the problem you are having

I have 3 cameras set up. I also have an automation to turn off detection and recordings for 2 of those cameras (facing into my house) when I leave my house. The 3rd camera (doorbell camera, facing outwards) is constantly recording and detecting and is never turned off.

In Frigate 0.15 Beta 2, when my automation turns off detection and recordings for 2 of those cameras, the doorbell camera also fails to produce any events. It is as if detection and recording is also turned off for the 3rd camera.

In Frigate 0.14, with the exact same config and the exact same automation, the doorbell camera continues to produce events. The only change between the versions is that I point the integration to -beta (so that the entities continue to exist). Everything else is the same.

Steps to reproduce

Create an automation turning off record and detection (switch.camera_recordings and switch.camera_detect) for 2 of 3 cameras for any trigger.
Activate the automation.
Note that Camera 3, the unaffected camera, also fails to produce any events somehow, even though it is still recording and detecting. Cameras 1 and 2 also do not produce events but that is expected.
Turn on record and detection for the 2 of 3 cameras.
Now note that Camera 3 begins to produce events as expected (as do Cameras 1 and 2 as expected).

Version

0.15 - Beta 2

In which browser(s) are you experiencing the issue with?

No response

Frigate config file

go2rtc:
  streams:
    doorbell: 
      - ffmpeg:rtsp://XXX:[email protected]/Preview_01_main#video=copy#audio=copy#audio=opus       
    upstairs: 
      - ffmpeg:rtsp://XXX:[email protected]/Preview_01_main#video=copy#audio=copy#audio=opus      
    downstairs: 
      - ffmpeg:rtsp://XXX:[email protected]/Preview_01_main#video=copy#audio=copy#audio=opus       

mqtt:
  enabled: true
  host: core-mosquitto
  port: XXX
  user: XXX
  password: XXX

detectors: # <---- add detectors
  coral:
    type: edgetpu
    device: usb

cameras:
###### DOORBELL CAMERA ######
  doorbell: # <------ Name the camera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/doorbell
          input_args: preset-rtsp-generic
          roles:
            - record
            - detect
      hwaccel_args: preset-vaapi
      output_args:
        record: preset-record-generic-audio-copy
    motion:
      mask: 0.139,0.958,0.295,0.958,0.296,0.995,0.139,0.993
    zones:
      Front_of_door:
        coordinates: 0.001,0.001,0.001,0.999,0.999,0.999,0.999,0.001
        loitering_time: 5
        inertia: 3
    review:
      alerts:
        required_zones: Front_of_door

###### UPSTAIRS CAMERA ######  
  upstairs: # <------ Name the camera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/upstairs
          input_args: preset-rtsp-generic
          roles:
            - record
            - detect
      hwaccel_args: preset-vaapi
      output_args:
        record: preset-record-generic-audio-copy
    motion:
      mask: 0.14,0.957,0.141,0.998,0.299,0.996,0.3,0.959
###### DOWNSTAIRS CAMERA ###### 
  downstairs: # <------ Name the camera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/downstairs
          input_args: preset-rtsp-generic
          roles:
            - record
            - detect
      hwaccel_args: preset-vaapi
      output_args:
        record: preset-record-generic-audio-copy
    motion:
      mask: 0.139,0.959,0.143,0.997,0.294,0.998,0.292,0.962

record:
  enabled: true
  events:
    pre_capture: 10
    post_capture: 10
    retain:
      default: 7
      mode: all

objects:
  track:
    - person

detect:
  enabled: true
  width: 1280
  height: 960
  fps: 5

snapshots:
  enabled: true
  retain:
    default: 7

version: 0.14

docker-compose file or Docker CLI command

NA

Relevant Frigate log output

2024-12-05 05:49:40.885762891 [INFO] Preparing Frigate...
2024-12-05 05:49:40.902637216 [INFO] Starting Frigate...
2024-12-05 05:49:42.421329923 [2024-12-05 13:49:42] frigate.app 2024-12-05 05:49:42.421465371 [2024-12-05 13:49:42] frigate.app 2024-12-05 05:49:42.421468870 [2024-12-05 13:49:42] frigate.util.config 2024-12-05 05:49:42.446101226 [2024-12-05 13:49:42] frigate.util.config 2024-12-05 05:49:42.642761937 [2024-12-05 13:49:42] frigate.util.services 2024-12-05 05:49:42.674583401 [2024-12-05 13:49:42] peewee_migrate.logs 2024-12-05 05:49:42.675374983 [2024-12-05 13:49:42] peewee_migrate.logs 2024-12-05 05:49:42.684617324 [2024-12-05 13:49:42] frigate.app 2024-12-05 05:49:42.690980987 [2024-12-05 13:49:42] frigate.app 2024-12-05 05:49:42.691203673 [2024-12-05 13:49:42] frigate.app 2024-12-05 05:49:42.716377978 [2024-12-05 13:49:42] detector.coral 2024-12-05 05:49:45.331755252 [2024-12-05 13:49:42] frigate.app 2024-12-05 05:49:45.332259228 [2024-12-05 13:49:42] frigate.detectors.p 2024-12-05 05:49:45.332943978 [2024-12-05 13:49:42] frigate.app 2024-12-05 05:49:45.333226642 [2024-12-05 13:49:42] frigate.app 2024-12-05 05:49:45.333448146 [2024-12-05 13:49:42] frigate.app 2024-12-05 05:49:45.333454321 [2024-12-05 13:49:42] frigate.app 2024-12-05 05:49:45.333614895 [2024-12-05 13:49:42] frigate.app 2024-12-05 05:49:45.333781056 [2024-12-05 13:49:42] frigate.app 2024-12-05 05:49:45.337564005 [2024-12-05 13:49:45] frigate.detectors.p 2024-12-05 05:51:36.618180711 [2024-12-05 13:51:36] frigate.comms.dispatcher 2024-12-05 05:51:36.661292944 [2024-12-05 13:51:36] frigate.comms.dispatcher 2024-12-05 05:51:36.662990781 [2024-12-05 13:51:36] frigate.comms.dispatcher 2024-12-05 05:51:36.664259772 [2024-12-05 13:51:36] frigate.comms.dispatcher 2024-12-05 11:40:59.855988578 [2024-12-05 19:40:59] frigate.comms.dispatcher 2024-12-05 11:40:59.897637702 [2024-12-05 19:40:59] frigate.comms.dispatcher 2024-12-05 11:40:59.898478192 [2024-12-05 19:40:59] frigate.comms.dispatcher 2024-12-05 11:40:59.899943943 [2024-12-05 19:40:59] frigate.comms.dispatcher INFO : Starting Frigate (0.14.1-f4f3cfa)
INFO : Creating directory: /tmp/cache
INFO : Checking if frigate config needs migration...
INFO : frigate config does not need migration...
INFO : Automatically detected vaapi hwaccel for video decoding
INFO : Starting migrations
INFO : There is nothing to migrate
INFO : Recording process started: 391
INFO : Recording process started: 397
INFO : go2rtc process pid: 98
INFO : Starting detection process: 420
INFO : Output process started: 422
lugins.edgetpu_tfl INFO : Attempting to load TPU as usb
INFO : Camera processor started for doorbell: 439
INFO : Camera processor started for upstairs: 440
INFO : Camera processor started for downstairs: 444
INFO : Capture process started for doorbell: 451
INFO : Capture process started for upstairs: 457
INFO : Capture process started for downstairs: 466
lugins.edgetpu_tfl INFO : TPU found
INFO : Turning off recordings for upstairs
INFO : Turning off detection for downstairs
INFO : Turning off detection for upstairs
INFO : Turning off recordings for downstairs
INFO : Turning on recordings for upstairs
INFO : Turning on detection for downstairs
INFO : Turning on detection for upstairs
INFO : Turning on recordings for downstairs

Relevant go2rtc log output

2024-12-05 05:49:40.890668208 [INFO] Preparing new go2rtc config...
2024-12-05 05:49:40.940279545 [INFO] Got IP address from supervisor: 192.168.50.139
2024-12-05 05:49:40.970793289 [INFO] Got WebRTC port from supervisor: 8555
2024-12-05 05:49:41.267213523 [WARN] Using go2rtc binary from '/config/go2rtc' instead of the embedded one
2024-12-05 05:49:41.267217408 [INFO] Starting go2rtc...
2024-12-05 05:49:41.421013832 13:49:41.420 INF go2rtc platform=linux/amd64 revision=dbe9e4a version=1.9.7
2024-12-05 05:49:41.423549136 13:49:41.422 INF config path=/dev/shm/go2rtc.yaml
2024-12-05 05:49:41.423552359 13:49:41.422 INF [rtsp] listen addr=:8554
2024-12-05 05:49:41.423553555 13:49:41.422 INF [api] listen addr=:1984
2024-12-05 05:49:41.423562132 13:49:41.422 INF [webrtc] listen addr=:8555/tcp
2024-12-05 05:49:50.884943862 [INFO] Starting go2rtc healthcheck service...

Operating system

HassOS

Install method

HassOS Addon

Network connection

Mixed

Camera make and model

Reolink E1 Zoom x2 and Wireless Doorbell

Screenshots of the Frigate UI's System metrics pages

NA. Coral running at 9-10 ms inference speeds.

Any other information that may be helpful

I use Reolink cameras. But this occurs whether I use HTTP streams or not, whether I use a separate substream or not, whether I use restream preset or generic preset. The only config difference between 0.14 to 0.15 is that instead of events it is now split into alert and detections (this was done via the migration on startup of 0.15). For what it's worth, my setup runs 100% stable on 0.14 with the config above (uptime more than 7 days without a single error).

hawkeye217 · 2024-12-06T04:25:57Z

hawkeye217
Dec 6, 2024
Collaborator

Your Frigate logs will show when recording and detection is enabled/disabled for each camera. We can't help without those logs.

If no logs are produced, this would point to an issue with the integration or how you've set it up.

15 replies

hawkeye217 Dec 17, 2024
Collaborator

So to be clear, does this issue only occur with the doorbell camera?

italicize9610 Dec 17, 2024
Author

it occurs with any combination of cameras. doorbell+living+downstairs off, upstairs on. living+downstairs+upstairs off, downstairs on. the on camera will not produce events, even though it does identify objects in debug view.

hawkeye217 Dec 17, 2024
Collaborator

As a test, can you comment out the loitering_time for the doorbell zones and see if the issue still occurs?

italicize9610 Dec 19, 2024
Author

hey @hawkeye217 my issue no longer seems to happen. I'm not sure what changed, I didn't change my hardware or my config or loitering time. regardless, everything looks ok now. guess we can close this topic!

hawkeye217 Dec 19, 2024
Collaborator

Great, glad to hear it's working.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Bug]: When two cameras have recording off, the third camera does not trigger events #15368

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 1 comment 15 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

[Bug]: When two cameras have recording off, the third camera does not trigger events #15368

italicize9610 Dec 6, 2024

Checklist

Describe the problem you are having

Steps to reproduce

Version

In which browser(s) are you experiencing the issue with?

Frigate config file

docker-compose file or Docker CLI command

Relevant Frigate log output

Relevant go2rtc log output

Operating system

Install method

Network connection

Camera make and model

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

Replies: 1 comment · 15 replies

hawkeye217 Dec 6, 2024 Collaborator

hawkeye217 Dec 17, 2024 Collaborator

italicize9610 Dec 17, 2024 Author

hawkeye217 Dec 17, 2024 Collaborator

italicize9610 Dec 19, 2024 Author

hawkeye217 Dec 19, 2024 Collaborator

italicize9610
Dec 6, 2024

Replies: 1 comment 15 replies

hawkeye217
Dec 6, 2024
Collaborator

hawkeye217 Dec 17, 2024
Collaborator

italicize9610 Dec 17, 2024
Author

hawkeye217 Dec 17, 2024
Collaborator

italicize9610 Dec 19, 2024
Author

hawkeye217 Dec 19, 2024
Collaborator