This is just a test…
This one’s going to be some work, but it’s too cool. Thanks @cameron!
3 Likes
In the chrome developer panel I get the following error:
Uncaught (in promise) /local/compact-custom-header/compact-custom-header.js?v=1.0.2b8
Does compact-custom-header.js exist in this folder: /www/compact-custom-header/?
The indenting looks off in both of the resource samples you posted as well, try this:
resources:
- url: /local/compact-custom-header/compact-custom-header.js?v=0.1.4
type: module
Thanks for answering me.
Excuse. There is no retreat.
using New lovelace editing mode
I’m in the version
0.88.2
resources:
- type: module
url: /local/compact-custom-header/compact-custom-header.js?v=0.1.4
- type: module
url: /local/mini-media-player-bundle.js?v=1.0.2
- url: /local/my-custom-card.js
- type: js
url: /local/custom_ui/weather-card.js
- type: css
url: /local/my-webfont.css
- resources: null
type: module
url: /local/button-card.js
- type: js
url: /local/card-tools.js?track=true
- type: module
url: /local/fold-entity-row.js
- type: module
url: /local/atomic-calendar.js
- type: js
url: /local/plugins/card-modder.js
- type: js
url: /local/upcoming-media-card.js
- type: module
title: Home Assistant
views:
- badges: []
cards:
- cards:
- entity: device_tracker.juliana_iphone
state_image:
home: /local/juliana.jpg
not_home: /local/julianaoff.jpg
type: picture-entity
- entity: device_tracker.renato_iphone
state_image:
home: /local/renato.jpeg
not_home: /local/renatooff.jpeg
type: picture-entity
type: horizontal-stack
- entity: weather.dark_sky
type: weather-forecastI have resolved. Spacing error. 
embarrassed.
1 Like
Yes I like that. But I was talking about individual tabs icon.
Oh I know, that was a proof of concept. Ideally anything that can change color would have the same behavior.
I could see this being used as an alert indicator, perhaps when there is a hidden notification in the options menu? Or any custom condition triggered by an automation.
1 Like
So this is the current idea for the config of this feature. This should show how this will loosely work.
conditional_styles:
entity: input_boolean.testing # Any entity
condition:
equals: off # string to compare entity's state to
# If the state is a number you could also use one or both of the following
greater_than: 20 # not to be used with "equals:"
less_than: 50 # not to be used with "equals:"
# what elements to change
button:
menu: red
background:
color: blue
image: url(/local/background.jpg)
I’m thinking about icon changes as well, but this all is really just a thought right now and is subject to change. Will most likely extend entity to also include entity attributes, not just state.
2 Likes
I like the idea of this tapping into notifications like you suggested. Probably with just “notification: true” as a condition.
Edit: That doesn’t really make sense. The notification might make more sense as an entity. So something more like:
conditional_styles:
entity: notification
background:
color: red
1 Like
Kinda stuck on the no tabs look for now and about done with the theme adds…
Thanks for the hard work!
1 Like
Can we have an option to hide the notification bell when there are no notifications, and show it if there are active notifications?
On mobile right now, its not ideal to keep it as overflow, because then you might miss the notifications, and when there are no notifications its just a waste of space
1 Like
I may have missed it, or someone may have asked already; but if not, I’d like to request a feature to display the current user in the upper right. Or a custom text per user?
Did the legacy browser version stopped working for anyone since move to 0.90? Any updates on this?
This and another feature request that I added to the github myself and have since removed (for adding entity states to the header) prove troublesome.
In order to keep things laid out correctly I need to calculate the space that they take up and since the length of user names and states can vary wildly I haven’t found a good solution. I’ve thought about just adding space dependent on amount of characters, but unfortunately since the default font is not monospaced this wouldn’t work either. I could force a monospace font for things like this, but would also need to force style updates every time the entity changed, etc. At the moment this seems to be more trouble than its worth.
Make sense, thanks for the response though!
It’s working well for me on HA v. 0.90.1, CCH v 1.0.2b1.
