environment_vars always fail config check where they are used (Not in the environment_vars section)
See original GitHub issueDescribe the problem you are having
I don’t want support. This is simply a bug however users aren’t allowed to create bugs for some reason.
It appears as if the variables are just not being passed or parsed inside the config.
Version
Frigate NVR Beta (0.10.0) v 3.2
Frigate config file
environment_vars:
MY_USER: xxx
MY_PASSWORD: xxx
FRIGATE_RTSP_USER: xxx
FRIGATE_RTSP_PASSWORD: xxx
RSTP_IP_1: 'xx:xx:xx:xx'
later…
- path: rtmp://{RSTP_IP_1}/bcs/channel0_main.bcs?channel=0&stream=0&user={FRIGATE_RTSP_USER}&password={FRIGATE_RTSP_PASSWORD}
### Relevant log output
```shell
*************************************************************
*************************************************************
*** Your config file is not valid! ***
*** Please check the docs at ***
*** https://docs.frigate.video/configuration/index ***
*************************************************************
*************************************************************
*** Config Validation Errors ***
*************************************************************
'FRIGATE_RTSP_USER'
*************************************************************
*** End Config Validation Errors ***
*************************************************************
FFprobe output from your camera
does not relate
Frigate stats
does not relate
Operating system
HassOS
Install method
HassOS Addon
Coral version
USB
Network connection
Wired
Camera make and model
does not relate
Any other information that may be helpful
No matter what environment variable is used first, that’s what will fail the config check. If I don’t use any, the above configuration passes. The first attempt to use any variable, the configuration fails check.
Using FRIGATE_ or not does not make a difference, it simply does not accept the environment variable.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Environment variables from launchsettings.json are being ...
json and will fail, because there is no correspondent configuration file: System.IO.FileNotFoundException : The configuration file 'appsettings.
Read more >Don't use environment variables for configuration | Hacker News
A gripe I have with environment variables is when they are used to modify a ... Environment vars should of course not be...
Read more >Environment Variables | Terraform - HashiCorp Developer
Learn to use environment variables to change Terraform's default behavior. Configure log content and output, set variables, and more.
Read more >Problems with Environment Variables
Environment variable is not set. If the error message states that the environment variable is not set, IT MEANS PRECISELY THAT ! The...
Read more >Using AWS Lambda environment variables
Any value you define is considered a literal string and not expanded. Perform the variable evaluation in your function code. Sections. Configuring environment ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@slepiavka For hw acceleration purposes, you can set them in the frigate config file and they will be set before frigate spawns the ffmpeg sub process.
And if environment vars are not to be used with hassOS, then this section needs to be removed
https://docs.frigate.video/configuration/advanced/#environment_vars