As I’ve been building my HA automations, I have found that I have a customize.yaml that is FULL of hidden objects. The majority of which are input_boolean. Is there a way to hide an entire domain by default? I’d much rather have input_booleans hidden and then consciously decide which few I’d like to show.
Hiding does nothing in Lovelace. Are you still using the old UI, or are you just setting hide on everything because you think it still affects the UI?
Hey @petro! Thanks for responding! I’m using Lovelace. I’m not sure if I’m using the old UI. I keep everything up to date. The attached screen shot is what I have. Is this the old one? I AM able to set the hidden property successfully using this one.
Yes, but it’s not doing anything other than adding an attribute ‘hidden: true’. What do you think it’s doing for you?
EDIT: Nm, it is hiding things for you because you are using the old UI. as @flamingm0e noticed.
That screenshot says otherwise. See how it says ‘Remove states as default page on this device’? and ‘Go to the Lovelace UI’?
You aren’t using Lovelace.
I suggest moving to lovelace and configuring your UI. Things won’t automatically be included but you won’t have to hide things. Also, you’ll have a much better time making a UI that looks the way you want it to look.
So, maybe I don’t really understand the difference between Lovelace and what I was using. They look very similar. And the “hidden” attribute works for both. The biggest difference I see is how ecobee and alarm.com controls are displayed. They both look a little fancier in Lovelace. Other than that, what is the difference (I know, probably a really dumb question!)? What would I do differently to configure the Lovelace UI versus what I was using?
Yes it looks similar because it imported the same look, but modifying states UI was a pain in the ass.
It doesn’t though.
Oh but it does. Granted, I have not clicked the “Take Control” button. Maybe after that is clicked, Hidden stops working.
Lol. It’s merely converted your current states view and chosen to not include those things in the view. It’s not using that attribute
So you’re saying it chose on its own which devices/booleans to show and which to hide, and it is just a coincidence that it exactly matches the dozens of items I have intentionally hidden? Not a chance. I think the key here is the fact that I have never hit the “Take Control” button, which probably tells it to stop using the yaml code. Anyway, thanks for the Lovelace UI link. I’ll check it out!
If you think so.
Haha. No.
Lovelace will “import” your current view and groups settings. So states UI and Lovelace UI look identical at first.
There are 3 ways to use Lovelace.
- automatic mode. This is the default. It automatically adds your devices/entities to the front end in whatever manner it wants. It stores all configuration in json files in the
.storagedirectory. - manual mode. This is where you “take control” and manually manage your UI directly from the UI. All config is stored in the same .storage directory as before.
- yaml mode. You have to manually tell your configuration yaml that you want to use Lovelace yaml mode and then you configure everything through your ui-lovelace.yaml
Welp, I created this input boolean…
And then hid it…
And restarted HA. And it was still there. Damn it, you were right. 
I do appreciate your help!
No worries.
You really should move to Lovelace though. It’s awesome. Using the UI to manage the UI is a step forward, and no restarts required for any lovelace modifications.
I will. Is it tedious to set up? Meaning, will I have to add every single entity manually? Or if I switch from automatic mode to manual mode, will it still inherit my current setup and then I can customize from there? And will I no longer need my yaml groups and customizations? I guess everything UI related gets set through Lovelace and yaml is only use for scripts, automations, etc.? Sorry to bombard you with questions!
Well, I have a lot of entities, but I don’t want or need them all on my GUI. It just clutters things up. Once you switch to lovelace, in auto mode, everything will automatically be added to the frontend.
Yes, it just continues “where you left off”
Customizations are probably best handled directly in the frontend, but groups are only needed if you want to group certain things together to act upon the group. You do NOT need groups to display things on the frontend.
1 Like
I don’t use the GUI method of Lovelace config (I use yaml mode for many reasons) but I’m pretty sure that once you “take control” then nothing will change immediately. It should still continue to look exactly the same as it did before. The only difference is it won’t auto add new entities.
Then you can go to the UI editor and start making changes to the existing code/set up in there.
you can also make a back up of the current config by clicking on the “raw” button and copying all of the code from there and put it some place safe. Then if you make a mistake and want to go back to the original you just need to to re-copy the old code back into the “raw” editor window.
At least that’s my understanding of how it’s supposed to work.
1 Like
Thank you @flamingm0e and @finity. I “took control” tonight. (That sounds really dumb) . To confirm, everything did look identical after I made the switch. That was convenient. I haven’t spent much time with it yet. I see how I can move groups up and down, but I sure wish you could drag and drop groups to move them. The up/down controls are pretty clunky!