@Mutt wrote:
Okay, I was eagerly anticipating 0.107 and the ability to create dashboards (accessability) according to user level.
I’ve played with the functinality and I’m clearly missing something.Basically it seems that I can have views OR dashboards NOT both ??? (please prove me wrong !)
I have 14 views (tabs) and I split functionality accross those views to give general fuctionality in different areas but I also have views that provide “no functionality” (that I want the general user to have access to (z-wave, timers, enables, entities I just want to hide etc.))
Dashbords require a file (per dashboard) in the config folder (why can’t I put them in a ‘dashboard’ sub_folder ? or ALL the lovelace files in a ‘lovelace’ sub-folder ? )
So far the only way I see this working is to replace the top row (tabs/views) with the side column (of tabs/dashboards) with the associated clutter in my config folder
I see that !include 's of lovelace still works so I can either break the yaml down into cards or ‘views’ and basically call the views in at dashboard level.
Is there a wrinkle that I’m just too dumb to see ?
Posts: 1
Participants: 1