Configurable Timeouts for MQTT #2664

New issue

Open

opened 2026-02-28 03:02:48 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-28 03:02:48 -05:00

Owner

Originally created by @Nurgak on GitHub (Oct 8, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

Simiar to issue 877, but for MQTT: have a configurable timeout for MQTT message monitoring.

Use case

I have a battery powered IOT device that deep-sleeps between updates (closed connection). Currently, updates are configured to be published every 60 seconds. If the check timeout duration is lower than the publish period (which it is right now) UK may miss them. Currently, I see the state of the device toggling between up and pending (with retry set to 2).

If the timeout was configurable it could set it to definitely catch the MQTT message, or definitely fail.

✔️ Solution

Same as #2142 , but for MQTT messages.

❓ Alternatives

No response

📝 Additional Context

As an example, a new field like this:

Originally created by @Nurgak on GitHub (Oct 8, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description Simiar to [issue 877](https://github.com/louislam/uptime-kuma/issues/877), but for MQTT: have a configurable timeout for MQTT message monitoring. # Use case I have a battery powered IOT device that deep-sleeps between updates (closed connection). Currently, updates are configured to be published every 60 seconds. If the check timeout duration is lower than the publish period (which it is right now) UK may miss them. Currently, I see the state of the device toggling between up and pending (with retry set to 2). If the timeout was configurable it could set it to definitely catch the MQTT message, or definitely fail. ### ✔️ Solution Same as #2142 , but for MQTT messages. ### ❓ Alternatives _No response_ ### 📝 Additional Context As an example, a new field like this: ![Screenshot 2023-10-08 at 15 51 46](https://github.com/louislam/uptime-kuma/assets/1785126/d4683e92-0122-4ac1-9fe5-f6829a6ef788)