When I load the instance, it briefly shows the set Title, and then shows Home Assistant. I had Custom Header installed, but for testing purposes disabled that. Also restarted a couple of times and cleared cache repeatedly.
see what happens (the blank flashing is when I click reload) :
configuration.yaml holds the same name, but shouldn’t really be of importance any longer. Clicking the general settings reveals the correct name also, although it shows I am in yaml mode, and cant change it there:
yes!
that was it. I did take out the ui-lovelace.yaml pointer to Custom Header, but the custom card was still loaded via the resources. Took it out and there was my correct name. Which brings me to 2 new questions for Custom Header:
1 - don’t override the title set in ui-lovelace.yaml
2 - be compatible with @thomasloven s favicon. 🔹 favicon - Change the favicon or title of your Home Assistant interface
of course the latter would be a vice versa Ill ask there also.
btw, I did manage now to reach the end goal, of dedicated icons and instance names according to the favicon custom component. Steps:
1- completely remove pointers to Custom Header, both in resources and ui-lovelace.yaml)
2- setup favicon according to https://github.com/thomasloven/hass-favicon
3- (re)install Custom Header
Note to have set a title in Ui-Lovelace.yaml, which should be default for all other integration/custom components really…
thanks
mayker
(maykar (pronounced "maker" with a southern accent))
6
I replied to your question on the title before here. Custom Header hides the default header and makes a new one. The header text is templatable, but it should use the one from lovelace config as default and I’ll probably add that to the next release.
HI Ryan,
we crossposted… thanks!
And yes you did, I just hadn’t linked it to this issue.
Please add that indeed, it would make a big difference.
Also as the steps I outlined above show, somehow the CH interferes with the favicon installation. Not only does it keep the Lovelace title from showing, but as a consequence it seems to stop styling the favicon as set in the favicon integration.
would be awesome if you could check why this would be and if you could join forces! Ive also asked Thomas here so no further need to post on your thread or Github is there …