marsh spear
Is there any way to adjust font size/color or background color of the standard cards?
Preferably by YAML or even better, directly supported in the UI?
Everything I have seen so far in my searches uses card-mod but that is 3rd party which I am trying to avoid to keep the system "supported"
BTW the mods should adjust the post guidelines to remove eperimental from the sections paragraph since it is now the default.
feral stone
If it is not mentioned in the docs for the card, then the short answer is going to be no. You could probably change some colors via a theme but that is going to be more of a global change (or at least a change for that view.) When you want to get a card to look different than what the Devs designed, that's where card_mod comes into play. All it does is modifies/injects changes to the CSS.
I am trying to avoid to keep the system "supported"
Support comes in all forms. If you have trouble with card_mod, users familiar with card_mod are going to help, for example. Relatively speaking, third-party additions won't break your system nor keep others from helping you. The whole point of add-ons is to help you make your system work the way you want it to. In other words, feel free to add what you want.
A couple of suggestions that I would recommend: card_mod, custom:button-card, and Mushroom card. They're probably three of the most widely used, IMO.
(BTW, I have tons of custom cards and additions to my HA and nothing has broke. Okay... Maybe just once, but I was messing around with stuff that I didn't know what I was doing and broke something in the database... And that was years ago.)
BTW the mods should adjust the post guidelines to remove eperimental from the sections paragraph since it is now the default.
There are some updates in the works that will probably change this in the near future.
marsh spear
> BTW the mods should adjust the post guidelines to remove eperimental from the ...
The dev's are pretty adamant that thou shalt be on your own if you choose to go outside the garden wall. Which is fine, I just find it annoying I have to agree to their waiver every time I want to look at what is available in HACS. I got it. The devs cannot support third party things. That makes total sense as they have no control over the third party code. Not taking on obvious shortcomings in the UI/UX seems to me to not benefit the users. I have done UI/UX work with industrial control systems and being able to change colors and font sizes is pretty basic and has been fully supported for decades.
Thanks for the thoughts. I may have to brave the annoyances of getting to HACS to have a decent looking dashboard display. The devs have come so far with the UI but missed some (to me) low hanging fruit for end user satisfaction.
feral stone
I just find it annoying I have to agree to their waiver every time I want to look at what is available in HACS.
I'm curious what you're referring to here. I've been running HA and HACS for roughly five years and have never seen a "waiver". Can you provide a screenshot of this?
Also, realize that support is community driven. The developers are not providing support, per se. Support comes from guys like me that run HA, tinker with it, figure things out, and just help out by providing knowledge that I've gained. (Granted, there are Devs in here, but most support comes from people like me.)
I am curious though. Did you purchase your system from somewhere or did you download it yourself and install it on your own hardware (or purchase an official HA Green or HA Yellow)? Reading your comments makes me think you're running some sort of "unofficial" distribution of HA.
@fossil lagoon can you look over this? Does this make any sense to you?
marsh spear
Every time I want to look at the functionality in HACS, I have to agree to the waiver dialog that gets presented. I am running HAOS in a VM in VMWare.
I ran openHAB for many years prior to switching to HA 3 or 4 years ago. Not a fan of programming java for automations, so HA is a better fit for me. With OH, I felt comfortable running other things in that VM that extended it, like playing audio notifications. With HAOS, I don't feel comfortable adding anything as I don't know what will happen on upgrades and I need the system to be as reliable as possible. So that means that any other functionality has to happen outside the HA VM.
I generally self support as my google-fu is quite good and most of the issues I will see, someone else probably has seen. I am more concerned about breaking something "under the hood" by adding drivers or other programs to the VM and having that either mess up an update or be broken by an update. That is why I am trying to keep the install as vanilla as possible. Uptime and reliability are more important than pretty or fully custom displays, but IMHO the display aspect should be highly customizable.
In researching solutions, nearly everyone's solution was card-mod and mushroom cards. It would seem that functionality should get rolled into an official Add-On. Capitalized since Add-On is an official term with a specific meaning in this world.
I feel like I sound adversarial, but I don't mean to.
fossil lagoon
Every time I want to look at the functionality in HACS, I have to agree to the waiver dialog that gets presented. I am running HAOS in a VM in VMWare.
That seems weird like a bug in HACS, but HACS is something maintained by a private individual, that's not something home assistant officially supports.
I might expect you to see that once when you install, but certainly not every time 😕
marsh spear
I would not rule out consumer malfunction. If many others have not seen this behaviour, then it could well be me doing something out of the ordinary.
feral stone
Yeah. That should only be a one-time message. To me, it seems like your HACS install process may not be "completing the process." A uninstall/re-install might be the first thing to try. Next to that, checking (or submitting) the issues on Github.
I wouldn't think that most frontend related items installed via HACS would break your system. Integrations and Add-ons, perhaps. Occasionally there are some breaking changes that affect some of the cards, but you would just want to look at the release notes before clicking the Update button. The ones that I've seen are written in big letters to get your attention.
feral stone
Thought of something else for you. You basically said you don't want to expose your production system to unnecessary risk via third-party additions. Suggestion: spin up another HA VM, but, on this one, enable the Demo integration and use this system to try out third-party additions. The Demo integration will give you dummy devices and entities that you can use to play test with. If a third-party addition seems stable and usable, then you can add it to your production system.
I have the Demo integration enabled on my system and its entities are what I use to help others with devices that I otherwise would not have such as blinds and HVAC. Here's an example where I was able to help someone with their blinds even though I don't have any but was able to work alongside of what the other user had. https://discord.com/channels/330944238910963714/1184380429432791091