Yes but have they been put in core now?
1 Like
In my case no, (I tried removing the custom quirk as the 1st test - ZHA starts but the device lacks functionality), and there is a still an open issue marked ācustom-quirk availableā for my device.
I suspect the number of similar issues with this release will see a bunch of custom quirks merged into zha-device-handlers in the next week or so.
1 Like
While I can understand the choice for adding the Light Slider / Button Options into the āmore infoā screen,
I can also understand those who donāt like that feature.
Especially with the new tile card, this slider on the āmore infoā page isnāt really something that adds much usability - since the slider on the tile card itself can be controlled pretty well on mobile phone screens.
Maybe, it should really be considered to add another option to check, if HA will be used with the Companion App - and then, display the sliders / buttons on the MoreInfo dialog - and if not, use the default as it was before?
Personally, I still donāt really care about those changes, because I barely use the more info dialog nor relly need to see the history for much of the affected entitiesā¦ at least, not on a regular basis - but I can fully understand the frustration for those who need the old way the more info dialog behaved.
7 Likes
Dont mind the new dialog boxes, but please can we have an option to supress the show more option.
Designing touch screen interfaces is impossible with this option. I have supressed all header and sidebar options, but the show more option seems to disregard the user rights and allows the user to exit the dashboard , forcing me to reboot the device to regain control. Yaml mode should allow this level of control .
Same problem here but after installing the 2023.3.1 update. I had my energy sensors set to W instead of kW after the 2023.3.0 update, which worked, but looks like itās broken in the 2023.3.1 updateā¦
I just tried something, I changed the rounding to 3 decimals and now it reset itself to W instead of kW. I now changed the rounding back to 0 decimals and now itās fine againā¦
Thanks! Good to know.
The problem is, these kinds of changes will continue. At some point the things you do care about will be tweaked to make them less useful.
This reminds me of Microsoft. After they stopped adding any meaningful improvements to their office products, they started just changing the UI in every version to make it look āfresh.ā Thatās great if your goal is to encourage people to pay for the update, or pad your resume as a designer. Not so good if youāre a user just trying to get a job done.
For a long time in the business world, weād look forward to new software versions. They usually gave us new features and made existing ones easier to use. At some point that changed, and we (users and support staff alike) started dreading updates. Changes would make things harder, ādumb downā the interface by removing functionality which might confuse beginners, and introduce bugs.
Iād hate to see HA go in that direction.
15 Likes
Still hat a Migration Failed error with 2023.3.1 so at least for me it did not work.
With the new Info-Layout of Light-Entities I canāt see the time since the last state change. When removing information from one layout it would be nice to at least put it in a sub-menu.
4 Likes
This may happen especially with users which are not explicitly supporting every change but attacking users who dare to criticize. Visit any Apple forum, there are plenty of users who shut down every attempt to criticize. Sorry for my broken English.
4 Likes
It goes both ways; no one likes to be attacked. Thatās something self-styled critics should consider when they express their untempered criticism.
With every new release, itās become increasingly common for users to freely attack a developerās work and, sometimes, even the developer. When I say āattackā I mean to criticize in a manner that is not constructive.
Thereās nothing daring about venting oneās unfiltered opinion. Whatās more challenging is to express it as constructive suggestions for improvement (free of whatever frustration one might be feeling).
If someone wants to attract a positive reaction to their commentary, they should not dismiss, mock, or insult a developerās contributions to the project. If the contribution falls short of your expectations, simply explain what you believe could improve it.
Constructive criticism has served to improve Home Assistant and is welcomed. The same isnāt true for unconstructive criticism.
17 Likes
I absolutely agree that critics must be constructive, not just āwtf?!ā especially from people who do not read docs. Have to deal with it almost every day on GitHub repos for some custom plugins/cards.
As for the last months - there was a tendency of ignoring userās complains, no wonder users are āheatedā and disappointed.
May be I want too much - but I think that Dev team should ask Community before adding features which may not be liked. Or, they should reconsider some solutions if they get a negative feedback. Good example - more-info with statistical data instead of precise history. Was it reconsidered after usersā complains? No.
Another example - using names instead of entity_ids in Dev tools, History and plenty other places. Was it reconsidered? Again no.
So, what users can expect with these ābig nice slidersā?
14 Likes
@home assistant devs
Do you read the positive but also negative feedback from community? And does it matter / is it taken seriously?
Iāve been participating in this community forum since late 2018 and donāt recall the development team ever asking the community to vet a feature. In other words, historically, itās not how the product is managed.
Like other open-source software projects, itās run like a ābenevolent dictatorshipā. Paulus chooses the projectās direction and is the ultimate arbiter of which contributions are accepted or rejected (I think that responsibility is also delegated to his employees at Nabu Casa).
Undoubtedly some user feedback does shape the project (i.e. some Feature Requests are eventually implemented) but my impression, based on observations, is that major decisions for the productās functionality and appearance arenāt based on user surveys. Again, just my impression; Iām not privy to how things actually work at Nabu Casa.
11 Likes
But most of us want the system be the PERFECT.
Like āletā use only AM/PM format ā - some people like it, some not; everyone may choose his preferred format. This is a simple example, but same could be implemented for graphs in more-info: use precise history in one tab, approximate statistics in another tab - as you wish. Or for these ālarge slidersā: select a simple āsimple modeā - see your large slider, select āadvanced modeā - see all staff together.
6 Likes
I agree with you. Basically what we see happening here is a āstupidificationā of the user interface.
Make trivial buttons/sliders bigger, and make stuff you need harder to find, hidden behind more unnecessary clicks.
8 Likes
There have been several comments asking people if they waited for the Database migration to be completed. Does this migration provide any progress indicator? or completion notice?
I had these:
recorder.migration] Database is about to upgrade from schema version: 33 to: 35
recorder.migration] Adding columns created_ts, start_ts, last_reset_ts to table statistics.
recorder.migration] Adding columns created_ts, start_ts, last_reset_ts to table statistics_short_term.
recorder.migration] Adding index `ix_statistics_start_ts` to database.
recorder.migration] Adding index `ix_statistics_statistic_id_start_ts` to database.
recorder.migration] Adding index `ix_statistics_short_term_start_ts` to database.
recorder.migration] Adding index `ix_statistics_short_term_statistic_id_start_ts` to database.
That was hours ago with nothing since. Nothing seems to report ādoneā. Can someone give a clue what Iām waiting for? HA itself seems to be operating fine. No issues. No errors logged.
1 Like
Yeah i agreeā¦ Also try to find this:
Its hidden in a nested tree sub menu and takes like 7 clicks or soā¦
Menu > Settings > System > Repairs (whyyy???) > Again menu top right > System info
Is there a more simple method?
10 Likes
Is the history graph card broken for anyone else? The data is incorrect when I have more than one entity displayed.
If the Persistent Notification about the DB upgrade is cleared (it auto clears) then the upgrade is doneā¦thats how it should work anyway
1 Like