product-and-ux

[noble geode]

Good day all 👋🏻

I guess a small introduction is in order for this channel.
My name is JLo, i'm the lead of Product and UX at the OHF, my team is responsible of the success of every products the foundation governs, Home Assistant being one of them.

As this is a Home Assistant server, let's focus on Home Assistant ☺️

Product areas

The team is composed for 4 product areas
These are independent structures to create value, led by a product manager and a UX designer.

Here they are, this structure is not really important for everyone, but at least you know the name, and the people working hard to make Home Assistant more user friendly and ultimately more successful.

🎨 Interactions & Touchpoints

Product Manager: @umbral minnow
UX Designer: @lethal linden

Mission: We help you interact with your smart home

Scope:

• Dashboard (Including the Home Page)
• Voice
• Notifications

🧠 Automation & Intelligence

Product Manager: @civic elm
UX Designer: @woeful plover

Mission: We empower you to automate your home

Scope:

• Automations
• Scripts
• Blueprints
• AI Tasks
• Suggestions
• Predictions

🔌 Integration & Open Protocols

Product Manager: @opal wyvern
UX Designer: @wet terrace

Mission: We help you add devices & services to your home

Scope:

• Devices & Services
• Open protocols
• Information architecture (Where devices are and what they do)
• Device types, device database (And How the data flows out of Home Assistant)

🌍 Set-up & Extend

Product Manager: @placid belfry
UX Designer: @manic crest

Mission: We help you set up and extend your system

Scope:

• OS installers
• Onboarding
• Backup & Restore
• HACS & Apps

(I removed a few things that are outside of Home Assistant itself as these teams also work across multiple products)

UX Research

Alongside the 4 areas, @dusk scaffold , our UX researcher is helping us get a better understanding of our community, uncover needs, prioritise problems, and overall making sure our time is spent where it matters the most.

🗺️ Roadmap

Right now, we are working hard on making our roadmap much more transparent and visible to everyone willing to participate.
It is available here
It's a work in progress but I do not mind sharing it there for you to comment on available opportunities if you want.

🎯 Goal of this particular channel

This channel is not going to be used to sync activities on what is happening right now.
We are going to work on related project channels alongside everyone building

I am not entirely sure how this channel will be used, I think each product area will be able to use this channel in order to communicate bigger vision and mission and status of what is currently in the pipe ☺️
Let's see how it evolves !

🔥 What we are currently working on, and where?

With that small introduction out of the way, whenever time permit, each product area could explain a bit what their focus is right now, and mostly where it's happening so that interested people can jump in 🙂

I can start with Automation & Intelligence as @civic elm is ramping up and taking over from me.

We're currently focusing on creating new purpose specific triggers and conditions.
The whole vision is available here
And we are currently working there : https://discord.com/channels/330944238910963714/1351529028112224359

Feel free to join the discussion!

[umbral minnow]

and 👏🏻 we 👏🏻 can 👏🏻 make 👏🏻 threads 👏🏻 here👏🏻

[woeful plover]

Yes 👏 and hello 👋

[digital brook]

Is this supposed to be read-only?

[proven frigate]

Only for people without Developer/Designer role.

[gaunt flume]

Great initiative! Really looking forward to seeing what this channel evolves into. UX is the bellwether for great, long-lived (long-loved?) software, and it's great to see HA / OHF embrace this.

btw, as a liittle bit of belated appreciation: the ctrl-K command palette is AMAZING

[keen ferry]

My people ...

My thoughts on the roadmap are that I think the focus should be more on building the design system and improving the documentation right now, because without a foundational language, every piece communicates in a different way. I hear that the expanse that is the design guidelines will be addressed (🙌) but I think that the guidelines would better compliment a new design system instead, than for developers to work on and implement upon what currently exists. I am excited to see the OHF move forward with improving the UX like this though! 😋 I would love to help in any way I can, and I cannot wait for Home Assistant to build on and improve the standards for open source. ❤️

[trim pagoda]

I want to get some attention to the vacuum segments UX #1346947552905531504 message

I think that we should have some default mapping that we go with in the backend without user intervention. Just best effort string matching. Worst case we do an incorrect match, we clean the wrong room? 🤷‍♂️

The copy and experience around the mapping of segments dialog is also suboptimal

See my link above for some feedback that I want to see addressed

[wet terrace]

