[Support]: configflow could not be loaded

[meinonA]

Describe the problem you are having

I installed the latest version (2.3) of Frigate NVR (Full Acces) and made the frigate.yml file.

Now I wanted to install Frigate in my settings > intergrations section. It does find the integration but when I try to install it, I get a "configflow could not be loaded" error.

So I searched in the Issues section on Github, removed the frigate file from my custom components and re-installed Frigate NVR (Full Acces) again and rebooted. This didn't solve the issue.

Version

0.9.4-26AE608

Frigate config file

mqtt:
  # Required: host name
  host: 192.168.1.189
  user: USERNAME
  # Optional: password
  # NOTE: Environment variables that begin with 'FRIGATE_' may be referenced in {}.
  #       eg. password: '{FRIGATE_MQTT_PASSWORD}'
  password: PASSWORD
cameras:
  # Name of your camera
  AD410:
    ffmpeg:
      inputs:
        - path: rtsp://@192.168.1.33:554/cam/realmonitor?channel=1&subtype=0&authbasic=64
          roles:
            - detect

    objects:
      track:
        - person
        - car
        - truck
        - bicycle
        - motorcycle
        - dog
        - cat

Relevant log output

[2021-11-16 00:25:28] watchdog.AD410                 ERROR   : FFMPEG process crashed unexpectedly for AD410.
[2021-11-16 00:25:28] watchdog.AD410                 ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
[2021-11-16 00:25:28] watchdog.AD410                 ERROR   : You may have invalid args defined for this camera.
[2021-11-16 00:25:28] ffmpeg.AD410.detect            ERROR   : [rtsp @ 0x55af3a30a940] method OPTIONS failed: 401 Unauthorized
[2021-11-16 00:25:28] ffmpeg.AD410.detect            ERROR   : rtsp://@192.168.1.33:554/cam/realmonitor?channel=1&subtype=0&authbasic=64: Server returned 401 Unauthorized (authorization failed)
[2021-11-16 00:25:28] frigate.video                  INFO    : AD410: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures
[2021-11-16 00:25:28] frigate.video                  INFO    : AD410: ffmpeg process is not running. exiting capture thread...
[2021-11-16 00:25:38] watchdog.AD410                 ERROR   : FFMPEG process crashed unexpectedly for AD410.
[2021-11-16 00:25:38] watchdog.AD410                 ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.

FFprobe output from your camera

[1] 552
[2] 523
bash: ffprobe: could not be found

Frigate stats

No response

Operating system

Debian

Install method

HassOS Addon

Coral version

CPU (no coral)

Network connection

Mixed

Camera make and model

Amcrest AD410

Any other information that may be helpful

No response

[ozett]

your log says this:
[2021-11-16 00:25:28] watchdog.AD410 ERROR : You may have invalid args defined for this camera.

so you may check/test your camera arguments?

[meinonA]

yeah, but I used the same as when I tested it with VLC player which did work. Also, I do see footage if I add the Frigate card to my lovelace dash but I can't see anything if I open the addon in the left menu.

Op di 16 nov. 2021 om 09:53 schreef toz @.***>:

your log says this: [2021-11-16 00:25:28] watchdog.AD410 ERROR : You may have invalid args defined for this camera.

so you may check/test your camera arguments?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/blakeblackshear/frigate/issues/2256#issuecomment-970054526, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGZF4LRBJGEIRIUH2N3MKDUMILZDANCNFSM5IC4YS5A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[ozett]

i would try to get the errors out of the log. try to change some ffmpeg parameters for that specific cam. try with ffprobe it there is no error.. may that helps. i dont use HAS/lovelace-dash, sorry.

[blakeblackshear]

Are you on an old version of home assistant?

[meinonA]

I don't think so: core-2021.11.4

Op di 16 nov. 2021 om 13:56 schreef Blake Blackshear < @.***>:

Are you on an old version of home assistant?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/blakeblackshear/frigate/issues/2256#issuecomment-970245257, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGZF4JXUT2DNR7UOLQE5W3UMJIILANCNFSM5IC4YS5A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[blakeblackshear]

The "configflow could not be loaded" error is related to the custom component in home assistant. Do you see anything that says why it couldn't be loaded in the HA logs?

[meinonA]

the HA logs don't give an error message.

I did find this in the MQTT log:

1637072626: Error: Unable to open include_dir '/share/mosquitto'. 1637072626: Error found at /etc/mosquitto/mosquitto.conf:33. [15:23:47] INFO: Successfully send discovery information to Home Assistant. [15:23:47] INFO: Successfully send service information to the Supervisor. Terminated [15:23:47] INFO: Starting mosquitto MQTT broker... 1637072627: Error: Unable to open include_dir '/share/mosquitto'. 1637072627: Error found at /etc/mosquitto/mosquitto.conf:33.

This is the MQTT config: logins:

• username: username password: password customize: active: false folder: mosquitto certfile: fullchain.pem keyfile: privkey.pem require_certificate: false

This is the Frigate log:

