[Bug]: Modifying motion tuning from the UI creates a config that violates the schema #15478
Replies: 1 comment
-
Thanks, this has already been fixed |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Checklist
Describe the problem you are having
When modifying the motion tuning settings from the UI, when you save them, the improve_contrast setting is saved as the string value
'true'
rather than the boolean valuetrue
. Even if improve_contrast is already set to the correct (according to the yaml schema) boolean value, as soon as you click either Reset or Save in the Motion Tuning UI, the value will be changed to a string, so even if I fix it, the next time I adjust the motion tuning settings, the schema violation notification will come back in the configuration UI.Steps to reproduce
'true'
rather thantrue
Version
0.14.1-f4f3cfa
In which browser(s) are you experiencing the issue with?
All
Frigate config file
docker-compose file or Docker CLI command
N/A for this issue
Relevant Frigate log output
None, this is just a nuisance in the configuration editor
Relevant go2rtc log output
None, this is just a nuisance in the configuration editor
Operating system
Proxmox
Install method
Docker Compose
Network connection
Wired
Camera make and model
unifi protect, various models
Screenshots of the Frigate UI's System metrics pages
N/A for this issue
Any other information that may be helpful
This isn't an error as far as I can tell. It does seem like Frigate happily interprets the string 'true' as a truthy boolean value. It's mostly just annoying to see the yellow squiggly line under the value. Also, you would think that frigate itself should generate 100% schema-valid configurations.
Beta Was this translation helpful? Give feedback.
All reactions