#dashboards in yaml or not

1 messages · Page 1 of 1 (latest)

kindred raptor
#

What is your opinion. Should I write all my dashboards in configuration.yaml? I see the advantage to split custom buttons into several files and beeing able to use them in different dashboards. On the other hand, editing the dashboard in raw give me the advantage to see the changes I made immediately, no need to restart HA.

My greatest problem every time is, that I have to copy i.e. card modifications into every card. In configuration file it is easier done.

What do you think?

pulsar valve
#

You don't need to restart HA anyway... YAML dashboard changes can be refreshed instantly

#

There's also nothing stopping you from experimenting in a UI dashboard and copying the YAML out

kindred raptor
#

YAML dashboard changes doesn't work, I've rearly considered any changes when only restart YAML.
And yes I know I can experiancing wihtinh UI dashboard. My question was more, hou the majority of the users are dealing with this.

pulsar valve
#

Yes, they work

#

Hit Refresh - that's all I do

#

That's all anybody does

#

That said, most people are using the UI, because it's easy. Those of us using YAML are the exception, but it excels for things like not having to duplicate config/YAML

kindred raptor
#

Where is this "Refresh"? Is this the browser refresh?

pulsar valve
#

Top right corner of the window, as shown in the image

kindred raptor
#

Nice, never tried this, thx. I've always tried "Reload all yaml configurations", which didn't work.

pulsar valve
#

Yeah, that's for everything but dashboards

crimson dove