[services.d] done. [2021-11-16 15:32:05] frigate.app INFO : Starting Frigate (0.9.4-26ae608) [2021-11-16 15:32:05] frigate.app INFO : Creating directory: /tmp/cache Starting migrations [2021-11-16 15:32:05] peewee_migrate INFO : Starting migrations There is nothing to migrate [2021-11-16 15:32:05] peewee_migrate INFO : There is nothing to migrate [2021-11-16 15:32:05] detector.cpu INFO : Starting detection process: 225 [2021-11-16 15:32:05] frigate.app INFO : Output process started: 226 [2021-11-16 15:32:05] frigate.app INFO : Camera processor started for AD410: 229 [2021-11-16 15:32:05] ws4py INFO : Using epoll [2021-11-16 15:32:05] frigate.edgetpu WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes. [2021-11-16 15:32:05] frigate.app INFO : Capture process started for AD410: 232 [2021-11-16 15:32:05] ws4py INFO : Using epoll [2021-11-16 15:32:05] frigate.video INFO : AD410: ffmpeg sent a broken frame. memoryview assignment: lvalue and rvalue have different structures [2021-11-16 15:32:05] frigate.video INFO : AD410: ffmpeg process is not running. exiting capture thread... [2021-11-16 15:32:25] watchdog.AD410 ERROR : FFMPEG process crashed unexpectedly for AD410. [2021-11-16 15:32:25] watchdog.AD410 ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2021-11-16 15:32:25] watchdog.AD410 ERROR : You may have invalid args defined for this camera. [2021-11-16 15:32:25] ffmpeg.AD410.detect ERROR : [rtsp @ 0x560194963940] method OPTIONS failed: 401 Unauthorized [2021-11-16 15:32:25] ffmpeg.AD410.detect ERROR : @.***:554/cam/realmonitor?channel=1&subtype=0&authbasic=64: Server returned 401 Unauthorized (authorization failed)

If there are any other logs I can show you to find out what I could do to solve this, please feel free to say so.

thanks for helping me out in advance

Op di 16 nov. 2021 om 14:09 schreef Blake Blackshear < @.***>:

The "configflow could not be loaded" error is related to the custom component in home assistant. Do you see anything that says why it couldn't be loaded in the HA logs?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/blakeblackshear/frigate/issues/2256#issuecomment-970257883, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGZF4NC4NPENUODTHLLMADUMJJYVANCNFSM5IC4YS5A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[meinonA]

Hi Blake, we just had a short conversation on Discord, this is the issue I was trying to explain to you. As I already opened an issue, I thought it was best to continue this conversation here.

[blakeblackshear]

On the issue, you mention that you run frigate as an addon. Can you confirm that you have access to the frigate UI in the side panel and the addon is running?

[meinonA]

it is

[blakeblackshear]

Can you navigate to the addon under supervisor where you can see the CPU stats and post the url from the browser when on that screen?

[meinonA]

https://192.168.1.189:8123/hassio/addon/ccab4aaf_frigate-fa/info

[blakeblackshear]

For the integration, use http://ccab4aaf-frigate-fa:5000 as the url and see if it connects.

[meinonA]

I'll try this evening, but of the top of my head that's the preset URL. That didn't work

Op do 18 nov. 2021 01:34 schreef Blake Blackshear @.***

:

For the integration, use http://ccab4aaf-frigate-fa:5000 as the url and see if it connects.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/blakeblackshear/frigate/issues/2256#issuecomment-972374051, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGZF4OAGOWDCI2KBRQVOGTUMRCZLANCNFSM5IC4YS5A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[meinonA]

nope, it doesn't. failed to connect. I checked with both the ufw enabled and disabled

[blakeblackshear]

It's definitely different than the preset url. Have you modified any of the settings for the addon for exposed ports?

[meinonA]

nope, RTMP is 1935 and webinterface is 5000

[meinonA]

@blakeblackshear ?

[blakeblackshear]

Do you know how to get a shell into the home assistant container or hassos somehow? I don't know why this wouldn't be working for you. If the addon is running properly, you should be able to run the following command from the home assistant container to test connectivity:

curl http://ccab4aaf-frigate-fa:5000/api/version

[meinonA]

You mean I could install a terminal addon and run curl http://ccab4aaf-frigate-fa:5000/api/version ?

Op za 20 nov. 2021 00:15 schreef Blake Blackshear @.***

:

Do you know how to get a shell into the home assistant container or hassos somehow? I don't know why this wouldn't be working for you. If the addon is running properly, you should be able to run the following command from the home assistant container to test connectivity:

curl http://ccab4aaf-frigate-fa:5000/api/version

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/blakeblackshear/frigate/issues/2256#issuecomment-974533126, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGZF4JOM7M5CK3ZUDFJ2MDUM3LB5ANCNFSM5IC4YS5A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[meinonA]

Curl (6) could not resolve host

[blakeblackshear]

Do you get any output when running docker ps?

[meinonA]

how do I do that if I run supervised?

Op za 20 nov. 2021 om 15:47 schreef Blake Blackshear < @.***>:

Do you get any output when running docker ps?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/blakeblackshear/frigate/issues/2256#issuecomment-974660153, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGZF4JEUYXVFIJZJNEW6ZLUM6YIFANCNFSM5IC4YS5A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[blakeblackshear]

I didn't realize you were running supervised. You should be able to run that command directly on the host.

[meinonA]

I do get some output of a few addons including MQTT but I don't see the output for Frigate

[blakeblackshear]

Is the frigate addon not running? Can you post a screenshot of the running addon from the supervisor in home assistant?

[meinonA]

it does run

[blakeblackshear]

Does it stay running? You should definitely see it listed when running docker ps on the host.

[stale[bot]]

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.