I would very much like to make a few comments without being judgmental and without regard to whether others have already addressed the issues.
I am working with students at a university and we are developing our own IoT devices, all of which are integrated into Openhab and controlled by it.
any programmed warnings were programmed in red text that they immediately catch the eye, this is currently no longer recognizable, one is flooded by the many red stimulus and overlooks so important under certain circumstances…
the separation in I say text on the left and actuators on the right helped a bit to avoid unintentional false triggering while scrolling, unfortunately the danger is now completely everywhere, because you can trigger switching actions everywhere…
one must scroll now clearly more, by less compact representation which will increase the faulty operation probably very much, very unpleasantly…
the fast overflightability of the measured values is also unfortunately no longer given by the interrupted text flow through the item names, especially with many measured values this is very unpleasant to read…
I would wish me please, that one much more individually both styles, thus new and old mixed can program, I see quite in the new also advantages, but just not everywhere.
Especially a simple color choice was so far our enthusiasm with Openhab and we have also decided in the university also because of the user interface for OpenHab and against other SmartHome environments.
That you go with the times and that the great app continues to develop, we welcome that very much, but the constraint without notice should really please be reconsidered and rather more design options are given to the users at hand.
In the meantime, the system has grown significantly, but unfortunately I have no time to somehow tinker there again what I get a screenshot of the entire site map.
I think but you can guess how many red elements appear in the sitemap, I have a true sea of red elements, which floods me personally anyway very reiz.
Since I particularly value a dynamic sitemap, many settings and displays are hidden and appear only when needed, or are hidden in submenus.
So by red elements you’re referring to the selected buttons? If so, those aren’t new, are they? They used to be present before as well, just somewhat smaller…
The argument that now is more space for item names, I can not confirm on the contrary as you can see in the heating control, I no longer even see the full °C indication…
in the old view I had as mentioned only warning messages in red, which were then at least conspicuous
significantly more scrolling now with higher risk of triggering operating errors, because the whole display now accommodates the possibility of buttons, which was previously limited only to the right edge strip
That indeed needs improvement. We didn’t have the use case of ‘Text with value, but without label’ in mind. I’ll have a look at this. On the plus side, after fixing that, it’ll look properly, without the alignment error on the left.
However, the app crashed after I set the theme selection to “Dynamic” and can’t be restarted afterwards (it keeps crashing on startup).
The crash is reproducible after deleting the apps data.
Pixel 6a, Android 13. Any other information I can provide?
The new UI looks great and especially with the latest improvements (compact-mode) I think it’s a hugh leap for the app. A big thank you for that!
As one mentioned above I also have trouble with the new behavior of the setpoint item. Even with the update limitation of 200ms you added it is still much too fast for my radiator valves (max! thermostat with homegear and homematic binding). I got errors in the log and the value is not set correctly.
I think also other devices like rollershutters can’t handle updates that fast.
Is there a way to get the “set button” back or to set a user defined update limit? Or as suggeted above a “set on finger release” feature?
