Homey Community Forum

Strange MQTT Client behavior

As soon as I can find some spare time, I will have a look at the pull request. Work and thesis consume all my time right now.

Thanks for the effort.

1 Like

@scanno Could it be an option to push this to the test channel?

That’s one heck of a lot of work Harrie. - well done.

If you haven’t the time to look at it Menno could we have it as a test version ???

Its in test now @HarriedeGroot

1 Like

I will leave the MQTT client in test for a while. Please let me know if all works out. If there are no (major) issues, I will submit it for certification.

Sorry for the lack of time, but I really have to focus on my research and thesis.

3 Likes

Thanks! Let’s monitor for a while indeed. No hurries. Study is much more important.

For completeness, the updated test version can be found here:

Please report your findings :slight_smile:

Details of the changes:

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!

1 Like

YW, got some good looking result here too:

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 App.

Doesn’t happen anymore :slightly_smiling_face: … Thanks mate …:smiley:

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 worse due the retained messages coming in now or is improved by the additional checks for incoming messages?

CPU/Memory usage? Memory leaks introduced?

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.

1 Like

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.

Your build #6 for app nl.scanno.mqtt is now waiting for certification.

Version is live I see, thanks @scanno.

It’s still working well for me. My devices use it on a daily basis.