Holy hell, I LITERALLY set up MQTT ~3 days ago. It was a pain as I mostly have experience with Zigbee devices via ZHA in Home Assistant, so I had to set up Mosquitto for the first time for some new devices running Tasmota. Spent way too long on the project (mostly because I didn't realize that my router was blocking all traffic between VLANs, so the messages between the IOT devices and my MQTT VM only worked one way). Should've just waited for your video to come out. (And I'm also excited to get back on track with your k3s video series, but setting it up w/ Ansible instead of the custom shell scripts from the older vidoes.) Cheers!
@@CyanureNeko Correct, you need a "full" version of Home Assistant. Because of the Add-Ons, I use HAOS, which is then much easier to manage with things like File Editor, Samba Share or TasmoAdmin. Not much of a problem if you already have a hypervisor beneath it. When you look at the Add-On list, you will find that you miss out on some mighty tools for several IoT families if you use HA on docker. You would have to do all that integration yourself, which in part contradicts Home Assistant's approach.
Mosquito is supposedly intended to be used for lightweight clusters so HA is not particularly an issue. For more complex and heavy scenarios for IoT devices there are other alternatives such as RabbitMQ, Kafka, etc.. that are designed with those capabilitie: HA, fault tolerance, resilience, etc..
![SAFEPLANET - ดาวเคราะห์ [ THE PLANET ]](http://i.ytimg.com/vi/4X1XL3I_k3c/mqdefault.jpg)
I think you just have you just aligned with exactly what I was looking for. To understand mqtt lol. As always thank you for the fantastic content.
You're welcome, appreciate the feedback.
Nice and comfortable voice.
Holy hell, I LITERALLY set up MQTT ~3 days ago. It was a pain as I mostly have experience with Zigbee devices via ZHA in Home Assistant, so I had to set up Mosquitto for the first time for some new devices running Tasmota. Spent way too long on the project (mostly because I didn't realize that my router was blocking all traffic between VLANs, so the messages between the IOT devices and my MQTT VM only worked one way). Should've just waited for your video to come out. (And I'm also excited to get back on track with your k3s video series, but setting it up w/ Ansible instead of the custom shell scripts from the older vidoes.) Cheers!
Thanks, I'll be moving onto Ansible RKE2 soon(ish!)
12:29 No, that's not base64, that's a proper `crypt` salted password hash.
Great, thanks for clarifying.
Thanks a lot.
Most welcome!
why not root the traffic through traefik?
I had to support RabbitMQ at my last gig. The queue backed up all the time.
So is Mosquito MQTT better than RabbitMQ?
Are you still available for questions about Mosquitto?
@@evilsun8492 sure
You actually do not need to spin up a docker MQTT broker if you want to use it for Home Assistant, as there is an add-on for it available.
Thanks, that's good to know. I'll cover that in a later video.
True! ...however, docker version of HA does not include add-ons, had to use Mosquito on another container
@@CyanureNeko I also prefer a micro services approach.
@@CyanureNeko Correct, you need a "full" version of Home Assistant. Because of the Add-Ons, I use HAOS, which is then much easier to manage with things like File Editor, Samba Share or TasmoAdmin. Not much of a problem if you already have a hypervisor beneath it.
When you look at the Add-On list, you will find that you miss out on some mighty tools for several IoT families if you use HA on docker. You would have to do all that integration yourself, which in part contradicts Home Assistant's approach.
Mosquito is supposedly intended to be used for lightweight clusters so HA is not particularly an issue. For more complex and heavy scenarios for IoT devices there are other alternatives such as RabbitMQ, Kafka, etc.. that are designed with those capabilitie: HA, fault tolerance, resilience, etc..