[Bug]: No possible to configure notification #21084
Replies: 4 comments
-
|
Based on the error in your logs, Frigate is crashing during notification initialization with a The crash occurs at this line in the stack trace: This appears to be a compatibility issue with the cryptography library used by the py-vapid package in Frigate 0.16.2. To resolve this issue:
For notifications to work properly in Frigate, you need(1):
The configuration format you should use once this is resolved is(1): notifications:
enabled: True
email: "johndoe@gmail.com"
cooldown: 10You can also configure notifications per camera(2): cameras:
doorbell:
notifications:
enabled: True
cooldown: 30Until this bug is fixed in a future Frigate release, notifications will not be functional in version 0.16.2. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
@inkeep can you support? notifications.pem has been never created... maybe sometihing wrong? |
Beta Was this translation helpful? Give feedback.
-
|
You're correct that From your logs, the crash happens at this exact point(2): This is a known bug in Frigate 0.16.2 related to the py-vapid cryptography library(1). The error occurs in the VAPID key generation code when Frigate tries to create the Workarounds reported by the community:
The manual key generation approach should allow Frigate to start with notifications enabled, since the crash only occurs when the file needs to be created for the first time(1). ** 📚 Sources:
Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
Closing as a duplicate of #20548 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you are having
When I setup notification if I restart frigate it doesn't start until notification setup will be deleted
Steps to reproduce
I installed frigate with docker composed on my synology.
http://localip:port1 --> works
https://localip:port5 --> the connection is not secure but it works
setup a reverse proxy on my synology from localip port6 to https port 5
https://myurl:port6 --> works
From here I setup notification, selecting the camera and setting up the emailaddress.
restart frigate and now the frigate is not able to start anymore (I need to remove all notification lines from config.yaml)
Version
version: 0.16-0
In which browser(s) are you experiencing the issue with?
Google Chrom/Edge
Frigate config file
automatically set from UIdocker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
Operating system
Other
Install method
Docker Compose
Network connection
Wired
Camera make and model
MISECU
Screenshots of the Frigate UI's System metrics pages
??
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions