[GH-ISSUE #1713] [Feature Request] Android client - Alternative connection address based on "home" wifi #1191

New issue

Open

opened 2026-05-07 00:30:57 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 00:30:57 +02:00

Owner

Originally created by @matterbyte on GitHub (Apr 22, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1713

💡 Idea

My idea is for the Android ntfy app to allow for an alternative connection address based on "home Wi-Fi" (similar to the home assistant app).

This would allow for direct connection to a local ntfy instance via the direct IP, based on one or more whitelisted wifi networks in range

The use case for this is that notifications would work locally even when the ntfy container's connection to the Internet is down (which could be the ISP, reverse proxy configuration, or otherwise). This is particularly useful if the user is also running something that notifies them to the issue specifics, such as uptime kuma or another similar monitoring tool.

💻 Target components
Android App

Originally created by @matterbyte on GitHub (Apr 22, 2026). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1713 :bulb: **Idea** My idea is for the Android ntfy app to allow for an alternative connection address based on "home Wi-Fi" (similar to the home assistant app). This would allow for direct connection to a local ntfy instance via the direct IP, based on one or more whitelisted wifi networks in range The use case for this is that notifications would work locally even when the ntfy container's connection to the Internet is down (which could be the ISP, reverse proxy configuration, or otherwise). This is particularly useful if the user is also running something that notifies them to the issue specifics, such as uptime kuma or another similar monitoring tool. :computer: **Target components** Android App