This repository was archived by the owner on Aug 22, 2021. It is now read-only.
Repository navigation
Notifiers
Mathieu Carrié edited this page Sep 21, 2019
·
1 revision
Flemzerd sends notifications for events occuring (download start/success/failure, new episodes/movies) using Notifiers. Each Notifier represents a method of notification (mail, sms, Telegram, ...).
Notifiers are optionnal in flemzerd. If no Notifiers are defined, notifications won't be sent. When multiple Notifiers are defined, each notification will be sent using all defined notifiers.
Flemzerd automatically uses the Event log notifier to make notifications display in the Web interface. This Notifier cannot be disabled.
Sends notifications through Pushbullet.
- Enable
pushbulletNotifier in configuration file
[notifiers]
[notifiers.pushbullet]
accesstoken = "accesstoken"
- The Pushbullet access token can be foudn on your Pushbullet account settings
Sends notifications to the desktop. The way this Notifier sends notifications depends on the OS:
- Linux:
notify-sendfo Gnome andkdialogfor KDE - Mac OS X:
terminal-notifierif installed orosascriptotherwise - Windows:
growlnotify
- Enable
desktopNotifier in configuration file
[notifiers]
desktop = []
Sends notifications to a Kodi instance.
- Enable
kodiNotifier in configuration file
[notifiers]
kodi = []
- Define
kodiMediacenter in configuration file. ThekodiNotifier uses the configuration from the Kodi mediacenter
[mediacenters]
[mediacenters.kodi]
address = "address"
port = 9090
Sends notifications via Telegram.
- Enable
telegramNotifier in configuration file
[notifiers]
telegram = []
- Define Telegram bot token
Flemzerd needs the bot token to be able to send notifications. This token is passed to flemzerd by defining the
FLZ_TELEGRAM_BOT_TOKENenvironment variable. When defined during flemzerd compilation, this variable is compiled into the binary. In packages found on GitHub, this key is precompiled into the binary. The Telegram notifier then needs to be enabled in the Settings page of the Web UI.