Default View and Views

Configuration
1

OK this is driving me crazy!

I have been running with just a home view but am splitting my cards into views now. I can’t for the life of me stop the switches and lights from having an overall on/off button - same for all automations. This only happens on the multi tab view. I have control: hidden for the view - I get a validation error if I have it in the group with the entities as I did previously.

devices:
  name: Lights & Switches
  view: yes
  icon: mdi:power
  control: hidden
  entities:
    - group.light
    - group.ios_devices
    - group.scenes
    - group.all_automations
    - group.switch

image
image731×664 37 KB

image

also… is there any way to put my scenes on a card? These displayed by default when I didn’t have different views. I can only see doing it by adding all scenes to a group.

2

Here is an example of the way mine is setup.

I have several tabs (views) and each tab has groups. To hide the control you need to include that in the group definition.

Views:

  default_view:
    view: yes
    name: Main
    entities:
      - updater.updater
      - sensor.sunroom_east_us_sensor_value
      - group.alarm_panel
      - group.mbr
      - group.sunroom
      - group.basement
      - group.garage
      - group.lights
      - group.switches
      - group.media
      - group.cameras
      - group.devices
      
  environment_view:
    view: yes
    name: Environment
    entities:
      - group.severe_alerts
      - group.environment_inside
      - group.environment
      
  automations_view:
    view: yes
    name: Automations & Scripts
    entities:
      - group.notifications
      - group.automations
      - group.scenes
      - group.scripts
      - group.light_motion_control
      - group.input_booleans
      - group.presence_simulation

and here are some groups. one has the control hidden & the other doesn’t:

  mbr:
    name: Master Bedroom
    control: hidden
    entities:
      - switch.master_bedroom_light
      - switch.master_bedroom_fan_1
      - switch.master_bedroom_fan_2
      - switch.master_bedroom_fan_3
      - switch.master_bedroom_fan_0
      - light.sengled_e11g13_030712d6_1

  basement:
    name: Basement
    entities:
      - switch.main_basement_lights_switch
      - switch.basement_workshop_lights
      - switch.basement_dragon_room_lights
      - binary_sensor.water_sensor_main_basement_sensor

Here is what it looks like:

ex
ex1543×689 47.6 KB

1 Like
3

Thanks but you can clearly see in the group I posted that it should be hidden.

4

I can clearly see that you have the “control: hidden” in your view definition. I’m not sure that will work to hide the control for the group cards for each sub group in the view, tho. I think you have to have it in the group definition.

5

In the group if I put control: hidden I get a config validation error.

6

I’m not sure why. you can see it in my examples above and it works perfectly.

what does the error say?

7

Configuration invalid
Invalid config for [group]: value is not allowed for dictionary value @ data[‘group’][‘Light’][‘control’]. Got ‘hidden - light.dining - light.lounge - light.yeelight_white_34ce00887db6 - light.yeelight_white_34ce00882e27 - light.office_light_group - light.office - light.spots’. (See /config/configuration.yaml, line 398). Please check the docs at https://home-assistant.io/components/group/

Light:
  control: hidden
    - light.dining
    - light.lounge
    - light.yeelight_white_34ce00887db6
    - light.yeelight_white_34ce00882e27
    - light.office_light_group
    - light.office
    - light.spots
8

You’re missing the “entities” key.

try:

Light:
  control: hidden
  entities:
    - light.dining
    - light.lounge
    - light.yeelight_white_34ce00887db6
    - light.yeelight_white_34ce00882e27
    - light.office_light_group
    - light.office
    - light.spots
9

funny you should say that… I’m just trying that. The examples in the cookbook don’t have that though and none of the other groups have it either… I don’t know how to do that for the automations though…

10

just create a group with whatever you want to call your automations group and then do the same thing.

here’s mine:

  automations:
    name: Various Automations
    control: hidden
    entities:
      - automation.delay_battery_notify_after_automation_reload
      - automation.delay_battery_notify_after_homeassistant_startup
      - automation.deck_light_off_at_1am
      - automation.deck_light_off_at_sunrise
      - automation.deck_light_on_at_dusk

It will then create a group with those automations and no main control.

11

I edited the customize.yaml and put it in there

group.all_automations:
  friendly_name: Automations
  hidden: false
  control: hidden

It’s already a group… I don’t want to specifically define that group because if I then add an automation I need to remember to add it to the group.

I really wish there was an all_scenes group for the same reason…

12

It works having it in customize as shown. I’d swear I tried that…

13

Cool

All sorted out then?

14

yeah and thanks for your help and helping me think it through.

15

No problem. :grinning: