Dashboards vs views

Configuration Frontend
1

There are “views” and “dashboards” - I think I understand the differences between the two; views behaves like “tabs” within a dashboard.

What I’m stuck on is what makes a good dashboard vs a good set of views within a dashboard.

Maybe my system just isn’t big enough yet? Maybe the two features are kind of redundant? Can anyone share their usage of views and dashboards to help me calibrate?

For context, I currently have the following Dashboards:

  • Plants (8-ish devices)
  • 3d printer (1 device)
  • Bedroom (one device)
  • Robot Vacuum (1 device)
  • Chores (no devices)
  • Climate (1 device)
  • Music (5 devices)
  • Cat (3 devices)
  • Security (3 devices)
  • Server status (1 device)
1 Like
2

I think it’s whatever works for you. I have an overview dashboard containing all devices, which consists of three views, one for each floor. Another example - a Dashboard showing the LQI values for all my Zigbee devices: two views, one for routers and one for end devices.

How are you going to use the dashboards? If it’s on a touchscreen device, there’s a custom component which allows you to swipe between views.

1 Like