-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
yaml: line 23: did not find expected key #106
Comments
This does appear to be a bug. template: can't appear to start with { otherwise it errors out and the error message was pretty useless because the problem wasn't line 23, it was serveral lines down. |
Dear @zombiehoffa, could you try to define the pattern in the following notation? alerts:
...
ntfy:
...
template: |
{{ .Camera }} spotted {{ .Label }} |
Just released v0.3.3, and I included a note in the docs to mention this. Using the multi-line format above works, or alternatively just quote the single-line template and that should be fine too |
Describe the bug
I followed the instructions for the config but no matter what I try I can't get it to load the config file with my ntfy server enabled. I kind of expect the problem to be me doing something boneheaded but I can't figure it out so I am posting here.
Expected behavior
yaml doesn't fail to load config on a did not find expected key error and the software starts up and runs
To Reproduce
start up frigate-notify with my config.yml
Versions:
Frigate-Notify Config:
This works if I comment out ntfy: and everything below.
Frigate-Notify Logs:
Additional context
If I disable ntfy: and below it works. line 20 is ntfy: according to nano. I really do think I am just doing something wrong here but I've tried a whole bunch of stuff and I can't figure out what I am doing wrong so I am posting as a bug in case it is a bug with the ntfy code.
Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: