MQTT-Explorer VS termux-api

Quote from MQTT Explorer

Sounds like you're on a good path tracking the problem to aws, not the esp. First of all, I'd try to make it work with a "proven" solution, then move on to your own implementation. I have had good success using http://mqtt-explorer.com/ on windows to diagnose a similar situation. Mqtt explorer gives you very granular control over endpoints and topics, so might be helpful to you too.

I would suggest using Mqtt explorer (http://mqtt-explorer.com/) to see how often the sensor updates its values. This as a first step to narrow down the problem.

Here are a few alternatives: http://mqtt-explorer.com/ https://mqttx.app/

Use MQTT Explorer to view and generate messages: http://mqtt-explorer.com/

For MQTT debugging, I like MQTT explorer

You can write test programs to send very specific messages to simulate errors, or simulate entire components that aren't written yet. There are also free programs like MQTT Explorer that will let you browse the message traffic, generate messages manually, log whatever you cant, and even graph your values if you happen to send numerical values (that is really cool when you do some long-term testing).

To use a local server can let you control all details of your full messaging chain. Try other clients can make you away from the ill behaviors or bugs of specific client. I recently demonstrate how easy a free MQTT client (MQTT explorer) send to a free MQTT database on Windows 10 in my video.

A useful tool is MQTT Explorer. You can connect to your broker and see what changes when you use the light through an app or switch or whatever. This should help you understand the manner in which the light talks with mqtt. Once you think you have understood it, you can use explorer to publish test messages to see if it works as desired.

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: