Hello, I observe quite strange behavior with MQTT Client. I have MQTT Hub, where all devices are published to topic homie/homey-5dd…1/# I also have other devices which publish messages like openHab/# and UPS/# I have two flows which subscribe to topic: UPS/status and openHab/Okno3/BlindsControl. …

I’ve been testing it during weekend and so far this build looks really stable. So far no random disable of flows. @HarriedeGroot , you did fantastic job. Thanks!

YW, got some good looking result here too: [image] MQTT Client Topic-Trigger? Apps (DE) I have 15 topic trigger active now. System load seems to keep stable. In the past, the 15 trigger got the system load up to 1500%. So many thanks for this improvement. The FlowTrigger…

works like a charm, updated without any problem and kept running since. No problems with broker and hub, all flows and nodered are still alive.

I am seeing promising results too… will post if I find anything ‘strange’ (Ignoring some v6 beta issues)

Great work Harrie… So far so good. The disabling of flows error (flows which used MQTT client) doesn’t occur anymore. These flows use # wildcards to listen for certain text. For me the disabling flows error would previously occur when ever I tried scanning for new Tasmota devices in the Tasmota Ap…

One week past. I’m curious if anyone had any issues with the beta/test version of the MQTT Client app? @scanno did you get any reports? How many users installed the test version? And the connection dropouts between apps? Are regular app restarts still needed? And Homey responsiveness? Became wors…

Perhaps I am not the most heavy user (though I am currently setting up a HA dashboard, so…), but have not had any issue at all. Currently MQTT Client is using 17.8MB (and Hub 25.6MB) memory. Homey seems very responsive too. (Broker in Docker on local Synology DS218+)

@HarriedeGroot there are 52 users using the test version. I have not received any bug reports and the crash count is 0.

For me all is fine with the test version. Topic subscription is working. Also after Homey restart (subscription, automatic Hub-broadcast). Homey systemload is stable and independent of number of topic subscriptions. Memory: Hub=21,6MB, Client=14,5MB

Thanks for the info. Looking all good to me; actually much better then expected. @scanno Are you comfortable pushing this to live? I’ve got some updates for the Hub on test already. These need the new unsubscribe API of the client. So waiting for the client before it can be released.

Strange MQTT Client behavior

Apps

HarriedeGroot June 8, 2021, 10:39am 84

@Russell_S A general example can be found here:

Topic		Replies	Views
MQTT Client Topic-Trigger? Apps (DE)	21	1516	April 18, 2021
[APP][Pro] MQTT Hub - Community version Apps app , mqtt , homey-pro	290	8214	August 1, 2026
MQTT Hub/Gateway Apps	1291	66714	August 1, 2024
[APP][Pro] MQTT Server - Publish Homey Pro's devices as an MQTT server Apps app , official , mqtt , homey-pro	22	1012	July 17, 2026
[App][Pro] MQTT Broker for Homey Apps app , tools	150	14546	July 16, 2025

Strange MQTT Client behavior

Related topics