ESP-Mail-Client VS mosquitto

Shot in the dark here - take a look at ESP-Mail-Client and see if you can use it to check/read mail and grab subject lines and/or other info to act upon.

Very cool, love the big button to stop the light! I echo what the other person suggested, you could give a try at this https://github.com/mobizt/ESP-Mail-Client. Also, it's funny I've been working on something quite similar, the same kind of rotating light but with broader use cases. Basically, you can connect it to pretty much anything to automatically turn it on (a new alert in your github, a new sale on your shopify, etc). https://getgumball.com/ I'm not gonna lie, I'm addicted to it (and yep, I'm obviously biased because I create it, but still!)

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/

MQTT is a message broker that's used commonly in IoT (internet of things). This is from all of one week's experience, so take it with a grain of salt, but it's a publisher/subscriber model where each device defines some channels (like openevse/wh openevse/amp etc) and then publishes its stats to an MQTT broker like Mosquitto. Then other services (I've tried it with HomeAssistant and openHAB) pull in the values to store them, drive automations, etc. OpenEVSE also subscribes to input channels that can control it, so I've seen people set up things like 'only allow the charger to run when my pool heater is not running'.

Mosquitto(MQTT)

Use the Paho library with Python to transmit your measurements, use Mosquitto as the brokers on the other side to hold data and deliver it to your dashboard code when needed.

MQTT from the ESP style devices is well supported - you could use the Pi as the broker. Mosquitto is not very heavy in processor or memory - I ran it happily on a zero :-) Just watch out on the security side if you are not using a private (none customer) WiFi...