Donāt normally post here, but this is a really poor change. The large switch doesnāt add anything, is really far too big, and putting all the relevant actions and info (especially colour / temperature) behind another click is just shockingly bad UX.
Iām assuming that this comment means thereās no going back to a more sensible design (even if an alternative thatās still ānice and cleanā). Is there a way of changing behaviour globally to get an alternative more-info? I know I can make changes in the dashboard to substitute the more-info action on a case-by-case basis, but would prefer not to have to do that everywhere.
I have Home Assistant OS and I face this problem after updating from 2023.2.5 to 2023.3.0 and still exist in 2023.3.1
Which is some of my Gree air conditions disconnected!
I have 10 Gree AC, five of them got this problem with different models.
This entity is no longer being provided by the gree integration. If the entity is no longer in use, delete it in settings.
I tried to restore to 2023.2.5, reconnect my AC, block the AC from WiFi for like 30mins then unblock it and reload Gree Climate Integration but still didnāt solve the problem at all.
I didnāt change anything in WiFi settings, I just update HA and this happened
I tried every sulotion that I can and got luck, any help?
Meanwhile same āone big sliderā more-info is going to be added for input_boolean and cover.
Is it what users do need?
Probably there should be 2 modes:
ā āone big red buttonā - i.e. these āone sliderā view mode;
ā āexpertā mode - a view contains all needed info (as it was before).
And this āexpert modeā checkbox is per-user settings.
These āone big sliderā changes remind me various changes in web sites and applications when developers do not add new features but just change a design to demonstrate a fact that they are working. Hopefully this is not our case.
That information doesnāt really exist. Itās a per integration case. You can check the developer tools ā yaml page. It will show you all things that reload via yaml. If your integration doesnāt exist on that list, then you canāt quick reload it.
I managed to install newer pybluez from github, however this did not solve the issue. Seems like device_tracker integration requires pybluez==0.22 and forces HA to install this version, which is not compatible with python 3.11.
I failed to migrate to venv python 3.11 because of this issue.
I do enjoy the new more info pop up for light and switch entities. Canāt wait to see more of them for covers and co.
It would be great if it considers groups enabling to set each entity within the group. For example similar to Hue, where the color of each light of the group can be set using the same color wheel.
Also it would be great if a lovlace button card with the look of a vertical switch/slider would be available.
While Iām not opposed to the streamlined appearance of the dialogs, this change does require more clicks of me. For example, instead of being able to close the dialog box directly if I move to the settings tab (in the old version), now I have to go back to the main tab to be able to click the X to close to dialog.
Windows has done this to us over the years as wellā¦ they have caused many activities to require more and more clicks than in prior versions, all in the name of āimprovementā or āstreamliningā or āsimplifying.ā Sometimes leaving well enough alone is the better answer.
Unfortunately the light dialogs are a step in the wrong direction for me. Instead of having the brightness/color controls on one page with the switch, now there is one huge ugly slider, and for color controls an additional click on a tiny icon is needed. Poor usability, especially on mobile.
Is there a way to revert back to the old style, or enable additional controls on the same page?
I have always been fighting with the slider in the old interface. I often had to try 2 or 3 times before the tip of the finger catch the slider to change intensity.
Now I can swipe in a second. I rarely change colour. I always change intensity.
I would think the buttons below the slider could be spaced a little more apart. They are very close on a phone - my finger covers two buttons
You need custom quirks if you have a device that isnāt fully handled in ZHA yet. I have a couple of presence sensors that I need the quirks for, Iām assuming others have similar issues.