Cool I have opened up my notepad++ and had a look at spacing which is all good and I had a re-read of the how to ask good question guide (I was wondering how to indent on the forum for code now I got it).
I found the issue to be that I downloaded the .js file from github and chrome kindly added html markup to the header of the bar-card.js file, I just copied the code from github and replaced the existing code in my file and restarted hass and now my bar is working .
There is post above which says customcards only applies to those who have installed and activated custom_updater in configuration.yaml which I havenât done yet, but looks like good idea. I have left my url as /local/custom-lovelace/bar-card/bar-card.js?v=1.1.0 and all is good now.
Release 1.2.0 adds the option to set the position of the icon to be outside of the bar. To avoid double config options show_icon has been replaced by icon_position.
Breaking Change
Removed show_icon config option.
Updates
Added icon_position config option. Set this to inside to replace the removed show_icontrue config option.
Fixes
Fixed min/max per entity config defaulting to 0/100 when no main min/max card config is set.
This is showing two bars each in a vertical-stack both of which are in a horizontal-stack (if that is relevant).
One of them has an explicit icon defined (for testing) the other doesnât (but the entity itself does).
No worries, I donât think youâre the only one forgetting about cache.
Iâd recommend using custom updater and tracker card. This allows you to set the resource url to redirect to customcards instead of local, which makes it so you donât have to add versioning to the resource url and just updates the cache whenever you update a card.
Wait, what? I do use custom updater and tracker card. Are you saying that means I shouldnât have to be constantly pressing F5? That is why I am so surprised embarrassed at forgetting.
Mine donât seem to (always) update the cache. Iâm using F5 the whole time!
Iâm not sure, there might be cases where it doesnât always work. But afaik if you use customcards instead of local in the resource url it should update the cache if you refresh the page.
However the example youâre referencing is not using per entity config, itâs using vertical stack in card. Iâm not sure if itâs possible to set the 3rd bar too 100% width.
My apologies if I have skipped this somewhere and itâs already possible, but Iâm in the process of condensing my LL yaml file and was wondering is it possible to have one main config for the styles, title, css, etc⌠and assign different severity levels to the entities. Case use being battery, CPU, temp and humidity are set to different severity and colors, so currently I am having to repeat the code 4 times to set the differences between them. Everything works as expected in my displays, just thought Iâd ask, and thank you for the incredible contribution, I see this getting included as a standard card IMO. @Gluwc
Not sure if you can have both icon inside and title centered. Maybe icon outside then title centered. I donât use icons, so not much help, but the docs are pretty clear from what Iâve read.
This is most likely a bug, but I canât reproduce it on my side. This is probably an issue that was fixed in 1.2.1, so make sure youâre running the latest version.
Well you do have an option to use custom entity attributes to set the config of the bar using the entity_config option. But that still requires you to set these options in customize.yaml.
The other option only really works when you define an entities list, which allows you to share the main card config between every entity in the list.