uptime-kuma
uptime-kuma copied to clipboard
MQTT Monitor Type - Timeout
⚠️ 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
📝 Describe your problem
I am unable to monitor the status of an MQTT server. I specified the URL, Port, Username and Password but it keeps returning 'MQTT': Failing: Timeout | Interval: 60 seconds | Type: mqtt
I don't know how to diagnose this problem. I searched existing issues and found nothing.
🐻 Uptime-Kuma Version
1.15.1
💻 Operating System and Arch
Debian Bullseye on Raspberry Pi 4 ARM64
🌐 Browser
Google Chrome 100
🐋 Docker Version
20.10.16
🟩 NodeJS Version
No response
I experience a similar issue. I get frequent timeout warnings - but have no reason to believe my broker has issues. The systems behaves normal and all mqtt clients get the data just fine.
I think it is logged in to your mqtt broker successfully, but Uptime Kuma don't receive topic response within 40 seconds.
I had the same issue, and I just found out that the topic part is case-sensitive. Perhaps this is the issue for yourself as well. Unfortunately, the “error” message from Kuma was not helpful at all. “Timeout” keeps me questioning if the connection works at all.
@louislam I don't think that's the case here. I tried subscribing and kept sending a message to the topic to keep it updated and still got the timeout error.
@buliwyf42 the topic case matches exactly what's on the broker. I don't think that's the case here.
- I increased the test interval to 120s and I don't get any more errors. Before I got either a message with the topic value - or with the timeout error. Now I get the availability but no ping value and therefore the graph is empty.
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 7 days.
Maybe the issue is not really an issue: If your topic is not updated within the timeframe of the kuma update interval - the test will fail. Yet the mqtt broker might be happy and alive - so I am not sure what to suggest.