Frigate Home Assistant Integration Showing Entities unavailable then available #16092

cloudbr34k84 · 2025-01-23T10:07:12Z

cloudbr34k84
Jan 23, 2025

Describe the problem you are having

For some reason, the frigate integration disconnects and reconnects. In the video attached, between the 7 - 10 second mark, the entities become unavailable then available.

IM running frigate on Proxmox

WHere do I start to try and diagnose this issue??

Process Output:

vainfo: VA-API version: 1.17 (libva 2.10.0)
vainfo: Driver version: Mesa Gallium driver 22.3.6 for AMD Radeon Graphics (rembrandt, LLVM 15.0.6, DRM 3.57, 6.8.12-5-pve)
vainfo: Supported profile and entrypoints
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD
VAProfileAV1Profile0 : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc

screencast-homeassistant_local_8123-2025_01_23-19_55_55.webm

Version

0.14.1-

What browser(s) are you using?

No response

Frigate config file

cameras:
  frigate_front_video_doorbell:
    ffmpeg:
      inputs:
        - path: rtsp://xxxxxx:xxxxxxxxx@xxxxxxxx:554/h264Preview_01_main
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://xxxxx:xxxxxx@xxxxxxxx:554/h264Preview_01_sub
          input_args: preset-rtsp-restream
          roles:
            - detect

Relevant Frigate log output

