I am trying to get to the EZ Dashboards... and just realized that every device needs to be setup on its own for the arrangement.... this is SO far away from "EZ"... these are just a massive step backwards.
Not being able to force a design for a dashboard is counter to ... a damn dashboard. Really unsure WTF the deal is with these. Now regretting blowing away some of my legacy dashboards. Going to have to rebuild all of them and dump these EZ dashes... since I am not going to go to every device/layout that works with these and manually reconfigure/sort the dashes per layout...
Some items I would like to see... Force a layout to be default and not use all the other ones. Heck you have one called "reactive"... and based on UI design terminology... that should mean design it once and use it on multiple screen sizes. Just bummed that these are so limited in functionality compared to the legacy dashes.
IMHO - building 'ez' dashboards after building dashboards sets a confusion and wrong expectation. I never accepted that part of HE and moved away years ago - I'm content now with an external solution. Again, IMHO, HE is a hub - not a web server, file server, dev platform or dashboard.
I went full-in on legacy dashboards, and I can make them do whatever I want with CSS, so I am happy with them. The legacy dashboards can do so much if you take the time to learn how to modify them, but it is up the person to take the time to learn, or not.
I agree that EZ dashboards are very limited, and the EZ part is not really much easier than using a legacy dashboard without customizations.
Actually Hubitat is all of those, but those features are just not the primary function of the hub, except for the web-based UI which is where the web server is a primary feature to use the hub at all. I store and use all kinds of files on the hub, including html.
well - no doubt we all see it differently. It wouldn't be hard to give a list of shortcomings I have but it is pointless to do so. I use my 'hub'itat elevation as a hub only.
