Templated dashboard for multiple devices

[tilz0R (Tilen)]

I am looking to buy about 6 NSpanel PRO devices, one for each room. All would have the same dashboard design, linked to the specific room (thermostat, lights, motion, presence) as I have all rooms identical. Each room would have different entities to interact with

Is there a way to create a templated (blueprinted?) dashboard, where:

• One can define the blueprint for the dashboard design
• One can create 6 dashboards and use this blueprint as a skeleton
• One can set the entities for each of the buttons, motions, lights, that are dashboard view specific?

Sure it is possible to create 6 dashboards and copy yaml in-between them, then modify the entity names for the light, motion, …

Having a blueprinted dashboard would allow modifications on one location to be propagated everywhere.

[koying (Chris B)]

I use the decluttering card

Lovelace: Decluttering Card

Hey, I’ve created a new card that helps you declutter your LL config if you use multiple times the same block of cards with small differences (like an entity for example) to display things in LL. Visit github for installation instructions, up to date documentation and troubleshooting guide [GitHub Release] [GitHub Activity] [custom_updater] [Project Maintenance] decluttering-card This card is for Lovelace on Home Assistant. We all use multiple times the same block of configuration acros…

[Ildar_Gabdullin]

Using decluttering-card too.
Some people like lovelace_gen - a very powerful thing.

Could be useful:

Calling reusable dashboard with input parameters?

With YAML frontend I have created a bunch of dashboards containing declutter-cards. My problem is that I want to also be able to have “dynamic” dashboards so that they can populate their cards with entities given as input parameters. Why? Well I have quite small on-wall Android screens that can only show 2x3 small cards. A tap on a card that represents a dimmable lamp should open up a full screen control of that dimmable entity to be easily viewed and adjusted. Then that control should be able…

[oneAU]

Yes decluttering-card is a breeze and it was the NSPanel PRO I was referring to in that thread. 90% of my cards contains custom stuff and NSPanel PRO might not have the performance needed for such things or it’s something else that makes the rendering slow for me.
My cards are fully reusable between “views” and some of them are also generic ones that will differ depending on some input parameters.
Here is my look-n-feel:

[tilz0R (Tilen)]

Thanks for sharing. This means that you have:

• One dashboard for all NSPanel
• Definition of the decluttering card skeleton in that dashboard
• More views inside the same dashboard, one for each NSPanel

You use the URL on the NSPanel PRO to open the correct view from the same dashbaord?

If you have a problem to render, it might be because you have more views and they all have to render, even if you don’t show them on all NSPanels.

[oneAU]

You are right.
Only one dashboard.
Several views with shared decluttering-templates.
Using Fully Kiosk Browser that has a specific home URL for each device.

And yes, your comment about too many views to render might be the issue.
That is one of the bullets I have on my debugging todo-list.
(But slow rendering happened in a very early stage as well with just a few views)