Internal broker stops recording on HS4-Pi?

[Moskus]

I've made a simple, stupid thing with WLED that I'm using at the office. I've also set up a HS4 system on a Pi at the office, it's in charge of charging our batteries. I installed mscMQTT on it and wanted to controll the WLED thing. It works great!

For a while...

It seems that the internal mscMQTT broker shuts down? The plugin is running, but the WLED sign does not respond to any of the controls in HS4. If I turn it on using the WLED web page, the status is not updated in HS4.

If I restart the plugin, it works again. For a while.

[Moskus]

Hmm... it might be too early to call. I shut down the Pi, and pulled the power. It has been stable for a few hours now. Crossing fingers!

[Michael McSharry]

There was another user with internal broker issue that would eventually fail on heavy MQTT load. It was diagnosed to socket issue waiting for something and just burning CPU cycles. I suggest using Mosquitto which has widespread use. Mosquitto MQTT Broker (steves-internet-guide.com)

[Moskus]

I'm using Mosquitto at home, but I love the simplicity of using the internal broker at work.
I get that it's not meant for heavy use, but a single WLED instance can't be heavy...?

If it doesnt' get better, I'll consider installing mosquitto on the Pi.