I thought that this YAML needs to be saved to /config/esphome/m5stack-atom-echo.yaml. How does this alter the firmware that is installed on the M5Stack ATOM Echo? Also, does there need to be a separate .yaml file saved in this folder for each ATOM Echo device?
I acknowledge that I must be missing something (probably a lot of somethings) in my understanding of how this works. Is there any comprehensive description that I ought to be referring to, please?
I have to admit that I have struggled this week too in getting an ESP programmed.
ESPHome is a very nice tool to use those micro-controllers and if you plan to do more with it, I strongly advice you to invest some time in understanding the process.
The other option is to give up and a wonderful world of endless possibilities will remain closed for you…
EDIT: I was interrupted and didn’t finish that sentence about the ready made projects.
There you can find an easy procedure to get the Echo running.
I’ve read the ESPHome material in the past but I will do so again - I suspect that it’s a moving feast.
I have to congratulate the developers for the wide range of capabilities that ESPHome seems to offer so; no I won’t give up but I will re-read everything that I can find to attempt to build a better understanding.
I have been using ESPWebTool running under the Chrome browser to install and configure all of my ESP32 devices. i tried to use this for the M5Stack ATOM Echo but couldn’t make any meaningful progress.
Your response that I have to use the ESPHome Builder program provided the Eureka moment.
Many thanks to you and to the folks that gave us the ESPHome Builder.