#Editor for ESPHome - Home Assistant Add-on

24 messages · Page 1 of 1 (latest)

reef current
#

Hi everyone!

This post is a little different—it’s not about an ESPHome device but rather an extension I created for ESPHome a while ago. Now, it also works as a Home Assistant Add-on!

Introducing ESPHome-Editor: A tool designed to make managing ESPHome devices easier and more efficient. It’s especially helpful for handling repetitive configuration tasks—whether you're managing multiple components in a single device or using the same component across multiple devices.

I’m excited to share the latest update! 🎉

I’d love to hear your thoughts! If you try it out, let me know how it works for you or if there’s anything I can improve.

screenshot.png
sonic willow
#

This looks intertesting. I've had trouble with this very thing- having multiple devices with identical hardware all needing updates.. thats said, I was told to use "include" statements and breaking the file into portions per use was the "right" way to handle this. .🤔

reef current
#

Yep. Include is yaml way of reusing code. It is good but limited. I hope this addon will help you a bit

sonic willow
#

I think maybe I'm not your target audience. I couldn't even figure out how to get this installed. 😦

reef current
#

Was there some issue with installing the addon repository or the addon itself?

reef current
#

You can run it via docker and provide url to esphome instance. Haos is not needed

gloomy perch
#

Any plans to make this run aarch64@reef current ?

reef current
#

The standalone version should work and I don't have HW to test the addon version. I guess I will just release it and wait if someone complains 🙂 I'll try it next week

reef current
#

@gloomy perch I just published v0.6.0 that supports additional platforms including aarch64

reef current
#

Editor for ESPHome - Home Assistant Add-on

west urchin
#

Just installed - looks cool!

shy ore
#

trying it too

#

is there any plans to support jinja2 templating so we can use same syntax as in esphome standard config ?

reef current
#

Currently not, but you should be able just have it in yaml and keep the processing up to esphome

cursive ether
#

What are the benefits between this add-on and the esphome dashboard and vscode add-on Exactly, what makes this add-on do the managing better f9r example ? It is not 💯 % clear to me.

reef current
#

Main benefit would be code/config generation.

stable zealot
#

As I see it, yaml can be a bit intimidating for newer users. Being able to drag and drop representations of components, with the implicit connections between them being shown could be a nicer way to get your feet wet.

#

I do see a problem with the possible use of packages. I would expect the UI to work with the output of esphome config tmpfile to get a flattened config, and add yaml for UI components to tmpfile directly. Having a UI component that results in a package: ... entry in tmpfile would be interesting, I'm picturing it as a container with the UI taking the output of esphome config includefile to determine what is in the container vs outside of it. And tbh, this is advanced usage, so not really what this is/should be aiming at, at least not in the beginning.

spice coral
stable zealot
#

I do think it would be useful to show/highlight things like implicit connections of uarts, spi buses, etc, which config shows, I believe?

#

but obviously, knowing what is default and what is custom would be very useful in terms of what is shown and what is hidden

#

but running config also gives error messages to show when your config is invalid, which is obviously important, as a canonical source of "yes, this should compile, vs this won't even pass validation" info.

#

Ideally the json schema would include a little validation information such as which parameters are optional, and if not present, what the default value is. (Not sure if that is already the case)