Agreed, it seems more often now these “prettifications” / simplifications are being added without sufficient thought into actual usability. I thought they were just fine before. It would be interesting to see if any of this was discussed (and ignored) in beta. A LARGE majority of the time the dev team is spot on, but sometimes we’re left .
I like the Sensor Display precision addition. I have a tone of sensors, and started going through my Dashboard to set the precision. It occurred to me that it would be super handy to be able to perhaps use a configuration parameter in YAML (or the UI) to set the default precision for a particular domain or attribute. There is a default precision specified in the dropdown. Perhaps there is (or could be) a way to set that default value ourselves. I’m thinking something like “all temperature values” or “all humidity values” or something like that.Perhaps that could be considered for a future addition.
Something I only just noticed on the weekend is that since the new light dialog has been implemented I no longer have the ability to alter the white channel of my RGBW lights (running ESPhome). All I have access to is the colour wheel but no white channel setting. Previously I was able to adjust the brightness of the colour and white channels separately. Anyone else aware of this? Is this being looked at? Seems like a pretty bad oversight…
It actually is the homeassistant.reload_all service I mentioned above.
from that PR:
Adds the homeassistant.reload_all service, which can be used to reload YAML configuration for all active domains.
The reason I didn’t think that was it was because I tested it and it didn’t work by just running it as the service call from the services page. I tested it by creating an input_boolean in yaml and ran that service and the input_boolean never showed up in the entities list.
But when I used the reload all yaml button in the yaml tab it did show up.
While I’m probably on the boat with others in regards to the new dialogs and how they’ve become a step backwards for user experience and accessability. I find having to navigate back and forth between two views to fine tune a brightness and colour highly counter-intuitive (it’s not always a matter of thinking a color then changing a brightness will acheive the result you’re after) getting the right result involves fine tuning both almost simultaneously.
But what bothers me more after playing around with WLED today, I noticed I can’t even see what effect is running or even if an effect is running unless i click the icon and scroll through the many options in the list. This I find is bad design.
I also don’t understand what happened to the way where you could set a custom more-info dialog for certain domain and entities from the customise yaml (I think it was there) but I can’t find any information on it anymore so I assume it’s been omitted a while ago.
2023.4.0 released but i can’t find the community discussion on this release. The usual link at the bottom of the release notes isn’t there and google isn’t providing anything useful.
I really don’t like that the new group feature doesn’t shows the entities in that group. There is plenty of unused space. And now we have to navigate multiple times back & forth to change color and brightness, it’s really a step back.
I REALLY hope you add an option to show entities in the group with on/off switch, like before. It was really intuitive.
.
