2025.4 Beta Week

one more feedback, and already briefly discussed in Discord:
Personally, I like the new breadcrumbs in the more-info panels. A lot. Especially now they’ve evolved to being clickable, providing a direct path to the entities Device, integration and Area.

However, in our usecase, this is not info I want to show to my family or other users/guests (all my entities are clear as to what they stand for, and I dont have 20 doors called Door…) under all circumstances.

I believe this info should be better positioned under a separate and single tab on the more-info (like we have icons there now for the Settings (cogwheel) and Menu (meatballs) ). Maybe just add an Info (mdi:information) and clean up all of the current more-info tabs.

Myself, I hide the breadcrumb conditionally with an input_boolean and a card-mod theming setting

  card-mod-more-info-yaml: |
    ha-dialog-header: |
      .breadcrumb {
        {% if is_state('input_boolean.hide_more_info_breadcrumb','on') %}
        display: none !important
        {% endif %};
      }

to allow it to show only when in dev mode, or require administrating the instance.

so it brings back the quieter and only essential info that is actually required for the end-user:

I hope the team will reconsider overpopulating all of the current more-info panels on an item, and make the interface less cluttered.

O and please dont ‘sprinkle’ all of this info everywhere in the UI.

When viewing the details of an entity in the entity dialog, we now provide more context about where the entity is originating from. Like its device and the area it is in. This is a first step in sprinkling more context throughout our UI. Thanks, @piitaya!

as is stated in the release notes

or make it opt-in/conditional.
We dont all want our interfaces show this ‘backend’ info in the frontend unconditionally without a choice.

I mean, why would my daughter checking the weather temp need to know which integration is providing the entity, or which automation uses this entity.

Clean up, dont Clutter…

9 Likes

Totally agree. Wonderful option… just make it optional!

1 Like

Mine also stops. Not slow. Not 5,000 entities. 1,780.

2 Likes

Are you talking about the new area dashboard, or the old autogenerated dashboard? Because Nathan is not participating in the beta. He is basing his comments on fear, not fact. If anything, his comments show why the new generated area dashboard is sorely needed.

The new dashboard targets very specific entities such as lights, covers, media players. Only a few sensors. It does not dump every sensor on earth in the dashboard the way the old one does. So what comes out is much more modest and useful. And it is configurable.

For me the old autogenerated dashboard is also completely unusable, but the new beta one is quite nice. I have an instance with 6200 entities. If I would dare to guess less than 5% of that ended up on the dashboard.

1 Like

And why I asked how it worked.|

Now that I know you need to put it in intentionally. That’s fantastic and how new features SHOULD be put in. I don’t have to worry about accident-ing across it - I’m fine. :wink: (Which was my initial concern - new cool auto feature that when loading a URL BOOM

… And pretty much what happens with the current autodash for me - I learned very early to just avoid that whole area. :slight_smile:

I mean I’d never use it because E you’re right I’m not the intended user, but yeah my kid - starting out in HA has two maybe three rooms and a half dozen bulbs - I can TOTALLY see this helping them get started. I like this one.

2 Likes

AND WE’VE REACHED THE END!

2025.4 is now released. Please head to the release blog thread to continue feedback regarding this release.

Thanks, y’all! 🫰🏻