search

0x2142 / frigate-notify

Event notifications for a standalone Frigate NVR instance
https://frigate-notify.0x2142.com/
MIT License
92 stars 8 forks source link

Notifications not working. #135

Open Mareckil opened 2 days ago

Mareckil commented 2 days ago

I am trying to setup notifications, unfortunately without success. My frigate is connecting to mqtt broker like that:

 mqtt:
  enabled: true
  host: 192.168.1.160
  port: 1883
  user: mosquitto
  password: passwd
  topic_prefix: frigate
  client_id: frigate
  stats_interval: 60

frigate-notify:

  mqtt:
    enabled: true
    server: 192.168.1.160
    port: 1883
    clientid: frigate_notify
    username: mosquitto
    password: passwd
    topic_prefix: frigate/events

Is it right or not?

0x2142 commented 2 days ago

Hi there, topic_prefix should match on both. So if Frigate is set to frigate, then Frigate-Notify should be the same.

Mareckil commented 2 days ago

Well now something is happening, but still doesn't work. SMTP messages doesn't work, so I've set up Discord and what I can see i n log:

Webhooks posted to forum channels must have a thread_name or thread_id" event_id=1727361371.801558-w0wyti provider=Discord

thats my config for discord:

discord:
    enabled: true
    webhook: https://discord.com/api/webhooks/xxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxx
    template: "Looks like {{ .Camera }} spotted a {{ .Label }}!!"
0x2142 commented 2 days ago

According to Discord's docs, you can append the thread_id to the webhook URL as a query parameter.

So you should be able to update the webhook URL to something like https://discord.com/api/webhooks/aaaaaaaaaaaaaaaa/bbbbbbbbbbbbbb?thread_id=111111