Badges vs Cards

Cards provide a great way for grouping devices.

And badges are rich UI elements

But are there some design principles perhaps around which should be should when?

Can a badge be shown also as part of a group on a card?

Just trying to get head my around this a bit.

thanks

1 Like

Badges are limited to the read only parts (sensor/device tracker) of HA + buttons for scripts/scenes. If you add an entity to a group it will no longer be shown as a badge but as a member of that group instead.

2 Likes

Iā€™m on the dev version and all my scripts and scenes are shown as a group, I canā€™t pin down why and searched through all the repository and forum without answer. The only major thing I changed was splitting customize and groups NB:I also have scenes referencing to light groups that I think Iā€™ll need to change as the logbook is getting spammed with state changes that I actually donā€™t need and read referencing lights multiple times in group isnā€™t desired.

Iā€™m seeing the same thing here. Been going through everything one by one but I canā€™t seem to narrow it down yet. Did you figure out the issue?

I also went through things one by one and noticed a few scenes that were missing, but even after fixing no luckā€¦
I noticed something strange in the logbook where default_view showed upā€¦
Have you also moved out your group setup with !includeā€¦ ?
My next step will be moving it back into configuration.yaml ā€¦

@nkgilley & @balloob : even after reading it, I somehow didnā€™t get it and kept thinking something was wrong in my setup, and I kept for 2 weeks trying to bring my badges back.

Iā€™m really sad of this decision : IMHO scenes and scripts made totally sense as badges.

They cannot be switches and took much less screen estate when they stayed on top (I have sliders and booleans along and it really helped me differentiating between actions and statuses / variables).

I would really like to have the choice between cards & badges and would happily make a donation toward this goal.

In hoping my small feedback will reach youā€¦
Matt

The problem is that it leads to a confusing user experience. You can press some badges and it will open a more info dialog. You can press another badge and all of a sudden all the lights change or you trigger a script.

They might be able to move back up if we can come up with another way of making them look that are not badges. The Play Store app details page (our inspiration for the badges) has some other badges, but none of them make them look like you can actually push them. Using material design FABs is not an option either, it looks weird having multiple of those.

On top of this is the fact that it feels messy to have many badges on top which also needs fixing.

All in all, what we currently have is giving a consistent experience. It will eventually evolve but these things all depend on time and design inspiration.

1 Like

TYSM for explaining your thinking!

Even if I got used to not having scripts & scenes as badges - only seeing the ā€œmore clutterā€ and ā€œless practicalityā€ - you helped me see how narrow sighted I was.

I liked the material design approach (and independently of HASS, so did one of my esteemed professional colleague) and your reply enlightened me why the user experience was affected (having cards & actions mixed).

Nevertheless I still cannot accept the change and may have a suggestion on how to solve this dilemma: what about a color coding?

For example a blue outline or box could be applied to state badges, and red to actions?
(Iā€™m color-blind in green tones, so I wouldnā€™t agree with the common green/red approach)

I may have missed something, but using views it seemed that my scripts/scenes groups arenā€™t sorted properly.

[grateful rant on]

Iā€™m using hass mainly to manually set scenes & brightness across different manufacturers (6 lifx & 20 hue lights). so - with my limited programming skills - I already had to work around the way hass work to build a brightness slider. Thatā€™s why Badges were really usefull to me as I was only using groups to display states.

I may not have said it already but I am really grateful not having to rely on IFTTT anymore : I saw too many web services go down over the last 5~10 years not to see how my reliance can impact my daily life (wink wink google reader).

Thatā€™s how I started to value opensource and digital altruism, when I was young I learned through shareware & freeware, but as soon as I made a living I couldnā€™t accept not giving something back to the community, first through participation and then donations.

Seeing how you & @fabaff are contributing to this project really touched me, making me think back on my many fails to adopt linux, and more recently node-red (giving up after a synology update ā€˜ate my paperā€™)

Same thinking goes to @mtremer who started an awsome firewall distro and in whom Iā€™ve invested through an ipfire duo box, even if not perfect : invested and dedicated developers are rare, and evern more so in the opensource world.

[/rant off]

If I can help in any way, please me (us) know, I really feel like a donation button/shortcut wouldnā€™t hurt!

M

Hello,
I think that a badge (without the strip: unit of measurement, ā€˜homeā€™, ā€˜not homeā€™, etc) and another type of outline could do the job as button.
It will be nice the possibility to choose the row (exmaple: row 0 for info, row 1 for scripts) and the possibility to insert inside a group.
I think that script/sence badge/circle itā€™s pretty cool: larger click area, nice photo, less space in UI (various badges in a row).
+1 for color coding in badges
Any more thoughts about in the past months?