2025-01-23 15:21:21.636233  [2025-01-23 15:21:21] frigate.app                    INFO    : Recording process started: 395188
2025-01-23 15:21:21.639286  [2025-01-23 15:21:21] frigate.app                    INFO    : go2rtc process pid: 141
2025-01-23 15:21:21.667930  [2025-01-23 15:21:21] detector.coral                 INFO    : Starting detection process: 395210
2025-01-23 15:21:24.828798  [2025-01-23 15:21:21] frigate.app                    INFO    : Output process started: 395213
2025-01-23 15:21:24.828866  [2025-01-23 15:21:21] frigate.app                    INFO    : Camera processor started for frigate_front_video_doorbell: 395229
2025-01-23 15:21:24.828888  [2025-01-23 15:21:21] frigate.app                    INFO    : Camera processor started for frigate_front_top_camera: 395235
2025-01-23 15:21:24.833020  [2025-01-23 15:21:21] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2025-01-23 15:21:24.833113  [2025-01-23 15:21:21] frigate.app                    INFO    : Camera processor started for frigate_front_balcony_camera: 395245
2025-01-23 15:21:24.833199  [2025-01-23 15:21:24] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found
2025-01-23 15:21:24.833235  [2025-01-23 15:21:21] frigate.app                    INFO    : Camera processor started for frigate_driveway_camera: 395246
2025-01-23 15:21:24.833268  [2025-01-23 15:21:21] frigate.app                    INFO    : Camera processor started for frigate_back_top_camera: 395258
2025-01-23 15:21:24.833296  [2025-01-23 15:21:21] frigate.app                    INFO    : Camera processor started for frigate_pool_camera: 395265
2025-01-23 15:21:24.833324  [2025-01-23 15:21:21] frigate.app                    INFO    : Camera processor started for frigate_laundry_camera: 395275
2025-01-23 15:21:24.833338  [2025-01-23 15:21:21] frigate.app                    INFO    : Camera processor started for frigate_garage_camera: 395283
2025-01-23 15:21:24.833455  [2025-01-23 15:21:21] frigate.app                    INFO    : Capture process started for frigate_front_video_doorbell: 395291
2025-01-23 15:21:24.833480  [2025-01-23 15:21:21] frigate.app                    INFO    : Capture process started for frigate_front_top_camera: 395296
2025-01-23 15:21:24.833492  [2025-01-23 15:21:21] frigate.app                    INFO    : Capture process started for frigate_front_balcony_camera: 395300
2025-01-23 15:21:24.833504  [2025-01-23 15:21:21] frigate.app                    INFO    : Capture process started for frigate_driveway_camera: 395305
2025-01-23 15:21:24.833516  [2025-01-23 15:21:21] frigate.app                    INFO    : Capture process started for frigate_back_top_camera: 395312
2025-01-23 15:21:24.833527  [2025-01-23 15:21:21] frigate.app                    INFO    : Capture process started for frigate_pool_camera: 395315
2025-01-23 15:21:24.833538  [2025-01-23 15:21:21] frigate.app                    INFO    : Capture process started for frigate_laundry_camera: 395321
2025-01-23 15:21:24.833568  [2025-01-23 15:21:21] frigate.app                    INFO    : Capture process started for frigate_garage_camera: 395327
2025-01-23 15:23:29.834580  [2025-01-23 15:23:29] frigate.ptz.onvif              ERROR   : Onvif is not setup for frigate_garage_camera
2025-01-23 15:42:55.616517  [2025-01-23 15:42:55] frigate.api.media              ERROR   : No recordings found for frigate_front_balcony_camera during the requested time range
2025-01-23 15:42:55.623957  [2025-01-23 15:42:55] frigate.api.review             WARNING : No motion data found for the requested time range
2025-01-23 15:42:56.636893  [2025-01-23 15:42:56] frigate.api.media              ERROR   : No recordings found for frigate_front_balcony_camera during the requested time range
2025-01-23 16:38:25.735433  [2025-01-23 16:38:25] frigate.ptz.onvif              ERROR   : Onvif is not setup for frigate_garage_camera
2025-01-23 17:57:15.431386  [2025-01-23 17:57:15] frigate.ptz.onvif              ERROR   : Onvif is not setup for frigate_garage_camera
2025-01-23 18:07:25.640913  [2025-01-23 18:07:25] frigate.ptz.onvif              ERROR   : Onvif is not setup for frigate_garage_camera
2025-01-23 18:08:47.151191  [2025-01-23 18:08:47] frigate.ptz.onvif              ERROR   : Onvif is not setup for frigate_garage_camera
2025-01-23 18:11:32.401362  [2025-01-23 18:11:32] frigate.ptz.onvif              ERROR   : Onvif is not setup for frigate_garage_camera
2025-01-23 18:38:40.759895  [2025-01-23 18:38:40] frigate.ptz.onvif              ERROR   : Onvif is not setup for frigate_garage_camera
2025-01-23 18:39:33.933870  [2025-01-23 18:39:33] frigate.ptz.onvif              ERROR   : Onvif is not setup for frigate_garage_camera
2025-01-23 18:40:11.337262  [2025-01-23 18:40:11] frigate.ptz.onvif              ERROR   : Onvif is not setup for frigate_garage_camera
2025-01-23 18:56:22.693572  [2025-01-23 18:56:22] frigate.ptz.onvif              ERROR   : Onvif is not setup for frigate_garage_camera
2025-01-23 19:31:47.652201  [2025-01-23 19:31:47] frigate.ptz.onvif              ERROR   : Onvif is not setup for frigate_garage_camera
2025-01-23 19:33:17.748520  [2025-01-23 19:33:17] frigate.ptz.onvif              ERROR   : Onvif is not setup for frigate_garage_camera
2025-01-23 19:44:55.636811  [2025-01-23 19:44:55] frigate.ptz.onvif              ERROR   : Onvif is not setup for frigate_garage_camera
2025-01-23 20:02:18.669397  [2025-01-23 20:02:18] frigate.comms.dispatcher       INFO    : Setting motion threshold for frigate_back_top_camera: 30
2025-01-23 20:02:18.670575  [2025-01-23 20:02:18] frigate.comms.dispatcher       INFO    : Setting motion contour area for frigate_back_top_camera: 10

Relevant go2rtc log output

2025-01-18 19:58:56.471582  [INFO] Preparing new go2rtc config...
2025-01-18 19:58:57.082292  [INFO] Starting go2rtc...
2025-01-18 19:58:57.154600  19:58:57.153 INF go2rtc platform=linux/amd64 revision=dbe9e4a version=1.9.7
2025-01-18 19:58:57.154650  19:58:57.154 INF config path=/dev/shm/go2rtc.yaml
2025-01-18 19:58:57.154675  19:58:57.154 INF [rtsp] listen addr=:8554
2025-01-18 19:58:57.154687  19:58:57.154 INF [webrtc] listen addr=:8555/tcp
2025-01-18 19:58:57.154936  19:58:57.154 INF [api] listen addr=:1984

FFprobe output from your camera

