[GH-ISSUE #1454] Create a mechanism that allows users of the Android app to recognize whether a displayed UnifiedPush connection is working reliably. #1021

New issue

Closed

opened 2026-05-07 00:29:38 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-07 00:29:38 +02:00

Owner

Originally created by @user4andre on GitHub (Oct 2, 2025).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1454

💡 Idea
Create a way for app users to see whether the established connection is still “healthy.”

Minimum solution until a better one is found:
Show when the last message was received for each entry in the ntfy app (rough display in days or with date is sufficient).

If there is any internal checking mechanism: Show whether connections to the ntfs server and the sending server are working for each established connection.

Unfortunately, I lack the background knowledge to judge whether this is possible or how much effort it would require.

💻 Target components

Android ntfy App if used for UnifiedPush
I cannot judge whether adjustments to the server would be necessary.

Originally created by @user4andre on GitHub (Oct 2, 2025). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1454 :bulb: **Idea** Create a way for app users to see whether the established connection is still “healthy.” Minimum solution until a better one is found: Show when the last message was received for each entry in the ntfy app (rough display in days or with date is sufficient). If there is any internal checking mechanism: Show whether connections to the ntfs server and the sending server are working for each established connection. _Unfortunately, I lack the background knowledge to judge whether this is possible or how much effort it would require._ :computer: **Target components**   Android ntfy App if used for UnifiedPush _I cannot judge whether adjustments to the server would be necessary._

BreizhHardware

2026-05-07 00:29:38 +02:00

closed this issue
added the
enhancement
label

BreizhHardware commented

2026-05-07 00:29:39 +02:00

Author

Owner

@binwiederhier commented on GitHub (Feb 5, 2026):

Done in github.com/binwiederhier/ntfy-android@b20f1322ef -- It'll just show the date like it does for the other subscriptions. That should be sufficient and was quite easy to do.

@binwiederhier commented on GitHub (Feb 5, 2026): Done in https://github.com/binwiederhier/ntfy-android/commit/b20f1322ef57c98efc4b5a7250ec91e0c39a4f01 -- It'll just show the date like it does for the other subscriptions. That should be sufficient and was quite easy to do.