I know what you are saying. I really do.
My point was that “immediate” in both cases is a difference of a second or two so there’s no real difference. I think both cases are pretty “immediate”.
I have never said it’s anything other than a personal preference but seem to be continually called on to justify why I do what I do. I’ve given my reasons and it works brilliantly for me - the best of both worlds for me. I really don’t care if people scratch their heads about it.
Actually I started with the GUI just to find out that it was not written the same as the docs. What I mean by that is that the GUI editor puts the types at the bottom of the code, whereas the docs put the types at the top.
Example:
- cards:
- cards:
type: horizontal-stack
type: vertical-stack
However the docs present them as:
- type: vertical-stack
cards:
- type: horizontal-stack
cards:
For me this was actually harder than using yaml mode. So I switched to yaml mode. The advantages of having !includes was a nice bonus. As well as the split config.
You don’t have to justify anything to me. You do you. After the many prior interactions on the same point it has become more of a rhetorical question.
We are giving advice to a person just trying to get started in Lovelace and I’m just offering the other side of the debate.
That seems to be a common problem with all of the “editors” that the HA GUI offers. they organize every entry in each sub-section in alphabetical order. The automation editor does the same thing.
I agree with that too. I really hate how the GUI editor mangles stuff. (And the automation editor doesn’t even support complex conditions)
1 Like
I try to avoid any HA GUI editors, mainly because they arrange code in a very peculiar way (and there is no guarantee it won’ change in the future).
There is nothing one cannot achieve without an editor. But to be able to choose they need to try both ways.
One of the other things with the GUI editor is it makes it easier to rearragne cards and if you add a new card it fills in the details for you and gives you drop-down lists to select entities as well…
I want to thank every contributor for their perspectives. Although not everyone agrees, the reasoning has all been sound and informative. Clearly there are advantages and disavantages to both options.
I have been fooling about with the ui configurator and enjoying myself. I may go to yaml eventually, but as I say, just playing around finding what is possible at present.
Again, thank you for the interesting perspectives.
1 Like
Yaml for me as I fairly recently switched to the Frenck style of HA configuration. It’s not for everyone, but it really helped me understand the backend of home assistant much more than I did and it also helps me when I am tinkering as I can look at parts in isolation rather than getting distracted by all the other stuff in there.
1 Like