# MQTT Client Rate Limiter issue from update to Homey Pro early 2026
**URL:** https://community.homey.app/t/mqtt-client-rate-limiter-issue-from-update-to-homey-pro-early-2026/153157
**Category:** Apps
**Created:** [March 30, 2026, 7:02pm UTC](https://community.homey.app/t/mqtt-client-rate-limiter-issue-from-update-to-homey-pro-early-2026/153157 "2026-03-30T19:02:40Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Hunters](https://community.homey.app/u/Hunters)
#### Post date: [March 30, 2026, 7:02pm UTC](https://community.homey.app/t/mqtt-client-rate-limiter-issue-from-update-to-homey-pro-early-2026/153157/1 "2026-03-30T19:02:41Z")
Hello,
I’m using MQTT Client and Broker on Homey from many years (before with Homey Pro early 2019).
Now I upgraded to a new Homey Pro early 2026 and my MQTT devices are not working anymore fine.
I have a self made circuit that publish every 5 seconds the speed of 4 fans and 1 temperature value. I have one flow of MQTT Client trigger for each of this topics:
fan/getSpeedO
fan/getSpeed1
fan/getSpeed2
fan/getSpeed3
fan/getTemperature
Every flow set the values it collect on 1 Virtual Device for each topic executing an Homey Script.
After the upgrade to new homey I’m getting issues having the values in realtime. Even when I stop the fans I see that the system is still giving me fan speed values while them are at zero. So checking the logs seems that the client is still processing a queue created on each topic. The logic is that it update the values during the time it is exhausting the queue so it is running very slow following the values in time.
You can see the logs in the attachment.
Do you have any ideas? The flows are very simple and 5 numeric values every 5 seconds do not justify such behavior I think.
Thank you in advance.
Regards
Marcello
---
### Author:  [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)
#### Post date: [March 30, 2026, 11:53pm UTC](https://community.homey.app/t/mqtt-client-rate-limiter-issue-from-update-to-homey-pro-early-2026/153157/2 "2026-03-30T23:53:35Z")
Hi Marcello,
When you’ve ruled out possible network issues, you can compare results with the alternative (sort-of-all-in-one) MQTT app:
> **[MQTT Server | Homey](https://homey.app/en-nl/app/net.weejewel.mqttserver/MQTT-Server/)**
>
> Publish Homey Pro's devices as an MQTT server.
You can install it next to the other MQTT apps, but make sure to turn off the MQTT Broker app when running this MQTT Server app (and vice versa); you can use the same credentials as used with MQTT Broker.
Because I’ve no issues with MQTT Client app since I moved to Pro 2026 medio last December, I’m curious if these delays don’t occur using this MQTT Server app.
---
### Author:  [@Hunters](https://community.homey.app/u/Hunters)
#### Post date: [March 31, 2026, 4:54am UTC](https://community.homey.app/t/mqtt-client-rate-limiter-issue-from-update-to-homey-pro-early-2026/153157/3 "2026-03-31T04:54:35Z")
Hello Peter,
thank you for the answer. Will try for sure but I’m sure that is not related to a network issue. Homey is connected with LAN cable and the Broker is regurarly receiving the update from my custom equipment. The issue seems to be internal on Homey itself from Client to Broker and specifically the rate limit is occurring inside the Client managing packets read from the Broker and flows execution.
As you can see from this other attachment the Broker is regurarly receiving packets. You can see the 4 fans speed RMPs and the temperature every 5 seconds.
Thank you
Regards
Marcello
---
### Author:  [@Hunters](https://community.homey.app/u/Hunters)
#### Post date: [April 1, 2026, 4:28am UTC](https://community.homey.app/t/mqtt-client-rate-limiter-issue-from-update-to-homey-pro-early-2026/153157/4 "2026-04-01T04:28:26Z")
Hello Peter,
unfortunately I cannot test the MQTT Server as I was thinking before.
My custom device has only the anonymous connecting method to MQTT Broker at the moment and the MQTT Server doesn’t work without a user credential so I cannot test it now.
Will try in the future but I have before to modify the software in the flash (it is an ESP32 self made 6 years ago) and have to get the time to organize myself to do it.
Thank you
Regards