Agreed, and we have discussed this. I see that Artur [replied](#1346947552905531504 message), that it was not picked up yet.

[trim pagoda]

Right, but the actual repair issue should not exist. We are discussing it here and I would love to see UX join https://discord.com/channels/330944238910963714/1476555716998332557

[keen ferry]

Improving the "Apps" Experience

[sour dust]

Hello,

with the release 2026.3 we are able to test frontend PRs within all home assistant instances via a configuration.yaml setting. Checkout the documentation here on how to set it up: https://developers.home-assistant.io/docs/frontend/development#test-an-existing-pr

And please don't forget to remove it again after your tests 🙂

If you have any question reach out to me.

[dapper monolith]

Can we get some input here please? #1476855515375206554 message

[dry apex]

I didn't realize how much I missed this.

[trim pagoda]

This is cool: "I built a self-learning climate control integration — RoomMind is now public" https://www.reddit.com/gallery/1ri824n

[strange pilot]

you're doing a music collection app too? 😉

[low stag]

how can one show their willingness to contribute design skills to be considered for the designers role?

[wet terrace]

If you want to help with design, start by checking the UX design activities board. If something looks interesting, comment on it or assign it to yourself.

You can also join the UX discussions to share ideas, feedback, or research. For quick chats, this channel in Discord works best.

Just start contributing. That’s the easiest way to show your interest and design skills.

(We’re currently working on improving documentation and processes in the UX design repository so it becomes clearer how designers can contribute)

[low stag]

Can we pin this message to the channel @bold oak 🙂

[bold oak]

Do you want the OHF role on this account while you're traveling? XD

[low stag]

haha yeah that could be useful.

although it's nice an d quiet 😅

[bold oak]

You have most mod powers with this role now. 😄

[bold oak]

Time to MUTE ALL THE THINGS

😂

[gaunt flume]

the only way to discord honestly

[wet terrace]

💡

I opened a UX discussion about the Overview page and how it currently mixes favorites with suggested entities. The proposal is to let users pick favorites or suggestions.

Would love to hear your opinions!

cc @umbral minnow @lethal linden @modern torrent

[gaunt flume]

left my two cents ❤️

enjoy my shitty mockups, a.k.a. @keen ferry -bait lol

[keen ferry]

https://tenor.com/view/lyxocx-lux-seal-screaming-seal-banana-seal-gif-14113207705912223170

The way that Google does it is interesting

Mind you, it's definitely not the best

[umbral minnow]

Bookmarked it for today! We wanted that too tbh but didn’t find a design tool that was satisfying. So super hyped to read the discussion and see options

[civic elm]

FWIW I really like Tobias' suggestion 🙃

[noble geode]

@woeful plover , @civic elm
Do you mind having a look at this PR when you have a minute?

https://github.com/home-assistant/frontend/pull/29906

[civic elm]

Allow trace graph to scroll independentl...

[keen ferry]

https://github.com/OpenHomeFoundation/ux-design/discussions/17#discussioncomment-16083861
Shared my thoughts on the UX for suggestions and favourites

[wet terrace]

Matt is on PTO right now. I’ll wait for his input, as he’s working on the Overview page.

[wet terrace]

@jolly python, do you remember why we have these buttons in the network visualization? I have a suggestion:

• We usually place the refresh button in the toolbar at the top right. Lets make that consistent.
• I wonder why a user would want to hide the labels. I think we can remove that option.
• That would leave only the Toggle physics button, and I would prefer to make that a real toggle instead.

What do you think?

[jolly python]

• The refresh is actually not a normal refresh but it sends a command to the controller to "explore" the network topology again. And it is sort of async. It can take a few seconds or more to do this. In my experience it does nothing 😄 tbh
• Hiding the labels is very useful for large networks with a lot of nodes. Lets you focus on the connections and states. Then only look at specific labels by hovering.

We can move the "refresh" and labels to a an overflow menu in the toolbar. This way they can have text so it's easier to understand them

[wet terrace]

I like that!

[wet terrace]

Just started this UX discussion based on the "Make more info adaptive bottom sheet height match tallest more info dialog" PR.

Would love to hear your opinions!

[keen ferry]

Could use this icon instead for that, then

[tiny root]

Anyone have the latest HA Design Kit components file for Figma?

[wet terrace]

@woeful plover has a great one that’s currently a work in progress. I stopped working on mine after that.

[wet terrace]

Home Assistant can also work well with simple wireframes. Would that be an option for you?

[tiny root]

Feel as though wireframes won’t give a clear visual representation of design mockups if I’m honest

[woeful plover]

To give a liiitle more context why this is not available ... Yes, the Home Assistant Figma UI kit is undergoing significant changes in various aspects. With the recent introduction of agentic vibe-coding, Figma published component slots, and the OHF branding team evaluating HA branding. Additionally, the front-end team is migrating components on a monthly basis. These factors create a lot of uncertainties, making it challenging to establish a reliable source of truth for anyone interested in designing for Home Assistant at the moment.

That said, all of these things I just mentioned are progressing

[tiny root]

It’s understandable, but I believe the design system should have been ready from the start before any transitional changes were made. This would have also prevented these situations. Having said that, I’ll see what I can work with for now

[keen ferry]

There's not much to work with yet, you'll basically have to just work with what you can find and cobble together

But rest assured, as soon as they're ready to press the gas on the DS, I'm leaping onto it 😂

[modern creek]

Since I once again came across the lengthy (if you have a lot of blueprints) dialog for creating automations/scripts, I started to improve it. For now, I’ve added a search and moved it to the bottom sheet on mobile. Any ideas to improve this maybe further?

[low stag]

Maybe it should be more like dashboards. We have two options, create from scratch and use blueprint. In future we can add AI. Having a dedicated blueprint dialoog might also offer us to explain what it is and where to find more

[civic elm]

Automation creation dialog

[wet terrace]

Big shoutout to @desert anvil⭐️
Amazing work on the camera dialog.

For all designers out there, feel free to join the conversation on the UX GitHub repository.

[umbral minnow]

Cross posting here, in case anyone here knows someone https://community.home-assistant.io/t/research-study-help-wanted-quick-call/996552

[reef cloud]

Was discussing https://github.com/home-assistant/frontend/pull/29908 (adding search to the visualization graphs) with @wet terrace
We could move the search bar to the top bar instead of floating, like we do for most pages. But on desktop, the search bar is not on the top bar.

[strange pilot]

dont know if this is the right place to post/ask, but would it be possible to animate/circle the refresh button for updates while looking for updates. Now you'd have to wait for the message updates found or not.

[dapper monolith]

Experimenting with popover support for adaptive dialog (this would only show on desktops)

Not at all final, it would only really work if we made settings, details etc show in their own dialog on top as the interactions should only really be on one view.

Another idea would be to make this popover variant more of a "mini" more info and have the fully fledged dialog/bottom sheet show when triggered by either one button or the current header actions as we have them now

[noble geode]

Random idea while looking at our more info for entities.
This is our current warning dialog when you delete an entity (Screenshot 1)

But 2 clicks away from this, we have a nice list of things that will definitely break if you delete it, the releated screen (Screenshot2)

Could be worth surfacing this info while you're trying to remove the entitiy.

Not the full list, maybe just a mention "BE carreful this entity is part of 62 automations, and 5 dashboards"

[wet terrace]

Random idea while looking at our more

[low stag]

For curtains, you don't tend to set position, but instead Open and close is important. Do we know why we have it act like tabs? Can't we put the three buttons below instead of having two tab buttons ? With lights we also have scene actions and on/off button

[low stag]

Was playing with an idea to see if notifications can be merged into profile.

[reef cloud]

We should allow specifying hours in the range selector of the energy dashboard (maybe hidden by default, to keep it simple). That would allow for checking the energy distribution at night, for example.

[trim pagoda]

I feel like the positioning of features is shown more prominently than adding features 😅

[gaunt flume]

yeah this has caught me out a couple times

[umbral minnow]

Yup. Already coming out of my current research - as soon as I finish interviews I will share the outcomes so we can see together the issues and biases. But yea, that screen in general needs better hierarchy

[trim pagoda]

I think a quick win could be to just move the add feature button above it

[gaunt flume]

a very quick win is to hide the features position picker unless you actually have a feature added

[umbral minnow]

yeah, I want to look like 5min at this screen at least, because its not just repositioning, its the fact that "add feature" is missed even pointed out

[civic elm]

Isn't the entire section collapsed by default?

[umbral minnow]

Yes, and once opened there is a true blindness towards "add feature"

[trim pagoda]

Features editor

[bold oak]

Project threads migrating to text channels

[strange pilot]

Possible to highlight the settings/notifications in sidebar a bit? underscore, bold,color, at least a bit different then the rest of the sidebar? 😉

[gaunt flume]

Possible to highlight the settings/

[uneven oar]

I said this before, and I'll say it again: HA would tremendously be better (UX-wise) if (part of the UI) would be made with the steps to take in mind. Like a stepper UI componount does.
It breaks a big UI into logical pieces, makes a path and guides the user through it, to get the final result 100% done.

[gaunt flume]

you mean like a wizard?

a guided "do this, then that" kinda thing?

[uneven oar]

Yes, sort of...

The updater/installer/"reboot or clear cache" dialog would benefit mostly from such a thing as an example. But the whole UI/UX would be more logical and easier to grasp when you force the path to result, instead of a lists of options.

Have a look here: https://www.eleken.co/blog-posts/stepper-ui-examples
All the specific components are already inside HA. They just(tm) need to be used like that

[gaunt flume]

32 Stepper UI Examples and What Makes Th...

[forest cove]

Posting this here as well

[civic elm]

Would like to get some more eyes on this: https://github.com/home-assistant/architecture/discussions/1359. A seemingly small proposed change to counters that I was tagged in because we recently dealt with them in the automation triggers project, but I'm not sure this is fully in my domain and also I don't have a strong preference for either of the two posed solutions.

Backup errors

[trim pagoda]

I noticed that for media player more info, we know the active input source, but we only show it when the user clicks on the "input source" icon. Seems odd, as it's for a receiver a very important thing. I wonder if we should show the input source as song metadata when there is no track info?

or maybe a different UI for different device classes, we know if it's TV, Receiver, Speaker

[proven frigate]

If the app/app store UI is getting a rework, might it be an idea to remove the autoupdate option? It would reduce unexpected changes during unrecognized updates and nowadays we get much better notifications about available ones anyway.

[modern nexus]

People would riot again

Even though I don't even know if it works. I have it enabled on one app but I still get notifications for updates

[wet terrace]

Ooh, I like that!

[wet terrace]

From what I get talking to different people. App developers hate them for the extra support it causes. App users love them as they think it is set and forget.

If we would change this, we should do a bit more research on it. As its more than just the UI.

We do have the app update backup nowdays that is a solution to a problem I would say.

[trim pagoda]

If we can differentiate between major and patch versions that would help

Semver allows app devs indicate if it's a breaking change

Or just a flag somewhere saying it's incompatible

[austere flint]

The main reason I still use the 3rd party mini media player card is that it allows me quick adjustment of my amp's power state, volume and source without having to open the pop-up. Maybe consider adding the source select as a tile feature and to the media player card? Compare:

[dapper monolith]

Sound mode / Source dropdown feature

[modern nexus]

While we are on the topic of media Players. What about merging media players in the UI? We can do it in YAML but that's not an easy task. I'd see it as a big improvement. Example: My Sony TV has all the I/O and Input options while AndroidTV or Jellyfin provide actual context of the media being played. I have to keep using 2-3 devices to actually see and control my TV. Same goes for some receiver/soundbar setups.

If you could define a virtual media player that picks the data automagicly from the device where others are missing info it would be perfect.

[dapper pebble]

Agreed. I read somewhere that was the plan, whilst phasing out the ‘Universal Media player’. Though, I haven’t heard much about it since

[trim pagoda]

Make a proposal 👌

I would expect a frontend only solution to be able to work, a stack one can browse through, that automatically surfaces active player

Or we let all media players go through music Assistant, which automatically does the merging nowadays

[opal wyvern]

Credential management - Next up Z-Wave locks

[civic elm]

Area-related suggestions

[dapper pebble]

I really like this idea. @modern nexus did you manage to create a proposal?

[modern nexus]

Got some notes, I've got a few days off now and will put it onto final form

[thorn wagon]

On the onboarding page, I think the restore backup experience could be improved slightly. Specifically errors like this, "must update supervisor first", for an end user, there is a call to action there, yet no easy way to actually perform that action without dropping into the CLI.

[long dragon]

i never noticed how off center the volume slider looks, it makes me feel uncomfortable haha

[trim pagoda]

Should we ask this user to contribute this to core? https://github.com/luuquangvu/blueprints-updater cc @topaz edge

Did not check code, just read features

[civic elm]

Should we ask this user to contribute

[dapper monolith]

Posting here before making it an actual change:

Thoughts on this small design update to settings dashboard? Reusing the card headings with the links to all, removing the show all buttons. Not sure if the sections below need headings or not (or extra spacing to seperate them) with this

[noble geode]

Well hello there 👋

Yesterday during the State of the Open Home 2026 we annouced our public roadmap 😊

🗺️ You can find it here
We shared our direction, our approachability goal, and a 2-month plan. (The building column of the roadmap)
The roadmap will be updated every 2 months now.

I made a small write up of our commitment for this first 2-month cycle and you can read it here
I will make statuses just like this one every 2 months to give you transparency on what we did on the ending cycle and what we're planning to do on starting cycle

Please participate in the discussion by commenting on every issues you find interesting in the roadmap!

• Considering section is what we are considering to build, but usually, we haven't started researching what to build
• Shaping section is what we want to build, and we're actively researching the best possible solution. I'd say this is where everyone's voice is most important
• Building section is the famous 2-month plan

In case you feel we are missing something, the best way to propose something is to make a feature request (We read them all).
As this is a Home Assistant Discord server: This is the link to our feature requests

Have a great day! And see you on the issues of the roadmap!

JLo

[wet terrace]

My fellow designers!

Do you also think our cover "more info" dialogs can be better?

Looking for some help redesigning the cover "more info" screen. The current upside-down slider only works for some devices and can be confusing on others.

Task: design the next version of the dialog across device classes

Motionblinds shared some screenshots for inspiration. And they look really nice!

Interested? Let me know.

[woeful plover]

👉 I want to talk about showing dismissible tips in HA -> in the effort to make some places of HA more approachable and understandable which is a roadmap goal for '26.
Recently, we've added a dismissible blue-banner tip on the home dashboard to help migrate users. This is a temporary solution that will be removed from code, but we could use this as a precedent to implement more banner-like tips in different places of HA. That said, since it will be dismissible, there should be a way to bring it back, so the idea is to also add a "Reset onboarding tips" to the User settings panel.

[wet terrace]

🧵 Quick question about how you manually control your vacuum.

When you manually start a clean, do you usually:

• just hit start and let it clean the whole area
• or do you pick specific rooms/zones most of the time

[modern nexus]

I've used a "reset toasts feature" in the past in Adobe products but I hated it everytime because it would reset all hints/tips not just the ones i wanted to see (e.g. after an update) So I'd suggest if you implement something like this give the user an option which ones should be resetting.

[woeful plover]

That's a valid point and yes, targeted reset of onboarding tips is something that I also thought about, but might complicate implementation

[bitter nymph]

👋 I was testing something completly different and end up into the bottom sheet to search an entity. I think the height of the search is way too small especially on mobile. Is that on purpose?

How am I suppose to click on that tiny text field

Also I think we are lacking some marging there no?

(arround the handle especially)

[woeful plover]

It's a placeholder input, because a proposed input design was postponed from implementation by JLo. So Wendelin added the smaller data-table search since it looked better than our MD style ones.

[bitter nymph]

Sure but can we not take the smaller? I can make the PR if we agree

[bitter nymph]

40px instead of 32px looks more raisonable don't you think?

[midnight flint]

not really sure where this goes or what to do about it, but here we go: profile > advanced mode: the learn more link does not give me any more information what these advanced features are, neither do i see any visible immediate change when activating it. the link goes to this one paragraph in a release note with no info at all.

[wet terrace]

Makes sense to me, but I'll let @woeful plover decide

[wet terrace]

Oke lol. The bigger fix we are working on is to remove this advanced mode toggle.

[dapper monolith]

Yeah theres already been a large effort already to remove these. We should task out the remaining items btw

[bitter nymph]

@woeful plover if you can have a look to https://github.com/home-assistant/frontend/pull/51576

(especially the screenshots)

[woeful plover]

Yup, go ahead!

Thanks Timo

[midnight flint]

i was fairly confused that i can not change my profile picture on the profile page. would that be a good issue for the ux board?

[woeful plover]

Yea it's a feature we'd need to design for and post as a task for somebody to pickup from the community

I'll try to do this!

[trim pagoda]

Probably needs a core change to make profile picture change accessible to non admins if it's their own picture

[keen ferry]

thats uh.. that isn't possible right now? im kind of surprised

[trim pagoda]

ah looks like the backend works for setting avatar

[hardy plank]

#1494698774004498643 message

[proven frigate]

That sounds like something for #1284966353798697001

[opal wyvern]

Hi everyone,
wanted to share some ideas on ongoing activities and ideas around infrared and radio-frequency proxying/support in HA.

As infrared never left the chat (see HA release 2026.4) we not only think about continuing there but also about how radio-frequency would add to the equation - all in-line with our efforts on sustainability and further shaping our protocols support.

For both ideas I wanted to share these 2 links for the ongoing discussions around them for everyone interested to chime in:

• Infrared (IR): https://github.com/OpenHomeFoundation/roadmap/issues/101
• Radio-frequency (RF): https://github.com/OpenHomeFoundation/roadmap/issues/102

Will also x-post to the projects channel.

[woeful plover]

Re: Color contrast of surfaces in the general UI
Recently I've submitted a PR that cleanup the tooltip that we have on the sidebar and app-bar (among other places). For that I needed to introduce new surface color tokens. As an additional change of that some of the surface colors of the general UI have changed.
The main reasoning is to introduce more contrast between dashboard and sub-view (settings) elements, since I do believe currently we have too low of a contrast between card elements and their backgrounds that might hinder some users with vision imparment, or be even problematic for regular users on displays that do not render shades of gray that well. This also opens up the possibility of us removing borders on cards to make the UI cleaner.

[woeful plover]

@wet terrace we recently updated the switch/toggle component look (and code). This has surfaced a opportunity for the Entities card which currently uses the same switch on dashboards, to switch it (🥁) to the Tile card switch feature component seen here. This would look like in the screenshot below. Now with all of this said, this change would also change how a switch is rendered in a device page, which currently still heavily uses "general" ui components (and is due for a redesign).
Now... while @lethal linden could do a redesigned entities card in the future, whats your take on reusing the Tile card "switch" component in the current device page ? And would it be aligned with any ideas for the future device page ?

[wet terrace]

@Matthias we recently updated the [

[opal wyvern]

Like infrared never left the chat (see HA release 2026.4) - so didn't serial proxying 🙂

In the ongoing efforts to make serial proxying become a first class citizen in Home Assistant and make it more approachable by everyone to use and build upon (https://github.com/OpenHomeFoundation/roadmap/issues/77) there's a first demo available by @trim pagoda

It shows the integration leveraging the new serial port selector to pick an ESPHome powered serial proxy.
And as a bonus it also shows the serial list automatically update when USB is plugged in. At the end of the video a manual volume change by rotating the knob on the physical device is instantly represented in HA.

Nice! 👏

While some more UI polishing is ongoing the framework to build upon is available. Thanks!

[bitter nymph]

We have a contributor that is working on a feature to preserve the path of where the user is while using the mobile app and changing URL (internal/external so basically coming/leaving home). While working on that he end up into a weird case where the history is empty but he might not be in the Overview dashboard (the user could be in the settings for instance). Is proposal is to synthetically add to the back history a back to the default dashboard.

But this could create maybe a strange behavior when using shortcuts for instance.

@south cargo did a good job by providing recording of the behavior https://github.com/home-assistant/android/pull/6447#issuecomment-4291455339 I would like to take the temperature on this idea here 🙏

[umbral minnow]

We have a contributor that is working on

[dapper pebble]

With the new background sections, I’ve noticed an accessibility issue. When the section background is set to a light colour at full opacity, header text with a light font theme becomes unreadable. Likewise, when the background is dark and the font theme is also dark, the header is not visible.

There are a few possible solutions here that wouldn’t compromise the styling:

• Add an option to customise the font colour for the Heading card.
• Use ‎mix-blend-mode (or a similar) so the primary-text maintains sufficient contrast against the background.
• Make the background and text colours themeable rather than hard-coded css. (though not for everyone).
• Add option to move the heading card out of the background colour.

Thoughts? Wanted to see which option is more viable, before creating and issues/pr's on it.

[opal wyvern]

Hi everyone,

[umbral minnow]

Hey hello! Just for FYI and some insights - there are a lot of cool updates coming up to the Overview page, in terms of more flexibility:

• New Mantainance dashboard! first version with battery levels
• Now you can hide Summaries in the sidebar - no more "Security things are just one click away"
• Added a cool new section for manual shortcuts 👏🏻 you can select any link, navigation or dashboard, and make it a Summary in your Overview page

Much more to come, but thanks for these amazing contributions 👏🏻

Aaaaand this amazing shortcut card can also be used in your custom dashboards 🔥 No more hacking into cards to remove the entity

[modern torrent]

Added the possibility to use attribute condition in dashboard (similar to automation condition). https://github.com/home-assistant/frontend/pull/51706
Link of the FR : https://github.com/orgs/home-assistant/discussions/668

type: tile
entity: sun.sun
visibility:
  - condition: state
    entity: sun.sun
    attribute: rising
    state: "true"

[umbral minnow]

hehehe @mossy rivet hehehhe

[dapper pebble]

Section Background: Accessibility

[modern torrent]

Another improvement for card conditions : It will now use the entity configured in the card/badge by default. https://github.com/home-assistant/frontend/pull/51708

[mossy rivet]

yep.... sorry for keeping bugging there 😉 and thx @modern torrent for picking it up, it will be a very appreciated addition indeed!

[gaunt flume]

smoooooth

[trim pagoda]

Someone please make an opportunity for Android settings cleanup and allow splitting up what is shared per server 🙏

[trim pagoda]

At our hackerspace we run HA. Everyone ends up sharing a bunch of sensors without knowing

No one understands our ui

[opal wyvern]

Like infrared never left the chat (see

[opaque narwhal]

https://github.com/OpenHomeFoundation/roadmap/issues/113 is proposing reorganisation of the card editor. I find the initiative very positive and made a few comments on the proposition. I would be happy to have them commented or criticised. I am pretty sure the subject is an important one and not just a simple reorder... The subject is in between ux and front-end...

[wet terrace]

Design help wanted: improve "more info" dialog for covers

The current interaction (upside-down slider) is inconsistent across devices and confusing for users. We need a clearer, more robust pattern that works on mobile, tablet, and desktop.

What we need:

• a redesigned "more info" dialog
• works across device classes
• simple interaction model
• optional: motion/transition ideas

Context and current designs:
https://github.com/OpenHomeFoundation/ux-design/issues/29

*If you’ve got 30–60 minutes to sketch something, that would already help a lot! *

I’ll review and move things forward quickly.

[mossy rivet]

Hi Paul, forgot to ask before, but this also works in a type: conditional ? (So cards not supporting visibility can be shown conditionally)

[modern torrent]

Yes, card conditions are the same. However, all cards support visibility.

[mossy rivet]

Thinking custom for a minute there … 😉

[opaque narwhal]

This will really be a game changer... For ex for error codes...
Thanks a lot!

[mossy rivet]

does it help to point at Tahoma/Somfy? their representation is very clear and cant confuse. If you want I can post screenshot

[wet terrace]

Yes, the more inspiration the better.

[mossy rivet]

The image at the top changes according to the slider real time

IKEA does this, also real time, with an actual product image

For comparison, this is what Google does with that same screen. Personally I find those controls way to ‘fat’

[modern torrent]

I did some experiments with claude design. (just research/discovery/inspiration)

Didn't know ikea was doing the same : illustration + slider

[opal wyvern]

@modern torrent Very nice and slick!

Did you by any chance also come across tilting and/or combining that with raising and lowering?

[noble geode]

Cross posting here, we just had our kick off of how to integrate AI in Home Assistant to manage the smart home, in comparison of controlling the smart home (Where Assist already shines)

You can read more here: #1346946515511279696 message

Make sure you follow this (👆🏻) discord channel in case you want to be part of the discussion !

JLo!

[civic elm]

Hi everyone! Good things are happening with automations and AI in Home Assistant (which we refer to as Intelligence), here's a quick rundown:

• Purpose-specific triggers and conditions are almost complete 🎉! In 2026.5, we'll finally ship support for durations (meaning you can trigger when a light has been on for a period of time, for example). We'll also have shipped, let's say, 99% of all the triggers and conditions we set out to add. We're on track to finish this project by the end of the current two-month cycle (marked by the 2026.6 release) and that's huge news I'm really stoked about! If there's anything you're missing still or that's not working, join the conversation here: https://discord.com/channels/330944238910963714/1351529028112224359.
• We've wrapped up the designs and created tasks for bringing home context into the automation editor. If anyone wants to read more, the what and why is here. If you'd like to jump into the development, all the tasks are free to pick up here.
• AI in Home Assistant is taking shape. Slowly, but still. We kicked this topic off yesterday with OHF members as well as community members. We'd love for more people to get involved here: #1346946515511279696 message.

[lethal linden]

Design help wanted -

Goal
Add a battery state-of-charge indicator, displayed as a percentage, to the Home Assistant energy dashboard.

Why though?
The dashboard shows energy moving to and from the battery but not what's actually in it.

That number changes the meaning of everything else on the screen.

Figma file to work from
https://www.figma.com/design/LYd6pa4zraTYqdSEno7z8W/Battery-state---Energy--3377?node-id=0-1&t=pn9dvbAsa9n3jn7Q-1

Needed artefacts

• Visual design of the location
• What is shown
• Are there other states involved? A charging and discharging indicator, an error etc...

Original request
https://github.com/orgs/home-assistant/discussions/3377

[trim pagoda]

Battery state in energy dashboard

[frigid crane]

Hello! Let me know if this isn’t the right place, but I wanted to raise that the new repairs and updates design feels too subtle. At a glance, I can’t immediately tell that there are more repairs than the two visible. I think even a little “…” underneath the second repair would be a signifier enough (and for later improvements, if tapping that would then expand out to show all the repairs )

[opal wyvern]

Hi everyone 👋

Cross-posting here to let you know of some general updates on the Device Database.

You can read more here #1361754948949512203 and be part of the discussion 🙂

Thanks

[trim pagoda]

It's very hard to add a time based automation today. Add trigger, by type, huge list and scroll all the way down to time

Seems odd. I would expect its a very common trigger !

Actions make it hard to find scenes unless added to an area

[civic elm]

Time triggers

[icy hill]

I'm not sure where the best location would be but since i consider this a UX factor, i'll throw it in here.
I've been thinking about automations, automation groups, and helpers. Quite often i have automations that go together, several automations that work together to implement a single features. Sometimes i'll end up condensing them into a single automation and use trigger IDs to differentiate, sometimes i'll put them in separate automations. either way, i'll have helper entities to either keep state for longer time and across HA restarts, or for example to configure aspects of those automations.
But doing so means i have some automations, some helpers, all spread out across home assistant. when working on those automations, i end up with several browser windows/tabs open, orchestrating between them. And then one day you no longer need the automation, but forget to get rid of the helpers, giving you orphan entities. You might work with some sort of naming scheme to keep things together, but its all just based on remembering to do things right. We do have automation groups, but those are only for visual organization in the various menus.

So being a software engineer by profession, i've been wondering why we dont use the concept of modules/packages/namespaces in HA, grouping a number of automations and helpers into modules. The entities could keep state for those automations, and still be used like any other entities.

Let me give an example: Time-dependant light controls. In my bathroom, during the day the lights should turn on to a bright neutral color, during the night i want dim, warm light. For this i have a time helper that defines when "night" starts (yes i know, i could use dusk+x for this). In the automation, i check if now is after the helpers time. The helper is only ever relevant in the context of the automation. But i have it on a dashboard to be able to comfortably change it.

Another example: I have a few automations for my robotic lawn mower. Because i dont run it every single day, and i dont like running it in the rain, i have a few helpers for "when did it run last" and "its paused until X" etc. And i have four different automations, that all belong together and will often use those shared helper entities.
It would be cool if i could see the shared helper entities in the same automation editor, maybe simply in a section like the conditions, or in the sidebar or something like that. just not all the way in a completely different part of the HA ui.

Reading up in this channel, i think "Bringing home context into the automation editor" from here #product-and-ux message already goes into a similar direction. My idea is to go one step further and not just show the entities and their state, but actually bind them together.
i dont know if this makes sense, it does in my head 😄

just something that i noticed in my setup here, something that bothered me. or maybe not even bothered, but an area where i think there could be more organization for somethign that currently can easily get a bit cluttered

[umbral minnow]

Sharing here something in beta because its ✨ if you don't have experience handling notifications, and even the simplest ones are a headache, now you can make simple text notifications by targetting the device with the HA app, since its an entity. It was part of the Migrate the mobile_app to the notify platform roadmap opportunity, and massively happy it got picked (thanks @bitter nymph @mild haven and @bleak jackal )

I know its limited - there is a lot to walk down this road - but for users not versed in how notifications work, just this means a huge step into approachability. Thanks and let's get it even better 💪🏻

Now if you'll excuse me, I'll be creating 300 automations today 🤣

[mild haven]

“This” as notify target

[civic elm]

Automation helpers

[bitter nymph]

New tag hide custom tag ID

[dapper monolith]

Quick opinion wanted on the look of this skeleton for graphs: https://github.com/home-assistant/frontend/pull/51882

[trim pagoda]

People loving the interactions with product to get things changed in HA https://bsky.app/profile/sebadeep.bsky.social/post/3ml63fpv4cs2l

SΞБΛSTłΛ́Л (@sebadeep.bsky.social)

Three months from conception to merge, I've had my first idea baked into @home-assistant.io 🥳 It's a small addition and I didn't code it, but it's still a great feeling to contribute to an amazing project. Closed by the main man himself @paulusschoutsen.nl credit to the Devs for getting in so fast!

Bluesky · May 6, 2026, 6:33 AM

[sour dust]

Automation UI comments 🧵

[mild haven]

Is this row highlight intentional? It looks like accessibility features are activated, not common to see this in other apps.

[civic elm]

Row highlight

[undone flame]

@bold oak I'm a product designer with over 15 years of experience (https://www.linkedin.com/in/andrei-raileanu/) working on complex, user-facing interfaces. I've been a Home Assistant user for a while now and I genuinely love what the project is about.

That said, I've been thinking a lot about the dashboard UI and how much potential it has to feel more modern. I want to be clear, this isn't me coming in to complain or be critical. I just think there's a real opportunity for a bigger overhaul here, one that makes things feel more polished and intuitive without losing any of the power and flexibility that makes Home Assistant great.

I'd love to know if there's any openness to that kind of contribution. I'm thinking holistically: visual language, component consistency, layout structure. I'm happy to start with a concept or proposal to see if it resonates with the team.

[bold oak]

Awesome!! I gave you the Designer role to join the convo in their private channel, but you can also check out the threads here in this channel and the posts in #1346914401508392980.

[void rose]

Hoping this is the right place to post. In the new security dashboard I feel there’s a need to hide some items. For example, the fact my dishwasher door is open won’t keep me awake at night! Likewise with all the doors/windows on the car, would be helpful to hide some of these. My car has several un-useful of them

Likewise in batteries maintenance. Could we hide some eg my users’ iPhones.

[wet terrace]

@Missy ✨ I'm a product designer with

[civic elm]

Hi everyone! Cross posting here as things are picking up with shaping the development of AI in Home Assistant. Please join the conversation here if you're interested! #1346946515511279696 message Thanks!

[dapper pebble]

I’m struggling to grasp the design and UX here.

• Why has the Power button been separated and icons displayed as binary? The “On” button resembles a separator, which is really confusing. The previous single button implementation was perfectly fine.
• The background for playback icons is excessively large and overlaps each other.
• Playback buttons are visible even when the device is off. They should be hidden by default.
• Album art should be a generic media button rather than a music note.

Honestly, this doesn’t align with the concept of HA being more approachable. I’m not here to complain but rather offer constructive feedback.

[wet terrace]

I’m struggling to grasp the design and

[opal wyvern]

👋 A short roadmap update as we're approaching our next 2 month cycle

Everything we're aiming to target next ties back to the same goal: making Home Assistant more approachable. Here's a selected set of themes we're thinking about focusing on, not the full picture, but some highlights.

We're shaping the software side for two upcoming hardware launches from our commercial partner Nabu Casa: Connect Proxy (serial proxying → #101) and Project Blast (IR/RF → #153), both working codenames for projects already shared publicly.

On the information architecture & visual representation front, we're generally looking at how you navigate and access your HA information: shaping base concepts, defining a shared visual design language starting with Home Assistant (#126), and restarting the Device Types conversation (#134). On RBAC and OIDC: your feedback was heard, and this is something we want to explore in this same context. Don't expect immediate results though, as this is a topic we want to approach carefully and iteratively, with you as part of the discussion.

For cameras, we're aiming to introduce Matter camera support using the existing UI (#119) alongside a first pass at general camera UI refinement (#120). This connects to the broader push to make adding Matter devices more approachable (#74), including getting OTBR + Thread 1.4 out of Beta (HA Epic #50) and improving Thread credential sharing for proper multi-admin, multi-fabric support (#91).

Finally, the OHF Device Database public website launch might be getting closer. Follow updates on #1361754948949512203 .

The current cycle wraps at the end of May, so there's still time to jump in on open targets too.

Join the discussions on the OHF roadmap and we'd love to have you involved. 🙌

(Finally, sorry for not linking the #items directly to the roadmap but space is limited here 🙂 )

[uneven oar]

Is there someone busy with working out the way text is presented/positioned throughout core? I would love to discuss the horizontal and vertical way of centering text, as it seems to be done mostly using px, instead of the correct way (rem). The later does a more proper way of vertical centering, without the 1px offset we are seeing right now throughout core, or mis-positioned centering in input text area's when using a custom font...

[wet terrace]

Is there someone busy with working out

Hoping this is the right place to post.

[umbral minnow]

Hey! Some brainstorming request, from anyone Dashboard-loving ☀️

There is a new proposal on the roadmap about building Dashboards with self-updating "sections". So instead of adding a card, you would be able to add a section with "all lights in the living room that are on".

Before we commit to it further, I want to propose build 3 sections and see how useful they are. I thought of 3 examples but they are not good...

So my question is...** which 3 ideas we could build?**

Please propose in 🧵

[wet terrace]

Just added @fathom burrow to our #designers channel. We met yesterday when he bought my Pixel Tablet, and by coincidence we started talking about Home Assistant, UX and Matter Cameras.

He has some ideas and might want to help out with some designs.

Welcome Max!

[fathom burrow]

Hey everyone 👋
Thanks Matthias for the warm welcome!

Funny coincidence indeed 😄
I’m a UX designer/developer from the Netherlands, currently working at smartphonehoesjes.nl and previously at Amac Apple Premium Partner. I’m always interested in making apps, websites and interfaces feel more polished, premium and intuitive to use. I also tinker a lot with Apple Home, Google Home and Home Assistant to push the limits of what’s possible with smart homes and Matter devices.

I’d love to help think about UX/design ideas where I can. Looking forward to seeing what everyone’s building here and hopefully contributing something useful myself 🚀

[wet terrace]

Update about the define visual design language for OHF products roadmap opportunity

Now
We have decided to re-scope the opportunity to match a more realistic approach. For this cycle of April and May we are focusing on the Home Assistant identity #124. We have planned a workshop with the Open Home Foundation leads and other stakeholders to define the Home Assistant brand personality.

This is needed before we can work on the visual design language. I hope to share more about this at the end of this month.

Next
For the next cycle of June and July, we are planning to focus on defining the visual design direction for Home Assistant #126. One of the outcomes is a visual direction document. We as OHF staff will write this, yet we need feedback from the community. We would love to hear your feedback when we have a first iteration, and we will keep iterating on it with this feedback.

This visual direction document is going to be used in translating it into foundations for Home Assistant #155. Here I see a bigger community involvement, for example in a workshop setting.

In the meantime I would like to get a clearer picture of how we can go from visual design language to frontend #127. More about that later.

[modern creek]

Hopefully this is the right channel 🙂 So I tried to make the automation/script traceing page a little less technical… What do you think? Please keep in mind that I’m not a UX designer, just a backend dev who also works on the frontend 🙈 And sorry for the mix of German and English 😄

[keen ferry]

If anything, utilising a node editor system might be pretty smart actually

Something akin to Blender

...or maybe something closer to a block editor like Scratch?

[modern creek]

Automation trace page

[gaunt flume]

node editors are cool when you wanna lower the cognitive cost of something that maps to an existing mental model. Expressing ideas in YAML or a prompt can be quite taxing, and it can get hard to spot errors, let alone know the right words.

It’s trickier when you don’t have that mental model; then the nodes don’t help you, and their visual footprint being super compact means they can’t guide you, or give affordances to help you learn. Tricky trade-off.

That said, the Blender node editor is dope 🙂

[trim pagoda]

https://lukew.com/ff/entry.asp?2152

[keen ferry]

I think a core problem with thinking that designers can be replaced by AI, is that ignores the immediate problem of how you're going to know whether or not the mockup that's built is using the best practices for user experiences

You can make mockups, but you still need somebody who can actually research, interview, and design UX to be effective (especially if you're a company looking to bring retention up on your site)

[wintry elk]

🤔

[proven frigate]

https://tenor.com/view/hello-there-gif-5677380953331354485

And...

https://tenor.com/view/obi-wan-obi-wan-kenobi-hello-there-goodbye-there-hello-gif-24946322

[frank yarrow]

I suppose you could give the AI a list of nielsen's heuristics?

[gaunt flume]

if you train AI on code that exhibits UI best practices, it will replicate (some) of those best practices. It will likely make something usable. The trick isn't the quality of the code AI writes (the newer models are better, faster, and take instructions better than half the coders I've ever met) but to value UI best practices in your work even though you're not writing any code. AI slop isn't only slop because it was made by AI; it's because of humans who don't really care about the output.

[keen ferry]

That's uh, my point haha

That blog post seems to be talking about not needing a designer for mockups, which isn't true lol

[gaunt flume]

yeah I wasn't disagreeing

but neither was the blog post. you can do fine without a designer when making mockups, all it takes is that you do the design work yourself 😇

[trim pagoda]

No the blog post is saying that everyone has a deeper understanding of the problem because everyone has used AI to make their own solution, and so the discussions can happen at a deeper level

[dusk scaffold]

I agree and disagree with the blog post - everyone CAN have the same understanding of the problem, but often I feel like only few people actually have the same understanding of a problem, others see an entirely different problem, and again other people don't even see a problem in that topic that's being discussed. The discussions do start on a deeper level because everything can happen way faster - but coming to a shared understanding of a problem space while leading the discussion quickly to a deep level is really difficult

[dapper pebble]

Got some notes, I've got a few days off

[gaunt flume]

I mean, it's almost arguable that the blog post is burying the lede: it's essentially saying that mockups aren't design, they're an exploration of the problem space. It also points out that using AI for mockups isn't replacing the designer, it's augmenting the exploration process in a way that brings more people into it, as they're not gatekept by being able to create mockups (or access to a person who can).

You can squint and say design can only happen once that space has been explored, not before.

[dusk scaffold]

true - I get your point
mockups can be an alternative way to describing the problem space instead of verbalizing the problem but illustrate a suggestion for an alternative, not the solution yet

[gaunt flume]

that’s usually how I treat them

[wet terrace]

Same!

Feel free to join as designer too!

[modern nexus]

I had to use AI once to create a mockup because I didn't have access to a program where I could do it myself. Results weren't great from a design perspective but it was easier than describing what I had in mind

Heck the mockup could be pink and green with square corners, if you're discussing how something should work you don't care at that moment

[gaunt flume]

man, I miss designing on a whiteboard 🙁

[modern nexus]

When I had Adobe on every PC in my surrounding I was somewhat elitist and shrugged at Ai mockups. Now I don't have that anymore and I can see the benefit.

[gaunt flume]

sometimes I work better in higher levels of abstraction. AI is really helpful there. I can "talk to my ideas" and still get tangible stuff out of it.

[modern nexus]

I also can't draw

Even with a ruler my lines get crooked kinda deal

Illustrator though? Easy peasy

[wet terrace]

I really like ProCreates straight line tool

[gaunt flume]

Ironic how AI used to mean something else...

[sour dust]

Hello,
There is an open PR: https://github.com/home-assistant/frontend/pull/51262 I would like to finish in this release circle. But I think we can improve it even more.

I would like to add a controls card to the existing app and description card. And get rid of the update available card. On the app card we add a update and a open webui action.

I created a mockup with chatGPT (don't take it too series). Open for feedback.

[sour dust]

Hello,

[wet terrace]

Hi 👋

We've been working on a proposal for how Home Assistant organises information across the household, not just for the person who set it up, but for everyone who lives with it.

It's called Home Assistant for the whole household and it introduces a framework of four spaces (Shared, Admin, Personal, Unresolved) to think about who should see what, and who controls what.

I'd love your input. Whether you agree, push back, or have questions, this is exactly the kind of conversation I want to have before anything moves forward.

👉 link to GitHub discussion

Especially curious to hear from designers who think about multi-user experiences and household dynamics.

[opal wyvern]

Hi everyone 👋

Wanted to let you know that we've kicked off the monthly community sync meeting for the #1361754948949512203 yesterday.

Thanks everyone for joining and sharing your questions before, during and after the meeting!

The next sync meeting will take place on 15th of June.

We're going to shape the Discord reminder on that before the best meeting so everyone interested is "alerted" accordingly.

Cross post of the original message and link to some notes: #1361754948949512203 message

[lethal linden]

Hello! Community input needed!

You know that feeling when you are editing a dashboard and you just can’t quite find that field you are looking for? You know it exists but it’s not where you were sure you left it.

We are rethinking how the Edit / Configuration cards are ordered and would love some input by you all.

I’ve made a quick (5 minute) card sorting exercise linked below. Your job is to drag the elements into the buckets that feel important to you.

CARD SORTING HERE

Me and @umbral minnow will then take the results and whip them up into some new solutions. Help us help you!

For roadmap reference-
The roadmap item

The design item

[bitter nymph]

🧵 I'm working on the redoing the Improv workflow and I need a bottom sheet before asking some permission. Does any one have a suggestion? (mostly for the center part that is dynamic could be BLE and Location or only one of them).

[frank yarrow]

how about... keep as is 😂

[opaque narwhal]

I proposed another tab reorder in the associated Github issue... Maybe group things by their purpose... "Content", "layout", "interactions". And split the current "content" and "feature" parameters in those two tabs.

I am not sure that having parameters visible and other parameters hidden will ease approachability and discoverability. The current UI forces you to open the tab.

• Bring back some features aspect ( choice and order) in the first tab should be enough not to "burry" features in the bottom.
• To create room, all layout options ( of the main card and feature) could be grouped together in a second tab.
• interactions tab is good as is.

This could be done the same way for all cards UI.

Not sure the sorting exercise will capture such "harmonisation" opportunities by only sorting parameters by usage...

[umbral minnow]

Please do the sorting if you want your input to count 🙏 we are looking for mass and see tendencies and validation of priorities, from several people. We cant discuss any individual proposal because we have very different projections of what is needed. This is why this solution IS shaped by

• beginner research-validated interviews
• card sorting and priority validation here, with the experienced community

Other topics - yes of course, we can openly discuss perspectives - here we need to be as objetive as we can.

[opaque narwhal]

Ok, fair.

May I just highlight that the two methods you rely on have some intrinsic caveats?
With only this as an "objective metrics", discoverability will be forgotten.

Small exagerated example: will you try a new fruit you do not buy often in the store if it was placed, only based on sales figures and non-fruit-eater interwiews, between tools and garden stuff and not between the other fruits? Surely not...

Those metrics are good, that is not my messagehere. I just hope they are not your ONLY inputs!

Anyway, I did perform the sorting exercise. And while I can say if I want things directly accessible, or burried in the interface, there is no way to propose any grouping other than here or github...
Thus I express here and there my concern about KEEPING what is currently VERY GOOD: a similar interfaces between ALL cards editors. So that anybody is not lost when editing first a Tile, then a shortcut, then a heading card...

(All store share similar layout, fruits with fruits, close to végétable, fish and meat, marketing knows how to make you discover products).

[umbral minnow]

Oh sorry I missed this

a similar interfaces between ALL cards editors. So that anybody is not lost when editing first a Tile, then a shortcut, then a heading card...
Yes, of course, that would be the case - even if we start with tile + expand, the end goal is that everything has the same structure so the mental model makes sense

[umbral minnow]

I want to show you the amazing progress in Suggested cards opportunity - on how to get better recommend people what cards to create in their custom dashboards 💖 .

As you see we did 2 main changes:

• swapped the order - "pick an entity" is now first
• replaced the plain entity selector for the pattern we already have in Automations (that has been thoroughly tested) and added the live preview of results to the right.

We also added a lot of options of configurations to pick from - and removed one extra step from the existing flow.

I hope you like this! its going to be live in next beta probably 🤞🏻

Thanks millions to @lethal linden and @modern torrent for the effort!!!!

[modern torrent]

Thinking of this, should we add more suggestion with more cards non?

[umbral minnow]

yes. Its in another task in the opportunity, to add custom etc. But it is already way better

[civic elm]

This is awesome! I notice the search bar is nested beneath the type/card selector. Is it a conscious decision to not include a "global" search bar, like in the automation trigger/condition picker?

[umbral minnow]

It is - its a filter, not really a sesrch. A global sesrch there is problematic because both tabs have completely different items, you cannot sesrch within the twl

[frank yarrow]

Looks great! I wonder if it could be a toggle you could enable/disable? For example 'Entities first', could affect both this and the automation editor. It means an extra click for me as I never use the entity picker.

[frank yarrow]

Custom would be much appreciated!

[gaunt flume]

this is sooo good. stellar work!

[opaque narwhal]

This was proposed in Github, to cycle between some Tile variant layout ( vertical, inline, default, and back).

But this is already awesome like this!

[trim pagoda]

If you click on an area, does it suggest multiple cards to represent all the things in that area? Or summarizes area in 1 card? Or just a card per entity inside that area ?

[umbral minnow]

In this first iteration, just the entities are selectable - every other element you are able to open, but not select. Because that is a rabbit hole - we want to explore it later

[trim pagoda]

Makes sense

I would love to be able to click on an area and we suggest a whole new area light section, with header + control for that area lights + all area lights as tile cards

but maybe that should be a "smart section", don't know

[umbral minnow]

Yeah, exactly - I want to see how these things evolve and live together. But it is indeed a natural next step.

[noble geode]

That's an opportunity Laura just pitched 😉

[trim pagoda]

Recently Matthias and I chatted a bit about how serial/IR/RF should be pages here in this list. And we wanted to add a popup to inform users when they add a new proxy. And that made me think: We should do that popup for Zigbee and Z-Wave too (basically, any time you unlock a new item in this list)

[woeful plover]

Whats the 'popup' in this scenario, and what does it do?

[trim pagoda]

Today when you add an ESPHome device that adds bluetooth, serial, RF or infrared proxy, you don't know.

We have been discussing that we want to tell the user, "hey, you just added an infrared proxy, this is what is possible now"

But my proposal is that we do that for Zigbee and Z-Wave etc too

[wet terrace]

Recently Matthias and I chatted a bit

Lets use this thread

[dapper pebble]

Some feedback regarding the new “Add to” dialog. Firstly, great addition! However, there are a couple of issues I’ve noticed:

• It feels far too repetitive and long.
• It’s hard to understand what the action is at a glance.

Here’s what I propose:

Header: Add to

Subheading: <device name>

Automations

• Add as Trigger in a new automation
• Add as Condition in a new automation
• Add as Action in a new automation
  Scripts
• Add as Action in a new script
  Scenes
• Add to a new Scene

This reduces repetition by relying on the device context in the subheading, and capitalising the key action words (Trigger, Condition, Action, Scene) makes it easier to scan the list quickly.