mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #32] Let user choose delivery mode: instant delivery, 1min, 5min, 15min, ... #30
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#30
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 @binwiederhier on GitHub (Dec 4, 2021).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/32
Make delivery mode configurable in the app:
@m0Re-p commented on GitHub (Dec 15, 2021):
Im waiting on this feature :)
@binwiederhier commented on GitHub (Dec 16, 2021):
@m0Re-p Just curious, are you waiting for this because you don't like the foreground service? Or are you having battery concerns? If so, is non-instant delivery not enough, or are you on the F-Droid flavor?
@m0Re-p commented on GitHub (Dec 16, 2021):
@binwiederhier I prefer F-droid options
Im using tasker with some plugins to monitoring temperature on my central heating stove. Tasker make a photo on every 2 minutes, use ocr to read temperature, save the results in CSV file. If temperature are greater then XX value I receive notifications. Using ntfy I can control my phone by any other devices
@binwiederhier commented on GitHub (Dec 16, 2021):
That's wild. Very cool. 😎
So you'd only want to check every two minutes instead of instant? Why? Battery? I'd assume your phone to monitor the stove is plugged in, right?
@m0Re-p commented on GitHub (Dec 16, 2021):
@binwiederhier thank you :)
Yes, example check every two minutes (but the better solution is situation when I can put any value what I want).
You are right, my phone to monitor the stove is plugged in but In my head I have a lot more ideas to use ntfy where this functionality is really necessary
Anyway this tool are really good. I launched my instance on RPI and works good too
@binwiederhier commented on GitHub (Feb 7, 2022):
I am inclined to close this, since the main reason for it was saving battery. Since that's no longer an issue, and the foreground service can be easily hidden, I'm going to close this.
Please re-open if this is desperately desired.
@Fabian-G commented on GitHub (May 21, 2023):
For what it's worth: I'd love to see this feature. Although the battery usage of ntfy is somewhat okay-ish, it is (at least on my device) not insignificant. On the other hand I usually don't really care if a notification arrives immediately or at some point within an hour, because my phone is in silent mode 24/7 anyway.
Currently ntfy sits at 4-5% per 3 hours in my battery stats. With a WorkManager based approach (or whatever you had in mind) I would expect ntfy to hardly show up in the stats at all. Therefore, I think it would be great if the user had control over this.
Edit: Nevermind. When I use only WiFi instead of Mobile Data ntfy doesn't even show up in the battery stats. Also the battery usage of other Apps on my phone that use websockets drop significantly. Which makes me believe there is something weird on my end.
@McOrvas commented on GitHub (Jun 23, 2025):
I use Ntfy with a self hosted server at home. My Android phone (Pixel 6, Android 16) is connected with WireGuard to my home network when I'm on the go. In my home Wifi a have absolutely no problems with the battery usage and even in other Wifis together with an active WireGuard connection it is not a problem. But with mobile data and WireGuard Ntfy really drains the battery in a short time. For my personal purposes it would be perfect to have the possibility to select a poll interval instead of the persistent connection.