NTFY app for Homey: Send notifications and images to your NTFY server

Developers
1

Hello everyone,

I would like to present an idea for a new Homey app that sends notifications and images to an NTFY server (ntfy.sh). The app should have the following features:

Send notifications and images to NTFY server: The app should be able to send both text notifications and images to an NTFY server.
Choose between own server or official server: The user should be able to choose to use either their own NTFY server or the official NTFY server.
Settings: The app should have settings where the user can configure the server address, API key, and other relevant parameters.
I have tried to create my own app, but I have not been able to get it to work completely correctly. I only get “triggered” notifications in my NTFY server. Therefore, I wonder if anyone else has made or started on such an app?

It would be great if we could collaborate to create a complete app that all Homey users can use.

Here are some questions that I would like to discuss:

What features are most important for an NTFY app?
How can we make the app easy to use and configure?
Are there any specific challenges we need to consider?
I look forward to hearing your thoughts and ideas!

Best regards,

Martin

2

I’ve not used NTFY but now you’ve alerted me to it, I might do in future.

I don’t think you need an app. Instead you can create an advanced flow that starts with a text tag. The flow can then use the Logic card: Make a … request to … with headers … and body …

Any flow can then invoke your flow with the message you want to send.

Sorry, re-read and spotted your requirement for images. Can’t see how NTFY expects image data to be provided, but it says it can.

[another edit] NTFY expects image urls in headers (Sending messages - ntfy) so you could use an advanced flow to either pick up message and image address from variables, or provide them in a text tag with a splitter character (e.g, |).

Andy

3

One of the best things about ntfy is that you can run a local server with Docker. I’ve been running it with logic and sending images with the string: http://********:82/Homey?attach=http://*******:*****@172.16../web/auto.jpg, but I thought it would be easier with a dedicated app where you can fetch messages and images, and also set up different topics/servers to use multiple receivers.

4

Sorry, maybe is this reaction too late, but i created the NTFY app for homey, so if you want to use it.
Ntfy App for Homey | Homey

5

Never to late :slight_smile: i will test thanks

6

Hi and thank you again for this app!

After an initial test, I have a couple of suggestions and bugs I’d like to report:

  1. There’s no field for the server port. Many people don’t run on the default port, so a separate port field next to Server IP is needed.

  2. Fields marked as Optional still have to be filled in to proceed. I get the error message “All fields are required” even when leaving the optional fields blank. Temporary workaround I found: If I enter a single space in the Username and Password fields, the app accepts it and everything works perfectly afterward.

Thanks in advance for looking into this – the app is otherwise really great!

7

Hi,

I’m reporting a bug with the NTFY Push Notifications app for Homey Pro (Early 2023).

Environment:

  • Homey Pro (Early 2023), firmware up to date
  • NTFY Push Notifications app (latest version from Homey App Store)
  • Self-hosted ntfy server (v2.27.0) behind HTTPS reverse proxy
  • Server with basic auth enabled

Setup:
I created two separate devices in the app, each configured with a different topic on the same server:

  • Device 1: server ntfy.bigkun.cc, topic homey-bp-riasztas (for critical alerts)
  • Device 2: server ntfy.bigkun.cc, topic homey-bp-info (for informational messages)

Both devices have the same username/password (same ntfy user account), only the topic differs.

Expected behavior:
Each device should publish to its own configured topic. Sending a test notification from Device 1 should go to homey-bp-riasztas, and from Device 2 to homey-bp-info.

Actual behavior:
Both devices publish to the SAME topic — whichever topic was configured last. For example:

  1. Created Device 1 with topic homey-bp-riasztas
  2. Created Device 2 with topic homey-bp-info
  3. Sent test message from Device 1 → arrived on homey-bp-info (wrong!)
  4. Sent test message from Device 2 → arrived on homey-bp-info (correct)

I verified this by:

  • Deleting both devices and recreating in reverse order (info first, riasztas second) → both then published to homey-bp-riasztas
  • Double-checking each device’s settings page — the topics ARE correctly shown per device
  • Monitoring the ntfy server to confirm which topic actually receives the message

This suggests the app stores the server/topic configuration globally rather than per-device, and the last saved configuration overwrites all previous ones.

Impact:
This makes it impossible to use separate topics for different alert priorities (e.g. critical vs informational), which is a core use case for the app’s advertised “multiple servers/topics via additional devices” feature.

Workaround:
I’m currently using HomeyScript with direct HTTP POST calls to ntfy, which works correctly with separate topics. But this defeats the purpose of having a dedicated app with Flow action cards.

Would appreciate a fix. Happy to help test.

Thank you