Tasmota VS mosquitto

All of my office devices are connected to Sonoff S31 smart plugs, flashed with Tasmota on their own locked-down VLAN, and can be controlled via voice, Alexa, Tasker automation on my Android, NFC tags at my office door and various scripts triggered via my StreamDeck (on Linux). This all works fantastic, and I can turn on or off my devices, including my printer, when I start or end my day at work.

The best alternative firmware example for true IOT devices is Tasmota [1]. Erase manufacturer firmware for every ESP devices the day after purchase to avoid those careless manufacturer firmwares.

[1] https://tasmota.github.io/docs/

The ESP8266 based Sonoff S31 and ESP32 based Switchbot plugs, both flashed with either Tasmota or ESPHome, are my go-to options for US WiFi smart plugs with power monitoring.

And if you want to turn your ESP8266 into a standalone appliance, with a web interface and directly editable config that doesn't need a build step, Tasmota is another great option.

https://tasmota.github.io/docs/

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.