Thank you 
1 Like
I donât want that my workflow is changed over the night. I use this for years and then one morning I wake up with different workflow.
Truth to be told, ok, it make sense but it takes time to adopt it.
Yes, sure I am my own admin for everything, from opnsense, to openwrt to my linux server running ha in docker container.
1 Like
Honestly, i can never âadoptâ to the pathetic Looking ( Mobile User UI ) under /config ( Settings ) 1 Vertical-Line of badges ⊠What is this for an Idea for a Admin-Section ?
Well i assume No one really cares, how HA looks âBehind The Curtainâ
UX experience for a PC/Laptop & +10inns User ? , Unbelievable Worst than iâve ever seen anywhere before 
When I started with HA, it took me a while, and I realized âOh, itâs a Docker container.â Why the hell did they not call it that? I still have the same question. Call it what it is.
1 Like
I agree to certain point with you. It really doesnât matter how it look if it delivers. It is home automation platform after all.
Look at openwrt. Does it have looks? Not really, but it delivers. No one using it for looks.
I agree that it is wasting money, energy and time on polishing gui and over complicating it in the process.
It would be much better if they focus on integrations and work uner the hood of ha then on gui. It seems to me that they started to add more integrations in x.3 version, but will see will they continue to improve gui or will they finally go and work under the hood.
1 Like
There are separate teams. The UI team works on the UI. The backend team works on the backend. The backend team is constantly updating the backend every release. You donât want the UI team to work on the backend because they donât know python, they are the frontend team after all.
TDLR: Your post about focusing on the backend doesnât make sense because thatâs already the focus of the backend team.
4 Likes
This feels a bit hypocritical, I use the dashboards/UI daily and its not just a backend/automation tool for me. A lot of folks use it this way as well (just look at all the threads of folks posting their dashboards/custom UIs). Folks can use HomeAssistant in their own ways, but I think theyâre trying to clean up choices made in the past before they got bigger. Its going to require breaking changes to do so, and theyâre giving a heads up (and donât force one to update).
3 Likes
Iâm just an user and Iâm not familiar with development of ha. I just didnât saw some breaking changes for me for a long time. The last thing after a while was roborock integration that finally was usable after a long period of time. You are most likely right because you know how this look from the inside and I donât.
Look give it a rest. No you will not update and use two year old version of ha.
Yeah right.
I donât update anything manually, system is doing this for me.
Wow, i did not even know that HA could update automatically. I always thought you had to approve an update. Learn something new everyday.
Sure it can. But it depends on how you set things up.
Iâm doing manual updates only for things I consider important if something goes wrong like openwrt routers or opnsense gateway.
But even my debian server updates it self automatically, so why wouldnât ha?
Oh, not questioning you. I just didnât know you could. Where do you go to tell HA to automatically update?
I donât know. Iâm using ha core in docker container and container that updates other containers automatically if you wish.
Ah, gotcha. Thanks for the responses. I did not mean to get off topic. I will bailout now. 
No problem.
Youâd have to make an automation. There is no âtoggle to turn on updatesâ function
1 Like
Oh, I was counting on the old attributes being back. After the update I find out that there was actually no revert. They screwed up even more, I really wasnât looking forward to the new update at all. Destroyed browser popup, confused layout of the more info dialog.
It seems to me more and more that the entire frontend dev team doesnât know what theyâre doing and what their goals are. Discord is still only dealing with new built-in dashboards. They are not interested in anything else. They donât care about any of the arguments made for the changes. Is this really what a modern UI should look like?
With every new update, I quietly curse what the **** theyâve done again.
Moving away from mdc components to webaewsome is inevitable given mdc is now unsupported. All credit to devs on this one for answering all my questions on the dialog migration so Browser Mod could follow 2026.3.0 with its 2.8.0 release. Any impact to syling general Browser Mod popups is documented - first link below. A summary of dialogs changes and styling with Uix check second link below.
1 Like
I hoped as well but then saw, that it was reverted/developed but then overruled/stopped again with another approach unspecified.
True but I would say that makes a case for moving to a more general Tools section rather than cramming more tools into Settings.