oof, I hardly rely on this function (mostly the kiosk). Thanks for all your work and I hope solution for getting kiosk back so that the big header is gone again 
I also never understood why the header is so big, it can’t be edited and spoils the overall look of the screen
2 Likes
Hi all. For the experienced devs. I already found this one here: https://gist.github.com/ciotlosm/1f09b330aa5bd5ea87b59f33609cc931
Could that be a solution as replacement
1 Like
First, thank you for having provided this awesome component. Like many others, the one feature I will miss most is the “hide header” one.
As you know how to do it (and I don’t and I’m not the only one here), could you provide a component doing only this?
I appreciate that with new HA features, eg hiding tabs can be done another way. But, “hide header”, you are the only one 
Thanks.
3 Likes
I would also like to add. It would really be enough to be able to remove that ugly, big header
Solves some of the issue, but I still need to hide some tabs for some users and others for others, also based on user agent, remove the chevrons and other declutter of menu items, change the color, etc 
Sad news, but completely understandable. Will be staying with 0.115 till everything I use from CH gets implemented into core.
Thanks for your work! Most important for me is to hide the header and tabs cause i use custom sidebar and fully kiosk on the tablet. Hope there will be another solution.
well, tbh, Ryan gave us a heads-up, but for now on 116, my CH is fully functional, with all exceptions and templates, in all its glory! On several dashboards, each with their own CH config. Without any performance hit at all.
I might even add, CH ‘feels’ more robust than before 
So for now, we’re good… no need to hold back on 116.
and of course, all the other ways mentioned here are hardly a substitute. Views can be set for users, but how raw is that compared to the fine grained options we have with CH? Yes, developer can be set an option.
But all other exceptions are so easily set in CH, HA doesn’t even come close.
This is a true gem lost.
2 Likes
It was amazingly supported while it lasted, thanks Mayker!
I used it to hide the header and also to hide the sidebar for guests. @finity All my verboten controls are in a separate admin only dashboard.
I’ve removed CH in preparation for the 0.116 update and every time I reload a page I wait for the header to shrink but it never happens 
Going to take a bit of getting used to.
Yeah, I can live with needing to create dashboards for each user.
But it’s going to suck that I can’t hide tabs anymore. I have a bunch of tabs I don’t normally want to see unless under certain circumstances so I turned them off with a boolean. Now I’m going to have to figure out the next best way of keeping them from cluttering up the header. Or just live with them there all the time.
I wouldn’t go that far.
One general access dashboard and one with dangerous controls that is admin only is enough to maintain for me.
Hate to see it go but thanks for all the work you had put in to it!
1 Like
I completely understand your decision. We’re in a very very delicate transition state of HA at the moment.
A lot of bad coding is being exposed everywhere, and tough (and sometimes wrong, IMHO) decisions are being made, which has to be made.
The benefit is of course that the code will get cleaner, but at the same time we currently loose a LOT of good functions, and some will not come back.
I completely agree that it’s important to keep it clean, and when people learn to code, they make strange things, until they learn ‘the right’ way of doing it.
What I’m going to loose:
- A lot of real estate in the Android app (it’s REALLY poorly optimized, menu, header, chevrons etc.).
- Sleak interface on my wallpanel tablet.
Very sad, and I hope that these things will be taken up in the GUI development soon.
Maybe you could be the next hire for nabu_casa and work on that part 
@tom_l Dangerous is an odd definition, what is dangerous, and for whome? with the current almost complete lack of ACL in the interface, everything is dangerous, and nothing is if people know what they do and the world is a perfect place. But I still consider it a necessity to have this enhanced in the GUI, it won’t solve it, as entities also needs ACL for it to be really usefull (so that my son can’t turn on/off the light on my daughters room or something like that). For now I have visibility of tab’s are turned on/off, which has nothing to do with security, but merely simplifies the interface for the different people in the household.
1 Like
Ah, thank you. That was not an option the last time I looked.
Too bad, but totally understandable. Thank you for all your work.
Hopefully HA core will implement at least hiding header and allowing a footer (like 99,99% of apps work with changing tabs). Or a dev will create a PR with only the basics like CH once was.
Where to place the code
no-header:
card-mod-theme: no-header
card-mod-root: |
app-toolbar {
display: none;
}
After card-mod is installed,
In your theme, place…
( your existing theme name: )
card-mod-theme: your existing theme name
card-mod-root: |
app-toolbar {
display: none;
}
4 Likes
/config/themes/yourname/yourname.yaml ???