Auto-populating Dashboards with Strategy Pack - Area Dashboard Strategy

Share your Projects! Dashboards & Frontend
, , ,
63

@itsteddyyo thanks for you reply! i made it!!!

1 Like
64

Heya, no that is not possible as a dashboard strategy needs to be the one creating the dashboard itself :smiley: Only view strategies can be inserted in views.

But the area-dashboard-strategy has a config option ā€œextraViewsā€ and with that you could pass your existing views to the dashboard :smiley:

Like this:

strategy:
  type: custom:area-dashboard-strategy
  config:
    ...other options
    extraViews:
      - ...your views
      - strategy: #just an example
          type: custom:battery-view-strategy
        icon: mdi:test
        path: test
        title: Test
65

Thank you for clarifying the views.
Going back to sorting the areas, I see we can create labels sort:1, sort:2, etc. and the dashboard populates accordingly. In my demo environment, i added the sort labels to get it to be in alphabetical order.

If we have many areas, however, how would you recommend sorting it in alphabetical order and maintaining it when we add areas in the future.
Ex: GYM (sort:1) POOL (sort:2)
Future add BAR (sort:1) ?

Additionally, is it possible to sort by floors?

66

You would need to change the labels assigned to each area :smiley: I think thatĀ“s an okay compromise as that probably wonā€™t happen too much :smiley:

If you only want to sort alphabetically just wait a little. Iā€™m currently working on a big refactor that would among other things allow that. Thereā€™s gonna be a few breaking changes but im pretty pleased with the new design and many caveats and impossibilities of v1 will be improved and the whole configuration will hopefully be more user-friendly :smiley:

Currently there is no support for floors but if you want you can open a feature request (Open Feature Request) and describe how you think the solution should look like :smiley:

67

That sounds great, looking forward to it! Thank you again for the feedback.

68

:rocket: Release 2.0.0 Incoming!

Version 2.0 is finally here! This update brings a complete redesign of the configuration API, along with many exciting new features.

Why the Redesign?

The old configuration API just wasnā€™t cutting itā€”it made customization harder than it should be. Too often, I found myself saying, ā€œThat doesnā€™t workā€ or ā€œYeah, that complicated workaround is the only option.ā€ So, I knew it was time for a changeā€”and here it is! :tada:

:warning: Breaking Changes Alert!

Since this is a major overhaul, there are breaking changes. To make your transition smoother, check out the migration guide: :link: Migration Guide

:tada: Whatā€™s New?

Aside from the breaking changes, thereā€™s plenty to be excited about!

:sparkles: New Features

:bug: Bug Fixes

  • card_mod Fix: The card_mod functionality should work properly in grids.
  • Multiple $entity Replacement Issue: Fixed issues with multiple uses of $entity.
  • Several minor enhancements have been made.

:rocket: Ready to upgrade? Check out the Migration Guide and enjoy the new features! Let me know if you have any questions or run into issues.

Happy configuring! :tada:

69

Hey!

Great work on the newest version.

One question I have:
If I set ā€œposition: 1ā€ for a grid, it will always show up below the default grids, right? (since they are 0 by default).

Will I need to override all their positions?

Maybe it might make more sense for the default to be higher than 0?

I also cant seem to get extraviews to work atm.

I tried this (to replace the battery view):

  extraViews:
    - strategy: null
      type: custom:grid-view-strategy
      config:
        global:
          card:
            type: custom:mini-graph-card
            entities:
              - $entity
            filter:
              include:
                - type: domain
                  value: sensor
                - type: attribute
                  config:
                    key: device_class
                  value: battery
        grids:
          - id: other
            title: Others
            filter:
              include:
                - type: domain
                  value: sensor
                - type: attribute
                  config:
                    key: device_class
                  value: battery

It always automatically adds the ā€˜nullā€™ after the strategy part.
And the view stays empty.

70

Heya, thanks! I really appreciate it! :smile:

Yes, it should always appear after them if the position is greater than 0.
If you donā€™t set a position or set it to 0, it will simply follow the order of the array, meaning it will also be at the bottom.
If you want it to appear before, you can set the position to a negative value (e.g., -1, -2, -3). The lower the number, the higher it will appear in the grid. :smile:

Your formatting seems to be incorrect - you need to specify type and config under strategy, not next to it:

    - strategy:
          type: custom:grid-view-strategy
          config:
              global:

Did I get that wrong somewhere in the documentation? If so, Iā€™m really sorry! Just let me know, and Iā€™ll fix it. :smile: It was a lot of YAML, so maybe one slipped through. :sweat_smile:

71

I was not aware negative numbers were possible with the position.

And I dont think you got it wrong. I tried quite a few things with the extra view and probably got it wrong at some point during trying to get it working. :smiley:

Thanks again. I quite like most changes.

72

Iā€™m a novice at dashboard designing, this sure helps a lot to get somewhat organized. Thanks for creating this.

1 Like
73

Is there anyway to have an Extra View tab go directly to another existing dashboard when you click on it?

74

Extra Views are just regular Home Assistant views, so I donā€™t think thereā€™s any way to make them behave like that. But you can use a card that lets you add a navigation action - like the basic button card (but there are many more) - right in your existing view.

type: button
icon: mdi:chevron-right-circle-outline
show_name: false
show_icon: true
tap_action:
  action: navigate
  navigation_path: /otherdashboard

Thatā€™ll take you to another dashboard when you tap the button :smile:

75

Yeah I figured that was the case. I had setup top cards which do work, but I do like the buttons on the top.

76

Newbie here!!

Iā€™m trying to intergrate Eufy Security with this but the entities the dashboard adds for the cameras dont work without webrtc controls. how do i replace them witht the below so i have the control to turn them on, otherwise they are static images.

type: custom:webrtc-camera
entity: camera.upstairs
poster: image.upstairs_event_image_event_image
ui: true
shortcuts:

  • name: Play
    icon: mdi:play
    service: camera.turn_on
    service_data:
    entity_id: camera.upstairs
  • name: Stop
    icon: mdi:stop
    service: camera.turn_off
    service_data:
    entity_id: camera.upstairs
77

Hey, for that you could use the grid overwrite feature to overwrite the existing row for cameras: Configuration | Strategy Pack

The current camera row is described here in the config: strategy-pack/src/config/areaDefaultConfig.yaml at 7cd904b9473ac5f5aeb38073dfb196668c242515 Ā· itsteddyyo/strategy-pack Ā· GitHub

Edit: forgot to link the FAQ Entry: FAQ | Strategy Pack