mosquitto VS termux-api

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.

But, I don't know how to turn off data edit: not possible, turn off hotspot or enable airplane mode (not sure if this is possible) or enable or disable hotspot (not sure again and it would be nice if you guys could help me with this :')

If it's just the startup time, it could be the same issue as for Termux:API, both use am to launch the app. I thought I included support for termux-am with am as a fallback, but it seems I only did that for the C library. Will fix that later for Python. As Termux:GUI only works with the GitHub release of Termux, termux-am should work always, though the am performance issue seems nearly solved: https://github.com/termux/termux-api/issues/552

It's possible that you need to also install termux-api

Termux:API - Not necessarily needed. See below

If you installed from github it's probably best to install the termux:api app from there as well. Here is the link: https://github.com/termux/termux-api

The Termux Android API does not yet have support to detect Media Key buttons so if your car has the next song button and you want to use that you can setup another Tasker Profile likeso: