Because we now can add any custom card in the redesigned badges section, I was experimenting with my ‘round’ custom: button-card buttons with live streaming cameras,
I just discovered we can’t use the aspect_ratio option in the cards options.
currently these are in the cards section of the view:
and obviously a bit too small for this functionality
if anyone has experimented with the custom:button-card and aspect_ratio (and size for that matter) succesfully, please let me know. Would actually be very nice to have these cameras stream via badges atop of the view
maybe this should go in button-card thread, because we can set the picture style to
entity_picture:
- width: 170px
- height: 170px
but because the video element is not using that same dimension we get this…
love the badges! finally one step closer to stop using mushroom but go with native cards.
Two things I am missing - hide state - I want to use icon only for navigation. and second is menu button to hide/show left panel.
EDIT: just found out that hide state is possbile by minimal settings
I’ve never used Badges in the 3 years plus that I have been using HA, but for people searching for an alternative to the current situation, here’s two solutions (examples) that I came up with.
The first row is using the Grid Card (5 elements) and is seeded with the Markdown Card (with optional link to other Dashboard Tabs) for each element.
The second row is again using the Grid Card (5 elements) and is seeded with the Custom Button Card for each element. Clicking on any of the five buttons calls a specific Script for that button which in turn updates a Text Helper.
The graph (ApexCharts Card) is configured to change on any of the above buttons via the Text Helper.
would you know if there is a way to modify the new badges ( which I don’t like at all) to be bigger? I cannot see very well and the new badges are now too small. thank you
Same here and approaching 60: But I like them a lot but they are challenging to see, in a quick glance. I know what you will say, buy a bigger phone or screen …
And yes, Ive asked some consideration for older eyes before… the new badges are too small to show certain info for my eyes, (I believe it is also the reason some would prefer the old style badges, however out of style in modern day design they are said to be)
if you have specific needs on visual accessibility, that would be another aspect, I dont have any experience with, but there are specialists at work to keep HA up to the latest I believe. Maybe contact them at the Frontend repo Accessibility Discussions for that?
Because the discussion didn’t come up again until reply #394. Before then, the problem was somewhat resolved with the discovery of custom:hui-state-badge-element. So yes, you’re correct about the cynicism.
Besides, I don’t lurk the forums that often. If I react to every post, it would look like a flame war despite it is not. Also, I can reassure everyone again and again that we are looking into fixes, but there’s nothing I can do if one wants to believe the otherwise.
I’d much rather not cultivate the idea that being toxic or outraged will get better responses. We are all just human beings here (I hope? ) trying to do some good. We make decisions good and bad, and yes we make mistakes too. It’s not corporate speak, but it’s more like the corporate mo****f*****rs abused healthy de-escalation techniques for their greed.
I found a new problem with the badges. I had a badge with hacs.sensor. After installing Hacs 2.0, Spook said correctly I had a messing entity hacs.sensor on my dashboard. But I could not delete it through the UI, as it was not showing. (Old ones would show). I had to go in the raw configuration editor to delete the badge.
That’s a bug. We will push a fix for that for next release. Don’t hesitate to open an issue in frontend repository for this kind of thing so we are aware of it.
All that is fair enough, but I think devs should more time gathering feedback here. There is a paucity of dev responses here. Not just you, but others. I’m sure they don’t have time on their present schedules, but perhaps they need to make that time, and step back the pace on development. But I know creators want to create, and there are only so many hours, and so much caffeine, in the day.
No Nick has used the saying correctly. “only so many” refers to a finite amount that is not enough to do all the tasks at hand. “Many” does not mean “a lot” in this context.
I’m struggling a bit to avoid making this sound personal. I’ve done development, and I’ve done customer support. And I’ve been a customer. I know the dynamics, and I know what works well and what leads to bad feelings between these groups.
High on that last list is developing an “us vs. them” attitude. Customers get angry, devs get defensive, and the gulf widens. I hate seeing that sort of thing happening here.
It’s fun to try new things as a developer. We love the “move fast and break things” approach. It’s no fun to just keep things working; fix bugs, add little changes that customers asked for, make sure everything is backward-compatible and generally just keep the lights on.
I think we talked about listening earlier in this thread. That’s why I was a bit surprised at the dismissive attitude toward this forum. This is the first place customers are sent for more information:
[Note: Yes, I’ve substituted the word “customer” for “user.” This was intentional. I’ve found that successful IT groups adopt this mindset. Whether paying or not, the users are your customers. They are the reason you do this work. They will decide whether you succeed or fail.]
Same as Tom I’ve lived in enterprise product support for most of my career. At the same place one of your coworkers recently moved from. Yes that place
If this ever comes up in planning discussion. This is my very sincerest of asks. This comes grounded in over 25 years of dev support.
Please Don’t EVER EVER EVER change a default like this again. Full stop.
ALWAYS put new feature to migrate to and a way to migrate with defaults but Never ever ever ever change a user’s setting for them. There is no good that can come from it.
Had the feature been named chips (heck you have Pitya not like you can’t use the name) and badges left to thier own to die on the vine in a year or two… None of this would have been necessary.
Thank you and the team for all the hard work. But I’m beside myself at how this is handled.
Nathan,
I generally agree with don’t change the default, but many times due to the direction the core is going , an api change or an integration by an out side vendor it is a necessity (I.E weather attributes, Aladdin, etc). Usually this is explained and users have ample time to come up with solutions months prior to any changes or during beta so solution can be given to the forum or in the release notes.
This changed to me came out of nowhere. The beta which was taking about new badges had an issue with many users. I struggling with it due to the Android companion app not working with the new badges. I did not look at the badges due to this issue until the end of beta and never addressed the issue it in the beta discord.
I believe if enough of us did during beta either the developers or the advanced users would have come up with a solution prior to the release.
I appreciate the optimistic position but my experience in product dev says. No, screams, otherwise.
Users like thier settings. The minute you’re changing them - EVEN for a worthy cause. You lost the game. You will NEVER (yes an absolute) please the user community if you are changing thier existing setting. The ONLY exception is if the setting g is depricated and doesn’t matter anymore.
Over my career I saw it happen to product after product. Usually when a new PM was added. And in those cases products that suffered this issue had it happen again. The post mortem basically went - did we not learn our lesson last time?
Edit: because someone asked. No I absolutely hate the old badges and think they should die in fire.
Not sure that I was optimistic, I was just pointing out what I have experienced in the many years using HA that either the coders, experienced users or sometimes the change is pulled when enough people point out the issue and it gets resolved very quickly. Most of the time (not all) I find the people making decisions in the direction of HA to be very reasonable.
I agree with what your are saying 100% of the time that no one likes changing to the existing settings. This has happened many times in the many years of me using HA. Most of the time the changes required extra work to get my system to work as before the release was made.
I’ll add my two cents worth of feedback on the new badges. I wanted to give it several days to see how it worked out. This feedback is particularly in regards to a tablet that I use running HA on FKB. The tablet is located at a fixed position on a countertop underneath a cabinet and I use it like a wall-mounted controller. My Tablet’s display is 8 inches and the distance from it to a user’s eyes is around 24 to 28 inches.
State information - font size is OK.
Name - font size is very much too small (can barely read it). The old badge’s font size was OK.
Icon size - is really too small. You can make it out, but more pleasing to the eye if larger. Again, the old Badge’s icon size was fine.
Width of the badge is probably OK, but prefer a smaller width in order to fit more badges on a single row.
But I like them a lot but they are challenging to see, in a quick glance. I know what you will say, buy a bigger phone or screen … 
) trying to do some good. We make decisions good and bad, and yes we make mistakes too. It’s not corporate speak, but it’s more like the corporate mo****f*****rs abused healthy de-escalation techniques for their greed.
