MQTT “Heartbeat” #1609

New issue

Closed

opened 2026-02-28 02:27:06 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 02:27:06 -05:00

Owner

Originally created by @mtjoernelund on GitHub (Dec 9, 2022).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

📝 Describe your problem

For the mqtt monitor, right now I use NodeRed to send a “heartbeat” message to the topic I subscribe to with Uptime-Kuma and it works well. But if my NodeRed server should go down, it would show mqtt as down as well. Is there a better way of sending the heartbeat mqtt message?

🐻 Uptime-Kuma Version

1.18.5

💻 Operating System and Arch

Debian

🌐 Browser

Safari / Chrome

🐋 Docker Version

No response

🟩 NodeJS Version

No response

Originally created by @mtjoernelund on GitHub (Dec 9, 2022). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem For the mqtt monitor, right now I use NodeRed to send a “heartbeat” message to the topic I subscribe to with Uptime-Kuma and it works well. But if my NodeRed server should go down, it would show mqtt as down as well. Is there a better way of sending the heartbeat mqtt message? ### 🐻 Uptime-Kuma Version 1.18.5 ### 💻 Operating System and Arch Debian ### 🌐 Browser Safari / Chrome ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version _No response_

deekerman

2026-02-28 02:27:06 -05:00

closed this issue
added the
Stale

help
labels

deekerman commented

2026-02-28 02:27:10 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 9, 2023):

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

@github-actions[bot] commented on GitHub (Mar 9, 2023): We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

deekerman commented

2026-02-28 02:27:11 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 11, 2023):

This issue was closed because it has been stalled for 2 days with no activity.

@github-actions[bot] commented on GitHub (Mar 11, 2023): This issue was closed because it has been stalled for 2 days with no activity.

deekerman referenced this issue

2026-02-28 02:47:32 -05:00

Configure status page to display based on tags #2233