-
-
Notifications
You must be signed in to change notification settings - Fork 106
Header Doesn't Always Load #264
Comments
Important:Issues that don't provide the necessary information listed below may not get a reply and will be closed until the info is provided.
If you haven't yet done so, please read the "Before Posting an Issue" section of the docs site. Include as much of the following info as you can to help me replicate and investigate your issue:
When pasting in your config always place 3 backticks |
This has been addressed in the latest pre-release 1.7.8. Please, report back here and let me know if it has fixed your issues. To view pre-releases in HACS go to the Custom Header listing under "Frontend", click the 3 dots in the right hand corner, select "Reinstall", turn on "Show beta versions", select 1.7.8, and hit "Install". Clear cache afterwards just in case. If you do not see the version 1.7.8 reported in your browser's dev tools console (F12). You may need to reinstall or clear cache. If you installed manually, make sure you're adding to the URL version number in your Lovelace resources. |
Closing as I'm pushing this into a full release and I'm confident this should be solved. If not please let me know. |
I've updated to 1.7.9 and cleared cache, but still had the issue this morning with a new error message:
The console does show the details of the custom header version, device ID, and user, which it did not with the previous issue. Let me know if this issue can be re-opened or if you want me to open a new one for the different error. |
No worries, I'll reopen and investigate further. Will keep you updated and let you know if I need more info. Thanks! |
Got a different error this morning:
|
Recently, I've been having an issue where custom header won't load. The regular Home Assistant header loads without being compact or styled. This doesn't seem to be happening in the mobile app, only in Chrome on Windows 10. I've tried clearing cache without success as well. Here's the error I get in Chrome Dev Tools:
I'm on the 1.7.7 release of Custom Header, installed through HACS and configured in YAML mode. I'm on .115 of Home Assistant but saw the same on .114 as well. Here's my YAML configuration for Custom Header:
Refreshing the browser reliably causes the header to properly load.
The text was updated successfully, but these errors were encountered: