Manchmal braucht es nur einen einzigen Post in der Timeline, und man landet in einem Kaninchenbau. So geschehen heute: Ein Mastodon-Post von @Doppellhelix vom 2. März 2026 hat mich auf das Projekt evcc Crowdscience aufmerksam gemacht. Ein Forschungsprojekt der HTW Berlin, bei dem evcc-Nutzer:innen ihre Ladedaten anonym für die Energiewende-Forschung spenden können. Klingt gut, dachte […]
https://hausbau.blog.dpesch.de/2026/03/07/evcc-crowdscience-timberwolf-server-docker/I made a helm chart for running Eclipse Mosquitto in a k8s cluster for my Home Assistant and wrote a blog post showing how to configure and install it.
https://unixorn.github.io/post/homelab/k8s/06-install-mqtt/
#k8s #homelab #homeassistant #mqtt #mosquitto #helm @homeassistant @homelab #selfhosting #iot
Now that the cluster is up and has Argo CD controlling application deployment, I’m starting to move my homelab services out of docker-compose stacks and into my k8s cluster. I run MQTT (Eclipse Mosquitto in my case) as a message bus between zigbee2mqtt and zwave-js-ui and Home Assistant, so it’s the first service I’m moving into the k8s cluster.
Short blog post on a few necessary adaptions when updating to Mosquitto 2.1: https://blog.mei-home.net/posts/mosquitto-2-1-update/
(Please note the length. Project "Posts, not tomes" yet lives. 🎉 )
I'm impressed by the upcoming mosquitto v2.1 server, currently in RC2. As a server, it blows the others I've tested out of the water.
The usual benchmark analysis and links to the raw data at https://github.com/gonzalop/mq/blob/main/docs/PERFORMANCE_ANALYSIS.md
Now that I'm done running the integration tests with mosquitto (pass), mochi-server(pass, server needs a patch) and VerneMQ (reported issues with the server in a previous post), it's time for a comparison of the throughput tests of the three servers:
https://github.com/gonzalop/mq/blob/main/docs/PERFORMANCE_ANALYSIS.md
mq🚀
First time setting up a @homeassistant instance. I'm trying to integrate an airquality sensor with it. HASS runs in a (podman) container (network host mode). #mosquitto MQTT is installed natively (port 8883 with SSL). HASS is connected to MQTT server (I can subscribe and publish messages). The sensor device is also connected to MQTT (mosquitto says "New client connected from ...").
What would be the next step? I expected the sensor to be automatically added to HASS.
Learn how to set up a secure Mosquitto MQTT broker on Linux (from installation to TLS encryption) in my latest video!
👇
https://shawnhymel.com/3085/how-to-use-the-mosquitto-mqtt-broker-with-ssl-tls/?utm_source=mastodon&utm_medium=social&utm_campaign=esp32_iot_course_evergreen