Click to customize component

Feature Requests
1

Right now the menu for customization is buried in the configuration making not that practical to use.

The tool would be better used if could be accessed when with a click/tap on a component itself. Let’s say you want to change an icon, instead of going all the way to configuration and find the item that you want to make the change you would just click on the component and click on some kind of config icon to have the option directly on the main screen.

I did a terrible mockup…but kind of gives the idea.

[Album] Imgur

What do you guys think?

2

It’s a great idea but it would also need the ability to prevent twankers er… ‘unauthorised users’ changing the config.

3

I also think that if this is not something you want to change all the time then it’s not worth dev time to code that functionality in. It’s not that hard editing the customise yaml file. It’s a once off per entity. Once this is set for your configuration you will pretty much never touch it again.

4

They already add the possibility to change the name of a few things.
Only with users, you could really avoid.

And would take at least 3 clicks at least to get the options to show up.

5

True but this has the potential to do a lot more damage than a name change.

6

Wouldn’t it be good to not have to open your computer if you want to change a device icon? Or forgot to change a single item?
(yes on hassio you could do it, but not everybody runs hassio)
I feel is it worthed, the devs should focus more on making a less labor-intensive the experience to configure an item.

And you want you could still use the yaml.

7

Yes but right now anyone can do damage in one way or another.
This kind of quick config shortcut is almost standard in any app that you use. Both Homekit and Alexa have it.

8

Not without access to the configuration files which are (in my case) password protected.

I’m not saying it’s a bad idea - I do like it. I would just like it to be developed after the implementation of user control, which I believe is on the roadmap.

9

It is not worth spending ANY time of something people are not going to use all the time IMO. There are other far more necessary things than having an option someone is going to use once.

10

It’s something that we can have both ways without having to change anything on the current yaml structure.

Do you use the customize menu?
I don’t.

11

Once. It butchered my automations. Never again.

12

Sorry to hear that. I didn’t know you could change automations there. I Thought was just the customize options like icon, name, HomeKit visible…
If is bad then defeats the purpose of my idea.