[GH-ISSUE #8] Look at mqtt #7

Closed
opened 2026-05-07 00:18:21 +02:00 by BreizhHardware · 2 comments

Originally created by @binwiederhier on GitHub (Nov 20, 2021).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/8

Originally created by @binwiederhier on GitHub (Nov 20, 2021). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/8
BreizhHardware 2026-05-07 00:18:21 +02:00
Author
Owner

@binwiederhier commented on GitHub (Nov 26, 2021):

I looked at mqtt and various Go libraries. It looks like a neat technology and specs. Long story short: I think I'm gonna pass and not implement it for ntfy.

Reasons: It seems quite large for ntfy and for its use case. Lots to configure, lots to confuse people.

I could see implementing a MQTT client on the server side that we'd also publish to, kinda like firebase is implemented, basically just forward message to another pubsub system. But I'll only implement that of somebody really needs it.

Libraries:

<!-- gh-comment-id:979959922 --> @binwiederhier commented on GitHub (Nov 26, 2021): I looked at mqtt and various Go libraries. It looks like a neat technology and specs. Long story short: I think I'm gonna pass and not implement it for ntfy. Reasons: It seems quite large for ntfy and for its use case. Lots to configure, lots to confuse people. I could see implementing a MQTT client on the server side that we'd also publish to, kinda like firebase is implemented, basically just forward message to another pubsub system. But I'll only implement that of somebody really needs it. Libraries: - Just a client: https://github.com/eclipse/paho.mqtt.golang - As far as I can see not embeddable: https://github.com/fhmq/hmq - broker lib: https://github.com/DrmagicE/gmqtt
Author
Owner

@jangrewe commented on GitHub (Dec 12, 2023):

This would be awesome as lots of home automation projects use MQTT as their messaging bus! A typical use case would be openHAB just publishing its notifications to an MQTT topic as usual, and ntfy subscribing to that (user configurable) topic to ... well, notify. ;-)
Maybe even allow subscribing to multiple separate topics, to categorize where the notifications are coming from. My Frigate server would be a second candidate for a topic.

<!-- gh-comment-id:1851842758 --> @jangrewe commented on GitHub (Dec 12, 2023): This would be awesome as lots of home automation projects use MQTT as their messaging bus! A typical use case would be openHAB just publishing its notifications to an MQTT topic as usual, and ntfy subscribing to that (user configurable) topic to ... well, notify. ;-) Maybe even allow subscribing to multiple separate topics, to categorize where the notifications are coming from. My Frigate server would be a second candidate for a topic.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#7
No description provided.