Pushover Notification ignores device list #1534

Closed
opened 2026-02-28 02:24:31 -05:00 by deekerman · 1 comment
Owner

Originally created by @Percy2Live on GitHub (Nov 6, 2022).

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ 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
threema-20221106-124842017

Originally created by @Percy2Live on GitHub (Nov 6, 2022). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/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_ ![threema-20221106-124842017](https://user-images.githubusercontent.com/63621052/200173790-be1e5517-c363-4807-bed9-c5557aae3e8d.jpg)
deekerman 2026-02-28 02:24:31 -05:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@Percy2Live commented on GitHub (Nov 7, 2022):

it is fixed in the current version, somehow I used a quite old version

@Percy2Live commented on GitHub (Nov 7, 2022): it is fixed in the current version, somehow I used a quite old version
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#1534
No description provided.