n/a

Frigate stats

No response

Install method

Proxmox via TTeck Script

docker-compose file or Docker CLI command

n/a

Object Detector

Coral

Network connection

Wired

Camera make and model

Reolink

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

No response

Answered by hawkeye217

Jan 23, 2025

You'll want to look into your MQTT broker. The integration uses Frigate's MQTT API.

View full answer

hawkeye217 · 2025-01-23T13:43:19Z

hawkeye217
Jan 23, 2025
Collaborator

You'll want to look into your MQTT broker. The integration uses Frigate's MQTT API.

1 reply

cloudbr34k84 Jan 23, 2025
Author

Thanks i didn't think to check the broker log

NickM-27 · 2025-01-23T13:47:09Z

NickM-27
Jan 23, 2025
Collaborator Sponsor

This issue usually means that you have multiple frigate instances connected on the same topic https://docs.frigate.video/troubleshooting/faqs#unable-to-publish-to-mqtt-client-is-not-connected

1 reply

cloudbr34k84 Jan 23, 2025
Author

I just downloaded MQTT Explorer and i can only see 1 frigate instance.

cloudbr34k84 · 2025-01-23T20:44:35Z

cloudbr34k84
Jan 23, 2025
Author

Just checked my Mosquito Broker logs. The 192.168.68.150:35104 is one I had it setup using docker, but that's been shutdown. or do I need to start it up and remove it from the config?

2025-01-24 06:36:06: New connection from 192.168.68.150:35104 on port 1883.
2025-01-24 06:36:06: Client frigate already connected, closing old connection.
2025-01-24 06:36:06: New client connected from 192.168.68.150:35104 as frigate (p2, c1, k60, u'mqtt-user').
2025-01-24 06:36:07: New connection from 192.168.68.184:51727 on port 1883.
2025-01-24 06:36:07: Client frigate already connected, closing old connection.

1 reply

hawkeye217 Jan 23, 2025
Collaborator

It may not have been shut down correctly then. Frigate disconnects from the broker when it shuts down, and even if it doesn't shut down cleanly, the broker will close any connection after a short timeout through LWT.

cloudbr34k84 · 2025-01-23T20:50:28Z

cloudbr34k84
Jan 23, 2025
Author

Well its seems all it took was restarting my broker.

0 replies

cloudbr34k84 · 2025-01-23T20:51:11Z

cloudbr34k84
Jan 23, 2025
Author

Thanks for helping!!

1 reply

hawkeye217 Jan 23, 2025
Collaborator

Great! Happy to help.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Frigate Home Assistant Integration Showing Entities unavailable then available #16092

{{title}}

Replies: 5 comments 4 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Frigate Home Assistant Integration Showing Entities unavailable then available #16092

cloudbr34k84 Jan 23, 2025

Describe the problem you are having

Version

What browser(s) are you using?

Frigate config file

Relevant Frigate log output

Relevant go2rtc log output

FFprobe output from your camera

Frigate stats

Install method

docker-compose file or Docker CLI command

Object Detector

Network connection

Camera make and model

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

Replies: 5 comments · 4 replies

hawkeye217 Jan 23, 2025 Collaborator

cloudbr34k84 Jan 23, 2025 Author

NickM-27 Jan 23, 2025 Collaborator Sponsor

cloudbr34k84 Jan 23, 2025 Author

cloudbr34k84 Jan 23, 2025 Author

hawkeye217 Jan 23, 2025 Collaborator

cloudbr34k84 Jan 23, 2025 Author

cloudbr34k84 Jan 23, 2025 Author

hawkeye217 Jan 23, 2025 Collaborator

cloudbr34k84
Jan 23, 2025

Replies: 5 comments 4 replies

hawkeye217
Jan 23, 2025
Collaborator

cloudbr34k84 Jan 23, 2025
Author

NickM-27
Jan 23, 2025
Collaborator Sponsor

cloudbr34k84 Jan 23, 2025
Author

cloudbr34k84
Jan 23, 2025
Author

hawkeye217 Jan 23, 2025
Collaborator

cloudbr34k84
Jan 23, 2025
Author

cloudbr34k84
Jan 23, 2025
Author

hawkeye217 Jan 23, 2025
Collaborator