#ESPHome configuration app

4 messages · Page 1 of 1 (latest)

edgy topaz
#

Hi everyone!
Some time ago we became interested in esp32 and setting up various sensors, using ESPHome. We constructed a shield for quickly switching these sensors and additionally decided to create a web-service for writing YAML-configurations, validate, compile and firmware updates esp directly from browser. You can find the code on https://github.com/apbodrov/esphome-yaml-constructor
Now it works on http://app.kolkhoz.io/

On the right side you can fill the form with parameters you need to configurate and set up various sensors. A YAML configuration is being assembled from the data on the left side. You can validate the code, compile the binary file, download or install it on controller connected via USB. You can also save config to your account or share it with others.
If someone could benefit from such a service, we can add your requests to the task queue.

edgy topaz
#

I'm sorry, wrong name

app2.png
silk verge
#

Generally this could be useful although feels very long with all the padding/margins around stuff, but I have a few questions/statements:

  • Why have the option of 1 uart or multiple and not just have multiple from the start? (Same for i2c)
  • Why force api and ota password? These should be able to be not specified at all...
  • Same with wifi credentials as people might not want to send their ssid and password to your server...
edgy topaz
# silk verge Generally this could be useful although feels very long with all the padding/mar...

Thank you for your feedback!
Essentially, this is a simplified diagram made for our needs, which we will expand over time.
In response to your questions:
• We will fix the margins soon.
• The number of uart or i2c depends on the circuit. If it is single, an id input is not required.
• We will make api and ota optional.
• You are absolutely right about the Wi-Fi credentials, but personally, we use this service to send configs to clients, and we already know their networks. However, there is an option to do this on the client side and not send sensitive information.