mosquitto VS zigbee2mqtt

mosquitto_transport, an experiment of writing SObjectizer-based wrapper around mosquitto library;

References: Felipe Flop’s website https://www.filipeflop.com/blog/controle-monitoramento-iot-nodemcu-e-mqtt/ accessed on 01/27/2018. Eclipse server for MQTT Broker https://iot.eclipse.org/ accessed on 01/27/2018. Mosquitto https://mosquitto.org/ accessed on 01/27/2018. Cloud MQTT https://www.cloudmqtt.com/ accessed on 01/27/2018. DuckDNS https://www.duckdns.org/ accessed on 01/27/2018. Proftpd http://www.proftpd.org/ accessed on 01/27/2018. Filezilla https://filezilla-project.org/ accessed on 01/27/2018. Fritzing https://fritzing.org/ accessed on 05/25/2022. Appendices:

This is a perfect use case for MQTT, e.g. this library for ESP boards. Create a broker on the network (e.g. a Raspberry Pi running Mosquitto, and have all the ESP boards subscribe to a topic. When you want to play a sound, publish a message to the topic, and all of the ESPs should see it very quickly. You don't need to synchronize clocks any more because it's simply based on the timing of publishing a message.

While working on a personal project Komponist, I was due to update Mosquitto MQTT Broker due to a CVE and found some interesting changes that will impact me in the future when it comes to configuring the Broker. This post provides a solution to make the Broker compatible with future versions using new and less visited concepts in Docker Compose v2, namely:

Optional: Mosquitto, an open-source message broker that implements the MQTT protocol; this tutorial uses the public test server

I think he means implementation of MQTT protocol, like https://mosquitto.org/

Could MQTT work for you? You'd need a broker like Mosquitto, and then any of a number of MQTT clients.

Have you considered Zigbee2mqtt[0]? You'd be running an extra program, but the docs are really good, it's pretty lightweight, and MQTT is incredibly easy to talk to from python or basically anything else.

[0] - https://www.zigbee2mqtt.io/

For Zigbee, I can recommend using the Zigbee2MQTT (https://www.zigbee2mqtt.io/) integration instead of HomeAssistant's built-in ZHA system. It might be a bit more complex to set up, but it's very powerful and works fantastically. (User "simon42" on YouTube has some good videos about the topic, but they're in German.)

This is definitely better than many of the alternatives but still not perfect. With Zigbee etc you end up locked into one or more of the ecosystems, not to mention some manufacturers implementing it in a way that has weird quirks (see [1]). With esphome you have a limited choice of devices (would love to see more), but you also usually end up locked into keeping a 2.4GHz WPA2 AP for your devices (and you miss out on mesh, but also the problems when it doesn't work...)

1: https://github.com/Koenkk/zigbee2mqtt/issues/16717

I can recommend this: https://www.zigbee2mqtt.io/

You can keep your Hue bulbs and devices but threw away the app, hub, and need to work with hue as an institution at all.

I got a $30 USB zigbee stick to replace the hub. works great!

It looks like it uses zigbee? If you have a server you could run zigbee2mqtt. You'd also need a zigbee dongle / adapter.

\also posted on the z2m* github device discussion board

If you want to use HA on your phone, you would need to install it on the pi, along with either ZHA or Zigbee2MQTT for the Zigbee network interface. Debian alone won't be able to interface with most of your smart devices.

I still haven't understood if the devices will change the path using the better route or not (since I've just tested a bTicino switch K4003C and it keeps using the worst path with 1 or 0 signal quality over a near Ikea repeater with a signal quality of 50).