frigate: [Config Support]: Frigate+ API Key not detected
Describe the problem you are having
Using HA frigate add-on, I set the PLUS_API_KEY but the “SEND TO FRIGATE+” button on events is greyed out and clicking it prompts me to setup a frigate+ account.
Version
0.11.1-2EADA21
Frigate config file
environment_vars:
PLUS_API_KEY: <api_key>
...
Relevant log output
Nothing looks relevant, searched for “PLUS_API_KEY” and “env” and “frigate+” without finding anything.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2023-04-06 23:15:26] frigate.app INFO : Starting Frigate (0.11.1-2eada21)
[2023-04-06 23:15:26] frigate.app INFO : Creating directory: /tmp/cache
Starting migrations
[2023-04-06 23:15:26] peewee_migrate INFO : Starting migrations
There is nothing to migrate
[2023-04-06 23:15:26] peewee_migrate INFO : There is nothing to migrate
[2023-04-06 23:15:26] frigate.app INFO : Output process started: 219
[2023-04-06 23:15:26] detector.cpu1 INFO : Starting detection process: 216
[2023-04-06 23:15:26] frigate.edgetpu WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
[2023-04-06 23:15:26] frigate.app INFO : Camera processor started for baby: 222
[2023-04-06 23:15:26] detector.cpu2 INFO : Starting detection process: 218
[2023-04-06 23:15:26] frigate.edgetpu WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
[2023-04-06 23:15:26] frigate.app INFO : Camera processor started for kitchen: 224
[2023-04-06 23:15:26] ws4py INFO : Using epoll
[2023-04-06 23:15:26] frigate.app INFO : Camera processor started for garage: 227
[2023-04-06 23:15:26] frigate.app INFO : Capture process started for baby: 228
[2023-04-06 23:15:27] frigate.app INFO : Capture process started for kitchen: 230
[2023-04-06 23:15:27] frigate.app INFO : Capture process started for garage: 235
[2023-04-06 23:15:27] ws4py INFO : Using epoll
[2023-04-06 23:16:07] frigate.video ERROR : garage: Unable to read frames from ffmpeg process.
[2023-04-06 23:16:07] frigate.video ERROR : garage: ffmpeg process is not running. exiting capture thread...
[2023-04-06 23:16:07] watchdog.garage ERROR : Ffmpeg process crashed unexpectedly for garage.
Frigate stats
No response
Operating system
HassOS
Install method
HassOS Addon
Coral version
CPU (no coral)
Any other information that may be helpful
No response
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 15 (1 by maintainers)
you must have snapshots enabled to be able to submit to frigate+
I still find this to be very confusing, I have my api key, im just not clear on where to put it. Had to do a bit of trial and error, but got it working. I think the docs need an example (screenshot even) showing where exactly your api key should be placed (for most use-cases, i realize placement may vary). (or maybe even have a spot in the webGUI to paste the key into)
Alot of the GitHub Issues posts i read show users having it in the config file inside of the frigate container (which seems to be working for those users), however the frigate docs state that you should NOT do this ie:
in my case (docker-compose) this is what worked for me:
Thanks for clarifying that. The instructions in Frigate+ where you generate the API key needs to be updated or clarified since it says:
Set your API key as an environment variable named PLUS_API_KEY to enable Frigate+ features inside of Frigate.
On Fri, Apr 7, 2023, 4:20 AM Blake Blackshear @.***> wrote: