mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Pushover Notification ignores device list #1534
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#1534
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Percy2Live on GitHub (Nov 6, 2022).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
Description
If pushover notifications are enabled and under "device" a single device is entered the expected behavior is that a push notification is only sent to this device. Unfortunately it seems the "device" field in the pushover configuration view seems to have no influence as notifications are always pushed on all devices
👟 Reproduction steps
Enter a device name in the pushover configuration.
Sent out a test message and see that it is sent to all devices
👀 Expected behavior
When a device name is entered, only the mentioned device should receive a push notification
😓 Actual Behavior
All devices of a user key are getting pushed
🐻 Uptime-Kuma Version
1.9.2
💻 Operating System and Arch
Docker
🌐 Browser
Chrome
🐋 Docker Version
No response
🟩 NodeJS Version
No response
📝 Relevant log output
No response

@Percy2Live commented on GitHub (Nov 7, 2022):
it is fixed in the current version, somehow I used a quite old version