# NTFY app for Homey: Send notifications and images to your NTFY server **URL:** \ **Category:** Developers\ **Created:** [February 11, 2024, 7:45am UTC](https://community.homey.app/t/ntfy-app-for-homey-send-notifications-and-images-to-your-ntfy-server/103727 "2024-02-11T07:45:22Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Martin\_H](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_h/32/7964_2.png) [@Martin\_H](https://community.homey.app/u/Martin_H)\ **Post date:** [February 11, 2024, 7:45am UTC](https://community.homey.app/t/ntfy-app-for-homey-send-notifications-and-images-to-your-ntfy-server/103727/1 "2024-02-11T07:45:22Z")
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 ---
**Author:** ![Andy\_Henderson](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andy_henderson/32/80642_2.png) [@Andy\_Henderson](https://community.homey.app/u/Andy_Henderson)\ **Post date:** [February 11, 2024, 1:45pm UTC](https://community.homey.app/t/ntfy-app-for-homey-send-notifications-and-images-to-your-ntfy-server/103727/2 "2024-02-11T13:45:31Z")
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](https://docs.ntfy.sh/publish/#__tabbed_2_4)) 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 ---
**Author:** ![Martin\_H](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_h/32/7964_2.png) [@Martin\_H](https://community.homey.app/u/Martin_H)\ **Post date:** [February 11, 2024, 3:53pm UTC](https://community.homey.app/t/ntfy-app-for-homey-send-notifications-and-images-to-your-ntfy-server/103727/3 "2024-02-11T15:53:43Z")
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. ---
**Author:** ![ketra90](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ketra90/32/9687_2.png) [@ketra90](https://community.homey.app/u/ketra90)\ **Post date:** [October 2, 2025, 7:48am UTC](https://community.homey.app/t/ntfy-app-for-homey-send-notifications-and-images-to-your-ntfy-server/103727/4 "2025-10-02T07:48:30Z")
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](https://homey.app/en-nl/app/eu.ketra.ntfy/Ntfy/) ---
**Author:** ![Martin\_H](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_h/32/7964_2.png) [@Martin\_H](https://community.homey.app/u/Martin_H)\ **Post date:** [December 4, 2025, 8:17pm UTC](https://community.homey.app/t/ntfy-app-for-homey-send-notifications-and-images-to-your-ntfy-server/103727/5 "2025-12-04T20:17:08Z")
Never to late 🙂 i will test thanks ---
**Author:** ![Martin\_H](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_h/32/7964_2.png) [@Martin\_H](https://community.homey.app/u/Martin_H)\ **Post date:** [December 5, 2025, 8:20am UTC](https://community.homey.app/t/ntfy-app-for-homey-send-notifications-and-images-to-your-ntfy-server/103727/6 "2025-12-05T08:20:28Z")
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! ---
**Author:** ![Zoltan\_Vaczi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/zoltan_vaczi/32/86516_2.png) [@Zoltan\_Vaczi](https://community.homey.app/u/Zoltan_Vaczi)\ **Post date:** [August 9, 2026, 11:27am UTC](https://community.homey.app/t/ntfy-app-for-homey-send-notifications-and-images-to-your-ntfy-server/103727/7 "2026-08-09T11:27:33Z")
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