Pushover
Pushover delivers push notifications to iOS, Android, and desktop devices. ChannelWatch delivers Pushover notifications through Apprise, which handles the Pushover API calls internally. You need two values, entered together as user_key@app_token: your User Key and an application API Token.
What you need
Section titled “What you need”- A Pushover account ($4.99 USD once per receiving platform after a 30-day trial)
- Your User Key (identifies your account)
- An API Token (identifies ChannelWatch as the sending application)
Both values are short alphanumeric strings. You’ll copy them from the Pushover dashboard, join them with @, and paste the combined value into ChannelWatch’s web UI.
Step 1: Get your User Key
Section titled “Step 1: Get your User Key”Your User Key is shown on the Pushover dashboard immediately after you log in. It appears in the top-right section of the page under your name. Copy it.
The User Key is tied to your account, not to any specific device. Notifications sent to your User Key reach all devices registered to that account unless you specify a device name.
Step 2: Create an API Token
Section titled “Step 2: Create an API Token”Pushover requires each application to have its own API Token.
- Go to pushover.net/apps/build.
- Fill in the application name (e.g.
ChannelWatch), type, and description. The icon is optional. - Agree to the terms and click Create Application.
- Copy the API Token/Key shown on the confirmation page.
Step 3: Enter credentials in ChannelWatch
Section titled “Step 3: Enter credentials in ChannelWatch”- Open the ChannelWatch web UI at
http://your-server-ip:8501. - Go to Settings > Notifications and stay on the Global scope.
- Turn on Pushover.
- In the Pushover URL field, enter your credentials as
user_key@app_tokenwithout thepover://prefix. - Click Save and wait for ChannelWatch to reload its notification providers.
Environment variable
Section titled “Environment variable”To configure Pushover without the web UI, set this variable in your docker-compose.yml:
environment: CW_APPRISE_PUSHOVER: "<pushover-user-key>@<pushover-app-token>"Replace both placeholder segments with the values from your Pushover dashboard. ChannelWatch prepends the pover:// scheme before passing the value to Apprise.
Step 4: Test delivery
Section titled “Step 4: Test delivery”Open Diagnostics, find Tests > Notifications, then run Test Channel Watching Alert. The notification should arrive on your Pushover-registered devices within a few seconds.
You can also test from the command line:
docker exec -it channelwatch python -m core.main --test-alert ALERT_CHANNEL_WATCHINGWhat Pushover notifications look like
Section titled “What Pushover notifications look like”Pushover renders ChannelWatch alerts as standard push notifications. The alert title becomes the notification title, and the alert body appears as the notification message. An eligible image appears as a thumbnail attachment; ChannelWatch omits hostname, private, and local image URLs under the v1.3.0 attachment safety policy described below.
A Channel Watching alert on Pushover looks like:
- ABCChannel: 7Program: Good Morning AmericaDevice: Living RoomIP: 192.168.1.101Source: HDHRTargeting a specific device
Section titled “Targeting a specific device”By default, Pushover delivers to all devices on your account. To target one device, append its device name after the application token in the Pushover URL field: <pushover-user-key>@<pushover-app-token>/<device-name>. Apprise also accepts multiple device names separated by /. Device names are shown in your Pushover account under Your Devices.
Troubleshooting
Section titled “Troubleshooting”Invalid token or user key
The application token or User Key is incorrect. Double-check both values in the Pushover dashboard. Both values are case-sensitive and contain no spaces.
User key is invalid
The User Key portion of the Pushover URL field contains a typo or extra whitespace. Copy it directly from the Pushover dashboard rather than typing it manually.
Notification delivered but no image
ChannelWatch v1.3.0 passes an image attachment to Apprise only when the source URL uses a literal, globally routable IP address and passes ChannelWatch’s URL safety checks. Hostname, private, and local image URLs are omitted, while the notification text still sends. When an image is accepted, Apprise fetches it and uploads the attachment bytes to Pushover; Pushover does not fetch the original image URL. Pushover currently limits an attachment to 5 MiB. See the Pushover attachment rules.
Pushover monthly quota
An individual Pushover account can send 10,000 messages per month for free. All applications registered to that account share the quota; it is not a separate 10,000-message allowance for each API token. Pushover rejects new messages with HTTP 429 after the account reaches its limit and resets the quota on the first day of the month at midnight Central Time. The application page shows current usage. See Pushover API limitations.
No notifications after saving credentials
Confirm that at least one alert type is enabled in Settings > Alerts. Pushover credentials can be valid but produce no notifications if all alert types are disabled.
Related pages
Section titled “Related pages”- Provider Matrix - compare all notification providers at a glance
- Custom (Apprise) - use any other Apprise-supported service
- Discord - webhook-based notifications for Discord channels
- Notification Examples - full gallery of alert formats
- Diagnostics - test and verify your notification setup