Skip to content

Notification configuration notes

dgtlmoon edited this page Nov 4, 2022 · 25 revisions
  • Be sure that your notification body contains atleast something, often {base_url} will be empty, an empty notification body often causes problems with many notification targets
  • Make sure you're not exceeding your target notification service message length when using {current_snapshot}, {diff} or {diff_full} tokens

ARMv7 (RaspberryPi 3 etc)

Discord and Telegram notifications are not super reliable on these devices, this is an issue for apprise not for changedetection.io

Looks like there's an issue with some ARMv7 devices https://github.com/dgtlmoon/changedetection.io/issues/217#issuecomment-1013917577 https://github.com/dgtlmoon/changedetection.io/discussions/366 - this is not fixable by my and has something todo either with the cross platform docker system or apprise

Also https://github.com/dgtlmoon/changedetection.io/issues/407 (rPi "permission denied")

Discord

Email

Example

Your SMTP server is located at mail.mycompany.com and your target email address is steve@gmail.com

You would specify it as mailto://<from-including-smtp-server>?to=email

mailto://john@mail.mycompany.com/?to=steve@gmail.com

For more help - see the Apprise email info https://github.com/caronc/apprise/wiki/Notify_email

Forms/HTTP POST support

JSON

Use the jsons:// notification type and simply set the body in the "Notification body"

GET/PLAIN API

See https://github.com/caronc/apprise/wiki/Notify_Custom_JSON#get-parameter-manipulation for the special syntax